This one has me stumped. I have been migrating devices to a C8 and it has been running OK for a few weeks. Today I updated from 2.3.6 to 2.3.8.123 and six of the 23 Zigbee devices dropped off.
One of those devices is a Sengled light that was still responding to a switch it was bound to. I tried to use the switch to toggle the bulb on and off to force a factory reset. It didn't go into reset mode nor did respond when doing a Zigbee pairing. Surprisingly it started responding to the device driver again.
Then I looked at the log files and everything is showing in the filters as the device driver name rather than the device name.
For example, the bound bulb mentioned above is dev31. It is named "KTN center" but in the filter section is it "Advanced Zigbee RGBW Bulb". You can see that all the bulbs are listed the same. The only things showing up correctly are non-Zigbee entries. For example, all the ones with a are groups.
Have you tried hitting “configure” on the device page, or changing the parameters like the various “transition time” settings to see if that fixes the issue. A while back I had to do this with a Sengled bulb to get it to respond to on/off commands. Specifically, I had to change the parameters to different values and save them.
This is probably the solution. I seem to recall that there was a JVM change around the start of 2.3.7 or 2.3.8 and I had a few devices that the preferences seemed to get jumbled on after updating.
You can see that it is still listed under the driver name. I'm not sure what the group messages are. If it is related to Zigbee binding then that light has never been bound to a switch.
If you are referring to the devices that dropped offline then I can't connect to them.
I did find some other information. The light that I reported as coming back online wasn't actually offline. It turns out that the motion sensor dropped off the mesh. The sensor is on a C8 pro and I now see that the hub is also showing the wrong names in the logs.
My old hubs (C4, C5, and C7) are not showing this.
It is possible that the dropped devices might be related to two hubs on channel 20, although they have run for several weeks without issue. That doesn't explain the drop on channel 25. The C4 and C5 will be decommissioned. None of this should have an impact on the logs (db?).
I did factory reset two of the bulbs and they rejoined fine. The three exterior lights I have to get the ladder out to reset.
Just to be safe, I change the zigbee channel to 26 before disabling the radio, since the radio doesn't actually shut off. It might not matter much, but it can't hurt.
Sorry, I missed that. Have you tried @bobbyD ? That's not something that I have ever seen happen.
EDIT: Perhaps that could happen if you just added several of the same devices, or deleted and rejoined devices without naming them. You could try doing a reboot with the log purge option checked and see if that fixes things.
I was thinking of purging the logs on one of the hubs. I wanted preserve at least one full log history in case we need to look back. I just haven’t tried it yet.
I definitely named them when I joined the devices. I’m rebuilding everything on the new hubs after years of learning, experimenting, and a failed radio. The naming convention is something I settled on after a lot of trial and error.
Reboot, reboot with DB rebuild, and firmware update all didn't help.
As noted above I didn't want to do that in case we needed to refer back to something. That was before I noticed that the C8 pro was also having the same issue. I just purged the logs on the pro and it is working again. I should have tried sooner.
While writing this I also purged the C8 which has the bulk of the devices.
center" but in the filter section is it "Advanced Zigbee RGBW Bulb". You can see that all the bulbs are listed the same. The only things showing up correctly are non-Zigbee entries. For example, all the ones with a 
are groups.
