Scene needs to be activated 2-3 times before all lights are changed

Hi …

Problem:
When I run my scene only 2/3 of the zigbee lights change - hitting the scene 1 or 2 more times, they all eventually changes… Same when I add all the lights into a group - need to turn the group off 2-3 times before all ligths are out. Turning on seems to do a better job… Not fast, all but 1-2 are on immediately and then the last 1-2-3 within 1-2 seconds.
Is there a trick for using scenes and zigbee ?

At bit more detail.
I have setup 10 zigbee (Ikea) lights in my front yard (from the street to the house), using a conbee II, and it works fine. I can control each light (on/off, change colors, brightness). I have created a small Christmas lightning (thanks for all the support here at the site - and steeling code snippets), so the lights changes colors (red and green) and brightness. Works very nice. All so good.

Next step - to add motion sensors and turn on some ‘white light’. I have managed to get 3 motion sensors (Ikea - would think I’m from Sweeden, but no…) working with timer, so the Christmas lights stops, and … then the idear was to enable a scene, that sets all lights to white. But adding this ‘call for scene’ only sets some of the lights.
Same behavior when just running the scene, or running it from development. running the scene 2-3 times in row, changes all (and yes - the Christmas automation is off).
My work around in the motion automation, is to stop the Christmas lights, and then call the scene 3 times … which most of the times gets the job done… but not the right solution.

So, I can image that it has something to do with the changing 10 lights at ones on the zigbee protocol is to much. And maybe the solution is in steed of using a scene, then do the change to white within the automation (and maybe add some wait) to slow it down.
But what is the right way to use scenes and zigbee ?

Using zha

System Health

Home Assistant Core Integration

version: 0.118.4
installation_type: Home Assistant OS
dev: false
hassio: true
docker: true
virtualenv: false
python_version: 3.8.6
os_name: Linux
os_version: 5.4.77
arch: x86_64
timezone: Europe/Copenhagen

Home Assistant Cloud

logged_in: true
subscription_expiration: January 4, 2021, 1:00 AM
relayer_connected: true
remote_enabled: true
remote_connected: true
alexa_enabled: true
google_enabled: true
can_reach_cert_server: ok
can_reach_cloud_auth: ok
can_reach_cloud: ok

Hass.io

host_os: HassOS 4.17
update_channel: stable
supervisor_version: 2020.12.6
docker_version: 19.03.12
disk_total: 30.8 GB
disk_used: 16.9 GB
healthy: true
supported: true
board: ova
supervisor_api: ok
version_api: ok
installed_addons: ESPHome (1.15.3), Node-RED (7.2.11), Samba share (9.3.0), Visual Studio Code (2.9.1), Portainer (1.3.0), Mosquitto broker (5.1), InfluxDB (3.7.7), Grafana (5.3.1), chrony (1.1.2)

Lovelace

dashboards: 2
mode: storage
views: 18
resources: 7

/Joern

1 Like

Create a group in Phoscon that contains all your lights. It will then be added to Home Assistant as another single light. When you use this light in your automation it will only send one command to the zigbee controller (ConBee II) and it will then be propagate automatically to the other lights instead of sending 10 commands to the controller.

No Phoscon here… using zha … but thanks for the answer.

Maybe the ‘cluster’ thing in zha could used ?

/Joern

Is there no group functionality in ZHA?

I’m having this issue too, was anyone able to resolve it?

I’m also seeing this issue with my setup (Conbee II, ZHA and Ikea Tradfri bulbs). I noticed I got this type of behavior controlling my Tradfri bulbs via my original Hue Hub setup. I wonder if this may be a symptom of the bulb type. Trawling through zigpy debug logs doesn’t seem to reveal an obvious answer, the commands seem to be sent correctly to each individual bulb for the scene change, but only some react on the first go.

Will keep looking into the issue, my solution was to activate the scene twice, 1 second apart. Makes me cringe doing it this way, but it is a workaround for now.

Grouping the bulbs together is a bit more reliable, but I find that sometimes only 1 aspect of the group is changed at a time. For example, when I turn on a ZHA group and set a particular brightness and color temperature, the group of Ikea bulbs only change their color temperature on the first go, and then a second activation of the scene is required to get the correct brightness.

1 Like

I have seen the same on 3 lights. I beleived it was because they are of a less know cheap brand, I actually decided to replace them at some point. Reason for waiting is they are on a physical hard place to access.
However my workarround works quite well. It is like this.

  1. Turn on the light with light.turn_on and a low brigthness (only to avoid a lot of light in the night)
  2. wiat 500ms
  3. Set the scene I whan’t (will differ based on time of day)

Works every time. If I only set the scene I get same result as mentioned above. If I trigger scene 2 times, it normally works, howeve not every time.

1 Like

I’m experiencing the same issue - also using Conbee II, ZHA, and Tradfri bulbs - some bulbs are grouped and again some bulbs in that group can change and others not even though the scene is applied to the group. Sometimes twice doesn’t even apply the scene even with a delay - I find myself activating it 2-3 times usually, particularly where both brightness and colour temperature are both changed on activation of the scene.

This is also happening in my very simple room scene, with just two Trådfri bulbs. The first scene activation changes the color temperature and then the second scene activation the brightness. I just migrated to ZHA and SkyConnect. With Conbee II and Deconz this did not happen.