Loss of WGR800 Sensors

[KVAALEXA30]

I'm currently running 4.9u

Some months back I lost contact with my WGR800 sensor - possibly coincident with battery failure. Looking back, this might have also been coincident with a software upgrade.

I ordered a new WGR800 and was not able to see data from the new or the old sensor.

I thought the problem might have been with my RFXCOM receiver, but other sensors worked just fine. After checking again recently, I found that the RFXCOM receiver is receiving data from both the new and old WGR800 wind sensors, but these are not showing up in Meteohub.

Further, the Meteohub log is chock-full of these entries:

logger (14.06.2013 00:12:01): Bad wind1739043(1a8923) sensor data, "chill x10" (-999) out of range [-700:1500]
logger (14.06.2013 00:12:18): Bad wind1739097(1a8959) sensor data, "chill x10" (-999) out of range [-700:1500]

I believe this shows reception from both of the wind sensors, but suggests that conversion from raw data to actual metrics has somehow failed.

Has anyone else seen this?

How might I be able to regain functionality? Is there something I need to reset?

No WGR800 wind sensors appear in my "sensors" page, though the other 6 temp and humidity sensors I have are operating normally.

Best,

...Mike

[gcams]

I reported this issue back at the start of the year here:

viewtopic.php?f=4&t=9138&p=12910&hilit= ... ill#p12910

But I didn't get any replies. I have found that if I restart data logging (sometimes takes 2 or 3 goes) the issue eventually clears, although it's obviously an less than ideal/reliable solution!!

Would be good to hear Boris's view on this issue.

[KVAALEXA30]

I'll try restarting the data logging, but I wonder if this will work since I don't even see even one of my WGR800 sensors on the sensor page.

Are you saying that in your experience the sensor did not appear, but after restarting the data logging the sensor re-appeared?

That would be an acceptable short term solution if I could get re-starts to make the issue go away.

I'm trying it now. Thanks for the response.

Anyone else out there see something like this? Boris?

Best,

...Mike

[KVAALEXA30]

So far, restarting data logging has had no effect.

Boris or anyone - are there any suggestions on how to recover from this?

Best,

...Mike

[KVAALEXA30]

Boris,

If I hear back from Boris or someone else here I will update this.

Sadly,

...Mike

[KVAALEXA30]

The meteohub is now recognizing *both* of my wind WGR800 wind sensors (old one and the new one purchased as an attempt to troubleshoot this issue).

Resetting all settings, then reverting to v4.8i immediately resolved the issue.

In my opinion, this is definitely a bug in some version of v4.9. I don't have time to progressively roll the versions forward from v4.8i.

If anyone else has more information, please feel free to share.


...Mike

[admin]

When 4.8i works fine for you, then please stick with it for the moment. I do try to remove bugs, but this one has a work-around and does only affect an extremely small user base. Please understand that I do support on best effort base, only.

Can you provide me login on ports 22 and 7777 on your Meteohub? I will need some on station tests to understand what the issue is.

[KVAALEXA30]

Boris,

Thank you for this. Good to hear from you.

I also received your e-mail and I've replied with the information needed to connect to the system.

...Mike

[admin]

I could login and check. Reason for wind sensor data not being presented is that temp sensor
specified on "weather station" page to be used for windchill computation is defined as "th0"...

1.png (13.46 KiB) Viewed 6396 times

...but there is no "th0" sensor defined. When changed to "th1" wind sensor data does come up again.

2.png (10.84 KiB) Viewed 6396 times

It is not very obvious, but root cause was exactly that.

[KVAALEXA30]

Boris,

Awesome job of tracking this one down - definitely not obvious and I wouldn't have been able to find this without your help.

Thanks also for upgrading to the latest version.

Definitely a satisfied user here - thank you again.

Best,

...Mike