Home Assistant Add-on: rtl_433 with MQTT auto discovery

@catduckgnaf I’ve installed the latest release of the addon, 2024.3.0, and I see some new options:
discovery_log_level and discovery_interval.
My current config is:
image

There is no change, however. I still don’t have autodiscovery working :sob:.
I see no log entries neither for the autodiscovery.

The folder config/rtl_433/logs is also empty. Shouldn’t there be the log files generated by the addon?

My current log from the addon page is:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
rtl_433 version 23.11-65-g8d1541bd branch master at 202402291155 inputs file rtl_tcp RTL-SDR
MQTT: Publishing MQTT data to core-mosquitto port 1883
MQTT: Publishing device info to MQTT topic "rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id]".
MQTT: Publishing events info to MQTT topic "rtl_433/9b13b3f4-rtl433/events".
MQTT: Publishing states info to MQTT topic "rtl_433/9b13b3f4-rtl433/states".
Found Rafael Micro R820T tuner
Exact sample rate is: 250000.000414 Hz
[SDR] Using device 0: Realtek, RTL2838UHIDIR, SN: 00000001, "Generic RTL2832U OEM"
SDR: Using device 0: Realtek, RTL2838UHIDIR, SN: 00000001, "Generic RTL2832U OEM"
[R82XX] PLL not locked!
[Auto Level] Estimated noise level is -16.4 dB, adjusting minimum detection level to -13.4 dB
Auto Level: Estimated noise level is -16.4 dB, adjusting minimum detection level to -13.4 dB
[Auto Level] Estimated noise level is -17.5 dB, adjusting minimum detection level to -14.5 dB
Auto Level: Estimated noise level is -17.5 dB, adjusting minimum detection level to -14.5 dB
[Auto Level] Current noise level -18.5 dB, estimated noise -17.6 dB
Auto Level: Current noise level -18.5 dB, estimated noise -17.6 dB
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

time      : 2024-03-01T10:50:34.667001+0200
Protocol  : 153
model     : Cotech-367959
ID        : 90
Battery   : 1
Temperature: 12.0 C
Humidity  : 69 %
Rain      : 42.6 mm
Wind direction: 226
Wind      : 0.5 m/s
Gust      : 0.7 m/s
Light Intensity: 5672 lux
UV Index  : 6
Integrity : CRC
Modulation: ASK
Freq      : 433.9 MHz
RSSI      : -0.1 dB
SNR       : 18.8 dB
Noise     : -18.9 dB
{"time" : "2024-03-01T10:50:34.667001+0200", "protocol" : 153, "model" : "Cotech-367959", "id" : 90, "battery_ok" : 1, "temperature_C" : 12.000, "humidity" : 69, "rain_mm" : 42.600, "wind_dir_deg" : 226, "wind_avg_m_s" : 0.500, "wind_max_m_s" : 0.700, "light_lux" : 5672, "uv" : 6, "mic" : "CRC", "mod" : "ASK", "freq" : 433.894, "rssi" : -0.124, "snr" : 18.798, "noise" : -18.922}
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

time      : 2024-03-01T10:50:34.667001+0200
Protocol  : 153
model     : Cotech-367959
ID        : 90
Battery   : 1
Temperature: 12.0 C
Humidity  : 69 %
Rain      : 42.6 mm
Wind direction: 226
Wind      : 0.5 m/s
Gust      : 0.7 m/s
Light Intensity: 5672 lux
UV Index  : 6
Integrity : CRC
Modulation: ASK
Freq      : 433.9 MHz
RSSI      : -0.1 dB
SNR       : 18.8 dB
Noise     : -18.9 dB
{"time" : "2024-03-01T10:50:34.667001+0200", "protocol" : 153, "model" : "Cotech-367959", "id" : 90, "battery_ok" : 1, "temperature_C" : 12.000, "humidity" : 69, "rain_mm" : 42.600, "wind_dir_deg" : 226, "wind_avg_m_s" : 0.500, "wind_max_m_s" : 0.700, "light_lux" : 5672, "uv" : 6, "mic" : "CRC", "mod" : "ASK", "freq" : 433.894, "rssi" : -0.124, "snr" : 18.798, "noise" : -18.922}
[Auto Level] Current noise level -18.5 dB, estimated noise -18.3 dB
Auto Level: Current noise level -18.5 dB, estimated noise -18.3 dB

