That's a while back and perhaps the platform is trapping really well now...
2 Likes
Yeah I broke a rule yesterday, and now have a persistent globe variable I cannot delete, by using ">" in the GV name. Don't do that.
1 Like
csteele,
Thanks for sticking with me on this fix. I FINALLY SOLVED the problem! Through a process of elimination it was None of the Suggested Solutions above. My Hallway Light Switch Device was the culprit. After adjusting a setting (about the time this all started) it was actually not functioning right. I never noticed it, because it would go on and off properly from the motion sensor trigger.
I set the Device back to factory settings and made sure I removed it from the ZWave network. I installed it back on the Network and the Hub now works just as fast as when I removed Hubconnect.
No Support ticket or anyone else would have been able to pinpoint this problem. I had to troubleshoot and eliminate rules, drivers, and user apps ONE by ONE until I could zero in on the issue. I just wonder if malfunctioning devices are causing so many other hub "slow downs"? Or it would just be a number of things and the only way to figure it out is to start from the beginning or where you left off, before the problem began. Anyway...thanks for all your help!!
3 Likes
As @april.brandt has pointed out multiple times, most slow downs are probably self-inflicted. I know the one I had certainly was - I force removed z-wave devices without excluding them.
2 Likes
Oh resemble that remark. This is why I try not to run any 3rd party apps besides what is absolutely necessary. (by my own preference) The trouble is that when something is malfunctioning, it will affect everything and the symptoms are hard to distinguish. My hub crashed twice in 24 hours this weekend. Found the culprit to be a misbehaving iris plug. Only because it happened to be the only thing logging at the time. It's headed to the drawer of shame.
2 Likes
Pay attention to that device. If you start to feel the pain again, that switch would definitely be suspect and if it acts up again, I would consider reaching out to the mfr and seeing if there is some warranty on it.
1 Like
Along with the pair of "Building a solid Z-device Mesh" documents we have, we need a "How to isolate a malfunctioning device that is adversely affecting your Z-Device network." 
4 Likes
Agreed.
One way I know of to make this happen is to use the PC Controller software. This also checks for "dead" zwave nodes.
It probably also can be done by zniffering.
However, both these methods are not suitable for the vast majority of Hubitat users - they are just too technical.
Although this is a major technical challenge, it's a VERY worthwhile pursuit for the Hubitat support people.
2 Likes
Just happened to me - a Qubino dual relay stopped responding and my main hub really slowed down. Had to force removed from HE, rebooted and ran repair - now things seem back to normal 
. Will be replacing with some smart switches.
1 Like
I would love a writeup on those methods
So I swapped the Qubino Dual out for a Zooz Dimmer and Switch now my UI is very fast. We'll have to see how it goes though.
It's interesting the serious impact a bad device (in this case 1 parent, 2 child devices) has on the system.. UI slow, delays in Maker API, erratic behavior of neighboring devices etc... makes sense of course given the technology in play but wow. I was fortunate enough that the Qubino suddenly stopped working with my "rules" or responding to UI controls so it became kind of obvious. If it had been just a wee bit more functional I might not have discovered it for a while..
4 Likes
How would the PC Controller software find the problem device in @erktrek's case? What process would he run?
So I have both a Z-Stick which I use for the controller software and a UZB3 which I do zniffing on.. With the Z-Stick I've found and removed ghosts etc but thats it.
With UZB3 and Zniffer software I've detected slow network performance but the issue for me is trying to trace things down to the "bad" device. That's where I noticed my MS6's were slowing things down although now I wonder if the Qubino had something to do with it.
I am totally interested in this stuff and willing to play around and learn but someone else who just wants it to "work" might not be... this is the issue. How to make it easier for the average user I guess..
1 Like
I’ve got both too and you may recall me mentioning my MS6s are operating at 9.6, super slow. Aeotec has never come back with any more details, I need to follow up again. I have 3 Qubinos, 2 Flush 1Ds, and a dual relay which have all been fine. At least I think they have 
2 Likes
yeah thats right.. mine were too so probably not related. Bummer that no one got back to you. The Qubino just stopped working in HE all of a sudden - physical switching was fine. The impact to my Hub was severe. I dunno how they will ever be able to isolate something like that given the nature of Z-Wave but it's definitely a real performance killer.
3 Likes
A very real thing of a errant z-wave device causing havoc to the mesh. The taking down the entire hub is troublesome though. Sounds like something was deadlocked waiting for a response or caught in a loop trying to do something.
2 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
