addons: deCONZ - FATAL: No device since 3.4 / 3.5

Today i updated deCONZ addon first to 3.4 and then to 3.5 On both new versions i get this error when i try to start the addon.

[16:52:47] FATAL: No device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE1962254-if00 found! That device path shows under “hassio/system/hardware” and worked on addon version 3.3

I have tried to change the device to this diffrent ones (one by one) but they give same error. “/dev/ttyUSB0” “/dev/ttyUSB1” “/dev/ttyAMA0” “/dev/ttyAMA1” “/dev/ttyACM0” “/dev/ttyACM1”

Restoring from snapshot to 3.3 makes it work again

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 31 (9 by maintainers)

Most upvoted comments

And for the record I have done all suggestions so far and I just did the docker rm hassio_supervisor And I reran the install script.

And it still fails the same way.

It is not correct to close an issue after so short time when several people are reporting the same issue. I can understand if it is one socker that refuse to try anything. But we are multiple people with same issue and there is obvious an issue caused by the changes in deconz 3.5

I will also say that mattias1972 reported a completely different symptom and his resolution has nothing to do with the issue originally reported.

The least one can do is revert the changes back to what actually worked until we understand what goes wrong.

KennethLavrsen on Sep 4, 2019

@balloob I want to complain about how this issue is treated. We are several people with the same issue and there is no resolution.

I will reopen new issue with same content

KennethLavrsen on Sep 4, 2019

I think we have several populations here.

From #680 people that already had the issue before the 3.4/3.5 update
People that get an error that device is not ready yet
And then we are at least 3 or 4 that have the situation where the by-id link does not work in 3.5 but works in 3.3

They should probably be split on 3 bug reports

I am only addressing case 3 which is what seems to best fit the original report.

I surely run docker-ce. I had upgraded to the latest 0.98.2 before the upgrade of deconz and it worked. I know because when it fails all my automatic light stops working so I would have noticed

Mine broke down the minute I upgraded the deconz addon from 3.3 to 3.5 (did not see the 3.4 update) and to get it back I had to use the straight /dev/ttyACM# link

When I look at the host Ubuntu I notice that udev create symbolic links from /dev/serial/by-id that point back to /dev When I use the ssh within HA the docker view of things are that /dev/serial/by-id/device_name are “files” and not links. I do not know if this means anything but it is an observation

I also have an Aeotec Z-wave stick using ZHA.

It is configured and WORKS like this

zwave:
  usb_path: /dev/serial/by-id/usb-0658_0200-if00
  network_key: !secret zwave_network_key

So for the zwave integration the by-id works fine.

In the Home Assistant hass.io -> Host System -> Hardware button I can the the two by-id devices

The error message from deconz is “FATAL: No device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE1962724-if00 found!”

This is the same error you get if you put some complete nonsense.

The conclusion I have so far that this seems to be an isolated problem to the deconz docker container. Inside this the by-id devices do not exist. We need to find out why. If we go back a few versions of deconz it did not work either. Then the feature was introduced so you could use by-id links. And now it is broken again. And it happens in a release where udev was dramatically chanced as far as I can see in the code without understanding what is it that happens. It seems some udev related stuff was change to using a python based library. But I do not know Python so I am a bit lost

KennethLavrsen on Sep 4, 2019