You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to remove the orphaned entities that remain when I removed and re-added the integration. I mad some significant changes to labels and partitions and they were not syncing correctly, so I removed the add-on and re-installed.
All of my new entities have come though with the new naming convention <device_type>.<panel_type>zone
However, the previous entities named <device_type>.zone_ persist.
The UI says there is no unique ID for these entities so I cannot manipulate them from the UI
I remove all of the discovery topics using MQTT explorer under /homeassistant/<device_Type>/ - this caused the new entities to be rediscovered, but my old entities still remain.
Strangely the UI says the integration is "binay sensor" and not MQTT, but I have not templates or other sources defining these sensors, so thay my be a PAI legacy.
The text was updated successfully, but these errors were encountered:
Alarm system
ECO 192
Environment
Home Assistant, latest Add On, IP150 Integration
Question
I'm trying to remove the orphaned entities that remain when I removed and re-added the integration. I mad some significant changes to labels and partitions and they were not syncing correctly, so I removed the add-on and re-installed.
All of my new entities have come though with the new naming convention <device_type>.<panel_type>zone
However, the previous entities named <device_type>.zone_ persist.
The UI says there is no unique ID for these entities so I cannot manipulate them from the UI
I remove all of the discovery topics using MQTT explorer under /homeassistant/<device_Type>/ - this caused the new entities to be rediscovered, but my old entities still remain.
Strangely the UI says the integration is "binay sensor" and not MQTT, but I have not templates or other sources defining these sensors, so thay my be a PAI legacy.
The text was updated successfully, but these errors were encountered: