See which of my Zigbee devices are repeaters?

No C7 with zwave active, but seems to go further on it.
Sorry for the thread hijack.
Will post another, and more specific.

1 Like

Is this possible in Zigbee 3.0? Like, could a hypothetical future version of HE display a table of Zigbee devices in the settings, including indicating which are repeater-capable (whether or not they're currently repeating)? Or is it a fundamental limitation of the protocol that the hub can't access that information?

I think it require another zigbee radio to do something like that. @mike.maxwell probably could explain it better than I could.

I guess my question should be how would a novice know about that. Knowing your mesh health is very important when things aren't working. When I tried to make the leap out to my detached garage with my zigbee network that kind of info would have helped. At that point I did not know how useful the forums are.

To that point the forums are great but the average user isn't going to understand alot of this. I've had to pull hubitat out of 2 peoples houses because they couldn't understand how it worked. I downgraded them to Alexa only, which we all know sucks as stand alone.

My suggestion would be something like the battery monitor in the dashboard but using a graphical interface showing signal strength like your wifi router or cell phone. People would understand that.

Mesh is complicated. Having a signal bar won't help an average user because it's dynamic and having the strongest signal doesn't mean best route back to the hub.

1 Like

Everyone in Ha has to educate themselves to a degree. Every one of your questions can be answered in the manual. Or simply by asking others. There is a learning curve to everything. People are going to be willing to learn or not. I think HE is novice friendly for setup and using the basic apps included. Learning about how z-wave and zigbee works is another thing. Lots of people know how to drive a car but don't actually understand how the motor works

2 Likes

I mean, this is an argument that goes back to the earliest days of software. Which functions should and shouldn't be exposed as information or options to the users? What should be visible vs discoverable vs in the manual vs totally secret? I've been part of many such debates, and rather than saying "you can't expose everything" or "power users can figure it out if they need to, read the manual", I tend to want to ask "Is the tradeoff of adding this one more thing worth the clutter?"

I think in the case of Zigbee connectivity and a little bit of mesh info (at least the stuff available at getChildAndRouteInfo), my opinion is that yes it's worth the clutter to have that info discoverable from the UI, probably from Hub Settings. That's the decision HE made for Z-Wave, after all. It feels inconsistent to have it for one but not the other, and it's pretty useful info. The Zigbee info page is not so cluttered that it can't handle this additional info (or at least a link to it).

But anyway, I wasn't here for the debate, I was here to learn how to find the info. I'm glad I did; thanks all! Hopefully this thread will be here for the next person who is wondering, if in fact nothing is changed to make it more discoverable. Cheers.

4 Likes