ring-mqtt: Ring Intercom - Could not publish attributes due to no health data

Describe the Bug

Starting from few days (don’t know exaxtly when) some entities (battery, wireless and info) are not shown anymore (they are unavailable)… while the other 2 (lock and ding) are available . It was working fine until few days ago

Steps to Reproduce

Even after re-autenticate… the problem remains

Expected Behavior

See all entities available as it was before

Log Output

2023-05-17T06:46:57.879Z ring-mqtt [Ingresso] ring/7bd72106-32fd-4e25-9e7a-841bb89a3392/intercom/343ea4b124bb/lock/state LOCKED
2023-05-17T06:46:58.326Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T06:47:23.903Z ring-disc Republishing existing device id: 343ea4b124bb
2023-05-17T06:47:23.992Z ring-disc HASS config topic: homeassistant/sensor/7bd72106-32fd-4e25-9e7a-841bb89a3392/343ea4b124bb_battery/config
2023-05-17T06:47:24.418Z ring-disc {
  name: 'Ingresso Battery',
  unique_id: '343ea4b124bb_battery',
  state_topic: 'ring/7bd72106-32fd-4e25-9e7a-841bb89a3392/intercom/343ea4b124bb/info/state',
  device_class: 'battery',
  unit_of_measurement: '%',
  state_class: 'measurement',
  value_template: '{{ value_json["batteryLevel"] | default("") }}',
  json_attributes_topic: 'ring/7bd72106-32fd-4e25-9e7a-841bb89a3392/intercom/343ea4b124bb/battery/attributes',
  availability_topic: 'ring/7bd72106-32fd-4e25-9e7a-841bb89a3392/intercom/343ea4b124bb/status',
  payload_available: 'online',
  payload_not_available: 'offline',
  device: {
    ids: [ '343ea4b124bb' ],
    name: 'Ingresso',
    mf: 'Ring',
    mdl: 'Intercom'
  }
}
2023-05-17T06:47:24.510Z ring-disc HASS config topic: homeassistant/lock/7bd72106-32fd-4e25-9e7a-841bb89a3392/343ea4b124bb_lock/config
2023-05-17T06:47:24.512Z ring-disc {
  name: 'Ingresso Lock',
  unique_id: '343ea4b124bb_lock',
  state_topic: 'ring/7bd72106-32fd-4e25-9e7a-841bb89a3392/intercom/343ea4b124bb/lock/state',
  command_topic: 'ring/7bd72106-32fd-4e25-9e7a-841bb89a3392/intercom/343ea4b124bb/lock/command',
  availability_topic: 'ring/7bd72106-32fd-4e25-9e7a-841bb89a3392/intercom/343ea4b124bb/status',
  payload_available: 'online',
  payload_not_available: 'offline',
  device: {
    ids: [ '343ea4b124bb' ],
    name: 'Ingresso',
    mf: 'Ring',
    mdl: 'Intercom'
  }
}
2023-05-17T06:47:24.514Z ring-disc HASS config topic: homeassistant/binary_sensor/7bd72106-32fd-4e25-9e7a-841bb89a3392/343ea4b124bb_ding/config
2023-05-17T06:47:24.516Z ring-disc {
  name: 'Ingresso Ding',
  unique_id: '343ea4b124bb_ding',
  state_topic: 'ring/7bd72106-32fd-4e25-9e7a-841bb89a3392/intercom/343ea4b124bb/ding/state',
  json_attributes_topic: 'ring/7bd72106-32fd-4e25-9e7a-841bb89a3392/intercom/343ea4b124bb/ding/attributes',
  icon: 'mdi:doorbell',
  availability_topic: 'ring/7bd72106-32fd-4e25-9e7a-841bb89a3392/intercom/343ea4b124bb/status',
  payload_available: 'online',
  payload_not_available: 'offline',
  device: {
    ids: [ '343ea4b124bb' ],
    name: 'Ingresso',
    mf: 'Ring',
    mdl: 'Intercom'
  }
}
2023-05-17T06:47:24.518Z ring-disc HASS config topic: homeassistant/sensor/7bd72106-32fd-4e25-9e7a-841bb89a3392/343ea4b124bb_info/config
2023-05-17T06:47:24.519Z ring-disc {
  name: 'Ingresso Info',
  unique_id: '343ea4b124bb_info',
  state_topic: 'ring/7bd72106-32fd-4e25-9e7a-841bb89a3392/intercom/343ea4b124bb/info/state',
  device_class: 'timestamp',
  value_template: '{{ value_json["lastUpdate"] | default("") }}',
  json_attributes_topic: 'ring/7bd72106-32fd-4e25-9e7a-841bb89a3392/intercom/343ea4b124bb/info/state',
  icon: 'mdi:information-outline',
  availability_topic: 'ring/7bd72106-32fd-4e25-9e7a-841bb89a3392/intercom/343ea4b124bb/status',
  payload_available: 'online',
  payload_not_available: 'offline',
  device: {
    ids: [ '343ea4b124bb' ],
    name: 'Ingresso',
    mf: 'Ring',
    mdl: 'Intercom'
  }
}
2023-05-17T06:47:28.526Z ring-mqtt [Ingresso] ring/7bd72106-32fd-4e25-9e7a-841bb89a3392/intercom/343ea4b124bb/ding/state OFF
2023-05-17T06:47:28.667Z ring-mqtt [Ingresso] ring/7bd72106-32fd-4e25-9e7a-841bb89a3392/intercom/343ea4b124bb/lock/state LOCKED
2023-05-17T06:47:32.335Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T06:48:10.659Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T06:53:10.484Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T06:58:10.797Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T07:03:10.775Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T07:08:11.394Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T07:13:10.935Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T07:18:10.886Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T07:23:13.052Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T07:28:11.114Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T07:33:10.738Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T07:38:10.906Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T07:43:10.933Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T07:44:58.399Z ring-mqtt Received updated refresh token
2023-05-17T07:44:58.403Z ring-mqtt Saving updated refresh token to state file
2023-05-17T07:44:59.530Z ring-mqtt Successfully saved updated state file: /data/ring-state.json
2023-05-17T07:48:11.021Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T07:53:10.805Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T07:58:11.020Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T08:03:11.735Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T08:08:11.194Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T08:13:10.837Z ring-mqtt [Ingresso] Could not publish attributes due to no health data
2023-05-17T08:18:11.125Z ring-mqtt [Ingresso] Could not publish attributes due to no health data

