I have a problem when I change mode to for example Evening mode from night o away.
When rule machine kicks in not all lights I want turns on and its not the same lights that dont on if I try several times. I have done repairs .
It feels like it came with the latest fw
c7 latest fw.
All devices have routes
I have fibaro dimmers and qubino dimmers
What could be wrong?
How many lights are you having turn on/off at one time? Have you tried to set this up in groups and scenes? That would be a better fit because it's written to delegate turning on/off several lights at one time. You've probably go commands walking all over each other. Switch your rule to groups and scenes and make mode your trigger. Probably turn on the optimize tick box as well in your rule. Post your findings.
Hi . Have tried with groups but no success. Its always one or two devices that dont turn on or off..... When I look in the logs it has not even tried to turn on or off the failing devices.....
How many lights are you trying to control at one time?
When I turn on night mode its about 20 devices to off that's on zwave...
So picture this - the hub trying to send a signal out to 20 devices at one time. Some using the same paths. They're bound to get bottlenecked. We say "It's just 20". But it's TWENTY. Might have better luck if turn them off in groups instead of expecting them to successfully interact all at once. That probably isn't going to happen. you're still going to get a popcorn effect at best IF the commands aren't colliding.
If you're getting the same issue in groups, I imagine that you have one rule calling for all 20 lights to turn off in separate lines of the same rule. That will not solve your problem. You would need to put a wait, or a separate rule. In essence, you're still asking the hub to turn off all 20 lights at basically the same time.
I would use groups with on/off optimization turned on. This will help get rid of unnecessary wireless traffic. Worked wonders for my big made changes (away,night,housekeeper)
Did you do the secondary manual update to the drivers?
it would certain make debugging easier to do that.
Probably propagating that many commands through that many switches is a problem. I would make few groups, like bedrooms, outdoor, main living area or whatever an then activate each is series.
April showing her age again. 
But @mailtomatte for sure, turning off groups of devices is going to "clog up" the Zwave. I am not sure if there is a number that IS going to work, but maybe try half (10) and see if it is a particular device that is causing it, or whether it is just that many at one time.
What do you mean with this?
ok but with vera it was not a problem with 20 devices. Of course it was with popcorn effect but that's ok. With Hubitatat it always forgets 2 or 3 devices but is faster than vera...
I have now tried putting light devices in groups with max 2-5 devices in each group and 3 seconds delay between them and it still does not turn everybody off (for example). Always som device that's not changing to right state. @bcopeland Whats the secret with zwave and Hubitat ? Im ripping my hair off..... Whats the best way to change state of 20 zwave lights directly?
These days, I use my own apps for my mass changes.. But if you are using groups I have found it helpful to turn off:
Hi ... omg! Your mode action app is the missing app for Hubitat!!! This is the way i like it. Easy and clean. Only thing missing is to be able to set dimmers individual .
I Will try how it works with mass action on lights.
Any progress on fibaro device drivers that Donāt work or not work good?
Thanx
When you update the firmware you then have to go to device then Z-Wave then there will be three dots, select Z-Wave details. It will be in there as of version 3.3.3.145, I think. There was instruction when you do an update of the hub. It was required to do it this was because of the nature of the bugs being fixed. Z-Wave Plus is a huge part of all the updates they have been doing the past month or two. Many for the C-7 to implement S2 properly without messing up other functions. They are also adding lots of devices. They really need to update the list on their web site too.
PS - There is bug in the MyQ Lite code I saw while reviewing it. Not sure how to submit it.
Hi i have trieded your own mode action app wich i think should be standard in Hubitat. Even if its nice same problem with som lights not turning off (or on)
I Donāt know how Hubitat software is built but why does it give up trying so fast? In Vera it tried 3 times and then moved on to next zwave device. And then when Done with all that worked it tries the one that didnt work on attemt 123. .
In my ears its something wrong with Hubitat code if it cant handle the max 232 zwave devices as it should.
I Mean Home automation nr 1 is to be able to turn on and off lights and now Hubitat cant turn off 20 of the max 232 lights...
I have tried every tip in This thread, All devices work good and turning on off manual is instant. I dont mind if turning 20 devices takes 20 seconds but now always missing devices.
I like Hubitat but i hate if i have to buy all new other brand /radio devices to get it work. I have a few shellys and they never miss! All lan devices also never miss , Only zwave
I cant be the Only one with problem....
Soon Either my zwave devices or my Hubitat Will go in historyelectronicsbox if i dont get it to work and i have tried everything now...
Now i have to go up from bed turning off 3 light that didnt turn off at night mode... Goodnight
/ Mattias
Hope this thread is still active. I am having the same exact issue and have literally tried any option that is out there. Have you figured out what caused your problem?
You would be far better off starting a new thread and describing your issues in detail. This was from over a year ago, and lots has changed on Hubitat since then.
Download the Hubitat app
