Passing /dev/hidraw* through to HA in docker #66

ff4500 · 2019-11-26T16:14:18Z

Previously, I had the component setup in my compose file to pass through with:

devices:
      - /dev/hidraw1:/dev/hidraw1

That worked out pretty well, until a reboot of the host system which changed the hidraw device. HA didn't open, had to remove from the config, yadda yadda.

So, I thought that the new version with device: auto would be the ticket. I'm sure that that it works great, but how would I go about passing a randomly assigned device to pass through in my compose file? I don't really want to mount the whole /dev dir and run in privileged mode if I can help it.

The text was updated successfully, but these errors were encountered:

kevinvincent · 2019-11-28T22:47:44Z

I don't have much experience with docker but if you mount the whole /dev dir you don't need to run in privileged mode right? It should still be able to read / write to the device?

tomhoover · 2019-12-29T03:31:36Z

@ff4500, here's how I did it:

Create /etc/udev/rules.d/99-wyze.rules:

SUBSYSTEM=="hidraw", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="e024", SYMLINK+="wyzesense"

Restart the host and verify the symlink /dev/wyzesense was created.
Edit docker-compose.yml to include:

    devices:
      - /dev/wyzesense

Edit configuration.yml to include:

binary_sensor:
  - platform: wyzesense
    device: /dev/wyzesense

Don't forget to stop your home-assistant docker container (e.g. docker stop xxx or docker-compose down xxx), and restart it via docker-compose up -d. If you only restart hass itself (without recreating the docker container), docker won't pass-thru '/dev/wyzesense'. (Ask me how I know that to be the case 🤦‍♂)

jes1417 · 2020-01-15T01:29:17Z

This worked perfectly for me in my container.

bepstein111 · 2020-03-28T23:02:23Z

@tomhoover

@ff4500, here's how I did it:
...
2. Edit docker-compose.yml to include:

Forgive me for my lack of knowledge, but when you refer to docker-compose.yml, do you mean one that we have set up previously, or is there one somewhere on the hassio-supervisor image that can be edited for launching the homeassistant container? Obviously I'm running hassio, not sure if this was meant specifically for HA Core?

TheColtron · 2020-04-09T01:09:15Z

@bepstein111 Did you ever figure this out by chance? I'm migrating to Hassio in docker and this is the one sticking point that I can't seem to get around.

bepstein111 · 2020-04-09T01:38:56Z

@bepstein111 Did you ever figure this out by chance? I'm migrating to Hassio in docker and this is the one sticking point that I can't seem to get around.

unfortunately not. I ended up just buying a Nabu Casa subscription and adding the devices via Wyze App > Amazon Alexa Wyze Skill > HA Alexa Integration. Bit of a workaround, but most things in hassio seem to be, and it added some other features I was looking for like automagic SSL/HTTPS.

I did notice that I hadn't actually tagged the original commenter, so I just did that and maybe we'll get a reply.

TheColtron · 2020-04-09T02:19:54Z

@bepstein111 Thanks for the quick reply.

They have an Alexa skill now?! That's good enough for me, and I don't think I would've thought to look at that option. Thank you!

kevinvincent · 2020-04-09T03:21:13Z

Just curious, how quick is the alexa trigger method? Honestly even though I developed this I'd prefer a more first-party supported integration given the weird quirks the custom component has.

…

On Wed, Apr 8, 2020 at 7:20 PM Colten Lumley ***@***.***> wrote: @bepstein111 <https://github.com/bepstein111> Thanks for the quick reply. They have an Alexa skill now?! That's good enough for me, and I don't think I would've thought to look at that option. Thank you! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#66 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKJUZPEIKAYZD6RZSL5Q2LRLUWFPANCNFSM4JR2M7YA> .

ff4500 · 2020-04-09T13:52:53Z

Of note, I haven't tried the suggested steps above yet, since I moved my HA environment over to a NUC from my Hypervisor (Proxmox, Alpine VM running on a Dell server with USB passthrough setup). The NUC doesn't seem to reassign the hidraw device on reboot, and it's been rock solid.