Screenshots

image

Config File

mqtt_url: mqtt://mosquitto:xxxxxxxxx@core-mosquitto:1883
mqtt_options: ""
livestream_user: ""
livestream_pass: ""
disarm_code: ""
enable_cameras: true
enable_modes: false
enable_panic: false
branch: addon
debug: ring-*
location_ids:
  - 7bd72106-32fd-4e25-9e7a-xxxxxxxxxxxxxxxxx

Install Type

Addon

Version

v5.2.2

Operating System

Home Assistan OS

Architecture

Arm v8

Machine Details

Pi3A+

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 19 (7 by maintainers)

Most upvoted comments

Guys, now all entities are again working… without doing anything…

Maybe it was a temporary problem with Ring API that they now solved (I see no other explanation).

For me the issue can be closed

+1
spanzetta on May 18, 2023

It’s possible that it’s changed, but the device health API call is unchanged in the 5 years I’ve been working with the Ring API, and is used across all “polled” devices (cameras/doorbells/chimes and, most recently, intercoms) so I’d be a little surprised. The fact that is returns data, but that data is totally useless, makes me think it more a system error vs a change, perhaps regional or device specific.

I won’t have any time to look at this in the next 10 days or so anyway, so let’s see what happens in that time.

+1
tsightler on May 17, 2023
Read more comments on GitHub
← ring-mqtt: Integration broken when HA is restarted
ring-mqtt: RTSP steams always failing, but snapshots and other entities working in HA →