On one of my hubs, when I look at the zigbee child and route info screen, I see one entry I don't understand:
status:Active, age:64, routeRecordState:0, concentratorType:None, [Xavier Bedroom Smart Vent, 17D7] via [null, 0862]
"null" doesn't seem good... And checking my zigbee details page, I have no zigbee device with an address of 0862.... However the device listed is talking to the hub, as I see events show up in the Zigbee Logs from it.
Any thoughts?
I don't have a clue, but I also have a null with a unique address show up occasionally. It may be around for 2 or three days and then gone. A little disconcerting to say the least.
Side note, I will say that my 'child and route' info screens seem to work 100% of the time on both hubs now that I moved half of my zigbee devices to another hub...
Before, when I had all devices on one hub, most of the time the 'child and route' info screen would just show HTML and no results. Sometimes it would work, but usually not.
Now it has worked every time I look (which is daily). Does that make any sense @mike.maxwell?
The only time I've not seen it work across 5 hubs is when zigbee has been disabled.
Hasn't really been a priority to sort out.
No worries.
Just wasn't sure if it was a sign of/correlated to some other internal loading or performance issue. And I thought it's weird that it works better (100% so far) now that I halved the number of zigbee devices per hub. Same devices, same drivers, just half as many.
It working, or not working, really doesn't impact my use of the hubs. Even when that screen wasn't working, my zigbee devices worked just fine.
What device counts are you dealing with?
Not what I would call very many -
Hub 1 - 24 zigbee devices (3 kwikset locks, 4 ikea outlets, 1 contact sensor, 16 ST moisture sensors)
Hub 2 - 21 zigbee devices (4 ikea repeaters, 4 keen vents, 13 xiaomi temp/humidity sensors)
@mike.maxwell do you have any idea what the phantom null device might be?
Do you have an Xbee or anything added to your network? Or have you ever tried to add any device (probably a repeater) that got stuck at "Initializing"? I saw "null" once with a DNI that matched that of my Xbee after I tried to add one and it got stuck at "Initializing" (XCTU still showed it as part of my network, routing to the coordinator and with the matching DNI). I could imagine something similar happening with any device that got added but stuck at "initializing." I'd wager a guess that "null" is what it shows for the device name/label when it's not in the hub database (and therefore doesn't have one) but is somehow on the network (as my Xbee was).
I also used to see raw HTML when I went to the getChildAndRouteInfo page until I reset my Zigbee radio and re-joined everything (not something I'd normally recommend). I have about 50 Zigbee devices, so well above the mid-20s where you began to see problems, but still probably far from a a large Zigbee network. This time, somehow, I got the Xbees to join properly, however. 
(Getting those devices reset was a bit of work and I'm still not sure exactly what I did provided the solution.)
I have noticed this from time to time on my network. I'm pretty sure it is the address of a device that is no longer responding to commands at that address, which would explain why no devices in the device list have that address. For me, when I see the null device listed, it usually means that one of my peanut plugs has dropped off. I have around 100 zigbee devices and for some reason one of the peanut plugs will drop off the network every week or two and I have to rejoin it.
I don't know. But on this hub I have only ever had four repeating zigbee devices - it is brand new. And all of them show up as repeaters in the list, and all four show up in the zigbee details page too. so I have no idea what the null device would be.
Like I said, everything is working on the hub so it must not be that big of a deal. Just seems weird.
I think that happens if one rejoins at a different address, maybe after a power disruption to the device. I don’t know if it will clear without a reboot.
We had a bunch of power blinks/outages a few days ago... Could have happened then.
I’ve had my Sylvania bulbs switch addresses after a power outage, but I didn’t know about the routing table because I was on SmartThings at the time.
I had a "null" show up recently when a Zigbee device died, and I deleted it from my Devices without removing it correctly.
Turning off the Zigbee radio for 45 minutes or so and then turning it back on made the "null" go away.
Download the Hubitat app
