I experienced the same and reported it. It seems to have settled down, but still misses once in a while.
I think there is a difference in how HE initializes Zigbee devices and manages their sleep behavior. Could be the long/short polling intervals, but who knows. Just about every motion and contact sensor occasionally fails to report an event. Not that it's the devices fault. The LED's always flash indicating activity, but the hub never gets the message.
I completely agree, a read-only view of processes and resource utilization would be extremely helpful. There are those of us with extremely deep technical backgrounds that are capable of doing advanced diagnostics before involving support. It's just information, why hide it? Two thumbs up for that request!
I trust that wasn't directed at me. Speaking only for myself, I've exhibited an extremely high level of patience. How many customers would wipe and reconnect hundreds of devices to try to solve a problem that support had not even acknowledged? The reality is that most would throw the hub back in the box and return it.
I think the feedback myself and others have provided to the HE team should be useful, and welcome by their dev team. The platform has bugs. There's no need for you to suppress that knowledge, nor should the developers to hide from it. There isn't a coder alive that has ever written a bug free application, and there probably never will be. That kind of feed back, even if it may be hard to swallow, is the only way an application or platform can ever truly mature.
I have hundreds of hours in doing just that at this point. Having a large network brings its own issues and a certain implied commitment to increased troubleshooting time and effort. But there comes a point where one needs to reevaluate the value proposition that a particular platform brings.
Completely agree. The community here has been great and very supportive. There's no need to suppress any feedback, good, bad, or indifferent.
That too is correct. When I make a decision or agree to do something, I do it with 100% effort and dedication. The move from SmartThings to Hubitat is no different. There however remains a breaking point in every endeavor, where the value proposition of a project diminishes to the point where a project is no longer feasible. For me, that point will be reached when the end of return period of the hub draws near. At that point it will have been about 7 weeks of trying to get it running stable, a more than reasonable attempt IMO. In my attempts to get this working stable, I've purchased 3 xBee's as well as several motion and contact sensors, to track down issues and replace suspect devices. None of those efforts have paid off at all.
Anyhow, I received a confirmation that support was looking into the issue. I'm encouraged that the devices are still showing in the radio device list. I trust (assume) that means they're still in the sticks Z-Wave routing table.