Release v5.7.0

docs/CHANGELOG.md

@@ -1,5 +1,11 @@
 ## v5.7.0
-This release implements the new FCMv1 APIs for push notifications as the legacy FCM/GCM API has been deprecated and will begin to shutdown starting on July 22nd, 2024.  While the transition to this new API should be transparent for most users, there are a lot of changes under the hood, including in several upstream dependencies and a completely new format for the push notificaitons themselves  While the goal is to make this transition as seemless as possible, 100% success can't be guaranteed.  Cameras have been heavily tested with the new format but, due to no access to a Ring Intercom, those devices have not been tested with the new format and problems are likely.  If you have a Ring Intercom and have issues with this version please open an issue and provide logs.
+The primary purpose of the release is the use of ring-client-api v13 which migrates to the new FCMv1 APIs for push notifications as the legacy FCM/GCM APIs have been deprecated for some time and have started shutting down at the end of July 2024.  While the transition to this new API should be transparent for most users, there are a lot of under the hood changes and a completely 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 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) In Authorized Client Devices find the device with the matching device name noted above and delete it
+5) Restart the addon and use the 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 various failure scenarios could lead to states where future streaming requests would not succeed and the only recourse was to restart the entire addon/container.  Hours of testing have gone into this version and many such issues have been addressed.
@@ -7,9 +13,9 @@ This release implements the new FCMv1 APIs for push notifications as the legacy
 **Dependency Updates**
 - ring-client-api v13.0.0
 - go2rtc v1.9.4 (custom build to fix a hang on exit issue)
-- NodeJS v20.13.1
+- Alpine Linux 3.20.2
+- NodeJS v20.15.1
 - s6-overlay v3.2.0.0
-- Alpine Linux 3.20.1
 
 ## v5.6.7
 This release is intended to address an ongoing instability with websocket connections by using a newer API endpoint for requesting tickets.

package.json

@@ -5,17 +5,16 @@
   "description": "Ring Devices via MQTT",
   "main": "ring-mqtt.js",
   "dependencies": {
-    "@tsightler/push-receiver": "^4.1.5",
     "aedes": "0.51.2",
     "body-parser": "^1.20.2",
     "chalk": "^5.3.0",
     "date-fns": "^3.6.0",
-    "debug": "^4.3.5",
+    "debug": "^4.3.6",
     "express": "^4.19.2",
     "is-online": "^10.0.0",
     "js-yaml": "^4.1.0",
     "minimist": "^1.2.8",
-    "mqtt": "^5.8.1",
+    "mqtt": "^5.9.1",
     "ring-client-api": "^13.0.0",
     "rxjs": "^7.8.1",
     "werift": "^0.19.4",
@@ -27,7 +26,7 @@
     "globals": "^15.9.0"
   },
   "overrides": {
-    "@eneris/push-receiver": "4.1.4"
+    "@eneris/push-receiver": "4.1.5"
   },
   "scripts": {
     "test": "echo \"Error: no test specified\" && exit 1",

scripts/update2branch.sh

@@ -56,10 +56,6 @@ else
             ;;
     esac
 
-    cd "/app/ring-mqtt-${BRANCH}/node_modules"
-    rm -rf @eneris
-    ln -s @tsightler @eneris
-
     cp -f "/app/ring-mqtt-${BRANCH}/init/s6/services.d/ring-mqtt/run" /etc/services.d/ring-mqtt/run
     chmod +x /etc/services.d/ring-mqtt/run
 fi