deCONZ - Official thread

Configuration Zigbee
562

The docker container and the standalone deCONZ behave differently. As far as I know the docker version doesn’t show wifi as it doesn’t apply in the case of use in Docker.

To recreate the container, you need to stop your existing container, delete it, and recreate it using the same config as the first container but you can point to a new image:

docker stop container-name
docker rm container-name
docker run -d [your options here] marthoc/deconz:2.05.66
563

@DieterClaeys there is an official hassio deCONZ add-on that will have continued support

564

marthocoo, thanks for the response

565

@Robban, from what I understand in the tread here, the AddOn will no further will be developed…
(post of Mar 18)

Edit 02: found out there are more then one add-on :slight_smile: , and one of them will not be supported anymore - sorry for the confusion

566

Thank you. This solves at least the problem with two gateways, when i open a private window in chrome.

567

Hi guys. In a quest to get a stable/supported Zigbee solution so I can migrate away from Smartthings, I bought a ConBee II USB stick, and installed the deCONZ addon, but I have had zero luck so far. Wondering if someone can help?

  1. I’m running Hassio on Proxmox and HA v0.98.3. Adding the USB to the VM seems to work fine. It shows up as ConBee II on USB3. I’ve changed the config file to /dev/ttyACM0
  2. I do have ZHA installed and running with a another ZigBee USB dongle. Would this be causing any issues?
  3. I’m not really sure how to tell from the logs if the USB hardware was found correctly. It keeps going into a device state timeout, but maybe this is normal? (see below)
  4. It shows up in the HA Integrations with a gateway and a daylight sensor, but the name is deCONZ-000000000000. Does this indicate that the hardware has been found?
  5. I can’t open the WebUI either using my DuckDNS or the IP address (tried both http/https). I had been playing with XGINX, but all the other WebUI pages work
  6. I tried the ConBee II USB stick in my laptop with the Windows software from the manufacture’s website and it seems to work OK

Log tail

13:08:03:755 COM: /dev/ttyACM0 / serialno:
13:08:03:755 COM: --dev: /dev/ttyACM0 (ConBee II)
13:08:04:245 device state timeout ignored in state 2
13:08:05:245 device state timeout ignored in state 2
13:08:06:245 device state timeout ignored in state 2
13:08:07:245 device state timeout ignored in state 2
13:08:08:245 device state timeout ignored in state 2
13:08:09:245 device state timeout (handled)
13:08:09:745 wait reconnect 15 seconds

UPDATE: Sorry, my bad. I can get into the WebUI now, but gateway page shows:

Vendor dresden elektronik
Product ConBee II
Version 2.05.67 / 22/04/2019
Firmware Not connected

I think the Firmware line means the that USB device isn’t found yeah?

Thanks!

568

The WebUI runs regardless of whether the Conbee stick is found or not.

Are there any other devices other than /dev/ttyACM0?
I run Hassio under VirtualBox, but my Conbee uses /dev/ttyUSB0.

1 Like
569

Same here, running on a esxi server, also shows ttyUSBx

You can see it in hassio in the system hardware tab , what ports are used

1 Like
570

I’m getting this message in the gateway settings: “Firmware not connected”

I’ve been running Conbee 2 for a couple of months and have about 15 Ikea lights and 30 Xiaomi sensor working smoothly. I wanted to migrate my Hass.io to a new SD card, so I made a snap shot and restored it to the new SD card. After rebooting on the new sdcard the Phoson App say no Ligths connected but 30 Xiaomi sensor are connect. In the settings I can see “Firmware Not Connected”.

I restartet the Hassio on the original SDCard, but issue still exists. (Bisides Node Red gives me a bad gateway error)

Any help is appreciated

