I wanted to provide a status update, and see if anybody else has any experience with the WiFiLogger that's similar to this, or has any ideas.
Ryan, I'm having problems with the WiFiLogger2. I'm reading it with weeWx. There is no email address on wifilogger.net, so I don't know how to reach out the the developer directly. It took a while to get the parameters on the WFL right, but I got it working, mostly. However, I still get lots of errors. Here is the weeWx error log for the last few hours: Sep 25 05:17:56 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: ip-read error: [Errno 104] Connection reset by peer Sep 25 05:17:56 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: LOOP try #1; error: [Errno 104] Connection reset by peer Sep 25 05:17:56 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: LOOP try #2; error: Expected 99 characters; got zero instead Sep 25 05:17:56 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: LOOP try #3; error: Expected 99 characters; got zero instead Sep 25 05:17:56 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: LOOP try #4; error: Expected 99 characters; got zero instead Sep 25 05:17:56 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: LOOP max tries (4) exceeded. Sep 25 05:17:56 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe Sep 25 05:17:56 ubu-mini-weather weewx[198474] CRITICAL __main__: Caught WeeWxIOError: Max tries exceeded while getting LOOP data. Sep 25 08:05:40 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: ip-read error: [Errno 104] Connection reset by peer Sep 25 08:05:40 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: LOOP try #1; error: [Errno 104] Connection reset by peer Sep 25 08:05:40 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: LOOP try #2; error: Expected 99 characters; got zero instead Sep 25 08:05:40 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: LOOP try #3; error: Expected 99 characters; got zero instead Sep 25 08:05:40 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: LOOP try #4; error: Expected 99 characters; got zero instead Sep 25 08:05:40 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: LOOP max tries (4) exceeded. Sep 25 08:05:40 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe Sep 25 08:05:40 ubu-mini-weather weewx[198474] CRITICAL __main__: Caught WeeWxIOError: Max tries exceeded while getting LOOP data. Sep 25 08:06:50 ubu-mini-weather weewx[198474] INFO weewx.engine: Clock error is 0.97 seconds (positive is fast) Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: ip-read error: [Errno 104] Connection reset by peer Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: LOOP try #1; error: [Errno 104] Connection reset by peer Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: LOOP try #2; error: Expected 99 characters; got zero instead Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: LOOP try #3; error: Expected 99 characters; got zero instead Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: LOOP try #4; error: Expected 99 characters; got zero instead Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: LOOP max tries (4) exceeded. Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe Sep 25 10:53:24 ubu-mini-weather weewx[198474] CRITICAL __main__: Caught WeeWxIOError: Max tries exceeded while getting LOOP data. I'm not sure how often weewx tries these loop reads. Archive interval is 10 minutes (both on weewx.conf and in hardware) but these loop reads don't seem to be synced with that. It only fails once every 2-3 hours, but of course it shouldn't fail at all. I lengthened the timeouts in the weeWx config, as much as seems reasonable. tcp_send_delay is now 1. It was 0.5, and I was getting a lot more ip-write errors, but I still got one error even with the longer delay. I was getting a lot more ip-write errors until I did that, though you can see that I still got one of those this morning. Vantage Timeout is now 10 seconds (it defaulted to 6) but I'm not sure that had any effect. I've set the parameters on the WFL very conservatively. The console archive interval is 10 minutes, all data exports are disabled (both individually and the "upload data" on the System setup screen), TCP port == Pause, Sleep Mode == Disabled. Web Interface == Enable, but I've been closing any browser windows that point to it so it doesn't spend time on web page updates. Stay Alive was set to "google + gateway", but I just set it to "disable" to see if that helps. I suspected that the WiFi communications might be the issue. the wifi signal from the WFL is quite weak. I moved it last night to just a few feet from a strong AP. That seems to have reduced the errors, but as you can see it hasn't stopped them. FWIW, even when located just 5 feet from the AP, my AP reports the signal from the WFL at -61dBm, which is quite low. I wonder if that's normal for the device. I love the convenience of the WFL, but unless this problem can be solved, I'm not sure I'd recommend it, and I may return it for the Davis wired interface. BTW, I sent this as an e-mail to Ryan at Scaled Instruments (from whom I bought the station and the interface). He responded instantly, but wasn't able to help directly. He forwarded the e-mail to Wojtek, the developer of the device. I would have sent him the e-mail, except that there's no contact information on his web site. Ryan also promised a full refund if I can't solve it. He's been great to deal with. Anybody have any ideas or wisdom? In any event, I'll update as I learn more. On Thursday, September 24, 2020 at 11:14:24 AM UTC-7 loonsailor wrote: > I'm still getting the LOOP errors, not every time, so the system does > work, but more often than I like. Once every few hours it will exhaust all > 4 retries and I lose a record. > > I'm continuing to play with some parameters, both in weewx.conf and on the > WFL. I'll update when I know more. > > On Thursday, September 24, 2020 at 7:13:57 AM UTC-7 [email protected] > wrote: > >> the wifi logger looks attractive, for getting rid of the cable. >> could someone tell me the firmware version of my davis vp2 envoy? i >> haven’t updated it for a while :-) but my console is older. wifi logger >> needs vp2 v1.9+. >> wee_device says: >> CONSOLE FIRMWARE: >> Date: Apr 10 2006 >> Version: <Unavailable> >> >> On 23 Sep 2020, at 9:54 am, 'loonsailor' via weewx-user < >> [email protected]> wrote: >> >> WiFiLogger 2 <https://wifilogger.net/> (firmware 2.33) >> >> >> -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e17c0c83-80f1-4e26-b483-8246e701ad0fn%40googlegroups.com.
