I have a rule ("turn off at certain time") that only works partially. I have 10 devices in the app and about 314 of them do not turn off as per required by the app. All devices are Z wave and not LR. The problem is that the same app used to work properly before.
If you only have 10 devices selected, I'd expect fewer than 314 to turn off. 
Assuming you mean something like 3 to 4, it would be helpful to know more information, including:
- manufacturer and model of devices (and the protocol if that is not apparent from that, e.g., Z-Wave, Zigbee, etc.)
- Hub hardware and platform version (from Settings > Hub Details)
- A screenshot or description of your specific app and configuration
- Any errors in Logs or other concerning information you may find by following the guidance here: How to Troubleshoot Apps or Devices | Hubitat Documentation
I meant 3 or 4 of them
I figured. 
Please look into the rest of my response, including the additional information requested and the tips provided in the document above.
I will get all the info but why has it worked flawlesly for two months and suddenly not
Platform Version 2.4.1.170 , C8-pro
The sequence is as follow:
| switch | off | MH Recess foyer was turned off [digital] | digital | MH Recess foyer | 5/16/2025 22:19:53.299 | ||
|---|---|---|---|---|---|---|---|
| command-off | Command called: off() | command | off 21h30 | 5/16/2025 21:35:00.360 | |||
| command-off | Command called: off() | command | off 21h30 | 5/16/2025 21:30:00.171 | |||
| P.S. The final command that turned it off was done manually. |
A zooz dimmer
Here is what I think might be useful for one device in error
You are missing most of the information I asked for above, although some of that can be helpful, too. Was one of those "command-off" commands produced by your rule? (This would be in the table you copied/pasted; it's a bit hard to read without the column headings -- and knowledge of what you rule is named.) If so, the rule sent the command, and you can eliminate the rule as the source of the problem (so no need to provide a screenshot or description of the rule).
You'd then be dealing with a Z-Wave network or device problem, which the above document also has some troubleshooting steps for. Maybe start by identifying if you have any "ghosts." If you haven't tried it yet, shutting down your hub, pulling power for about 30 seconds or more, then reconnecting is the way to fully reboot the Z-Wave radio and can help with certain problems, though this isn't usually one -- but it should be harmless enough to try (if you do it this way).
Since you're on a C-8 Pro, it may also be good to know: did you switch to Z-Wave JS? If you aren't sure but see a button in Settings > Z-Wave Details offering you to switch back to legacy Z-Wave (instead of switch to Z-Wave JS), the answer is yes. Either one should work, but it's still notable.
1 Like
Thank you for the detailed explanations, I am relatively new to Hubitat, coming from Ezlo. I will verify your points and get back. But, looking at the log, there is a zooz double portable plug that triggered over 39000 times compare to the other devices that did trigger about 100 times. I disabled this device and will see if it had an impact on the apps.
What do you mean with "triggered"?
Also, if your "double plug" is a Zooz ZEN25, make sure your firmware is up-to-date, and consider including it without security when prompted. Some device firmware versions on the ZEN25 were known to be particularly chatty when added using S2, a problem I remember some C-7 users running into when the device was new (and still availalbe) but something I don't think would be different on the C-8/C-8 Pro. (Or for any device, see if there is newer firmware and anything in the changelog suggests it might help with this problem, and consider updating if so.)
