Deconz and openhab UI fight a fight deconz wins

[bdv (Bruno)]

@Wolfgang_S

I think I have not seen an answer to my question about

@Wolfgang_S

check if deCONZ comes back with the same webpage on both ports

If the content at both ports is different it will give an indication about which service to redirect to an other port.

The content is indeed different: on port 8081 I get the phoscon web-ui, on port 8080 i get an error, the same error as when openhab-service has been stopped.

Is that the answer to your question?

[bdv (Bruno)]

@mstormi

did you install strictly using openhabian-config only ?

Please investigate yourself how to start deconz so it does not occupy 8080 (play with the --ws-port option, too).

Strictly openhabian-config. The only thing I change is for mqtt I add

“listener 1883
allow_anonymous true”
to the config.

For the rest it is pure openhabian, latest image.
I’ll try the --ws-port too, i’ll go search where I can change that. I already tried to change the --http-port=80 in deconz-gui.service in /lib/systemd/system/deconz-gui.service to --http-port=8082 but to no avail…

[bdv (Bruno)]

Never head of this option before, but that was the trick. Adding the –ws-port=8081 in deconz.service did the trick. Both webinterfaces come online, and both work without issues for now.

[Unit]
Description=deCONZ: ZigBee gateway – REST API
Wants=deconz-init.service deconz-update.service
StartLimitIntervalSec=0

[Service]
User=1000
ExecStart=/usr/bin/deCONZ -platform minimal --http-port=8081 –ws-port=8081
Restart=on-failure
RestartSec=30
AmbientCapabilities=CAP_NET_BIND_SERVICE CAP_KILL CAP_SYS_BOOT CAP_SYS_TIME

[Install]
WantedBy=multi-user.target