RSSI      : -0.1 dB
SNR       : 18.6 dB
Noise     : -18.7 dB
{"time" : "2024-03-01T10:51:06.660821+0200", "protocol" : 153, "model" : "Cotech-367959", "id" : 90, "battery_ok" : 1, "temperature_C" : 12.056, "humidity" : 69, "rain_mm" : 42.600, "wind_dir_deg" : 281, "wind_avg_m_s" : 0.200, "wind_max_m_s" : 0.300, "light_lux" : 5763, "uv" : 6, "mic" : "CRC", "mod" : "ASK", "freq" : 433.897, "rssi" : -0.099, "snr" : 18.621, "noise" : -18.720}
[Auto Level] Current noise level -18.5 dB, estimated noise -18.4 dB
Auto Level: Current noise level -18.5 dB, estimated noise -18.4 dB
[Auto Level] Estimated noise level is -18.5 dB, adjusting minimum detection level to -15.5 dB
Auto Level: Estimated noise level is -18.5 dB, adjusting minimum detection level to -15.5 dB
[Auto Level] Current noise level -18.5 dB, estimated noise -18.5 dB
Auto Level: Current noise level -18.5 dB, estimated noise -18.5 dB
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

time      : 2024-03-01T10:51:22.661538+0200
Protocol  : 153
model     : Cotech-367959
ID        : 90
Battery   : 1
Temperature: 12.1 C
Humidity  : 69 %
Rain      : 42.6 mm
Wind direction: 277
Wind      : 0.3 m/s
Gust      : 0.3 m/s
Light Intensity: 5378 lux
UV Index  : 4
Integrity : CRC
Modulation: ASK
Freq      : 433.9 MHz
RSSI      : -0.1 dB
SNR       : 18.5 dB
Noise     : -18.6 dB
{"time" : "2024-03-01T10:51:22.661538+0200", "protocol" : 153, "model" : "Cotech-367959", "id" : 90, "battery_ok" : 1, "temperature_C" : 12.056, "humidity" : 69, "rain_mm" : 42.600, "wind_dir_deg" : 277, "wind_avg_m_s" : 0.300, "wind_max_m_s" : 0.300, "light_lux" : 5378, "uv" : 4, "mic" : "CRC", "mod" : "ASK", "freq" : 433.896, "rssi" : -0.122, "snr" : 18.481, "noise" : -18.603}
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

time      : 2024-03-01T10:51:22.661538+0200
Protocol  : 153
model     : Cotech-367959
ID        : 90
Battery   : 1
Temperature: 12.1 C
Humidity  : 69 %
Rain      : 42.6 mm
Wind direction: 277
Wind      : 0.3 m/s
Gust      : 0.3 m/s
Light Intensity: 5378 lux
UV Index  : 4
Integrity : CRC
Modulation: ASK
Freq      : 433.9 MHz
RSSI      : -0.1 dB
SNR       : 18.5 dB
Noise     : -18.6 dB
{"time" : "2024-03-01T10:51:22.661538+0200", "protocol" : 153, "model" : "Cotech-367959", "id" : 90, "battery_ok" : 1, "temperature_C" : 12.056, "humidity" : 69, "rain_mm" : 42.600, "wind_dir_deg" : 277, "wind_avg_m_s" : 0.300, "wind_max_m_s" : 0.300, "light_lux" : 5378, "uv" : 4, "mic" : "CRC", "mod" : "ASK", "freq" : 433.896, "rssi" : -0.122, "snr" : 18.481, "noise" : -18.603}
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

