Replies: 2 comments 3 replies
-
Don't use |
Beta Was this translation helpful? Give feedback.
1 reply
-
Minimum set of keys is "model" and "id". |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've written and debugged a decoder and confirmed that it correctly decodes the message that was transmitted. But in my "production" environment, the messages from that device are not published via MQTT while messages from other devices ARE published.
For example,
rtl_433 -F json -F mqtt://localhost:1883
shows all decoded messages on the console, but the messages from the new device (Protocol 275) are not published via MQTT (while all the others are):{"time":"2025-02-04 11:28:26","protocol":40,"model":"Acurite-Tower","id":4652,"channel":"A","battery_ok":1,"temperature_C":6.4,"humidity":54,"mic":"CHECKSUM","mod":"ASK","freq":433.94736,"rssi":-0.308662,"snr":23.26314,"noise":-23.5718}
appears on the console AND the MQTT client (on another, network-connected computer), but
{"time" : "2025-02-04 11:28:26", "protocol" : 275, "type" : 1, "id" : 1, "temperature_C" : -95.900, "temperature_C" : -18.300, "humidity" : 35.000, "humidity" : 49.000, "pressure_hPa" : 999.300, "voltage_V" : 4.940, "mic" : "CRC8", "mod" : "ASK", "freq" : 433.947, "rssi" : -0.309, "snr" : 23.263, "noise" : -23.572}
does NOT appear on the MQTT client. [No, it's not -95.9°C here ... just test data to validate the decoder.]
Any suggestions where I might look to fix this? I have a feeling that it's something simple that I overlooked, perhaps not even related to the rtl_433 cmake build.
Beta Was this translation helpful? Give feedback.
All reactions