Light Group not all members responding from blueprint

Configuration
, ,
1

I am new to Home assistant, I have been using the following setup for about 6 months without issue, I recently updated and then I am having a problem with a light group not changing the state of all members.

I have a light group (main_dl) setup, it has 4 members Dl1, Dl2, Dl3 and DL4. If I operate this light group from group helpers screen then all lights change as expected. If this same group is triggered from a blueprint(Controller - Philips 929002398602 Hue Dimmer switch v2) then a single light in the group changes state (in this case Dl3). This was previously working prior to updating in November, though I am not sure what update if any broke it as I didn’t notice immediately as I thought it was just the lights not responding.

I have tried creating a new group of lights but still the same behaviour, but the light operated changed from DL4 to Dl3. I also tried creating a new Helper from the Blueprint but I am still getting the same behaviour.

If I try to operate the group from the Group options of the group then I get a Failed to perfrom the action light/turn_on. not a valid value for the dictionnary calue @ data[‘entity_id’]

The YAML from the button press is

metadata: {}
data: {}
action: light.toggle
target:
  entity_id: light.main_dl

I have tried changing the action to turn on instead of toggle with still the same light(Dl3) turning on.

If anyone has some tips of where to start that would be great.

Thanks

2

Hi Ruzyho,
Welcome the the Home Assistant Forums!

If you are having a problem with a specific Blueprint, the first point of contact is in the Exchange (or Github) post that you found the Blueprint in originally.
There are people there using the equipment and the blueprint and will be able to give you more accurate information regarding your problem.
Here you might find someone.

3

Does a simple automation work?

E.g.,:

action: light.toggle
entity_id: light.main_dl

? (I’m not sure why you would have metadata: {} and data: {} in the automation.)

If the simple automation does not work, then it’s a bug in HA somewhere. But if it does, then the blueprint may be doing something that is causing a problem. E.g., if it is trying to expand the group or something, so you would have to look there.

-David

4

Thanks David,

I think it must be a bug in the Blueprint but it was working perfectly prior to a Home assistant update and I use multiple of the switches and all of them have been affected by it. After one of the comments yesterday I tried creating a number of simple automations to mimic each function that the blueprint was doing and managed to get it working.

It was the push I needed to work out trigger ids and I created a automation(a combination of the multiple individual automations) that mimics the behaviour that I used in the blueprint but I understand what is going on behind the scenes which will help in the future.

Thank you very much for the assistance.