Deconz not functional after updating to HassOS 4.8

repjas · June 1, 2020, 1:52pm

I’ve just updated to HassOS 4.8 and after restart all deCONZ devices lost availability.

Below is the log. Any ideas?

[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] done.
[services.d] starting services
[services.d] done.
starting version 232
[15:43:22] INFO: Waiting for device…
[15:43:22] INFO: Starting the deCONZ gateway…
libpng warning: iCCP: known incorrect sRGB profile
[15:43:23] INFO: Starting Nginx…
[15:43:23] INFO: Running Home Assistant discovery task…
2020/06/01 15:43:23 [notice] 562#562: using the “epoll” event method
2020/06/01 15:43:23 [notice] 562#562: nginx/1.10.3
2020/06/01 15:43:23 [notice] 562#562: OS: Linux 5.4.42-v7l
2020/06/01 15:43:23 [notice] 562#562: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2020/06/01 15:43:23 [notice] 562#562: start worker processes
2020/06/01 15:43:23 [notice] 562#562: start worker process 570
[15:43:23] INFO: Running the deCONZ OTA updater…
[15:43:23] INFO: Running the IKEA OTA updater…
[15:43:23] INFO: Running the LEDVANCE/OSRAM OTA updater…
[15:43:23] INFO: deCONZ is set up and running!
This plugin does not support propagateSizeHints()
This plugin does not support propagateSizeHints()
[15:43:33] INFO: Successfully send discovery information to Home Assistant.
This plugin does not support propagateSizeHints()
15:43:23:095 HTTP Server listen on address 0.0.0.0, port: 40850, root: /usr/share/deCONZ/webapp/
15:43:23:152 CTRL. 3.16.215:43:23:230 dev /dev/ttyAMA0
15:43:23:230 COM: --dev: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2194288-if00 (RaspBee)
15:43:23:231 ZCLDB init file /data/.local/share/dresden-elektronik/deCONZ/zcldb.txt
15:43:23:388 parent process bash
15:43:23:388 gw run mode: docker/hassio
15:43:23:388 GW sd-card image version file does not exist: /data/.local/share/dresden-elektronik/deCONZ/gw-version
15:43:23:388 sd-card cid: 1b534d454231515430ffffffff014200
15:43:23:390 DB sqlite version 3.16.2
15:43:23:392 DB PRAGMA page_count: 30
15:43:23:392 DB PRAGMA page_size: 4096
15:43:23:392 DB PRAGMA freelist_count: 0
15:43:23:392 DB file size 122880 bytes, free pages 0
15:43:23:393 DB PRAGMA user_version: 6
15:43:23:393 DB cleanup
15:43:23:393 DB create temporary views
15:43:23:409 don’t close database yet, keep open for 900 seconds
15:43:23:410 started websocket server at port 8081
15:43:23:418 found node plugin: libde_rest_plugin.so - REST API Plugin
15:43:23:421 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
15:43:27:440 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
15:43:27:472 dev /dev/ttyAMA0
15:43:27:472 COM: --dev: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2194288-if00 (RaspBee)
15:43:28:237 dev /dev/ttyAMA0
15:43:28:955 Announced to internet http://dresden-light.appspot.com/discover
15:43:28:956 discovery server date: Mon, 01 Jun 2020 13:43:28 GMT
15:43:28:956 local time seems to be ok
15:43:28:956 discovery found version 2.04.35 for update channel stable
15:43:37:201 dev /dev/ttyAMA0
15:43:37:201 COM: --dev: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2194288-if00 (RaspBee)
15:43:38:207 dev /dev/ttyAMA0
15:43:38:207 COM: --dev: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2194288-if00 (RaspBee)
15:43:38:237 dev /dev/ttyAMA0
15:43:38:237 COM: --dev: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2194288-if00 (RaspBee)
15:43:38:269 dev /dev/ttyAMA0
15:43:38:378 New websocket 172.30.32.1:37998 (state: 3)
15:43:39:209 dev /dev/ttyAMA0
15:43:39:209 COM: --dev: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2194288-if00 (RaspBee)
15:43:39:239 dev /dev/ttyAMA0
15:43:39:239 COM: --dev: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2194288-if00 (RaspBee)
15:43:39:679 Device firmware version 0x264A0700
15:43:39:686 unlocked max nodes: 200
15:43:39:762 Device protocol version: 0x010B
15:43:39:769 new node - ext: 0x00212effff05a459, nwk: 0x0000
15:44:02:182 don’t close database yet, keep open for 900 seconds
15:44:02:183 LightNode 2: Lamp hoek added
15:44:04:680 don’t close database yet, keep open for 900 seconds
15:44:04:680 LightNode 3: Hal licht added
15:44:06:018 don’t close database yet, keep open for 900 seconds
15:44:06:018 LightNode 4: Lamp monkey added
15:44:08:434 SensorNode 2 set node 0x00158d00034f6464
15:44:08:434 SensorNode 3 set node 0x00158d00034f6464
15:44:08:459 SensorNode 4 set node 0x00158d0003f42d4c
15:44:08:460 SensorNode 5 set node 0x00158d0003f42d4c
15:44:08:474 SensorNode 6 set node 0x00158d00044b7055
15:44:08:514 SensorNode 9 set node 0x00158d00032b8686
15:44:17:003 SensorNode 7 set node 0x00158d0003556337
15:44:17:004 SensorNode 8 set node 0x00158d000346b27b
15:44:17:087 invalid current channel 0 (TODO)
15:44:17:091 Remove websocket 172.30.32.1:37998 after error Unknown error
15:44:17:125 dev /dev/ttyAMA0
15:44:17:159 Current channel 25
15:44:17:175 CTRL ANT_CTRL 0x03
15:44:17:176 New websocket 172.30.32.1:38082 (state: 3)
15:44:17:199 Device protocol version: 0x010B
15:44:17:249 Current channel 25
15:44:17:264 CTRL ANT_CTRL 0x03
15:44:19:433 don’t close database yet, keep open for 900 seconds
15:44:19:433 LightNode 1: Configuration tool 1 added
15:44:23:174 Current channel 25
15:44:23:182 Device TTL 2756 s flags: 0x7
15:44:27:204 dev /dev/ttyAMA0

