If you're running weewx with the reference driver, you're listening to the UDP which has the sensor id in it.
If you're running wfpiconsole, you're connecting to the WF REST interface for your station. I think they're different. Just for grins, substitute in the new tempest id in weewx, restart weewx, and see if magic happens. It's already not working, so you can't break anything by doing a quick test. Alternately run my listener program and see what UDP is coming across the LAN (or run a sniffer or equivalent). On Friday, January 20, 2023 at 7:27:02 PM UTC-8 [email protected] wrote: > Thanks Vince, but the Tempest phone app has a replacement feature that > renames the new unit to the old sensor so that history is not lost. My new > sensor is now also ST-00044122 when I look at it in the phone app, and as > I mentioned, the wfpiconsole works like a charm without any changes to the > configuration, just left it as ST-00044122 and it works fine. Something > else is going on. > > Dan > > > On Friday, January 20, 2023 at 2:58:39 PM UTC-5 vince wrote: > >> Each Tempest has a unique ID. If you replaced your Tempest sensor, >> your ST-00044122 is now incorrect and you need to edit weewx.conf to use >> the new sensor's device ID so the driver looks for readings from 'that' new >> device. >> >> -- 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/40d3450e-e626-4b79-bd4a-af6599fb947an%40googlegroups.com.
