Helper created by Switch as X integration disappears after HA Core upgrade

[gralin]

How to reproduce the problem:

1. Change one of your Switch entities (MCP23017 output) to be shown as Light.

2. Place the new entity (light helper) on your dashboard.

3. Upgrade HA Core. During HA restart your entities won't be available.

5. Check your entities after HA restart. In my case the new entity (light helper) is gone.

At first I thought it happens on each HA restart, but it actually hapens on each HA Core upgrade. Maybe during/after upgrade there is some cleanup mechanism and because MCP23017 is loading slowly, there is some race condition and the system detects the helper entity (light) as orphaned and deletes it? I didn't see any errors or warnings in logs, but maybe it's logged on lower level...

I didn't report this in HA repository yet, because it only happens for me in case of this integration. I tried reproducing the problem with with entities from other integration (Gree, a core integration) and the helper entities don't disappear.

[gralin]

I've been having this problem ever since I started converting switches to lights, so it's not linked to any particular version of HA.

[jpcornil-git]

Hi @gralin,

I never used this switch_as_x integration (prefer to either adapt the name/icon directly in de dashboard or via customization, e.g. a homeassistant/customize section in my configuration.yaml)

You should may be add some logging before L81 of /switch_as_x/init.py to trace this (likely place where switch_as_x config_entry is removed), e.g.:

...
            _LOGGER.warning(
                f"[DEBUG] Removing config_entry {entry}",
            )
            device_registry.async_update_device(
                device_id, remove_config_entry_id=entry.entry_id
            )
...

[jpcornil-git]

Hi @gralin,
Have you been able to trace this further (race condition between switch_as_x initialisation and availability of this integration I guess, former relies on the latter) ?
Cheers,
jpc

[jpcornil-git]

For the records, fix #18 seems to address this issue as well