henrikbla · June 1, 2020, 2:21pm

I only have one Zigbee device at the moment, but that device (door open / close sensor) was at first showing as “unavailable” but became available after the next state update (opening the door in my case) and has been working ever since.

tirelli · June 1, 2020, 3:12pm

Same issue here. After upgrading to HassOS 4.8 all my Zigbee devices are unavailable. Please fix it. Thank you.

Virgil_Popa · June 1, 2020, 3:55pm

Yap, is down

repjas · June 1, 2020, 4:57pm

I am considering to restore a snapshot that I made just before the update. But will that also downgrade the HassOS version? I don’t think it will actually?

Willybits · June 1, 2020, 5:24pm

Snapshot does not include the OS, so re-installing HassOS 4.6 (in my case) and restoring a snapshot then is the way to go.
For me the problems began after HassOS 4.7. Weird issues with USB stopping after 9 hours, or reboots hanging, Supervisor not starting, etc etc. All weird issues. But at the same time I could not pinpoint it as there were also new Home assistant versions, new Deconz, New ConbeeII firmware. After a lot of testing it is indeed the HassOS that causes the problems for me.
Back at 4.6 now with a good snapshot so safe for me to help testing.

I am also using a beta device (Odroid N2) so problems were expected. After these issues I tried to install my Pi4 again, but that also gave a lot of problems, not booting, slow, running hot, no UI reachable. All on HassOS 4.8.

Please do try to find id the issue is HassOS 4.8 or 4.7 for you as well and report bugs and fill in the forms and supply the logs. That will help fix these issues for sure.

dtidey · June 1, 2020, 5:36pm

Another log file to assist with debugging.

