I think I have asked this before but never got an answer from the community? @dandanache great mapping tool used to show all 68 of my devices.
Since I had some ZB issues a few months ago I usually have about 10 that fail to populate.
I wonder if my ZB network, though running fine with these devices, gets a little corrupt? Not enough to fail function but enough to mess up the mapping app?
I have to delete the devices and re-add them whenever they occur to get them mapped.
Bit of a pain as we all know, adding them all back into the automation scripts, Dashboards etc.
Status Devices Config
Addr Name
-- click here to search device --
23A8 928 Presence
B3C7 Doorbell
2CB2 Ensuite Motion
539E Freezer Temp
E69A Garage Motion South
F506 Kitchen Motion
774D Laundry Room Water
7275 Living Room Motion
B4BE Main Bath Motion
22DC Staircase Light Right
70F1 Staircase Motion
8202 Workroom Motion
The app does not talk to battery-powered devices, cause they are probably asleep and won't respond to queries (radio is off 99.9% of the time to conserve energy).
The app talks only to mains-powered routing/repeater devices and asks them the list of other devices they "are friends" with. This list includes:
other routing/repeater devices that are in their radio range and can be used as first-hop when relaying messages to the hub
battery-powered devices that use them as "parent". These battery-powered devices only talk to their "parent", but they can select another parent if the current one is not in range anymore, or their radio signal becomes weak.
If a battery-powered device is not discovered by the app, this means that the routing/repeater device that acts as their "parent" is misbehaving in some way:
they are offline or have other problems - a power off/wait 1 min/power on should fix this
they refuse to respond to the query issued by the app (Zigbee spec before 3.0 says that responding to this type of query is optional) - These devices are colored magenta, and I would personally remove them from my mesh
There are also some battery-powered devices that are just "bad children" and deserve a spank . Children devices are supposed to check-in from time-to-time with their parent device, and when they don't do that (probably to conserve even more energy), their parent would just remove them from the list of children. Most notorious are Sonoff sensors and buttons, that I replaced with other good behaving alternatives (mostly cheap IKEA stuff).
You don't need to remove them and thus break your automations, this is torture! Just start the Zigbee pairing on your hub, and then put these devices in pairing mode. The hub would say something like "found already known device" but a pairing process still took place. When doing this, the battery-powered device will select a new "parent" based on the strongest radio signal available in the mesh.
Thanks for the refresher.
Through all myt ZB issues I have found that re-pairing them never works.
Yes, the are always Found and re-added but they just remain in limbo until I Delete and re-add.
This is mains powered but it still doesn't play until the 'ol Delete. 22DC Staircase Light Right.
As a suggestion from other meembers during my ZB crash and ongoing issues I removed all my powered non-3.0 devices and put them on battery so I have nothing but powered 3.0 repeaters now and they are the only things talking to the hub.
So sad, before the issue I had 100% of my lovely dots on the map.
Have the hub off for 20 minutes right now just for giggles.
I'll see with anything changes.
Not sure if this will help, but, if these devices are mains-powered, you can try to click the on the Zigbee address field. This will trigger an interview for that specific device:
I only have one and I did try that a while ago. It interviews but doesn't change the map.
The only thing I find that works is to delete the device and add it back.
Too much work to reassociate 10-12 items just for the sake of the map, sadly.
I like my map.
The Tuya repeaters are very strong so they are ZB magnets.
I lowered my hub power to 8 so nothing connects to the hub.
I also join any device at the location so it will always see a repeater first.
There are still 12 that won't show up so it's not that impressive
928 Presence
. Children devices are supposed to check-in from time-to-time with their parent device, and when they don't do that (probably to conserve even more energy), their parent would just remove them from the list of children. Most notorious are Sonoff sensors and buttons, that I replaced with other good behaving alternatives (mostly cheap IKEA stuff).
