Addons: Deconz 3.7 Errors; Could not connect to any X display.

[d0ugal]

I upgraded to deconz 3.7, after having 3.6 working well for some time. After quite a bit of output it eventually gave up and I got this error.

20:49:03:165 LightNode 26: Kitchen Ceiling A 1 added
20:49:03:176 don't close database yet, keep open for 900 seconds
20:49:03:176 LightNode 27: Kitchen Ceiling A 3 added
20:49:03:186 don't close database yet, keep open for 900 seconds
20:49:03:186 LightNode 17: General Socket added
20:49:03:239 Current channel 15
20:49:03:255 CTRL ANT_CTRL 0x03
20:49:03:279 Device protocol version: 0x0108
20:49:03:327 Current channel 15
20:49:03:343 CTRL ANT_CTRL 0x03
20:49:03:379 APS-DATA.indication from unknown node 0x2EB3
20:49:03:379 ZCL attribute report 0x0000000000000000 for cluster 0x0006, ep 0x08
20:49:03:383 ZCL attribute report 0x00124B0018DF32BA for cluster 0x0006, ep 0x08
20:49:07:730 reconnect network done
20:49:07:758 saved node state in 0 ms
20:49:07:772 sync() in 13 ms
20:49:07:772 REST API plugin shutting down
20:49:07:782 sync() in 9 ms
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
qt.qpa.screen: QXcbConnection: Could not connect to display 
Could not connect to any X display.

The error is pretty weird, I am not sure why it would be looking for a X display. I assume that means X11, which I hope wont ever be present in this case :smile:

I restored 3.6 from a snapshot, and that is working great again. I made no configuration changes etc. for 3.7

[frenck]

Hmmm, interesting @d0ugal! I'm sorry to hear you are experiencing problems.

Could you provide some more information about your system? In general, the output of the hassio info command is really helpful. That would allow us to try and reproduce it.

(On my own system, I haven't got this issue, which is why I ask).

[d0ugal]

Sure thing. I am running hass.io on ubuntu server and not hassos, so maybe that could be the root cause.

arch: amd64
channel: stable
hassos: null
homeassistant: 0.101.2
hostname: hoose
logging: info
machine: qemux86-64
supervisor: "192"
supported_arch:
- amd64
- i386
timezone: Europe/London

[frenck]

Check, thanks! Don't worry, so does my production system 😉

Could you share the add-on configuration you are using? (please, mask any credentials if they are in there).

[d0ugal]

My config is minimal.

{
  "device": "/dev/ttyACM0",
  "vnc_password": ""
} 

I guess the error is related to the vnc support? I didn’t notice that feature before. I’m now wondering what other config settings I should try 😄

[frenck]

Hmm... Two questions come to mind:

• Have you set a VNC port in the "Network options"?
• Have you installed a graphical environment on your host operating system?

[sandert98]

Thanks for merging :) .
No, I don't have any VNC options set.
No, I have installed Raspbian Buster Lite without a gui:

pi@rpi4-sander:/ $ uname -a
Linux rpi4-sander 4.19.75-v7l+ #1270 SMP Tue Sep 24 18:51:41 BST 2019 armv7l GNU/Linux

pi@rpi4-sander:/ $ cat /etc/os-release 
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

pi@rpi4-sander:/ $ docker --version
Docker version 19.03.4, build 9013bf5

[frenck]

@sandert98 Could you try setting the vnc_password and assign a port to the VNC in the Network settings? (e.g., 5900 and if it fails, maybe try 5901).

Sorry for all the questions, but I've not been able to reproduce this, thus looking for a situation that works and might indicate the culprit.

[sandert98]

