Support didn't find anything causing the issue in my logs, recommended that i start removing apps to see if that clears it out. It's strange, i see the logs stop each evening overnight, where the hub becomes unresponsive, including 8081. Rebooter last night reforming a reboot prior to the event didn't even keep the issue from occurring later on.
I'll keep removing user, then built-in apps. If that doesn't fix it, i'll factory reset and start over. I am still liking Hubitat over ST, but a bit frustrated that this popped up on the 2.2.5 FW update a couple of weeks ago.
I'm still having the issues 1-2x a day, where a power cycle is needed for devices to become responsive via modes, rules, or Alexa, be able to use dashboards, and to log into the hub (inc 8081). I think i'm going to try to factory reset this weekend and start over from scratch.
My apps now are down to using 6 simple automation rules, mode manager (which i've found is a pain to adjust if mode didn't change due to lockup), and 2 notifications (leak/battery).
I've removed all the user/ & built in apps, besides the 3 above.
While I'm still i would say on the lower end of devices, is it best to exclude all the devices before factory reset, and then re-include?
Main Device Types/Brands
Zooz/Innovelli Switches/Dimmers
Iris sensors
Samsung Leak Detectors
Sengled Zigbee bulbs
ZSE40 Zooz 4-in-1 (already removed, getting a stick to include again)
ZSE25 dual switches
The hub is back on 2.2.4. For some reason it was not accessible from support tool while running later versions of 2.2.5, and logs don't show any reason.
@spartysh32, please let me know how 2.2.4 fairs. If things don't freeze on it, I'll be taking a closer look at code differences. The freezes manifest as "nothing happens for several hours" gaps in the logs, there's no additional information otherwise.
Do you happen to have dashboards that are viewed on an Amazon Fire tablet by any chance?
@spartysh32
I am interested to see if you were able to resolve your issues and upgrade to 2.2.5 . I have been experiencing very similar problems in my efforts to upgrade to 2.2.5.131 and have had to revert to 2.2.4.158 in order to keep my hub running. I have been following several threads on this topic and would like to know if you have been able to identify the problem and resolve the issue.
I'm still sitting on 2.2.4. I have a support ticket open, and am planning to wait for a response before trying to update to 2.2.5 again. Strange that it only affects a few.
Thank you for your response. I too have reverted as the 2.2.5 platform is unstable for me. As it does appear that we have a couple of devices, Zooz ZSE40 motion sensons, Zooz switches and Sengled bulbs, in common, I wonder if these could be where the problem lies.
I have a C7 on 2.2.6.137 and have noticed that starting a few days ago I am having to do one or more reboots per day. If I don't anything going through the hub stops working. I am using all Inovelli switches except one Aeotec Smart Switch 7. I have 24 Red Dimmers, 5 Black switches and 5 fan+lights. Switches that control the load still work and any switches connected via an association to another switch still works. As soon as I do a controlled shutdown, reboot it all starts to work again for some hours - but only for some hours.
I did have a ghost earlier that I was able to remove quickly. I also see one I didn't name (0x51, (081)). After going through my list of devices I don't see one I didn't name, but I could be 100% positive if I could see what DSK was associated with the device. Is there any way to find that out in Hubitat without say pushing the paddle of every device and looking at the log? It seems the DSK has to be stored somewhere in Hubitat that can be looked up.
So while I only gracefully shut it done and rebooted once in the last week, and that was only because I was installing a switch, I think I’ve discovered the problem may likely be an extremely slow response at times from the hub vs. it not working at all.
Since I never know when a button push will work or not, I haven’t timed them, but it feels like 10-30 seconds at times before a light turns on. It is certainly long enough that I’m standing there wondering if the light is ever going to turn on. This is limited to using the Inovelli red dimmer config button (which is a button 7 push) and/or using buttons with no load but have rules to control lights or multi-taps. Lights that directly turn on a load are no problem. As mentioned before, I only have 1 Rule Machine rule, I have removed security from all of my devices and I don’t see any ghost devices in my Z-Wave listing or Devices listing.
If there is an invisible ghost I don’t know how to find it/kill it. Do I need to air gap and/or throw the circuit breaker on every device? Would a Z-Wave repair help? I just got 2 Aeotec Range Extender 7s a few days ago, and they are connecting directly to the hub, but so far, nothing is going through them. As there seems to be 2 very distinct schools of thought about ever running a Z-Wave repair I’m letting them be for now to see if the mesh self-adjusts itself.
