external devices - zigbee

[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.

[rjousse18]

but it didn't works I had to chmod again, is there any solution to launch a script at startup ? I don't want to chmod every time the app is updated

[nebulon]

So to be on the same page, if you give read/write permissions to all users HomeAssistant can use the device fine, but not if only root and dialout group have it? Reason I ask is, since HomeAssistant as such runs with the dialout group. Which kind of integration is this? Maybe it spawns other processes which run as different user?

Since I can't reproduce this locally, maybe you can send a mail to support@cloudron.io if you want us to take a direct look at your case to get this fixed.

[rjousse18]

Yep it does work only if i perform a chmod 666. If you can't give read/write permissions to all users by default, is it possible to launch a script at launch automatically ?

[nebulon]

To reactivate that thread, as a fallback for now you can add a custom cron job to chmod this device https://docs.cloudron.io/apps/#cron however ideally we can figure out why HomeAssistant can't access it otherwise. At least the USB device I have works fine that way. Maybe the integration for the device you are using behaves differently? Which device and integration is this?

[rjousse18]

I use the zigbee dongle from sonoff (https://sonoff.tech/product/gateway-and-sensors/sonoff-zigbee-3-0-usb-dongle-plus-p/)

[joseph]

Cloudron's cron has a special @service pattern to run once on startup