I set the port number to 5900 and a vnc_password, and it seems to work. The add-on is on :) Thanks!
11:02:59:728 APS-DATA.confirm id: 165, status: 0x00 SUCCESS 11:02:59:728 APS-DATA.confirm request id: 165 -> confirmed, timeout 30411664 11:02:59:732 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 1, rssi: 13 11:02:59:732 APS-DATA.indication request id: 165 -> finished 11:02:59:732 APS-DATA.request id: 165 erase from queue 11:03:05:955 APS-DATA.confirm id: 164, status: 0xA7 NO_ACK 11:03:07:273 APS-DATA.indication srcAddr: 0x5e07, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -55 11:03:07:273 device announce 0x90FD9FFFFE2A577C (0x5E07) mac capabilities 0x8E 11:03:07:273 device announce 0x90FD9FFFFE2A577C (0x5E07) mac capabilities 0x8E 11:03:07:293 APS-DATA.indication srcAddr: 0x7660, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -56 11:03:07:293 device announce 0x90FD9FFFFE2B872A (0x7660) mac capabilities 0x8E 11:03:07:293 device announce 0x90FD9FFFFE2B872A (0x7660) mac capabilities 0x8E 11:03:07:298 APS-DATA.indication srcAddr: 0xc2f7, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -46 11:03:07:298 device announce 0x000D6FFFFEC7D790 (0xC2F7) mac capabilities 0x8E 11:03:07:298 device announce 0x000D6FFFFEC7D790 (0xC2F7) mac capabilities 0x8E 11:03:07:308 APS-DATA.indication srcAddr: 0x5e87, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -51 11:03:07:308 device announce 0xD0CF5EFFFE2FBD22 (0x5E87) mac capabilities 0x8E 11:03:07:308 device announce 0xD0CF5EFFFE2FBD22 (0x5E87) mac capabilities 0x8E 11:03:07:316 APS-DATA.request id: 171, addrmode: 0x02, addr: 0x5e07, profile: 0x0000, cluster: 0x0002, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x04 11:03:08:031 APS-DATA.indication srcAddr: 0x5e07, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -55 11:03:08:031 device announce 0x90FD9FFFFE2A577C (0x5E07) mac capabilities 0x8E 11:03:08:031 device announce 0x90FD9FFFFE2A577C (0x5E07) mac capabilities 0x8E 11:03:08:039 APS-DATA.indication srcAddr: 0x7660, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -56 11:03:08:039 device announce 0x90FD9FFFFE2B872A (0x7660) mac capabilities 0x8E 11:03:08:039 device announce 0x90FD9FFFFE2B872A (0x7660) mac capabilities 0x8E 11:03:08:049 APS-DATA.indication srcAddr: 0xc2f7, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -46 11:03:08:049 device announce 0x000D6FFFFEC7D790 (0xC2F7) mac capabilities 0x8E 11:03:08:049 device announce 0x000D6FFFFEC7D790 (0xC2F7) mac capabilities 0x8E 11:03:08:057 APS-DATA.indication srcAddr: 0x5e87, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -51 11:03:08:057 device announce 0xD0CF5EFFFE2FBD22 (0x5E87) mac capabilities 0x8E 11:03:08:057 device announce 0xD0CF5EFFFE2FBD22 (0x5E87) mac capabilities 0x8E 11:03:08:356 remove discovery request duplicate 11:03:08:356 remove discovery request duplicate 11:03:10:023 APS-DATA.indication srcAddr: 0x5e87, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -56 11:03:10:023 device announce 0xD0CF5EFFFE2FBD22 (0x5E87) mac capabilities 0x8E 11:03:10:023 device announce 0xD0CF5EFFFE2FBD22 (0x5E87) mac capabilities 0x8E 11:03:10:038 APS-DATA.indication srcAddr: 0xc2f7, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -55 11:03:10:038 device announce 0x000D6FFFFEC7D790 (0xC2F7) mac capabilities 0x8E 11:03:10:038 device announce 0x000D6FFFFEC7D790 (0xC2F7) mac capabilities 0x8E 11:03:10:078 Search sensors done 11:03:10:269 don't close database yet, keep open for 900 seconds 11:03:10:425 APS-DATA.indication srcAddr: 0x7660, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -56 11:03:10:430 APS-DATA.indication srcAddr: 0x5e07, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -54 11:03:10:803 APS-DATA.indication srcAddr: 0xc2f7, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -46 11:03:10:808 APS-DATA.indication srcAddr: 0x7660, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -56 11:03:10:819 APS-DATA.indication srcAddr: 0x5e87, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -51 11:03:11:235 remove discovery request duplicate 11:03:11:252 APS-DATA.indication srcAddr: 0x5e07, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -54 11:03:11:252 device announce 0x90FD9FFFFE2A577C (0x5E07) mac capabilities 0x8E 11:03:11:252 device announce 0x90FD9FFFFE2A577C (0x5E07) mac capabilities 0x8E 11:03:11:258 APS-DATA.request id: 184, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 1 len: 3 tx.options 0x00 11:03:11:258 send permit join, duration: 59 11:03:11:268 APS-DATA.confirm id: 184, status: 0xD2 11:03:13:052 APS-DATA.indication srcAddr: 0x5e07, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -55 11:03:13:052 device announce 0x90FD9FFFFE2A577C (0x5E07) mac capabilities 0x8E 11:03:13:052 device announce 0x90FD9FFFFE2A577C (0x5E07) mac capabilities 0x8E 11:03:13:059 APS-DATA.indication srcAddr: 0x7660, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -56 11:03:13:059 device announce 0x90FD9FFFFE2B872A (0x7660) mac capabilities 0x8E 11:03:13:059 device announce 0x90FD9FFFFE2B872A (0x7660) mac capabilities 0x8E 11:03:13:155 remove discovery request duplicate 11:03:13:166 APS-DATA.indication srcAddr: 0x5e87, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -57 11:03:13:166 device announce 0xD0CF5EFFFE2FBD22 (0x5E87) mac capabilities 0x8E 11:03:13:166 device announce 0xD0CF5EFFFE2FBD22 (0x5E87) mac capabilities 0x8E 11:03:13:170 APS-DATA.indication srcAddr: 0xc2f7, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -48 11:03:13:170 device announce 0x000D6FFFFEC7D790 (0xC2F7) mac capabilities 0x8E 11:03:13:170 device announce 0x000D6FFFFEC7D790 (0xC2F7) mac capabilities 0x8E 11:03:15:555 APS-DATA.request id: 189, addrmode: 0x03, addr: 0xd0cf5efffe2fbd22, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00 11:03:15:746 APS-DATA.confirm id: 189, status: 0xE1 11:03:17:955 APS-DATA.request id: 190, addrmode: 0x03, addr: 0x90fd9ffffe2b872a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00 11:03:18:136 APS-DATA.confirm id: 190, status: 0xE1 11:03:21:316 APS-DATA.request id: 191, addrmode: 0x03, addr: 0x000d6ffffec7d790, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00 11:03:21:547 APS-DATA.confirm id: 191, status: 0xE1 11:03:23:715 APS-DATA.request id: 192, addrmode: 0x03, addr: 0x00212effff048b9a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00 11:03:23:720 APS-DATA.confirm id: 192, status: 0x00 SUCCESS 11:03:23:720 APS-DATA.confirm request id: 192 -> confirmed, timeout 31935472 11:03:23:723 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 241, rssi: 19 11:03:23:723 APS-DATA.indication request id: 192 -> finished 11:03:23:723 APS-DATA.request id: 192 erase from queue 11:03:26:115 APS-DATA.request id: 194, addrmode: 0x03, addr: 0x00212effff048b9a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00 11:03:26:121 APS-DATA.confirm id: 194, status: 0x00 SUCCESS 11:03:26:121 APS-DATA.confirm request id: 194 -> confirmed, timeout 29784144 11:03:26:123 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 241, rssi: 19 11:03:26:123 APS-DATA.indication request id: 194 -> finished 11:03:26:123 APS-DATA.request id: 194 erase from queue 11:03:26:834 APS-DATA.confirm id: 171, status: 0xA7 NO_ACK 11:03:28:516 APS-DATA.request id: 196, addrmode: 0x03, addr: 0x00212effff048b9a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00 11:03:28:527 APS-DATA.confirm id: 196, status: 0x00 SUCCESS 11:03:28:527 APS-DATA.confirm request id: 196 -> confirmed, timeout 28994096 11:03:28:531 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 4, rssi: 38 11:03:28:531 APS-DATA.indication request id: 196 -> finished 11:03:28:531 APS-DATA.request id: 196 erase from queue 11:03:31:271 Current channel 15 11:03:31:279 Device TTL 1449 s flags: 0x7 11:03:31:875 APS-DATA.request id: 198, addrmode: 0x03, addr: 0x00178801027deb2c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00 11:03:32:073 APS-DATA.confirm id: 198, status: 0x00 SUCCESS 11:03:32:073 APS-DATA.confirm request id: 198 -> confirmed, timeout 28538136 11:03:36:283 dev /dev/ttyAMA0 11:03:36:284 GW firmware version: 0x264a0700 11:03:36:284 GW firmware version is up to date: 0x264a0700 11:03:57:075 APS-DATA.request id: 199, addrmode: 0x02, addr: 0x5e07, profile: 0x0000, cluster: 0x0002, ep: 0x00 -> 0x00 queue: 1 len: 3 tx.options 0x04

Next problem, I can't add any lights or sensors 😅I searched for lights and sensors, and it couldn't find any (and they are set to factory defaults)

[sandert98]

Problem for adding lights is solved, I have a new device that occured as interference. So this issue/bug report is only about (I think) the requirement of a port number for VNC.

[frenck]

Well, you basically activated VNC by setting these options, which is more a workaround, than a real solution (not the intended working).

At least I have a pointer to work on, so that is awesome! Thank you.

Will look into this as soon as possible for me.

[chbndrhnns]

I am facing this issue at random times, as well. I see a similar error message and the container dies after this line:

Could not connect to any X display.

I have to manually restart it then from the GUI but until my whole zigbee network is down which is kind of bad. I am running it on a Synology DS218+ and in the last months I was running a Docker container with deconz outside of hass and had not a single issue there.

[d0ugal]

I upgraded from 3.6 to 3.8 today and didn't hit the issue. So think this must be 3.7 specific and a regression in deconz itself?

If anyone has this issue in 3.8 please comment and it can be reopened.

[frenck]

Nice! Thanks for letting us know! :+1:

[thelefty]

I have this problem in 5.3.2