time      : 2024-03-01T10:51:22.661538+0200
Protocol  : 153
model     : Cotech-367959
ID        : 90
Battery   : 1
Temperature: 12.1 C
Humidity  : 69 %
Rain      : 42.6 mm
Wind direction: 277
Wind      : 0.3 m/s
Gust      : 0.3 m/s
Light Intensity: 5378 lux
UV Index  : 4
Integrity : CRC
Modulation: ASK
Freq      : 433.9 MHz
RSSI      : -0.1 dB
SNR       : 18.5 dB
Noise     : -18.6 dB
{"time" : "2024-03-01T10:51:22.661538+0200", "protocol" : 153, "model" : "Cotech-367959", "id" : 90, "battery_ok" : 1, "temperature_C" : 12.056, "humidity" : 69, "rain_mm" : 42.600, "wind_dir_deg" : 277, "wind_avg_m_s" : 0.300, "wind_max_m_s" : 0.300, "light_lux" : 5378, "uv" : 4, "mic" : "CRC", "mod" : "ASK", "freq" : 433.896, "rssi" : -0.122, "snr" : 18.481, "noise" : -18.603}
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

time      : 2024-03-01T10:51:22.661538+0200
Protocol  : 153
model     : Cotech-367959
ID        : 90
Battery   : 1
Temperature: 12.1 C
Humidity  : 69 %
Rain      : 42.6 mm
Wind direction: 277
Wind      : 0.3 m/s
Gust      : 0.3 m/s
Light Intensity: 5378 lux
UV Index  : 4
Integrity : CRC
Modulation: ASK
Freq      : 433.9 MHz
RSSI      : -0.1 dB
SNR       : 18.5 dB
Noise     : -18.6 dB
{"time" : "2024-03-01T10:51:22.661538+0200", "protocol" : 153, "model" : "Cotech-367959", "id" : 90, "battery_ok" : 1, "temperature_C" : 12.056, "humidity" : 69, "rain_mm" : 42.600, "wind_dir_deg" : 277, "wind_avg_m_s" : 0.300, "wind_max_m_s" : 0.300, "light_lux" : 5378, "uv" : 4, "mic" : "CRC", "mod" : "ASK", "freq" : 433.896, "rssi" : -0.122, "snr" : 18.481, "noise" : -18.603}
[Auto Level] Current noise level -18.6 dB, estimated noise -18.7 dB
Auto Level: Current noise level -18.6 dB, estimated noise -18.7 dB

Hello,

Yes, very interesting on the logging. I would backup and delete your entire rtl_433 folder. Reinstall the add on and attempt to start fresh with as little changes as possible. I have a work around temporarily got discovery, but the lack of logging which is a default is interesting.

Hello!

Same here. I started from scratch, here are my conf files:

rtl_433.conf

## version 2024.2

report_meta stats
report_meta time:iso:usec:tz
report_meta protocol

# For RTL-SDR: gain in tenths of dB ("0" is auto).
gain 0

# usb device index 
# device 0

# this is suggested
convert si

## default is "433.92M", other reasonable values are 315M, 345M, 915M and 868M
frequency     433.92M

# default is "600" seconds, only used when multiple frequencies are given
hop_interval  600

# default is "250k", other valid settings are 1024k, 2048k, 3200k
sample_rate   250k

#  Set minlevel automatically based on average estimated noise.
pulse_detect autolevel

#  Skip frames below estimated noise level to lower cpu load.
# pulse_detect squelch

# Log levels 1=fatal, 2=critical, 3=error, 4=warning (default), 5=notice, 6=info, 7=debug, 8=trace
verbose 7

## at a minimum you must enter username and password below. Replace rtl433_user with your username, and rtl433_pass with your password
output mqtt://core-mosquitto:1883,user=xxx,pass=yyy,retain=1,devices=rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id],events=rtl_433/9b13b3f4-rtl433/events,states=rtl_433/9b13b3f4-rtl433/states

# to see logs in console
output kv

# log to json file, easier to see device information
output json:/config/rtl_433/logs/output.json


protocol 230 # Vauno EN8822C

addon conf

