I'd love to get rid of this unknown zigbee device

[kahn-hubitat]

This is.usually caused by repeaters that dont purge their neighbor table.

[Inge_Jones]

This unknown however is shown as a direct child of the hub

[kahn-hubitat]

@Inge_Jones

This unknown however is shown as a direct child of the hub

Ok hard to tell from initial pic

[jimhim]

@Inge_Jones

This unknown however is shown as a direct child of the hub

I have a couple of those too. Have had them for a while. Hoping they go away someday.

[rlithgow1]

I wonder if doing a rebuild network would purge those unknowns. If not, then I would go with @kahn-hubitat 's thought about being in a table..

[Inge_Jones]

Things learnt so far:

1. Keep your repeaters to the same brand as far as possible. The battery devices are not as important as they can only wreck their own connections

2. If you move a repeater to repurpose it, it's not enough just to change its name - remove it from the system completely, reset and rejoin. Otherwise other neighbors in the system might cling to it when there is no longer a good signal.

I still have the unknown but I think I remember taking a leak sensor offline and thinking "I'd better remove the battery" and not getting round to it. Now I just have to find the little devil.

[HarleysWorld]

@Rxich

One other thing , some Zigbee devices deploy multiple end points, and I think that siren could be a candidate for having multiple endpoints. You could try disconnecting the siren and rerun the Zigbee Mapp app and see if the unknown disappears.

I've just experienced this. I have 4 unknowns in my Zigbee network after pairing 3 water leak sensors. Ugh... Is it worth getting rid of them and repairing or should I just leave it alone?

[Rxich]

@Inge_Jones

If you move a repeater to repurpose it, it's not enough just to change its name - remove it from the system completely, reset and rejoin. Otherwise other neighbors in the system might cling to it when there is no longer a good signal.

I was under the impression Zigbee is very good and quick at self-healing the topology. Now whether the Hubitat is somehow modifying that ability, in the name of "stability" I do not know, but these 2 Jedi would:
@kkossev & @dandanache

[Inge_Jones]

My hunch is it's more likely to be end devices at fault for not looking for updated routes, but who knows. I can't imagine how something in hubitat's coding can reach down the chain and tell the ZigBee devices how to connect throughout the network. It would be great if we had the power to decide what the topology should be but I can't see how that could be imposed.

[user1974]

After chasing 2 unknown's for a while, I finally cross referenced the zigbee graph devices against my list of devices. i had 18 total devices at the time, the graph also had 18 devices but 2 were "unknown". After checking off the known devices from my device list, the last 2 remaining devices on the device list had to be the cause of the unknown issue. They likely fell off the zigbee network but after a re-pairing of them, the unknowns were gone and I had 18 devices mapped.

[kahn-hubitat]

Easy enough to check if devicea have fallen off. Look at last message date in.zigbee details

For me all the unknown are not this case. They are old devices stored in another devices/repeater node list that are not purged. And as such dont effect anything.