deCONZ APP/Binding on same Pi as OpenHABian stopped working after reboot

Setup, Configuration and Use Runtime
, ,
1

During an upgrade system (02) with openhabian-config I noticed some remarks related to deconz_2.14.01

Important: enable_uart=1 should be set in /boot/config (RaspBee only)
Important: /boot/cmdline must not contain console=serial0 (RaspBee only)

The ConBee II USB stick was added just lately to the same machine as OH and I did not experienced any problems so far and the Phoscon APP was also at this point still working as normal.

However after a reboot of this Pi the Phoscon APP/Binding stopped working.
I found a similar but older topic started by @fanavity about this subject
Tried to change /boot/config.txt from

console=serial0,115200 console=tty1 root=PARTUUID=77282c36-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

into

enable_uart=1,115200 console=tty1 root=PARTUUID=77282c36-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

BTW LATER THIS APPEARED THE WRONG SOLUTION FOR TWO REASONS; I HAVE A CONBEE II AND WAS MIXING THE TWO FILES SO DO NOT CUT & PASTE THIS :laughing:

But likely this is an incorrect/incomplete syntax because after another reboot the Phoscon APP/Binding was not working anymore.

For NOOBS like me the workaround to redo in openhabian-config menu-option '29 - deCONZ to restart this. But likely I will need to redo this after each reboot.
Can anyone guide me to get a more permanent solution? Thank you.

System details are:

  • Installed = OpenHABian
  • Release Build = 3.2.0 release build
  • Release = Raspbian GNU/Linux 10 (buster)
  • Kernel = Linux 5.10.63-v7l+ armv7l
  • Platform = Raspberry Pi 4 Model B Rev 1.1

BTW Most of this info is not visible anymore when you logon with SSH but google was my friend:
uname -snrvmo

2

I would suggest to run
sudo journalctl | grep -i deconz
or
sudo journalctl -xu deconz
this should give a hint about why the deconz service cannot be started.

3

These commands are helpful and after another test reboot of my system the inital log is:

Feb 15 09:20:34 openhabian sudo[24197]: openhabian : TTY=pts/0 ; PWD=/home/openhabian ; USER=root ; COMMAND=/usr/bin/journalctl -xu deconz
Feb 15 09:27:03 openhabian systemd[1]: Stopping deCONZ: ZigBee gateway -- REST API...
Feb 15 09:27:03 openhabian systemd[1]: Stopping deCONZ: ZigBee gateway -- WIFI Service...
Feb 15 09:27:03 openhabian systemd[1]: Stopping deCONZ: ZigBee gateway -- Update Service...
Feb 15 09:27:03 openhabian systemd[1]: deconz-update.service: Main process exited, code=killed, status=15/TERM
Feb 15 09:27:03 openhabian systemd[1]: deconz-update.service: Succeeded.
Feb 15 09:27:03 openhabian systemd[1]: Stopped deCONZ: ZigBee gateway -- Update Service.
Feb 15 09:27:03 openhabian systemd[1]: deconz-wifi.service: Main process exited, code=killed, status=15/TERM
Feb 15 09:27:03 openhabian systemd[1]: deconz-wifi.service: Succeeded.
Feb 15 09:27:03 openhabian systemd[1]: Stopped deCONZ: ZigBee gateway -- WIFI Service.
Feb 15 09:27:13 openhabian systemd[1]: deconz.service: Main process exited, code=exited, status=143/n/a
Feb 15 09:27:13 openhabian systemd[1]: deconz.service: Failed with result 'exit-code'.
Feb 15 09:27:13 openhabian systemd[1]: Stopped deCONZ: ZigBee gateway -- REST API.
Feb 15 09:27:26 openhabian systemd[1]: Started deCONZ: ZigBee gateway -- WIFI Service.
Feb 15 09:27:26 openhabian systemd[1]: Started deCONZ: ZigBee gateway -- Update Service.
Feb 15 09:29:33 openhabian sudo[1634]: openhabian : TTY=pts/0 ; PWD=/home/openhabian ; USER=root ; COMMAND=/usr/bin/journalctl -xu deconz

In OH deCONZ is stuck on initializing and the bridge is in error, the deCONZ APP is not accessible.
Performing my NOOBS solution (menu option ‘29’) gives the following lines in the background:

openhabian@openhabian:~ $ sudo openhabian-config
2022-02-15_09:40:18_CET [openHABian] Checking for root privileges... OK
2022-02-15_09:40:19_CET [openHABian] Loading configuration file '/etc/openhabian.conf'... OK
2022-02-15_09:40:19_CET [openHABian] openHABian configuration tool version: [openHAB3]{2022-01-28T11:18:18+01:00}(aaf8aca)
2022-02-15_09:40:19_CET [openHABian] Checking for changes in origin branch openHAB3... OK
2022-02-15_09:40:23_CET [openHABian] Switching to branch openHAB3... OK
2022-02-15_09:40:23_CET [openHABian] Adding slightly tuned bash configuration files to system... OK
2022-02-15_09:41:14_CET [openHABian] Updating Linux package information... OK
2022-02-15_09:41:16_CET [openHABian] Adding required keys to apt... OK
2022-02-15_09:41:16_CET [openHABian] Preparing deCONZ repository ... OK
2022-02-15_09:41:22_CET [openHABian] Installing deCONZ ... OK

and adds this to the log:

