meteohub.de

I have a Ambient Weather WS-1400-IS which sends data to its Observer-IP box hooked to my router. The Observer-IP sends data directly to Weather Underground which has been flawless for the last 7 days since I set it up. I also created a Meteobridge using a TL-MR3020 and configured it for wireless operation to my home network. It sees my Observer-IP box and I have it set to repeat the data to PWSWeather.com and CWOP. A few days ago and again today it began sending absurdly high temp and dew point values in the 140-160 range because it is taking Observer-IP values that are Fahrenheit and interpreting them as Celsius. Once it begins doing this randomly it will do it for 80% or so of the data points it sends. A reboot of the Meteobridge will fix it but the problem randomly returns at a later point.

So here are the hard facts...

Observer-IP box is on version 3.0.5
Observer-IP box is set to Fahrenheit for all temps.
Observer-IP box always shows correct values for temp even when problem is occurring on the Meteobridge.
Observer-IP box always sends correct data to Weather Underground.

Meteobridge is using a TP-LINK TP-MR3020
Meteobridge is running 2.8 build 9883, FW 1.4
Meteobridge has a 0 temp offset setting, however I do have the offset box set to Fahrenheit (problem also occurred when it was set to default of Celsius)
Meteobridge when the error occurs shows ALL temps (indoor, outdoor, dew point) by taking the F temps from the Observer-IP and showing them as C, leading to very high reported F temps.
Meteobridge reboot will fix the error but it will return randomly (sometimes a day or two, in some cases minutes later).
Meteobridge is sending these error values to PWSWeather and CWOP which is causing a major issue for temp accuracy on these sites which are used by my internet enabled Rachio Iro irrigation controller.

Any idea what is going on?

Here is PWSWeather.com and you can see it happen in the 5/10 data... http://www.pwsweather.com/obs/KILPLAIN41.html

Data at Weather Underground for my station KILPLAIN41 at the same time is perfect.

Also the problem is only temperature, all other data points of rain, wind etc. are correct.

***finally as one last point... it seems that when i would reboot the meteobridge the problem would go away but return in a short period of time. i have now rebooted the observer-ip and the problem has gone away for a much longer period of time. i believe i rebooted both boxes last time this occured which was a few days ago so i am certain it will eventually return. perhaps rebooting the observer-ip helped in someway but again at no time did the observer-ip show the wrong data in its live feed on its own dashboard nor did it send incorrect data to weather underground. i am not sure where the issue lies.***

thanks!

Meteobridge just reads out observer IPs web interface and grabs data from there.
So no true magic applied. Did you check the Observer IP web interface when
Meteobridge reports silly temperature numbers?
Is it just one isolated false reading or does it continue to read false data?
Is it on specific temperatures (going beyond 100 °F or something like this?

The observer-ip web interface reads correctly when the meteobridge reads incorrect on its live data web interface. The problem reoccurs daily over and over and isn't just one particular temperature. What is clearly happening is the meteobridge is misreading the the observer-ip interface temps as if they are Celsius when they are actually Fahrenheit. So suddenly I will go from 70.7F to 70.7C. This happens again and again. Rebooting either the meteobridge or the observer-ip will fix it for anywhere from 1 to 24 hours then it begins again. Once it starts happening at least 80% of the 5 minute snapshots I have the meteobridge setup for will show the problem. The observer-ip again never shows the problem in its web interface and all data it sends directly to WU is correct.

I am at a total loss.

well i can't imagine that this is the problem but just in case... i had the meteobridge plugged into a usb hub just for power. i realized the hub was no longer plugged into its electrical plug and was relying on power from the Apple iMac it is plugged into. while i have never seen the meteobridge unpowered sometimes after these problems would begin (temp being read as C instead of F from observer-ip, sometimes the meteobridge would then totally stop reporting ANY data.) i don't know if perhaps it was a power issue as the computer went to sleep etc. i rebooted BOTH the observer-ip and meteobridge for the millionth time last night but this time i have the meteobridge plugged directly into the USB power plug it came with (no hub) and 18 hours later all data is flowing well. I can't imagine how a power issue would cause the misreading of temp data (although I could see it causing the data to stop being delivered) but so far so good.

I believe everything is working now, and frankly I can't believe what the solution was. I am posting here in the odd event someone else had the same issue... if the problem crops up again I will post but so far I am over 48 hours with perfect posting of data by the meteobridge. Here goes...

My meteobridge was powered obviously by the USB cord, but I had plugged that USB cord into a USB hub, not its wall plug for power. It appears my USB hub which is plugged into my iMac and gets supplemental power from an AC adapter had gotten unplugged from that AC adapter. This resulted in my iMac solely powering the hub. It appears it was enough power to boot the meteobridge and make everything work fine but when my iMac would go to sleep after some amount of hours there must have been power issues to the meteobridge that resulted in somehow (don't ask me how it seems insane) not parsing the data from the observer-ip correctly and occasionally not sending the observer-ip data at all. Of course when I went to "check" on why it wasn't working properly I used that iMac which restored more power to the meteobridge (although it continued to show incorrect live data until both it and the observer-ip were rebooted.) This was reproducible for over a week and the meteobridge would always start messing up within hours of me "leaving it alone" because I assume it had power supply issues.

Well, what I did was simply unplug the meteobridge from the hub and plug it into the wall plug that came with the unit and directly into a socket (I had been trying to save a socket location since I had plenty of slots left in the hub) and bam... no problems ever again, everything working like clock work. While it has only been 48 hours, I never could get more than 12-18 hours out of the meteobridge correctly when it was powered by the iMac powered hub so I think this has been the fix.

Summary: plugging your meteobridge into a hub for power may create enough to make it appear to be functional but result in sporadic problems that are hard to diagnose. Be sure your meteobridge has a sufficient supply of power.
Modify message