Openhab Conbee II

Very new to OpenHab.
I’ve used Fhem for years and now i’m using Home Assistant in my Home since years.

Yester i started fresh with RpiZero2 and OpenHab, no problems.
I inserted a Conbee II USB Stick, installed as descriped on the phoscon site.
I’d no problems to find and add some Zigbee devices.

Today i want to start with MQTT Broker, to add some ESP Devices, i installed the MQTT Broker, restarted the RPi.
But the Phoscon Gateway is now unknown and the Bindings from yesterday are on Error.

Where to start with error searching ?

Which OH version do you use ? What does the openhab.log content show ?

openHAB 4.0.1
events.log:

2023-08-01 09:42:35.799 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'deconz:deconz:000000000000' changed from UNINITIALIZED (NOT_YET_READY) to INITIALIZING
2023-08-01 09:42:35.826 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'deconz:deconz:000000000000' changed from INITIALIZING to UNKNOWN
2023-08-01 09:42:35.859 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'deconz:switch:000000000000:00158d0001e82493010006' changed from UNINITIALIZED (NOT_YET_READY) to INITIALIZING
2023-08-01 09:42:35.874 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'deconz:switch:000000000000:00158d0001e82493010006' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2023-08-01 09:42:35.888 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'deconz:temperaturesensor:000000000000:00158d00094c4ad1010402' changed from UNINITIALIZED (NOT_YET_READY) to INITIALIZING
2023-08-01 09:42:35.902 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'deconz:temperaturesensor:000000000000:00158d00094c4ad1010402' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2023-08-01 09:42:35.914 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'deconz:humiditysensor:000000000000:00158d00094c4ad1010405' changed from UNINITIALIZED (NOT_YET_READY) to INITIALIZING
2023-08-01 09:42:35.928 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'deconz:humiditysensor:000000000000:00158d00094c4ad1010405' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2023-08-01 09:42:35.970 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'deconz:onofflight:000000000000:cc86ecfffef679450b' changed from UNINITIALIZED (NOT_YET_READY) to INITIALIZING
2023-08-01 09:42:35.985 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'deconz:onofflight:000000000000:cc86ecfffef679450b' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)

