feat(container): update tsightler/ring-mqtt docker tag to v5.7.1

[raelix-bot]

This PR contains the following updates:

Package	Update	Change
tsightler/ring-mqtt	minor	5.6.3 -> 5.7.1

---

Release Notes

tsightler/ring-mqtt (tsightler/ring-mqtt)

v5.7.1

Compare Source

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

v5.7.0

Compare Source

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

v5.6.7

Compare Source

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

v5.6.6

Compare Source

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

v5.6.5

Compare Source

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

v5.6.4

Compare Source

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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.