I dumped Wink. I really like my Hubitat but I have one small issue...
I have a group of switches in my master suite. When I issue a command to turn them all ON it works perfectly. However when I issue a command to turn them all off it takes between 1 and 3 minutes for them all to completely turn off. This behavior is seen in any group I create that combines switches and dimmers. I have even tried to make a separate group for each type separately and it still has the same issue. Is there a workaround for issuing commands to both a switch and a dimmer that avoids this?
Wow that was fast lol. Thanks fellas. So I did try a scene and I got the same result. I use voice commands via Alexa 100% of the time. I found that if I create 1 group of lights and add it to a room in the Alexa app the performance is much better than if I expose a scene or the devices themselves. I assume it’s only 1 command to the cloud to trigger a group vs one for each light. So the command is definitely off as well. Another observation is that while it’s processing the command other commands can be issued against those devices. As an example I say “downstairs lights off” and the delay begins... then I say “kitchen lights off” which are contained in the group downstairs. Nothing happens. Eventually all downstairs lights will go off including the kitchen.
I’ll try direct in the “app” and see what happens.
In my experience, sending commands to a lot of Z-Wave devices at once will significantly slow down the Z-Wave mesh. There is a possibility that this is what you are seeing, though not for certain...
I typically don’t use Hubitat groups in Alexa. I map what light is in what room directly in Alexa and this tends to work well. It is especially nice when a hub is in a specific room, I can just tell it to turn off the lights and it does.
That said, one thing that I didn’t do in Wink but that I do in Hubitat is use sensors to detect if someone is in a room or not. This means that I now rarely if ever have to tell Alexa or use the dashboard to turn on or off lights. It did require that I purchase multiple motion sensors... but I did that slowly. I particulier like the sensors that can read illuminance as this avoids lights turning on when there is sufficient light in the room already.
So you’re of the opinion that if a room has 8 switches it’s faster to add each switch instead of a group in the Alexa “room”? I’ll try that too. I assumed it would call for 8 cloud calls instead of just 1 for the group. As far as too many switches in a group - they’re the same size groups as they were in wink. I will try these suggestions and use a scene as suggested yesterday and report back.
I would avoid nesting Hubitat Groups inside other Hubitat Groups.
Also, when you get to your 10 Philips Hue lights, leave them attached to the Hue Bridge and create groups within the Philips Hue native app. Then use the Hubitat Hue Integration to import the individual bulbs, as well as the Hue groups, into Hubitat. You can then control the Hue groups very easily, and with no 'popcorn effect' to worry about.
Still an absolute issue. I have to just say the Alexa integration is terrible maybe? Even trying to turn on a simple scene with 3 lights does not work. It’s starting to feel like none of these hubs work at all. What good is automation if I have to get up and press a button or open an app on my phone?
Are all your devices zwave? Do you have any ghosts or stranded devices? I ask because the symptoms you describe are consistent with something being awry with the zwave network.
