ring-mqtt: Ring intercom does not update ding binary sensor

Describe the Bug

The ding binary_sensor is not updaring when someone rings the intercom, it stays off all the time. Everything else is working ok. This happens since the last upade.

Steps to Reproduce

Tried ringing the intercom, I get the notification on the oficial app but nothing on home assistant

Expected Behavior

The binary sensor must turn on

Log Output

By mail

Screenshots

No response

Config File

{
    "mqtt_url": "",
    "mqtt_options": "",
    "livestream_user": "",
    "livestream_pass": "",
    "disarm_code": "",
    "enable_cameras": true,
    "enable_modes": false,
    "enable_panic": false,
    "hass_topic": "homeassistant/status",
    "ring_topic": "ring",
    "location_ids": []
}

Install Type

Docker

Version

V5.6.7

Operating System

Raspbian

Architecture

arm

Machine Details

Raspi4

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 1
  • Comments: 15 (8 by maintainers)

Most upvoted comments

Thanks, that’s why I asked, reforcing authentication does force a new refresh token, however, it’s not enough to completely force a new registration with the FCM service. To do this you need to stop the addon, remove ring-mqtt from authorized devices in Ring Command Center, then restart the addon and re-authenticate. This will force a completely new registration of ring-mqtt with the Ring API, including generating an entirely new FCM registration. This might be required in a few cases due to the migration to the new FCM APIs.

Sorry for the slow response, I’ve been travelling for the last week so very little time. Testing the dev branch is easy, just setting the BRANCH config option to “dev” and restarting is all that is required. The container will pull down the latest dev branch when it is restarted. For the addon just set the “branch” config option to “dev” and restart.

I do probably need to double check to make sure the logging needed is enabled, I’ll try to do that early this week.

It seems we’ve been able to get the data we need and, theoretically, the current development version should work. If anyone with an intercom could please test the dev version using the instructions above and report success/failure, it would be much appreciated. In the end, I will likely release 5.7.0 as soon as ring-client-api v13 has a non-beta release regardless, but it would be really good to know if the problem is resolved before release.