I’m a bit confused by the logs, in your zll.db it looks that at some point ConBee 2 to ConBee 3 migration was done. But the logs show ConBee 2 with version 0x26780700 again.
Is that correct, or only old database data, which version is shown in: deCONZ → Help → About deCONZ ?
Other than that the logs indicate what the actual problem might be here. The local coordinator neighbor table only contains entries for sleeping devices but no routers and looks a bit small (only 8 entries), I’ll have a look in the firmware but would be good to know if ConBee 2 or 3 is at play here.
Ok thanks, I’ve forwarded my assumption to the firmware developer. The reason that your network stays silent seems to be that the routers aren’t queried, since this is done recursively starting from the coordinators neighbor table which in your case doesn’t contain router entries and is too small.
So this needs to be adjusted in firmware. The reason it works in older deCONZ versions is that these in addition also try to reach the routers via broadcast (without going through neighbor table first), guess I need to bring this back in the next version.
For a test this can also be done manually for a few mains powered devices by selecting the (yellow) node in the deCONZ GUI and pressing keyboard zero 0.
I’ve spoken with firmware dev, so the ConBee 3 has a large enough neighbor table. Also checked in my network here it looks fine and table has more than 8 entries and routers. Right now we’re not sure what is happening exactly.
Since you have a spare ConBee 2 perhaps it makes sense we maka a live sniffer session to see whats going on.
Damn that would have been helpful. Ok then I suggest we try if the yellow (router) nodes react when selecting them in the GUI and pressing 0 to see if they are reachable at all.