Darn... You found me. 
Channel change and checking current repeaters and adding additional would be my approach.
1 Like
I would also power-cycle all the repeaters, since you don't have that many anyway; maybe one of them went berserk.
2 Likes
Thanks for all your help so far!
All the plugs and mmWave sensors were experiencing the same issue as devices that were directly connected to the Hubitat hub, even those in the same room as the hub. This indicated that both the repeater connections and the direct hub connections were unstable. Additionally, I was no longer able to pair any Zigbee devices directly at the hub.
Based on this, right or wrong, I concluded that the issue was with the hub itself rather than the repeaters. I realize now that I should have made this clearer in my original post.
Have you tried a power-cycle?
It is possible. We don't see this too often, but it is possible.
If you refresh the channel scan you showed earlier, does it get populated?
P.S. You'll see something very similar from the channel scan and the symptoms you've described if there was a single device spamming the zigbee radio.
Hey @jtmpush18,
Thanks for the insight!
I have to say, I got a good chuckle out of thisāthose are actually the exact plugs Iām using now! But I do appreciate the suggestion.
I completely understand and appreciate @aaiyarās suggestion (heās been incredibly helpful to me in the past). However, Iām reaching a "critical mass" of what I can actually plug in, given my householdās panel and outlet limitations. At this rate, I might need a second breaker panel just for Zigbee!
Oh, I know that approach well! Back in my IT operations days, when Novell was the star (long before Microsoft took over and then...), my team and I practically lived by that philosophyāwhen in doubt, throw more hardware at the problem!
Thanks for the idea, @Sebastien!
Both of my neighbours are pretty light on technology (mostly just basic internet users)āin fact, Iām usually the one helping them set up new TVs and troubleshoot their devices! Unless theyāve secretly outsourced a smart home setup to someone else (which seems unlikely, given how intimidated they are by mine), I donāt think thatās the case. But hey, itās worth looking into!
1 Like
Note Edit hit save by mistake.
Thanks for the suggestion, @danabw!
I changed the channel as per @bravenelās recommendation and am seeing some improvements. However, I havenāt tried pairing or re-pairing yet. Now, Iām just looking for more places to plug in additional repeaters! 
1 Like
Thanks for the suggestion @dandanache. This was my first line of defense which I should have pointed out in the opening comment.
2 Likes
Is a utility serving your are installing an automated meter reading system?
I wonder if that could be a factor?
1 Like
As long as it's not the monitoring version of ThirdReality Plugs.
Some have had issues with them being very chatty.
Edit: This is from a non-monitoring plug.
1 Like
Interesting concept. While I hope thatās not the case, I should mention that we have had automated meter reading for the past seven years, so I don't believe it would have a direct effect now.
In the US, these meters use low channel zigbee (i.e. < 980 MHz; channels 0-10). There is no way they would interfere with high channel zigbee (2.4 GHz, channels 11-26).
These are very spammy zigbee devices.
1 Like
Thanks for the heads up, @Ranchitat!
Iām using the Model P1SBP4Z, Smart Plug Gen 2, which does have monitoring, and Iām running the Third Reality Power Meter Plug v1.03 driver. From looking at the logs, I wouldnāt call these plugs chatty at all. In fact, over four hours, I only saw five log entries. Now, on the other hand, I do have a Fibaro Z-Wave Plug that could teach a masterclass in chatterāitās almost like it canāt stop talking! Despite my best efforts to quiet it down, Iāve had limited success. Just wanted to point that out, as I do have a real comparison for what qualifies as āchatty.ā
I believe the ones they use for Toronto Hydro are using the same band.
I haven't kept up on the status of the ThirdReality monitoring plug firmware/drivers.
Last I heard there was not much improvement in the actual number of monitoring events sent out to the ZigBee mesh by the plugs, just that some drivers were dropping them from being displayed on the hub.
Hopefully that's better now. 
They're fine. Got a dozen here. No problem.
Still, @DGBQ, if in doubt, you could swap them for inexpensive IKEA Inspelning.
I got one.
On firmware - v1.00.92. Very very spammy. In fact ~20% of the traffic on my z2m mesh originates from that one plug. The mesh has about 80 devices.
The ones I have output power reports every 10 seconds. Completely unnecessary and they are the most verbose devices on my mesh by a long shot. But still not a problem. They are on the compatible device list, too.
There is a lot of folklore surrounding power reporting devices somehow overwhelming Zigbee meshes but evidence of such verbosity being a cause of anything, let alone something like what the OP is experiencing, is scarce or nonexistent, AFAIK.
Regardless, if I was the OP I would spend $30 or $40 on IKEA plugs and remove that variable from the equation.
I used that driver for a while and it makes the "spammy" situation worse by enabling additional clusters and attributes (current, voltage, power factor, etc). Unless you really need all that, you might want to switch back to the system Generic Zigbee Outlet driver, then reset and re-pair those plugs. I doubt it'll fix your issue, though.
1 Like
