When you subscribe to # are you seeing anything?
devices=/rtl433 was suppose to be on your rtl_433 command
Nope i see nothing
I run the command with verbose mode here is the output:
root@inferno:/# rtl_433 -F mqtt://192.168.88.10:1883,user=test,pass=test,retain=0,devices=/rtl_433 -vvv
rtl_433 version 18.12-203-ge47b62d branch master at 201904291632 inputs file rtl_tcp RTL-SDR
Trying conf file at “rtl_433.conf”…
Trying conf file at “/root/.config/rtl_433/rtl_433.conf”…
Trying conf file at “/usr/local/etc/rtl_433/rtl_433.conf”…
Trying conf file at “/etc/rtl_433/rtl_433.conf”…
Publishing MQTT UDP datagrams to 192.168.88.10 port 1883Consider using "-M newmodel" to transition to new model keys. This will become the default someday. A table of changes and discussion is at https://github.com/merbanan/rtl_433/pull/986.Registering protocol [1] “Silvercrest Remote Control”
Registering protocol [2] “Rubicson Temperature Sensor”
Registering protocol [3] “Prologue Temperature Sensor”
Registering protocol [4] “Waveman Switch Transmitter”
Registering protocol [8] “LaCrosse TX Temperature / Humidity Sensor”
Registering protocol [11] “Acurite 609TXC Temperature and Humidity Sensor”
Registering protocol [12] “Oregon Scientific Weather Sensor”
Registering protocol [15] “KlikAanKlikUit Wireless Switch”
Registering protocol [16] “AlectoV1 Weather Sensor (Alecto WS3500 WS4500 Ventus W155/W044 Oregon)”
Registering protocol [17] “Cardin S466-TX2”
Registering protocol [18] “Fine Offset Electronics, WH2, WH5, Telldus Temperature/Humidity/Rain Sensor”
Registering protocol [19] “Nexus Temperature & Humidity Sensor”
Registering protocol [20] “Ambient Weather Temperature Sensor”
Registering protocol [21] “Calibeur RF-104 Sensor”
Registering protocol [23] “DSC Security Contact”
Registering protocol [25] “GT-WT-02 Sensor”
Registering protocol [26] “Danfoss CFR Thermostat”
Registering protocol [29] “Chuango Security Technology”
Registering protocol [30] “Generic Remote SC226x EV1527”
Registering protocol [31] “TFA-Twin-Plus-30.3049, Conrad KW9010, Ea2 BL999”
Registering protocol [32] “Fine Offset Electronics WH1080/WH3080 Weather Station”
Registering protocol [33] “WT450, WT260H, WT405H”
Registering protocol [34] “LaCrosse WS-2310 / WS-3600 Weather Station”
Registering protocol [35] “Esperanza EWS”
Registering protocol [36] “Efergy e2 classic”
Registering protocol [38] “Generic temperature sensor 1”
Registering protocol [39] “WG-PB12V1 Temperature Sensor”
Registering protocol [40] “Acurite 592TXR Temp/Humidity, 5n1 Weather Station, 6045 Lightning”
Registering protocol [41] “Acurite 986 Refrigerator / Freezer Thermometer”
Registering protocol [42] “HIDEKI TS04 Temperature, Humidity, Wind and Rain Sensor”
Registering protocol [43] “Watchman Sonic / Apollo Ultrasonic / Beckett Rocket oil tank monitor”
Registering protocol [44] “CurrentCost Current Sensor”
Registering protocol [45] “emonTx OpenEnergyMonitor”
Registering protocol [46] “HT680 Remote control”
Registering protocol [47] “Conrad S3318P Temperature & Humidity Sensor”
Registering protocol [48] “Akhan 100F14 remote keyless entry”
Registering protocol [49] “Quhwa”
Registering protocol [50] “OSv1 Temperature Sensor”
Registering protocol [51] “Proove / Nexa / KlikAanKlikUit Wireless Switch”
Registering protocol [52] “Bresser Thermo-/Hygro-Sensor 3CH”
Registering protocol [53] “Springfield Temperature and Soil Moisture”
Registering protocol [54] “Oregon Scientific SL109H Remote Thermal Hygro Sensor”
Registering protocol [55] “Acurite 606TX Temperature Sensor”
Registering protocol [56] “TFA pool temperature sensor”
Registering protocol [57] “Kedsum Temperature & Humidity Sensor, Pearl NC-7415”
Registering protocol [58] “Blyss DC5-UK-WH”
Registering protocol [59] “Steelmate TPMS”
Registering protocol [60] “Schrader TPMS”
Registering protocol [62] “Elro DB286A Doorbell”
Registering protocol [63] “Efergy Optical”
Registering protocol [67] “Radiohead ASK”
Registering protocol [68] “Kerui PIR / Contact Sensor”
Registering protocol [69] “Fine Offset WH1050 Weather Station”
Registering protocol [70] “Honeywell Door/Window Sensor”
Registering protocol [71] “Maverick ET-732/733 BBQ Sensor”
Registering protocol [73] “LaCrosse TX141-Bv2/TX141TH-Bv2 sensor”
Registering protocol [74] “Acurite 00275rm,00276rm Temp/Humidity with optional probe”
Registering protocol [75] “LaCrosse TX35DTH-IT, TFA Dostmann 30.3155 Temperature/Humidity sensor”
Registering protocol [76] “LaCrosse TX29IT Temperature sensor”
Registering protocol [77] “Vaillant calorMatic VRT340f Central Heating Control”
Registering protocol [78] “Fine Offset Electronics, WH25, WH32B, WH24, WH65B, HP1000 Temperature/Humidity/Pressure Sensor”
Registering protocol [79] “Fine Offset Electronics, WH0530 Temperature/Rain Sensor”
Registering protocol [80] “IBIS beacon”
Registering protocol [81] “Oil Ultrasonic STANDARD FSK”
Registering protocol [82] “Citroen TPMS”
Registering protocol [83] “Oil Ultrasonic STANDARD ASK”
Registering protocol [84] “Thermopro TP11 Thermometer”
Registering protocol [85] “Solight TE44”
Registering protocol [86] “Wireless Smoke and Heat Detector GS 558”
Registering protocol [87] “Generic wireless motion sensor”
Registering protocol [88] “Toyota TPMS”
Registering protocol [89] “Ford TPMS”
Registering protocol [90] “Renault TPMS”
Registering protocol [91] “inFactory”
Registering protocol [92] “FT-004-B Temperature Sensor”
Registering protocol [93] “Ford Car Key”
Registering protocol [94] “Philips outdoor temperature sensor”
Registering protocol [95] “Schrader TPMS EG53MA4”
Registering protocol [96] “Nexa”
Registering protocol [97] “Thermopro TP08/TP12 thermometer”
Registering protocol [98] “GE Color Effects”
Registering protocol [99] “X10 Security”
Registering protocol [100] “Interlogix GE UTC Security Devices”
Registering protocol [102] “SimpliSafe Home Security System (May require disabling automatic gain for KeyPad decodes)”
Registering protocol [103] “Sensible Living Mini-Plant Moisture Sensor”
Registering protocol [108] “Hyundai WS SENZOR Remote Temperature Sensor”
Registering protocol [109] “WT0124 Pool Thermometer”
Registering protocol [110] “PMV-107J (Toyota) TPMS”
Registering protocol [111] “Emos TTX201 Temperature Sensor”
Registering protocol [112] “Ambient Weather TX-8300 Temperature/Humidity Sensor”
Registering protocol [113] “Ambient Weather WH31E Thermo-Hygrometer Sensor”
Registering protocol [114] “Maverick et73”
Registering protocol [115] “Honeywell ActivLink, Wireless Doorbell”
Registering protocol [116] “Honeywell ActivLink, Wireless Doorbell (FSK)”
Registering protocol [119] “Bresser Weather Center 5-in-1”
Registering protocol [121] “Opus/Imagintronix XT300 Soil Moisture”
Registering protocol [124] “LaCrosse/ELV/Conrad WS7000/WS2500 weather sensors”
Registering protocol [125] “TS-FT002 Wireless Ultrasonic Tank Liquid Level Meter With Temperature Sensor”
Registered 98 out of 125 device decoding protocols
Found 1 device(s)trying device 0: Realtek, RTL2838UHIDIR, SN: 00000001
Found Rafael Micro R820T tuner
Using device 0: Generic RTL2832U OEM
Exact sample rate is: 250000.000414 Hz
[R82XX] PLL not locked!
Sample rate set to 250000 S/s.
Bit detection level set to 0 (Auto).
Tuner gain set to Auto.
Reading samples in async mode…
Tuned to 433.920MHz.
Allocating 15 zero-copy buffers
MQTT Connected…
MQTT Connection established.
Badly formatted OS v2.1 message: {132} 06 ad 55 6a da d0 6a d5 56 ad ad 06 ad 55 6a da d0
Unrecognized Msg in OS v3: {132} 06 ad 55 6a da d0 6a d5 56 ad ad 06 ad 55 6a da d0
Possible Nexus: bitbuffer:: Number of rows: 1
[00] {182} 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 40 00 00 00 00 00 00 00
Possible DSC Contact: bitbuffer:: Number of rows: 1
[00] {11} 80 00 : 10000000 000
row 0 bit count 11
DSC row 0 invalid bit count 11
acurite_txr
bitbuffer:: Number of rows: 3
[00] {57} ac aa 44 21 09 65 29 00
[01] {57} ac aa 44 21 09 65 29 00
[02] {57} ac aa 44 21 09 65 29 00
acurite_txr: row 0 bits 57, bytes 8
acurite_txr Parity: 0000001
acurite_txr: row 1 bits 57, bytes 8
acurite_txr Parity: 0000001
acurite_txr: row 2 bits 57, bytes 8
acurite_txr Parity: 0000001
pulse_demod_pwm(): Acurite 592TXR Temp/Humidity, 5n1 Weather Station, 6045 Lightning
bitbuffer:: Number of rows: 3
[00] {57} ac aa 44 21 09 65 29 00
[01] {57} ac aa 44 21 09 65 29 00
[02] {57} ac aa 44 21 09 65 29 00
acurite_986: row 0 bits 60, bytes 5
acurite_986: skipping wrong len
acurite_986: row 1 bits 60, bytes 5
acurite_986: skipping wrong len
acurite_986: row 2 bits 60, bytes 5
acurite_986: skipping wrong len
RH ASK preamble not found
acurite_00275rm
bitbuffer:: Number of rows: 1
[00] {57} ac aa 44 21 09 65 29 00
acurite_00275rm
bitbuffer:: Number of rows: 1
[00] {57} ac aa 44 21 09 65 29 00
acurite_00275rm
bitbuffer:: Number of rows: 1
[00] {57} ac aa 44 21 09 65 29 00
philips_callback: wrong number of bits (183)
Interlogix: Preamble not found, bit_offset: 56
Interlogix: Preamble not found, bit_offset: 56
Interlogix: Preamble not found, bit_offset: 56
RH ASK preamble not found
AmbientWeather-TX8300: wrong size (182 bits)
Pulse data: 183 pulses
[ 0] Pulse: 162, Gap: 153, Period: 315
[ 1] Pulse: 160, Gap: 152, Period: 312
[ 2] Pulse: 159, Gap: 153, Period: 312
[ 3] Pulse: 159, Gap: 153, Period: 312
[ 4] Pulse: 107, Gap: 52, Period: 159
[ 5] Pulse: 59, Gap: 100, Period: 159
[ 6] Pulse: 107, Gap: 53, Period: 160
[ 7] Pulse: 59, Gap: 101, Period: 160
[ 8] Pulse: 107, Gap: 52, Period: 159
[ 9] Pulse: 107, Gap: 52, Period: 159
[ 10] Pulse: 60, Gap: 100, Period: 160
[ 11] Pulse: 59, Gap: 101, Period: 160
[ 12] Pulse: 106, Gap: 53, Period: 159
[ 13] Pulse: 59, Gap: 100, Period: 159
[ 14] Pulse: 107, Gap: 52, Period: 159
[ 15] Pulse: 60, Gap: 100, Period: 160
[ 16] Pulse: 107, Gap: 52, Period: 159
[ 17] Pulse: 59, Gap: 101, Period: 160
[ 18] Pulse: 107, Gap: 52, Period: 159
[ 19] Pulse: 60, Gap: 100, Period: 160
[ 20] Pulse: 59, Gap: 101, Period: 160
[ 21] Pulse: 106, Gap: 52, Period: 158
[ 22] Pulse: 60, Gap: 100, Period: 160
[ 23] Pulse: 59, Gap: 100, Period: 159
[ 24] Pulse: 59, Gap: 101, Period: 160
[ 25] Pulse: 107, Gap: 52, Period: 159
[ 26] Pulse: 59, Gap: 100, Period: 159
[ 27] Pulse: 60, Gap: 100, Period: 160
[ 28] Pulse: 59, Gap: 100, Period: 159
[ 29] Pulse: 59, Gap: 101, Period: 160
[ 30] Pulse: 107, Gap: 52, Period: 159
[ 31] Pulse: 60, Gap: 100, Period: 160
[ 32] Pulse: 59, Gap: 100, Period: 159
[ 33] Pulse: 59, Gap: 100, Period: 159
[ 34] Pulse: 60, Gap: 100, Period: 160
[ 35] Pulse: 107, Gap: 53, Period: 160
[ 36] Pulse: 58, Gap: 101, Period: 159
[ 37] Pulse: 59, Gap: 100, Period: 159
[ 38] Pulse: 59, Gap: 100, Period: 159
[ 39] Pulse: 60, Gap: 100, Period: 160
[ 40] Pulse: 107, Gap: 52, Period: 159
[ 41] Pulse: 59, Gap: 101, Period: 160
[ 42] Pulse: 59, Gap: 100, Period: 159
[ 43] Pulse: 108, Gap: 52, Period: 160
[ 44] Pulse: 59, Gap: 100, Period: 159
[ 45] Pulse: 107, Gap: 53, Period: 160
[ 46] Pulse: 107, Gap: 52, Period: 159
[ 47] Pulse: 59, Gap: 101, Period: 160
[ 48] Pulse: 59, Gap: 100, Period: 159
[ 49] Pulse: 107, Gap: 53, Period: 160
[ 50] Pulse: 59, Gap: 100, Period: 159
[ 51] Pulse: 107, Gap: 53, Period: 160
[ 52] Pulse: 59, Gap: 100, Period: 159
[ 53] Pulse: 59, Gap: 100, Period: 159
[ 54] Pulse: 108, Gap: 52, Period: 160
[ 55] Pulse: 59, Gap: 100, Period: 159
[ 56] Pulse: 107, Gap: 53, Period: 160
[ 57] Pulse: 59, Gap: 100, Period: 159
[ 58] Pulse: 59, Gap: 101, Period: 160
[ 59] Pulse: 107, Gap: 52, Period: 159
[ 60] Pulse: 59, Gap: 566, Period: 625
[ 61] Pulse: 160, Gap: 152, Period: 312
[ 62] Pulse: 160, Gap: 152, Period: 312
[ 63] Pulse: 160, Gap: 153, Period: 313
[ 64] Pulse: 160, Gap: 152, Period: 312
[ 65] Pulse: 107, Gap: 52, Period: 159
[ 66] Pulse: 60, Gap: 106, Period: 166
[ 67] Pulse: 107, Gap: 53, Period: 160
[ 68] Pulse: 59, Gap: 100, Period: 159
[ 69] Pulse: 107, Gap: 53, Period: 160
[ 70] Pulse: 107, Gap: 52, Period: 159
[ 71] Pulse: 60, Gap: 100, Period: 160
[ 72] Pulse: 59, Gap: 101, Period: 160
[ 73] Pulse: 106, Gap: 53, Period: 159
[ 74] Pulse: 59, Gap: 100, Period: 159
[ 75] Pulse: 107, Gap: 53, Period: 160
[ 76] Pulse: 59, Gap: 100, Period: 159
[ 77] Pulse: 107, Gap: 53, Period: 160
[ 78] Pulse: 59, Gap: 100, Period: 159
[ 79] Pulse: 107, Gap: 53, Period: 160
[ 80] Pulse: 59, Gap: 100, Period: 159
[ 81] Pulse: 59, Gap: 100, Period: 159
[ 82] Pulse: 107, Gap: 53, Period: 160
[ 83] Pulse: 59, Gap: 100, Period: 159
[ 84] Pulse: 59, Gap: 101, Period: 160
[ 85] Pulse: 59, Gap: 100, Period: 159
[ 86] Pulse: 108, Gap: 52, Period: 160
[ 87] Pulse: 59, Gap: 100, Period: 159
[ 88] Pulse: 59, Gap: 100, Period: 159
[ 89] Pulse: 60, Gap: 100, Period: 160
[ 90] Pulse: 59, Gap: 100, Period: 159
[ 91] Pulse: 108, Gap: 52, Period: 160
[ 92] Pulse: 59, Gap: 100, Period: 159
[ 93] Pulse: 59, Gap: 101, Period: 160
[ 94] Pulse: 59, Gap: 100, Period: 159
[ 95] Pulse: 59, Gap: 101, Period: 160
[ 96] Pulse: 107, Gap: 52, Period: 159
[ 97] Pulse: 60, Gap: 100, Period: 160
[ 98] Pulse: 59, Gap: 100, Period: 159
[ 99] Pulse: 59, Gap: 100, Period: 159
[100] Pulse: 60, Gap: 100, Period: 160
[101] Pulse: 107, Gap: 52, Period: 159
[102] Pulse: 59, Gap: 101, Period: 160
[103] Pulse: 59, Gap: 100, Period: 159
[104] Pulse: 108, Gap: 52, Period: 160
[105] Pulse: 59, Gap: 100, Period: 159
[106] Pulse: 107, Gap: 53, Period: 160
[107] Pulse: 107, Gap: 52, Period: 159
[108] Pulse: 59, Gap: 101, Period: 160
[109] Pulse: 59, Gap: 100, Period: 159
[110] Pulse: 108, Gap: 52, Period: 160
[111] Pulse: 59, Gap: 100, Period: 159
[112] Pulse: 107, Gap: 53, Period: 160
[113] Pulse: 59, Gap: 100, Period: 159
[114] Pulse: 59, Gap: 100, Period: 159
[115] Pulse: 108, Gap: 52, Period: 160
[116] Pulse: 59, Gap: 101, Period: 160
[117] Pulse: 107, Gap: 52, Period: 159
[118] Pulse: 60, Gap: 100, Period: 160
[119] Pulse: 59, Gap: 100, Period: 159
[120] Pulse: 107, Gap: 53, Period: 160
[121] Pulse: 58, Gap: 566, Period: 624
[122] Pulse: 160, Gap: 152, Period: 312
[123] Pulse: 160, Gap: 153, Period: 313
[124] Pulse: 160, Gap: 152, Period: 312
[125] Pulse: 160, Gap: 152, Period: 312
[126] Pulse: 108, Gap: 52, Period: 160
[127] Pulse: 59, Gap: 100, Period: 159
[128] Pulse: 107, Gap: 53, Period: 160
[129] Pulse: 59, Gap: 100, Period: 159
[130] Pulse: 108, Gap: 52, Period: 160
[131] Pulse: 107, Gap: 52, Period: 159
[132] Pulse: 60, Gap: 100, Period: 160
[133] Pulse: 59, Gap: 101, Period: 160
[134] Pulse: 107, Gap: 52, Period: 159
[135] Pulse: 59, Gap: 100, Period: 159
[136] Pulse: 108, Gap: 52, Period: 160
[137] Pulse: 59, Gap: 101, Period: 160
[138] Pulse: 107, Gap: 52, Period: 159
[139] Pulse: 59, Gap: 100, Period: 159
[140] Pulse: 108, Gap: 52, Period: 160
[141] Pulse: 59, Gap: 100, Period: 159
[142] Pulse: 59, Gap: 101, Period: 160
[143] Pulse: 107, Gap: 53, Period: 160
[144] Pulse: 59, Gap: 100, Period: 159
[145] Pulse: 59, Gap: 100, Period: 159
[146] Pulse: 60, Gap: 100, Period: 160
[147] Pulse: 107, Gap: 52, Period: 159
[148] Pulse: 59, Gap: 101, Period: 160
[149] Pulse: 59, Gap: 100, Period: 159
[150] Pulse: 59, Gap: 101, Period: 160
[151] Pulse: 59, Gap: 100, Period: 159
[152] Pulse: 107, Gap: 53, Period: 160
[153] Pulse: 59, Gap: 100, Period: 159
[154] Pulse: 59, Gap: 100, Period: 159
[155] Pulse: 60, Gap: 100, Period: 160
[156] Pulse: 59, Gap: 100, Period: 159
[157] Pulse: 118, Gap: 52, Period: 170
[158] Pulse: 59, Gap: 100, Period: 159
[159] Pulse: 60, Gap: 100, Period: 160
[160] Pulse: 59, Gap: 100, Period: 159
[161] Pulse: 59, Gap: 100, Period: 159
[162] Pulse: 108, Gap: 52, Period: 160
[163] Pulse: 59, Gap: 101, Period: 160
[164] Pulse: 58, Gap: 101, Period: 159
[165] Pulse: 107, Gap: 53, Period: 160
[166] Pulse: 59, Gap: 100, Period: 159
[167] Pulse: 107, Gap: 52, Period: 159
[168] Pulse: 108, Gap: 52, Period: 160
[169] Pulse: 59, Gap: 101, Period: 160
[170] Pulse: 58, Gap: 101, Period: 159
[171] Pulse: 107, Gap: 53, Period: 160
[172] Pulse: 59, Gap: 101, Period: 160
[173] Pulse: 106, Gap: 52, Period: 158
[174] Pulse: 60, Gap: 100, Period: 160
[175] Pulse: 59, Gap: 100, Period: 159
[176] Pulse: 108, Gap: 52, Period: 160
[177] Pulse: 60, Gap: 100, Period: 160
[178] Pulse: 107, Gap: 53, Period: 160
[179] Pulse: 58, Gap: 101, Period: 159
[180] Pulse: 59, Gap: 100, Period: 159
[181] Pulse: 107, Gap: 52, Period: 159
[182] Pulse: 59, Gap: 2501, Period: 2560
Possible DSC Contact: bitbuffer:: Number of rows: 1
[00] {11} 80 00 : 10000000 000
row 0 bit count 11
DSC row 0 invalid bit count 11
acurite_txr
bitbuffer:: Number of rows: 1
[00] { 1} 00 : 0
acurite_txr: row 0 bits 1, bytes 1
RH ASK preamble not found
acurite_00275rm
bitbuffer:: Number of rows: 1
[00] { 1} 00 : 0
philips_callback: wrong number of bits (1)
RH ASK preamble not found
Short preamble: 1 bits (expected 17)
Pulse data: 1 pulses
[ 0] Pulse: 63, Gap: 2501, Period: 2564
OK I just updated and I’m trying to catch up to you.
In your rtl_433 output do you see some thing like the picture shown on rtl_433 website?
It’s a very colorful display and shows the readings from your devices.
look here - https://github.com/merbanan/rtl_433/
In your log I see error messages regarding acurite_986 skipping wrong len
What device are you trying to capture?
I have many acurites but they all register under device 40.
Taking MQTT out of the picture completely use the command
rtl_433 -R 40 -C customary and see if you get the colorful picture.
I’ll check back on you later, but right now I don’t think your acurites are talking to your rtl_433 machine.
Here is the output:
root@inferno:/# rtl_433 -R 40
rtl_433 version 18.12-203-ge47b62d branch master at 201904291632 inputs file rtl_tcp RTL-SDR
Trying conf file at “rtl_433.conf”…
Trying conf file at “/root/.config/rtl_433/rtl_433.conf”…
Trying conf file at “/usr/local/etc/rtl_433/rtl_433.conf”…
Trying conf file at “/etc/rtl_433/rtl_433.conf”…
Consider using "-M newmodel" to transition to new model keys. This will become the default someday.
A table of changes and discussion is at https://github.com/merbanan/rtl_433/pull/986.
Registered 1 out of 125 device decoding protocols [ 40 ]
Found Rafael Micro R820T tuner
Exact sample rate is: 250000.000414 Hz
[R82XX] PLL not locked!
Sample rate set to 250000 S/s.
Tuner gain set to Auto.
Tuned to 433.920MHz.
Allocating 15 zero-copy buffers
time : 2019-05-07 13:34:22
model : Acurite tower sensor id : 11434
sensor_id : 0x2caa channel : B Temperature: 25.5 C Humidity : 33 battery_low: 0
time : 2019-05-07 13:34:22
model : Acurite tower sensor id : 11434
sensor_id : 0x2caa channel : B Temperature: 25.5 C Humidity : 33 battery_low: 0
time : 2019-05-07 13:34:22
model : Acurite tower sensor id : 11434
sensor_id : 0x2caa channel : B Temperature: 25.5 C Humidity : 33 battery_low: 0
^CSignal caught, exiting!
Just ran a couple test on my system using this command
sudo rtl_433 -R 40 -C customary -F “mqtt://192.168.1.10:1883,retain=0,devices=/rtl_433”
and it generated tons of mqtt transactions that all start with /rtl_433 in the topic. I have a separate transaction for each parameter (temp, humidity etc) Like I said tons of them.
I don’t have security on my mqtt broker? are you sure test, test is what you used?
Are you sure the IP number is right for your mqtt broker?
Are you executing from the command line?
Do you have rtl_433 running in supervisor?
Yes the ip is good for the broker
yes i execute from the command line on the host machine where hassio is located with the USB key.
I think there is a problem with the RQTT, because the rtl_433 work fine
Well i got it working with another MQTT in a docker ! Now i just have to figure out how to show them in Home Assisant, Thank you very much for you help cyn and 123 !
It’s working !
Glad to hear it!
I have two questions for you:
-
Which SDR device (Software Defined Radio) did you buy to receive the 433 MHz signals?
-
Does the device get warm during use?
That’s Great to hear.
@123 I have this one, warm yes, hot no
https://www.amazon.com/gp/product/B009U7WZCA/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
Just saw this discussion - I am also using a RTL-SDR exactly like what @cyn is using.
I setup rtl_433 using the new MQTT instead of JSON as well.
This I believe can be turned off if you prefer one message with all the data.
there are three types of messages, device, state, and event.
From zuckschwerdt’s (major contributer who worked on the MQTT part) comments on a discussion I had with him:
So take a look at what is being received on your MQTT broker and decide what messages you want. Then you can modify your rtl_433 command to only use devices, or events, or states, or a combination as you’d like.
Cheers!
DeadEnd
I have the same as cyn, and yes it’s a little bit warm !
Little question about the MQTT server, does it keep all the entrys in the topic ? Or it deletes it after a certain amount of time ? I have installed eclipse-mosquitto in a docker but i don’t see any configuration about that
By default, the broker is a simple ‘middleman’ who passes a topic’s message from the publisher to all the topic’s subscribers. It does not retain the message.
For example, if I publish ‘hello’ to the topic home/greeting, all subscribers to that topic, that are currently connected to the broker, will receive the message hello. If you subscribe to home/greeting after the hello message was sent, you will not receive the hello message. You will only receive future messages that are published after you have connected.
A publisher can request the broker to retain a copy of the message. The stored message is available to currently connected subscribers and future subscribers.
For example, let’s assume I published ‘hello’ to home/greeting as a retained message. All currently connected subscribers receive it. You connect to the broker later on, subscribe to home/greeting and immediately receive the retained message hello.
The broker keep the stored messages in its database. If you delete the database, all retained message will, of course, be gone.
2 Likes
Ahh good, thanks a lot for that detailed anwser !
That may depend on the sensor.
Some sensors call it ID, others SID, sensor_ID, etc. and there are other variations.
I know they are working on standardizing these in the rtl_433 - and I expect this is to allow just what you are asking.
So, currently it depends on the sensor… if it has an ID that matches what rtl_433 recognizes, I believe it will already be added - if it does not (or instances it calls the ID “sensor_ID”) then the program doesn’t recognize it.
You can use an MQTT client to see what is being published to know if it is being used. If it is not, you can take a look at the repo and find your sensor to see what the ID is being sent as. Then, if you are experienced enough, you could do a pull request to fix it - or you could put in an issue request to have it fixed. I see the most recent commit was to fix this for a few different sensors (commit #1034).
- DeadEnd
I guess I’m confused, I see the sensor’s ID in the message but I would like it to be in the topic.
In my testing of the new -F MQTT, All my sensor’s publish to /rtl_433 which would then require logic to separate them in Home Assistant. Seems inefficient. Hopefully I’m missing something in my understanding.
I’m using this:
rtl_433 -R 40 -C customary -F mqtt://192.168.1.10:1883,events=/rtl433
would like something like this
rtl_433 -R 40 -C customary -F mqtt://192.168.1.10:1883,opt=id,events=/rtl433,topic=id