Closed M0LTE closed 8 months ago
I'm getting the same thing
I am getting the same thing
This is happening because the run.sh
in the latest docker image doesn't contain the standalone docker code. The docker image needs to be updated to include the latest run.sh
Is the addon version 0.2.3
above correct? That was a version for rtl_433
, not the autodiscovery addon.
0.2.3
is now over a year old. Can you upgrade to the latest releases?
Same situation. Any ETA for a fix? Many thanks for the efforts!
Mike
@kristoficko are you able to confirm the addon version? The original report is confusing that way.
I am hoping to look at this in the next week or two. Otherwise, help from others submitting and reviewing fixes is always appreciated!
I'm running HA as a docker container without Add-on support, so I'm also running autodiscovery directly as a container.
Container repository:
ghcr.io/pbkhrv/rtl_433-hass-addons-rtl_433_mqtt_autodiscovery-amd64
Tag:
latest
Image ID:
734fa2d3616f
Image created:
19 months ago
Docker compose entry: `rtl_433_autodiscovery: container_name: rtl_433_autodiscovery image: ghcr.io/pbkhrv/rtl_433-hass-addons-rtl_433_mqtt_autodiscovery-amd64 environment:
Mike
Ah! Can you instead set the image to run 0.6.0 with ghcr.io/pbkhrv/rtl_433-hass-addons-rtl_433_mqtt_autodiscovery-amd64:0.6.0
. I think our automation isn't pushing latest
images at all, which is why that date is 19 months old.
looks like it's working!
kyle@bently 12:56:56 ~/docker on master [?] $ sudo docker logs docker-rtlha-1 -f
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Running in stand-alone docker mode
Starting rtl_433_mqtt_hass.py...
WARNING:root:User or password is not set. Check credentials if subscriptions do not return messages.
INFO:root:Discovering all devices
INFO:root:MQTT connected: Connection Accepted.
INFO:root:Subscribing to: rtl_433/+/events
INFO:root:Published Ambientweather-F007TH/1/70: time, channel, battery_ok, temperature_F, humidity
INFO:root:Published Ambientweather-F007TH/3/58: time, channel, battery_ok, temperature_F, humidity
Issue resolved here as well when specifying docker image version as 0.6.0.
Many thanks!
The problem
I run Home Assistant and rtl_433 in Docker, and trying to run rtl_433_autodiscovery in another container. However something seems to be up with the parameters being passed to rtl_433_mqtt_hass.py:
My docker-compose.yml:
I have no supervisor in my setup, and I have my own standalone MQTT server, no auth. Is my setup supported?
What addon are you reporting the bug for?
rtl_433_mqtt_autodiscover
What is the addon version?
0.2.3
What type of MQTT Broker are you using?
Other (details in the bug description)
Addon log messages
No response
Additional information
No response