Replies: 1 comment 1 reply
|
Thanks for reporting this! We were able to reproduce the issue. Root cause: The config flow used a free text field (TextSelector), but HA stores labels internally as slugified IDs. Your label X:Warning:Ignore becomes something like x_warning_ignore internally, so the comparison always fails silently. Fix: We replaced the TextSelector with a LabelSelector (dropdown). This stores the correct label ID directly. The fix will ship with v2.3. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Not sure if this is a bug, unimplemented feature or if I'm doing something wrong, so I'll ask here before filing a bug report.
There's a config field where you can specify the haghs_ignore label. Since I employ a strict namespaceh based labeling system I changed this to "X:Warning:Ignore", which doesn't seem to work. No matter if I label an entity or device with X:Warning:Ignore or haghs_ignore, they will still be counted as a zombie.
I created a second integration entry with the haghs_ignore label setting intact, and this successfully ignores devices and entities with the haghs_label.
One quick thought I haven't tested yet is if there's a bug in case detection (so x:warning:ignore would have worked) or if the colon sign breaks the feature.
All reactions