rtl_433_conf_file: /config/rtl_433/rtl_433.conf
discovery: true
discovery_retain: true
discovery_force_update: false
discovery_host: core-mosquitto
discovery_port: 1883
discovery_user: xxx
discovery_password: yyy
discovery_topic: rtl_433/+/events
discovery_prefix: homeassistant
device_topic_suffix: ""
discovery_interval: 600
discovery_ids: "230" (I can't delete "")
discovery_log_level: debug
other_args: ""

discovery_ids: “230” : I can’t delete “”

addon logs

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
rtl_433 version 23.11-68-gb2a9bf38 branch master at 202403021530 inputs file rtl_tcp RTL-SDR
MQTT: Publishing MQTT data to core-mosquitto port 1883
MQTT: Publishing device info to MQTT topic "rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id]".
MQTT: Publishing events info to MQTT topic "rtl_433/9b13b3f4-rtl433/events".
MQTT: Publishing states info to MQTT topic "rtl_433/9b13b3f4-rtl433/states".
Registering protocol [230] "Vauno EN8822C"
[Protocols] Registered 1 out of 253 device decoding protocols
Protocols: Registered 1 out of 253 device decoding protocols
[Input] The internals of input handling changed, read about and report problems on PR #1978
Input: The internals of input handling changed, read about and report problems on PR #1978
[SDR] Found 1 device(s)
SDR: Found 1 device(s)
[SDR] trying device 0: Realtek, RTL2838UHIDIR, SN: 00000001
SDR: trying device 0: Realtek, RTL2838UHIDIR, SN: 00000001
Found Rafael Micro R820T tuner
[SDR] Using device 0: Realtek, RTL2838UHIDIR, SN: 00000001, "Generic RTL2832U OEM"
SDR: Using device 0: Realtek, RTL2838UHIDIR, SN: 00000001, "Generic RTL2832U OEM"
Exact sample rate is: 250000.000414 Hz
[R82XX] PLL not locked!
[SDR] Sample rate set to 250000 S/s.
SDR: Sample rate set to 250000 S/s.
[Input] Bit detection level set to 0.0 (Auto).
Input: Bit detection level set to 0.0 (Auto).
[SDR] Tuner gain set to Auto.
SDR: Tuner gain set to Auto.
[Input] Reading samples in async mode...
Input: Reading samples in async mode...
[SDR] rtlsdr_set_center_freq 433920000 = 0
SDR: rtlsdr_set_center_freq 433920000 = 0
[SDR] Tuned to 433.920MHz.
SDR: Tuned to 433.920MHz.
[acquire_thread] acquire_thread enter...
acquire_thread: acquire_thread enter...
[MQTT] MQTT Connected...
MQTT: MQTT Connected...
[MQTT] MQTT Connection established.
MQTT: MQTT Connection established.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
time      : 2024-03-02T14:47:32.466370-0500        Protocol  : 230
model     : Vauno-EN8822C ID        : 111
Channel   : 3            Battery   : 1             Temperature: 18.3 C       Humidity  : 39 %          Integrity : CHECKSUM
[pulse_slicer_ppm] Vauno EN8822C
codes     : {0}0, {42}6f20b74e0ec, {1}0, {42}6f20b74e0ec, {1}0, {42}6f20b74e0ec, {1}0, {42}6f20b74e0ec, {1}0, {42}6f20b74e0ec, {1}0, {42}6f20b74e0ec, {0}0
pulse_slicer_ppm: Vauno EN8822C codes [{0}0, {42}6f20b74e0ec, {1}0, {42}6f20b74e0ec, {1}0, {42}6f20b74e0ec, {1}0, {42}6f20b74e0ec, {1}0, {42}6f20b74e0ec, {1}0, {42}6f20b74e0ec, {0}0]
[pulse_slicer_ppm] Vauno EN8822C
codes     : {0}0, {38}6f20b74e0c, {0}0, {0}0
pulse_slicer_ppm: Vauno EN8822C codes [{0}0, {38}6f20b74e0c, {0}0, {0}0]
[pulse_slicer_ppm] Vauno EN8822C
codes     : {3}6, {1}0, {37}6f20b74e08, {0}0, {0}0
pulse_slicer_ppm: Vauno EN8822C codes [{3}6, {1}0, {37}6f20b74e08, {0}0, {0}0]
[pulse_slicer_ppm] Vauno EN8822C
codes     : {1}0, {42}6f20b74e0ec, {1}0, {0}0, {0}0
pulse_slicer_ppm: Vauno EN8822C codes [{1}0, {42}6f20b74e0ec, {1}0, {0}0, {0}0]
[pulse_slicer_ppm] Vauno EN8822C
codes     : {31}05ba7076, {1}0, {5}68, {0}0, {0}0
pulse_slicer_ppm: Vauno EN8822C codes [{31}05ba7076, {1}0, {5}68, {0}0, {0}0]
[pulse_slicer_ppm] Vauno EN8822C
codes     : {36}c82dd383b, {1}0, {42}6f20b74e0ec, {0}0
pulse_slicer_ppm: Vauno EN8822C codes [{36}c82dd383b, {1}0, {42}6f20b74e0ec, {0}0]
[pulse_slicer_ppm] Vauno EN8822C
codes     : {19}a7076, {1}0, {0}0, {0}0, {0}0
pulse_slicer_ppm: Vauno EN8822C codes [{19}a7076, {1}0, {0}0, {0}0, {0}0]
[pulse_slicer_ppm] Vauno EN8822C
codes     : {35}905ba7076, {1}0, {42}6f20b74e0ec, {1}0, {18}6f208, {0}0, {0}0
pulse_slicer_ppm: Vauno EN8822C codes [{35}905ba7076, {1}0, {42}6f20b74e0ec, {1}0, {18}6f208, {0}0, {0}0]
[pulse_slicer_ppm] Vauno EN8822C
codes     : {23}ba7076, {1}0, {0}0, {0}0
pulse_slicer_ppm: Vauno EN8822C codes [{23}ba7076, {1}0, {0}0, {0}0]
[pulse_slicer_ppm] Vauno EN8822C
codes     : {42}6f20b74e0ec, {0}0, {0}0
pulse_slicer_ppm: Vauno EN8822C codes [{42}6f20b74e0ec, {0}0, {0}0]
[pulse_slicer_ppm] Vauno EN8822C
codes     : {42}6f20b74e0ec, {0}0
pulse_slicer_ppm: Vauno EN8822C codes [{42}6f20b74e0ec, {0}0]

Screenshot of MQTT Explorer:

Nothing in the log folder.

Any idea?

Thanks!!!

Log folder should be /config/rtl_433/logs/output.json

I am currently working with the old add-on devs to try and combine resource. Currently discovery does not seem to work, I will try to figure out why…

This week I had to move (physically) entire servers to a new location and it has been alot.

@deviantintegral any idea on why my built in discovery isn’t seeing things? Mismatch between my default template and script?

So tried to tinker some more and install catduckgnaf version and only messed things up further. I restored a backup I made before tying the different version and neither rtl_433 or rtl_433 MQTT Auto Discovery will start. They will show items in the log, but if I stay on the info screen the wheel will just keep spinning. If I go to the logs I’ll see info, but back to info and it’s not running.

EDIT: For some reason I needed to reboot the whole raspeberry pi rather than just HA to fix this issue.

any idea why my 433mhz door sensor is empty with the Auto-Discovery add on?

in my MQTT, i see it as:

Message 10 received on rtl_433/17069798-rtl433/events at 1:38 PM:

{
    "time": "2024-03-09T13:38:13.568714-0500",
    "model": "Kerui-Security",
    "id": 133120,
    "cmd": 14,
    "opened": 1,
    "state": "open"
}

The Vivint system I inherited when I bought my home uses a 2GIG TAKE-345 device to transmit all of my wired sensors’ data, which is mainly from door sensors and several heat sensors. I noticed that the 2Gig DW10/DW11 are the only supported 2GIG products in the “supported device protocols” list. Do any of the listed protocols support the TAKE-345?

I tried setting protocol to 70 (Honeywell Door/Window Sensor, 2Gig DW10/DW11, RE208 repeater), which found 3 alarm devices but those appear to be my wireless smoke detectors. The rtl_433 addon has yet to find any of the door sensors, but my Vivint system also stopped detecting them over time. If anyone can confirm that this addon supports the TAKE-345, that’ll help me troubleshoot our wired sensors. If you got this far, thanks for reading this!

Has anyone had any luck using either the DW10 or DW11 door/window sensors? They’re listed in the supported protocols, but this issue on a similar project has been open since 2020. Looks like the transmissions from the the DW10 and DW11 are encoded and the community has yet to figure out how to decode them.

Hello Everyone, Currently the discovery I built in doesn’t seem to be working.
I have been a little tied up with some personal things, so I have been unable to diagnose the issue. I was also hoping to get some additional developer support from other rtl_433 users who have been using longer then I have. Right now rtl_433 is only slightly better then where it has been, but I agree if its your first time using rtl_433 things are still not perfect.


I am trying to not just bandaid fix discovery, but improve things all around. I am currently working on why it isn't working with all the mqtt topics etc. This is not my perfect area, and I believe its something simple I overlooked.

Long story short, if you are new to Rtl_433 Please be patient and wait, nothing is worse then it was, but consider it not working. If you have used rtl_433 for a while, then give it a go or help out.

Check in a week, and I hope to have a good update. In the mean time, you can try and use the old scripts, but really just hang in there and work on a another project. :)

