But you have specified 315MHz in the config, not 433.92MHz. You can use hop interval if you want data from multiple frequencies.
Frequency hopping is my plan, but I was temporarily only trying to see stuff in the 315M range. But I was assuming that the log in the RTL433 add on would say tuned to 315M or something. When I was looking around at other people’s stuff, their log would say what they were tuned too
So I am using this as a addon in HA and I cannot see a way to pin a specific release in the add on. Google wasn’t much help. Am i missing something or do I need to just spin this up in its own docker container?
I don’t know much about this RTL stuff, but I have a Nooelec Mini plugged into a USB extension that’s directly connected to the second USB port on my HA Green. All I did was install the RTL 433 (Next) Addon and MQTT explorer to see what it was picking up. The only line of code I added to the config file it creates was the output line with my user name and password. Couple posts up you can see what I have. I then used MQTT Auto discovery add on to bring the temp sensors I was looking for into HA. Once I found them in my under my MQTT integration I deleted all the other random devices that auto discovery found and stopped the auto discovery addon and turned off the start on boot.
You can skip the MQTT auto discovery but I didn’t want play around with creating the individual devices in MQTT. Seemed easier to me to just delete all the devices that weren’t mine
That’s basically all I know. I can’t seem figure out how change frequency’s for it to listen too or if I’m doing it right it don’t get any confirmation in the log
this works great for auto discovery.
Unfortunately this is a bit limited in Home Assistant: Add the possibility to install a previous release of an addon - #6 by jmcollin
If you simply want to stay at your current version, then make sure automatic updates are off (they are by default).
Another possibility would be to make a backup of the addon, download it, extract and edit it to point to the older version, and then restore it. I have a vague recollection of doing this in the past, but clearly YMMV!
One final option would be to clone the addon locally and treat it as if you’re developing on it. Then you can change it as you see fit to update the config file to use an older tag.
Is this any different than the RTL 433 MQTT Auto Discovery add on other than it lets you choose what to send to HA, where as the former just pulls all RTL433 MQTT topics?
Not really different no. The ability to pick and choose is nice.
This is catduckgnaf discovery script.wrapped up in a home assistant addon,
Working for me.
If you want to try it out you just need to have rtl_433 running somewhere.
Install the addon.
Fill in your mqtt info.
It is discovering all devices by default but there is a field for ID
enter multiple ids with a space. ie: 76410004 87 0 154491068
Get the ID from mqttexplorer. or the rtl_433 log
Am I reading the update change log correct? 0.5.2 now supports the v4?
Yes! It’s been in the next branch for a while with no issues, and I rolled a new stable tag today.
1 Like
I am running into difficulty specifying a specific decoder from within the config file.
I successfully capture the packets, but the raw data is returned non-decoded. The instructions for the specific project state the following for RTL_433 on the command line, but I’m not sure I’ve formatted it correctly in the HA Add On config file.
rtl_433 -R 0 -f 868.298M -X 'n=Marlec,m=FSK_PCM,s=10,l=10,g=1000,r=2000,preamble=aad391d391'
My HA RTL_433 config file is:
output mqtt://${host}:${port},user=${username},pass=${password},retain=${retain}
report_meta time:iso:usec:tz
frequency 868.3M
output kv
decoder n=Marlec,m=FSK_PCM,s=10,l=10,g=1000,r=2000,preamble=aad391d391
protocol 188
Can anyone see what I am doing wrong?
Thanks for any pointers!
Are you implementing a brand new protocol, or one that is already supported? If it’s one that rtl_433 knows about, you just need the protocol number. If you are implementing a new decoder, you need the decoder line.
It’s a lot faster to test and debug new decoders outside of home assistant, so I’d suggest installing rtl_433 on your normal computer and working there until you get a working decoder line.
Pulling my hair out, please help to save my good looks 
6-12 months ago Home Assistant / RTL_433 stopped picking up my Bresser 7in1 weather station. Today I tried to troubleshoot the issue.
On my Pop_OS desktop PC, everything is fine:
When I then connect the radio to Home Assistant OS (NUC) again, the logs of the RTL_433 add-on do not show anything being detected:
This is the config:
frequency 868M
protocol 173
# pulse_detect auto
# sample_rate 1M
# gain 25
convert si
report_meta time:iso:tz:local
output kv
# output json
How can I troubleshoot this further? I am at a loss right now.
Is there any chance the protocol number somehow changed? I see it in your HA config file but not in the command line on your desktop.
Also, rtl_433 on your desktop is quite old (2021!), so it’s possible there’s been a regression since then. Could you try 23.11 or newer on your PC, to match what’s in Home Assistant?
It may also be worth browsing through the issues upstream at https://github.com/search?q=repo%3Amerbanan%2Frtl_433+bresser&type=issues in case others have noticed anything.
Thanks for the advice! I verified some more, unfortunately not a fix yet.
- I tried the newer rtl_433 version 23.11 on my desktop with the same result: the Bresser weather station is getting picked on the desktop perfectly.
- Confirmed there that protocol 173 is still the correct one.
- Checked out the issues upstream, but found nothing relevant.
I think I should now focus on the difference between PC (with PopOS/Ubuntu) and NUC (with HA-OS). Do you have any advice how I could further pinpoint the issue? Thanks in advance!
I’ve tried to get a friends Bresser 7 in 1 station to pick up with the Fitipower FC0012 tuner, but even if I got a some reading the tuner would stop reporting after couple of hours. The tuner worked fine with 433 signal, but with 868 it had troubles. The we tried a different tuner the Nooelec RTL-SDR v5 SDR and it worked great with this set up:
frequency 868.3M
verbose 7
gain 0
protocol 173 # Bresser Weather Center 7-in-1
convert si
output kv
report_meta level
#report_meta noise
report_meta stats
report_meta time:usec
report_meta protocol
pulse_detect minlevel=-36
pulse_detect magest
sample_rate 250k
There is also an option to set up the station to send data to your own web server (this depends on the firmware, the newer station do not have this option), you can try this to send data to NodeRED and then to HA. If you want I can help you with this. It is all local and uses your local wifi to get data from the station to Home Assistant.
Thanks @DominikW for your suggestions.
For now, I will try to connect the Fitipower to a Raspberry Pi 3 I have lying around. Perhaps that works.
Sending data to my own webserver/NodeRed is not really a preferred option because I would like to not use the Bresser display/server. RTL-433 has served me well for several years. If RPI3 doesn´t work out, I will check out the RTL-SDR v5. Thanks!
I am using the rtl_433 add on in home assistant. Something weird and I am hoping someone can answer
If I have the hop interval specified like the below then the device which is on 319.5 gets detected
# Uncomment the following line to also enable the default "table" output to the
# addon logs.
output kv
hop_interval 60
frequency 433.92M
frequency 319.5M
However if I remove the hop interval no device gets detected
# Uncomment the following line to also enable the default "table" output to the
# addon logs.
output kv
frequency 319.5M
Any help would be appreciated
not sure what i am doing wrong but I am having no luck getting to discovery to find my Acurite-5n1 but it shows in the log for rtl433 any tips on what I might be missing?