meteohub.de

I was wondering if I should be getting emails if I receive the following errors:

logger (31.03.2009 23:32:15): Bad wind0 sensor data, "average speed x10" (1140) out of range [0:500]
logger (31.03.2009 23:32:17): Bad wind0 sensor data, "average speed x10" (1140) out of range [0:500]
logger (31.03.2009 23:32:19): Bad wind0 sensor data, "average speed x10" (1140) out of range [0:500]
logger (31.03.2009 23:32:21): Bad wind0 sensor data, "average speed x10" (1140) out of range [0:500]

I do have my settings on meteohub to send me emails for a failed sensor. Does this not constitute a failed sensor? I'm running 4.1.

Thanks!

I get a similar error message occasionally for my th0 humidity sensor ((101) out of range [0:100]) but that doesn't denote a failed sensor, all it denotes is that Meteohub is receiving unanticipated data from your data logger or base station. In my case, I bump my humidity reading up by +3% at the base station because it tends to skew low compared to other nearby stations, especially during rainy weather, so on rare occasions it goes above range.

I would certainly try to figure out why you're getting the error, especially since that's waaaaay outside the accepted range (and it could be a bug in how Meteohub is processing that data for your type of station -- what are the details for your setup?), but since it's still sending data it hasn't failed.

I have a Davis Wireless Weather Envoy for my Vantage Pro2. Once I got those readings I wanted to see if it was Meteohub or not, so I unhooked the Envoy (USB) from my Linksys station and plugged it into my computer. Sure enough, the WeatherLink software was not reading those sensors either. The only sensor it was reading was the Indoor sensor. You think this is a bad Wireless Envoy?

What were the wind readings reported by WL? This sounds like this might be a simple communication problem between the ISS and the Envoy?

I was getting nothing from the wind sensor. I'm thinking too it was a communication problem. My Vantage Pro2 console was getting all the readings though and it is downstairs (wireless as well).

I'm not entirely familiar with the Envoy set up (I have a VP2 console plugged directly into the Meteohub), but at first guess I'd say it's a setup/sync problem with the various pieces of Davis equipment.

Does the Envoy simply serve as an ISS receiver, providing indoor thb0 data as relayed from the VP2 console, or does it have its own temperature gauge along with serving as an ISS receiver? If it's the former, then you probably just don't have it synced properly with the ISS and it should be fairly trivial to fix by following the Envoy manual.

(And have you ever confirmed that the Envoy was properly receiving data from the ISS in the past?)

The envoy grabs data from it's own internal sensor for inside temperature and humidity. I don't know if it can communicate with the VP2 console or not. That might be good to check into. Currently, I just set my weather station outside to broadcast at Station 5. I then tell my Envoy to pick up the IIS signal from Station 5. It's a pretty similar setup as with the Pro2 console.

The Envoy and the console will not cross communicate at all unless you set one of them up to be a repeater device to relay from the ISS. I have a friend who tried that and it was his conclusion that if the two devices are about equally far away from the ISS, then it is best to just try to get both the console and Envoy to receive directly from the ISS. The repeater relay option is more useful when one of the receivers is beyond a reasonable range of the ISS.

Is there any particular reason why you are using TX ID#5? I have a problem with a neighbor jamming my TX ID#1 with his ISS so I have to use another channel. I started with TX ID #5, but I found that the reception seemed to improve the closer the channel ID was to #1, e.g. I had fewer sync drops, misses and CRC errors on the lower numbered channels. So I've settled on TX ID #2.

If you can get the Envoy to sync with the ISS, you can find those reception stats in WL at the Console Diagnostics choice under the Reports item. I think you might have a period of tuning/tweaking your reception with WL (maybe by adjusting the two antennas) and then you should be able to put the Meteohub back on the Envoy.

I find that my console has poorer reception than my Envoy so this isn't a reception problem with Envoys in general.

Very interesting. I set the IIS to Station 5 because there is a neighbor with a station about 400 feet from me. Do you think I should just set it back to Station 1 since he is probably too far away?

During set up tests inside my house, I couldn't get my console to receive my ISS located a few feet away on TX ID #1, but it would pick up my neighbor over a 1000 feet away. That is when I chose #5. Then occasional sync drops caused me to start experimenting with lower ID #s.

I think you should try ID #2 and also try changing the 123 lithium battery in the ISS in case it is weak. There shouldn't be any interference on #2 from your neighbor's #1 radio transmissions.

I found another house today with a Vantage Pro2! I think that house is more than 1000 feet away though.

This weekend I'll definitely change my station's id to #2.

I'll let you know how it goes.