My confusion comes from the error you posted. I know that WF servers have hiccups periodically, so not being able to grab data from their REST interface is possible, and your weewx going boom when that happens is also possible if your driver doesn't handle those cases well.
But - the weatherflowUDP driver does not use REST at all. Are you sure you didn't also install one of the forked WeatherFlow drivers that somebody was cooking up to try to talk REST or both UDP+REST ? You could also do something like "grep -rHi 18869[0-9]" from the top of your weewx tree to look for what file defines the device id you're seeing in your logs. On Tuesday, March 21, 2023 at 11:15:37 AM UTC-7 Justin Cole wrote: Specifically, it seems to have the wrong device id somehow. in the GET function "https://swd.weatherflow.com:443 "GET /swd/rest/observations/device/188684?token=mytoken' statement, the device id should be 188685. Mar 21 12:04:58 nagios weewx[12883] CRITICAL __main__: Caught unrecoverable exception: Mar 21 12:04:58 nagios weewx[12883] CRITICAL __main__: **** Could not fetch records from WeatherFlow webservice: <Response [404]> -- 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/00ca4c3c-e07d-4284-bddd-e360ed338400n%40googlegroups.com.
