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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/ba5c2fcc-dd9b-4af1-8f37-05c56f249d8en%40googlegroups.com.
