pbkhrv / rtl_433-hass-addons Goto Github PK

View Code? Open in Web Editor NEW

214.0 16.0 101.0 403 KB

Collection of Home Assistant add-ons that use rtl_433

Dockerfile 17.24% Shell 82.76%

home-assistant rtl-433 sdr home-assistant-addons

rtl_433-hass-addons's Introduction

rtl_433 Home Assistant add-ons

This is a collection of Home Assistant add-ons that work with rtl_433.

How to add this add-on repository to your Home Assistant install
Use https://github.com/pbkhrv/rtl_433-hass-addons as the URL for the repository.

Running the Development Version

First, follow the tutorial at Tutorial: Making your first add-on to learn how to build a basic addon.
Use git to clone this repository same addons folder used in the tutorial.
Make changes to the code, or use git to checkout branches to test.
Remember to to reload and reinstall the addon to rebuild the Docker containers to see any changes.

Release Process

The next branch represents the upcoming version of these addons.
rtl_433/config.json and rtl_433_mqtt_autodiscovery/config.json will contain the version numbers of the previously set addon versions, but will have different code.
When next is ready to be tagged for a release:
1. Create a pull request against main, bumping the versions of each config.json file if the individual addon has been changed. As well, update the CHANGELOG.md in the same pull request.
2. When the pull request has been approved, create a date-based tag such as 2022.12.01.0 on the last commit of the pull request. This will build docker containers with the version numbers in config.json.
3. Merge the PR into main to actually promote the release to end users. Note the new version(s) in the commit message.
- Note we do not tag main in git, since each addon has it's own version number.
1. Create a new branch off of main setting the addon versions back to next. Create a PR to merge main into next to reconcile the branches.

rtl_433-hass-addons's People

Contributors

Stargazers

Watchers

Forkers

junster1 wauswaus gregkolod arbal srsgit bigwebstas georgeioak bitfliq deviantintegral bartrumb blitt001 jarguel kgwhitmer daemongloom shbatm kdknigga seanstar12 mblocker henriblancke matteob99 ecylcje epalmans packetwarrior stmcdonl hertzg kdeyev pchaves1 jordanduffybd grinco otnow oesvends edenhome glendower hoffi848 rfam13 tjcav sdt16 dfrazao mcjamesloon scottroach jaseelye mssmison mikewadsten d-rock6689 dscao nisdac nightwolfgroup szala1981 iserloh sean1983 err53 sg1888 peddamat onceking bmorton ryanad joanwa mdouailin jongilmore airdrummingfool mbartosik0 3v1n0 pgwipeout qviper dragulceo unverbraucht baronhoot mholgatem geoffreys lumascet evolseven carmeanw ministorm3 cserem tomkusz mbucknel lmilius maciejgornicz anienhuis benklop catduckgnaf ewintec chn110 chrisromp binarydev aaltalmas exelsis423 jochakovsky hindsight2021 jaroslawp joshpearce carsten9 jayekub teosoft123 dominic7 sbcwsgit tds04

rtl_433-hass-addons's Issues

Docker build not working on fresh pull

Hello,

I've been trying to build the rtl_433 addon in and out of HASS without success. In both case, it throws the same error.

Fresh checkout from the repo.

On Armbian 20.04, aarch64.

~/dev/rtl_433-hass-addons/rtl_433$ docker build --build-arg BUILD_FROM="homeassistant/aarch64-base:latest" -t local/rtl_433 ./
Sending build context to Docker daemon  29.18kB
Step 1/25 : ARG BUILD_FROM
Step 2/25 : FROM $BUILD_FROM as builder
 ---> d5dbda55fa00
Step 3/25 : MAINTAINER [email protected]
 ---> Running in 3cab7f656427
Removing intermediate container 3cab7f656427
 ---> af851342c5f2
Step 4/25 : ENV LANG C.UTF-8
 ---> Running in 747e048623da
Removing intermediate container 747e048623da
 ---> 5764a970280a
Step 5/25 : RUN apk add --no-cache --virtual .buildDeps     build-base     libusb-dev     librtlsdr-dev     cmake     git
 ---> Running in 7b1d80f6135f
fetch https://dl-cdn.alpinelinux.org/alpine/v3.14/main/aarch64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.14/community/aarch64/APKINDEX.tar.gz
(1/36) Installing libgcc (10.3.1_git20210424-r2)
(2/36) Installing libstdc++ (10.3.1_git20210424-r2)
(3/36) Installing binutils (2.35.2-r2)
(4/36) Installing libmagic (5.40-r1)
(5/36) Installing file (5.40-r1)
(6/36) Installing libgomp (10.3.1_git20210424-r2)
(7/36) Installing libatomic (10.3.1_git20210424-r2)
(8/36) Installing libgphobos (10.3.1_git20210424-r2)
(9/36) Installing gmp (6.2.1-r0)
(10/36) Installing isl22 (0.22-r0)
(11/36) Installing mpfr4 (4.1.0-r0)
(12/36) Installing mpc1 (1.2.1-r0)
(13/36) Installing gcc (10.3.1_git20210424-r2)
(14/36) Installing musl-dev (1.2.2-r3)
(15/36) Installing libc-dev (0.7.2-r3)
(16/36) Installing g++ (10.3.1_git20210424-r2)
(17/36) Installing make (4.3-r0)
(18/36) Installing fortify-headers (1.1-r1)
(19/36) Installing patch (2.7.6-r7)
(20/36) Installing build-base (0.5-r2)
(21/36) Installing libusb (1.0.24-r2)
(22/36) Installing pkgconf (1.7.4-r0)
(23/36) Installing libusb-dev (1.0.24-r2)
(24/36) Installing librtlsdr (0.6.0-r1)
(25/36) Installing librtlsdr-dev (0.6.0-r1)
(26/36) Installing libacl (2.2.53-r0)
(27/36) Installing libbz2 (1.0.8-r1)
(28/36) Installing expat (2.4.4-r0)
(29/36) Installing lz4-libs (1.9.3-r1)
(30/36) Installing zstd-libs (1.4.9-r1)
(31/36) Installing libarchive (3.5.2-r0)
(32/36) Installing rhash-libs (1.4.1-r0)
(33/36) Installing cmake (3.20.3-r0)
(34/36) Installing pcre2 (10.36-r0)
(35/36) Installing git (2.32.0-r0)
(36/36) Installing .buildDeps (20220204.215013)
Executing busybox-1.33.1-r6.trigger
OK: 270 MiB in 75 packages
Removing intermediate container 7b1d80f6135f
 ---> 2f08f9bac0ef
Step 6/25 : WORKDIR /build
 ---> Running in d3c6fd93084c
Removing intermediate container d3c6fd93084c
 ---> d9b9a8eaa928
Step 7/25 : RUN git clone https://github.com/merbanan/rtl_433
 ---> Running in 64525d8740d8
Cloning into 'rtl_433'...
Removing intermediate container 64525d8740d8
 ---> ed539ccc01a4
Step 8/25 : WORKDIR ./rtl_433
 ---> Running in 7e01892f74b4
Removing intermediate container 7e01892f74b4
 ---> cd5df8456e82
Step 9/25 : ARG rtl433GitRevision=21.12
 ---> Running in 2e26f4dce95f
Removing intermediate container 2e26f4dce95f
 ---> 6bb59c3cba0d
Step 10/25 : RUN git checkout ${rtl433GitRevision}
 ---> Running in 1bb9239c5dfb
Note: switching to '21.12'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 5e44ab3e build: Add workflow_dispatch to Release action
Removing intermediate container 1bb9239c5dfb
 ---> 1a57f0610eb7
Step 11/25 : WORKDIR ./build
 ---> Running in 67e0c7da6efe
Removing intermediate container 67e0c7da6efe
 ---> 7e8937398c8b
Step 12/25 : RUN cmake ..
 ---> Running in e377e3dc8c47
CMake Deprecation Warning at CMakeLists.txt:4 (cmake_minimum_required):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.


-- The C compiler identification is GNU 10.3.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc - broken
CMake Error at /usr/share/cmake/Modules/CMakeTestCCompiler.cmake:66 (message):
  The C compiler

    "/usr/bin/cc"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: /build/rtl_433/build/CMakeFiles/CMakeTmp

    Run Build Command(s):/usr/bin/make -f Makefile cmTC_0a904/fast && /usr/bin/make  -f CMakeFiles/cmTC_0a904.dir/build.make CMakeFiles/cmTC_0a904.dir/build
    make: /usr/bin/make: Operation not permitted
    make: *** [Makefile:127: cmTC_0a904/fast] Error 127





  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:14 (project)


-- Configuring incomplete, errors occurred!
See also "/build/rtl_433/build/CMakeFiles/CMakeOutput.log".
See also "/build/rtl_433/build/CMakeFiles/CMakeError.log".
The command '/bin/ash -o pipefail -c cmake ..' returned a non-zero code: 1

