external devices - zigbee

[eyecreate]

I've been using this device:
https://slae.sh/projects/cc2652/
As well as a development device with a Texas Instruments CC2531 chip for testing.

[nebulon]

Thanks for the link. From https://slae.sh/projects/cc2652/#homeassistant-hassio this seems to be quite specific with various caveats for the /dev nodes to use. Looks like unfortunately we have to implement something which allows a very technical and lowlevel approach then....

[rjousse18]

How could it be implemented ? Via the app settings in cloudron with a section where we could choose what usb device(s) the app can access ?

[nebulon]

Yes I think that would be the idea, maybe a free flow text input which binds the mentioned device(s) into the container. Similar to what we do for vaapi device access https://git.cloudron.io/platform/box/-/blob/master/src/docker.js?ref_type=heads#L409

[rjousse18]

If it's, for now, specific to Home Assistant app, why not just use workarounds like https://community.home-assistant.io/t/home-assistant-in-docker-pass-usb-device-from-host/184674/2 or https://community.home-assistant.io/t/home-assistant-in-docker-pass-usb-device-from-host/184674/6 ?

[nebulon]

Alright, we have added initial basic support for attaching devices from the host to the container. For the moment this will just be a list of devices with a 1to1 mapping. So for example /dev/ttyUSB0 from the host can then be mapped to /dev/ttyUSB0 within the container.

[rjousse18]

nice ! when will we be able to test this feature on home assistant ?

[joseph]

@rjousse18 8.2 is in unstable. if you update to the unstable, you can test it out - https://docs.cloudron.io/apps/#devices

[rjousse18]

Hi ! Zigbee not working even after usb device added in "device" section.

[nebulon]

Most likely it is a permissions issue, can you open a webterminal into the app and check the group ownership of the node?

ls -l /dev/<yourdevice>

[rjousse18]

[rjousse18]

chmod 777 resolved the problem but not sure it's a good idea lol

[joseph]

Probably don't need the 'x' bit on devices. So 666 maybe.

[nebulon]

ah good next package release will add the cloudron user to the dialout group, that should fix it also in the long run then.

[rjousse18]

not fixed with the latest stable release, juste to mention

[nebulon]

oh indeed, the change didn't make it. Will include it with next release then

[rjousse18]

Just updated to 1.1.0. Still not working, had to chmod

[nebulon]

Just did another test install and at least my ttyUSB0 device would show up correctly with:

> ls -l /dev/tty*
crw-rw-rw- 1 root root      5, 0 Feb 16 12:18 /dev/tty
crw-rw-rw- 1 root dialout 188, 0 Feb 16 12:18 /dev/ttyUSB0

So in your case you still had to add read-write access to the group for your device?

[rjousse18]

Yep, as you can see, /dev/ttyACM0 has no right for group :

[nebulon]

actually the group permissions are rw only others have no access. So this looks correct to me.