Okay :) So, then both options should work :) - HP25xx console + Interceptor - or GWxx00 console + gw1000 driver
I guess I'll experiment more closely when I receive the weather station :) Thanks very much! On Friday, August 26, 2022 at 9:30:45 AM UTC+2 lang....@googlemail.com wrote: > the Ecowitt Gateway driver works on a pull procedure, i.e. requests the > data from the GWyx00 console, whereas the interceptor driver works with > data pushed by the console via the custom server functionality. > In both cases the consoles communicate via WiFi/WLAN into the local > network, and weewx requests/pulls (GW1000 API) or catches (interceptor) > via the network. (in case of a GW2000 this can be completely LAN based > without WLAN). > For the Ecowitt Gateway driver the IP of the console is entered into > weewx.conf [GW1000] > for the interceptor driver the IP of the weewx server is entered into the > console for the custom server. > > the interceptor doesn't need to be "placed" somewhere - that's a strange > wording imho. It's just installed with weewx. > If you want to see a picture how this works - and get also some more > understanding of your EW console hardware, > read through https://www.wxforum.net/index.php?topic=40730.0 (chapter 7. > data flow, but all chapters are worth reading) > > On 26.08.2022 09:12, Invisible Man wrote: > > From the GW-1000 weewx driver README.md, I read: > "*The Ecowitt Gateway driver utilises the Ecowitt LAN/Wi-Fi Gateway API > thus using a pull methodology for obtaining data from the gateway device > rather than the push methodology used by other drivers*". > > So, if I understand correctly, the GWyx00 does not talk to the Weewx.* > It's the other way round: the Weewx communicates with the GWyx00 gateway*. > I suppose we configure in the weewx driver the IP address of the GWxy00 and > it questions it to get weather data. > > Later the README.md says: > "*Note: If necessary you can specify the device IP address and port using > the --ip-address and --port command line options.*" > > Not sure whether this is the IP address of the GWyx00 console, or the IP > address of the Weewx host. The former, I think. > > If so, that answers the second question of my previous post :) > > On Friday, August 26, 2022 at 8:49:20 AM UTC+2 Invisible Man wrote: > >> Woaw, thanks this is extremely helpful! >> >> The *interceptor* driver ( >> https://github.com/matthewwall/weewx-interceptor) looks cool. Except >> that *I suppose the interceptor needs to be placed where it can read all >> wifi packets* (from the wifi the weather station uses), right? >> That's not very convenient in my case because the WiFi is created by the >> Internet box. The Internet box is from my ISP. I don't have any control on >> it, *can't install a weewx driver on it* for instance ;-) >> Or can the interceptor be placed on *any machine on the same wifi as the >> weather station* ? >> >> So, let's investigate the option where I get a *GWyx00* console: >> >> >The communiation from HP25x0 and GWyx00 console goes via WiFi into the >> local LAN. >> >> Ok, so you said that the USB connector on the GWyx00 console was for >> power only. Then, the data from GWyx00 is emitted on WiFi. >> My weewx host (a Rapsberry Pi) is on the LAN. They can ping each other >> and communicate if they wish, no problem. >> But will the GWyx00 directly send data to the weewx host: is that >> configurable? *Can I configure the GWxy00 console to communicate with a >> given IP address?* I fear that the GWyx00 console will rather directly >> send its data to an external Internet weather server. Then, same issue, my >> weewx host can't "intercept" the data. >> >> Thanks very much for your help! >> On Thursday, August 25, 2022 at 7:10:33 PM UTC+2 lang....@googlemail.com >> wrote: >> >>> The HP25x0 consoles do not have an API and cannot be queried via the >>> GW1000 API/Ecowitt Gateway driver. >>> You either use a GW1x00/GW2000 instead (receive the same sensors in >>> parallel) with the Ecowtt Gateway (GW1000) driver, >>> or you will have to use the weewx Interceptor driver with the HP25x0 >>> console custom server functionality >>> The interceptor driver as available on GitHub from M. Wall covers only >>> the basic sensors (T/H indoor, outdoor, rain, wind, solar). >>> If you have more sensors, you need to use a modified interceptor driver. >>> Some users here have developed an extended version which covers all recent >>> Ecowitt sensors. >>> >>> The communiation from HP25x0 and GWyx00 console goes via WiFi into the >>> local LAN. >>> Weewx will pick up the data via local LAN (LAN or WLAN) depending on the >>> server on which weewx runs and its network interfaces. >>> >>> There is no USB connection between consoles and weewx >>> The USB port on the GW1x00 consoles/gateways is for power supply only. >>> The USB port of the HP25x0 consoles is for factory use initial device >>> firmware only. >>> >>> On 25.08.2022 19:00, ewhain...@gmail.com wrote: >>> >>> The IS a USB port on the drawing. I found the manual here: >>> https://www.ecowitt.com/shop/goodsDetail/1# >>> >>> Manual & Software tab, Page 7 in the manual, however it also states it >>> is for firmware updates only... >>> >>> On Thursday, August 25, 2022 at 9:55:10 AM UTC-4 axelle....@gmail.com >>> wrote: >>> >>>> >The GW1100 is included with a number of display-less stations. As I >>>> >understand it, there's a local API and the driver is just talking to >>>> >that API and injecting to weewx. >>>> >>>> Right. And the GW1100 is plugged by USB to the weewx server, right? or >>>> can weewx read GW1100 over wifi? >>>> >>>> >it looks like there is the equivalent of the GW1100 inside the >>>> console, >>>> >because it says it uploads to similar places >>>> >>>> I have the feeling the protocol will be the same too. Same reason as >>>> you. >>>> >>>> The main issue that might occur is whether weewx GW1000 driver is able >>>> to operate via wifi too or not? Looks like the HP2551 console does not >>>> have >>>> a USB port (not sure though, couldn't find a photo). And I wasn't able to >>>> find any info on Wifi connection on >>>> https://github.com/gjr80/weewx-gw1000 nor about support for HP2551 or >>>> HP2552 or HP2553. >>>> >>>> Anybody from GW1000 driver can answer? >>>> >>>> Thanks, >>>> On Thursday, August 25, 2022 at 12:38:46 PM UTC+2 Greg Troxel wrote: >>>> >>>>> >>>>> Invisible Man <axelle....@gmail.com> writes: >>>>> >>>>> > I'm considering the purchase of a EcoWitt HP2551 : it has a console >>>>> + a >>>>> > 7-in-1 sensor. Just not totally sure how to integrate it with Weewx. >>>>> > People said here to use the Ecowitt GW-1100 driver, right? But >>>>> EcoWitt >>>>> > HP2551 does not have that GW1100 gateway. Will the driver work >>>>> > nevertheless? >>>>> > Basically, I'm not sure the EcoWitt HP2551 (or 2552, or 2553) has a >>>>> USB >>>>> > cable. So how would I connect it to the RPi on which Weewx runs? >>>>> >>>>> I am unclear on details but am heading down the path of figuring out >>>>> which EcoWitt station someone else should get. I lean to EcoWitt >>>>> because it seems to be reasonable quality at very low prices and they >>>>> seem to be open-source and local-access no-cloud-required friendly. So >>>>> many things are cloud-only which I consider a total fail -- the >>>>> interceptor driver is an impressive hack but it's a bad situation that >>>>> it's necesary. >>>>> >>>>> The GW1100 is included with a number of display-less stations. As I >>>>> understand it, there's a local API and the driver is just talking to >>>>> that API and injecting to weewx. Thus it should work if the internet >>>>> is >>>>> down (or if the GW1100 is firewalled to keep the data from being sent >>>>> to >>>>> their cloud), but I'm not 100% sure as sometimes devices have code >>>>> that >>>>> phones home and stops if that doesn't work. >>>>> >>>>> Reading >>>>> >>>>> https://shop.ecowitt.com/products/hp2551 >>>>> >>>>> it looks like there is the equivalent of the GW1100 inside the >>>>> console, >>>>> because it says it uploads to similar places, and there is a list of >>>>> optional sensors that seems to match. It would be sane to offer the >>>>> same API and for them to reuse their code and circuit design, just >>>>> sharing the case/etc. -- and doing so would be consistent with my >>>>> impression of EcoWitt's approach. >>>>> >>>>> However, skimming the driver github site I don't see direct >>>>> confirmation >>>>> that the HP2551 is wire-protocol compatible. With any luck someone >>>>> will >>>>> post that they've used the driver. >>>>> >>>>> -- >>> 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/f99be245-5334-4b28-bb66-7229fdee4569n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/weewx-user/f99be245-5334-4b28-bb66-7229fdee4569n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> >>> -- > 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/ddd1cab4-6ced-41d1-8ae7-cae76007bf1cn%40googlegroups.com > > <https://groups.google.com/d/msgid/weewx-user/ddd1cab4-6ced-41d1-8ae7-cae76007bf1cn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/04eb8bc0-dbd8-4d0e-b0e7-d936c05db158n%40googlegroups.com.