starting version 232
[08:47:23] INFO: Starting the deCONZ gateway…
[08:47:23] INFO: Running the deCONZ OTA updater…
[08:47:23] INFO: Running the IKEA OTA updater…
[08:47:23] INFO: Running Hass.io discovery task…
{“uuid”:“18c34b4b62fa47c09e376a9451f18f76”}
[08:47:27] INFO: Success send discovery information to Home Assistant
[08:47:27] INFO: deCONZ is set up and running!
libpng warning: iCCP: known incorrect sRGB profile
This plugin does not support propagateSizeHints()
This plugin does not support propagateSizeHints()
08:47:28:910 HTTP Server listen on address 0.0.0.0, port: 40850, root: /usr/share/deCONZ/webapp/
08:47:29:347 CTRL. 3.16.208:47:29:441 dev /dev/ttyAMA0
08:47:29:441 COM: /dev/ttyACM1 / serialno:
08:47:29:441 COM: --dev: /dev/ttyACM1 (ConBee II)
08:47:29:442 ZCLDB init file /data/.local/share/dresden-elektronik/deCONZ/zcldb.txt
08:47:30:429 parent process bash
08:47:30:430 gw run mode: docker/hassio
08:47:30:430 GW sd-card image version file does not exist: /data/.local/share/dresden-elektronik/deCONZ/gw-version
08:47:30:430 sd-card cid: 9e4245202020202002ffffffff012709
08:47:30:433 DB sqlite version 3.16.2
08:47:30:437 DB PRAGMA page_count: 40
08:47:30:437 DB PRAGMA page_size: 4096
08:47:30:437 DB PRAGMA freelist_count: 3
08:47:30:437 DB file size 163840 bytes, free pages 3
08:47:30:437 DB PRAGMA user_version: 6
08:47:30:437 DB cleanup
08:47:30:496 DB create temporary views
08:47:30:560 don’t close database yet, keep open for 900 seconds
08:47:30:561 started websocket server at port 40860
08:47:30:565 discovery updated announce interval to 10 minutes
08:47:30:648 found node plugin: libde_rest_plugin.so - REST API Plugin
08:47:30:655 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
08:47:35:903 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
08:47:35:936 dev /dev/ttyAMA0
08:47:35:936 COM: /dev/ttyACM1 / serialno:
08:47:35:936 COM: --dev: /dev/ttyACM1 (ConBee II)
08:47:36:013 dev /dev/ttyAMA0
08:47:36:013 COM: /dev/ttyACM1 / serialno:
08:47:36:013 COM: --dev: /dev/ttyACM1 (ConBee II)
08:47:36:054 dev /dev/ttyAMA0
08:47:36:054 COM: /dev/ttyACM1 / serialno:
08:47:36:054 COM: --dev: /dev/ttyACM1 (ConBee II)
08:47:36:561 New websocket 192.168.99.108:44962 (state: 3)
08:47:36:598 dev /dev/ttyAMA0
08:47:36:851 discovery network reply error: Error transferring http://dresden-light.appspot.com/discover - server replied: Service Unavailable
08:47:37:096 device state timeout ignored in state 2
08:47:38:096 device state timeout ignored in state 2
08:47:39:097 device state timeout ignored in state 2
08:47:40:097 device state timeout ignored in state 2
08:47:40:305 New websocket 192.168.99.109:59645 (state: 3)
08:47:41:097 device state timeout ignored in state 2
08:47:42:097 device state timeout (handled)
08:47:42:547 New websocket 192.168.99.109:59646 (state: 3)
08:47:42:559 New websocket 192.168.99.109:59647 (state: 3)
08:47:42:571 New websocket 192.168.99.109:59648 (state: 3)
08:47:42:583 New websocket 192.168.99.109:59649 (state: 3)
08:47:42:596 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
08:47:42:596 device state timeout ignored in state 1
08:47:43:097 wait reconnect 15 seconds
08:47:44:096 wait reconnect 14 seconds
08:47:45:096 wait reconnect 13 seconds
08:47:46:096 wait reconnect 12 seconds
08:47:47:096 wait reconnect 11 seconds
08:47:47:137 dev /dev/ttyAMA0
08:47:48:097 wait reconnect 10 seconds
08:47:49:096 wait reconnect 9 seconds
08:47:50:096 wait reconnect 8 seconds
08:47:51:097 wait reconnect 7 seconds
08:47:52:097 wait reconnect 6 seconds
08:47:53:096 wait reconnect 5 seconds
08:47:54:096 wait reconnect 4 seconds
08:47:55:096 wait reconnect 3 seconds
08:47:56:096 wait reconnect 2 seconds
08:47:57:096 wait reconnect 1 seconds
08:47:57:143 dev /dev/ttyAMA0
08:47:57:143 COM: /dev/ttyACM1 / serialno:
08:47:57:143 COM: --dev: /dev/ttyACM1 (ConBee II)
08:47:57:177 dev /dev/ttyAMA0
08:47:58:241 device state timeout ignored in state 2
08:47:59:193 device state timeout ignored in state 2
08:48:00:144 device state timeout ignored in state 2
08:48:01:097 device state timeout ignored in state 2
08:48:02:096 device state timeout ignored in state 2
08:48:03:096 device state timeout (handled)
08:48:03:596 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
08:48:03:596 device state timeout ignored in state 1
08:48:04:096 wait reconnect 15 seconds
08:48:05:096 wait reconnect 14 seconds
08:48:06:097 wait reconnect 13 seconds
08:48:07:003 scan skip host .108
08:48:07:096 wait reconnect 12 seconds
08:48:07:139 dev /dev/ttyAMA0

