Issues with setting up rtl_433(next) and rtl_433 Auto discovery (next)

Configuration
1

I have installed these two add-ons and am succesfully receiving data from my oil sensors which i can see in MQTT Explorer and am displaying on my dashboard. This is without any specific configuration in the options section of the rtl_433 (next add-on)

rtl_433 (next)
rtl_433 (next)1593×520 33 KB

in the rtl_433 autodiscovery (next) addon, i have my mqtt date as follows:
rtl_433 MQTT Autodiscovery (next)
rtl_433 MQTT Autodiscovery (next)1531×666 82 KB

If, within the rtl_433 (next) add-on, i change the entry as follows:

rtl_433_conf_file: ""
retain: true
frequency: 433.92M, 433.905M, 431.837M, 868.30M, 868.268M -s 1024k
hop_interval: 20
rtl433_flags: "-vv -F log"

No changes can be seen in the log tab even after restarting. no hopping of frequencies, no added logging data etc.

So it seems to me the add-on is not reading this code for some reason.
In Studio Code Server, i have looked through all teh HA files and see nothing relevant other than the rtl_433 directory which only contains the rtl_433.conf.template file with contents starting with: “this is an empty template file…”

Could anyone help and tell me where i can add options so that:
A) i can see any frequency hopping,debug and scanning data in the log?
B) scan frequency 433.92M (as it is already succesfully doing by default it seems)
plus
frequency 868.30M
frequency 868.268M
I have tried uninstalling the add-on and deleting its data and reinstalling, that made no difference. I have spent a day searching through the forum as well as trying co-pilot (very frustrating) but seem stuck.

Many thanks!

2

I see the problem - frequency and hop_interval and rtl433_flags are not actual config options. Instead there’s a file in /config/rtl_433 you can edit. See the README for more details!

3

Hi Andrew, this is probably an exceedingly dumb question but, in my /433/ folder, I only have one file called “rtl_433.conf.template” and no other files that might be a conf.
Shoudl I create a new file called rtl_433.conf or edit the afore mentioned “rtl_433.conf.template”

Of course I have read the readme but am none the wiser. In my defense :wink: there seem to be otehr posters onthe forum having similar issues. Sadly, I cannot find any examples anywhere where soemone with a similar setup, shows a how to.

Would I simply copy the

retain: true
frequency: 433.92M, 433.905M, 431.837M, 868.30M, 868.268M -s 1024k
hop_interval: 20
rtl433_flags: "-vv -F log"

text into the “rtl_433.conf.template”? Or should i create a rtl_433.conf as the README suggests?

Many thanks!

Jaap

4

You can edit that file directly. It ends in .template to support automatically setting up the MQTT connection information. If it doesn’t end in .template, the addon assumes you know what you’re doing and want to hardcode everything.

Sort of, but not in that format. The rtl_433 file isn’t YAML. There’s a fully documetned example up at rtl_433/conf/rtl_433.example.conf at 9a78a488fa782a3b9f0158cba9cc2174bbeedebe · merbanan/rtl_433 · GitHub.

Hope that helps!

5

I am not one of those people that know what I am doing;)

I have seen the file you link to of corse but taht reffers to rtl_433.conf so confuses me. But ok, if I ignore, i now undertand I shoud edit the rtl_433.conf.template file.

Given it works without any config for devices on 433MHZ (I use autodiscover), do I only remove relevant hash symbols to lines I want to add ?

Looking at the file, I would only unhash and edit line 53 to 61 to add frequencies and hop

and to hopefully see better what is going on in the log:
perhaps the 21-25 to increase verbosity?

For me this does not work, if I add -v on a line for example, i would expect verbose but the log says unknown keyword “-v” throwns awobbly gives me a list of commands and stops

Finally, I assume I ADD #s in front of all the protocals I don’t need. Given mine is already picking up sensors via MQTT and i use them in my dashboard, I guess anything refering to that setup can be ignore.

IN simple terms, I understand what goes in .template ADDS to any settings that are set soewhere else? Would hashing or unhashing then reverse any setting I change?

6

would anyone be able to put the options I want in a format that can go into the template file? Andrew kindly pointed me to the example but it is frying my brain a bit. have been fiddeling for a couple if weeks without success and hate to admit defeat;)
Given it works for 433, all i want to change is that it scans multiple ffrequencies and a hop command.
frequency: 433.92M, 433.905M, 431.837M, 868.30M, 868.268M -s 1024k
hop_interval: 20

Thank you all!

7

You’ve got it!

Right, the flag versions only work if you’re typing them directly at a command line.

