--Hello,A while ago I did some changes to Pat O'Brian's version of Tom Keffer's ObserverIP plugin. It works by "scraping" the data from the ObserverIP's public web page.This technique has been considered flaky, but I found a simple fix for the hangups and crashes: every 24 hours the driver reboots the ObserverIP.The driver has been working flawlessly for me for almost a year.I have attached the .py file, and you can also get it from here: http://dougbraun.com/software/observerip_scraper_py.txtDoug
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/8a077335-3f0c-4ac8-a6e4-7521635691af%40googlegroups.com.
Credit goes 100% to Pat O'Brian. I don't know why he put my name on the driver!-tk
On Sun, Nov 24, 2019 at 8:57 AM Doug Braun <do...@dougbraun.com> wrote:
--Hello,A while ago I did some changes to Pat O'Brian's version of Tom Keffer's ObserverIP plugin. It works by "scraping" the data from the ObserverIP's public web page.This technique has been considered flaky, but I found a simple fix for the hangups and crashes: every 24 hours the driver reboots the ObserverIP.The driver has been working flawlessly for me for almost a year.I have attached the .py file, and you can also get it from here: http://dougbraun.com/software/observerip_scraper_py.txtDoug
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx...@googlegroups.com.
After much troubleshooting , it seems that the problem actually related to ObserverIP itself. The following is an excerpt from ObserverIP firmware page (old version):
Some users have reported conditions where their ObserverIP has become totally, or partially unresponsive (or very slow) to requests for web pages by either a browser, or secondary device (such as WeatherBridge or MeteoBridge, or computer running software that “interrogates” the ObserverIP web pages). In all cases the problem would occur somewhat unpredictably, and was seen as frequent as once a week, but most often less frequently. The problem manifests as web page timeouts, seen by a browser user or by a secondary device or software. Sometimes the problem is transient, sometimes it is (semi) permanent. To recover, the only solution is a “cold restart” which can be affected by removing power from the ObserverIP for 5 seconds, or by pressing the reset button located on the rear of the ObserverIP.
This was said to be solved, but apparently (and as posted in other forums), that actually NOT. Upon On/Off of ObserverIP, things seems get back "normal" till ObserverIP gets "overwhelm" once again... and another On/Off.