Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permanent hub name #80

Open
JFC-Dev opened this issue Jan 1, 2020 · 1 comment
Open

Permanent hub name #80

JFC-Dev opened this issue Jan 1, 2020 · 1 comment

Comments

@JFC-Dev
Copy link

JFC-Dev commented Jan 1, 2020

I am using Hass.io in a Docker container. I got my Wyze hub detected using the "device: auto" setting in the confiuration.yaml. I am still new to HA and learning but I figured it might be even better if I set a permanent name for the Wyze hub instead of using auto.

So I modified /etc/udev/rules.d/usbcustom.rules and added
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="e024", SYMLINK+="wyze_hub"

I applied the new configuration
sudo udevadm trigger

And I verified that the name was set to wyze_hub
ls -l /dev/wyze_hub gave me /dev/wyze_hub -> hidraw0

Then I changed configuration.yaml for
device: "/dev/wyze_hub"

Then I rebooted my server (I wanted to make sure the name would still work after a reboot).

ls -l /dev/wyze_hub gave me /dev/wyze_hub -> hidraw0 so it seemed to work. However HA would not see my Wyze sensors anymore and I had no wyzesense*. in Services.

I changed the configuration.yaml to auto and restarted HA (I didn't reboot the server) and everything was working again.

I am wondering what I did wrong. It is definately not a problem since it is working fine with auto but I thought it would have been better to use /dev/wyze_hub.

@kevinvincent
Copy link
Owner

kevinvincent commented Jan 16, 2020

Can you try the steps on here: #66

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants