Battery powered sensors only.
Here's one result that confirms it (224 mentioned specifically at bottom of page).
Innr also confirms it in the Amazon product listing.
Granted, I'd rather manus simply spelled it out more clearly in their own websites, but I suspect they think that level of detail will be TMI / induce confusion for the new average-joe consumer they are pursing (i.e. the "works with google/alexa" person)? Just a guess.
1 Like
I bought a bunch of new Sengled plugs and minor-ly tested some of them, but went back to repeater-less.
I think the net might be more reliable, if they are not needed, and all sensors report direct to hub, which is on a battery.
Plus, I like the look of the graph. 
Of course, I don't know if you can even buy a repeater-less plug anymore, so as soon as I plug in a zigbee plug, there's goes my radial concept.
I've got some ZEN04's in the bullpen though, ready to go.
I have at least 22 mains powered repeaters, all 3.0 as far as I can tell from the specs. All direct to the hub is not an option for me due to the distance and construction of the house.
I started off with eWeLink smartplugs rated at 10 amps. However, after we had an ice storm that caused several power surges and an outage, several of those plugs were damaged. I replaced them with Third Reality smartplugs rated at 15 amps. Both the eWeLink and Third Reality seem to be good repeaters.
If you do decide on the Third Reality devices, be aware that they come in two versions. Gen 1 plugs do not have power reporting. They are less expensive and are ideal if you do not require power reporting. The Gen 2 plugs have power reporting. However, some have reported that the plugs send far too much data to the hub and can bring the hub to its knees if you have too many of them. Thus, get the Gen 1 plugs unless you need power reporting. I have heard that Third Reality is supposed to be releasing new firmware for the Gen 2 plugs that will allow you to set reporting intervals. Most of mine are Gen 1 plugs, so power reporting is not an issue.
1 Like
I feel like I have found the problem with the zigbee radio shutting off. I posted about it here...
Note: I have the C7.
I only have 1.2 devices, I haven't yet reached 3.0 and I see that this will be the way forward.
I went down to 40 because that was the device number they have downstairs. What I did was set up another room on floor 1 and I have separate zigbee networks.
I share more information about my experience. Since I have 5 hub c8 I have the ability to experiment.
There are two c8 hubs that were defective, both of them apart from having a zigbee off radio problem, also after two days the hub remains completely frozen, it does not even respond to a soft reset, I had to remove the power to restart it.
Clearly, and with this I do not want to detract from the people of Hubitat who continue working and posting for the project, but in my opinion, equipment came with a hardware failure, they already sent me a replacement and I have to file a claim to have them change me the other.
I think we have to wait and see how they solve this problem, which does not happen to all C8s. I have another C8 running for several days without a problem.
For my part I will have to buy another C7 because these work like a rock.
Look at this case. This equipment is faulty, in total I have 78 devices 30 are with batteries the rest are Zigbee 1.2 router
And the routines I have are simple, you occupy 0.35% of CPU usage. I don't even have an RM set up.
1 Like
Side question: what are you using to generate your mesh network map? The default one from Hubitat definitely doesn't look like that.
It's called zigbee-graph you can install it through Hubitat Package Manager
1 Like
This post spawned HE to include this capability:
1 Like
Still hanging in there...no Zigbee reboot since I booted up on June 14, so nearly three weeks.
Have had a couple of devices pause reporting briefly, but a Refresh on their Device page "woke them up" and they started reporting again.
So not perfect but worlds better than before, and my automations that rely on Zigbee devices are running w/out issue. I've also been able to join new Zigbee devices w/out issue, previously joining or re-joining Zigbee devices was an iffy proposition.
3 Likes
Ya every time i join or rejoin a device zigbee reboots. When i get home i am gonna have to request a new hub as well.
1 Like
My improved results have continued, thankfully. Everything continued to work perfectly while my wife's family was visiting last week, to the point where she even bragged to them about a couple of my automations. (Be still, my beating heart.) 
OT: I also added a couple Z-Wave devices (iBlinds) and setup and automations worked w/out issues.
6 Likes
Looks like things are starting to settle, I myself haven’t had any issues at all with the radio restarts or the transition to the C8 overall, but still feeling pretty bad for all the people that have, nothing worse than constantly chasing issues.
Let’s hope thing continue to progress to the point of having a rock solid home automation system like the C7 and prior iterations.
3 Likes
1 Like
My c7 seems to be relatively stable (moved almost two thirds of my zigbee devices back to that) but the c8 still seems to suffer regular reboots several times a day unfortunately. However with most of the crucial zigbee devices back on the c7, the reboots are now not of as great concern.
(Edit) But it does appear that the reboots are not as frequent. Only 6 over the past two days (rather than say, 6 in an hour which is more like what I used to have). Though this might have more to do with the fact that most of my zigbee devices have now been moved off it. Probably a good week or so before I finish moving all zigbee devices over to the c7.
I had the same experience. Started moving devices off. Reboots slowed. Eventually they stopped when I moved just about everything off. Doesn’t really solve the problem but now everything is running on the old C5 without issue.
So am I missing out on anything leaving it there?
1 Like