I've tried to completely remove any prior install of this addon, purge any docker image related to it. It never seems to work. It always throw this error.

I am able to successfully compile rtl_433 on the same machine.

Causes HA to hard crash

First, when I installed this, I was so tthankful. It is everything I was hoping for.

After several weeks of running this on the HAOS with a SSD, with a NESDR Mini 2+, I have found it has been making my home assistant unstable. The system will hard crash making it non-responsive to ethernet traffic. I cannot ssh into the device, it does not respond to pings, and sniffing traffic on the router port shows traffic being sent, but not responses. It even loses its IP address. A true hard crash that can only be recovered with a restart.

After restart, it will last for hours or up to two days.

I pulled the NESDR, ran tests on it, and it appears fine. I left it out for over a week, uninstalled rtl_433 and the auto-discovery add-on and did not have a single crash the entire duration. HA worked normally.

Given the way logs clear, I am unable to see what happens. But, I do log device temperature, CPU use, and hard drive utilization. These three look normal.

What can I do to debug/capture information that I could send to you that might help determine what is going on? Keep in mind, this is HA on a Raspberry Pi 4, with 4G RAM, that is running the HAOS, so I am looking for a native solution.

Thanks!!!

Auto discovery, add retain flag ?

Can the autodiscovery addon be updated to provide a config value to set the retain flag ? The python script has a parameter available, but its currently not configurable from the addon config.

parser.add_argument("-r", "--retain", action="store_true")

Just plugged in and spun up both addons tonight and they worked fantastic right out of the box. Thanks for the work to get this packaged into an addon... saved me all sorts of headaches!

Auto-discovery script uses invalid device_class "weather" for some devices

Upstream at rtl_433/examples/rtl_433_mqtt_hass.py uses "weather" as device_class in some places. There is an outstanding PR to fix that, but that's stuck behind some other PR etc etc. Temporarily pointing Dockerfile here to my own fork of rtl_433 with that script fixed. Will point back to upstream when merged there. Keeping this issue open until then.

Bug: Logging gets truncated

In trying to diagnose the problems in #23 on my Raspberry Pi, I noticed that the Log output provided in the Home Assistant UI was initially truncated and didn't show what the full startup messaging looks like.

For example, if I run the following command in HAOS Root:

docker run --device /dev/bus/usb/001/003 hertzg/rtl_433:debian -f 915M

... the initial console output looks like this:

# docker run --device /dev/bus/usb/001/003 hertzg/rtl_433:debian -f 915M
rtl_433 version 21.05 (2020-05-09) inputs file rtl_tcp RTL-SDR SoapySDR with TLS
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"...

New defaults active, use "-Y classic -s 250k" for the old defaults!

Registered 157 out of 186 device decoding protocols [ 1-4 8 11-12 15-17 19-23 25-26 29-36 38-60 63 67-71 73-100 102-105 108-116 119 121 124-128 130-149 151-161 163-168 170-175 177-186 ]
Detached kernel driver
Found Rafael Micro R820T tuner
Exact sample rate is: 1000000.026491 Hz
[R82XX] PLL not locked!
Sample rate set to 1000000 S/s.
Tuner gain set to Auto.
Tuned to 915.000MHz.
Allocating 15 zero-copy buffers
baseband_demod_FM: low pass filter for 1000000 Hz at cutoff 200000 Hz, 5.0 us
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
time      : 2021-10-25 00:13:26
model     : LaCrosse-TH3 Sensor ID : 13efb7
Sequence  : 0            unknown   : 0             Temperature: 22.9 C       Humidity  : 37 %          Integrity : CRC

But if I run my (currently malfunctioning) rtl_433-hass-addons setup the header info gets chopped off and it starts much deeper in the sequence. I took the default rtl_433.example.conf and just changed the contents to match what I needed in the base config.

    [94]  Philips outdoor temperature sensor (type AJ3650)
    [95]  Schrader TPMS EG53MA4, PA66GF35
    [96]  Nexa
    [97]  Thermopro TP08/TP12/TP20 thermometer
    [98]  GE Color Effects
    [99]  X10 Security
    [100]  Interlogix GE UTC Security Devices
    [101]* Dish remote 6.3
    [102]  SimpliSafe Home Security System (May require disabling automatic gain for KeyPad decodes)
    [103]  Sensible Living Mini-Plant Moisture Sensor
    [104]  Wireless M-Bus, Mode C&T, 100kbps (-f 868950000 -s 1200000)
    [105]  Wireless M-Bus, Mode S, 32.768kbps (-f 868300000 -s 1000000)
    [106]* Wireless M-Bus, Mode R, 4.8kbps (-f 868330000)
    [107]* Wireless M-Bus, Mode F, 2.4kbps
    [108]  Hyundai WS SENZOR Remote Temperature Sensor
    [109]  WT0124 Pool Thermometer
    [110]  PMV-107J (Toyota) TPMS
    [111]  Emos TTX201 Temperature Sensor
    [112]  Ambient Weather TX-8300 Temperature/Humidity Sensor
    [113]  Ambient Weather WH31E Thermo-Hygrometer Sensor, EcoWitt WH40 rain gauge
    [114]  Maverick et73
    [115]  Honeywell ActivLink, Wireless Doorbell
    [116]  Honeywell ActivLink, Wireless Doorbell (FSK)
    [117]* ESA1000 / ESA2000 Energy Monitor
    [118]* Biltema rain gauge
    [119]  Bresser Weather Center 5-in-1
    [120]* Digitech XC-0324 temperature sensor
    [121]  Opus/Imagintronix XT300 Soil Moisture
    [122]* FS20
    [123]* Jansite TPMS Model TY02S
    [124]  LaCrosse/ELV/Conrad WS7000/WS2500 weather sensors
    [125]  TS-FT002 Wireless Ultrasonic Tank Liquid Level Meter With Temperature Sensor
    [126]  Companion WTR001 Temperature Sensor
    [127]  Ecowitt Wireless Outdoor Thermometer WH53/WH0280/WH0281A
    [128]  DirecTV RC66RX Remote Control
    [129]* Eurochron temperature and humidity sensor
    [130]  IKEA Sparsnas Energy Meter Monitor
    [131]  Microchip HCS200 KeeLoq Hopping Encoder based remotes
    [132]  TFA Dostmann 30.3196 T/H outdoor sensor
    [133]  Rubicson 48659 Thermometer
    [134]  Holman Industries iWeather WS5029 weather station (newer PCM)
    [135]  Philips outdoor temperature sensor (type AJ7010)
    [136]  ESIC EMT7110 power meter
    [137]  Globaltronics QUIGG GT-TMBBQ-05
    [138]  Globaltronics GT-WT-03 Sensor
    [139]  Norgo NGE101
    [140]  Elantra2012 TPMS
    [140]  Elantra2012 TPMS
    [141]  Auriol HG02832, HG05124A-DCF, Rubicson 48957 temperature/humidity sensor
    [142]  Fine Offset Electronics/ECOWITT WH51 Soil Moisture Sensor
    [143]  Holman Industries iWeather WS5029 weather station (older PWM)
    [144]  TBH weather sensor
    [145]  WS2032 weather station
    [146]  Auriol AFW2A1 temperature/humidity sensor
    [147]  TFA Drop Rain Gauge 30.3233.01
    [148]  DSC Security Contact (WS4945)
    [149]  ERT Standard Consumption Message (SCM)
    [150]* Klimalogg
    [151]  Visonic powercode
    [152]  Eurochron EFTH-800 temperature and humidity sensor
    [153]  Cotech 36-7959 wireless weather station with USB
    [154]  Standard Consumption Message Plus (SCMplus)
    [155]  Fine Offset Electronics WH1080/WH3080 Weather Station (FSK)
    [156]  Abarth 124 Spider TPMS
    [157]  Missil ML0757 weather station
    [158]  Sharp SPC775 weather station
    [159]  Insteon
    [160]  ERT Interval Data Message (IDM)
    [161]  ERT Interval Data Message (IDM) for Net Meters
    [162]* ThermoPro-TX2 temperature sensor
    [163]  Acurite 590TX Temperature with optional Humidity
    [164]  Security+ 2.0 (Keyfob)
    [165]  TFA Dostmann 30.3221.02 T/H Outdoor Sensor
    [166]  LaCrosse Technology View LTV-WSDTH01 Breeze Pro Wind Sensor
    [167]  Somfy RTS
    [168]  Schrader TPMS SMD3MA4 (Subaru)
    [169]* Nice Flor-s remote control for gates
    [170]  LaCrosse Technology View LTV-WR1 Multi Sensor
    [171]  LaCrosse Technology View LTV-TH Thermo/Hygro Sensor
    [172]  Bresser Weather Center 6-in-1, 7-in-1 indoor, new 5-in-1, 3-in-1 wind gauge, Froggit WH6000, Ventus C8488A
    [173]  Bresser Weather Center 7-in-1
    [174]  EcoDHOME Smart Socket and MCEE Solar monitor
    [175]  LaCrosse Technology View LTV-R1 Rainfall Gauge
    [176]  BlueLine Power Monitor
    [177]  Burnhard BBQ thermometer
    [178]  Security+ (Keyfob)
    [179]  Cavius smoke, heat and water detector
    [180]  Jansite TPMS Model Solar
    [181]  Amazon Basics Meat Thermometer
    [182]  TFA Marbella Pool Thermometer
    [183]  Auriol AHFL temperature/humidity sensor
    [184]  Auriol AFT 77 B2 temperature sensor 
    [185]  Honeywell CM921 Wireless Programmable Room Thermostat
    [186]  Hyundai TPMS (VDO)
