Nah, all lifx lights that use wifi. Could be ZHA.
Just went back into the UI editor for the automation and it changed it to this formatting
for the entities.
I thought it was supposed to be this
Wondering if wrong formatting could be causing it.
Also both of these pass config check which seams weird.
- data:
brightness: 200
entity_id:
- light.sengled_e11g13_03092ed4_1
- light.sengled_e12n14_03099ca9_1
- light.sengled_e12n14_0309bf86_1
- light.sengled_e12n14_0309cda5_1
service: light.turn_on
- id: '1593273180752'
alias: Kitchen Motion On
description: ''
trigger:
- device_id: 224ba4208e06496b94e14dcf3c2803c9
domain: binary_sensor
entity_id: binary_sensor.centralite_3326_l_43e42211_ias_zone
for:
hours: 0
minutes: 0
seconds: 0
platform: device
type: motion
condition: []
action:
- data:
brightness: 200
entity_id:
- light.sengled_e11g13_03092ed4_1
- light.sengled_e12n14_03099ca9_1
- light.sengled_e12n14_0309bf86_1
- light.sengled_e12n14_0309cda5_1
service: light.turn_on
I tested this script and it works correctly (all three lights were set to brightness=65). All three lights referenced in this script use the MQTT Light integration.
test_script:
sequence:
service: light.turn_on
data:
brightness: 65
entity_id:
- light.hallway
- light.kitchen
- light.family
The list items can be aligned with entity_id or indented, both are valid YAML and are not the cause of the problem you are experiencing.
Try the following script:
test_script:
sequence:
service: light.turn_on
data:
brightness: 200
entity_id:
- light.sengled_e11g13_03092ed4_1
- light.sengled_e12n14_03099ca9_1
- light.sengled_e12n14_0309bf86_1
- light.sengled_e12n14_0309cda5_1
1 Like
Created script and ran get the same results
If I run it with the brightness option only 1 light turns on
If I remove the brightness all lights turn on fine.
Well one person with Lifx and one with MQTT looks like maybe ZHA
Did complete manual automation for each light and still only the 1st light turns on
unless I remove the brightness statements.
This is driving me nuts, any ideas?
- id: '1593273180752'
alias: Kitchen Motion On
description: ''
trigger:
- device_id: 224ba4208e06496b94e14dcf3c2803c9
domain: binary_sensor
entity_id: binary_sensor.centralite_3326_l_43e42211_ias_zone
for:
hours: 0
minutes: 0
seconds: 0
platform: device
type: motion
condition: []
action:
- data:
entity_id: light.sengled_e11g13_03092ed4_1
brightness: 200
service: light.turn_on
- data:
entity_id: light.sengled_e12n14_03099ca9_1
brightness: 200
service: light.turn_on
- data:
entity_id: light.sengled_e12n14_0309bf86_1
brightness: 200
service: light.turn_on
- data:
entity_id: light.sengled_e12n14_0309cda5_1
brightness: 200
service: light.turn_on
Thatās the most plausible theory so far because thereās nothing wrong with the way you are using the brightness option and itās proven to work with two other lighting integrations.
Does anyone have Sengled Zigbee lights using HUSBZB-1 stick that they could test
so I know if itās just me or a ZHA issue.
Thanks for all of the suggestions!
How are you using groups?
I have a group in my groups.yaml file but donāt see it in states.
kitchen_lights:
name: 'Kitchen Lights'
entities:
- light.sengled_e11g13_03092ed4_1
- light.sengled_e12n14_03099ca9_1
- light.sengled_e12n14_0309bf86_1
- light.sengled_e12n14_0309cda5_1
Thatās a normal group. You want a light group:
Itās a platform you configure under light:
Created Light group and tested.
Exactly the same as all other attempts.
Works fine without brightness as soon as I add brightness only 1st light turns on.
Looks like same results with groups. scenes, even manual.
Then there is something wrong with the integration you use to control your lights.
1 Like
Hang On
What happens with ONLY 1 light in the script
Run it with brightness 52
Then re-run it with brightness 255
Is it taking the brightness setting ?
If it is you may have to try 5 scripts (pass brightness as a variable to each)
Start runing them sequentially with (say) 5 sec gap
Reduce the gap second by second till you get to 0 gap
Stop at any time it stops working
Report back
Yes it changes the brightness of the only 1 light or if multiple then the 1st one.
With multiple lights the 2nd, 3rd etcā¦donāt even turn on itā like they get ignored.
But whats confusing is if I remove the brightness all lights turn on fine.
Yes weāve been over that but if each light IS controlled when alone in a script, iāM trying to determine if you can put the all in separate scripts, then call each in turn and how long between each one
We are trying to gather data to assist
I have tried that in a script and automation still the same results
Here is the script I ran, and put a 30 second delay between each light on
1st one turns on but none of the next ones come on.
'1587879937818':
alias: Test Light Transition
sequence:
- data:
brightness: 2
entity_id: light.sengled_e11g13_03092ed4_1
service: light.turn_on
- delay: 00:00:30
- data:
brightness: 2
entity_id: light.sengled_e12n14_03099ca9_1
service: light.turn_on
- delay: 00:00:30
- data:
brightness: 2
entity_id: light.sengled_e12n14_0309bf86_1
service: light.turn_on
- delay: 00:00:30
- data:
brightness: 2
entity_id: light.sengled_e12n14_0309cda5_1
service: light.turn_on
No, you said it worked in a single script.
So make 5 off single scripts
Call one, delay 30 secs (template the delay it will save time)
Call the next script
Will it do 2?
Try 3
Try 4
Try 5
Then start reducing the timers
Same result
Light turns on with 1st script
No other ones come on.
Check the developer tools states menu for the lights listed. Do they all have the same supported features listed in the attributes column?
Iām wondering if some of your lights have been discovered as binary/switch lights that do not support brightness.
Snap Bro
that was my thinking
are they dimmable lights and are switch.
only cause just wired a shelly1 to the toilet light which is a switch
The sengled e12-n14 do support brightness