<![CDATA[external devices - zigbee]]>I was playing around with homeassistant to see of I could use this server app instead of my RPI. It seems I can't find a way to pass in devices like my USB ZigBee radio to the container. Is there a workaround or plan to make this possible?

]]>https://forum.cloudron.io/topic/12742/external-devices-zigbeeRSS for NodeFri, 17 Jul 2026 01:50:37 GMTTue, 05 Nov 2024 16:36:01 GMT60<![CDATA[Reply to external devices - zigbee on Fri, 20 Jun 2025 10:17:13 GMT]]>I am marking this topic as solved.
Now hardware devices can be added to the app by the user and it works.

]]>https://forum.cloudron.io/post/109069https://forum.cloudron.io/post/109069Fri, 20 Jun 2025 10:17:13 GMT<![CDATA[Reply to external devices - zigbee on Fri, 14 Mar 2025 14:40:10 GMT]]>Cloudron's cron has a special @service pattern to run once on startup

]]>https://forum.cloudron.io/post/103284https://forum.cloudron.io/post/103284Fri, 14 Mar 2025 14:40:10 GMT<![CDATA[Reply to external devices - zigbee on Fri, 14 Mar 2025 13:42:37 GMT]]>I use the zigbee dongle from sonoff (https://sonoff.tech/product/gateway-and-sensors/sonoff-zigbee-3-0-usb-dongle-plus-p/)

]]>https://forum.cloudron.io/post/103280https://forum.cloudron.io/post/103280Fri, 14 Mar 2025 13:42:37 GMT<![CDATA[Reply to external devices - zigbee on Fri, 14 Mar 2025 12:57:35 GMT]]>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?

]]>https://forum.cloudron.io/post/103278https://forum.cloudron.io/post/103278Fri, 14 Mar 2025 12:57:35 GMT<![CDATA[Reply to external devices - zigbee on Mon, 03 Mar 2025 16:35:34 GMT]]>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 ?

]]>https://forum.cloudron.io/post/102564https://forum.cloudron.io/post/102564Mon, 03 Mar 2025 16:35:34 GMT<![CDATA[Reply to external devices - zigbee on Wed, 26 Feb 2025 09:57:03 GMT]]>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.

]]>https://forum.cloudron.io/post/102336https://forum.cloudron.io/post/102336Wed, 26 Feb 2025 09:57:03 GMT<![CDATA[Reply to external devices - zigbee on Tue, 25 Feb 2025 14:01:26 GMT]]>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

]]>https://forum.cloudron.io/post/102295https://forum.cloudron.io/post/102295Tue, 25 Feb 2025 14:01:26 GMT<![CDATA[Reply to external devices - zigbee on Fri, 21 Feb 2025 14:22:48 GMT]]>actually the group permissions are rw only others have no access. So this looks correct to me.

]]>https://forum.cloudron.io/post/102107https://forum.cloudron.io/post/102107Fri, 21 Feb 2025 14:22:48 GMT<![CDATA[Reply to external devices - zigbee on Fri, 21 Feb 2025 10:54:33 GMT]]>Yep, as you can see, /dev/ttyACM0 has no right for group :

