Re: [weewx-user] Wind direction wmr200

[Thomas Keffer]

Follow up to the rest of the group: I have not heard back from Franck, but
I'm pretty confident this was caused by a bug in the WMR200 driver that
effectively caused the value for ignore_zero_wind to be ignored. Fixed in
commit da0a31e.

-tk

On Sun, Sep 24, 2017 at 3:42 PM, Thomas Keffer  wrote:

> Please send your weewx.conf file to me in a private email. You may want to
> obfuscate any passwords first. My email address is tkef...@gmail.com
>
> -tk
>
> On Sun, Sep 24, 2017 at 11:33 AM, jahfly1000  wrote:
>
>> hello
>>
>> "sudo weewxd weewx.conf" no work just "cd / home / weewx
>> sudo
>> ./bin/weewxd weewx.conf"
>> Because i installed weewx using setup.py
>>
>> and i use the "sudo /etc/init.d/weewx restart" command
>>
>> my first rec
>>
>> REC:2017-09-24 20:00:00 CEST (1506276000) altimeter: 30.0319972875,
>> appTemp: 67.2474531037, barometer: 30.0429462776, clockUnsynchronized: 0.0,
>> cloudbase: 4485.52191023, dateTime: 1506276000.0, dewpoint: 48.1924182234,
>> ET: None, forecastIcon: 6.0, heatindex: 67.64, humidex: 69.1315325364,
>> inDewpoint: 56.8044164637, inHeatindex: None, inHumidity: 51.0, inTemp:
>> 76.28, interval: 5, maxSolarRad: 0.0, outHumidity: 49.75, outTemp: 67.64,
>> outTempBatteryStatus: 0.0, outTempFault: 0.0, pressure: 29.9729373125,
>> rainBatteryStatus: 0.0, rainFault: 0.0, usUnits: 1, uvBatteryStatus: 0.0,
>> uvFault: 0.0, windBatteryStatus: 0.0, windchill: 67.64, windDir: None,
>> windFault: 0.0, windGust: 5.63709346689, windGustDir: None, windrun:
>> 50.0497166216, windSpeed: 0.0
>>
>>  and after stop
>>
>> REC:2017-09-24 20:20:00 CEST (1506277200) altimeter: 30.0319972875,
>> appTemp: 66.3488980482, barometer: 30.0430757159, clockUnsynchronized: 0.0,
>> cloudbase: 4199.28441572, dateTime: 1506277200.0, dewpoint: 48.4798631992,
>> ET: None, forecastIcon: 6.0, heatindex: 66.668, humidex: 68.2846680055,
>> inDewpoint: 56.6389574404, inHeatindex: None, inHumidity: 51.0, inTemp:
>> 76.1, interval: 5, maxSolarRad: 0.0, outHumidity: 52.0, outTemp: 66.668,
>> outTempBatteryStatus: 0.0, outTempFault: 0.0, pressure: 29.9729373125,
>> rainBatteryStatus: 0.0, rainFault: 0.0, usUnits: 1, uvBatteryStatus: 0.0,
>> uvFault: 0.0, windBatteryStatus: 0.0, windchill: 66.668, windDir: None,
>> windFault: 0.0, windGust: 0.0, windGustDir: None, windrun: 50.4613139224,
>> windSpeed: 0.0
>>
>> Sep 24 20:20:02 raspberrypi weewx[29817]: wmr200: MainThread: D   Queuing
>> live packet rx:72 live_queue_len:1
>> Sep 24 20:20:03 raspberrypi weewx[29817]: wmr200: MainThread: D genLoop()
>> Yielding live queued packet id:78
>> Sep 24 20:20:07 raspberrypi weewx[29817]: wmr200: MainThread: D   Queuing
>> live packet rx:73 live_queue_len:1
>> Sep 24 20:20:07 raspberrypi rsyslogd-2007: action 'action 17' suspended,
>> next retry is Sun Sep 24 20:21:37 2017 [try http://www.rsyslog.com/e/2007
>> ]
>> Sep 24 20:20:08 raspberrypi weewx[29817]: wmr200: MainThread: D genLoop()
>> Yielding live queued packet id:79
>> Sep 24 20:20:11 raspberrypi weewx[29817]: wmr200: MainThread: D
>> Acknowledged control packet rx:7
>> Sep 24 20:20:13 raspberrypi ntpd_intres[688]: host name not found:
>> 192.168.1.20/weewx
>> Sep 24 20:20:17 raspberrypi weewx[29817]: wmr200: MainThread: D   Queuing
>> live packet rx:74 live_queue_len:1
>> Sep 24 20:20:18 raspberrypi weewx[29817]: wmr200: MainThread: D genLoop()
>> Yielding live queued packet id:81
>> Sep 24 20:20:18 raspberrypi weewx[29817]: manager: Added record
>> 2017-09-24 20:20:00 CEST (1506277200) to database 'weewx.sdb'
>> Sep 24 20:20:18 raspberrypi weewx[29817]: manager: Added record
>> 2017-09-24 20:20:00 CEST (1506277200) to daily summary in 'weewx.sdb'
>> Sep 24 20:20:19 raspberrypi weewx[29817]: reportengine: Running reports
>> for latest time in the database.
>> Sep 24 20:20:19 raspberrypi weewx[29817]: wmr200: MainThread: D genLoop()
>> phase getting live packets
>> Sep 24 20:20:19 raspberrypi weewx[29817]: reportengine: Running report
>> StandardReport
>> Sep 24 20:20:19 raspberrypi weewx[29817]: reportengine: Found
>> configuration file /home/weewx/skins/simple/skin.conf for report
>> StandardReport
>> Sep 24 20:20:19 raspberrypi weewx[29817]: cheetahgenerator: using search
>> list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station',
>> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats',
>> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
>> Sep 24 20:20:19 raspberrypi weewx[29817]: manager: Daily summary version
>> is 2.0
>> Sep 24 20:20:20 raspberrypi weewx[29817]: wmr200: MainThread: D   Queuing
>> live packet rx:75 live_queue_len:1
>> Sep 24 20:20:21 raspberrypi weewx[29817]: wmr200: MainThread: D genLoop()
>> Yielding live queued packet id:82
>> Sep 24 20:20:23 raspberrypi weewx[29817]: cheetahgenerator: Generated 8
>> files for report StandardReport in 4.46 seconds
>> Sep 24 20:20:23 raspberrypi weewx[29817]: 

