deCONZ - Official thread

Jus a shot in the dark: Noticed that in deconz app configuration there are only 2 options where to be select the device, neither one was the one currently in use. (I have /dev/ttyACM0)

However, there is the option for /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2215107-if00 with which the VNC seems to appear, Phoscon app does not connect to the gateway, though.

There is an option (3 dots on the upper right corner) to use .yaml to configure device, which might accept others than listed.

However, I cannot try right now, my system is controlling my garage, and there are people inside, who probably do not apprecaite lights going off :slight_smile: Can someone try?

Same issue here. How to rollback without a backup?

If anyone has the same problems. Its not a real & solid solution but a workaround:

  1. Stop add-on and disable autostart/watchdog
  2. Open terminal
  3. Check what is the latest version of used container docker images
  4. Download needed version docker pull homeassistantant/armhf-addon-deconz:6.10.0
  5. Delete version what is used by add-on docker rmi homeassistantant/armhf-addon-deconz:6.11.0
  6. Re-tag downloaded version with deleted docker tag homeassistantant/armhf-addon-deconz:6.10.0 homeassistantant/armhf-addon-deconz:6.11.0
  7. Start add-on.

Same Problem here! Rpi4, Conbee2 with extension, seems like deconz 6.11.0 is broken!

Edit: they are into it already! 6.11.0 update breaks DeconZ API · Issue #2317 · home-assistant/addons · GitHub

2 Likes

Same here, deconz 6.11.0 on ha rpi4 conbee ii is broken!

Mine’s gone too: Rpi4, Conbee2, HA OS. From the logs:


2021-12-20 15:27:32 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry 00212E053928 for deconz
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 313, in async_setup
result = await component.async_setup_entry(hass, self) # type: ignore
File "/usr/src/homeassistant/homeassistant/components/deconz/__init__.py", line 37, in async_setup_entry
if not await gateway.async_setup():
File "/usr/src/homeassistant/homeassistant/components/deconz/gateway.py", line 171, in async_setup
self.api = await get_gateway(
File "/usr/src/homeassistant/homeassistant/components/deconz/gateway.py", line 280, in get_gateway
await deconz.refresh_state()
File "/usr/local/lib/python3.9/site-packages/pydeconz/gateway.py", line 121, in refresh_state
data = await self.request("get", "")
File "/usr/local/lib/python3.9/site-packages/pydeconz/gateway.py", line 141, in request
return await self._request(
File "/usr/local/lib/python3.9/site-packages/pydeconz/gateway.py", line 160, in _request
raise ResponseError(
pydeconz.errors.ResponseError: Invalid content type: text/html
15:39:58:956 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2147277-if00 / serialno: DE2147277, ConBee II
PROTO: CRC error
15:40:00:452 Device firmware version 0x26660700 ConBee II
15:40:00:455 unlocked max nodes: 512
15:40:00:474 Device protocol version: 0x010C
15:40:00:537 Current channel 25
15:40:00:542 CTRL ANT_CTRL 0x03
15:40:00:554 Device protocol version: 0x010C
15:40:00:581 CTRL ANT_CTRL 0x03
parse error: Invalid numeric literal at line 1, column 34

same here :frowning:

… me too. Going back to the previous version.

Sampe problem here, I had to roll back to the previous version

Got the same issue. Went back to previous version.

Also same issue here. After update devices are unavailable. Using Conbee II in VM on Synology.

Same here running I’m on NUC with Proxmox VM. Reroll back to v6.10.0. Will wait for the next ‘stable’ update

Thank god, Its not just me… Rasp Pi 4, using Conbee II - rolling back now then.

How do you roll back?

Maybe wait for 6.11.1 ?

I also have the same problem

Same here. Backup saved my day …

1 Like

Same here. Rolled back with Backup.

6.11.1 launched already

1 Like

Same problem for me. Thanks for defaulting backup with ALL updates :smiling_face_with_three_hearts: