Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Home Assistant
  3. external devices - zigbee

external devices - zigbee

Scheduled Pinned Locked Moved Unsolved Home Assistant
28 Posts 4 Posters 2.2k Views 5 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • nebulonN Offline
    nebulonN Offline
    nebulon
    Staff
    wrote on last edited by
    #18

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

    1 Reply Last reply
    0
    • R Offline
      R Offline
      rjousse18
      wrote on last edited by
      #19

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

      1 Reply Last reply
      0
      • nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #20

        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?

        1 Reply Last reply
        0
        • R Offline
          R Offline
          rjousse18
          wrote on last edited by
          #21

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

          image.png

          1 Reply Last reply
          0
          • nebulonN Offline
            nebulonN Offline
            nebulon
            Staff
            wrote on last edited by
            #22

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

            1 Reply Last reply
            0
            • R Offline
              R Offline
              rjousse18
              wrote on last edited by
              #23

              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

              1 Reply Last reply
              0
              • nebulonN Offline
                nebulonN Offline
                nebulon
                Staff
                wrote on last edited by
                #24

                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.

                1 Reply Last reply
                0
                • R Offline
                  R Offline
                  rjousse18
                  wrote on last edited by
                  #25

                  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 ?

                  1 Reply Last reply
                  0
                  • nebulonN Offline
                    nebulonN Offline
                    nebulon
                    Staff
                    wrote on last edited by
                    #26

                    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?

                    1 Reply Last reply
                    0
                    • R Offline
                      R Offline
                      rjousse18
                      wrote on last edited by
                      #27

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

                      1 Reply Last reply
                      0
                      • J Offline
                        J Offline
                        joseph
                        Staff
                        wrote on last edited by
                        #28

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

                        1 Reply Last reply
                        0
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        • Login

                        • Don't have an account? Register

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Bookmarks
                        • Search