Re: [weewx-user] Re: Intermittent dew point data to Wunderground

[Thomas Keffer]

Take a look at this longish discussion about rtfreq
.

TL;DR?

It's there to provide a refresh rate for the WU flash plugin. Otherwise,
it's ignored.

-tk

On Mon, Sep 25, 2017 at 4:12 PM, gjr80  wrote:

> RF may well be the culprit though with the RF cache it should be behaving
> (with all WU's foibles I have to wonder though what WU does with RF updates
> that have rtfreq=2.5 when in fact they aren't). Might be worth setting
> debug=2, stop/start weeWX then when WU goes haywire have a look at what
> weeWX was publishing at that time (and 5-10 minutes either side).
>
> As an aside, I don't know any details of your weeWX setup but weeWX is
> complaining about not being able to find any of your skins. If you don't
> want to run the reports then just remove the StdReport service (
> weewx.engine.StdReport) from the list of services to be run at
> report_services in weewx.conf.
>
> Gary
>
> On Tuesday, 26 September 2017 02:02:51 UTC+10, Tom Keffer wrote:
>>
>> The WU screenshot you posted is for a different time period than the LOOP
>> packets you showed, but it appears that dewpoint is being emitted often
>> enough (about once every 30 seconds) for the WU to show a value. Not so
>> sure about barometer. There are some long gaps without values, so it's
>> possible there were some 5+ minute gaps during the time period of the
>> screen shot, which would lead to no value being recorded by the WU.
>>
>> I've learned through the years that the WU database is just plain
>> unreliable. It occasionally drops points and there isn't anything you can
>> do about it except drive yourself crazy trying to figure it out.
>>
>> It's worth trying without Rapidfire. You may have to choose between using
>> RF and having consistent dewpoint values.
>>
>> -tk
>>
>> On Mon, Sep 25, 2017 at 8:46 AM, Patrick Boyle  wrote:
>>
>>> I've attached a copy of syslog w/ debug=1, and also a copy of some LOOP
>>> data. There is also a screenshot from Wunderground showing that temp and
>>> humidity is there, but no dewpoint. I've also noticed there is no
>>> barometric pressure when dewpoint is absent.
>>>
>>> I do have rapidfire enabled, which I'd like to use if possible.
>>>
>>> On Friday, September 22, 2017 at 9:48:05 PM UTC-6, Patrick Boyle wrote:


 Hello, new weewx user here. Loving it so far. It's working perfecty
 with one exception. When looking at my station on wunderground I see
 extremely intermittent dew point data, as in there are hours of time
 between little blips of data. However, looking at the console I can see a
 dew point value being reported regularly. How should I go about
 troubleshooting this?

 Thanks!

>>>
>>> --
>>> 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+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> 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 https://groups.google.com/d/optout.
>

-- 
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 https://groups.google.com/d/optout.

Re: [weewx-user] Re: Intermittent dew point data to Wunderground

[gjr80]

RF may well be the culprit though with the RF cache it should be behaving 
(with all WU's foibles I have to wonder though what WU does with RF updates 
that have rtfreq=2.5 when in fact they aren't). Might be worth setting 
debug=2, stop/start weeWX then when WU goes haywire have a look at what 
weeWX was publishing at that time (and 5-10 minutes either side).

As an aside, I don't know any details of your weeWX setup but weeWX is 
complaining about not being able to find any of your skins. If you don't 
want to run the reports then just remove the StdReport service (
weewx.engine.StdReport) from the list of services to be run at 
report_services in weewx.conf.

Gary

On Tuesday, 26 September 2017 02:02:51 UTC+10, Tom Keffer wrote:
>
> The WU screenshot you posted is for a different time period than the LOOP 
> packets you showed, but it appears that dewpoint is being emitted often 
> enough (about once every 30 seconds) for the WU to show a value. Not so 
> sure about barometer. There are some long gaps without values, so it's 
> possible there were some 5+ minute gaps during the time period of the 
> screen shot, which would lead to no value being recorded by the WU.
>
> I've learned through the years that the WU database is just plain 
> unreliable. It occasionally drops points and there isn't anything you can 
> do about it except drive yourself crazy trying to figure it out.
>
> It's worth trying without Rapidfire. You may have to choose between using 
> RF and having consistent dewpoint values. 
>
> -tk
>
> On Mon, Sep 25, 2017 at 8:46 AM, Patrick Boyle  > wrote:
>
>> I've attached a copy of syslog w/ debug=1, and also a copy of some LOOP 
>> data. There is also a screenshot from Wunderground showing that temp and 
>> humidity is there, but no dewpoint. I've also noticed there is no 
>> barometric pressure when dewpoint is absent.
>>
>> I do have rapidfire enabled, which I'd like to use if possible.
>>
>> On Friday, September 22, 2017 at 9:48:05 PM UTC-6, Patrick Boyle wrote:
>>>
>>>
>>> Hello, new weewx user here. Loving it so far. It's working perfecty with 
>>> one exception. When looking at my station on wunderground I see extremely 
>>> intermittent dew point data, as in there are hours of time between little 
>>> blips of data. However, looking at the console I can see a dew point value 
>>> being reported regularly. How should I go about troubleshooting this?
>>>
>>> Thanks!
>>>
>>
>> -- 
>> 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 https://groups.google.com/d/optout.

[weewx-user] Re: problems with pressure on WeatherRanger

[Damjan Hajsek]

here are loop packets again, before I forget to disable calibration

http://zerobin.povej.net/?170843575d112ab6#m8n6suRJmh/WbTp9FTuSxwETZKDodPNnJQbQ4R4h4bw=

Dne ponedeljek, 25. september 2017 21.54.07 UTC+2 je oseba Damjan Hajsek 
napisala:
>
> Here are packet I hope this time I get right packets.
>
>
> http://zerobin.povej.net/?617f993cae15cb3f#c/uDiL2ZHhGvTFQQ8sZgY0ILHUuhFKcBVsB/rFdxdE8=
>
>
>
> Dne petek, 22. september 2017 13.55.41 UTC+2 je oseba Andrew Milner 
> napisala:
>>
>> Where are the LOOP and REC packets??  They are not in the file you 
>> posted. 
>>
>>
>>
>> On Friday, 22 September 2017 14:28:02 UTC+3, Damjan Hajsek wrote:
>>
>>> Here is a link for values I write both preassure and rain rate and below 
>>> data from weewx.
>>> When I manually start weewx I get some errors so half is with manually 
>>> starting weewx and half when restart weewx.
>>>
>>>
>>> http://zerobin.povej.net/?2b67951062395755#msXGtrC6ARHSBTBUCDj5qdeV920nG2FzZbloR3nozAI=
>>>
>>>
>>>
>>> Dne četrtek, 21. september 2017 19.43.59 UTC+2 je oseba mwall napisala:

 On Tuesday, September 19, 2017 at 7:54:35 AM UTC-4, Damjan Hajsek wrote:
>
> About preassure,  I use absolute preassure which is higher than sea 
> level preassure, my altitude is 293m (I have this setting in weewx.conf). 
> When I checked my absolute preassure it was about 1008mbar until sea 
> level 
> was I think about 995mbar. But I have always set to absoulte preassure 
> and 
> when is absoulte preassure 1010mbar weewx shows 1008 mbar.
>
> Dne torek, 19. september 2017 13.38.51 UTC+2 je oseba mwall napisala:
>>
>>
>> regarding pressure, are you comparing apples to apples?  is the 
>> console reporting gauge pressure or sea level pressure?  what is the 
>> station altitude?
>>
>
 run weewx directly.

 post the output from a few LOOP packets, not the log output.  for each 
 LOOP packet you post, also post the value for pressure that was displayed 
 on the console at the time of that LOOP packet.

 m

>>>

-- 
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 https://groups.google.com/d/optout.

[weewx-user] Re: problems with pressure on WeatherRanger

[Damjan Hajsek]

Here are packet I hope this time I get right packets.

http://zerobin.povej.net/?617f993cae15cb3f#c/uDiL2ZHhGvTFQQ8sZgY0ILHUuhFKcBVsB/rFdxdE8=



Dne petek, 22. september 2017 13.55.41 UTC+2 je oseba Andrew Milner 
napisala:
>
> Where are the LOOP and REC packets??  They are not in the file you posted. 
>
>
>
> On Friday, 22 September 2017 14:28:02 UTC+3, Damjan Hajsek wrote:
>
>> Here is a link for values I write both preassure and rain rate and below 
>> data from weewx.
>> When I manually start weewx I get some errors so half is with manually 
>> starting weewx and half when restart weewx.
>>
>>
>> http://zerobin.povej.net/?2b67951062395755#msXGtrC6ARHSBTBUCDj5qdeV920nG2FzZbloR3nozAI=
>>
>>
>>
>> Dne četrtek, 21. september 2017 19.43.59 UTC+2 je oseba mwall napisala:
>>>
>>> On Tuesday, September 19, 2017 at 7:54:35 AM UTC-4, Damjan Hajsek wrote:

 About preassure,  I use absolute preassure which is higher than sea 
 level preassure, my altitude is 293m (I have this setting in weewx.conf). 
 When I checked my absolute preassure it was about 1008mbar until sea level 
 was I think about 995mbar. But I have always set to absoulte preassure and 
 when is absoulte preassure 1010mbar weewx shows 1008 mbar.

 Dne torek, 19. september 2017 13.38.51 UTC+2 je oseba mwall napisala:
>
>
> regarding pressure, are you comparing apples to apples?  is the 
> console reporting gauge pressure or sea level pressure?  what is the 
> station altitude?
>

>>> run weewx directly.
>>>
>>> post the output from a few LOOP packets, not the log output.  for each 
>>> LOOP packet you post, also post the value for pressure that was displayed 
>>> on the console at the time of that LOOP packet.
>>>
>>> m
>>>
>>

-- 
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 https://groups.google.com/d/optout.

Re: [weewx-user] Re: Intermittent dew point data to Wunderground

[Thomas Keffer]

The WU screenshot you posted is for a different time period than the LOOP
packets you showed, but it appears that dewpoint is being emitted often
enough (about once every 30 seconds) for the WU to show a value. Not so
sure about barometer. There are some long gaps without values, so it's
possible there were some 5+ minute gaps during the time period of the
screen shot, which would lead to no value being recorded by the WU.

I've learned through the years that the WU database is just plain
unreliable. It occasionally drops points and there isn't anything you can
do about it except drive yourself crazy trying to figure it out.

It's worth trying without Rapidfire. You may have to choose between using
RF and having consistent dewpoint values.

-tk

On Mon, Sep 25, 2017 at 8:46 AM, Patrick Boyle  wrote:

> I've attached a copy of syslog w/ debug=1, and also a copy of some LOOP
> data. There is also a screenshot from Wunderground showing that temp and
> humidity is there, but no dewpoint. I've also noticed there is no
> barometric pressure when dewpoint is absent.
>
> I do have rapidfire enabled, which I'd like to use if possible.
>
> On Friday, September 22, 2017 at 9:48:05 PM UTC-6, Patrick Boyle wrote:
>>
>>
>> Hello, new weewx user here. Loving it so far. It's working perfecty with
>> one exception. When looking at my station on wunderground I see extremely
>> intermittent dew point data, as in there are hours of time between little
>> blips of data. However, looking at the console I can see a dew point value
>> being reported regularly. How should I go about troubleshooting this?
>>
>> Thanks!
>>
>
> --
> 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 https://groups.google.com/d/optout.
>

-- 
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 https://groups.google.com/d/optout.

[weewx-user] WeeWxIOError: Unable to load driver: Unrecognised memory size

[Andreas Wohlfahrt]

Hello,

I am using WeeWx on Rasperry Pi 3 with a TFA Nexus Station. Installed from 
DEB package on Raspbian Jessie.
Every couple of days WeeWx suddenly cannot read new data anymore and stops 
working (see attached logfile.txt with debug=1).
When I stop and start WeeWx with sudo /etc/init.d/weewx stop and start or 
when I restart the Raspberry Pi, the missed out data gets downloaded from 
the station and everything works fine for the next few days.

I googled the error messages from the logfile but couldn't find any helpful 
solution. Does anybody know what I can do to solve this?
The message "Kein passendes Gerät gefunden" from the logfile can be 
translated as "No suitable device found".
Thank you in advance for your help!

-- 
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 https://groups.google.com/d/optout.
Sep 19 17:26:26 raspberrypi weewx[3241]: te923: read: address 0x020001
Sep 19 17:26:26 raspberrypi weewx[3241]: te923: read: 5a 10 a2 66 28 c1 89 89 
c1 66 0a 00 0a 0a 00 0a 0a 00 0a ff ff ff 3e 05 18 c1 41 00 15 00 ed a7 00 c3
Sep 19 17:26:26 raspberrypi weewx[3241]: te923: read: address 0x4c
Sep 19 17:26:26 raspberrypi weewx[3241]: te923: read: 5a ff ff ff ff ff ff ff 
ff ff ff ff ff ff 54 a7 00 06 53 ff ff 29 19 17 19 ff 3e 01 3f 00 3f 07 3f c5
Sep 19 17:26:36 raspberrypi weewx[3241]: te923: read: address 0x020001
Sep 19 17:26:37 raspberrypi weewx[3241]: te923: Failed attempt 1 of 5 to read 
data: error submitting URB: Kein passendes Gerät gefunden
Sep 19 17:26:37 raspberrypi weewx[3241]: te923: Waiting 3 seconds before retry
Sep 19 17:26:37 raspberrypi kernel: [103090.880775] usb 1-1.5: USB disconnect, 
device number 14
Sep 19 17:26:37 raspberrypi kernel: [103091.178948] usb 1-1.5: new low-speed 
USB device number 15 using dwc_otg
Sep 19 17:26:37 raspberrypi kernel: [103091.316350] usb 1-1.5: New USB device 
found, idVendor=1130, idProduct=6801
Sep 19 17:26:37 raspberrypi kernel: [103091.316365] usb 1-1.5: New USB device 
strings: Mfr=0, Product=1, SerialNumber=0
Sep 19 17:26:37 raspberrypi kernel: [103091.316373] usb 1-1.5: Product:  
Sep 19 17:26:37 raspberrypi kernel: [103091.324758] hid-generic 
0003:1130:6801.000C: hiddev0,hidraw0: USB HID v1.10 Device [ ] on 
usb-3f98.usb-1.5/input0
Sep 19 17:26:37 raspberrypi systemd-udevd[3614]: failed to execute 
'/lib/udev/mtp-probe' 'mtp-probe 
/sys/devices/platform/soc/3f98.usb/usb1/1-1/1-1.5 1 15': No such file or 
directory
Sep 19 17:26:40 raspberrypi weewx[3241]: te923: Failed attempt 2 of 5 to read 
data: error sending control message: Kein passendes Gerät gefunden
Sep 19 17:26:40 raspberrypi weewx[3241]: te923: Waiting 3 seconds before retry
Sep 19 17:26:43 raspberrypi weewx[3241]: te923: Failed attempt 3 of 5 to read 
data: error sending control message: Kein passendes Gerät gefunden
Sep 19 17:26:43 raspberrypi weewx[3241]: te923: Waiting 3 seconds before retry
Sep 19 17:26:46 raspberrypi weewx[3241]: te923: Failed attempt 4 of 5 to read 
data: error sending control message: Kein passendes Gerät gefunden
Sep 19 17:26:46 raspberrypi weewx[3241]: te923: Waiting 3 seconds before retry
Sep 19 17:26:49 raspberrypi weewx[3241]: te923: Failed attempt 5 of 5 to read 
data: error sending control message: Kein passendes Gerät gefunden
Sep 19 17:26:49 raspberrypi weewx[3241]: te923: Waiting 3 seconds before retry
Sep 19 17:26:52 raspberrypi weewx[3241]: engine: Main loop exiting. Shutting 
engine down.
Sep 19 17:26:52 raspberrypi weewx[3241]: engine: Shutting down StdReport thread
Sep 19 17:26:52 raspberrypi weewx[3241]: engine: StdReport thread has been 
terminated
Sep 19 17:26:52 raspberrypi weewx[3241]: te923: release interface failed: could 
not release intf 0: Kein passendes Gerät gefunden
Sep 19 17:26:52 raspberrypi weewx[3241]: engine: Caught WeeWxIOError: Read 
failed after 5 tries
Sep 19 17:26:52 raspberrypi weewx[3241]:   Waiting 60 seconds then 
retrying...
Sep 19 17:27:52 raspberrypi weewx[3241]: engine: retrying...
Sep 19 17:27:52 raspberrypi weewx[3241]: engine: Using configuration file 
/etc/weewx/weewx.conf
Sep 19 17:27:52 raspberrypi weewx[3241]: engine: debug is 1
Sep 19 17:27:52 raspberrypi weewx[3241]: engine: Initializing engine
Sep 19 17:27:52 raspberrypi weewx[3241]: engine: Loading station type TE923 
(weewx.drivers.te923)
Sep 19 17:27:52 raspberrypi weewx[3241]: te923: driver version is 0.24
Sep 19 17:27:52 raspberrypi weewx[3241]: te923: polling interval is 10
Sep 19 17:27:52 raspberrypi weewx[3241]: te923: sensor map is 
{'extraBatteryStatus1': 'bat_2', 'outTemp': 't_1', 'outHumidity': 'h_1', 
'extraHumid4': 'h_5', 'uvBatteryStatus': 'bat_uv', 'extraHumid2': 'h_3', 
'extraHumid3': 'h_4', 'rainLinkStatus': 'link_rain', 'extraHumid1': 'h_2', 
'rainBatteryStatus': 'bat_rain', 'extraTemp2': 't_3', 'extraTemp4': 't_5', 

Re: [weewx-user] Wunderground reporting "missing wind data"

[Andrew Milner]

Just out of curiosity which way does your vane point when there is no 
wind??  If the vane is slightly off balance/true it could well be biased to 
point east under no wind conditions!!



On Monday, 25 September 2017 17:25:51 UTC+3, Erik Berg wrote:

> This works for me, except on my WMR100 it defaults to East when there is 
> no wind.  Is there any way that it could keep reporting the last wind 
> direction?
>
> Erik
>
> On Wednesday, November 16, 2016 at 3:12:43 PM UTC-6, Tom Keffer wrote:
>>
>> It should look something like this when you're done.
>>
>> [StdWXCalculate]
>>
>> ignore_zero_wind = false
>>
>> [[Calculations]]
>> # Derived quantities are calculated by this service. Possible values 
>> are:
>> #  hardware- use the value provided by hardware
>> #  software- use the value calculated by weewx
>> #  prefer_hardware - use value provide by hardware if available,
>> #  otherwise use value calculated by weewx
>> 
>> pressure = prefer_hardware
>> barometer = prefer_hardware
>> altimeter = prefer_hardware
>> windchill = prefer_hardware
>> heatindex = prefer_hardware
>> dewpoint = prefer_hardware
>> inDewpoint = prefer_hardware
>> rainRate = prefer_hardware
>>
>>
>> If that doesn't solve the problem, then we need to see more of the log. 
>> You only included one second's worth. We need at least an archive period 
>> (generally 5 to 10 minutes).
>>
>> -tk
>>
>> On Wed, Nov 16, 2016 at 12:01 PM, Paul Weber  wrote:
>>
>>> Not sure if this is what you want.  I did notice however that my insert 
>>> of "ignore_zero_wind" is at the beginning of the list and not at the end so 
>>> may 
>>> be getting canceled?  Anyway if this is not what you want let me know.  
>>> Thanks for your help.
>>>
>>>
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.
>>> engine.StdTimeSynch
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>>> weewx.engine.StdTimeSynch
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.
>>> engine.StdConvert
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: StdConvert target unit is 
>>> 0x1
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>>> weewx.engine.StdConvert
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.
>>> engine.StdCalibrate
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>>> weewx.engine.StdCalibrate
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.
>>> engine.StdQC
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>>> weewx.engine.StdQC
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
>>> weewx.wxservices.StdWXCalculate
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: wxcalculate: The following values 
>>> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
>>> dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=hardware, 
>>> windrun=prefer_hardware, heatindex=prefer_hardware, 
>>> maxSolarRad=prefer_hardware, humidex=prefer_hardware, 
>>> pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware, 
>>> altimeter=prefer_hardware, cloudbase=prefer_hardware
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: wxcalculate: The following 
>>> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>>> weewx.wxservices.StdWXCalculate
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
>>> weewx.engine.StdArchive
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Archive will use data 
>>> binding wx_binding
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Record generation will be 
>>> attempted in 'hardware'
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Using archive interval of 
>>> 300 seconds (specified in weewx configuration)
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Use LOOP data in hi/low 
>>> calculations: 1
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Using binding 'wx_binding' 
>>> to database 'weewx.sdb'
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: manager: Starting backfill of daily 
>>> summaries
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: manager: Daily summaries up to date
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>>> weewx.engine.StdArchive
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
>>> weewx.restx.StdStationRegistry
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: StationRegistry: Station 
>>> will not be registered: no station_url specified.
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>>> weewx.restx.StdStationRegistry
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
>>> weewx.restx.StdWunderground
>>> Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: Wunderground-PWS: Data for 
>>> 

Re: [weewx-user] Wunderground reporting "missing wind data"

[Erik Berg]

This works for me, except on my WMR100 it defaults to East when there is no 
wind.  Is there any way that it could keep reporting the last wind 
direction?

Erik

On Wednesday, November 16, 2016 at 3:12:43 PM UTC-6, Tom Keffer wrote:
>
> It should look something like this when you're done.
>
> [StdWXCalculate]
>
> ignore_zero_wind = false
>
> [[Calculations]]
> # Derived quantities are calculated by this service. Possible values 
> are:
> #  hardware- use the value provided by hardware
> #  software- use the value calculated by weewx
> #  prefer_hardware - use value provide by hardware if available,
> #  otherwise use value calculated by weewx
> 
> pressure = prefer_hardware
> barometer = prefer_hardware
> altimeter = prefer_hardware
> windchill = prefer_hardware
> heatindex = prefer_hardware
> dewpoint = prefer_hardware
> inDewpoint = prefer_hardware
> rainRate = prefer_hardware
>
>
> If that doesn't solve the problem, then we need to see more of the log. 
> You only included one second's worth. We need at least an archive period 
> (generally 5 to 10 minutes).
>
> -tk
>
> On Wed, Nov 16, 2016 at 12:01 PM, Paul Weber  > wrote:
>
>> Not sure if this is what you want.  I did notice however that my insert 
>> of "ignore_zero_wind" is at the beginning of the list and not at the end so 
>> may 
>> be getting canceled?  Anyway if this is not what you want let me know.  
>> Thanks for your help.
>>
>>
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.engine
>> .StdTimeSynch
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.engine.StdTimeSynch
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.engine
>> .StdConvert
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: StdConvert target unit is 
>> 0x1
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.engine.StdConvert
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.engine
>> .StdCalibrate
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.engine.StdCalibrate
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.engine
>> .StdQC
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.engine.StdQC
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
>> weewx.wxservices.StdWXCalculate
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: wxcalculate: The following values 
>> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
>> dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=hardware, 
>> windrun=prefer_hardware, heatindex=prefer_hardware, 
>> maxSolarRad=prefer_hardware, humidex=prefer_hardware, 
>> pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware, 
>> altimeter=prefer_hardware, cloudbase=prefer_hardware
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: wxcalculate: The following 
>> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.wxservices.StdWXCalculate
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
>> weewx.engine.StdArchive
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Archive will use data 
>> binding wx_binding
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Record generation will be 
>> attempted in 'hardware'
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Using archive interval of 
>> 300 seconds (specified in weewx configuration)
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Use LOOP data in hi/low 
>> calculations: 1
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Using binding 'wx_binding' 
>> to database 'weewx.sdb'
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: manager: Starting backfill of daily 
>> summaries
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: manager: Daily summaries up to date
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.engine.StdArchive
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
>> weewx.restx.StdStationRegistry
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: StationRegistry: Station will 
>> not be registered: no station_url specified.
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.restx.StdStationRegistry
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
>> weewx.restx.StdWunderground
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: Wunderground-PWS: Data for 
>> station ILOGONEO2 will be posted
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.restx.StdWunderground
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
>> weewx.restx.StdPWSweather
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: PWSweather: Posting not 
>> enabled.
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: 

Re: [weewx-user] Re: One shot 'Daily Summaries' using php.

[Devonian]

>
> > In any case, it was an early design decision not to entangle the HTML 
> pages 
> > with database access. It requires colocation of the database and the 
> > webserver, which most people can't do. 
>
 
I think most people can, on their own personal network anyway (LAN) as the 
default weewx install provides a webserver and database for local network 
viewing.
I agree that most don't want to/can't easily make their WX station 
available to the public/internet.

I use nginx on an old R-Pi to reverse proxy incoming internet page requests 
to my internal LAN addresses, e.g.
http://www.nthead.co.uk/weewx/wxobs/index.php

Nigel.

-- 
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 https://groups.google.com/d/optout.

Re: [weewx-user] Wind Gust N/A

[Nicolas Cazan]

I realize that the wind graph is incomplete
very low or no wind.

for the windgustdir which displays N/A this occurs regularly as the wind is 
less than 10 km /h.

As wind gusts exceed 10 km / h no problem for the directions.

[StdWXCalculate]
  ignore_zero_wind = false
 [[Calculations]]

this does not change anything in wind nil, N/A at all wind values.

-- 
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 https://groups.google.com/d/optout.