Sensors reporting as unavailable even though the app can see them
iOS device model, version and app version
Model Name: iPad Air (5th generation) Software Version: iOS 16.6 App version: 2023.4 (2023.460)
Home Assistant Core Version
Home Assistant 2023.8.1
Describe the bug
Two days ago, all sensors from my iPad started returning "unavailable". Two iPhones and a Mac both continue to work fine.
I can see the sensor data in the iOS app. However, when I look at the webhook payload all of the sensors say unavailable. This makes me think it's an issue with the app and not Home Assistant core.
2023-08-11 11:47:45.295 DEBUG (MainThread) [homeassistant.components.mobile_app.webhook] Received webhook payload from Andrew’s iPad for type update_sensor_states: [{'icon': 'mdi:dots-square', 'state': 'unavailable', 'type': 'sensor', 'unique_id': 'activity'}, {'icon': 'mdi:dots-square', 'state': 'unavailable', 'type': 'sensor', 'unique_id': 'battery_level'}, {'icon': 'mdi:dots-square', 'state': 'unavailable', 'type': 'sensor', 'unique_id': 'battery_state'}, {'icon': 'mdi:dots-square', 'state': 'unavailable', 'type': 'sensor', 'unique_id': 'storage'}, {'icon': 'mdi:dots-square', 'state': 'unavailable', 'type': 'sensor', 'unique_id': 'connectivity_ssid'}, {'icon': 'mdi:dots-square', 'state': 'unavailable', 'type': 'sensor', 'unique_id': 'connectivity_bssid'}, {'icon': 'mdi:dots-square', 'state': 'unavailable', 'type': 'sensor', 'unique_id': 'connectivity_connection_type'}, {'icon': 'mdi:dots-square', 'state': 'unavailable', 'type': 'binary_sensor', 'unique_id': 'focus'}, {'icon': 'mdi:dots-square', 'state': 'unavailable', 'type': 'sensor', 'unique_id': 'last_update_trigger'}]
To Reproduce
???
Expected behavior
Screenshots
Additional context
About 2 months ago I migrated to a new iPad. When that happened, I ended up with duplicate configuration entries in Home Assistant. I disabled the one that wasn't updating, planning on fully deleting it later, but I hadn't got that yet.
To try to fix, I:
- Uninstalled the app from the iPad.
- Deleted both configuration entries for the iPad in the integration.
- Reinstalled and set up the app from scratch.
Do you still experience this using latest core and companion app versions?
Feel free to reopen if needed