if anyone has used my add-on, and they want to try executing the discovery script separately, I am sure this is not the best practice, but go to Home Assistant terminal, (install the add-on)

add-py3-paho-mqtt
python3 -u config/rtl_433/scripts/rtl_433_mqtt_hass.py  -H "Host" -p "Port" -u "Username" -P "Password" -R rtl_433/+/events -i 600 --ids "23"

replace everything in quotes, with the correct information and remove the quotes.

Have to figure out the issue as to why it isn’t working with the add-on, and I need to work on a proper integration.

Tried with the two commands you noted, however the first one is not working:
image

I installed paho-mqtt package with pip install paho-mqtt, then I started the discovery script.
It throws an error and stops:

Then I attempted to start the rtl_433 addon and now it seems it’s attempting to start Discovery, however it stops at the same step and does not move forward (perhaps it the discovery script crashes the same way as above)


So perhaps your addon needs to install paho-mqtt client also for Discovery to work.

The addon has it.

I think struggling to get the add on run the script and regular rtl_433 at the same time.

Working on the discovery script right now in the way I am is not the best use of my time. So for now I have disabled discovery with my add-on, and will focus on

You are more then welcome to try a repo I made, of just the discovery script.

I understand its not working for you, and you are still more then welcome to figure out how to manually configure rtl_433 if this doesn’t work. It is alot of work making a true integration, and I haven’t got there yet.

