Network gone bad, tips for sensible debugging?

General
1

I have no idea how things went wrong, but it appears that my deconz setup is in some sort of confused state. I’ve tried it with 2.29 and down-grading back to 2.23… no change. This is on a Windows 10 machine.

When I start deconz the diagram of device appears and does populate arcs between many of them. Some are battery-operated, so won’t always show connections at the start.

However, when I try to use the phoscon web app (either via web browser or android app) I can’t seem to control any of the plugs or lights? I can see that data has updated for motion sensors (lux level, temp, etc).

I’d very much like to avoid starting all over from scratch. As there’s at least two dozen devices and two other automation systems use deconz to reach them. Though I realize that software and configurations can get corrupted over time and it’s often quicker to just start over again. If it was just deconz alone I’d just reset the gateway and start the slog of pairing and renaming all over again.

Before I do that it seems like it’d be worth debugging things a bit to see if there’s something fixable.

Is there documentation on the Debug window messages?

2

Hello

So you have return, but can’t send command ? Have you tried using direclty the GUI ? or the API (without Phoscon) ?

Is there documentation on the Debug window messages?

IDK, but to start you can just use the “error”+“error_l2” and “info” + “info_l2” you will be able to see error about system, database, network configuration, lot of usefull stuff.

3

the error and error_l2 logs were showing nothing.

I solved this problem by noticing there were 0xE1 errors in the info_l2 log. Turns out the channel mask had all but 20 unchecked. Don’t recall ever making that change, but checking all of the other channels brought the network back to life.

There was apparently ‘enough’ interference to only allow some of the devices to heard by the Conbee, but the Conbee was unable to actually send any control commands.