v5.3.0
The primary goal of this update is to address issues with camera/doorbell/intercom notifications that have impacted many users due to changes in the Ring API for push notifications. This version uses a new upstream ring-client-api that persist the FCM token and hardware ID across restarts which will hopefully address these issues, however, it's important to note that addressing this will likely require users to re-authenticate following the instructions below:
Steps to fix notifications
If you have cameras/doorbells/intercoms and are not receiving notifications you will need to follow these steps to re-establish authentication with the Ring API:
- Stop the addon and verify that it is no longer running
- In the official Ring App or using the Ring web based dashboard go to the Control Center
- Click on Authorized Client Devices
- In the list of authorized devices find and remove all devices associated with ring-mqtt, these devices will have names like the following:
- ring-mqtt
- ring-mqtt-addon
- Device name not found
- Unknown device
- Once you have removed all of these devices restart the addon.
- Review the addon logs and it should show that the existing token is invalid and you need to use the web UI to create a new one
- Use the addon web UI to authenticate with Ring and re-establish the connection with the Ring API
- Notifications should now be working!
New Features
- Added support to enable/disable motion detection for cameras
Fixed Bugs
- Use persistent FCM tokens so that push notifications survive restarts
- Remove doubled-up devices in Ring Control Center, including one "unknown device" when authenticating
- Fix random crash of go2rtc process which impacted some users (fixed by bumping go2rtc to v1.5.0)
Dependency Updates
- ring-client-api v11.8.0-beta.0
- werift v0.18.3
- rxjs v7.8.1
- go2rtc v1.5.0
- s6-overlay v3.1.5.0