Disabled entities are still known to HA, but you will not be able to read information from them or control them. When using Lovelace in auto-mode, disabled entities will not be shown. When in configurative mode, you’ll get a nice yellow entry in your UI.
Btw: HA’s “registry” is still a series of text-files in the .storage-folder. You can stop HA, then manipulate those files (backup first) and restart HA.
Be thankful that you only have two. I’ve seen forum posts saying they get a new Samsung TV device every time it is switched on (yes they had static IPs). Seems this integration has really gone to the dogs since moving to the UI.
I can see that Balloob’s response makes some sense and indeed as stated in that thread:
the UniFi integration does seem to handle this (thanks Robban).
However the Sonos integration doesn’t and surely integrations shouldn’t be accepted to the ‘core’ of HA unless they are bug free (as far as can be expected, obviously) i.e. they perform as expected.
I suspect the Sonos (and Samsung) integrations precede the ‘storage’ configuration though…
That would decimate the number of integrations. Maybe even more than 1 in 10 integrations I’ve tried have had serious issues. Some have issues that have been open for 3 years.
I’m not sure it’s good approach. But it confirms my feelings. It affects user experience and then overal grade HA takes.
I admit some compromises must be done but in general quantity over quality is not considered good approach, isn’t it?
Maybe more strict attitude to components quality, with risk of their removal from HA can encourage devs? or maybe actual removal will create users demand enough to motivate devs?
Huh, I find it interesting that “internal” integrations don’t have a rating published. Hopefully that is due to internal integrations having higher barrier for entry/minimum requirements
Ah rough. Wish I had the skills to contribute. I’m just the kind of person who would spend their spare time poking around obscure and old issues just for fun