If I move it back to the Hypervisor, I will definitely try the link steps again. And @kevinvincent, I have tried the Alexa HA integration before and it wasn't quick like local polling. As much as we lose power/internet in the spring, I appreciate being able to still use sensors to turn my lights on and off when I can't connect to the internet.

bepstein111 · 2020-04-09T16:54:40Z

@kevinvincent If you do it within the Alexa app, it's immediate - I have motion sensors on mine and they're quite responsive. I hate not having EVERYTHING running through HA, but honestly, it works well, and I'm not opposed to opening up a second app when I need to. That said, I TOTALLY understand @ff4500 sentiment about losing power/internet. Not sure if Alexa remembers triggers during outages (internet, that is), so it may or may not work without internet.

sdunnagan · 2020-04-11T12:56:35Z

@tomhoover Thanks for your solution with the symbolic link to the hidraw device. I see the link getting created,sometimes to hidraw0, sometimes hidraw1, etc. The only problem is that I don't know how to update the Docker containers used by Home Assistant Supervised.

tomhoover · 2020-04-11T15:25:47Z

@bepstein111, @TheColtron, @sdunnagan, I do not use Home Assistant Supervised, so the following suggestion is based upon a quick review of the Home Assistant Supervised installer. Beware this is untested, and should only be used if you're comfortable with the command line.

Find the script hassio-supervisor (installed in /usr/sbin by default).
Create a backup of the file in case this doesn't work for you.
Edit hassio-supervisor and search for the line -v /run/dbus:/run/dbus \
Immediately following that line, add the following line:

-v /dev/wyzesense:/dev/wyzesense \

