Anyone else seeing a device with ID 0000(0) on the zigbee logging page? I noticed it yesterday and was having some zigbee device control problem for a few of the devices. I tried to change the zigbee channel to 25 from 12 and left it for the night. Woke up this morning and still couldn't control any zigbee devices at all so I changed it back to 12. 99% of zigbee devices are back to life again except for a couple of devices that wouldn't respond. Maybe those unresponsive devices went to channel 25 and still partying over there?
@patrick Any clue?
I don’t, I ran my logging for a couple hours and nothing like that showed up on mine.
Does a device 0000(0) show up in the zigbee info page? or device list page? (you can search on DNI in the search box, FYI)
Sounds like a device has lost its associated short code and if we can find what its 16 code is we could figure out which device and probably reset that device.
Changing the channel should get the others over, but if not, you might have to just do a reset / re-pair on those devices to get them to find the new channel / hub. Not sure if it will note anything in logging, yet. But the device should start reporting back in.
Thanks Patrick, I see no device 0000(0) in the zigbee device page. I’ll do the reset and re-pair the dead ones tonight and see.
So apparently clusterID 8038 has something to do with Management Network Update Notify 0x8038 . Seems to be on a 15 minutes interval.
00002018-03-15 15:47:20.149 profileId:0x0, clusterId:0x8038, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:255, lastHopRssi:0
00002018-03-15 15:27:39.821 profileId:0x0, clusterId:0x8038, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:255, lastHopRssi:0
00002018-03-15 15:12:20.417 profileId:0x0, clusterId:0x8038, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:255, lastHopRssi:100:
I am having the same issue trying to discover a ThingShield device. Nothing is discovered but the Zigbee log shows:
 2018-03-15 21:29:17.193 profileId:0x0, clusterId:0x8032, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:255, lastHopRssi:0
yay… i’m not crazy… now how do get rid of it team hubitat?
Do both of you have a ThingShield? Trying to figure out the commonalities.
I do not have a ThingShield. I need to test some more. I left zigbee logs page on for almost an hour and didn’t get any of those messages this morning. One thing i did last night was I moved my hub to a more central location in the house.
So the zigbee coordinator is always id 0000. So that means that device is the actual Hub. I don’t think this is anything to worry about in the Zigbee Logs.
Sorry, didn’t chime in sooner. If you have a really quiet Zigbee network, the hub will send one of those messages to the radio to make sure it is still alive.
Thanks for the clarification guys.
Just noticed this today. Glad I clicked search on the forums
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.