Hue entities with labels aren't running the requested service from automations or dev tab when selected with label_id

[VNRARA]

The problem

Some entities with labels aren't running the requested service from automations or dev tab when selected with label_id. Example: I've labeled 4 motions switches from HUE with the label "motionsensor". I create a automation, script or use devtools to trigger based on that label, the switches stay off. Manually switching works fine. So targeting the entities as label_id doesn't work. Targeting them as "entity_id" does work.

I've tested with non-Hue switches as well. Same issue so it's not HUE I believe.

What version of Home Assistant Core has the issue?

2024.8.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

labels

Link to integration documentation on our website

https://www.home-assistant.io/docs/organizing/labels/

Diagnostics information

No response

Example YAML snippet

action: switch.turn_on
data: {}
target:
  label_id: motionsensor

Anything in the logs that might be useful for us?

Logs don't show anything specific.

Additional information

No response

[mib1185]

Hi @VNRARA

i've tried to reproduce the issue, but for me it works as expected

label

entitities

performed action

state before action performed

perform action

action: switch.turn_off
target:
  label_id: switches
data: {}

result

---

Please provide more details about the switch entities, how they are labled and the label itself - with this I might be able to reproduce your issue, thx :+1:

[VNRARA]

Try Hue's motion sensor enable/disable switch. I'll amend this comment with more later:

• Hue motion sensor running through the Hue integration. So not through 3rd party zigbee coordinator.
• The illuminance entity is also affected.
• Also doesn't work with Android IP Webcam's torch entity (turn flashlight on Android on).

To add to this; the label icon <> also doesn't split the label to the correct entities when clicked. It just disappears.

Tried it with a fresh instance and I have the same issues.

[VNRARA]

Anywhere I could look deeper for logs to find what's going on??

[mib1185]

please provide the output of following template

label_devices: {{label_devices('motionsensor')}}
label_entities: {{label_entities('motionsensor')}}

[VNRARA]

please provide the output of following template

label_devices: {{label_devices('motionsensor')}}
label_entities: {{label_entities('motionsensor')}}

label_devices: [] label_entities: ['switch.voordeursensor_motion', 'switch.kaksensor_motion', 'switch.keukensensor_motion', 'switch.schoenenkastsensor_motion', 'switch.voordeursensor_illuminance', 'switch.kaksensor_illuminance', 'switch.keukensensor_illuminance']

[mib1185]

i still can't reproduce your issue - even the part about the split by clicking on <> is working. Further without any logs or error messages it is hard to find out what's happen. You can try to create a small script with just the switch.turn_on action and the label selected, ensure that all related switch entities are in state off, than run this script and check the trace of it.

[VNRARA]

I haven't had confirmation that you tried the aformentioned HUE products so I'm going to try to find something else that can do the SWITCH. domain

Core works, but the integrations I am using may be plagued with the issue I'm currently experiencing. Using the label_id with a template switch works just fine but HUE for example doesn't. That would mean that lots of the integrations like HUE aren't properly coded to take advantage of the new label_id as a target.

[bpottle1]

I'm having the same or similar issue. I am trying to run an automation with a Number:Set action and using a label as the target ID is not working to trigger the entities. The entities are from a zigbee2mqtt device, if that makes a difference. I'm happy to help troubleshoot however I need to, but just not sure where to start.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[VNRARA]

unstale pls

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[VNRARA]

Don't close pls