I have 12 third reality Zigbee shades all using the generic Zigbee shade driver on a C7 hub running the most current software. All but one works well. Weāll call this the grinch shadeā¦.. In devices the grinch works great. It opens and closes when I press open or close. So I know the hub communicates with it. However if I go to my Shades dashboard it doesnāt respond while all the others do. I also have an automationā¦close shades at sundown. All the shades but the grinch go down. I also have a button (zen 34) to have all the shades openā¦ using button controllerā¦. All but the grinch go up. In all of these (dashboard, automation, and button controller) Iāve taken the grinch out, hit update and then selected grinch again as a device to be controllerā¦ hit update. Still nothing from the grinch.
Soā¦why would the grinch work great when selecting it from devices but be unresponsive in my dashboard, automation or button controller apps while the other 11 work great. Itās not a distance issue as one of the working ones is 1 inch awayā¦two shades for one large window and 5 others are within 10 feet of it. Can you help my grinch get a big heart?
Im having similiar problem with my 10 third reality shades but i think its a delay or congestion issue or something when i command all or a lot of them to open or close at the same time.
Im also having an issue on my dash they get stuck in opening or closing even though they are physically fully opened or closed. Do you have this issue?
I see the same thing with axisgear using the same driver, idk if the devices updates the hub properly after/during a changeā¦ for all my automations that control my blinds/shades i run a refresh ~1min after every change and the issue no longer effects me.
So here is what I came up with to get the driver out of opening or closing status. It's not perfect because i believe it is refreshing all the shades even if just 1 is activated but a conditional action doesnt have an option for "changed" and sees open and opening as the same thing.
@bobbyD is it possible for Hubitat to add an adjustable refresh on the driver. My shades seem to still be in motion when the hub makes it's final check on the device causing the device to be stuck in opening or closing status.
So through the forum I found a solution. It appears trying to send a close shades command at sunset to 12 shades at once overloads the Zigbee network. I re-wrote the rule with one action closing 6 shades at sunset and then added another action to close the other 6 shades at sunset after a 2:00 delay. All works beautifully now! Thanks to everyone on here for their help.
