unable to get RTL_433 to MQTT Bridge to work with HAssio

[tonyfitzs]

Hi there, I have spent many hours trying to get this to work with no success. I have installed the RTL_433 to MQTT Bridge as per the instructions, when I attempt to get it to start I am getting the following log message
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Starting RTL_433 with parameters:
MQTT Host = 10.110.10.5
MQTT User = mqtty
MQTT Password = *******
MQTT Topic = homeassistant/sensor/currentcost
RTL_433 Protocol = 100
RTL_433 Frequency = 433
RTL_433 Gain = 30
RTL_433 Frequency Offset = 350
rtl_433 version 20.02-145-gb091ab6 branch master at 202009071341 inputs file rtl_tcp RTL-SDR
Use -h for usage help and see https://triq.org/ for documentation.
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"...
Registered 1 out of 166 device decoding protocols [ 100 ]
No supported devices found.
[cmd] /bin/ash exited 0
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

Based on the above I can see that RTL_433 is unable to find the device as indicated by the highlighted text. When I run lsmod in a terminal session initially I can see both dvb_usb_rtl28xxu and dvb_usb_v2. This tells me that the device is at lease connected and recognized by the underlying operating system.
I issue the command sudo rmmod dvb_usb_rtl28xxu rtl2832 dvb_usb_v2 to un-block the SDR and run lsmod again and I can see these entries are now removed however I still get the same log output as above.

The log below is after running lsmod post rmmod. One issue which is a side issue for the moment is I am not able to persist changes or blacklist the dvb_usb_rtl28xxu etc, I can update the blacklist-rtl.conf but it doesn’t appear to have an effect, most likely because the file I am editing is not within the docker structure (my Linux and Docker skills are pretty average)

Module Size Used by Tainted: G
rfcomm 53248 4
nf_conntrack_netlink 40960 0
nfnetlink 16384 2 nf_conntrack_netlink
xfrm_user 36864 1
xfrm_algo 16384 1 xfrm_user
aes_arm_bs 20480 0
crypto_simd 16384 1 aes_arm_bs
cryptd 24576 1 crypto_simd
algif_skcipher 16384 0
af_alg 28672 1 algif_skcipher
bnep 20480 2
hci_uart 40960 1
btbcm 16384 1 hci_uart
serdev 20480 1 hci_uart
bluetooth 397312 31 rfcomm,bnep,hci_uart,btbcm
ecdh_generic 28672 1 bluetooth
sch_fq_codel 20480 7
evdev 24576 0
brcmfmac 319488 0
brcmutil 20480 1 brcmfmac
cfg80211 655360 1 brcmfmac
bcm2835_codec 36864 0
v4l2_mem2mem 24576 1 bcm2835_codec
rfkill 28672 4 bluetooth,cfg80211
bcm2835_v4l2 49152 0
bcm2835_mmal_vchiq 32768 2 bcm2835_codec,bcm2835_v4l2
videobuf2_vmalloc 16384 1 bcm2835_v4l2
videobuf2_dma_contig 20480 1 bcm2835_codec
videobuf2_memops 16384 2 videobuf2_vmalloc,videobuf2_dma_contig
videobuf2_v4l2 24576 3 bcm2835_codec,v4l2_mem2mem,bcm2835_v4l2
vc_sm_cma 36864 1 bcm2835_mmal_vchiq
videobuf2_common 45056 4 bcm2835_codec,v4l2_mem2mem,bcm2835_v4l2,videobuf2_v4l2
rpivid_mem 16384 0
snd_bcm2835 28672 4
snd_pcm 102400 2 snd_bcm2835
snd_timer 32768 2 snd_pcm
snd 77824 9 snd_bcm2835,snd_pcm,snd_timer
r820t 28672 0
raspberrypi_hwmon 16384 0
hwmon 16384 1 raspberrypi_hwmon
i2c_mux 16384 0
uio_pdrv_genirq 16384 0
uio 20480 1 uio_pdrv_genirq

So in an effort to prove that there is nothing wrong with the hardware, I have also run things up on a second Raspberry pi running Raspbian. I am able to successfully get rtl_433 working and publishing my MQTT server, however this is not ideal as I have other uses for the raspberry Pi I am using and would prefer to have it self contained in the Home Assistant environment.

I have also used the SD card that I created for my second Raspberry Pi after successfully getting rtl_433 working in the same hardware as I am using for Home Assistant. And can confirm that there are no issues with it working with the Home assistant hardware, so the issue defiantly appears to be within the home assistant software configuration its self.

As stated, I am not strong with Linux, so if its something obvious to you, its not obvious to me.
Thanks in advance.

[JakubJaszczur]

Another question, how to set listening of all protocols?