I have a 6 of the Aquara Roller Shade Driver E1 (ZNJLBL01LM) in my room. i have an automation setup that triggers manually (hitting the button on the app) to move all those 6 curtains to a position. Lately it happens that -almost every time- when activating this automation only a few of the 6 curtains actually move. if i try to run the automation again directly after the first press, it does not do anything but if i wait 2 minutes and press again, those other roller shades also finally start moving into position.
In the automation trace timeline i see the “cover set position” on all devices but then the next line only shows actually two of the devices “have turned open”.
i`ve attached screenshots of the trace, you can see that the "cover set to position " is “send” to all devices in the automation, but actually in the next line it only shows that a 2 turned opening.
The usage of entity_id instead of device_id is a good one, but it is not the issue here.
The problem is that the RF spectrum is saturated by the many commands you send, so some of them is garbled up in the noise.
This means only a few of the shades move and the rest is assumed to be moving, but once they report back the system see that they haven’t.
Try to split the action up with 1 or 2 seconds delay between calling action to set the cover position and only one cover in each action.
thank you for your anwer, Wally.
just out of curiosity, how do you know the RF is saturated? i have only 22 zqmtt devices and 3 of those are smartplugs functioning as repeaters.
edit: would there be a way for me to measure/check somehow if the RF really is saturated? can i see that somewhere?
thanks!
It is not the amount of devices it is how many that you activate at the same time.
It has always been the bane of RF devices and mesh networks needs to find out of it, especially, because signals needs to be relayed a lot.
Zigbee groups are signaled with a single packet to the group ID, so it lowers the RF signals send.
HA groups will just group all devices into on group, but on the Zigbee network it will still need to send a signal to each device.
just as an update: setting entity IDs did not help, and introducing a delay of 2 seconds did not help either.
ill try Zigbee groups and report back!
thanks!
I have had a lot of difficulty getting groups of ZigBee devices to respond together reliably. For example, I have 12 bulbs in my living room, and this is what I do to get them all to dim down reliably. light.living_room_lamp_2 is a light group with 6 separate bulbs, so this is 12 total. You can try the same thing here with the position: set it to 65%, then wait 5 seconds, set to 70%, then wait and set it to 75%. In my experience you’ll got almost all of them to between 65-75% in the end.
-David
# It takes a while for all of the blubs to actually respond, so adjus the brightness over time
- service: light.turn_on
entity_id: light.living_room_lamp_1, light.living_room_lamp_2
data:
brightness_pct: 27
transition: 5
- delay: "00:00:05"
- service: light.turn_on
entity_id: light.living_room_lamp_1, light.living_room_lamp_2
data:
brightness_pct: 26
- delay: "00:00:35"
- service: light.turn_on
entity_id: light.living_room_lamp_1, light.living_room_lamp_2
data:
brightness_pct: 25
20 seconds should be more than enough.
I would say 3-5 seconds should normally be adequate between each roller.
Maybe your Zigbee channel is saturated.