[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] done.
[services.d] starting services
[services.d] done.
starting version 232
[18:26:06] INFO: Waiting for device…
[18:26:07] INFO: Starting VNC server…
[18:26:11] INFO: Starting the deCONZ gateway…
libEGL warning: DRI2: failed to open swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: DRI2: failed to open swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)
libpng warning: iCCP: known incorrect sRGB profile
[18:26:12] INFO: Starting Nginx…
[18:26:12] INFO: Running Home Assistant discovery task…
[18:26:12] INFO: Running the deCONZ OTA updater…
[18:26:13] INFO: Running the IKEA OTA updater…
2020/06/01 18:26:13 [notice] 586#586: using the “epoll” event method
2020/06/01 18:26:13 [notice] 586#586: nginx/1.10.3
2020/06/01 18:26:13 [notice] 586#586: OS: Linux 5.4.42-v7
2020/06/01 18:26:13 [notice] 586#586: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2020/06/01 18:26:13 [notice] 586#586: start worker processes
2020/06/01 18:26:13 [notice] 586#586: start worker process 598
[18:26:13] INFO: Running the LEDVANCE/OSRAM OTA updater…
[18:26:13] INFO: deCONZ is set up and running!
[18:26:30] INFO: Successfully send discovery information to Home Assistant.
18:26:12:747 HTTP Server listen on address 0.0.0.0, port: 40850, root: /usr/share/deCONZ/webapp/
18:26:12:813 CTRL. 3.16.218:26:13:012 dev /dev/ttyAMA0
18:26:13:012 COM: /dev/ttyAMA0 / serialno:
18:26:13:012 COM: --dev: /dev/ttyAMA0 (RaspBee)
18:26:13:013 ZCLDB init file /data/.local/share/dresden-elektronik/deCONZ/zcldb.txt
18:26:13:501 parent process bash
18:26:13:501 gw run mode: docker/hassio
18:26:13:501 GW sd-card image version file does not exist: /data/.local/share/dresden-elektronik/deCONZ/gw-version
18:26:13:502 sd-card cid: 035344534333324780ffffffff0132cb
18:26:13:514 DB sqlite version 3.16.2
18:26:13:517 DB PRAGMA page_count: 33
18:26:13:517 DB PRAGMA page_size: 4096
18:26:13:517 DB PRAGMA freelist_count: 1
18:26:13:517 DB file size 135168 bytes, free pages 1
18:26:13:517 DB PRAGMA user_version: 6
18:26:13:517 DB cleanup
18:26:13:519 DB create temporary views
18:26:13:561 don’t close database yet, keep open for 900 seconds
18:26:13:562 started websocket server at port 8081
18:26:13:577 found node plugin: libde_rest_plugin.so - REST API Plugin
18:26:13:587 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
18:26:30:123 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
18:26:30:169 dev /dev/ttyAMA0
18:26:30:169 COM: /dev/ttyAMA0 / serialno:
18:26:30:169 COM: --dev: /dev/ttyAMA0 (RaspBee)
18:26:30:436 New websocket 172.30.32.1:58122 (state: 3)
18:26:30:498 dev /dev/ttyAMA0
18:26:30:874 Announced to internet https://phoscon.de/discover
18:26:30:875 discovery server date: Mon, 01 Jun 2020 17:26:30 GMT
18:26:30:875 local time seems to be ok
18:26:30:875 discovery found version 2.04.35 for update channel stable
18:26:40:511 dev /dev/ttyAMA0
18:26:40:511 COM: /dev/ttyAMA0 / serialno:
18:26:40:511 COM: --dev: /dev/ttyAMA0 (RaspBee)
18:26:40:554 dev /dev/ttyAMA0
18:26:41:031 device state timeout ignored in state 2
18:26:41:982 device state timeout ignored in state 2
18:26:42:965 device state timeout ignored in state 2
18:26:43:965 device state timeout ignored in state 2
18:26:44:965 device state timeout ignored in state 2
18:26:45:965 device state timeout (handled)
18:26:45:978 device disconnected reason: 1, index: 0
18:26:46:465 wait reconnect 15 seconds
18:26:46:465 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
18:26:46:465 device state timeout ignored in state 1
18:26:47:465 wait reconnect 14 seconds
18:26:48:465 wait reconnect 13 seconds
18:26:49:465 wait reconnect 12 seconds
18:26:49:466 start reconnect to network
18:26:50:465 wait reconnect 11 seconds
18:26:50:512 dev /dev/ttyAMA0
18:26:51:465 wait reconnect 10 seconds
18:26:52:465 wait reconnect 9 seconds
18:26:53:466 wait reconnect 8 seconds
18:26:54:465 failed to reconnect to network try=1
18:26:54:465 wait reconnect 7 seconds
18:26:55:466 wait reconnect 6 seconds
18:26:56:465 wait reconnect 5 seconds
18:26:57:465 wait reconnect 4 seconds
18:26:58:465 wait reconnect 3 seconds
18:26:59:465 failed to reconnect to network try=2
18:26:59:465 wait reconnect 2 seconds
18:27:00:466 wait reconnect 1 seconds
18:27:00:516 dev /dev/ttyAMA0
18:27:00:516 COM: /dev/ttyAMA0 / serialno:
18:27:00:516 COM: --dev: /dev/ttyAMA0 (RaspBee)
18:27:00:565 dev /dev/ttyAMA0
18:27:01:043 device state timeout ignored in state 2
18:27:01:993 device state timeout ignored in state 2
18:27:02:965 device state timeout ignored in state 2
18:27:03:965 device state timeout ignored in state 2
18:27:04:465 try to reconnect to network try=3
18:27:05:965 device state timeout ignored in state 2
18:27:06:965 device state timeout (handled)
18:27:06:975 device disconnected reason: 1, index: 0
18:27:07:465 wait reconnect 15 seconds
18:27:07:465 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
18:27:07:465 device state timeout ignored in state 1
18:27:08:465 wait reconnect 14 seconds
18:27:09:465 failed to reconnect to network try=4
18:27:09:465 wait reconnect 13 seconds
18:27:10:465 wait reconnect 12 seconds
18:27:10:511 dev /dev/ttyAMA0
18:27:11:465 wait reconnect 11 seconds