* Disabled by default, use -R n or -G
[cmd] /run.sh exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

Is it possible to slow down the initial startup of the code with a SLEEP or something so the logger can properly capture more debug info?

reset rain gauge to zero

First comment is great work, and easy to set up
I noticed, which maybe be by design, that I am unable to reset Acurite rain gauge (Acurite-Rain899-0-1322-RT) rain value back to zero. I used mqtt explorer to reset topic 'rtl_433/9b13b3f4-rtl433/devices/Acurite-Rain899/0/1322/rain_mm' to zero, but within a min or so the topic valve returns to previous value for accumulated rainfall. This is true with rtl_433 addons running or not running, if not running, when I restart them, the rainfall changes from 0 to previous accumulated value. Over time I can imagine this number gets quite large. I can use utility meter home assistant integration to monitor interval rainfalls. Is there a trick to reset to zero?

autodiscover addon not seeing published sensor

Add-on does not seem to properly recognize published sensor data.

Log says:
[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.
mqtt found in this Home Assistance instance.
Starting rtl_433_mqtt_hass.py...
MQTT connected: Connection Accepted.

published topic looks like this:

error: Image 74930c0d/aarch64-addon-rtl433:0.1.2 does not exist for addon_74930c0d_rtl433

Hello I am try install this complement but I have this error:
Image 74930c0d/aarch64-addon-rtl433:0.1.2 does not exist for addon_74930c0d_rtl433

only run with RPI 32 bits?

Thanks

error: pathspec '21.12' did not match any file(s) known to git

I'm trying to re-install RTL_433 after removing it. It randomly stopped working so was trying this as one last nuclear option since I've tried just about everything else I can think of. I get the following in the supervisor log:

`
21-12-30 11:14:25 INFO (SyncWorker_4) [supervisor.docker.addon] Starting build for 9b13b3f4/aarch64-addon-rtl433:0.1.2
21-12-30 11:14:36 ERROR (SyncWorker_4) [supervisor.docker.addon] Can't build 9b13b3f4/aarch64-addon-rtl433:0.1.2: The command '/bin/ash -o pipefail -c git checkout ${rtl433GitRevision}' returned a non-zero code: 1
21-12-30 11:14:36 ERROR (SyncWorker_4) [supervisor.docker.addon] Build log:
Step 1/31 : ARG BUILD_FROM
Step 2/31 : FROM $BUILD_FROM as builder
---> d5dbda55fa00
Step 3/31 : MAINTAINER [email protected]
---> Using cache
---> 3df4dba2aed0
Step 4/31 : ENV LANG C.UTF-8
---> Using cache
---> e9422cd336bb
Step 5/31 : RUN apk add --no-cache --virtual .buildDeps build-base libusb-dev librtlsdr-dev cmake git
---> Using cache
---> eee3024f5f42
Step 6/31 : WORKDIR /build
---> Using cache
---> 6c861aecc81b
Step 7/31 : RUN git clone https://github.com/merbanan/rtl_433
---> Using cache
---> c2501db24e5a
Step 8/31 : WORKDIR ./rtl_433
---> Using cache
---> 21b6150baa56
Step 9/31 : ARG rtl433GitRevision=21.12
---> Using cache
---> e3edcfafa155
Step 10/31 : RUN git checkout ${rtl433GitRevision}
---> Running in d2a610b61e87
error: pathspec '21.12' did not match any file(s) known to git

Removing intermediate container d2a610b61e87
`

Any ideas? Thanks in advance.

Feature Request: Compatibility with secrets.yaml

Somewhat related to #8, are you able to add compatibility with the Home Assistant secrets file to avoid having plaintext credentials stored in the config?

Error loading shared library librtlsdr.so.0

Hi,

I installed the addon and i get this error:

[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 -c /config/rtl_433/rtl_433.conf
Error loading shared library librtlsdr.so.0: No such file or directory (needed by /usr/local/bin/rtl_433)
Error relocating /usr/local/bin/rtl_433: rtlsdr_get_device_count: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_reset_buffer: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_get_tuner_gains: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_get_device_usb_strings: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_set_tuner_gain_mode: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_close: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_get_device_name: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_set_tuner_gain: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_get_sample_rate: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_read_async: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_set_center_freq: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_open: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_set_sample_rate: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_get_center_freq: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_get_index_by_serial: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_cancel_async: symbol not found
Error relocating /usr/local/bin/rtl_433: rtlsdr_set_freq_correction: symbol not found
[cmd] /run.sh exited 127
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.

My configfile looks like this:

output      mqtt://homeassistant.local:1883,user=******,pass=*******   <<I masked the usr en paswd

frequency   433.92M
protocol    15

convert     si
report_meta newmodel

As instructed i saved the file in /config/rtl_433/rtl_433.conf

Any idee how to fix this ? "ore what dit wrong"

Thanks.

Add-on not working with error: usb_open error -1

Since last updates of HASS.IO OS and supervisor on my both instances (Rpi3 x64 and VMware) add-on is not working with the same errors:

Log:

Publishing MQTT data to 192.168.72.109 port 1883
Publishing device info to MQTT topic "rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id]".
Publishing events info to MQTT topic "rtl_433/9b13b3f4-rtl433/events".
Publishing states info to MQTT topic "rtl_433/9b13b3f4-rtl433/states".
Registered 148 out of 178 device decoding protocols [ 1-4 8 11-12 15-17 19-21 23 25-26 29-36 38-60 63 67-71 73-100 102-105 108-116 119 121 124-128 130-149 151-161 163-168 170-175 177-178 ]
usb_open error -1
[cmd] /run.sh exited 2

Core
Version
core-2021.2.2

Supervisor
Version
supervisor-2021.02.5

Operating System
Home Assistant OS 5.11

Everything was excellent before last updates!

Auto-discovery script uses invalid device_class "moisture" for Ecowitt WH51

I'm getting a "voluptuous.error.MultipleInvalid: value must be one of..." error due to the device class "moisture" being used.

Can we change this to humidity or something that homeassistant accepts?

wind_max_km_h is not available for autodiscovery

Weather station in my neighborhood sends "wind_max_km_h" field, but it is not available for autodiscovery.

All devices connected via rtl_433 have stopped working

Hi,

I would like to ask you for help with solving my problem.
Yesterday morning, all my devices connected via rtl_433 stopped working.
Home Assistant runs on Raspberry Pi 4B and I use this SDR https://www.passion-radio.com/sdr-receivers/rtl-sdr-r820t2-248.html

Here is the log from rtl_433:

[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 -c /config/rtl_433/rtl_433.conf
[13:51:32] WARNING: rtl_433 now supports automatic configuration and multiple radios. The rtl_433_conf_file option is deprecated. See the documentation for migration instructions.
rtl_433 version 21.05 branch at 202105091238 inputs file rtl_tcp RTL-SDR
Use -h for usage help and see https://triq.org/ for documentation.
Publishing MQTT data to core-mosquitto port 1883
Publishing device info to MQTT topic "rtl_433 / 9b13b3f4-rtl433 / devices [/ type] [/ model] [/ subtype] [/ channel] [/ id]".
Publishing events info to MQTT topic "rtl_433 / 9b13b3f4-rtl433 / events".
Publishing states info to MQTT topic "rtl_433 / 9b13b3f4-rtl433 / states".
Registered 2 out of 186 device decoding protocols [125 165]
Found Fitipower FC0012 tuner
Exact sample rate is: 250000.000414 Hz
Sample rate set to 250000 S / s.
Tuner gain set to Auto.
Tuned to 433.920MHz.
Allocating 15 zero-copy buffers
MQTT Connected ...
MQTT Connection established.

Here is the log from rtl_433 MQTT Auto Discovery:

[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.
mqtt found in this Home Assistance instance.
Starting rtl_433_mqtt_hass.py ...
MQTT connected: Connection Accepted.

I don't see any of the devices connected via rtl_433 in HA now.
I tried to connect SDR to a laptop with Windows and there I receive data from all devices via rtl_433 without any problem.
I think the problem will be in rtl_433 MQTT Auto Discovery, because I don't see in its log that any devices have been discovered. It used to be there.
As I tried to find out where the problem was yesterday, I restarted both add-ons several times. I also restarted the whole HA. Then the information from the device appeared to me a few times, but it was irregular and with outages, and now it doesn't work at all.
I also reinstalled both add-ons.
Yesterday, when I found out that rtl_433 is not working properly, its log also wrote pulse_FSK_detect (): Maximum number of pulses reached
It doesn't appear there now.

Here I attach the settings from rtl_433 MQTT Auto Discovery:

And here is the rtl_433 configuration file:

output      mqtt://core-mosquitto:1883,user=homeassistant,pass=XXXX
frequency   433.92M
protocol 125
protocol 165

I'm still wondering if there's a problem with the MQTT broker.
I can see in the log that rtl_433 is disconnected.

1639061485: New connection from 172.30.32.2 on port 1883.
1639061485: Socket error on client <unknown>, disconnecting.
1639061605: New connection from 172.30.32.2 on port 1883.
1639061605: Socket error on client <unknown>, disconnecting.
1639061725: New connection from 172.30.32.2 on port 1883.
1639061725: Socket error on client <unknown>, disconnecting.
1639061845: New connection from 172.30.32.2 on port 1883.
1639061845: Socket error on client <unknown>, disconnecting.
1639061965: New connection from 172.30.32.2 on port 1883.
1639061965: Socket error on client <unknown>, disconnecting.
1639062085: New connection from 172.30.32.2 on port 1883.
1639062085: Socket error on client <unknown>, disconnecting.
1639062205: New connection from 172.30.32.2 on port 1883.
1639062205: Socket error on client <unknown>, disconnecting.
1639062325: New connection from 172.30.32.2 on port 1883.
1639062325: Socket error on client <unknown>, disconnecting.
1639062398: Saving in-memory database to /data/mosquitto.db.
1639062432: Socket error on client auto-2632259D-A266-AD8B-ADC4-35D77B6DE51B, disconnecting.
1639062437: New connection from 172.30.33.6 on port 1883.
1639062437: New client connected from 172.30.33.6 as auto-DAD67A7D-A3CA-FAA4-2057-607EA2294187 (p2, c1, k60, u'addons').
1639062445: New connection from 172.30.32.2 on port 1883.
1639062445: Socket error on client <unknown>, disconnecting.
1639062565: New connection from 172.30.32.2 on port 1883.
1639062565: Socket error on client <unknown>, disconnecting.
1639062649: Socket error on client auto-DAD67A7D-A3CA-FAA4-2057-607EA2294187, disconnecting.
1639062655: New connection from 172.30.33.6 on port 1883.
1639062655: New client connected from 172.30.33.6 as auto-8F9C7773-7A45-76E9-4C0E-01422991C85A (p2, c1, k60, u'addons').
1639062685: New connection from 172.30.32.2 on port 1883.
1639062685: Socket error on client <unknown>, disconnecting.
1639062764: Socket error on client rtl_433-4801ffff, disconnecting.
1639062769: New connection from 172.30.33.5 on port 1883.
1639062769: New client connected from 172.30.33.5 as rtl_433-4801ffff (p2, c0, k60, u'homeassistant').
1639062805: New connection from 172.30.32.2 on port 1883.
1639062805: Socket error on client <unknown>, disconnecting.
1639062925: New connection from 172.30.32.2 on port 1883.
1639062925: Socket error on client <unknown>, disconnecting.
1639063045: New connection from 172.30.32.2 on port 1883.
1639063045: Socket error on client <unknown>, disconnecting.
1639063165: New connection from 172.30.32.2 on port 1883.
1639063165: Socket error on client <unknown>, disconnecting.
1639063276: Socket error on client rtl_433-4801ffff, disconnecting.
1639063282: New connection from 172.30.33.5 on port 1883.
1639063282: New client connected from 172.30.33.5 as rtl_433-4801ffff (p2, c0, k60, u'homeassistant').
1639063285: New connection from 172.30.32.2 on port 1883.
1639063285: Socket error on client <unknown>, disconnecting.
1639063316: Socket error on client auto-8F9C7773-7A45-76E9-4C0E-01422991C85A, disconnecting.
1639063322: New connection from 172.30.33.6 on port 1883.
1639063322: New client connected from 172.30.33.6 as auto-386CAC4B-05D9-BD72-95A0-B3C08FAB9471 (p2, c1, k60, u'addons').
1639063405: New connection from 172.30.32.2 on port 1883.
1639063405: Socket error on client <unknown>, disconnecting.
1639063525: New connection from 172.30.32.2 on port 1883.
1639063525: Socket error on client <unknown>, disconnecting.
1639063645: New connection from 172.30.32.2 on port 1883.
1639063645: Socket error on client <unknown>, disconnecting.
1639063742: New connection from 172.30.32.1 on port 1883.
1639063742: New client connected from 172.30.32.1 as 6tAyNaJbh9SjMvloWTQelC (p1, c1, k60, u'homeassistant').
1639063742: Client 6tAyNaJbh9SjMvloWTQelC disconnected.
1639063765: New connection from 172.30.32.2 on port 1883.
1639063765: Socket error on client <unknown>, disconnecting.
1639063865: Socket error on client auto-386CAC4B-05D9-BD72-95A0-B3C08FAB9471, disconnecting.
1639063870: New connection from 172.30.33.6 on port 1883.
1639063870: New client connected from 172.30.33.6 as auto-6E6621BD-7BF3-31FB-CBDF-4C79A5E01FB7 (p2, c1, k60, u'addons').
1639063880: Socket error on client rtl_433-4801ffff, disconnecting.
1639063885: New connection from 172.30.32.2 on port 1883.

Thanks to these add-ons, I can see in HA what the outdoor temperature is and also what volume of water remains in the well.
It worked fine the whole time and stopped abruptly yesterday.
I will be very happy for your advice.

Compile both the latest rtl_433 tag and the master branch and make configurable

When building the container:

Build the current tag as we currently do.
Also, build a copy based on master.
Expose an addon configuration option with a set of radios to choose "stable" or "master".
Ensure that when master is used, rtl_433 logs the commit hash and date it was built from.

Shutting down

Can't you just add a conf file that logs messages to the log until the user adds mqtt settings,
the previous addon worked for me but this just prints out the protocols and exists:

[cmd] /run.sh exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

light_lux not in supported keys list, only lux

I came across rtl_433 MQTT Auto Discovery (version: 0.2.1) logging

Skipped Cotech-367959/111: light_lux - where light_lux is not in the supported keys list stated in the README. A complete json payload from my switchdoclabs weatherstation is

[rtl_433] rtl_433 version 21.12 branch  at 202112141644 inputs file rtl_tcp RTL-SDR
[rtl_433] {"time" : "2022-02-19T22:40:20+0100", "model" : "Cotech-367959", "id" : 111, "battery_ok" : 0, "temperature_C" : 5.667, "humidity" : 60, "rain_mm" : 39.500, "wind_dir_deg" : 116, "wind_avg_m_s" : 2.200, "wind_max_m_s" : 3.600, "light_lux" : 0, "uv" : 0, "mic" : "CRC"}

Not sure if the supported keys follow some specific conventions, but it looks like measuredthing_unit. The README says lux is a supported key, but lux would only be a unit without the thing itself, and light_lux would follow the same as convention as rain_mm or temperature_C.

So I would suggest to add light_lux as a supported key in the same manner as lux.

Damned, just seeing it's a duplicate of #25

Apologies!!

LIBUSB_ERROR_NOT_FOUND error

Hi,
very useful add-on! But I got errors when I start add-on:

[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.
[16:49:49] WARNING: rtl_433 now supports automatic configuration and multiple radios. The rtl_433_conf_file option is deprecated. See the documentation for migration instructions.
Starting rtl_433 -c /config/rtl_433/rtl_433.conf
rtl_433 version 21.12 branch  at 202112141644 inputs file rtl_tcp RTL-SDR
Use -h for usage help and see https://triq.org/ for documentation.
Publishing MQTT data to 192.168.1.10 port 1883
Publishing device info to MQTT topic "rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id]".
Publishing events info to MQTT topic "rtl_433/9b13b3f4-rtl433/events".
Publishing states info to MQTT topic "rtl_433/9b13b3f4-rtl433/states".
newmodel option (-M) is deprecated.
Registered 176 out of 207 device decoding protocols [ 1-4 8 11-12 15-17 19-23 25-26 29-36 38-60 63 67-71 73-100 102-105 108-116 119 121 124-128 130-149 151-161 163-168 170-175 177-197 199 201-207 ]
Detached kernel driver
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
MQTT Connected...
baseband_demod_FM: low pass filter for 250000 Hz at cutoff 25000 Hz, 40.0 us
cb transfer status: 1, canceling...
LIBUSB_ERROR_NOT_FOUND: Entity not found!
Check your RTL-SDR dongle, USB cables, and power supply.
WARNING: async read failed (-5).
Library error -5, exiting...
Reattaching kernel driver failed!
[cmd] /run.sh exited 5
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

Thanks

Can't see Govee Leak Detector messages

I know that the Govee Water sensors have recently been added to rtl_433 (device 192), but for some reason I am not seeing the message come through mqtt.

My assumption is that this add on installs the latest version of rtl_433. Is that the case, or is there some other cause for them not to show up?

I had previously run rtl_433 on a separate Raspberry PI, but now am attempting to get it running directly in HA.

No Sensors found

I got both Addons running and detecting Devices, but iam unbale to see any Sensors to use in HA

protocol causing crash

Hi,

I'm having a weird issue. So I recently did a 'rebuild' so that I would pull down the latest version of rtl_433, looks like it had some changes with how it handles conf files but I specified the exact conf file in the supervisor config and it loaded up just fine.

I attempted to enable protocol 192 (its a newer protocol somewhat recently merged to master for Govee leak sensors) and when I do that, the container just exits. I'm having a hard time trying to figure out why. I did confirm the version of RTL running is the latest so maybe I'm missing something?

Issues with 433.92M and MQTT - 868 works fine

I am having weird issues with my config. To eliminate other issues, I keep my config minimal for now, with only one line:

output      mqtt://a.b.c.d:1883,user=xxxx,pass=yyyy

However when I start the addon, I get the following:

[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.
/tmp/rtl_433_heredoc: line 2: warning: here-document at line 1 delimited by end-of-file (wanted `EOD')
Starting rtl_433 with rtl_433.conf...
[rtl_433] rtl_433 version 21.12-51-g2b49b81a branch  at 202201311039 inputs file rtl_tcp RTL-SDR
[rtl_433] Use -h for usage help and see https://triq.org/ for documentation.
[rtl_433] Publishing MQTT data to a.b.c.d port 1883
[rtl_433] Publishing device info to MQTT topic "rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id]".
[rtl_433] Publishing events info to MQTT topic "rtl_433/9b13b3f4-rtl433/events".
[rtl_433] Publishing states info to MQTT topic "rtl_433/9b13b3f4-rtl433/states".
[rtl_433] Registered 181 out of 212 device decoding protocols [ 1-4 8 11-12 15-17 19-23 25-26 29-36 38-60 63 67-71 73-100 102-105 108-116 119 121 124-128 130-149 151-161 163-168 170-175 177-197 199 201-212 ]
[rtl_433] Found Rafael Micro R820T tuner
[rtl_433] Exact sample rate is: 250000.000414 Hz
[rtl_433] [R82XX] PLL not locked!
[rtl_433] Sample rate set to 250000 S/s.
[rtl_433] Tuner gain set to Auto.
[rtl_433] Tuned to 433.920MHz.
[rtl_433] Allocating 15 zero-copy buffers
[rtl_433] MQTT Connected...
[rtl_433] baseband_demod_FM: low pass filter for 250000 Hz at cutoff 25000 Hz, 40.0 us
[rtl_433] MQTT Connection error: 5
[rtl_433] MQTT Connection failed...
[rtl_433] MQTT Connected...
[rtl_433] MQTT Connection error: 5
[rtl_433] MQTT Connection failed...
[rtl_433] MQTT Connected...
[rtl_433] MQTT Connection error: 5
[rtl_433] MQTT Connection failed...
[rtl_433] MQTT Connected...
[rtl_433] MQTT Connection error: 5
[rtl_433] MQTT Connection failed...
[rtl_433] MQTT Connected...
[rtl_433] MQTT Connection error: 5
[rtl_433] MQTT Connection failed...
[rtl_433] MQTT Connected...
[rtl_433] MQTT Connection error: 5
[rtl_433] MQTT Connection failed...
[rtl_433] MQTT Connected...
[rtl_433] MQTT Connection error: 5
[rtl_433] MQTT Connection failed...
[rtl_433] MQTT Connected...
[rtl_433] MQTT Connection error: 5
[rtl_433] MQTT Connection failed...
[rtl_433] MQTT Connected...
[rtl_433] MQTT Connection error: 5
[rtl_433] MQTT Connection failed...
[rtl_433] MQTT Connected...
[rtl_433] MQTT Connection error: 5
[rtl_433] MQTT Connection failed...
[rtl_433] MQTT Connected...
[rtl_433] MQTT Connection error: 5

This goes on forever. My password or username don't contain any special characters.

when I stop the addon and specify frequency in addition:

frequency   433.92M

It does not start at all and hangs at:

[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.
/tmp/rtl_433_heredoc: line 3: warning: here-document at line 1 delimited by end-of-file (wanted `EOD')
Starting rtl_433 with rtl_433.conf...
[rtl_433] rtl_433 version 21.12-51-g2b49b81a branch  at 202201311039 inputs file rtl_tcp RTL-SDR

As soon as I change that frequency to 868M, it works immediately, without any MQTT issues:

[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.
/tmp/rtl_433_heredoc: line 3: warning: here-document at line 1 delimited by end-of-file (wanted `EOD')
Starting rtl_433 with rtl_433.conf...
[rtl_433] rtl_433 version 21.12-51-g2b49b81a branch  at 202201311039 inputs file rtl_tcp RTL-SDR
[rtl_433] Use -h for usage help and see https://triq.org/ for documentation.
[rtl_433] Publishing MQTT data to a.b.c.d port 1883
[rtl_433] Publishing device info to MQTT topic "rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id]".
[rtl_433] Publishing events info to MQTT topic "rtl_433/9b13b3f4-rtl433/events".
[rtl_433] Publishing states info to MQTT topic "rtl_433/9b13b3f4-rtl433/states".
[rtl_433] 
[rtl_433] New defaults active, use "-Y classic -s 250k" for the old defaults!
[rtl_433] 
[rtl_433] Registered 181 out of 212 device decoding protocols [ 1-4 8 11-12 15-17 19-23 25-26 29-36 38-60 63 67-71 73-100 102-105 108-116 119 121 124-128 130-149 151-161 163-168 170-175 177-197 199 201-212 ]
[rtl_433] Found Rafael Micro R820T tuner
[rtl_433] Exact sample rate is: 1000000.026491 Hz
[rtl_433] [R82XX] PLL not locked!
[rtl_433] Sample rate set to 1000000 S/s.
[rtl_433] Tuner gain set to Auto.
[rtl_433] Tuned to 868.000MHz.
[rtl_433] Allocating 15 zero-copy buffers

If I restart HA (core), keep the config file empty, and start the addon, it again hangs at:

[rtl_433] rtl_433 version 21.12-51-g2b49b81a branch  at 202201311039 inputs file rtl_tcp RTL-SDR

Basically I am unable to get 433,92MHz to work. Either by some miracle, I am able to start it, but get MQTT related errors, or I don't at all. If I change frequency to 868MHz, without any HA/Core restarts, everything works well.

Any ideas?

Fineoffset-WH51 not reporting on sensors

Hi there. My HA crashed last year so I did a new install and copied some of my old data into the fresh install.

Strange thing is my Fineoffset-WH51 moisture % doesn't show on my sensors anymore. When I listen on MQTT I can see it is publishing, but it seems not to be picked up at the end.

Any ideas on what this might be?

Invalid device class "depth"

Hey,

I just installed an Apollo sensor on my kerosene tank, and it's essentially just a depth sensor to monitor how low the oil level is.
I'm not using the addon as I don't use hass, but I did copy the very handy rtl_433_mqtt_hass.py to have HA discover the devices.

It seems to set the device class for the depth sensor to "depth", which HA is not loving. I had to delete that line (391) to have HA accept that entity.
Looks like there's also a typo line 383 for the noise entity, it has valuei, I imagine someone was using vim and pressed i one too many time, I also removed that in my copy.

Thanks for the script, apart from those two details it's very useful !

Unable to read devices after update to v0.1.2

This may be because I'm not configuring my USB device correctly. I'm unclear how to determine the correct USB device and the format to specify this.

This is what's in my rtl.s_433.conf.template:

# This is an empty template for configuring rtl_433. mqtt information will be
# automatically added. Create multiple files ending in '.conf.template' to
# manage multiple rtl_433 radios, being sure to set the 'device' setting.
# https://github.com/merbanan/rtl_433/blob/master/conf/rtl_433.example.conf

device	4
frequency   915M
protocol    171
convert     customary
output      mqtt://192.168.0.147:1883,user=xxxxxxxx,pass=xxxxxxxxxxxxx,retain=0,events=rtl_433[/model][/id]

# Uncomment the following line to also enable the default "table" output to the
# addon logs.
# output kv

Here's the rtl_433 addon log:

Any help would be greatly appreciated.

(0.1.2) MQTT connected -> connection failed -> connected ..

Hi,

When I launch the addon (0.12) I see that it is successfully connecting to the MQTT broker.
But right after that it says "MQTT error 5" - which I suppose is an authentication problem.
It stays in the loop "connected -> connection failed -> connected ..."

Needless to say that the credentials are verified (mqtt lens)

Any help is very much appreciated!
Thank you!

The log shows me:

if "model" not in data

please let me know if you need to know anything else.
thanks

{"time" : "2021-05-25 04:09:26", "model" : "Fineoffset-WH51", "id" : "00c7ae", "battery_ok" : 0.778, "battery_mV" : 1400, "moisture" : 87, "boost" : 0, "ad_raw" : 392, "mic" : "CRC"}

Protocols commented out still being detected

I've commented out almost every protocol except of a few Acurite ones.

My Acurite sensors are being detected by the SDR and add-on but so are a few other devices for protocols that I've commented out so I wonder if I'm missing something.

Could it just be that these guys happen to be using the same protocol?

re: rtl_433.c Hopping hack to sit on Freq1 for time and hop on success for Freq2

LOVE THIS ADDON!!!
But I think I might need this hop after success feature seen here...
loopy321/rtl_433@390b5c1

My problem is one of my meters seems to skip an hour every now and again.
I have set the hop rate pretty darn high and I spend half my time at a frequency/signal that has no issues and doesn't even need to be read that often. 7 or 10 seconds every 10 or 15 minutes or so would be fine for that 2nd frequency.

I am running on a pi4 with "official" HA OS install. Could I change/edit that rtl_433.c on my local machine? After that... then what? Could I use that new parameter in the rtl_433-hass-addon?

Thanks Yall.

Enable long term statistics for rtl_433 sensors?

Feature request: Enable long term statistics for rtl_433 sensors to enable graphing on a "Statistics Graph" card.

https://developers.home-assistant.io/docs/core/entity/sensor/#long-term-statistics

Bug: rtl_433 Alpine:latest code doesn't work on RPi4

Hi there.

I've been trying to see if I can get a Nooelec NESDR SMArTee v2 RTL2832U ( https://www.nooelec.com/store/sdr/sdr-receivers/smart/nesdr-smartee.html) to work with rtl_433-hass-addon on my Raspberry PI4 to interpret my LaCrosse Technologies LTV-TH2 Weather Sensor 915 MHz output.

I was able to get good data with rtl_433 on my Mac with code from Homebrew, so I knew it was theoretically possible to do. Unfortunately, every time I tried to use rtl_433-hass-addon it ended immediately in "[cmd] /run.sh exited 1".

Trying the rtl_433 Docker code used by this addon on a straight Raspberry PI 400 with latest Raspberry PI OS 32-bit, the Alpine code would instantly die with an "Assertion failed" error.

According to hertzg/rtl_433_docker#3 this is a known problem with ARM Alpine 3.13 in Latest caused by some stale library code in various distributions. There are two possible solutions:

Use the alpine-3.12 version based images (example: hertzg/rtl_433:alpine-3.12-latest)

Use debian based images (example: hertzg/rtl_433:debian-buster-latest)

After I figured out how to get into my real HAOS Root with https://github.com/adamoutler/HassOSConfigurator , I was able to get the code to run properly in this environment with the same command as the P400:

docker run --device /dev/bus/usb/001/003 hertzg/rtl_433:debian -f 915M

I'm still learning the basics of Docker at the moment, so I don't know what's all possible to do with it or how to reconfigure the files from this codebase yet.

Is it possible to make the rtl_433-hass-addon Docker initialization code branch for ARM processors to use the Debian build instead of Latest?

install error "manifest unknown" for v0.2.0

trying to uninstall and re-install as recommended in the CHANGELOG. Getting:

Failed to install add-on
Can't install ghcr.io/pbkhrv/rtl_433-hass-addons-rtl_433-aarch64:0.2.0: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=0.2.0&fromImage=ghcr.io%2Fpbkhrv%2Frtl_433-hass-addons-rtl_433-aarch64: Internal Server Error ("manifest unknown")

Create a new "next" branch and update the README

Create a branch called "next", and set it to be the default branch for PRs
Update the README with a note pointing to main for the current tagged release
Update with docs about the need to bump the version in config.json when merging from next to main, for future contributors
Re-point any existing PRs to merge to "next"

Allow autodiscover to be used with standalone docker

I run Home Assistant through docker, so add-ons are not available. I was hoping to be able to run this same container in a standalone docker environment.

It looks like run.sh finds arguments to the python file from bashio. Is there an equivalent way to pass arguments just through docker?

I tried running roughly the following:

docker run --rm -e MQTT_HOST=mqtt.com -e MQTT_PORT=1883 -e MQTT_USERNAME=username -e MQTT_PASSWORD=password --name mqtt_auto ghcr.io/pbkhrv/rtl_433-hass-addons-rtl_433_mqtt_autodiscovery-amd64

And get the following:

curl: (6) Could not resolve host: supervisor
[07:19:03] ERROR: Something went wrong contacting the API
Starting rtl_433_mqtt_hass.py...
usage: rtl_433_mqtt_hass.py [-h] [-d] [-q] [-u USER] [-P PASSWORD] [-H HOST]
                            [-p PORT] [-r] [-f] [-R RTL_TOPIC]
                            [-D DISCOVERY_PREFIX] [-i DISCOVERY_INTERVAL]
rtl_433_mqtt_hass.py: error: argument -p/--port: invalid int value: 'null'

Update the CHANGELOG

I totally missed it existed in the repository, and it's missing release notes for the last few tags.

HA MQTT: rtl_433_mqtt_hass.py: error: argument -H/--host: expected one argument

Hi,

I'm not exactly sure when this happened but my mqtt auto discovery addon has stopped working. It is now failing below:

I have noticed that the configuration has changed and no longer seems to require the username/password/server fields:

mqtt_host: XXXXX
mqtt_port: 1883
mqtt_user: XXXX
mqtt_password: XXXX

Apologies if this is really simple!

Chris

Repostitory structure for main is not compliant

Hi,

Thanks for this great work. I would like to add this to my home assistant but I got this message "Repostitory structure for main is not compliant". Do you have any idea?

light_lux

rtl_433_mqtt_autodiscovery

Published Fineoffset-WH65B/59: battery_ok, temperature_C, humidity, wind_dir_deg, wind_avg_m_s, wind_max_m_s, rain_mm, uv
Skipped Fineoffset-WH65B/59: uvi, light_lux

Here MQTT-EXPLORER:
{"time":"2021-11-02 11:52:26","model":"Fineoffset-WH65B","id":59,"battery_ok":1,"temperature_C":14.7,"humidity":72,"wind_dir_deg":196,"wind_avg_m_s":2.10375,"wind_max_m_s":2.55,"rain_mm":6316.72607,"uv":1188,"uvi":2,"light_lux":45012.0,"mic":"CRC"}

can you update script to look "light_lux" ?

Listen to multiple specific protocols at once

I took a shot at refreshing the rtl_433_mqtt bridge a while back but never shared it publicly. In my attempt I wanted to give the option to specify a list of protocols to listen for, as in my case I want to pick up readings from my oil tank and also from the electricity monitor as well.

I may be missing something but is the current rtl_433 -c (config file) approach limited to a single protocol selection?
In my case I resorted to parsing the config so I could feed in independent -R options to select the protocols of interest.

If my code is of any use please feel free to grab it? I've sent you an invite to collaborate so you can see the code as I left it here: https://github.com/michthom/hassio_addons

AcuRite 609TXC

Please disregard.

protocol 154 scm+ breaks auto discovery

trying to auto discover electric meter that uses scm+ protocol. Meter is found but not added due to:

[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.
mqtt found in this Home Assistance instance.
Starting rtl_433_mqtt_hass.py...
MQTT connected: Connection Accepted.
homeassistant/sensor/TPMS-Renault-9713f4/TPMS-Renault-9713f4-UTC/config : {"device_class": "timestamp", "name": "TPMS-Renault-9713f4-UTC", "icon": "mdi:clock-in", "state_topic": "rtl_433/9b13b3f4-rtl433/devices/TPMS/Renault/9713f4/time", "unique_id": "TPMS-Renault-9713f4-UTC", "device": {"identifiers": "TPMS-Renault-9713f4", "name": "TPMS-Renault-9713f4", "model": "Renault", "manufacturer": "rtl_433"}, "force_update": "true"}
homeassistant/sensor/TPMS-Renault-9713f4/TPMS-Renault-9713f4-P/config : {"device_class": "pressure", "name": "TPMS-Renault-9713f4-P", "unit_of_measurement": "kPa", "value_template": "{{ value|float }}", "state_topic": "rtl_433/9b13b3f4-rtl433/devices/TPMS/Renault/9713f4/pressure_kPa", "unique_id": "TPMS-Renault-9713f4-P", "device": {"identifiers": "TPMS-Renault-9713f4", "name": "TPMS-Renault-9713f4", "model": "Renault", "manufacturer": "rtl_433"}, "force_update": "true"}
homeassistant/sensor/TPMS-Renault-9713f4/TPMS-Renault-9713f4-T/config : {"device_class": "temperature", "name": "TPMS-Renault-9713f4-T", "unit_of_measurement": "\u00b0C", "value_template": "{{ value|float }}", "state_topic": "rtl_433/9b13b3f4-rtl433/devices/TPMS/Renault/9713f4/temperature_C", "unique_id": "TPMS-Renault-9713f4-T", "device": {"identifiers": "TPMS-Renault-9713f4", "name": "TPMS-Renault-9713f4", "model": "Renault", "manufacturer": "rtl_433"}, "force_update": "true"}
Published TPMS/Renault/9713f4: time, pressure_kPa, temperature_C
Skipped TPMS/Renault/9713f4: flags
homeassistant/sensor/SCM+-1552820016/SCM+-1552820016-UTC/config : {"device_class": "timestamp", "name": "SCM+-1552820016-UTC", "icon": "mdi:clock-in", "state_topic": "rtl_433/9b13b3f4-rtl433/devices/SCM+/1552820016/time", "unique_id": "SCM+-1552820016-UTC", "device": {"identifiers": "SCM+-1552820016", "name": "SCM+-1552820016", "model": "SCM+", "manufacturer": "rtl_433"}, "force_update": "true"}
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/threading.py", line 973, in _bootstrap_inner
self.run()
File "/usr/local/lib/python3.9/threading.py", line 910, in run
self._target(*self._args, **self._kwargs)
File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3591, in _thread_main
self.loop_forever(retry_first_connection=True)
File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1756, in loop_forever
rc = self._loop(timeout)
File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1164, in _loop
rc = self.loop_read()
File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1556, in loop_read
rc = self._packet_read()
File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2439, in _packet_read
rc = self._packet_handle()
File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3033, in _packet_handle
return self._handle_publish()
File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3327, in _handle_publish
self._handle_on_message(message)
File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3570, in _handle_on_message
on_message(self, self._userdata, message)
File "/rtl_433_mqtt_hass.py", line 515, in mqtt_message
bridge_event_to_hass(client, topicprefix, data)
File "/rtl_433_mqtt_hass.py", line 599, in bridge_event_to_hass
if publish_config(mqttc, topic, model, instance, mappings[key]):
File "/rtl_433_mqtt_hass.py", line 571, in publish_config
mqttc.publish(path, json.dumps(config), retain=args.retain)
File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1233, in publish
raise ValueError('Publish topic cannot contain wildcards.')
ValueError: Publish topic cannot contain wildcards.

TPMS sensors that include temp data being published

I'm getting lots of TPMS sensors that include temperature data being published. A change, or an option to ignore all ^TPMS* sensors would be nice.

Cannot use RTL stick after HassOS 7.2 upgrade

After upgrading HassOS to 7.2, RTL433 cannot use the stick, though removing it from the USB port and re-inserting produces these kernel messages:

[47616.223418] usb usb3-port1: disabled by hub (EMI?), re-enabling...
[47616.223602] usb 3-1: USB disconnect, device number 2
[47616.470623] usb 3-1: new full-speed USB device number 5 using ohci-pci
[47616.566633] hassio: port 18(veth2ad7d48) entered disabled state
[47616.566886] veth65e4d11: renamed from eth0
[47616.602932] hassio: port 18(veth2ad7d48) entered disabled state
[47616.604229] device veth2ad7d48 left promiscuous mode
[47616.604258] hassio: port 18(veth2ad7d48) entered disabled state
[47616.630343] usb 3-1: not running at top speed; connect to a high speed hub
[47616.648282] usb 3-1: New USB device found, idVendor=0bda, idProduct=2838, bcdDevice= 1.00
[47616.648289] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[47616.648293] usb 3-1: Product: RTL2838UHIDIR
[47616.648296] usb 3-1: Manufacturer: Realtek
[47616.648299] usb 3-1: SerialNumber: 00000001
[47680.643250] retire_capture_urb: 4 callbacks suppressed
[47725.294143] usb 3-1: USB disconnect, device number 5
[47731.247671] usb 3-1: new full-speed USB device number 6 using ohci-pci
[47731.408307] usb 3-1: not running at top speed; connect to a high speed hub
[47731.426322] usb 3-1: New USB device found, idVendor=0bda, idProduct=2838, bcdDevice= 1.00
[47731.426332] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[47731.426335] usb 3-1: Product: RTL2838UHIDIR
[47731.426339] usb 3-1: Manufacturer: Realtek
[47731.426342] usb 3-1: SerialNumber: 00000001

and the RTL also seems to find the device (even detect its tuner) before exiting:

Starting rtl_433 with rtl_433.conf...
[rtl_433] rtl_433 version 21.12 branch  at 202112141644 inputs file rtl_tcp RTL-SDR
[rtl_433] Use -h for usage help and see https://triq.org/ for documentation.
[rtl_433] Publishing MQTT data to core-mosquitto port 1883
[rtl_433] Publishing device info to MQTT topic "rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id]".
[rtl_433] Publishing events info to MQTT topic "rtl_433/9b13b3f4-rtl433/events".
[rtl_433] Publishing states info to MQTT topic "rtl_433/9b13b3f4-rtl433/states".
[rtl_433] Registered 4 out of 207 device decoding protocols [ 16 19 79 141 ]
[rtl_433] Found Rafael Micro R820T tuner
[rtl_433] Exact sample rate is: 250000.000414 Hz
[rtl_433] [R82XX] PLL not locked!
[rtl_433] Sample rate set to 250000 S/s.
[rtl_433] Tuner gain set to Auto.
[rtl_433] Tuned to 433.920MHz.
[rtl_433] Allocating 15 zero-copy buffers
[rtl_433] Async read stalled, exiting!
[rtl_433] 
[rtl_433] LIBUSB_ERROR_NOT_FOUND: Entity not found!
[rtl_433] Check your RTL-SDR dongle, USB cables, and power supply.
[rtl_433] 
[rtl_433] WARNING: async read failed (-5).
[cmd] /run.sh exited 3
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

my conf.template is the bare minimum, only added the time format because of an earlier issue, and had no problems with HassOS 7.1

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

# Uncomment the following line to also enable the default "table" output to the
# addon logs.
# output kv

frequency   433.92M

protocol    16
protocol    19
protocol    79
protocol    141

report_meta time:iso:tz:local

Cannot Install Auto-Discovery Add-On (ModuleNotFoundError: No module named 'contextlib')

Hello, when trying to install Auto-Discovery Add-On, following error occurs:
`The command '/bin/ash -o pipefail -c pip install --no-cache-dir --prefer-binary paho-mqtt && chmod a+x /run.sh' returned a non-zero code: 1

Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:109 
Integration: Home Assistant Supervisor (documentation, issues) 
First occurred: 16 November 2021, 20:41:55 (16 occurrences) 
Last logged: 13:23:21

Failed to to call /addons/9b13b3f4_rtl433mqttautodiscovery/install - The command '/bin/ash -o pipefail -c pip install --no-cache-dir --prefer-binary paho-mqtt && chmod a+x /run.sh' returned a non-zero code: 1
Failed to to call /addons/a844d815_rtl4332mqtt/info - Addon a844d815_rtl4332mqtt does not exist
Failed to to call /addons/9b13b3f4_rtl433/stats -

Supervisor Logs:

21-11-17 13:23:17 INFO (SyncWorker_7) [supervisor.docker.addon] Starting build for 9b13b3f4/aarch64-addon-rtl433mqttautodiscovery:0.1.9
21-11-17 13:23:21 ERROR (SyncWorker_7) [supervisor.docker.addon] Can't build 9b13b3f4/aarch64-addon-rtl433mqttautodiscovery:0.1.9: The command '/bin/ash -o pipefail -c pip install         --no-cache-dir         --prefer-binary         paho-mqtt         && chmod a+x /run.sh' returned a non-zero code: 1
21-11-17 13:23:21 ERROR (SyncWorker_7) [supervisor.docker.addon] Build log: 
Step 1/11 : ARG BUILD_FROM=homeassistant/amd64-base-python:3.9-alpine3.13
Step 2/11 : FROM ${BUILD_FROM}
 ---> 7c0b4c02319e
Step 3/11 : COPY run.sh rtl_433_mqtt_hass.py /
 ---> Using cache
 ---> 3659106438c8
Step 4/11 : RUN     pip install         --no-cache-dir         --prefer-binary         paho-mqtt         && chmod a+x /run.sh
 ---> Running in b773466ced92
Traceback (most recent call last):
  File "/usr/local/bin/pip", line 5, in <module>

    from pip._internal.cli.main import main
  File "/usr/local/lib/python3.9/site-packages/pip/_internal/cli/main.py", line 10, in <module>

    from pip._internal.cli.autocompletion import autocomplete
  File "/usr/local/lib/python3.9/site-packages/pip/_internal/cli/autocompletion.py", line 9, in <module>

    from pip._internal.cli.main_parser import create_main_parser
  File "/usr/local/lib/python3.9/site-packages/pip/_internal/cli/main_parser.py", line 7, in <module>

    from pip._internal.cli import cmdoptions
  File "/usr/local/lib/python3.9/site-packages/pip/_internal/cli/cmdoptions.py", line 18, in <module>

    from distutils.util import strtobool
  File "/usr/local/lib/python3.9/distutils/util.py", line 9, in <module>

    import importlib.util
  File "/usr/local/lib/python3.9/importlib/util.py", line 2, in <module>

    from . import abc
  File "/usr/local/lib/python3.9/importlib/abc.py", line 17, in <module>

    from typing import Protocol, runtime_checkable
  File "/usr/local/lib/python3.9/typing.py", line 23, in <module>

    import contextlib
ModuleNotFoundError: No module named 'contextlib'

Removing intermediate container b773466ced92

System Config:
Home Assistant OS 6.6
supervisor-2021.10.8
core-2021.11.4

Feature Request: rounding of values

Now the add-on sends values with many decimal digits after the dot.
For example, temperature is 28,83334 °C.
But in practice, I don't need that precision.
It would be nice if there was a rounding option in the settings indicating how many decimal places should be.

Feature Request: Contact sensors like GS-WDS07

Hi,

I'd like to submit a feature request to support generic contact sensors and generic motion sensors like the GS-WDS07 (arguably the most popular 433 contact sensor). I'm more than happy to provide any needed information that I get from RTL_433.

Thank you,
Jon

Error installing add.on: The command '/bin/ash -o pipefail -c cmake ..' returned a non-zero code: 1

Hi,
I got this error when I install the add-on
Core 2021.9.7
Supervisor: 2021.12.2
OMV 4 (Debian) docker 19.03.8

Thx

Supervisor log:
---> daa20bd29f45

Step 6/31 : WORKDIR /build

---> Using cache

---> 8493b6fa5f75

Step 7/31 : RUN git clone https://github.com/merbanan/rtl_433

---> Using cache

---> ff0bd820055e

Step 8/31 : WORKDIR ./rtl_433

---> Using cache

---> 2b0aa6bcc665

Step 9/31 : ARG rtl433GitRevision=21.12

---> Using cache

---> 158ad7e42071

Step 10/31 : RUN git checkout ${rtl433GitRevision}

---> Using cache

---> 6947275f4dea

Step 11/31 : WORKDIR ./build

---> Using cache

---> c214b12eadb8

Step 12/31 : RUN cmake ..

---> Running in 46c623fecaec

CMake Deprecation Warning at CMakeLists.txt:4 (cmake_minimum_required):
Compatibility with CMake < 2.8.12 will be removed from a future version of
CMake.

Update the VERSION argument value or use a ... suffix to tell
CMake that the project does not need compatibility with older versions.

-- The C compiler identification is GNU 10.3.1

-- Detecting C compiler ABI info

-- Detecting C compiler ABI info - failed

-- Check for working C compiler: /usr/bin/cc

-- Check for working C compiler: /usr/bin/cc - broken

CMake Error at /usr/share/cmake/Modules/CMakeTestCCompiler.cmake:66 (message):
The C compiler

"/usr/bin/cc"

is not able to compile a simple test program.

It fails with the following output:

Change Dir: /build/rtl_433/build/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/make -f Makefile cmTC_89b1a/fast && /usr/bin/make  -f CMakeFiles/cmTC_89b1a.dir/build.make CMakeFiles/cmTC_89b1a.dir/build
make: /usr/bin/make: Operation not permitted
make: *** [Makefile:127: cmTC_89b1a/fast] Error 127

CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:14 (project)

-- Configuring incomplete, errors occurred!
See also "/build/rtl_433/build/CMakeFiles/CMakeOutput.log".
See also "/build/rtl_433/build/CMakeFiles/CMakeError.log".

Removing intermediate container 46c623fecaec

Datetime without timezone exceptions with HA 12.0

Workaround

Add report_meta time:iso:tz:local to each configuration file as suggested at merbanan/rtl_433#1904 (comment)

Original Issue

Few minutes after upgrading to Home Assistant Core 12.0, the log is full with (hundreds) of exceptions because timestamps from RTL 433 sensors do not include timezone.
I guess this could something to do with this change in HA

2021-12-11 23:49:43 ERROR (MainThread) [homeassistant.components.sensor] Error adding entities for domain sensor with platform mqtt
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 382, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 613, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 748, in add_to_platform_finish
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 505, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 538, in _async_write_ha_state
state = self._stringify_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 511, in _stringify_state
if (state := self.state) is None:
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 411, in state
raise ValueError(
ValueError: Invalid datetime: sensor.auriol_hg02832_1_89_utc provides state '2021-12-11 23:49:23', which is missing timezone information

2021-12-11 23:49:43 ERROR (MainThread) [homeassistant.util.logging] Exception in message_received when handling msg on 'rtl_433/9b13b3f4-rtl433/devices/Fineoffset-WH0530/36/time': '2021-12-11 23:49:20'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/mqtt/debug_info.py", line 37, in wrapper
msg_callback(msg)
File "/usr/src/homeassistant/homeassistant/components/mqtt/sensor.py", line 249, in message_received
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 505, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 538, in _async_write_ha_state
state = self._stringify_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 511, in _stringify_state
if (state := self.state) is None:
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 411, in state
raise ValueError(
ValueError: Invalid datetime: sensor.fineoffset_wh0530_36_utc provides state '2021-12-11 23:49:20', which is missing timezone information

Error updating Add-on to 0.1.3

I get this error when I try to upgrade rtl_433 from 0.1.2 to 0.1.3 in Home Assistant (supervised) from the Add-ons page. HA is at 2021.12.9, everything is up to date as far as I can see.

The command '/bin/ash -o pipefail -c git checkout ${rtl433GitRevision}' returned a non-zero code: 1

From the supervisor log:

Jan 13 10:05:53 hass b89826351873[650]: #033[32m22-01-13 10:05:53 INFO (SyncWorker_0) [supervisor.docker.interface] Updating image 74930c0d/amd64-addon-rtl433:0.1.2 to 74930c0d/amd64-addon-rtl433:0.1.3#033[0m
Jan 13 10:05:53 hass b89826351873[650]: #033[32m22-01-13 10:05:53 INFO (SyncWorker_0) [supervisor.docker.addon] Starting build for 74930c0d/amd64-addon-rtl433:0.1.3#033[0m
Jan 13 10:05:55 hass b89826351873[650]: #033[31m22-01-13 10:05:55 ERROR (SyncWorker_0) [supervisor.docker.addon] Can't build 74930c0d/amd64-addon-rtl433:0.1.3: The command '/bin/ash -o pipefail -c git checkout ${rtl433GitRevision}' returned a non-zero code: 1#033[0m
Jan 13 10:05:55 hass b89826351873[650]: #033[31m22-01-13 10:05:55 ERROR (SyncWorker_0) [supervisor.docker.addon] Build log: 
Jan 13 10:05:55 hass b89826351873[650]: Step 1/31 : ARG BUILD_FROM
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: Step 2/31 : FROM $BUILD_FROM as builder
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> bc9cabb4596e
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: Step 3/31 : MAINTAINER [email protected]
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> Using cache
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> 67a91e9f5c2e
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: Step 4/31 : ENV LANG C.UTF-8
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> Using cache
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> 8324568c7b07
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: Step 5/31 : RUN apk add --no-cache --virtual .buildDeps     build-base     libusb-dev     librtlsdr-dev     cmake     git
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> Using cache
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> 77962d14ebf8
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: Step 6/31 : WORKDIR /build
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> Using cache
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> 9ef11d15df88
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: Step 7/31 : RUN git clone https://github.com/merbanan/rtl_433
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> Using cache
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> 508af6cf78bf
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: Step 8/31 : WORKDIR ./rtl_433
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> Using cache
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> 6f232cf2ebeb
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: Step 9/31 : ARG rtl433GitRevision=21.12
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> Using cache
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> be073053985e
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: Step 10/31 : RUN git checkout ${rtl433GitRevision}
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]:  ---> Running in b70bf3e2ce48
Jan 13 10:05:55 hass b89826351873[650]: 
Jan 13 10:05:55 hass b89826351873[650]: error: pathspec '21.12' did not match any file(s) known to git
Jan 13 10:05:55 hass b89826351873[650]: Removing intermediate container b70bf3e2ce48
Jan 13 10:05:55 hass cf6d7a6e659d[650]: 2022-01-13 10:05:55 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /store/addons/74930c0d_rtl433/update - The command '/bin/ash -o pipefail -c git checkout ${rtl433GitRevision}' returned a non-zero code: 1

pbkhrv / rtl_433-hass-addons Goto Github PK

rtl_433-hass-addons's Introduction

rtl_433 Home Assistant add-ons

Running the Development Version

Release Process

rtl_433-hass-addons's People

Contributors

Stargazers

Watchers

Forkers

rtl_433-hass-addons's Issues

Workaround

Original Issue

Recommend Projects

Recommend Topics

Recommend Org