| 23 Aug 2021 |
 Church | I see this when adding a zigbee coordinator usb to the integration. | 17:51:53 |
| Church | Seems to fail to connect for some reason.
Had this happen with a HUBUSB zigbee/zwave dual stick as well. | 17:52:48 |
 @hexa:lossy.network | do you have a journal log? | 19:04:51 |
| @hexa:lossy.network | latest version is 2021.8.8 btw | 19:05:01 |
| @hexa:lossy.network | * Church: do you have a journal log? | 19:05:08 |
| Church | Nothing in journald | 19:28:01 |
| Church | I'll have to try updating agai | 19:28:12 |
| Church | * I'll have to try updating again | 19:28:14 |
| @hexa:lossy.network | it's probably due to hardening settings | 19:46:01 |
| @hexa:lossy.network | what is the path to the serial device? | 19:47:09 |
| @hexa:lossy.network | we allow ttyACM, ttyAMA and ttyUSB character devices | 19:47:20 |
| @hexa:lossy.network | what is the component you are using? | 19:48:30 |
| 24 Aug 2021 |
| Church | Path to the serial device by device path is: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2448684-if00
By regular dev path it's /dev/ttyACM0 | 02:52:35 |
| Church | Component is a conbee2 | 02:52:42 |
 etu | Oh, I have exact same device, but I tend to pin my home assistant to a nixpkgs revision and only update it now and then | 08:34:42 |
| etu | My zigbee is working at the moment, but haven't updated hass in a while, haven't had the time. | 08:35:02 |
| @hexa:lossy.network | right, so we set DeviceAllow to char-tty{ACM,AMA,USB} rw | 10:02:31 |
| @hexa:lossy.network | if /dev/ttyACM0 works and /dev/serial/by-id/ we should probably open a systemd issue? | 10:03:17 |
| @hexa:lossy.network | * if /dev/ttyACM0 works and the same device linked into /dev/serial/by-id/ does not, we should probably open a systemd issue? | 10:03:39 |
| @hexa:lossy.network | what you can always do is systemd.services.home-assistant.serviceConfig.DeviceAllow = [ "/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2448684-if00" ]; | 10:04:35 |
| @hexa:lossy.network | Church: conbee2 does not seem to be a home-assistant component | 10:05:22 |
| @hexa:lossy.network | you probably meant deconz? | 10:05:46 |
| @hexa:lossy.network | etu: and you? | 10:05:50 |
| etu | I use the zha thingy I think | 10:07:08 |
| etu | They deprecated specifying the device in config some time ago: https://github.com/etu/nixconfig/blob/main/hosts/fenchurch/services/hass.nix#L297-L303 | 10:07:44 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/misc/home-assistant.nix#L276-L317 | 10:07:58 |
| @hexa:lossy.network | if Church uses deconz we likely didn't give them permissions for serial access | 10:08:37 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/135540 | 10:11:27 |
| Church | Ugh right, it's deconz.
I'll give the unit override a try in a bit. | 10:28:42 |
| Church | hexa: So made the DeviceAllow tweak:
systemd = {
services = {
home-assistant = {
serviceConfig = {
DeviceAllow = [ "/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2448684-if00" ];
};
};
};
};
Still seeing a connection error.
| 10:39:28 |
