| 24 Aug 2021 |
 Church | Component is a conbee2 | 02:52:42 |
 @etu:semi.social | 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:semi.social | 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:semi.social | I use the zha thingy I think | 10:07:08 |
| @etu:semi.social | 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 |
| @hexa:lossy.network | home-assistant logs? | 10:40:56 |
| @hexa:lossy.network | try char-ttyACM rw instead of the serial device | 10:41:25 |
| Church | Nothing in logs | 10:43:06 |
| Church | Tried that, see this in the unit: DeviceAllow=char-ttyACM rw
Seeing failed to connect still. Nothing in logs. | 10:44:41 |
| Church | Hmm wonder if there's a debug log flag somewhere.... | 10:45:02 |
| Church | Hmm not seeing anything with debug logs turned on. | 10:49:31 |
| @hexa:lossy.network | can you try /dev/ttyACM0? | 10:50:59 |
| Church | Ah there we go... here's something | 10:51:28 |
| Church | Download hass.logs | 10:54:10 |
| Church | Getting a permission denied error | 10:54:23 |
| Church | * Getting a permission denied error trying to probe the /dev/ path | 10:55:32 |
| @hexa:lossy.network | right, can you test https://github.com/NixOS/nixpkgs/pull/135540? | 11:05:36 |
| @hexa:lossy.network | In reply to @hexa:lossy.network
can you try /dev/ttyACM0? or that :) | 11:06:23 |
