ring-mqtt: Integration broken when HA is restarted
Describe the bug
After HA is restarted, all of the entities show as unavailable. After restarting mqtt-ring docker container, the entities immediately get updated.
I have the container to restart automatically when it exits (see below). I suspect that the restart happens too early for ring-mqtt. I am not sure how else to run the container.
Describe your environment
HA Running in docker. Version = 2021.9.2.
Separate mqtt server.
Describe your settings and what you’ve tried
Docker install:
docker run
–init
-d
–cpu-shares 300 --memory=256mb --memory-reservation=100mb --memory-swap=512mb --oom-kill-disable
–restart=unless-stopped
–mount type=bind,source=/root/data/ring-mqtt,target=/data
-e “MQTTHOST=192.168.11.225”
-e “MQTTPORT=1883”
-e “MQTTRINGTOPIC=ring_topic”
-e “MQTTHASSTOPIC=hass_topic”
-e "RINGTOKEN=mysecrettoken
-e “ENABLECAMERAS=true”
-e “SNAPSHOTMODE=all”
–name=ring-mqtt
tsightler/ring-mqtt
Debug Logs
I ran docker logs mqtt-ring --since 1h --follow
It seems to be that ring-mqtt is still reporting alarm/camera status as usual. For some reason HA just doesn’t receive any updates to the entities.
-------------------------------------------------------
| Ring Devices via MQTT |
| Docker Edition |
| |
| Report issues at: |
| https://github.com/tsightler/ring-mqtt |
-------------------------------------------------------
[cont-init.d] ring-mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
-------------------------------------------------------
ring-mqtt.js version: 4.8.4
Node version v14.17.6
NPM version 7.17.0
git version 2.32.0
-------------------------------------------------------
Running ring-mqtt...
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 16 (7 by maintainers)
4.8.5 remotes these from the docs completely.
Good point, I basically removed all documentation of this as being configurable a long time ago, even though it still technically is able to be configured in the code, but I never removed the line from the docker run example. Heck, I basically forgot it was there at all. I should have noticed it in your first post.
For 4.8.5 the documentation is somewhat refactored to split standard install vs docker installs into different docs so I’ll make sure to address it there.
Glad you got it working and thanks!