Hi,
Updated my Hub C7 to 2.3.8.134 (was 3 or 4 versions behind) and Virtual buttons with Rules stopped working correctly, Even Rules with physical switches stopped working.
for Example: I have a rule that says, if a specific switch is on for 60 minutes turn it off.
It just stays on all day...
Help? 
Open the rules impacted and click Done to make sure all the subscriptions are set.
If that does not work, turn on logging for the devices and rules, then post logs (screenshots).
What rule program are these in? If in RM, what version?
What drivers are the devices using? Many of us have an issue with some changes made to the advanced Zigbee drivers in .134.
Do you use Private booleans in your rules? I had to create a debugging dashboard with buttons to reset PBs because sometimes during a system reboot or update the rule would have finished because it was running during the reboot waiting for an event which never got logged because the system was rebooting.
Hi,
Sorry for the late response, there were 2 platform updates i tough might fix it but it still fails to work.
Following your advice, I Opened the rule, clicked Done and tried again, still not working.
I turned logging on and this is what i see on the rule:
app:452024-04-22 08:29:05.532infoAction: Off: Living Room Light, Dinning Table Light, Living Room, Samsung TV82, Kitchen Light, Balcony, Balcony Light
app:452024-04-22 08:29:05.505infoTriggered: Good Night switch on
app:452024-04-22 08:29:05.503infoEvent: Good Night switch on
app:452024-04-22 08:22:14.922infoInitialized
attaching the rule itself (Rule machine 5.1)
Thanks,
Lior
Hi, Thanks for the replay.
I'm using Zwave devices...
I don't know what's Private Booleans are so i guess not
Thanks...
Screenshots of logs are much easier to read.
Is that all it does is the first step then it just dies?
I have seen this before, on a hub that had a bunch of defunct LAN/IP integrations that were hammering offline IPs. If the hub is overloaded it can cause RM rules to die part way through execution.
While the rule of turning off the boiler after 1 hour doesn't works i've noticed that additionally the boiler switch on the dashboard stopped working.
I've reseted the hubitat hub and it started working again, pressing the switch button on the dashboard works fine,
wen't to sleep, woke up and the button stopped working again.
so i know the button is defined right and the dashboard has access to it (it was working fine for years) but now i can't press it on the dashboard and the rule stopped working.
Please advise,
Lior.
If a reboot fixed it then it sounds like your hub is overloaded. What sorts of IP /Lan /cloud integrations and devices do you have?
Almost all devices are Z-wave.
I've got 6 IP devices which are all reserved ip and set correctly on the hubitat device (1 Yamaha receiver, 1 tv and 4 Chromecast devices)
in the logs there are no running jobs and no hub actions.
few basic scheduled jobs (attached picture)
when i enter the "Boiler" device on hubitat i can press "on", i hear the boiler switch turning on but the "Current stats" stays " * switch : off" like hubitat doesn't knows i've turned it on...
How do i find whos the blame? 
So i found MANY debug warning in logs for a device and I've disabled it, hubitat worked fine for a day and started lagging again.
searching in logs I've found another device filling the log with errors, what can i do about it? (pretty sure all started from some update)
Turn off debug logging for that device. Those are all debug logs.
How do i find why is my Hubitat stops responding well after some time?
I Can't even use the Dashboard, pressing a device does nothing until i reset the Hubitat...
Can i downgrade firmware?
You can revert the platform using the diagnostic tool: Hubitat Diagnostic Tool | Hubitat Documentation
If you want to download an older major version you can use this endpoint, where 237 = 2.3.7, replace with any version number you want. Once downloaded it will show up in the "Restore Previous..." button in the Diag Tool.
http://HUB.IP/hub/advanced/downloadPlatform/237
LAN integrations like this are always suspect. Did you try disabling these, and see if there was any improvement?
The other thing you probably should do is post a screenshot (preferably on a desktop computer) of your Z-wave details page, all columns and all rows. Take multiple screenshots if needed. Maybe someone will spot an issue that is crashing your hub.
You also should list what these Z-wave devices are, brand and model, and how many of each. Some devices seem to have issues and can significantly slow down the hub when they misbehave.
There was a receiver integration I remember reading about here in the past that could be a problem. Don't remember if it was Yamaha or not...
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
