Good to know. I'll give a power off a try first.
Is there any way to easily map device ID to name (either give XCTU a list of device names, or export a list from both Hubitat and XCTU and merge them)?
Kind of a pain to look up each device one by one. =)
No sorry it is a pain.
In XTCU there is a feature request you can send to XTCU developer which I did but the more people to request this feature the better chance they will impliment it.
what feature did you request? being able to import names?
also not 100% sure how to actually interpret the map. Some lines have numbers, some are just ?/?, etc.
Now I'm thinking you're right, and I think I'll just unpair all the xiaomi devices and unplug all my non-Tradfri outlets and repair. Shouldn't take that long. Might wait until my last Xiaomi temp/humidity sensor shows up though.
Wonder why this functionality (mapping peers, etc) can't be built directly into the hub?
+1 It's such a sorely needed feature and I can't imagine it's that difficult to do.
It is. 
See this post by Mike in another thread. (Of note, it doesn't work on any of my hubs, but I seem to be the only one.)
You’ve never been alone; only raw html for me. 
Hmm. I have raw text for it. Interesting....
I get error 404
The page requested could not be found.
On both of my hubs. 
for the life of me, I still can't get Xbee3 to finish pairing. It just remains at initializing and then shows up as a "Device". it seems like it never fully pairs since it seems to take forever to scan my network (it finds routers quickly, but edge devices take until they report in with a status. =/ Also a Xiaomi contact sensor was pairing with the Xbee3 and then dropping off nearly immediately and requiring repairing with the Xbee3 off. Seems like it's not fully being added to the mesh. =/
dang. gets worse. I removed it from my HE as a discovered device, and can no longer get it to join. Did a full "defaults" setting for the Xbee3 and then reconfigured using NoWon's settings, still won't discover. =( This is with firmware 1006... =/
Hmm... something is clearly not right. since HE says the Xbee3 isn't part of the network, but if I got into XCTU and hit scan network, it shows nodes being detected. So the Xbee3 still thinks it's part of the network. =/ How do I convince it it's not (that's probably why it's never going into join mode)?
You know if it's still part of HE by open up your Zigbee log page and let it run for a while. Your will probably get a device with 4 hex code but not on the HE Zigbee device list.
It's correct to see xbee as a "device" because there is no driver for it.
Sorry, I know there is no driver. What I’m saying is it never finishes the device found stage where it says “initializing”.
I’m going to see if I can break out the commissioning pins to get it back into pairing mode unless someone knows the commands for the xbee console.
have you updated the firmware on the Xbee and what kind of usb board are you using?
Is it connected to the PC when you are trying to join it or remotely?
If connected to PC have you tried rebooting your pc then joining?
Has anyone tried this that's having problems adding it to HE?
I did update firmware (1006). I have not rebooted host computer. It seems like the Xbee3 still thinks it's part of mesh. According to Xbee3 manual, I need to either break out the commission pin (to a button, or just short it, which is DIO1 according to XCTU), or issue a command in it's console to get it back into join mode.
Will try something tonight.
I would try this first
If it is showing up as part of the mesh in the scan then it has already joined just Hubitat didn't add it.
I had it happen once and I am overly paranoid worried that it would not work correctly.
So I actually set the Xbee settings for an end device (see first post) and then put hub in pairing mode and added the Xbee as an end device then removed it and reset the settings back to a router and readded back to Hub.
But that was a long time ago and it was a pain. I think just using jrfarrrar suggestion and leaving it or then deleting it then adding it again would be faster. You will know that it worked for removing the device if after you create a device and add the address's then delete the device and you then do a XTCU scan (before trying to add the Xbee again).
The scan should not see anything other than the Xbee.
Then put the hub in pairing mode and add the Xbee again.
(to be clear you should not need to change the Xbee settings to an end device if you do it this way)
will have to try that tonight. I'm remote, and for whatever reason my Xbee3 module now requires me to hit the reset button every time I add it to XCTU now. =( Not sure if it's 1006 or not.
I can't get it deleted from HE because it's already been deleted. The Xbee still thinks it's part of the mesh though. I can't find any way to send the command to the xbee to forget it's network, or restart pairing. But again, remote, and can't get it back into console without readding. =(
I see what you're saying though. Add a virtual device and plug in its info to that Virtual Device, then delete it from HE and see if that gets it to actually leave the network?
yes exactly I never narrowed down the cause (I suspected computer reboot fixed it) and it was a long time ago and only happened once. I have 3 different usb adapter boards and 4 Xbee3.
Also double check your Xbee settings a mouse wheel scroll can easily accidentally change one of those settings.
Download the Hubitat app