The # is a comment marker. Any settings in the example file starting with it are commented out and don’t do anything.

Right - those settings are the defaults rtl_433 uses out of the box (such as setting the frequency to 433mhz). Whatever is in the config file overrides those.

8

i “think” i might be making progress thank to your kind help.

I copied the following into my template file and for the first time, after restarting rtl_433 addon the service does not try to start and then stops but just runs.
"
So at least it is still running. Unfortunately, I have no idea if it is actually doing what I would like it to do.

I copied in the following: (from the “#jmr copied” in onward)

# https://github.com/merbanan/rtl_433/blob/9a78a488fa782a3b9f0158cba9cc2174bbeedebe/conf/rtl_433.example.conf

output mqtt://${host}:${port},user=${username},pass=${password},retain=${retain}

#jmr copied in

# as command line option:
#   [-f <frequency>] [-f...] Receive frequency(s) (default: 433920000 Hz)
# default is "433.92M", other reasonable values are 315M, 345M, 915M and 868M
frequency     433.92M, 868.30M

# as command line option:
#   [-H <seconds>] Hop interval for polling of multiple frequencies (default: 600 seconds)
# default is "600" seconds, only used when multiple frequencies are given
hop_interval  60

#endJMR

My log in the rtl addon:

Starting rtl_433 with rtl_433.conf...
[rtl_433] rtl_433 version 25.02-3-g08899fff branch master at 202503031203 inputs file rtl_tcp RTL-SDR SoapySDR with TLS
[rtl_433] MQTT: Publishing MQTT data to core-mosquitto port 1883
[rtl_433] MQTT: Publishing device info to MQTT topic "rtl_433/9b13b3f4-rtl433-next/devices[/type][/model][/subtype][/channel][/id]".
[rtl_433] MQTT: Publishing events info to MQTT topic "rtl_433/9b13b3f4-rtl433-next/events".
[rtl_433] MQTT: Publishing states info to MQTT topic "rtl_433/9b13b3f4-rtl433-next/states".
[rtl_433] Use "-F log" if you want any messages, warnings, and errors in the console.
[rtl_433] Found Rafael Micro R828D tuner
[rtl_433] RTL-SDR Blog V4 Detected
[rtl_433] Exact sample rate is: 250000.000414 Hz

I now added "verbose"on one line but does not seem to make any difference. at least it is still running.
I have not run it long enough to see if my oil sensors still update (they were catching on 433) - (edit : i think it still does)

Is there anyway I can set something so I can see it is actually scanning & hopping a particular frequency?

Is there anyway to prevent picking up a device (say for example 59 steelmate TPMS) or whatever? (or the opposite when I actually want it?)
In my list I do not have watchman sonic listed but it decodes it anyway. (I happen to want it so that is handy) but I also pick up: Interlogics-Security, Markisol, Cardin-S466 and TPMS renault-0435R. I live in a very rural location and have only 1 close neighbour. (Who does nothave a renault)

Out of interest, where does any information added in the config file go/get written too? I cannot find any file on my HA

9

Add “verbose 7” to your configuration file and restart, and it will log every time it hops frequencies.

10

thanks, tried that but still nothing.
Have changed hop to 60 in order not to have to wait so long. but i see no hopping…(neither in the rtl_433 nor the rtl_433 mqtt auto discover logs).

The section i added in the rtl_433.conf.template is the following:

#jmr copied in
verbose 7
# as command line option:
#   [-f <frequency>] [-f...] Receive frequency(s) (default: 433920000 Hz)
# default is "433.92M", other reasonable values are 315M, 345M, 915M and 868M
frequency     433.92M, 868.30M

# as command line option:
#   [-H <seconds>] Hop interval for polling of multiple frequencies (default: 600 seconds)
# default is "600" seconds, only used when multiple frequencies are given
hop_interval  60

#endJMR

hope someone can point out my error.
Thanks!
11

I assume many are using trl_433 but I do not understand why there is not one example of a working setup file with a hop command to switch between frequencies.
It has so much potential in an HA environment yet so little information for a beginner.

I have tried for weeks without any success, other than on the default 433 MHZ.

Frustrating, still hope someone will publish a copy of their setup template file.
I know the example template and all the documentation that is out there but still zero success.

Many thanks!

Jaap

12

I’m pretty sure this doesn’t take a comma and you need to do each one on it’s own line:

frequency 433.92M
frequency 868.30M

Also, I personally did something like this for 6 months or a year, but I found every few months the radio itself would stop switching frequencies. I ended up buying a second radio instead.

I also noticed this line which I think is new:

Use "-F log" if you want any messages, warnings, and errors in the console.

I needed to add output log to get verbose to work correctly.

13

thanks, that definately did something! haven’t picked anything up on 868 yet but will try teh different frequencies.

IN the meantime, is there any way I can disable looing for specific device protocols. my log is completely spammed. (a very small section below).
Manythanks

Jaap

[rtl_433] RTL-SDR Blog V4 Detected
[rtl_433] SDR: Using device 0: RTLSDRBlog, Blog V4, SN: 00000001, "Generic RTL2832U OEM"
[rtl_433] Exact sample rate is: 1000000.026491 Hz
[rtl_433] SDR: Sample rate set to 1000000 S/s.
[rtl_433] Input: Bit detection level set to 0.0 (Auto).
[rtl_433] SDR: Tuner gain set to Auto.
[rtl_433] Input: Reading samples in async mode...
[rtl_433] SDR: rtlsdr_set_center_freq 433920000 = 0
[rtl_433] SDR: Tuned to 433.920MHz.
[rtl_433] acquire_thread: acquire_thread enter...
[rtl_433] MQTT: MQTT Connected...
[rtl_433] Baseband: low pass filter for 1000000 Hz at cutoff 100000 Hz, 10.0 us
[rtl_433] calibeur_rf104_decode: DECODE_FAIL_SANITY data all 0x00 or 0xFF
[rtl_433] pulse_slicer_osv1: preamble 1  857 10001
[rtl_433] radiohead_ask_extract: preamble not found
[rtl_433] philips_aj3650_decode: wrong number of bits (1)
[rtl_433] radiohead_ask_extract: preamble not found
[rtl_433] ttx201_decode: Short preamble: 2 bits (expected 17)
[rtl_433] ecowitt_decode: Preamble not found
[rtl_433] norgo_decode: wrong size of bit per row 1
[rtl_433] pulse_slicer_pcm: Security+ (Keyfob) codes [{22}c00000]
[rtl_433] markisol_decode: bits_per_row[0] = 1
[rtl_433] rainpoint_decode: bit_per_row 5 out of range
[rtl_433] jasco_decode: invalid bit count 10
[rtl_433] regency_fan_decode: Expected 21 bits, got 1.
[rtl_433] emos_e6016_decode: Repeated row fail
[rtl_433] emos_e6016_rain_decode: Repeated row fail
[rtl_433] pulse_slicer_pcm: Neptune R900 flow meters codes [{39}fffffff800]
[rtl_433] watts_thermostat_decode: Preamble not found
[rtl_433] rosstech_dcu706_decode: bit_per_row 14 out of range
[rtl_433] risco_agility_decode: Preamble not found
[rtl_433] MQTT: MQTT Connection established.
[rtl_433] SDR: rtlsdr_set_center_freq 868300000 = 0
[rtl_433] SDR: Tuned to 868.300MHz.
[rtl_433] pulse_slicer_pwm: Efergy e2 classic codes [{48}ffffffffffff]
[rtl_433] pulse_slicer_pcm: emonTx OpenEnergyMonitor: Exact bit width (in us) is 20.00 vs 20.00, 47 bit measured
[rtl_433] pulse_slicer_pcm: emonTx OpenEnergyMonitor codes [{267}a5555555a6b4a8d6820a9514a5aaa8000000000146522cc88a5000000000018aac6]
[rtl_433] pulse_slicer_manchester_zerobit: Steelmate TPMS codes [{20}70a04]
[rtl_433] pulse_slicer_pwm: Efergy Optical codes [{48}ffffffffffff]
[rtl_433] pulse_slicer_pcm: LaCrosse TX35DTH-IT, TFA Dostmann 30.3155 Temperature/Humidity sensor codes [{20}00000]
[rtl_433] pulse_slicer_pcm: LaCrosse TX29IT, TFA Dostmann 30.3159.IT Temperature sensor codes [{63}b30080004500000a]
[rtl_433] fineoffset_WH0290_callback: short package. Row length: 62. Header index: 86 codes [{62}b30080008a000014]
[rtl_433] pulse_slicer_pcm: Fine Offset Electronics, WH25, WH32, WH32B, WN32B, WH24, WH65B, HP1000, Misol WS2320 Temperature/Humidity/Pressure Sensor codes [{62}b30080008a000014]
[rtl_433] pulse_slicer_pcm: GE Color Effects codes [{25}b300800]
[rtl_433] pulse_slicer_pcm: GE Color Effects codes [{20}45000]
[rtl_433] pulse_slicer_pcm: Exact bit width (in us) is 10.07 vs 10.00, 28 bit preamble
[rtl_433] pulse_slicer_pcm: Wireless M-Bus, Mode C&T, 100kbps (-f 868.95M -s 1200k) codes [{214}aaaaaaad391d3912c1d7401003331240d0d172b4b0000000000000]
[rtl_433] pulse_slicer_pcm: Wireless M-Bus, Mode C&T, 100kbps (-f 868.95M -s 1200k) codes [{125}a0f1a181387860c14260000000000000]
[rtl_433] pulse_slicer_pcm: Wireless M-Bus, Mode C&T, 100kbps (-f 868.95M -s 1200k) codes [{31}a0caba1e]
[rtl_433] pulse_slicer_pcm: Wireless M-Bus, Mode S, 32.768kbps (-f 868.3M -s 1000k) codes [{50}a51302a0aa800]
[rtl_433] pulse_slicer_pcm: Wireless M-Bus, Mode S, 32.768kbps (-f 868.3M -s 1000k) codes [{32}2a2a4200]
[rtl_433] pulse_slicer_pcm: Ambient Weather WH31E Thermo-Hygrometer Sensor, EcoWitt WH40 rain gauge, WS68 weather station codes [{63}b30080004500000a]
[rtl_433] pulse_slicer_pwm: Honeywell ActivLink, Wireless Doorbell (FSK) codes [{48}ffffffffffff]
[rtl_433] bresser_5in1_decode: bit_per_row 16 out of range
[rtl_433] directv_decode: incorrect number of bits in bitbuffer: 2 (expected between 
[rtl_433] pulse_slicer_pcm: IKEA Sparsnas Energy Meter Monitor: Exact bit width (in us) is 28.15 vs 27.00, 27 bit measured
[rtl_433] ikea_sparsnas_decode: Too short or too long packet received. Expected 160, receiv codes [{131}a5130150554000000054548400000002a]
[rtl_433] pulse_slicer_pcm: IKEA Sparsnas Energy Meter Monitor codes [{131}a5130150554000000054548400000002a]
[rtl_433] pulse_slicer_pcm: AOK Weather Station rebrand Holman Industries iWeather WS5029, Conrad AOK-5056, Optex 990018 codes [{26}0000000]
[rtl_433] pulse_slicer_pcm: ESIC EMT7110 power meter codes [{20}00000]
[rtl_433] pulse_slicer_pcm: Fine Offset Electronics/ECOWITT WH51, SwitchDoc Labs SM23 Soil Moisture Sensor codes [{62}b30080008a000014]
[rtl_433] pulse_slicer_pwm: Holman Industries iWeather WS5029 weather station (older PWM) codes [{72}ffffffffffffffffff]
[rtl_433] fineoffset_wh1080_callback: short package. Header index: 86 codes [{62}b30080008a000014]
[rtl_433] pulse_slicer_pcm: Fine Offset Electronics WH1080/WH3080 Weather Station (FSK) codes [{62}b30080008a000014]
[rtl_433] pulse_slicer_pwm: Sharp SPC775 weather station codes [{72}000000000000000000]
[rtl_433] insteon_callback: new buffer 3 rows
[rtl_433] lacrosse_breezepro_decode: Wrong packet length: 20
[rtl_433] pulse_slicer_pcm: LaCrosse Technology View LTV-WSDTH01 Breeze Pro Wind Sensor codes [{20}00000]
[rtl_433] lacrosse_wr1_decode: Packet too short: 20 bits
[rtl_433] pulse_slicer_pcm: LaCrosse Technology View LTV-WR1 Multi Sensor codes [{20}00000]
[rtl_433] lacrosse_th_decode: Packet too short: 20 bits
[rtl_433] pulse_slicer_pcm: LaCrosse Technology View LTV-TH Thermo/Hygro Sensor codes [{20}00000]
[rtl_433] bresser_6in1_decode: bit_per_row 16 out of range
[rtl_433] bresser_7in1_decode: to few bits (16)
[rtl_433] ecodhome_decode: to few bits (6)
[rtl_433] lacrosse_r1_decode: Packet too short: 20 bits
[rtl_433] pulse_slicer_pcm: LaCrosse Technology View LTV-R1, LTV-R3 Rainfall Gauge, LTV-W1/W2 Wind Sensor codes [{20}00000]
[rtl_433] pulse_slicer_pcm: TFA Marbella Pool Thermometer codes [{20}00000]
[rtl_433] pulse_slicer_pcm: Honeywell CM921 Wireless Programmable Room Thermostat: Exact bit width (in us) is 27.83 vs 26.00, 23 bit measured
[rtl_433] honeywell_cm921_decode:  codes {133}a513015055400000002a2a4200000000a8
[rtl_433] honeywell_cm921_decode: preamble_start=133 start=163 len=-30
[rtl_433] pulse_slicer_pcm: Honeywell CM921 Wireless Programmable Room Thermostat codes [{133}a513015055400000002a2a4200000000a8]
[rtl_433] pulse_slicer_pcm: RojaFlex shutter and remote devices codes [{26}0000000]
[rtl_433] pulse_slicer_pcm: Somfy io-homecontrol: Exact bit width (in us) is 23.46 vs 26.00, 52 bit measured
[rtl_433] pulse_slicer_pcm: Somfy io-homecontrol codes [{56}a51300a812a800]
14

now changed verbose to 6 which as a one off list protocols registers (the lot) and then gives less verbal, showing working hopping. Not picking up the iBoosts yet though (i have 2).

Will update if it turns out i get lucky.

Still gives me some log entries which are meaningless to me:

rtl_433] Registering protocol [271] "Landis & Gyr Gridstream Power Meters 9.6k"
[rtl_433] Registering protocol [272] "Landis & Gyr Gridstream Power Meters 19.2k"
[rtl_433] Registering protocol [273] "Landis & Gyr Gridstream Power Meters 38.4k"
[rtl_433] Registering protocol [274] "Revolt ZX-7717 power meter"
[rtl_433] Registering protocol [275] "GM-Aftermarket TPMS"
[rtl_433] SDR: trying device 0: RTLSDRBlog, Blog V4, SN: 00000001
[rtl_433] Found Rafael Micro R828D tuner
[rtl_433] RTL-SDR Blog V4 Detected
[rtl_433] Exact sample rate is: 1000000.026491 Hz
[rtl_433] SDR: Using device 0: RTLSDRBlog, Blog V4, SN: 00000001, "Generic RTL2832U OEM"
[rtl_433] SDR: Sample rate set to 1000000 S/s.
[rtl_433] Input: Bit detection level set to 0.0 (Auto).
[rtl_433] SDR: Tuner gain set to Auto.
[rtl_433] Input: Reading samples in async mode...
**[rtl_433] SDR: Tuned to 433.920MHz.**
[rtl_433] MQTT: MQTT Connected...
[rtl_433] Baseband: low pass filter for 1000000 Hz at cutoff 100000 Hz, 10.0 us
[rtl_433] norgo_decode: wrong size of bit per row 1
[rtl_433] markisol_decode: bits_per_row[0] = 1
[rtl_433] risco_agility_decode: Preamble not found
[rtl_433] MQTT: MQTT Connection established.
[rtl_433] markisol_decode: bits_per_row[0] = 1
[rtl_433] risco_agility_decode: Preamble not found
**[rtl_433] SDR: Tuned to 868.000MHz.**
[rtl_433] fineoffset_WH0290_callback: short package. Row length: 66. Header index: 90 codes [{66}b3020200004000010]
[rtl_433] fineoffset_wh1080_callback: short package. Header index: 90 codes [{66}b3020200004000010]
[rtl_433] lacrosse_breezepro_decode: Wrong packet length: 21
[rtl_433] lacrosse_wr1_decode: Packet too short: 22 bits
[rtl_433] lacrosse_th_decode: Packet too short: 22 bits
[rtl_433] lacrosse_r1_decode: Packet too short: 22 bits
[rtl_433] honeywell_cm921_decode:  codes {136}a5130029220800000008a00c8000000022
[rtl_433] honeywell_cm921_decode: preamble_start=136 start=166 len=-30
[rtl_433] thermopro_tp28b_decode: Packet too short: 22 bits

Not sure what all the stuff there is, except where it seems to cycle through all the protocols (I would rather turn them all -except iBoost on 188 and perhaps 1 other-off-no idea how yet)

The entries in my config now are:

#jmr copied in
output log
verbose 6
# as command line option:
#   [-f <frequency>] [-f...] Receive frequency(s) (default: 433920000 Hz)
# default is "433.92M", other reasonable values are 315M, 345M, 915M and 868M
frequency 433.92M
frequency 868M
frequency 868.30M
frequency 686.268M

# as command line option:
#   [-H <seconds>] Hop interval for polling of multiple frequencies (default: 600 seconds)
# default is "600" seconds, only used when multiple frequencies are given
hop_interval  300

#endJMR
15

If you look for protocol in the full example file, you’ll see options both to enable specific ones or disable them. You can also just remove the verbose line when you’re happy with things and all of those other messages will stop.