Status:
openhabian@openhabian:~ $ sudo service deconz-gui status
● deconz-gui.service - deCONZ: ZigBee gateway -- GUI/REST API
     Loaded: loaded (/lib/systemd/system/deconz-gui.service; disabled; vendor p>
     Active: inactive (dead)


Aug 01 09:41:57 openhabian systemd[1]: /lib/systemd/system/deconz-gui.service:1>
Aug 01 09:45:58 openhabian systemd[1]: /lib/systemd/system/deconz-gui.service:1>
Aug 01 09:54:44 openhabian systemd[1]: /lib/systemd/system/deconz-gui.service:1>
lines 1-7/7 (END)

Start:


openhabian@openhabian:~ $ sudo systemctl start deconz-gui.service
openhabian@openhabian:~ $ sudo service deconz-gui status
● deconz-gui.service - deCONZ: ZigBee gateway -- GUI/REST API
     Loaded: loaded (/lib/systemd/system/deconz-gui.service; disabled; vendor p>
     Active: activating (auto-restart) (Result: signal) since Tue 2023-08-01 09>
    Process: 3549 ExecStart=/usr/bin/deCONZ --http-port=80 (code=killed, signal>
   Main PID: 3549 (code=killed, signal=ABRT)
        CPU: 160ms
lines 1-6/6 (END)

What is the output of

sudo netstat -tulpe | grep -i deconz

This should show all ports that the deconz port is listening on.

Now i’ve tried to start Deconz in Debug mode.

openhabian@openhabian:~ $ /usr/bin/deCONZ --dbg-info=2 --dbg-error=2
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.

Aborted

no output

Then no deconz process seems to run. You may validate that by using ps -ef | grep -i deconz

Try

sudo systemctl restart deconz

Any error message ? Does the netstat call return results now ? If not what is shown by

sudo journalctl | grep -i deconz
Aug 01 10:13:39 openhabian systemd[1]: Failed to start deCONZ: ZigBee gateway -- Initialisation.
Aug 01 10:14:09 openhabian systemd[1]: deconz-gui.service: Scheduled restart job, restart counter is at 37.
Aug 01 10:14:09 openhabian systemd[1]: Stopped deCONZ: ZigBee gateway -- GUI/REST API.
Aug 01 10:14:09 openhabian systemd[1]: Started deCONZ: ZigBee gateway -- GUI/REST API.
Aug 01 10:14:09 openhabian systemd[1]: deconz-init.service: Start request repeated too quickly.
Aug 01 10:14:09 openhabian systemd[1]: deconz-init.service: Failed with result 'start-limit-hit'.
Aug 01 10:14:09 openhabian systemd[1]: Failed to start deCONZ: ZigBee gateway -- Initialisation.
Aug 01 10:14:09 openhabian deCONZ[5323]: qt.qpa.xcb: could not connect to display :0
Aug 01 10:14:09 openhabian deCONZ[5323]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Aug 01 10:14:09 openhabian deCONZ[5323]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Aug 01 10:14:09 openhabian deCONZ[5323]: Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
Aug 01 10:14:09 openhabian systemd[1]: deconz-gui.service: Main process exited, code=killed, status=6/ABRT
Aug 01 10:14:09 openhabian systemd[1]: deconz-gui.service: Failed with result 'signal'.
Aug 01 10:14:09 openhabian systemd[1]: deconz-init.service: Start request repeated too quickly.
Aug 01 10:14:09 openhabian systemd[1]: deconz-init.service: Failed with result 'start-limit-hit'.
Aug 01 10:14:09 openhabian systemd[1]: Failed to start deCONZ: ZigBee gateway -- Initialisation.
Aug 01 10:14:39 openhabian systemd[1]: deconz-gui.service: Scheduled restart job, restart counter is at 38.
Aug 01 10:14:39 openhabian systemd[1]: Stopped deCONZ: ZigBee gateway -- GUI/REST API.
Aug 01 10:14:39 openhabian systemd[1]: Started deCONZ: ZigBee gateway -- GUI/REST API.
Aug 01 10:14:39 openhabian systemd[1]: deconz-init.service: Start request repeated too quickly.
Aug 01 10:14:39 openhabian systemd[1]: deconz-init.service: Failed with result 'start-limit-hit'.
Aug 01 10:14:39 openhabian systemd[1]: Failed to start deCONZ: ZigBee gateway -- Initialisation.
Aug 01 10:14:39 openhabian deCONZ[5609]: qt.qpa.xcb: could not connect to display :0
Aug 01 10:14:39 openhabian deCONZ[5609]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Aug 01 10:14:39 openhabian deCONZ[5609]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Aug 01 10:14:39 openhabian deCONZ[5609]: Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
Aug 01 10:14:39 openhabian systemd[1]: deconz-gui.service: Main process exited, code=killed, status=6/ABRT
Aug 01 10:14:39 openhabian systemd[1]: deconz-gui.service: Failed with result 'signal'.
Aug 01 10:14:39 openhabian systemd[1]: deconz-init.service: Start request repeated too quickly.
Aug 01 10:14:39 openhabian systemd[1]: deconz-init.service: Failed with result 'start-limit-hit'.
Aug 01 10:14:39 openhabian systemd[1]: Failed to start deCONZ: ZigBee gateway -- Initialisation.
Aug 01 10:14:51 openhabian sudo[5776]: openhabian : TTY=pts/0 ; PWD=/home/openhabian ; USER=root ; COMMAND=/usr/bin/systemctl restart deconz
Aug 01 10:14:51 openhabian systemd[1]: deconz-init.service: Start request repeated too quickly.
Aug 01 10:14:51 openhabian systemd[1]: deconz-init.service: Failed with result 'start-limit-hit'.
Aug 01 10:14:51 openhabian systemd[1]: Failed to start deCONZ: ZigBee gateway -- Initialisation.
Aug 01 10:14:51 openhabian systemd[1]: Stopping deCONZ: ZigBee gateway -- REST API...
Aug 01 10:15:00 openhabian systemd[1]: deconz.service: Main process exited, code=exited, status=143/n/a
Aug 01 10:15:00 openhabian systemd[1]: deconz.service: Failed with result 'exit-code'.
Aug 01 10:15:00 openhabian systemd[1]: Stopped deCONZ: ZigBee gateway -- REST API.
Aug 01 10:15:00 openhabian systemd[1]: deconz.service: Consumed 8.916s CPU time.
Aug 01 10:15:00 openhabian systemd[1]: Started deCONZ: ZigBee gateway -- REST API.
Aug 01 10:15:00 openhabian deCONZ[5832]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-openhabian'
Aug 01 10:15:00 openhabian deCONZ[5832]: libpng warning: iCCP: known incorrect sRGB profile
openhabian@openhabian:~ $ sudo netstat -tulpe | grep -i deconz
tcp        0      0 0.0.0.0:http            0.0.0.0:*               LISTEN      openhabian 38254      7427/deCONZ
tcp        0      0 0.0.0.0:https           0.0.0.0:*               LISTEN      openhabian 38264      7427/deCONZ
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           openhabian 38291      7427/deCONZ
openhabian@openhabian:~ $

Mmmh, now the Phoscon GW is online!
Why?

You used the service that starts with GUI which is not available on a headless system. The display couldn’t be opened.
Did you shut down your server before deconz was not running/working ?
What is the output of

sudo systemctl status deconz.service

does it show enabled in:

 Loaded: loaded (/lib/systemd/system/deconz.service; enabled; vendor preset: enabled)

If not the service will not be started automatically after a reboot/restart of the Pi.
That start was done manually with the command I asked you to execute.

the http and https services are required to access the Phoscon API which is used by the binding.
As those were not running OH was not able to access the Conbee stick.

Ok, thx for your patiens :slight_smile:

I just booted the RPi, Deconz does not work.
i entered
sudo systemctl restart deconz
now it works

So i’ve to find a way to autostart it?
I’m not very familar with Linux :slight_smile:

i tried
sudo systemctl enable deconz-gui
but does not autostart

because that is again the wrong service.
That is the service that complains about missing QT libraries because you have a headless install …?
You need to enable the other service that you manually started before

sudo systemctl enable deconz

After it is enabled

sudo systemctl status deconz.service

will show that it is enabled.

Yeah, Thx, now it works
and i’ve learned a lot

1 Like

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.