-
-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
Emulated Hue Permission Issue #4737
Comments
It's actually a Linux safeguard. Binding to < 1024 requires being root. The solution is probably going to be making home-assistant understand how to drop privs back to a normal user after binding to the port. |
One could also grant the capability to bind to privileged ports for the python binary in the virtualenv like sudo setcap 'cap_net_bind_service=+ep' /srv/hass/bin/python3 |
@algorythmic, good call. The only issue is that to my knowledge sudo access is turned off inside the venv that the AiO script makes. |
same here. |
@ronvl I think that is because it is being advertised on port 8300 if the config is set to 8300. What we would need support for is having the emulated_hue component think it is on port 80, but actually be bound to port 8300 |
as I'm not running virtuelenv I used: and it works .... cool 👍 |
For people who are following this thread, after a little research the setcap command does work for the AiO method. The magic sauce for people running HA in a venv via the AiO script is
After running that, I was able to spin up the component no problem which both Google Home and the Amazon Echo can see. Sick! @balloob, is this something that can be added to the component or would it be easiest to update the Emulated Hue component page? Cheers! |
I think this would fit best at the emulated_hue page |
Sweet! I'll try and get a pull pulled together on that page soon. Cheers! |
Hi, |
What would be the equivalent command to get Google Home working on a Mac HA install? |
Thanks Antexa - I needed that! |
not working for me i cannot get google home to work the port 80 not working for me after using all commands |
@mohaggag Google Home updated to require a Hue account to be registered to add Phillips hue devices. It is no longer possible to add new emulated hue setups to Google Home, but existing ones will still work. We would have to register the Home Assistant as if it were a full fledged Phillips Hue hub tying into their cloud and everything in order to fix this problem. |
This morning i setup HA and my google home it worked fine with my vera + emulated bridge. Had to run as root get get it to run over port 80 however. |
@kerbysj how did you make it .. i got port 80 to work but emulated hue now using hue account as @demonspork mention so it cann't be done .. |
Well i just setup the emulated hub on port 80 and then paired in google home and it all just worked...
|
@kerbysj not sure how you did this as nobody else can. You can't bind to port 80 without being root or the above commands, and i just received a google home and you have to sign into Hue to add the device I bought a google home specifically for HA, so really disappointed right now! |
Hello! I'm having an issue with the emulated hue component. Not sure if this is localized issue or something more widespread. In my quick googling, looks like Python doesn't like binding ports lower than 1024 or so without giving it more permissions as a privileged user.
I'm running HA in a venv via the All-In-One script.
Thanks much for any feedback and/or help!
Home Assistant release (
hass --version
): 0.34.1Python release (
python3 --version
): 3.4.2Component/platform:
Emulated Hue
Description of problem:
Emulated Hue won't start. Throwing an error in the log.
Expected:
Emulated Hue runs
Problem-relevant
configuration.yaml
entries and steps to reproduce:The text was updated successfully, but these errors were encountered: