1. if you set loop_on_init = true at the top of weewx.conf the driver reacts gracefully
2. I'd trust Gary did the units part correctly :-) When you test the driver you see what the hardware emits... $ PYTHONPATH=/usr/share/weewx python3 -m user.gw1000 --test-driver Using configuration file /etc/weewx/weewx.conf Interrogating GW1000 at 192.168.1.129:45000 2021-10-13 10:32:47 PDT (1634146367): batteryStatus1: 0, batteryStatus2: 0, batteryStatus3: 0, batteryStatus4: 0, batteryStatus8: 0, dateTime: 1634146367, extraHumid1: 45, extraHumid2: 42, extraHumid3: 46, extraHumid4: 48, extraTemp1: 21.3, extraTemp2: 22.1, extraTemp3: 22.8, extraTemp4: 22.1, inHumidity: 45, inTemp: 22.5, outHumidity: 90, outTemp: 8.0, outTempBatteryStatus: 0, pressure: 1006.7, relbarometer: 1018.2, soilMoist1: 66, usUnits: 17, wh26_sig: 4, wh31_ch1_sig: 4, wh31_ch2_sig: 4, wh31_ch3_sig: 4, wh31_ch4_sig: 4, wh51_ch1_sig: 4 And when I query the db you can see the temperatures are in my desired US units after weewx did its thing... $ echo "select dateTime,outTemp,inTemp,extraTemp1,extraTemp2,extraTemp3,extraTemp4 from archive limit 10;" | sqlite3 weewx.sdb 1633887900|52.25|70.16|68.54|73.4|71.24|69.8 1633888200|52.16|69.98|68.54|73.34|71.18|69.8 1633888500|52.304|69.908|68.612|73.22|71.06|69.728 1633888800|52.532|69.836|68.576|73.352|70.976|69.62 1633889100|52.748|69.98|68.54|73.352|70.88|69.62 1633889400|52.88|69.98|68.54|73.2971428571429|70.7771428571429|69.62 1633889700|52.88|69.98|68.54|73.256|70.7|69.62 1633890000|53.0|69.8|68.54|73.22|70.652|69.62 1633890300|53.24|69.8|68.504|73.22|70.52|69.62 1633890600|53.48|69.764|68.54|72.98|70.52|69.584 On Wednesday, October 13, 2021 at 10:14:27 AM UTC-7 Francesco wrote: > Good evening, I have a Walbeck Halley WH2650 with the WH32B indoor T/H/P > sensor, the WS69 outdoor array and a WH57 lighting detector. I'm using > weewx on a raspberry, sending data to Meteotemplate and a remote influxDb > server+Grafana. At the moment I managed to get everything successfully > working with a custom modified version of the Interceptor driver, but I was > thinking to switch to the gw1000 api driver, in order to custom upload data > to another external server (now I'm sending data to the local raspberry). I > have two questions for those who are using it: > 1. What happens if wifi drops or router reboots (I have scheduled a router > reboot every night - a couple of minutes to complete the process - to > avoid issues with connection getting stuck - I'm using a usb sim card > dongle) and the driver is unable to reach the wh2650? Will it crash /stop > weewx (so that I have to manually restart it) or it will continue? (with > the interceptor being a simple "sniffer" nothing bad happens). > 2. Is the lightning_distance field treated correctly? What I mean is that > while the units of the main station packet loop are imperial and stored as > imperial in Weewx database (but shown and extracted as metric), the > lightning_distance field provided by the WH57 is in kilometres (checked > with the ecowitt app), causing a units' mismatch (it was one of the small > modifications I had to made to the interceptor driver - it was thinking > that lightning_distance was in miles, storing it directly to the database > and giving a mismatched value) > Sorry for being a bit lenghty, thank you for any help you can offer -- 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/452097bc-1c23-4072-ace9-d5be45906404n%40googlegroups.com.
