Just comment it out of the image generator section of
skins/Standard/skin.conf to stop the plotg being created and comment out
the references to the appropriate plot in the plot division towards the end
of the templates. You may even be able to use the same method as for the
tabular (see how
Newbie question – I have a SDR “station” that doesn’t (yet) have an indoor
temp.
I used “if $day.inTemp.has_data” (week, month,year) tro suppress the tabular
stuff; but can’t seem to figure out how to suppress the graph.
Help?
Clay Jackson
--
You received this message
Yeah – and now that I’ve done it; it definitely makes sense – caught me by
surprise more than anything.
From: weewx-user@googlegroups.com [mailto:weewx-user@googlegroups.com] On
Behalf Of Andrew Milner
Sent: Sunday, February 5, 2017 9:57 PM
To: weewx-user
Aha - that makes more sense now - a little bit more than just a
reconfiguration (depending on how you were running the simulator and what
dates/times you were using). Yes, switching from 'test mode' to 'live
mode' would more than likely require the database tables being dropped,
NOAA files
Yeah – I changed the station type from simulator (testing) to SDR (I have an
Acurite 5n1 with a console that does not support USB).
From: weewx-user@googlegroups.com [mailto:weewx-user@googlegroups.com] On
Behalf Of Andrew Milner
Sent: Sunday, February 5, 2017 8:12 PM
To: weewx-user
Hello,
I have an RPi properly configured to allow the /dev/ttyAMA0 serial port to
work. To verify this, I've jumpered pins 8 & 10 on the RPi GPIO connector,
so data is looped back as I type. When connecting the VP2 and running
'sudo wee_device' I get:"weewx.WakeupError: Unable to wake up
Clay - since weewx configuration changes do not usually require a database
to be dropped and recreated empty can you clarify what reconfiguration
changes you had made and what the logs showed?
On Sunday, 5 February 2017 22:26:35 UTC+2, Clay Jackson wrote:
> Problem solved! Turns out that
thanks for the fast replay
sorry for the post didn't know about a new version
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
On Sunday, February 5, 2017 at 11:10:03 AM UTC-5, Radar wrote:
>
> showing N/A for temp and dewpt
>
> snip of the log
>
the parser was not handling cases where temperature (or dewpoint) were
double-digit negative numbers leading the 6-hour forecast block.
fixed at forecast v3.2.12
m
--
You
Thnx Tom, for clarifying that.
Op zondag 5 februari 2017 20:45:24 UTC+1 schreef Tom Keffer:
>
> Depends on the hardware and the setting of record_generation.
>
> If record_generation=hardware, and the hardware emits it, then that value
> is used.
>
> Otherwise, weewx calculates it as the average
Depends on the hardware and the setting of record_generation.
If record_generation=hardware, and the hardware emits it, then that value
is used.
Otherwise, weewx calculates it as the average wind speed over the archive
interval.
-tk
On Sun, Feb 5, 2017 at 11:16 AM, Eelco F
In addition to this, how is the value of $current.windspeed defined? Is it
a 10 minute average, as defined in determining beaufort windforce? Or is it
just the latest measurement at the moment when creating the html pages.
If so, should I use $span(time_delta=600).windSpeed.avg.formatted to
That did the trick. Thanks again Tom
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit
Tnx a lot
Tested and success
then the problem is wu
El domingo, 5 de febrero de 2017, 16:58:30 (UTC+1), Tom Keffer escribió:
>
> It is almost surely the Weather Underground, but here is a way to check.
> Copy and paste the following URL into a browser:
>
>
>
The initializer for the TimespanBinder object takes an argument 'context',
which is what formatting to use for time. The default is "current". Other
options are "hour", "day", "week", "month", "year", and "rainyear". Choose
one of those, depending on whether you are displaying an aggregate over a
On Sunday, February 5, 2017 at 11:44:05 AM UTC-5, Francisco Puig wrote:
>
> I'm trying to add to weewx V3.6.2 the weatherbug support, I added;
>
> [[WeatherBug]]
> publisher_id = pX
> station_number = Y
> password = YOUR_WBUG_PASSWORD
>
> to the weewx.conf but I
I'm trying to add to weewx V3.6.2 the weatherbug support, I added;
[[WeatherBug]]
publisher_id = pX
station_number = Y
password = YOUR_WBUG_PASSWORD
to the weewx.conf but I don't know if anything else is needed.
Thanks.
--
You received this message because
the 3hrly is fine but the 6hrly showing N/A for temperature and dewpoint
config setting
[[NWS]]
lid = NDZ011
foid = BIS
just a thought is that the temp and dewpt has minus that is one space in
front of the 06 row
6hryl00
temp -10
i attached a snap shot of part the forecast
--
>
> ii libusb-0.1-4:armhf 2:0.1.12-25
> armhfuserspace USB programming library
> ii libusb-1.0-0:armhf 2:1.0.19-1
>armhfuserspace USB programming library
> ii
showing N/A for temp and dewpt
snip of the log
Feb 5 10:00:14 localhost weewx-3.6.2[7669]: interceptor: ServerThread:
sniff: timestamp=1486310414.93 pktlen=60 data=00 24 21 1f 7d 8c 24 c8 6e 01
76 5d 08 00 45 00 00 28 06 cb 00 00 64 06 26 2e c0 a8 02 0e 34 14 33 0d 10
17 00 50 b9 42 04 03 87
It is almost surely the Weather Underground, but here is a way to check.
Copy and paste the following URL into a browser:
http://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?action=updateraw=YOURSTATION=YOURPASSWORD=weewx-3.7.0a1=26.8=2017-02-02%2023%3A25%3A00
Then
I am having some problems updating wunderground.
Have a look:
Feb 5 16:35:37 raspberrypi weewx[20333]: restx: Wunderground-PWS:
Published record 2017-02-05 16:35:00 CET (1486308900)
Feb 5 16:40:40 raspberrypi weewx[20333]: restx: Wunderground-PWS: bad
login; waiting 60 minutes then
the 0.18rc3 driver *should* handle the 'no data available' and 'no error'
conditions properly for english, italian, german, french, and spanish
locales.
it does not yet handle timeouts properly. ideally it would recognize and
ignore timeouts on the initial communication, then recognize and
On Sunday, February 5, 2017 at 7:34:02 AM UTC-5, Alberto Sánchez wrote:
>
> Hi mwall,
>
> I am testing your new WMR300 drivers. 0,18rc2. It collects me data
> correctly but reports me this error:
>
> Feb 05 13:29:16 raspberrypi weewx[1369]: wmr300: e.errno=None
> e.strerror=None e.message=could
On Sunday, February 5, 2017 at 2:47:32 AM UTC-5, Clay Jackson wrote:
>
> Just getting started with weewx and an Acurite station that does not
> support USB - so, I'm using SDR/RTL.
>
> If I set up to use a MySQL (Maria, actually) database on a different
> server, when I start weewx, the RTL
Hi mwall,
I am testing your new WMR300 drivers. 0,18rc2. It collects me data
correctly but reports me this error:
Feb 05 13:29:16 raspberrypi weewx[1369]: wmr300: e.errno=None
e.strerror=None e.message=could not detach kernel driver from interface 0:
No data available repr=USBError('could not
26 matches
Mail list logo