From a command line, execute systemctl restart hassio-supervisor.service. (If that doesn't restart the service, you may need to restart your system for it to read the new file.)

If anything breaks, please restore the backup file you made earlier, and reboot your system. As mentioned above, this has not been tested by me, so BE CAREFUL!

sdunnagan · 2020-04-11T19:24:43Z

Very helpful, thanks!

My HA config looks like:

/usr/share/hassio/homeassistant/configuration.yaml
--------------------------------------------------
...
binary_sensor:
  - platform: wyzesense
    device: /dev/wyzesense
    initial_state:
      77793176: "on"
      77793193: "off"

Docker is getting run as you suggested with the volume mount of the device file:

    docker run --name hassio_supervisor \
        --privileged \
        $APPARMOR \
        --security-opt seccomp=unconfined \
        -v /run/docker.sock:/run/docker.sock \
        -v /run/dbus:/run/dbus \
        -v /dev/wyzesense:/dev/wyzesense \
        -v "${HASSIO_DATA}":/data \
        -e SUPERVISOR_SHARE="${HASSIO_DATA}" \
        -e SUPERVISOR_NAME=hassio_supervisor \
        -e HOMEASSISTANT_REPOSITORY="${HOMEASSISTANT}" \
        "${SUPERVISOR}"

But device isn't detected, and I see this in the log:

FileNotFoundError: [Errno 2] No such file or directory: '/dev/wyzesense'

However, udev did in fact create the symbolic link:

$ ls -al /dev/wyzesense
lrwxrwxrwx 1 root root 7 Apr 11 14:41 /dev/wyzesense -> hidraw0

Anyway, I can live with configuring HA with "device: auto". But it's an interesting problem.

bepstein111 · 2020-04-11T21:12:11Z

@sdunnagan with hassio supervised, the problem is that /dev/wyzesense exists on the local machine, but not inside the container that HA runs inside of. @tomhoover 's latest reply should fix that, hopefully.

haxx0r07 · 2020-04-14T13:47:30Z

The issue with @tomhoover 's changes is that that only passes the device into the container for the supervisor. This does not actually pass the device into the container where Home Assistant actually runs. I've been looking through all of the supervisor configuration/script but I can't find where or what it uses to create the container running home assistant.

bepstein111 · 2020-04-14T16:20:04Z

The issue with @tomhoover 's changes is that that only passes the device into the container for the supervisor. This does not actually pass the device into the container where Home Assistant actually runs. I've been looking through all of the supervisor configuration/script but I can't find where or what it uses to create the container running home assistant.

This was the brick wall I faced as well. Bummer that the latest attempt by tom wasn't successful. Definitely interested in any solutions, but for now, 5 bucks a month was worth it to me.

TheColtron · 2020-04-17T18:51:00Z

Just curious, how quick is the alexa trigger method? Honestly even though I developed this I'd prefer a more first-party supported integration given the weird quirks the custom component has.

I finally got some time to test the Alexa integration and ended up reverting back to this component pretty quickly. The Alexa route is very responsive, but the major downside is that node-red control is much more difficult. Some of my motion rules are pretty elaborate and can't really be translated into Alexa routines, so this component is much more valuable imo.

RonSpawnson · 2020-04-27T03:11:35Z

Following this issue, as if we can determine how to make this work for HA supervised, it will unlock my ability to create auto-restart for the sensors not responding issue: #114.

I'm noticing occasionally my sensors stop responding, and the hidraw device has changed. When I try re-initializing the entire component, it says the new /dev/hidrawN file is not found, even though I can see it in /sys/class/hidraw. Suspect I'm running into the issue you all are, and keen to see if someone figures out how to fix it.

RonSpawnson · 2020-04-27T04:02:16Z

@haxx0r07 I think this is where supervisor runs the homeassistant container, and this is where they configure which volumes are to be used/bound.

Perhaps we can add a volume binding here? The only issue is I'm not exactly sure how to locally make a change to this and run it locally. The README for homeassistant supervisor seems to make it sound like you need to use hassio-builder with custom tagged image, it's not clear to me at all how I'd modify this and test it locally.

RonSpawnson · 2020-04-28T00:40:14Z

Talking with Supervisor devs, sounds like Supervisor has a hardware abstraction layer to support udev devices. Looks like "hidraw" devices are not yet looked for in this abstraction layer, so we should look into adding them: https://github.com/home-assistant/supervisor/blob/dev/supervisor/misc/hardware.py

haxx0r07 · 2020-04-29T11:43:31Z

Nice work @RonSpawnson I'm not the best with python, but I'll look through that file and see if I can come up with anything.

RonSpawnson · 2020-04-29T14:18:04Z

I've got a diff I can share this evening, I just cannot figure out how to use hassio-build to create a test image to try it out as per README, so I have no way of testing. I opened an issue asking for clarification and did receive a tip, so that's next on my plan of action when I get more free time home-assistant/supervisor#1685 (comment)

carltonwb · 2020-05-20T23:16:47Z

I am running hassio in a VM on unraid installed witha a quecow2 file.
I can plug in the device and run lsusb and it does find it.
I have enabled it in the unraid VM. I do not have access to a docker container to change the udev rules. Did try to do it on the unraid server but every time the file would disappear.
I have run dmesg | grep hidraw and this is the result

[ 10.421011] hidraw: raw HID events driver (C) Jiri Kosina [ 12.632714] hid-generic 0003:051D:0002.0001: hiddev96,hidraw0: USB HID v1.00 Device [American Power Conversion Back-UPS NS 1500M2 FW:957.e3 .D USB FW:e3 ] on usb-0000:00:14.0-10/input0 [ 13.202984] hid-generic 0003:1A86:E024.0002: hiddev97,hidraw1: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-13/input0 [ 781.737274] hid-generic 0003:051D:0002.0003: hiddev96,hidraw0: USB HID v1.00 Device [American Power Conversion Back-UPS NS 1500M2 FW:957.e3 .D USB FW:e3 ] on usb-0000:00:14.0-10/input0 [23912.624848] hid-generic 0003:1A86:E024.0004: hiddev96,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-13/input0 [23914.086048] hid-generic 0003:051D:0002.0005: hiddev97,hidraw1: USB HID v1.00 Device [American Power Conversion Back-UPS NS 1500M2 FW:957.e3 .D USB FW:e3 ] on usb-0000:00:14.0-10/input0 [23926.641196] hid-generic 0003:051D:0002.0006: hiddev96,hidraw0: USB HID v1.00 Device [American Power Conversion Back-UPS NS 1500M2 FW:957.e3 .D USB FW:e3 ] on usb-0000:00:14.0-10/input0 [25611.752758] hid-generic 0003:051D:0002.0007: hiddev96,hidraw0: USB HID v1.00 Device [American Power Conversion Back-UPS NS 1500M2 FW:957.e3 .D USB FW:e3 ] on usb-0000:00:14.0-10/input0 [25619.450795] hid-generic 0003:051D:0002.0008: hiddev96,hidraw0: USB HID v1.00 Device [American Power Conversion Back-UPS NS 1500M2 FW:957.e3 .D USB FW:e3 ] on usb-0000:00:14.0-10/input0 [27991.703708] hid-generic 0003:1A86:E024.0009: hiddev96,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-13/input0 [27993.165598] hid-generic 0003:051D:0002.000A: hiddev97,hidraw1: USB HID v1.00 Device [American Power Conversion Back-UPS NS 1500M2 FW:957.e3 .D USB FW:e3 ] on usb-0000:00:14.0-10/input0 [28028.016852] hid-generic 0003:051D:0002.000B: hiddev96,hidraw0: USB HID v1.00 Device [American Power Conversion Back-UPS NS 1500M2 FW:957.e3 .D USB FW:e3 ] on usb-0000:00:14.0-10/input0 [29130.877253] hid-generic 0003:1A86:E024.000C: hiddev96,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-4/input0 [30401.157644] hid-generic 0003:051D:0002.000D: hiddev97,hidraw1: USB HID v1.00 Device [American Power Conversion Back-UPS NS 1500M2 FW:957.e3 .D USB FW:e3 ] on usb-0000:00:14.0-10/input0 [31160.267145] hid-generic 0003:1A86:E024.000E: hiddev96,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-4/input0

I have added the appropriate binary sensor in my yaml file.
I do not see the hidraw listed in my system hardware.
Any help is truly appreciated.

xenocidex · 2020-10-01T16:54:10Z

I am also I am running hassio in a VM on unraid installed witha a quecow2 file @carltonwb did you ever find a resolution?

chabad360 · 2020-11-11T20:23:22Z

I've got a diff I can share this evening, I just cannot figure out how to use hassio-build to create a test image to try it out as per README, so I have no way of testing. I opened an issue asking for clarification and did receive a tip, so that's next on my plan of action when I get more free time home-assistant/supervisor#1685 (comment)

Did you ever get it working?

RonSpawnson · 2020-11-13T04:59:03Z

Sadly no, I think I got them showing up in HA but they weren't mounting in the container still. I've resolved most of my stability issues with USB 3, and with pulling my SSD and WyzeSense to externally powered USB hub. But I do think getting supervisor support of hidraw would be best, it seems supervisor is on some strange depreciation path.

…

On Wed, Nov 11, 2020, 2:23 PM Mendel Greenberg ***@***.***> wrote: I've got a diff I can share this evening, I just cannot figure out how to use hassio-build to create a test image to try it out as per README, so I have no way of testing. I opened an issue asking for clarification and did receive a tip, so that's next on my plan of action when I get more free time home-assistant/supervisor#1685 (comment) <home-assistant/supervisor#1685 (comment)> Did you ever get it working? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#66 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACC5JUSR2R2H3X243NFLWY3SPLXERANCNFSM4JR2M7YA> .

fortwally · 2020-12-06T16:00:06Z

tomhoover commented on Dec 28, 2019.
This method worked for me. Just running HA in docker

kevinvincent mentioned this issue Jan 14, 2020

No hidraw showing up #87

Closed

This was referenced Jan 16, 2020

Permanent hub name #80

Open

Set up failure - Will not recognize Wyze hub #91

Closed

uncled1023 mentioned this issue Feb 9, 2020

AssertionError during _DoCommand (Send) #102

Open

RonSpawnson mentioned this issue Apr 27, 2020

Sensors Stop Responding - Requires Reboot #114

Open

jhenkens mentioned this issue Apr 29, 2020

Check for /dev/wyzesense raetha/wyzesense2mqtt#16

Closed

RoldyBuffalo mentioned this issue Jul 3, 2020

Latest Hassio - Wyzesense not working #155

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Passing /dev/hidraw* through to HA in docker #66

Passing /dev/hidraw* through to HA in docker #66

ff4500 commented Nov 26, 2019

kevinvincent commented Nov 28, 2019 •

edited

Loading

tomhoover commented Dec 29, 2019

jes1417 commented Jan 15, 2020

bepstein111 commented Mar 28, 2020 •

edited

Loading

TheColtron commented Apr 9, 2020

bepstein111 commented Apr 9, 2020 •

edited

Loading

TheColtron commented Apr 9, 2020

kevinvincent commented Apr 9, 2020 via email

ff4500 commented Apr 9, 2020

bepstein111 commented Apr 9, 2020 •

edited

Loading

sdunnagan commented Apr 11, 2020

tomhoover commented Apr 11, 2020 •

edited

Loading

sdunnagan commented Apr 11, 2020 •

edited

Loading

bepstein111 commented Apr 11, 2020

haxx0r07 commented Apr 14, 2020

bepstein111 commented Apr 14, 2020 •

edited

Loading

TheColtron commented Apr 17, 2020

RonSpawnson commented Apr 27, 2020 •

edited

Loading

RonSpawnson commented Apr 27, 2020 •

edited

Loading

RonSpawnson commented Apr 28, 2020

haxx0r07 commented Apr 29, 2020

RonSpawnson commented Apr 29, 2020 •

edited

Loading

carltonwb commented May 20, 2020

xenocidex commented Oct 1, 2020

chabad360 commented Nov 11, 2020

RonSpawnson commented Nov 13, 2020 via email

fortwally commented Dec 6, 2020

Passing /dev/hidraw* through to HA in docker #66

Passing /dev/hidraw* through to HA in docker #66

Comments

ff4500 commented Nov 26, 2019

kevinvincent commented Nov 28, 2019 • edited Loading

tomhoover commented Dec 29, 2019

jes1417 commented Jan 15, 2020

bepstein111 commented Mar 28, 2020 • edited Loading

TheColtron commented Apr 9, 2020

bepstein111 commented Apr 9, 2020 • edited Loading

TheColtron commented Apr 9, 2020

kevinvincent commented Apr 9, 2020 via email

ff4500 commented Apr 9, 2020

bepstein111 commented Apr 9, 2020 • edited Loading

sdunnagan commented Apr 11, 2020

tomhoover commented Apr 11, 2020 • edited Loading

sdunnagan commented Apr 11, 2020 • edited Loading

bepstein111 commented Apr 11, 2020

haxx0r07 commented Apr 14, 2020

bepstein111 commented Apr 14, 2020 • edited Loading

TheColtron commented Apr 17, 2020

RonSpawnson commented Apr 27, 2020 • edited Loading

RonSpawnson commented Apr 27, 2020 • edited Loading

RonSpawnson commented Apr 28, 2020

haxx0r07 commented Apr 29, 2020

RonSpawnson commented Apr 29, 2020 • edited Loading

carltonwb commented May 20, 2020

xenocidex commented Oct 1, 2020

chabad360 commented Nov 11, 2020

RonSpawnson commented Nov 13, 2020 via email

fortwally commented Dec 6, 2020

kevinvincent commented Nov 28, 2019 •

edited

Loading

bepstein111 commented Mar 28, 2020 •

edited

Loading

bepstein111 commented Apr 9, 2020 •

edited

Loading

bepstein111 commented Apr 9, 2020 •

edited

Loading

tomhoover commented Apr 11, 2020 •

edited

Loading

sdunnagan commented Apr 11, 2020 •

edited

Loading

bepstein111 commented Apr 14, 2020 •

edited

Loading

RonSpawnson commented Apr 27, 2020 •

edited

Loading

RonSpawnson commented Apr 27, 2020 •

edited

Loading

RonSpawnson commented Apr 29, 2020 •

edited

Loading