Startup problem (since update service ran?)

deCONZ General Support
1

Good day!

Since that morning, my gateway setup seems broken. I have a ConBee II connected on a Raspberry Pi 4B and since yesterday, everything worked fine. I didn’t touch anything, but there’s a backup and update script running every night (apt update / full-upgrade). Now since this morning, deconz-gui doesn’t start properly anymore. The GUI freezes in the start screen, stating “Connecting to device” in the status bar at the bottom.

Now here’s what /var/log/syslog states:

Line  5786: Jul 17 07:57:03 rpi4 systemd[1]: Starting deCONZ: ZigBee gateway -- Initialisation...
Line  5787: Jul 17 07:57:03 rpi4 systemd[1]: Started deCONZ: ZigBee gateway -- Update Service.
Line  5823: Jul 17 07:57:03 rpi4 deCONZ-init.sh[409]:  stopping deconz-wifi.service
Line  5847: Jul 17 07:57:04 rpi4 systemd[1]: /lib/systemd/system/deconz-gui.service:11: Unknown key name 'StartLimitIntervalSec' in section 'Service', ignoring.
Line  5858: Jul 17 07:57:04 rpi4 systemd[1]: deconz-init.service: Succeeded.
Line  5859: Jul 17 07:57:04 rpi4 systemd[1]: Finished deCONZ: ZigBee gateway -- Initialisation.
Line  5911: Jul 17 07:57:08 rpi4 systemd[1]: Started deCONZ: ZigBee gateway -- GUI/REST API.
Line  5992: Jul 17 07:57:17 rpi4 deCONZ[648]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
Line  5993: Jul 17 07:57:17 rpi4 deCONZ[648]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Line  5994: Jul 17 07:57:17 rpi4 deCONZ[648]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Line  5995: Jul 17 07:57:17 rpi4 deCONZ[648]: Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
Line  5996: Jul 17 07:57:17 rpi4 systemd[1]: deconz-gui.service: Main process exited, code=killed, status=6/ABRT
Line  5997: Jul 17 07:57:17 rpi4 systemd[1]: deconz-gui.service: Failed with result 'signal'.
Line  6001: Jul 17 07:57:17 rpi4 systemd[1]: Starting deCONZ: ZigBee gateway -- Initialisation...
Line  6027: Jul 17 07:57:17 rpi4 deCONZ-init.sh[784]:  stopping deconz-wifi.service
Line  6042: Jul 17 07:57:18 rpi4 systemd[1]: /lib/systemd/system/deconz-gui.service:11: Unknown key name 'StartLimitIntervalSec' in section 'Service', ignoring.
Line  6044: Jul 17 07:57:18 rpi4 systemd[1]: deconz-init.service: Succeeded.
Line  6045: Jul 17 07:57:18 rpi4 systemd[1]: Finished deCONZ: ZigBee gateway -- Initialisation.
Line  6116: Jul 17 07:58:09 rpi4 systemd[1]: deconz-gui.service: Scheduled restart job, restart counter is at 1.
Line  6117: Jul 17 07:58:09 rpi4 systemd[1]: Stopped deCONZ: ZigBee gateway -- GUI/REST API.
Line  6118: Jul 17 07:58:09 rpi4 systemd[1]: Started deCONZ: ZigBee gateway -- GUI/REST API.
Line  6119: Jul 17 07:58:09 rpi4 systemd[1]: Starting deCONZ: ZigBee gateway -- Initialisation...
Line  6120: Jul 17 07:58:09 rpi4 deCONZ-init.sh[1709]:  stopping deconz-wifi.service
Line  6121: Jul 17 07:58:09 rpi4 deCONZ[1708]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-pi'
Line  6124: Jul 17 07:58:09 rpi4 systemd[1]: /lib/systemd/system/deconz-gui.service:11: Unknown key name 'StartLimitIntervalSec' in section 'Service', ignoring.
Line  6125: Jul 17 07:58:09 rpi4 systemd[1]: deconz-init.service: Succeeded.
Line  6126: Jul 17 07:58:09 rpi4 systemd[1]: Finished deCONZ: ZigBee gateway -- Initialisation.
Line  6128: Jul 17 07:58:11 rpi4 deCONZ[1708]: libpng warning: iCCP: known incorrect sRGB profile
Line  6129: Jul 17 07:58:11 rpi4 deCONZ[1708]: libpng warning: iCCP: known incorrect sRGB profile
Line  6130: Jul 17 07:58:12 rpi4 deCONZ[1708]: error: XDG_RUNTIME_DIR not set in the environment.
Line  6136: Jul 17 07:58:15 rpi4 deCONZ[1708]: qt.qpa.xcb: QXcbConnection: XCB error: 148 (Unknown), sequence: 192, resource id: 0, major code: 140 (Unknown), minor code: 20

The message “Unknown key name ‘StartLimitIntervalSec’ in section ‘Service’” doesn’t appear in any of the older syslog files. So maybe that’s a start.

Linked here, please also find debug01.txt, which is a result of the call

/usr/bin/deCONZ -platform minimal --dbg-aps=2 --dbg-info=2 --dbg-error=2 | tee debug.txt

It became a bit long, cause I had to wake up my little boy and he chose to take some daddy-time.

I hope so much you can help me find the issue.

Thanks! Thomas

2

Hello, your issue is realy like this one, can take a look Conbee II stopped working on RPi 4 - #3 by manup

3

Now, little boy is with grandma and I had some time to go through the logs, googl’d a bit and not only found a solution but also the reason causing my problem.

It’s all well described here: After a sudo apt update && sudo apt full-upgrade and a reboot deconz no longer connects to the conbee 2 · Issue #6937 · dresden-elektronik/deconz-rest-plugin · GitHub

Summary:

It’s an debian error, Symlinks are not set after upgrade.

Fix:
Either launch with deCONZ --dev=/dev/ttyACM0 or add dev parameter in your service file. See link above.

Please assume this thread as solved.