Core: Ikea Signal Repeaters under ZHA lost user given name/area in 0.110

[tube0013]

The problem

I have 5 Ikea Signal Repeaters in my ZHA network. each had a user given name and area set. With 0.110 that name is gone, and the areas have been lost. Attempting to rename or add them to an area does not stick either.

Environment

• Home Assistant Core release with the issue:
• Last working Home Assistant Core release (if known): 0.109.x
• Operating environment (Home Assistant/Supervised/Docker/venv): Supervised
• Integration causing this issue:
• Link to integration documentation on our website:

Problem-relevant configuration.yaml

Traceback/Error logs

Additional information

These zigbee devices do not have any entities. maybe related to #35106 ?

[probot-home-assistant[bot]]

Hey there @dmulcahey, @adminiuga, mind taking a look at this issue as its been labeled with a integration (zha) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[tofurky]

i'm seeing similar behavior in 0.110.0 with lutron connected bulb remotes. they are handled by https://github.com/zigpy/zha-device-handlers

they do not have entities - only device entries - so #35106 was deleting them upon startup. they disappeared from all automations and the devices page after upgrading to 0.110.0.

i re-paired all of them, and i was able to use them until restarting HA. they then disappeared from all automations and the devices page.

i've reverted #35106 locally for the time being, which allows the lutron zigbee remotes to survive a restart of home assistant.

@balloob, were devices without entities like these zigbee remotes/repeaters considered when making the change? i guess adding entities would need to be done by the zha integration?

[Adminiuga]

@dmulcahey is it because the device_registry is not updated with config_entry id, unless there are entities present? Nah, we do update device registry regardless of the entities

[Adminiuga]

@tube0013 does the name dis-appear after a reboot or does not stick at all?

The name and area sticks on my repeater, but it was freshly added and not migrated. Waiting for OTA to complete and trying to reboot

[tube0013]

It doesn’t ever stick. I can’t give it a user given name at all. As soon as I leave the device details page on the zha config panel it is gone. I’ll restart again in a bit but restarted a bunch last night and didn’t see any difference.

[Adminiuga]

it sticks in the current dev

But area is not displayed correctly in ZHA device page

[Adminiuga]

and it's gone after a reboot

[Adminiuga]

unrelated question. The latest firmware on Tradfri is Zigbee 3, isn't it? Does it still drop old xiaomi devices if paired through it?

[Adminiuga]

But I'm positive this is related to https://github.com/home-assistant/core/pull/35106 as in my case those disappear after a reboot

[tube0013]

Not that I’ve noticed. I have a few xiaomi devices that drop but can never remember where they were paired.

[Adminiuga]

I'm tagging this for core and open for suggestiosn.
Synopsis: ZHA integration has a corner case for "Ikea Signal Repeaters" which is a Zigbee device but it does not have any entities. Since it doesn't have any entities, with https://github.com/home-assistant/core/pull/35106 it is getting clean-up automatically -- not expected user experience for those who gave it a specific device name and zone assignment

[Adminiuga]

per #35106 device will be cleaned up if "no config entries reference them". In this case ZHA config entry still references it, no? https://github.com/home-assistant/core/blob/0514960bda07b9d503efaf3d0482ece66b849342/homeassistant/components/zha/core/gateway.py#L461-L468 Why is it still being clean-ed up? what am i missing?

[balloob]

This is my bad. Introduced it in #35106

https://github.com/home-assistant/core/blob/0514960bda07b9d503efaf3d0482ece66b849342/homeassistant/helpers/device_registry.py#L402-L407

[balloob]

This case was not considered and we should disable that check in a hot fix.

[Adminiuga]

Should be fixed by https://github.com/home-assistant/core/pull/35977

[tofurky]

35977 did indeed fix it, thanks.

[Adminiuga]

Excellent. Closing this one as the fix should be in 0.110.2