deconz 6.1.0 doesnt start on Raspberry Pi 4 #1480
Comments
|
Have a similar problem , Deconz upgraded to Version 6.0.0 on Hass.io on PI4. and now it can't start. Have also tried to reboot PI [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [16:58:29] INFO: Waiting for VNC to start |
|
Have also an problem with DeCONZ 6.1.0 on Home Assistant (Hass.io) on an Raspberry Pi 4 with 2 GB of RAM. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. |
|
For me 6.1 fails on Hassio@Synology |
|
After uptading to deCONZ 6.0.1, the add-on doesn't start on my Raspberry Pi 3 Model B+ 32bit with ConBee USB gateway |
|
the armhf Issues seems to be fixed with 6.1.0 (9e67f09) Unfortunately, my Supervisor UI doesnt offer me this Version yet |
|
Same here for 6.0. Unfortunately I tried to uninstall, but didn't help. |
|
Upgraded to 6.1.0 (Reload @ Supervisor Menu) |
fti7
changed the title
|
The 6.1.0 version solved the problem on my Raspberry Pi 3 Model B+ |
Idem at Pi4 4GB after update from 6.0.1 to 6.1.0. |
|
For 6.1.0 with the "qt.qpa.screen: QXcbConnection: Could not connect to display :0" Error: |
|
My deconz addon has not started since the update from 5.3.6 to 6.1.0. I have a Raspberry 4 with 4GB Ram.
|
Disable VNC fix the Problem on my RP4. |
Thanks, this workaround let's my Deconz addon start. |
|
Same issue after upgrading to 6.1.0 |
|
Guys the issue is clear. Please, instead of "same issue" or "me too", please just use the 👍 emoji on the initial issue report/description. Thanks 👍 |
|
My current feeling says this is limited to ARMHF installations like the Raspberry Pi. Edit: Got it reproduced on an ODROID N2, so I have something to work with now. Looking for a solution. |
|
If a Intel Celeron J3355 with 64 arch counts for AMD64: No issues on that (synology DS218+ VM with HA generic install and Addon). |
|
I've also upgraded deCONZ to the 6.1.0 release. here is a snippet of the log: |
|
@GitHubxtsnl That issue is not related to this one. However, it looks like an issue with deCONZ itself, which should be reported with dresden/deCONZ. |
|
A workaround for the VNC issue has been found, currently testing an implemented change. |
|
Issue remains after update to 6.1.1: Deconz add-on starts and I can open UI, and IKEA lights are detected, but cannot trigger any action on them. Also cannot add new lights from discovery. Tried to restart Hassio and behaviour is the same |
|
I can confirm for aarch64 (Cortex-A53) the last version 6.1.1 resolved issue with VNC - had exactly as described in the issue description - and everything works fine now. Thanks for the quick fix. |
|
@vdiogo That is not the problem reported in this issue. Please don't stack different problems, instead open up separate issues with details for each problem. Thanks 👍 |
|
@frenck noted 👍 |
|
after I preformed the update to 6.1.1, enabled VNC again all seems to be working. I had to add the deCONZ integration again allowing it to pair with the ConBeeII. |
My error seems very similar to what is reported in this issue, but in my case on amd64 platform. Logging below is from a local ly installed version where I added the ARCH info: If I remove the VNC port mapping the output changes, but the addon still fails to start: |
|
Upgraded deconz to 6.1.1 with hassio addons on my synology today and now i cant start it. reinstall did not help. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. |
|
Same error as above with 6.1.2 When restoring back to 5.3.6 it works again! |
|
For synology user or people with old EOL kernel 3 -> #1487 |
homeassistant/armhf-addon-deconz:6.0.1
EDIT: FIXED in 6.1.0 - But still not starting - see bugreports below
Workround:
For 6.1.0 with the "qt.qpa.screen: QXcbConnection: Could not connect to display :0" Error:
Under Configure, remove the Host Port mapping for 5900/tcp.
After this, VNC will not be started
@pvizeli can you maybe look into this? thx
The text was updated successfully, but these errors were encountered: