Release v5.7.3

v5.7.3

Minor Enhancements

• Instead of silently blocking device discovery, offline hubs will now be listed in the log which should make it easier for users to identify the device causing the issue.
• Updated ring-client-api now uses long-lived HTTPS connections, improving performance and dramtically reducing the number of DNS queries and firewall connections logged, which could previously make dozens, or even hundreds of queries per minute.
• Suppress spurious 'Message dropped as it could not be decrypted' messages from push-receiver which didn't cause any problems but just seemed to confuse people.

Bugs Fixed

• Upated ring-client-api uses long-lived HTTPS connections which should work around the hangs experienced in some environments during startup. Much thanks to @RoryJMc for amazing help testing and providing logs which finally led to a solution to this issue.

Dependency Updates

• mqtt 5.10.2
• ring-client-api 13.2.1-beta.0

Release v5.7.2

v5.7.2

Bugs Fixed

• Fix an isse that caused push notifications for camera/doorbell/intercom motion and ding events to stop working after interruptions in network connectivity for more than a few minutes..
• Fix an issue with Modes where the incorrect mode was sometimes published during initial startup. Thanks to @wahflz for the PR to address this!
• Fix a locking issue which prevented live and event streams from being active concurrently on the same camera.

Dependency Updates

• aedes 0.51.3
• body-parser 1.20.3
• date-fns 4.1.0
• debug 4.3.7
• express 4.21.1
• ffmpeg 7.0.2
• is-online 11.0.0
• mqtt 5.10.1
• node 22.11.0
• push-receiver 4.3.0
• ring-client-api 13.2.0-beta.1
• s6-overlay v3.2.0.2
• werift 0.20.1
• write-file-atomic 6.0.0

Release v5.7.1

v5.7.1

New Features

• Add experimental support for Zooz water valves. This support is currently untested, but was developed using user data dumps kindly contributed from several users and also based on a similar PR submitted for ring-homebridge from another user. Please feel free to open an issue on the Github project page if you have problems with this device and thanks to all involved for their support.

Dependency Updates

• ring-client-api v13.1.0

Release v5.7.0

v5.7.0

This release migrates to the new FCM HTTP v1 API for push notifications as the legacy FCM/GCM APIs have been deprecated for some time and shutdown of those legacy APIs started in late July 2024. While the transition to this new API should be transparent for most users, the under the hood changes are signfiicant including an entirely new push notification format. While the goal is to make this transition as seemless as possible, it is impossible to guarantee 100% success. If you experience issues with motion/ding notification from cameras, doorbells or intercoms after upgrading to this version, please follow the standard push notification troubleshooting steps as follows:

1. Open the ring-mqtt web UI and note the device name
2. Stop the ring-mqtt addon/container
3. Navigate to the Ring Control Center using the Ring App or Ring Web console
4. Locate the device with the matching device name from step 1 in Authorized Client Devices and delete it
5. Restart the addon and use the addon web UI to re-authenticate to the Ring API

Minor Enhancements

• A significant amount of work has gone into improving the reliability of streaming, especially the live stream. In prior versions there were various failure scenarios that could lead to states where future streaming requests would not succeed and the only option was to restart the entire addon/container. Hours of testing have gone into this version and many such issues have been addressed.

Dependency Updates

• ring-client-api v13.0.1
• go2rtc v1.9.4 (custom build to fix a hang on exit issue)
• Alpine Linux 3.20.2
• NodeJS v20.15.1
• s6-overlay v3.2.0.0

Release v5.6.7

v5.6.7

This release is intended to address an ongoing instability with websocket connections by using a newer API endpoint for requesting tickets.

Dependency Updates

• ring-client-api v12.1.1

Release v5.6.6

v5.6.6

This release reverts go2rtc to v1.9.2 to address streaming stability issues caused by exec handling changes that were implemented in go2rtc v1.9.3.

Dependency Updates*

• aedes v0.51.2
• debug v4.3.5

Release v5.6.5

This release is intended to address the current brokenness of HA 2024.6.x by forcing the alarm control panel entity discovery to set code_arm_required = false even when no code is configured. While I believe this should be fixed in upstream HA, I have no influence over if/when that will happen and this workaround should have no negative impact on older versions.

Dependency Updates

• go2rtc v1.9.3
• mqtt v5.7.0
• werift v0.19.3

Release v5.6.4

v5.6.4

Minor Enhancements

• New attributes alarmClearedBy/alarmClearedTime are updated when alarm is in triggered state and is cleared via the keypad or app.
• Some entities have now have categories assigned so that they appear in Configuration and Diagnostic categories in the Home Assistant UI. This also means that these entities will not be automatically included in automatically generated views, for example, when exporting devices from Home Assitant to another platform like HomeKit, although you can still manually choose to export those entities if desired. Thanks to @xannor for initial PR for this feature.

Bugs fixed

• Fixed an issue where the alarm state would lose syncronization if alarm was disarmed but a fire/co alarm was triggered and then cleared. Thanks to @iptvcld for reporting this issue and providng the details required to reproduce.

Dependcy Updates

• Alpine Linux 3.18 (Docker image)
• go2rtc v1.8.5
• ring-client-api v12.1.0
• werift v0.19.1
• aedes v0.51.0
• mqtt v5.5.2
• express v4.19.2
• S6 Overlay v3.1.6.2
• bashio v0.16.2

Release v5.6.3

v5.6.3

Minor Enhancements

• lastArmBy/lastDisarmBy now reports correct names for guest users as well as shared users
• Locks now support "LOCKING" and "UNLOCKING" status which provides for a richer experience in the Home Assistant UI
• HVAC enhanced to use new "supported_features" capability in Home Assistant >2023.9. This allows ring-mqtt to inform Home Assistant which arming modes are supported thus suppressing unavailable arming modes from being visible in the Home Assistant user interface.

Other Changes

• Remove auxillary heat implementaion which was deprecated in Home Assistant 2023.9. Auxillary/emergency heat is still available but is now exposed as a preset mode instead (behavior is duplicated from the Z-wave thermostat implementation).
• Suppress hass warnings from go2rtc (cosmetic only)

Dependcy Updates

• go2rtc v1.7.1
• ring-client-api v12.0.1

Release v5.6.2

v5.6.2

Bugs Fixed

• Fix crash when discovering Ring Bridge due to missing operator

v5.6.1

New Features

• Add support for configuring chirp tones for Ring binary sensors
• Return support for Ring Bridge which was temporarily removed in v5.6.0 due to phantom devices for some users
• Snapshot camera attributes now include the snapshot type of the current snapshot in addition to the previous timestamp attribute. Snapshot types can be any of "motion", "ding", "interval" or "on-demand". This can assist with automation cases where a specific snapshot type is preffered. However, note that no snapshot is ever guarateed and it can sometimes take multiple seconds to request and return a snapshot so, as an example, if the automation is triggered by motion, but then waits for a motion snapshot, a timeout should also be included to keep the automation from waiting forever if for some reason the snapshot could not be retrieved.

Dependcy Updates

• go2rtc v1.7.0

v5.6.0

New Features

• Cameras now include a button entity to request an on-demand snapshot. This was a much requested feature and is intended primarily to allow snapshots to be triggered from automations (in Home Assistant this can be doen via the button press service). Note that on-demand snapshots are limited to no more than one request every 10 seconds, more frequent requests will be logged, but otherwise ignored. Also, low-power Ring cameras are unable to take snapshots while recording so there is no guarantee that a request for a snapshot on these cameras will be possible.
• For doorbells it's now possible to get snapshots from ding events in addition to motion events and new snapshot modes have been introduced to select which combination of ding, motion, and interval snapshots are desired. Ding snapshots are enabled by default for both Auto and All modes, but note that battery cameras will likely require a Ring subscription to get reliable snapshots from dings, just like motion.
• Add support to enable/disable chirps on Ring keypads

Other Changes

• Adapt MQTT discovery messages to new entity naming guidelines introduced in Home Assistant 2023.8
• Minor tweak for tamper sensor to increase compatibility with OpenHAB (thanks to @zolakk for the PR)
• Merge and simplify WebRTC connection code and include recent minor updates for better reliability
• Try to capture and log null responses during web token generation

Dependcy Updates

• ring-client-api v12.0.0
• aedes v0.50.0
• werift 0.18.5