Crypto-key missing

[jgassens]

Hello! The ring integration seems to be failing. I have attemtpted to reauthenticate and reboot, but it looks like something has changed with Ring (my Ring system works fine in the app)

here is the log:

s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/ring-mqtt.sh
-------------------------------------------------------
| Ring-MQTT with Video Streaming                      |
| Addon for Home Assistant                            |
|                                                     |
| For support questions please visit:                 |
| https://github.com/tsightler/ring-mqtt/discussions  |
-------------------------------------------------------
cont-init: info: /etc/cont-init.d/ring-mqtt.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun ring-mqtt (no readiness notification)
s6-rc: info: service legacy-services successfully started
-------------------------------------------------------
ring-mqtt.js version: 5.7.2
Node version v22.11.0
NPM version 10.9.0
git version 2.45.2
-------------------------------------------------------
Running ring-mqtt...
2024-11-20T14:00:09.459Z ring-mqtt Detected runmode: addon
2024-11-20T14:00:09.470Z ring-mqtt Configuration file: /data/options.json
2024-11-20T14:00:14.491Z ring-mqtt Reading latest data from state file: /data/ring-state.json
2024-11-20T14:00:14.506Z ring-mqtt Succesfully started the token generator web UI
2024-11-20T14:00:14.525Z ring-mqtt Discovered MQTT Host: core-mosquitto
2024-11-20T14:00:14.525Z ring-mqtt Discovered MQTT Port: 1883
2024-11-20T14:00:14.526Z ring-mqtt Discovered MQTT User: addons
2024-11-20T14:00:14.526Z ring-mqtt Discovered MQTT password: <hidden>
2024-11-20T14:00:14.526Z ring-mqtt MQTT URL: mqtt://addons:********@core-mosquitto:1883
2024-11-20T14:00:14.752Z ring-mqtt Attempting connection to Ring API using saved refresh token...
2024-11-20T14:00:17.461Z ring-mqtt Successfully established connection to Ring API using saved token
2024-11-20T14:00:17.465Z ring-mqtt Received updated refresh token
2024-11-20T14:00:17.465Z ring-mqtt Saving updated refresh token to state file
2024-11-20T14:00:18.503Z ring-mqtt Successfully saved updated state file: /data/ring-state.json
2024-11-20T14:00:19.463Z ring-mqtt Attempting connection to MQTT broker...
2024-11-20T14:00:20.975Z ring-mqtt MQTT connection established, processing Ring locations...
2024-11-20T14:00:23.433Z ring-mqtt ------------------------------------------------------------------------------------------
2024-11-20T14:00:23.433Z ring-mqtt This account has access to the following locations:
2024-11-20T14:00:23.434Z ring-mqtt             [redacted] (******************************)
2024-11-20T14:00:23.434Z ring-mqtt                                                                                           
2024-11-20T14:00:23.434Z ring-mqtt IMPORTANT: If *ANY* alarm or smart lighting hubs at these locations are *OFFLINE* 
2024-11-20T14:00:23.435Z ring-mqtt            the device discovery process below will hang and no devices will be    
2024-11-20T14:00:23.435Z ring-mqtt            published!                                                             
2024-11-20T14:00:23.435Z ring-mqtt                                                                                           
2024-11-20T14:00:23.435Z ring-mqtt            If the message "Device Discovery Complete!" is not logged below, please
2024-11-20T14:00:23.436Z ring-mqtt            carefully check the Ring app for any hubs or smart lighting devices    
2024-11-20T14:00:23.436Z ring-mqtt            that are in offline state and either remove them from the location or  
2024-11-20T14:00:23.436Z ring-mqtt            bring them back online prior to restarting ring-mqtt.                  
2024-11-20T14:00:23.436Z ring-mqtt                                                                                           
2024-11-20T14:00:23.436Z ring-mqtt            If desired, the "location_ids" config option can be used to restrict   
2024-11-20T14:00:23.436Z ring-mqtt            discovery to specific locations. See the documentation for details.    
2024-11-20T14:00:23.436Z ring-mqtt ------------------------------------------------------------------------------------------
2024-11-20T14:00:23.436Z ring-mqtt Starting Device Discovery...
2024-11-20T14:00:23.436Z ring-mqtt                                                                                           
2024-11-20T14:00:23.436Z ring-mqtt New location: [redacted] (******************************)
Message dropped as it could not be decrypted: crypto-key is missing

That last line there has me thinking Ring changed its API but... if anyone has any other ideas, please let me know.

[tsightler]

People always read the last line in the log instead of the message highlighted as "IMPORTANT"! :)

If you are 100% sure that none of your hub devices are offline (no unused smart lighting hubs, bulbs, locks, etcs), then you can try the dev branch, but 99.9% of reports of a hang here are because the alarm hub is offline/on cellular backup.

[jgassens]

oh boy 🤦
yes, the alarm was in cellular backup mode. I didn't notice that.
I did get one error but im not sure it is important:
Unsupported device: bridge.flatline

Any idea what that could be?

[tsightler]

Not really an error, obviously this project doesn't support every single device in existence (supported devices are listed in the docs). I'm not 100% sure, but I believe that bridge.flatline is the Ring Retrofit Alarm Kit which connects existing wired sensors to a Ring Alarm. Does your setup have one of these? This retrofit bridge itself is not currently supported (it won't show up as it's own device), but I've been told by others that the sensors connected to it still show up individually so this isn't really a major issue.

[jgassens]

Thanks! yes, I do have a Ring Retrofil Alarm Kit… but the sensors do indeed show up. So, I think I am all good :)

thanks

[Vlada3333]

This is important, thank you.