2.3.1 was a huge improvement on my C7, most notably the zwave firmware update. I have a ?medium? sized zwave network.. around 60 zwave and 15 or so zigbee. A handful of rules and simple dashboards, etc.. meshed with a C4 and shared with home assistant. Prior to 2.3.1 the zwave would bog down, stop responding and just plain suck. The hub itself would freeze and stop responding.. even the diagnostic web access would go dark.. had to pull the plug and reboot.. this was maybe once a week or once every two weeks.. The mesh is solid and has always been.. the firmware update to the zwave was a huge improvement.. when 2.3.2 hit last month things have gone backwards.. not as bad as before, but there is definitely something off.. no real new devices or rules have been added.. and the last 3 weeks I have had to pull the plug twice now.. anyone else notice anything with 2.3.2?
For me, things have definitely slowed down, but I was blaming it on HubiVue calling for updates constantly while I have the app open.
That and a new water sensor that keeps dropping off (probably from the giant metal tank and metal leak pan).
I have not noticed anything. I would suggest checking Past Logs, App Stats, and Device Stats for anything unusual, and think about if you've changed anything else since 2.3.1.
I have not noticed any issues either - on my C7 & C5's.
I have been getting some noncritical Zigbee lags in sensor responses some mornings but not sure that is firmware related and I haven't really investigated.
The z-wave firmware update and hub firmware updates are distinct, AFAIK.
So I agree with @bertabcd1234 if you’re having issues, you’ll want to drill down a little more specifically into what could be causing that to happen.
This is why threads that start out like “I noticed my hub slowed down recently…” can be difficult to help troubleshoot without more details. There are many reasons why each individual’s hub could run into some kind of problem, and it could be a different reason for each user.
Whatever the underlying problem, repeatedly pulling the power plug can result in hub database corruption, which will only make things worse.
If you have to power cycle the hub like that to get it responding again, do a soft reset and restore the hub from a backup. Then continue troubleshooting.
Yeah if you must reboot regularly then maybe consider using a watchdog app instead. Usually needing to reboot points to resource issues like memory or networking (cloud apps, frequent polling etc). Also check your network interface settings - there were some issues with it not being set to auto-negotiate (Settings/Networking) but is probably unrelated to your current situation.
Haven't noticed any slowdowns on a C-5 or a C-7. Neither one has been rebooted since I installed 2.3.2.141 (the last 2.3.2 release). Their current uptime is at 19 days.
If anything 2.3.2 seems faster for me on my C3 and C4 hubs, no noticeable difference on my C7, no Z-Wave here though.
thanks for the comments everyone. I will try a soft reset to see how it goes.. one thing I forgot to mention was when I updated originally to 2.3.2 - it was an immediate difference.. meaning I changed nothing.
soft reset yesterday.. lets see how it goes.. so far everything is fine.. although one of my blind opening rules did not fire this morning.. but the rule that closes them when no one is home worked.. so must a been a glitch in the matrix.. lol
How's your z-wave table look?
No z-wave details page. Settings))z-wave details (screen shot all of it)
You shouldn't disconnect a mains based stuff like that. Between that and the ghost you will have delays in your mesh... The plug needs put back in or removed from HE altogether and that ghost should be removed. If you know the device that created that device needs to have its power disconnected, reboot the hub then remove the ghost. Or use a z-wave stick to remove the ghost.
I've had a similar feeling. Nothing specific that I can point my figure at, though. And, it mostly seems to be OK.
Just a general "things aren't running as smoothly as before" feeling (once in a while, stuff just doesn't respond, etc.).
As for "ghosts"--the new release seems to make some of my devices (battery powered usually) show up as not having routes. However, when I do a refresh and/or kick the device back to life, it pops back just fine.
Also, the past release or so, my "memory alert" notifications are popping pretty regularly on my "apps but no devices" hub. I know @gopher.ny said the memory stats were adjusted in some of the recent releases--and I've not tried to figure out if that's the issue or not (reboots seem to make it generally happier and when it trips my memory alert, it reboots that night; So, I figured that was a reasonable thing to let happen).
These are not ghosts, then (though this does seem to be scaring some people as much as ghosts do lately 
). A lack of routes in the Z-Wave Details table can be normal. The information is cleared on each reboot, so the device first needs communication with the hub. Then, it needs to wait for the table to actually get the updated information (I'm not sure what that schedule is, but it's not instant). This behavior is particularly likely with battery-powered devices, most of which (for Z-Wave) are are not listening for commands from the hub unless awake and only send things of their own as needed. No need to refresh or otherwise touch the device if there isn't actually a problem, which blank routes aren't per se.
Not sure about the other issues, other than that App Stats, Device Stats, Logs, and any changes you've made in your setup may be worth considering. There were some changes/improvements to Zigbee and Z-Wave serial processing, with staff noting the metering band-aid should no longer be needed in most cases, so if your problems deal specifically with those devices in things like Groups and Scenes, it may be worth revisiting such configurations.
Im too also noticed abit of a change, but ive also added quite a few new devices, im now at about 140 zigbee, 70 zwave and 20 wifi devices, and about 200 webcore piston rules.
Im starting to think i need to move to two hubs
This is one of those threads with a lot of misinformation in it, presented as if fact. It's done.