So now we have basically what we had before, only a little better.

Supervisor can’t upgrade to 2024.3.10
24-03-14 09:24:41 INFO (MainThread) [supervisor.docker.addon] Updating image 2eac6316/amd64-addon-rtl_433:2024.3.9 to 2eac6316/amd64-addon-rtl_433:2024.3.10 24-03-14 09:24:41 ERROR (MainThread) [supervisor.docker.addon] Invalid build environment, can't build this add-on!

Try uninstall and reinstall, I don’t understand why.

Now Discovery and Add-on are separate repos. I plan to replace the discovery script, but We should have a working alternative in the mean time.

I removed discovery from the other add-on. I have tested it, and it seems to work, only discovery device ID that are asked for.

Also, please update your rtl_433.conf to have the following format for mqtt.

output mqtt://core-mosquitto:1883,user=rtl433_user,pass=rtl433_pass,retain=1,devices=rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id],events=rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id],states=rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id]/states

It is slightly different, that matters.

The goal now is to build a true integration, and to expand on the useability of discovery script in the mean time. I/We would appreciate any help and collaboration on this project. However we should be in a good place!

Ok, uninstalled and installed fresh. That way it worked.
I also updated rtl_433.conf as you instructed.

Installed discovery addon, configured it, but still does not work.

It just hangs here, like the other day
image

Hi! Nice work!

I have both add ons working, rtl_433 and autodiscovery, but autodiscorey reports that my model is not recognized.

How can I setup auto discovery to work with my model?

I would like to contribute to the project also.

My sensors format and data are:

