1 Meross Ghost Entity & VLAN Routing Fix#
1.1 The Issue#
When deleting and re-adding a Meross device, Home Assistant might refuse to connect and continuously restore the old ghost entity name while throwing a KeyError and AttributeError: 'NoneType' object has no attribute 'attach' in the logs.
1.2 Why it happens#
- The Registry Ghost: When a device is deleted from the UI, Home Assistant sometimes keeps its UUID permanently trapped in the hidden
deleted_devicesanddeleted_entitiesrecycle bins inside the.storageregistry. Whenever you re-add the device, HA automatically restores the old, corrupted data. - The Cloud Profile Cache: The
meross_lanintegration caches the Meross Cloud Profile. If you re-add a device to the Meross app,meross_lanmay still use an expired offline cache (e.g.,meross_lan.profile.xxxxxx) which lacks the new UUID or MQTT keys, causing aKeyError. - The VLAN Block: If Home Assistant is on a different VLAN than the IoT devices and HTTP (Port 80) is blocked,
meross_lancannot push the local MQTT configuration to the new device, leaving it “Unavailable”.
1.3 The Complete Fix & Automation Script#
Target SSH Host: root@10.1.2.200