My device has been working flawlessly for the last few years, but after recent updates, it's been nothing but a nightmare. The routines work sometimes, and turning on a light or switch is really slow and sometimes doesn't work at all
Thanks for your feedback. Unfortunately, without providing more specific details it would be very difficult for anyone to help you troubleshoot any problems you may have, if that is what you are looking for.
If you are just looking for ways to recover from some issues you may have had with the latest updates, then you are lucky, because Hubitat gives you the flexibility of managing your hub on your own terms. If the latest update doesn't work for you, you can always reverse to a version that worked best for you. Head to the Diagnostic Tool and select "Restore previous version".
7 Likes
IMO it’s always worth troubleshooting before assuming an update is the source of a recent problem.
There are many cases of “the update borked my hub!” reported here that turn out to be caused by something else after digging a little deeper.
4 Likes
OK. I too have been experiencing all manners of weirdness. BUT, I have figured out that this release, 2.4.3.127, on my HE 8 Pro caused all STOPped rules to start up. So, various debugging/seasonal/debugging/testing rules are running. In particular I have about a dozen "XMAS: Do this decorative thing" type rules that are running. Taking out the trash and seeing the lovely green and red porch lights did it for me.
So, yes like a previous release some time back, 2.4.3.127 turns on STOPped and maybe PAUSED rules too.
Hope that helps.
And yes, I will re-write these with new hub variables using the value of XMAS_MODE, DEBUG_MODE etc. since this has happened twice now.
Jay Tagging @bobbyD for visibility on this thread.
1 Like
Looking into that.
I have a bunch of paused rules, none of those unpaused themselves. That would have been very noticeable. Which doesn't mean something isn't fishy, just that it's not obviously fishy.
Edit: reproduced, fix is coming.
6 Likes
Awesome. Thanks Victor. Meanwhile I added a required expression to all of these rules that I've relied upon STOPping so this doesn't bite me again. For anyone wondering how to do this, I created a Hub Variable called XMASMode and set it to False for now. Then modified each of these rules like this:
3 Likes
I experienced the same after upgrading to 2.4.3.127 as reported as @wiegout. I use Keypad on a tablet to activate HSM when departing the residence. All heck broke loose after the upgrade. PIN codes went unrecognized and I began hearing announcements from apps that had been stopped but not removed or disabled during the course of developing the front end. Reverting to a previous backup did not resolve the situation. I subsequently reverted to the previous firmware version 2.4.3.123. In addition to reverting to 2.4.3.123. It was also necessary to go back several local backups in order to restore service. When I did hit upon a working backup, I did upgrade to the most recent version of firmware to verify that the update was indeed impacting rules. The update broke the rules and I repeated the above to get the house back in order.
So I've tried all that I've wiped the unit restore to a previous version some devices work and some don't rules are not working
The stopped rules issue has been resolved in firmware 2.4.3.131 (or later). The bug was limited to Rule Machine rules, it was a side effect of missing device subscriptions check.
4 Likes
15 posts were split to a new topic: Z-Wave Mesh Issues (ZWave devices unresponsive after platform update)
