Very awesome work, @tsightler and @rajansub !! I just converted to Ring from ADT and it’s great to know there is integration (though unofficial) compared to ADT…! Bravo
Just to ensure I’m clear on the steps - as a hassio user, the correct package is https://github.com/rs1932/ring-alarm-hassio-addon
Nothing else is needed?
@rajansub have you tried to get this into Hacs? 
Thank you again!
All of the addons that you are linking to are outdated. The official addon for ring-mqtt, which I also maintain, is available at:
The other projects you are linking to are outdated, from the early days of this effort, and are no longer supported and would not likely even work. Please use the addon from the link above.
Regarding HACS, no this project is not part of HACS because it has no reason to be, it is already an addon which can be managed easily via the addon store, HACS is used for custom integrations (i.e. custom_components) which are not addons and can’t be managed as such. HACS is a great project because, prior to HACS, you had to manually manage custom_components folder and UI integrations, but it has absolutely nothing to do with addons. Addons and custom integrations are very different.
Regarding home assistant vs hassio, the hassio term has been deemphasized by Home Assistant, if you visit the hassio page you will see that there is not a single mention of hassio on that page, just references to Home Assistant. Basically if you are running a standard Home Assistant install which includes the addon store, you can use the addon. Otherwise, if you’re running Home Assistant via some install method that does not support addons, you’ll have to manually run this project.
Thank you so much, @tsightler! I appreciate the insight and details.
I guess because I was reading the older posts, I was out of sync. Thanks for getting me up to speed - that includes the Hacs reference, the transferable and use of hassio vs home assistant reference
Thanks again! Off to install the official add-on! Nice work, thanks again!
Annnnnnd I’m back… I installed, configured and tried to run the addon, but it won’t start.
[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.
ifelse: fatal: unable to exec /run.sh: Exec format error
[cmd] /run.sh exited 126
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
I’m running hassio on Ubuntu venv style.
ring alarm hassio integration
Current version: 0.55
Any ideas, @tsightler?
Based on the version information above, you still installed one of the versions which I clearly stated are outdated. Current version of ring-mqtt and the addon is 4.2.1 so, to say the least, 0.55 is not the correct one and doesn’t say stuff about hassio.
Also, I’m not even aware how you managed to install an addon if you are using python venv style install as, from what I know (I also run exactly this way) this install method does not support addons. Most likely you will need to manually install the ring-mqtt script and integrate it via Docker or by running the script as a service on your Ubuntu install. All of this is documented on the ring-mqtt site.
If you wish to proceed further, you should post more details about exactly what you did when you “installed, configured, and tried to run” the addon.
Sorry about that - don’t know how I even installed the old repository. It must have been before even finding this thread and before even purchasing the Ring gear.
I was able to install the new repo and addon version and I’m up and running.
re my install… I use the addons tool/store to enable the 3rd party functions (nodered, mqtt, deconz, etc), I don’t perform any manual installations. I just installed Docker in Ubuntu and I do everything from within Home Assistant. Rarely if ever do I need to manually do anything outside of the Home Assistant installation.
Thanks and sorry for the confusion.
Ah, no issues, the confusion was mostly in your mention of using a venv install, which is a python venv install and only support running Home Assistant Core and thus no add-ons since there is nothing to manage the Docker environment. Instead, it sounds like you’re running a Home Assistant Supervised install via Docker, which does provide the full Home Assistant experience, including addons.
I’ve actually been thinking of switching my environment to this setup as well, but I did a venv setup quite some time ago and it continues to be reliable and easy enough to manage not to bother with changing it so far. Maybe one day…
Well you know the saying - if it ain’t broke, don’t fix it. So long as the extra steps here and there aren’t too much more effort than what the benefit from change would introduce.
And Actually, yes, you’re right and that is exactly how I’m running my Home Assistant install. I think it’s the more complex of them all - I think(?). I don’t even know where I found the documentation to get it installed this way, but god forbid the day comes where I have to rebuild or migrate to new hardware. I hope I can just pick up my snapshots and lay it onto another install and be good 
So I’m up and running now and I’l be trying to figure out some cool ways to integrate this. What’s actually really cool is now I can use the sensors and motions to double for other home automation uses
Thanks again!
@“just pick state trigger instead of device trigger”
And that worked! Thank you! Pretty much everything I need is working now.
One thing that ISN’T working is the smart lighting bridge. None of the devices attached to the bridge show up, and the bridge itself does not show up either (it is in the Ring app but nowhere in ring-mqtt). However, at this point I’m not sure I care because I’ve learned the Ring smart lights are really annoying anyway–they turn themselves off after 15min and I need my lights to stay on until I turn them off. Unless that’s NOT the case when controlled by HA I’m going to return all my Ring smart lighting and instead go with Zigbee lights.
Ring’s working great as an alarm system, and ring-mqtt is working great for the alarm devices.
I don’t have Ring smart lighting, it’s always seemed far too overpriced for me, but indeed it’s true that they turn off automatically based on the time set and I believe the maximum is 15 minutes. This doesn’t change when controlled by HA, although I guess you could creatively automate this problem away.
No idea why the smart lights are not showing up, I’ve had no other reports of this issue and, since I don’t have Ring smart lighting, I don’t have any way to test it myself. With the number of users this project has these days and the fact that almost any breakage of even the most esoteric features seems to generate bug reports in a matter of a few hours, I’d think that lighting must be working in the current code, but who knows, it could also be a bug!
I don’t really see any way to implement this into this project as the core functionality of this project is to allow interfacing with Ring devices via MQTT. MQTT isn’t a platform for video streaming so that’s not really a fit for this project. The best I could implement is screenshots as that’s all the Home Assistant MQTT camera integration supports, but this is already supported by the native HA Ring component so that seems mostly a waste for HA users.
Anyone update to 0.117 and have any issues with this addon?
Only asking because a breaking change was “MQTT Discovery is now enabled by default”.
Just asking a question - better safe than sorry!
I haven’t noticed any issues. Seems to be working fine as is.
Love this add-on and it just stopped working for me this week. All the entities are now unavailable and the logs show the token is successful and then it just gets stuck on “Found new location xxx with id xxxxxx”.
I’ve uninstalled and reinstalled the add-on and Mosquito MQTT from scratch but still seeing the same results. I was on the latest release and then restored from a 0.116.2 snapshot which was working to test but still no luck. This is all on a RP4 running HassOS 4.14.
Typically this would indicate that the API call to get all devices is hanging. The only cases where I’ve seen this happen is a) the base station is on cellular backup or one of your locations is offline say perhaps an old base station that no longer is around but is not deleted, or b) some device is offline. I’d check the Ring app on your phone and verify that everything with the base station is functional and that the devices all show up and are online (i.e. no dead batteries in the sensors, etc).
@tsightler, first big thanks for your addon.
It is more of a enhancement request
is there any way to pull the battery status for both Ring Base station and Retrofit. It will helpful to set alerts on the battery levels if we we have them.
Thanks! Upgraded and no issues.
@Sakthidasang, it’s already possible to get the battery status for the base station. If you look at the sensor the “batteryStatus” field is available and you can use a template to get this status and alert on it however you like.
charging
charged
full
ok
low
none
The “charging/charged” states are used when the acPower is in ok state, and the other values are various states reported as the battery discharges when acPower is not available, so you can use this to build an alert however you like.
I’m not sure how the Retrofit device reports battery status. Most Ring devices report either “batteryLevel” as a number, these are typically devices that are battery only devices, while most devices that run on ac power but also have a battery report the “batteryStatus” field similar to the base station, and some device, like the keypad report both values, and some devices even report a “batteryBackup” status field.
The info sensor for the device should always have this information available which you can extract and alert on using a value template like any other JSON value available in the information sensor.