Deconz GUI service wont start on Debian 12 GNOME

deCONZ General Support
1

Describe the bug

deconz GUI will not start when run as a service sudo systemctl start deconz-gui but the GUI starts okay if I run /usr/bin/deCONZ from the same terminal.

Steps to reproduce the behavior

  1. Install Debian 12 GNOME on amd64 PC (I used Index of /debian-cd/current/amd64/iso-dvd)
  2. Follow instructions on ConBee II Installation to install deconz
  3. Enable auto login so the GUI can start
  4. sudo systemctl enable deconz-gui
  5. sudo systemctl disable deconz

I also changed the http-port to 8081 in the service file sudo systemctl edit deconz-gui

Expected behavior

Deconz should start and show GUI

Environment

  • Host system: PC
  • Running method: Debian 12
  • Firmware version: 26720700
  • deCONZ version: 2.22.02
  • Device: ConBee II
  • Do you use an USB extension cable: yes
  • Is there any other USB or serial devices connected to the host system? If so: Which? Wireless mouse

deCONZ Logs

Aug 18 17:30:27 lm700 systemd[1]: deconz-gui.service: Scheduled restart job, restart counter is at 1.
Aug 18 17:30:27 lm700 systemd[1]: Stopped deconz-gui.service - deCONZ: ZigBee gateway -- GUI/REST API.
Aug 18 17:30:28 lm700 systemd[1]: Started deconz-gui.service - deCONZ: ZigBee gateway -- GUI/REST API.
Aug 18 17:30:28 lm700 systemd[1]: Starting deconz-init.service - deCONZ: ZigBee gateway -- Initialisation...
Aug 18 17:30:28 lm700 deCONZ-init.sh[31735]: cat: /sys/block/mmcblk0/device/cid: No such file or directory
Aug 18 17:30:28 lm700 deCONZ[31727]: Authorization required, but no authorization protocol specified
Aug 18 17:30:28 lm700 deCONZ[31727]: qt.qpa.xcb: could not connect to display :0
Aug 18 17:30:28 lm700 deCONZ[31727]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Aug 18 17:30:28 lm700 deCONZ[31727]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Aug 18 17:30:28 lm700 deCONZ[31727]: Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Aug 18 17:30:28 lm700 deCONZ-init.sh[31728]:  stopping deconz-wifi.service
Aug 18 17:30:28 lm700 systemd[1]: deconz-gui.service: Main process exited, code=killed, status=6/ABRT
Aug 18 17:30:28 lm700 systemd[1]: deconz-gui.service: Failed with result 'signal'.
Aug 18 17:30:28 lm700 systemd[1]: Reloading.
Aug 18 17:30:28 lm700 systemd[1]: deconz-init.service: Deactivated successfully.
Aug 18 17:30:28 lm700 systemd[1]: Finished deconz-init.service - deCONZ: ZigBee gateway -- Initialisation.
2

This looks like deCONZ is started in a non X11 session, or the systemd service is called before X session is running?

3

I am facing similar issue after updating my RPi based Phoscon appliance (RasBee II) to Raspberry OS 12 (Bookworm). And I suspect it has something to do with change to Wayland instead of Xorg for Desktop.

Luckily I have not that much devices and very low change rate, so I use it actually headless. But accessing deConz GUI is rather a pain …

4

i can’t recreate your issue atm but i think it could be releated to the Environment Setting of the GUI-Service.

could you try
sudo systemctl edit deconz-gui

And Edit it like that:

image
image1481×859 207 KB

5

Ok, came a little further, looks like the bookworm upgrade kind of killed the desktop installation. I could fix that and am able now to switch successfully switch between Xorg & wayland. But Xorg doesn’t run stable at all, service does constantly restart after being activated. I can (Xorg) VNC to the phoscon appliance, but don’t see a desktop.

Switching to wayland (wayfire or labwc), that does run stable. After deactivating (Xorg) “VNC” on CLI “raspi-config” and enabling and starting “wayvnc.service”, I can VNC to the phoscon appliance (encrypted), but get only a grey area, no desktop or logon screen. I don’t know if the raspi-config “autologon” for desktop setting is still working for wayland …

Has anybody else faced similar issue?

6

Now, finally I got it working again. Existing settings in “config.txt” hasn’t been correct for RPi graphics. Basically neither Xorg nor labwc-pi could find a GPU to hook on.

Since the standard in Debian/Raspberry OS 12 is Wayland using “labwc-pi”, I tried to make use of it. “raspi-conf” does indeed configure to start the right VNC service for the actually running “session type”, “wayvnc” or “vncserver-x11”.

But no real luck with “labwc-pi”, so switched back to X11 desktop (“lightdm”) and could make “deconz-gui.service” run again. That VNC connection unfortunately remains not encrypted … unlike “wayvnc”.