after upgrade to weewx 3.6.1 not outdoor sensor data displayed (WMR200)

[Ivars Strazdins]

Hi there,

after upgrading from 3.5.0 to 3.6.1 and sorting out the mess with extra sensors (had to rename extra*2 to extra*1 and extra*3 to extra*2, then update DB data, too) I see that outdoor sensor data sometimes is not displayed on webpage.

WMR200 displays outdoor data in console and there are no errors in weewx log, but the data is often missing in wewx web page (http://gimnasti.selfip.org).

Of course, it can be the famous case with car and ice cream (https://goo.gl/73Ta) and some other factor has come into play that I have no idea about, yet maybe you have seen something similar?

Appreciate any insights. Thank you in adcance!

Ivars

[Andrew Milner]

What is your archive interval??  As I understand the wmr200 it emits partial packets, so if your archive interval is too small it is very likely that no reading for a sensor was received during the archive period.  Are you using a different interval now to what you used to use - did you change the interval while you were trying to get the sensors to read perhaps?? 

Try with an archive interval of 300 seconds and see if it is any better

If that fails, stop weewx, set debug = 1, restart and post the log FROM THE RESTART UP TO AT LEAST THE SECOND REPORT GENERATION SEQUENCE

[mwall]

On Sunday, October 23, 2016 at 5:07:36 AM UTC-4, Ivars Strazdins wrote:

Hi there,

after upgrading from 3.5.0 to 3.6.1 and sorting out the mess with extra sensors (had to rename extra*2 to extra*1 and extra*3 to extra*2, then update DB data, too) I see that outdoor sensor data sometimes is not displayed on webpage.

WMR200 displays outdoor data in console and there are no errors in weewx log, but the data is often missing in wewx web page (http://gimnasti.selfip.org).

ivars,

try running weewx directly.  that will tell you exactly what weewx is getting from the sensors and how it maps to the database fields.

run weewx for at least one archive interval, preferably two or three (you will see a REC at each archive interval)

m

[Ivars Strazdiņš]

Thank you all for suggestions and sorry for my late reply.

I have set archive_interval to 300 (was set to 120), but that did not improve anything.

Running weewx directly is confusing, because it not all sensor data is shown every time.

Anyway, it’s looks certain that weewx upgrade has not caused my woes. Actually, I was able to trace back "Temp outdoor sensor fault” message occurring regularly, just not for such large and noticeable periods of time.

But now I am getting a lot of failues, like today I had the message “weewx[7384]: wmr200: MainThread: W Temp outdoor sensor fault” logged 600 times. And I did replace batteries, too.

The only reason I can think of is unfortunate station location so that it is unable to receive outdoor sensor data.

Thanks and regards,

Ivars

--
You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/NH0d3G5lS90/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[bjs...@gmail.com]

Where can I find the information on the extra sensor changes?  I just upgraded to 3.6.2 using the WMR200 and my extra sensors are out of sequence.

[Thomas Keffer]

I don't know what you mean by "sensor changes."

On the WMR200:

sensor ID 1 is mapped to outTemp and outHumidity. 

sensor ID 2 is mapped to extraTemp1 and extraHumid1.

sensor ID 3 is mapped to extraTemp2 and extraHumid2.

etc.

Is that what you're looking for? Not sure if that answers your question...

-tk

--
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+unsubscribe@googlegroups.com.