[2024-03-28T13:08:53+0100] DEBUG:root:MQTT message: "{\"time\":\"2024-03-28 13:08:53.104150\",\"protocol\":153,\"model\":\"Cotech-367959\",\"id\":156,\"battery_ok\":1,\"temperature_C\":8.11111,\"humidity\":90,\"rain_mm\":177.5,\"wind_dir_deg\":153,\"wind_avg_m_s\":4.0,\"wind_max_m_s\":4.6,\"light_lux\":19712,\"uv\":10,\"mic\":\"CRC\",\"mod\":\"ASK\",\"freq\":434.05072,\"rssi\":-0.262642,\"snr\":16.37101,\"noise\":-16.6337}"
[2024-03-28T13:08:53+0100] WARNING:root:No suitable identifier found for model: Cotech-367959
[2024-03-28T13:09:06+0100] DEBUG:paho.mqtt.client:Received PUBLISH (d0, q0, r0, m0), 'rtl_433/9b13b3f4-rtl433-next/events', ...  (248 bytes)
[2024-03-28T13:09:06+0100] DEBUG:root:MQTT message: "{\"time\":\"2024-03-28 13:09:05.807000\",\"protocol\":20,\"model\":\"Ambientweather-F007TH\",\"id\":193,\"channel\":3,\"battery_ok\":1,\"temperature_C\":19.61111,\"humidity\":61,\"mic\":\"CRC\",\"mod\":\"ASK\",\"freq\":434.05162,\"rssi\":-0.198952,\"snr\":16.70143,\"noise\":-16.9004}"
[2024-03-28T13:09:06+0100] WARNING:root:No suitable identifier found for model: Ambientweather-F007TH

Thanks!

Hello,

Would love your help contributing. I have nobody helping, so right now the add-on is better, but basically if you can’t add it yourself manually you are SOL…

I plan to write a custom integration to add devices. The script has never worked, so that’s what started this.

So if you want to contribute, and can help code a custom integration that would be great. I hope I have more time in the future.

Basically, it’s unusable like it always was if you don’t know how to manually had discovery.

hello @catduckgnaf I’ve just updated to latest version and have an error while starting :frowning:


s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Starting rtl_433 with MQTT option using rtl_433.conf
rtl_433 version 23.11-99-g9448d429 branch master at 202403301828 inputs file rtl_tcp RTL-SDR
MQTT: Publishing MQTT data to core-mosquitto port 1883
MQTT: Publishing device info to MQTT topic "rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id]".
MQTT: Publishing events info to MQTT topic "rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id]".
MQTT: Publishing states info to MQTT topic "rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id]/states".
		= Output format option =
  [-F log|kv|json|csv|mqtt|influx|syslog|trigger|null] Produce decoded output in given format.
	Without this option the default is LOG and KV output. Use "-F null" to remove the default.
	Append output to file with :<filename> (e.g. -F csv:log.csv), defaults to stdout.
	Specify MQTT server with e.g. -F mqtt://localhost:1883
	Add MQTT options with e.g. -F "mqtt://host:1883,opt=arg"
	MQTT options are: user=foo, pass=bar, retain[=0|1], <format>[=topic]
	Default user and password are read from MQTT_USERNAME and MQTT_PASSWORD env vars.
	A base topic can be set with base=<topic>, default is "rtl_433/HOSTNAME".
	Supported MQTT formats: (default is all)
	  events: posts JSON event data
	  states: posts JSON state data
	  devices: posts device and sensor info in nested topics
	Any topic string overrides the base topic and will expand keys like [/model]
	E.g. -F "mqtt://localhost:1883,user=USERNAME,pass=PASSWORD,retain=0,devices=rtl_433[/id]"
rtl_433: option requires an argument: F
	With MQTT each rtl_433 instance needs a distinct driver selection. The MQTT Client-ID is computed from the driver string.
	If you use multiple RTL-SDR, perhaps set a serial and select by that (helps not to get the wrong antenna).
	Specify InfluxDB 2.0 server with e.g. -F "influx://localhost:9999/api/v2/write?org=<org>&bucket=<bucket>,token=<authtoken>"
	Specify InfluxDB 1.x server with e.g. -F "influx://localhost:8086/write?db=<db>&p=<password>&u=<user>"
	  Additional parameter -M time:unix:usec:utc for correct timestamps in InfluxDB recommended
	Specify host/port for syslog with e.g. -F syslog:127.0.0.1:1514

Look like add on on every start overwrites my config file with default :frowning:

I am so sorry, it is not supposed to do that. I’m going to test a fix right now and push