To clarify, it looks like the display console screen is called "Observer", and the black box antenna based unit is called ObserverIP. I would recommend not scraping the ObserverIP. Not all Ambient stations use the Observer, nor the ObserverIP.
Picture of the ObserverIP. This is the unit I'm using socketlogger with: http://ep.yimg.com/ay/yhst-37697109791737/ambient-weather-ws-1400-ip-observer-solar-powered-wireless-ip-weather-station-with-internet-publishing-12.gif Pat On Monday, January 30, 2017 at 9:56:05 AM UTC-5, Pat O'Brien wrote: > > Hey Matthew, your GitHub link 404s. Do you have an updated link for it? > > My model, the 1400, does not use the console (by console I'm assuming you > mean the screen?) to upload data. My only way to intercept the data is > either by screen scraping, or redirection. As mentioned, screen scraping > the Observer is not ideal and caused more problems than it's worth. Using > the redirection has been working great, not only for weewx, but other > archival methods since the data is freely available on the socket. > > In any case, I strongly recommend you do not advertise the scraping > method. It is known to cause issues with the ObserverIP unit. The > ObserverIP (black box with antenna on it) is an inexpensive unit that can > barely survive an uptime of 30 days, let alone screen scraping every 15 > seconds. > > Understood on the ease of use. My method is not necessarily easy, however > my blog posts outlines step by step on how to get started (across 2 > different methods) which have helped a few other users. Again, I wasn't > going to consider submission, but was nudged to do so today. > > Pat > > > On Monday, January 30, 2017 at 9:34:56 AM UTC-5, mwall wrote: >> >> pat, >> >> please take a look at this weewx wiki page: >> >> https://github.com/weewx/weewx/wiki/observer >> >> the interceptor approach is pretty much the only option for the fine >> offset bridges, but there is a direct-connect approach for the fine offset >> wifi consoles that requires zero configuration (no scraping or capture or >> php or listen or sniff is necessary). i started a driver for this approach >> (https://github.com/matthewwall/observer), but susan actually has a >> working implementation: >> >> https://groups.google.com/forum/#!topic/weewx-development/rzLBh9g-pIU >> >> its nice that there are a lot of options for getting data from this >> hardware, but it would be nice to consolidate into a driver that we can >> include in the weewx distribution. >> >> given the popularity of the fine offset stations, and since >> direct-connect requires zero configuration, i think it is a no-brainer to >> put a direct-connect driver in weewx. >> >> however, including a driver that uses the interception approach is not so >> obvious - either sniff or listen requires not-insignificant >> network/hardware/software configuration. >> >> tom can provide some guidelines about what should or should not be part >> of the weewx distribution... >> >> m >> >
