I did not update those. Just a standard update to weewx v5___"Sent from my mobile device"On Feb 13, 2024, at 9:54 AM, matthew wall wrote:On Tuesday, February 13, 2024 at 8:41:31 AM UTC-5 Kingsclear Studios wrote:re:
did you update rtl-sdr?did you update rtl_433?did you up
On Tuesday, February 13, 2024 at 8:41:31 AM UTC-5 Kingsclear Studios wrote:
re:
did you update rtl-sdr?
did you update rtl_433?
did you update weewx-sdr?
did you update weewx-mqtt?
Do you have suggestions on how to execute that properly - can do the
research if needed, just curious if there's
re:
did you update rtl-sdr?
did you update rtl_433?
did you update weewx-sdr?
did you update weewx-mqtt?
Do you have suggestions on how to execute that properly - can do the
research if needed, just curious if there's a quick way to accomplish that
properly without impacting V5
On Tuesday, F
On Tuesday, February 13, 2024 at 7:42:35 AM UTC-5 Kingsclear Studios wrote:
No idea how to start picking this apart to find the root cause in V5.
i would be surprised if something in v5 is the root cause, but who knows?
did you update rtl-sdr?
did you update rtl_433?
did you update weewx-sdr?
d
Details:
Acurite 5-in-1 sensor, RTL_433 to MQTT (matt wall) + Weewx.
Weewx conf sensors:
[SDR]
# This section is for the software-defined radio driver.
# The driver to use
driver = user.sdr
path = /usr/local/bin
log_unknown_sensors = True
log_unmapped_sensors = True
