On Thursday, March 7, 2019 at 7:48:08 PM UTC-5, John S wrote: > > I have weewx working on my Ubuntu 18 box with Apache2. I did a deb install > and sorted through the docs to get it running in intercept mode, using GAS > to send the GW1000U data to this machine via proxy. > I'm stumped how to get the data redirected to the Lacrosse site. I am an > apache2 novice. Lacrosse says it hasn't seen my machine since I did the > redirect via the proxy. I would prefer to have a fully functioning weewx > system vs one that isn't. >
the protocol used by the GW1000U is rather complicated, so it is not possible to have the GW1000U talk to both the lacrosse servers AND the weewx-interceptor driver. it should be possible to add a 'sniff' option to the weewx-interceptor so that the interceptor passively watches the traffic between the GW1000U and the lacrosse servers. this behavior was implemented for the wu and ambient protocols, but i never got around to doing it for the GW1000U protocol. unlike the wu and ambient protocols, you cannot just do reverse proxy and url rewrites - the GW1000U protocol requires some specific back-and-forth between the device and the server. (since i do not have the lacrosse hardware, and since lacrosse provides zero information about their devices or protocols, it was, shall we say, a challenge to get *anything* to work) if you want to experiment a bit, i could help you write the packet-sniffing implementation. the first step is to capture the packets, and the second step is to parse/decode them. we already know how to do both of those steps. m -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
