@mike.maxwell I had this issue before I enabled SDM API or Community (Enabled yesterday actually). So Maker I'll just remove that was an experiment anyway. MyQ sucks to remove, but I'll remove that as well and if that still doesn't work report back.
@SmartHomePrimer FYI I finished disabling all power events. But something came to mind while I was doing it. As I mentioned previously, I don't have traditional switches therefore the switches aren't actually powering anything and the power draw stays the same at whatever the switch draws (very minimal). So the default 10W change wouldn't have ever been triggered to report the power difference. But I did change them all anyway. After disabling all of the power events I still experienced issues hours later and also today.
@tony.fleisher My apologies I have monoprice z-wave recessed sensors and they are battery using the generic z-wave contact sensor. I think those are my only z-wave battery devices. Most are switches. I also forgot to mention I have a couple GE Outlets that are also z-wave, powered of course. And lastly I have 1 Zooz battery z-wave motion sensor using the Zooz driver. Hub Platform: 2.2.4.158
@Ken_Fraleigh Yeah for me it's definitely a z-wave issue and not zigbee as the zigbee devices appear to report fine and Hue control from the Hue app remains stable. And yes I agree with you based on my understanding of the way the zigbee and z-wave networks work. You can slow them down, but for devices to just not respond is different. There will always be times when communication is lost, but those times should be logged as z-wave is 2-way communication and the lack of the ACK should generate some log of that failure. DevOps/DevSecOps is what I do all day every day. Securing and optimizing backend operations for Software platforms is my life. That being said this is a different type of network and definitely not my specialty. But that's why I beg for enlightenment, because I want to understand from the technical level and unfortunately there's not a lot of information out there about it. Lastly, total devices I have about 1/2 of what you have in Hubitat (40 of them required changes per SmartHomePrimer), but a lot come from Hue and I have about 7 integrations on the Google side (Big A$$ Fans, Bose, Dyson, Kwikset, Rachio, Remootio, and Smarthings for Refrigerator, Oven, Cooktop, Hood and Dishwasher)
@rocketwiz Yes I've been tempted to get another hub, and break out rules on one and devices on the other. I guess it's just a matter of doing it. Also I know, from looking on these forums for months that there's probably not going to be an "aha moment". I expected most of the answers I've received and if anything they just provide motivation to go down that arduous process. I've even taken the time to write my own Shade drivers (I've had the issues with my drivers and the generic).
@Brandon I stand corrected I have a few. But this morning I removed 4 of them from the network. After removing those 4 I still had issues.
So here's the steps I have taken and things I noticed:
1 - Removed all power reporting from Inovelli Switches (no positive change noted)
2 - Removed 4 Monoprice Z-Wave Battery Contact Sensors (no positive change noted)
3 - Removed Maker API (no positive change noted)
4 - When operating blinds in the Master Bedroom this morning from a Kindle 10 containing a dashboard the blinds didn't operate as expected. The system locked up.
5 - After #4 I moved the blinds to a driver I made and off of the Generic, we'll see what happens but so far the blinds are working a lot better.
6 - The only GE Wall Switch that I have completely locked up at the paddle. It's one of the few that controls the lights via power "load" to the lights. I replaced that switch with an Inovelli switch today. I didn't mess with it previously because it's a GE 3-Way, but was super easy to swap.
So here's what I've noticed now after all of the above aforementioned steps. The network recovers on it's own, but it takes about 5 minutes. So when things start to go haywire I experience a brief time where nothing works, then all of a sudden it starts working again.