Bug: motion and ring events arent triggered for cameras since version 5.1.0

[wgentine]

Describe the Bug

There are no events triggered for ring or motion (in the logs or coming into mqtt)

Steps to Reproduce

Run any version from 5.1.0 onwards. Version 5.0.5 works fine.

Expected Behavior

Events will be triggering state=ON for ding and motion.

Log Output

2023-02-24T12:59:12.098Z ring-attr [Front Door] ring_topic/df55f6cc-e006-4918-b993-5f85df0343de/camera/54e019c014a5/wireless/attributes {"wirelessNetwork":"WCG-SS-IoT","wirelessSignal":-54}
2023-02-24T12:59:12.201Z ring-mqtt [Backyard] Successfully retrieved updated snapshot
2023-02-24T12:59:12.201Z ring-mqtt [Backyard] ring_topic/df55f6cc-e006-4918-b993-5f85df0343de/camera/a406e98bcc1f/snapshot/image <binary_image_data>
2023-02-24T12:59:12.202Z ring-attr [Backyard] ring_topic/df55f6cc-e006-4918-b993-5f85df0343de/camera/a406e98bcc1f/snapshot/attributes {"timestamp":1677243552}
2023-02-24T12:59:12.543Z ring-mqtt [Front Door] Successfully retrieved updated snapshot
2023-02-24T12:59:12.543Z ring-mqtt [Front Door] ring_topic/df55f6cc-e006-4918-b993-5f85df0343de/camera/54e019c014a5/snapshot/image <binary_image_data>
2023-02-24T12:59:12.543Z ring-attr [Front Door] ring_topic/df55f6cc-e006-4918-b993-5f85df0343de/camera/54e019c014a5/snapshot/attributes {"timestamp":1677243553}

Screenshots

No response

Config File

{
    "mqtt_url": "mqtts://mqtt.xxx:8883",
    "mqtt_options": "--rejectUnauthorized=false,--clientId=RING",
    "ring_token": "",
    "disarm_code": "",
    "enable_cameras": true,
    "livestream_user": "",
    "livestream_pass": "",
    "enable_modes": true,
    "enable_panic": false,
    "hass_topic": "homeassistant/status",
    "ring_topic": "ring_topic",
    "location_ids": [
        ""
    ]
}

Install Type

Docker

Version

v5.1.3

Operating System

Ubuntu

Architecture

x86_64

Machine Details

Ryzen 5600U - No hypervisor

[tsightler]

Unfortunately, I don't really know what to tell you. Over 80% of users have been running 5.1.2 or 5.1.3 for weeks now, that's approximately 4000 users, and there are no other reports of this issue, nor do I see it on any of my instances. There were basically no changes to the code that handles motion/ding events between the versions you state work/don't work. Unfortunately, that means that this is likely an issue unique to you and your setup, most likely push notifications aren't making it for some reason. My best suggestion would be to re-generate a new token and see if that helps, but be sure to clear our any unused devices as discussed in this topic: dgreif/ring#933 (comment)

[wgentine]

@tsightler well... I dont know either. I dont have any unused devices. Tried generating a new token and still doesnt work with the newest versions. There's not much else I can do in my setup as its simply a container in a river of many others.
But thanks anyway. Will keep running 5.0.5 for now.