After more than a year I'm trying to switch from the interceptor to the gw1000 driver (I bought a new, more stable router that doesn't need rebooting), but I'm having some issues (one small). Here is the output running the driver directly: UV: 0, dateTime: 1669558961, dayRain: 0.0, daymaxwind: 9.2, inHumidity: 69, inTemp: 10.3, lightning_distance: None, lightning_last_det_time: None, lightning_strike_count: None, lightningcount: 0, luminosity: 2852.0, monthRain: 125.8, outHumidity: 74, outTemp: 7.7, pressure: 948.2, rain: None, rainRate: 0.0, relbarometer: 1020.3, stormRain: 0.0, usUnits: 17, uvradiation: 2.4, weekRain: 0.0, wh25_batt: 0, wh25_sig: 4, wh57_batt: 4, wh57_sig: 4, wh65_batt: 0, wh65_sig: 4, windDir: 65, windGust: 3.6, windSpeed: 1.4, yearRain: 752.4 The first (small one) is probabily due to the old weewx /Seasons skin version (4.5.1), pressure value is not shown on Seasons skin (N/A) (I could solve it by upgrading weewx or by editing the gw1000 field map, not a big issue). The other one is that the WH2650 stops posting to Weather Underground (it is configured to post directly to WUnderground website through the API key). If I switch back to the interceptor driver, posting starts to work again. Could somehow the polling from the driver "block" Wunderground posting? Does anybody have the same issue / know how to fix it? Thank you! Il giorno giovedì 14 ottobre 2021 alle 08:21:13 UTC+2 Francesco ha scritto:
> Ok, perfect, I will give the gw1000 a try and let you know. Thank you > again for your help! > Il giorno mercoledì 13 ottobre 2021 alle 23:06:05 UTC+2 gjr80 ha scritto: > >> 1. As Vince says set loop_on_init = True. If the GW1000 driver loses >> connection to the GW1000 it will retry (by default) two more times before >> giving up. If loop_on_init is set True WeeWX will then wait 60 seconds >> before effectively restarting, thus kicking off the process again. I can't >> guarantee that a router reboot will see GW1000 connectivity restored, it >> should, but its possible it may not. Vince and others appear to have >> success in this regard, but at times WeeWX has been unable to find my >> GW1000 after a network outage. Certainly the GW1000 driver is slightly more >> fragile in this regard than the interceptor. If you try it and have issues >> post something here as there are other things we can try (eg increasing the >> GW1000 driver retry time). >> >> 2. Yes. The interceptor driver works fine with the GW1000, but does not >> natively support the WH57 lightning detector. When used with the GW1000 the >> interceptor driver emit loop packets in US customary units (ie distance in >> miles) as the usUnits field is set to 1. It sounds like whatever >> modifications have been made to your interceptor driver simply took the >> WH57 lightning distance value and blindly added it to the loop packet >> without checking the unit system used in the loop packet and converting as >> necessary. >> >> The good thing about the GW1000 driver is that you can install the driver >> and run it directly without changing your existing WeeWX setup. Refer to >> the GW1000 driver readme <https://github.com/gjr80/weewx-gw1000#readme>, >> in particular step 5. If you don't like it, simply uninstall the driverit >> and your existing WeeWX install will be unchanged. >> >> Gary >> > -- 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/025691d4-d8a7-4d0c-895c-21337ef0fcb4n%40googlegroups.com.
