I had an ObserverIP and it was a nightmare to keep it up while the Meteobridge got data from it, which it needs to do constantly. It was so bad that I got a second ObserverIP thinking maybe I had a defective one. No matter what I did the ObserverIP would need to be constantly rebooted sometimes daily and sometimes it would last a week. I finally got crafty and I devised a way to automatically restart the ObserverIP whenever the Meteobridge lost data. To do this the Meteobridge would send out an email alert upon data loss, which then caused my email account incoming rules to send out a text message to my phone and then that text message would trigger IFTTT which would activate an action on SmartThings to turn off the ObserverIP and then turn it back on. Convoluted but it worked perfectly every time. The reason to have the email converted to a text was to speed up IFTTT response because otherwise it would be slow to respond to an email. With this automated routine I could forget about the unreliability of the ObserverIP. Well almost forget because I would see the text messages and it just bothered me how frequent they were sometimes.
Some people claim no problems with the ObserverIP and a Meteobridge. Maybe they are running older versions of Meteobridge. Or maybe their Meteobridge was on Ethernet (mine was on WiFi). I tested every version of the ObserverIP firmware and the problem never went away. I got excited every time the ObserverIP got newer firmware, but no nothing. I ran both ObserverIP devices simultaneously. Whichever one was just working alone and not providing data to the Meteobridge ran flawlessly. So it was definitely caused by the Meteobridge taxing the ObserverIP resources to provide it data via its Live Data page that would get scraped. The ObserverIP has a very low end processor and was just not built for such constant hammering of letting the Live Data page be scraped for data. One day I learned things got better if I set a static IP on the ObserverIP. Not a static reservation on the router, but actually entering in a static IP into the ObserverIP settings. It still didn't fully make the problem go away.
But all that is in the past. The solution is to buy an Ecowitt GW1000 and use that to feed the Meteobridge. The GW1000 is $30 on Amazon so there is absolutely no excuse for not having one. There is just no reason to put up with the ObserverIP nonsense. I don't know how much the Ecowitt GW1000 is to order directly from Ecowitt and to ship elsewhere in the world but it can't be much more.
Besides the great reliability of the GW1000 there is more to gain. You get to use a proper network API which the Meteobridge supports. You get to read in extra sensors. You get quicker sensor updates. The GW1000 uses WiFi unlike the ObserverIP which requires Ethernet. The GW1000 has a nice Live Data feature with WS View app. The GW1000 is newer and more powerful. The GW1000 will work for any frequency you order 433, 868, or 915 MHz. The GW1000 will see all your other sensors no matter the reseller branding from Fine Offset. The GW1000 gets power from USB and can conveniently plug into the Meteobridge. The GW1000 is easy to setup and use with the VS View app. Pretty soon the GW1000 will be able to send data to even more weather software simultaneously.
I don't miss my two ObserverIP devices... Good riddance!
TL;DRBuy an Ecowitt GW1000 and forget the ObserverIP if you own a Meteobridge. Yeah there are many ways to open a can of tuna, but having the can opener is not only the best way, it's the only sane way. The GW1000 is the can opener. The ObserverIP is a dull jagged rock.
https://www.wxforum.net/index.php?topic=36772.0