571

Based on the wait reconnect message it looks like you have the wrong USB port configured. The post from Fabio above your post shows how to check the used ports in Hassio.

572

This is my hw config.
image
I suppose it should be of the highlighted, which I have tried. Do I need to restart Deconz or Hassio?

573

strange, on my esxi, i have enabled passthrough an USB port, so i actually see an USB port there, not acm0

574

I’ve tried ttyAMCM0 againg and this time it worked. I’ve got rid of the “Firmware not connected” and the lights are back. But the conbee is very slow now. It takes about 5 a light and my scenes with 8 lights about a minutes.
Any ideas?

575

Based on this I would choose the dev/serial/by-id with Conbee II in the name.
Advantage of using this one is that it always stays the same, even after restarts.

576

You can also use the /dev/by-id/usb-dresden… path in your config.
This path works and will always be the same.

577

Not sure if this is specific to my setup, but just thought I’d highlight something I experienced over the last few days in relation to this conversation. I use the deconz Integration and as part of the configuration had identified the USB port into which conbee II is plugged using the “/dev/serial/by-id/usb-dresden…” definition.

Not sure where this has happened but following an upgrade to 0.98.2 and the deconz integration to 3.4 and subsequently to 3.5 the integration stopped recognising the USB device.

When I reverted to “/dev/tty/ACM0” it started working again.

578

Thx for the help getting configuration fixed. Next issue.
I’m able to connect ikea lights, but when I turn the light on in the Poscon app it takes 5-10 second before the light reacts. My deconz log is full of this

13:05:09:596 delay sending request 125 dt 3 ms to 0xD0CF5EFFFE72CBC7, cluster 0x0008
13:05:09:696 delay sending request 125 dt 3 ms to 0xD0CF5EFFFE72CBC7, cluster 0x0008
13:05:09:797 delay sending request 125 dt 3 ms to 0xD0CF5EFFFE72CBC7, cluster 0x0008
13:05:09:896 delay sending request 125 dt 3 ms to 0xD0CF5EFFFE72CBC7, cluster 0x0008
13:05:09:998 delay sending request 125 dt 3 ms to 0xD0CF5EFFFE72CBC7, cluster 0x0008
13:05:10:096 delay sending request 125 dt 4 ms to 0xD0CF5EFFFE72CBC7, cluster 0x0008
13:05:10:196 delay sending request 125 dt 4 ms to 0xD0CF5EFFFE72CBC7, cluster 0x0008
13:05:10:297 delay sending request 125 dt 4 ms to 0xD0CF5EFFFE72CBC7, cluster 0x0008
13:05:10:396 delay sending request 125 dt 4 ms to 0xD0CF5EFFFE72CBC7, cluster 0x0008
13:05:10:496 delay sending request 125 dt 4 ms to 0xD0CF5EFFFE72CBC7, cluster 0x0008
13:05:10:597 delay sending request 125 dt 4 ms to 0xD0CF5EFFFE72CBC7, cluster 0x0008
13:05:10:696 delay sending request 125 dt 4 ms to 0xD0CF5EFFFE72CBC7, cluster 0x0008
13:05:10:796 delay sending request 125 dt 4 ms to 0xD0CF5EFFFE72CBC7, cluster 0x0008
13:05:10:896 delay sending request 125 dt 4 ms to 0xD0CF5EFFFE72CBC7, cluster 0x0008
13:05:10:996 delay sending request 125 dt 4 ms to 0xD0CF5EFFFE72CBC7, cluster 0x0008

579

Anyone using other remote controllers than these with deconz?

HUE_DIMMER_REMOTE,
TRADFRI_REMOTE, TRADFRI_WIRELESS_DIMMER,
AQARA_DOUBLE_WALL_SWITCH, AQARA_MINI_SWITCH, AQARA_ROUND_SWITCH, AQARA_SQUARE_SWITCH,

580

I use the Ikea tradfri remote

581

The two button one?