Somehow my C7 is messing things up without my help - or at least I think it's without my help!
I have this thing which I have deleted repeatedly - it's shows up under devices as 'Device'.
It has a zigbee ID, and I'm clueless what it is, and where it is coming from.
I have deleted it multiple times now. and it stays gone for 1/2 a day... then out of the blue- there it is again.
How can I find out what this is?
I don't think the hub is "messing up"--it's probably this feature in action:
(I think. This was added in the past for both Zigbee and Z-Wave, then at least one of them got nixed, but I think that was Z-Wave--and that was also before the C-7 and it's new Z-Wave stack.)
So, what you likely have are devices that were once part of your Zigbee mesh but not reset/politely removed and are still sending messages on it. The solution is to find and reset the device. (A "remove" from Hubitat will usually do this--for devices that are awake at that time, which most but not all battery-powered Zigbee devices still are and most/all mains-powered devices should be. But if the device isn't heard from after a few seconds, the device will just be removed from the hub and it's on you to reset it. Sonoff, Xiaomi, and possibly Ikea are three well known brands I can think of that may require a manual reset--or removal of the battery, etc. until you re-pair them. But there are likely others.)
For physically identifying the device, many (probably not all?) Zigbee devices have their MAC address printed somewhere on the back or inside. This will match the "long" Zigbee ID on the Device Details page (not the Device Network ID--that's assigned by the hub). Manually comparing the two is one option if it's available--more than you'd have to go with for Z-Wave, where it's just the hub-assigned node ID! You can also probably make some good guesses if you think the above may have happened with any of your devices.
It's actually the auto-Re-add zigbee that got removed according to Mike. When the mystery device shows up , change the driver to Zigbee-Generic Device Toolbox, by none other than Markus. Then hit "get info" and then load your logs and observe what comes back.
Ah, nevermind, so I had it backwards. 
That's a good idea to find more information! (As long as the device responds, though maybe the "Device Details" will show you something too if not.)
okay - that was awesome. I've seen markus' Id routines - didn't know he boxed it seperately. Here is the result:
52022-02-25 01:09:56.010 am debugsendZigbeeCommands(cmd=[he raw 0x283C 1 0x01 0x0000 {10 00 00 04 00}, delay 2000, he raw 0x283C 1 0x01 0x0000 {10 00 00 05 00}, delay 2000])
dev:3652022-02-25 01:09:56.008 am debugrefresh cmd: [he raw 0x283C 1 0x01 0x0000 {10 00 00 04 00}, delay 2000, he raw 0x283C 1 0x01 0x0000 {10 00 00 05 00}, delay 2000]
dev:3652022-02-25 01:09:55.985 am debugrefresh() model='null'
dev:3652022-02-25 01:09:55.982 am infoupdated()
dev:3652022-02-25 01:09:52.727 am infoCurrent Preferences: [txtEnable:true, reversed:false, autoOffOn:0, logEnable:true, infoLogging:true, enableAutomaticGetInfo:true, debugLogging:false]
dev:3652022-02-25 01:09:51.677 am infoupdated()
dev:3652022-02-25 01:09:40.800 am infoStopped ALL Device Schedules!
dev:3652022-02-25 01:09:37.272 am infoCurrent Preferences: [txtEnable:true, reversed:false, autoOffOn:0, logEnable:true]
dev:3652022-02-25 01:09:36.431 am infoINCOMPLETE - DO NOT SUBMIT THIS - TRY AGAIN: fingerprint model:"null", manufacturer:"null", profileId:"0104", endpointId:"01", inClusters:"null", outClusters:"null"
dev:3652022-02-25 01:09:36.426 am warnOne or multiple pieces of data needed for the fingerprint is missing, requesting it from the device. If it is a sleepy device you may have to wake it up and run this command again. Run this command again to get the new fingerprint.
dev:3652022-02-25 01:09:36.425 am traceApplication: null
dev:3652022-02-25 01:09:36.419 am infoNOT IMPORTANT: Application ID is missing for the fingerprint, requesting it from the device. If it is a sleepy device you may have to wake it up and run this command again. Run this command again to get the new fingerprint.
dev:3652022-02-25 01:09:36.418 am traceModel: null
dev:3652022-02-25 01:09:36.412 am warnModel name is missing for the fingerprint, requesting it from the device. If it is a sleepy device you may have to wake it up and run this command again. Run this command again to get the new fingerprint.
dev:3652022-02-25 01:09:36.411 am traceManufacturer: null
dev:3652022-02-25 01:09:36.405 am warnManufacturer name is missing for the fingerprint, requesting it from the device. If it is a sleepy device you may have to wake it up and run this command again. Run this command again to get the new fingerprint.
dev:3652022-02-25 01:09:36.402 am debugGetting info for Zigbee device...
Hmm, no useful info, at least not any that I'm capable of understanding.
Any neigbors that might be using zigbee? or a smart meter in the house?
Next step would be packet sniffing with a cheap CC2530 dongle, TI software and wireshark.
More work than I'm willing to apply but thanks!
Download the Hubitat app