Let me know if I can be of any assistance with debugging the problem.

David

sec · June 1, 2020, 5:39pm

Had the same problem (with a RaspBee). Solved it by changing the device in the addon config to /dev/ttyS0

pedrohbr · June 1, 2020, 6:50pm

Had the same problem (with a RaspBee). Solved it by changing the device in the addon config to /dev/ttyS0

Same issue with me, and this fix addressed the problem.

dtidey · June 1, 2020, 7:16pm

Just to confirm that changing the device in the addon config to /dev/ttyS0 resolves this problem.

David

repjas · June 1, 2020, 8:26pm

I have a Conbee II and for me this didn’t fix the issue. Using /dev/ttyS0 results in ‘no device found’.
Using the generic path /dev/ttyACM0 also didn’t work.

Can anybody who made it work explain what they did exactly?

robidog · June 1, 2020, 8:41pm

Confirm that ttyS0 solved the problem on my Pi4 with a RaspBee.

robidog · June 1, 2020, 8:42pm

I believe ttyS0 only applies to RaspBee, but I could be wrong.

repjas · June 1, 2020, 8:54pm

I used the /dev/ttyACM0 instead, and it seems to recognize the device. However can’t get it to work. Can you explain the specific steps you did?

bart · June 1, 2020, 9:00pm

Here the same. Stoped working. After changing the config to /dev/ttyS0 , it worked again. thank you!

alvinger · June 2, 2020, 8:54am

@sec, thank you! I spent a couple of hours trying to debug my install before stumbling onto your reply.

This really should be mentioned somewhere in the release notes. Or better yet, automatically changed.

repjas · June 2, 2020, 9:11am

Anybody already got his working with a conbee stick? The above solution does not work for me.

Rendeik · June 2, 2020, 9:29am

It is not the first time that happens, to me almost every time I update the OS I lose the connection with the devices.

Megachef · June 2, 2020, 11:30am

Anything new on this?

Tried this:

/dev/ttyS0
And also this:

/dev/ttyAMA0
/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2141012-if00
/dev/ttyACM0

Nothing works, HA cant find anything, its unavailable

ValleBL · June 2, 2020, 11:41am

Same for Homematic using RPI-RF-Mod

Iv already played arround but nothing worked.

2020-06-02 13:46:00,844 [ERROR] BidCosRpcDispatcher - Could not register BidCos-RF_java
2020-06-02 13:46:05,845 [ERROR] BidCosRpcDispatcher - Could not register BidCos-RF_java
2020-06-02 13:46:10,845 [ERROR] BidCosRpcDispatcher - Could not register BidCos-RF_java
2020-06-02 13:46:15,845 [ERROR] BidCosRpcDispatcher - Could not register BidCos-RF_java