Feb 15 09:41:31 openhabian systemd[1]: /lib/systemd/system/deconz-gui.service:10: Unknown lvalue 'StartLimitIntervalSec' in section 'Service', ignoring
Feb 15 09:41:31 openhabian systemd[1]: /lib/systemd/system/deconz-gui.service:10: Unknown lvalue 'StartLimitIntervalSec' in section 'Service', ignoring
Feb 15 09:41:31 openhabian systemd[1]: Stopping deCONZ: ZigBee gateway -- WIFI Service...
Feb 15 09:41:31 openhabian systemd[1]: deconz-wifi.service: Main process exited, code=killed, status=15/TERM
Feb 15 09:41:31 openhabian systemd[1]: deconz-wifi.service: Succeeded.
Feb 15 09:41:31 openhabian systemd[1]: Stopped deCONZ: ZigBee gateway -- WIFI Service.
Feb 15 09:41:31 openhabian systemd[1]: /lib/systemd/system/deconz-gui.service:10: Unknown lvalue 'StartLimitIntervalSec' in section 'Service', ignoring
Feb 15 09:41:31 openhabian systemd[1]: /lib/systemd/system/deconz-gui.service:10: Unknown lvalue 'StartLimitIntervalSec' in section 'Service', ignoring
Feb 15 09:41:32 openhabian systemd[1]: Started deCONZ: ZigBee gateway -- REST API.
Feb 15 09:41:32 openhabian systemd[1]: Starting deCONZ: ZigBee gateway -- Initialisation...
Feb 15 09:41:32 openhabian deCONZ-init.sh[3891]:  starting deconz-wifi.service
Feb 15 09:41:32 openhabian systemd[1]: Started deCONZ: ZigBee gateway -- WIFI Service.
Feb 15 09:41:32 openhabian deCONZ-init.sh[3891]: Created symlink /etc/systemd/system/multi-user.target.wants/deconz-wifi.service → /lib/systemd/system/deconz-wifi.service.
Feb 15 09:41:32 openhabian deCONZ[3890]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-openhabian'
Feb 15 09:41:32 openhabian systemd[1]: deconz-init.service: Succeeded.
Feb 15 09:41:32 openhabian systemd[1]: Started deCONZ: ZigBee gateway -- Initialisation.
Feb 15 09:41:33 openhabian deCONZ[3890]: libpng warning: iCCP: known incorrect sRGB profile
Feb 15 09:41:34 openhabian deCONZ[3890]: This plugin does not support propagateSizeHints()
Feb 15 09:41:34 openhabian deCONZ[3890]: This plugin does not support propagateSizeHints()
Feb 15 09:41:36 openhabian deCONZ[3890]: This plugin does not support propagateSizeHints()
Feb 15 09:41:44 openhabian deCONZ-update2.sh[387]: found deCONZ port 8081
Feb 15 09:41:44 openhabian deCONZ-update2.sh[387]: use database file /home/openhabian/.local/share/dresden-elektronik/deCONZ/zll.db
Feb 15 09:41:44 openhabian deCONZ-update2.sh[387]: process update state noupdates
Feb 15 09:44:22 openhabian sudo[5613]: openhabian : TTY=pts/0 ; PWD=/home/openhabian ; USER=root ; COMMAND=/usr/bin/journalctl -xu deconz

And both the bridge and APP are back alive.
However I not able to determine what is missing and should be changed to get this service started after a reboot except for the initial hint (what brings me back to the syntax problem)

So if anyone has the ConBee II on a the same device as Openhab may be I can do a T&E with their /boot/config.txt to see if that is the solution.

4

Based upon the log comment ‘deconz status=15’ I found this topic:

Not sure if it contains already the answer but will explore this further, if anybody already found their solution I will appreciate their input.

5

Conbee is running here with a Raspberry Pi 4.
/etc/systemd/system/deconz.service.d/override.conf contains:

[Service]
ExecStart=
ExecStart=/usr/bin/deCONZ -platform minimal --http-port=8090 --ws-port=9443

in this way I do not have any port conflicts with other services.

/etc/udev/rules.d/69-conbee.rules contains:

ATTRS{idVendor}=="1cf1", ATTRS{idProduct}=="0030", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="1cf1", ATTRS{idProduct}=="0030", ENV{MTP_NO_PROBE}="1"
KERNEL=="ttyACM?", SUBSYSTEMS=="usb", DRIVERS=="usb", ACTION=="add", ATTRS{idVendor}=="1cf1", ATTRS{idProduct}=="0030", SYMLINK+="ttyConBee2", GROUP="dialout", MODE="0660"

As far as I remember I did not change anythin in /boot/config.txt ( listed are only lines that do not start with #:

dtparam=audio=on

[pi4]
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
gpu_mem=16
6

Thank you for your input, in my system (also a Pi4) difference are:

  • file '/etc/systemd/system/deconz.service.d/override.conf ’ is empty
  • file ‘/etc/udev/rules.d/69-conbee.rules’ is identical except for last line which is still on comment
  • file ‘/boot/config.txt’ identical plus additial line with ‘dtoverlay=disable-wifi’ because my Pi4 is wired and I do not use here Wifi
  • file ‘/boot/cmdline.txt’ did not change this file/reverted back to original because I RTFM comments better and realised this was only required for a RaspBee and not for the ConBee II

So think my solution will be in the 1st file, explore that further so thank you again.

7

I was able to solve this problem myself or should I give credits to this earlier topic

and @Felix_Schneider for giving the simple solution:

sudo systemctl enable deconz

Not sure why this command was not added during installation.