Data Upload to Weatherbug Error

[wrj0]

Greetings,

I have completed installation of Meteohub on a SheevaPlug and most everything seems to be working fine, except for frequent errors uploading data to Weatherbug. Meteohub is set to send data to Weatherbug every 5 minutes, or 12 times per hour. When it works, Weatherbug data properly appears on their web site for my station. While Meteohub ran overnight, I received the following email error 5 or 6 times (out of 12) every hour:

subject: Meteohub (meteoplug): Cannot connect to Weather Network "No data upload to weather networks as sensor selected on weather network page for outdoor temp, outdoor humidity or outdoor dewpoint is not providing recent data."

The Davis Vantage Pro2 (6163 wireless) has a serial data logger with a serial-USB converter to connect to the PC or to the SheevaPlug. Sensor signal strength to the Vantage console is strong, and no sensor data errors are reported by the console. Data from the Davis Vantage Pro 2 seems to be OK when connected to the USB port of a PC running Weatherlink, but when connected to the SheevaPlug, these errors appear. Moving the location of the Vantage console or the Sheevaplug does not seem to make any difference.

Meteohub Time synchronizes properly, and I was able to upgrade from 4.7 to 4.7b, 4.7c, & 4.7d using the internet connection without difficulty, so it appears the internet connection is solid.

Tomorrow, I will plan to buy a snap-on ferrite for the USB cable, as other in this forum have suggested.

Is there anything else I may try?

Thanks.
-Bill

[wrj0]

Problem solved! I found that the value for Weather Station, “Hold time for live data,” was set for 30 seconds. The Meteohub manual says, “Standard value is 300 seconds.” When set to 300 seconds, the email problems ceased and Weatherbug gets updated properly. Apparently, sensor data was occasionally not ready when it was time for data to be sent to Weatherbug, which caused the error reported. For the past three hours no errors have occurred with the hold time sent to 300. I am not sure at what point during the setup process that the value got set to 30s, but thanks to the great documentation in the manual the problem has been corrected. Thanks.