ebaauw/homebridge-deconz

Error after Updating Synology DSM to 7.2.1.-69057

Closed this issue · 7 comments

Spy-1 commented

I have installed deconz in a docker Container.
After Update synology DSM to latest V 7.2.1.69057 i dont have any longer acess to my Gateway.

[10/31/2023, 5:15:16 PM] [deCONZ] warning: 192.168.178.20:8081: not a deCONZ gateway - retrying in 60s [10/31/2023, 5:16:16 PM] [deCONZ] warning: 192.168.178.20:8081: not a deCONZ gateway - retrying in 60s [10/31/2023, 5:17:16 PM] [deCONZ] warning: 192.168.178.20:8081: not a deCONZ gateway - retrying in 60s [10/31/2023, 5:18:16 PM] [deCONZ] warning: 192.168.178.20:8081: not a deCONZ gateway - retrying in 60s

I don´t know how to solve this.

ebaauw commented

Neither do I; this is an issue with your setup, not with Homebridge deCONZ. You might run deconz -DD -H 192.168.178.20:8081 config from the command line to see the debug output gives you some clue as to what is wrong.

Spy-1 commented

After that i´m, getting this:
root@homebridge:/var/lib/homebridge $ deconz -DD -H 192.168.178.20:8081 config deconz: 192.168.178.20: request 1: GET /config deconz: 192.168.178.20: request 1: GET http://192.168.178.20:8081/api/config deconz: 192.168.178.20: request 1: response: {"apiversion":"1.16.0","bridgeid":"00212EFFFF01BB04","datastoreversion":"93","factorynew":false,"mac":"00:11:32:e9:b2:55","modelid":"deCONZ","name":"Phoscon-GW","replacesbridgeid":null,"starterkitid":"","swversion":"2.24.1"} deconz: 192.168.178.20: request 1: 200 OK deconz: fatal: 192.168.178.20:8081: not a deCONZ gateway

ebaauw commented

devicename is missing from the response. Did deCONZ connect to the ConBee?

Spy-1 commented

No. That's why I thought of the DSM update as the culprit.

ebaauw commented

Could be. Maybe the device file changed, or it’s no longer exposed to the container. If memory serves, there were issues in Debian/Raspberry Pi OS, where the logical device files were no longer created, and you had to specify the physical device file to deCONZ as command-line parameter. I cannot help you here, best ask the deCONZ Discord or support forum.

Spy-1 commented

Now that I have completely reinstalled deconz and added it to Homkit, I have access to the conbee II but get this message within homebridge:
[11/1/2023, 11:26:07 AM] [deCONZ] Phoscon-GW: request 4: GET / [11/1/2023, 11:26:07 AM] [deCONZ] Phoscon-GW: warning: request 4: /: api error 1: unauthorized user
Maybe its a stupid question, but how to authoriz the user?

Spy-1 commented

The issue can be closed.
Obviously, there was still data in the Data-Directory of the Deconz container.
After deleting them and reinstalling everything, everything works fine again.
Thanks for the support!