What platform are you running Home Assistant on (i.e. hardware/processor)? The error above indicates that it couldn’t download the Docker image from Docker Hub. I don’t know why that would be the case but I admittedly have only a single test platform so perhaps I missed something.
I’m running Home Assistant on a Raspberry Pi 4. You don’t think it has anything to do with the addon showing the wrong version number? (i.e., https://github.com/tsightler/ring-mqtt-ha-addon says the latest release is 3.0.1 although there are a bunch of 4.0s in the files).
Updated to 4.0.0 release, everything went smootly.
Just stepping in to thank you for your excellent work, it is much appreciated 
That’s just tagged releases in Github, nothing special about them and I’m not really doing those anymore for the addon, probably should just delete those. It’s clear that you are downloading the latest addon and that the addon is attempting to pull the correct Docker image:
404 Client Error: Not Found (“No such image: tsightler/ring-mqtt-ha-addon:4.0.0”)
This has nothing to do with Github, this is when the installer attempts to pull the pre-build Docker image from Docker Hub.
By any chance are you using the 64-bit version of instead of 32-bit?
No, I’m using the 32-bit. Is there any other information I can get you to help diagnose the issue? I’ve been using your integration for a long time and have never had a problem.
@tsightler
I just found something interesting. The Snapshot I made before the upgrade to 4.0 is 220 MB. The Snapshot I made after the upgrade is 129 MB. Clearly I lost something here. Perhaps I should restore that previous Snapshot?
According to most Google searches, the 404 error, while very misleading, usually indicates that you do not have enough disk space to install the addon image. You may need to clean up older, unused images (I have had one user with that problem during the beta phase, although they had a slightly different error message). There’s mulitple reports of this issue in almost every addons issues section and that’s almost always the cause.
I guess it could still be something wrong with the images, in 4.0.0 I moved to using pre-built Docker images vs building them locally on each machine because the latter method is considered proper only for “testing” and I was tired of supporting people who had problems with this process, so I was hoping pulling a pre-built image would be more reliable. However, it’s difficult to see how the image could be an issue as it’s already had nearly 100 pulls since I pushed 4.0.0 last night and I’ve already had multiple users report success.
This is certainly strange. My installation isn’t all that complex, and I’m certainly not using much space on the SD card (64 GB SD card and only 5.6 GB is used). Did you catch my previous post about the Snapshot image size? It got a whole lot smaller after the upgrade to 4.0 and that seems like an unexpected behavior. I’m inclined to go back to the previous Snapshot and try the upgrade again.
Can you please open an issue on the Github addon page and we’ll try to work through it there? I’m sure it has to be something very basic, but I’m just not sure what it could be as the overall process is super simple.
OK, I opened the issue there.
Hi. I’m also having issues I’m guessing because I updated to the new version last night.
The add-on isn’t even Starting. When I try to manually start, I get Failed to start addon and the message “Unkown error, see logs”. When I go to the logs of the add-on and refresh, it’s completely blank. Nothing in the Configuration > Logs either.
Any ideas?
I would suggest to simply save the config, remove the addon and then attempt to reinstall it. That’s all it took to fix it for @slim0287 and several others. For some reason the upgrade is not always pulling the updated Docker image, but I’m not sure why as that operation is performed by Home Assistant, not the addon, and I’ve not been able to reproduce it and it clearly doesn’t happen in all cases. However, so far, simply removing and reinstalling seems to work.
Perfect, that did it. I had to fiddle with the MQTT settings a bit in my configuration file but everything is back to normal now. Thanks!
Awesome new easy configuration setup. Though I will suggest potentially some white text on the Web UI success message for some of us running it in dark mode. Thought something messed up after I logged in until I vaguely saw the black text on dark background.
Great new update, appreciate the hard work!
Uninstalling and reinstalling resolved this issue for me too, before that I kept on getting the Unknown Error message too.
Thanks for the great work!
I’ve updated to the latest version, seems to working fine for the arm/disarm control card in UI.
I am running docker, and added the persistent volume to the docker-compose.yaml file
volumes:
- ~/xxx/ringalarm:/data
I saw the folder ~/xxx/ringalarm created, but it is empty. Is it normal?
In HASS UI, how can I find all entities from ring alarm system?
What card and entity_id need to use the new feature like show the alarming status or trigger the alarm?
Thanks!
The devices show up in Configuration…Devices and all entities are there.
Basic alarming status is part of the Alarm Control Panel. “Triggered” state means any alarm, “Pending” state means entry delay.
If you want more details about the exact type of alarm you can use the info sensor, which includes the exact state of the alarm typically “all-clear”. However, for the easiest way to know, for example, if it is a “burglar” vs “fire” you can enable the panic buttons and monitor their state. The panic buttons will switch to “on” state whenever any alarm event of their class is active. Note that this could use some testing (by nature it’s difficult to test “real” alarm status).
Please note, if you choose to use automations to trigger panic alarms I will not be responsible for false alarms. Panic switches are disabled by default and must be explicitly enabled. When used with Home Assistant they can trigger alarm events but please note that this likely violates the Ring terms of use, especially if you are using their professional monitoring (for example triggering alarms via 3rd party sensors) and I would highly discourage this use case.
1 Like
Thanks for the remind on caution using automation, I don’t plan to use but just want to know the status.
I have the Alarm control panel card, but didn’t see the tamper_status, although it is in the configuration/state page.
How do I enable panic buttons and monitor their state? I didn’t see such attribute of alarm control panel, or any separate entity? (I searched panic in the state
Panic buttons are enabled using the enable_panic optione in the config or ENABLEPANIC environment variable for Docker.
The tamper_status (now tamperStatus) in now part of the device level information sensor vs the sensor entities since tamper is a device level attribute. For example, a flood/freeze sensor has both a flood sensor and a freeze sensor, but tamperStatus is for the device as a whole, not for the individual sensors, so it didn’t really make sense to have tamperStatus for each of those. The info sensor includes all device level information in JSON and you can present this information in the UI however you like or use it as part of automations using value templates like any other device.
1 Like
I am trying to update to 4.1 from 3.3, but the update fails. I’ll hit the update button, but nothing happens. I’ve tried updating it while stopped but still no luck. Any idea what I can try?
If you look at the supervisor log it should show an error which would provide a clue to the issue.