image.png

]]>https://forum.cloudron.io/post/102095https://forum.cloudron.io/post/102095Fri, 21 Feb 2025 10:54:33 GMT<![CDATA[Reply to external devices - zigbee on Sun, 16 Feb 2025 12:24:25 GMT]]>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?

]]>https://forum.cloudron.io/post/101813https://forum.cloudron.io/post/101813Sun, 16 Feb 2025 12:24:25 GMT<![CDATA[Reply to external devices - zigbee on Fri, 14 Feb 2025 14:59:23 GMT]]>Just updated to 1.1.0. Still not working, had to chmod

]]>https://forum.cloudron.io/post/101748https://forum.cloudron.io/post/101748Fri, 14 Feb 2025 14:59:23 GMT<![CDATA[Reply to external devices - zigbee on Thu, 13 Feb 2025 11:53:53 GMT]]>oh indeed, the change didn't make it. Will include it with next release then

]]>https://forum.cloudron.io/post/101699https://forum.cloudron.io/post/101699Thu, 13 Feb 2025 11:53:53 GMT<![CDATA[Reply to external devices - zigbee on Thu, 13 Feb 2025 09:33:12 GMT]]>not fixed with the latest stable release, juste to mention

]]>https://forum.cloudron.io/post/101685https://forum.cloudron.io/post/101685Thu, 13 Feb 2025 09:33:12 GMT<![CDATA[Reply to external devices - zigbee on Thu, 09 Jan 2025 10:08:32 GMT]]>ah good next package release will add the cloudron user to the dialout group, that should fix it also in the long run then.

]]>https://forum.cloudron.io/post/99604https://forum.cloudron.io/post/99604Thu, 09 Jan 2025 10:08:32 GMT<![CDATA[Reply to external devices - zigbee on Thu, 09 Jan 2025 10:04:13 GMT]]>Probably don't need the 'x' bit on devices. So 666 maybe.

]]>https://forum.cloudron.io/post/99603https://forum.cloudron.io/post/99603Thu, 09 Jan 2025 10:04:13 GMT<![CDATA[Reply to external devices - zigbee on Thu, 09 Jan 2025 09:52:17 GMT]]>chmod 777 resolved the problem but not sure it's a good idea lol

]]>https://forum.cloudron.io/post/99598https://forum.cloudron.io/post/99598Thu, 09 Jan 2025 09:52:17 GMT<![CDATA[Reply to external devices - zigbee on Thu, 09 Jan 2025 09:47:20 GMT]]>image.png

]]>https://forum.cloudron.io/post/99597https://forum.cloudron.io/post/99597Thu, 09 Jan 2025 09:47:20 GMT<![CDATA[Reply to external devices - zigbee on Wed, 08 Jan 2025 17:07:23 GMT]]>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>
]]>https://forum.cloudron.io/post/99553https://forum.cloudron.io/post/99553Wed, 08 Jan 2025 17:07:23 GMT<![CDATA[Reply to external devices - zigbee on Wed, 08 Jan 2025 16:51:29 GMT]]>Hi ! Zigbee not working even after usb device added in "device" section.

]]>https://forum.cloudron.io/post/99550https://forum.cloudron.io/post/99550Wed, 08 Jan 2025 16:51:29 GMT<![CDATA[Reply to external devices - zigbee on Wed, 18 Dec 2024 15:53:33 GMT]]>@rjousse18 8.2 is in unstable. if you update to the unstable, you can test it out - https://docs.cloudron.io/apps/#devices

]]>https://forum.cloudron.io/post/98410https://forum.cloudron.io/post/98410Wed, 18 Dec 2024 15:53:33 GMT<![CDATA[Reply to external devices - zigbee on Wed, 18 Dec 2024 15:06:43 GMT]]>nice ! when will we be able to test this feature on home assistant ?

]]>https://forum.cloudron.io/post/98405https://forum.cloudron.io/post/98405Wed, 18 Dec 2024 15:06:43 GMT<![CDATA[Reply to external devices - zigbee on Thu, 05 Dec 2024 13:51:10 GMT]]>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.

]]>https://forum.cloudron.io/post/97807https://forum.cloudron.io/post/97807Thu, 05 Dec 2024 13:51:10 GMT<![CDATA[Reply to external devices - zigbee on Tue, 03 Dec 2024 16:10:15 GMT]]>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 ?

]]>https://forum.cloudron.io/post/97670https://forum.cloudron.io/post/97670Tue, 03 Dec 2024 16:10:15 GMT<![CDATA[Reply to external devices - zigbee on Fri, 08 Nov 2024 13:43:04 GMT]]>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

]]>https://forum.cloudron.io/post/96565https://forum.cloudron.io/post/96565Fri, 08 Nov 2024 13:43:04 GMT