Working on multiple emulated_hue instances

I stopped it from booting

Not sure if you were able to resolve this.

If not, you should try running HA as root or sudo.

Port 80 requires privilege. This should show up as an error when the port is being bound during HA startup.

Never tried that. I have installed Hass in virtual environment as per instruction on AIO install

Is this error from emulated_hue at port 80?

17-02-26 09:33:16 ERROR (MainThread) [homeassistant.components.http] Failed to create HTTP server at port 80: [Errno 13] error while attempting to bind on address (‘192.168.1.239’, 80): permission denied

Here’s an issue thread talking about this problem.

They mention updating the documentation. So, then I went and looked and yes indeed there is a section of the HA emulated_hue documentation that refers to this solution:

1 Like

still nothing in GH app … The app had a major change in view, is yours still working?

EDIT It works, had to unlink the Hue hub, and relink. Is working.

Will try now more then 49 devices

Relinking is getting annoying! had to relink twice last week :frowning:.

It wouldn’t be so bad but adding all the devices to their corresponding rooms again is slightly annoying :stuck_out_tongue:

So far is stable.

@shenning00

Just to let you know that I am seeing this error in my log…

17-03-10 18:06:37 ERROR (Thread-4) [custom_components.emulated_hue] hue livingroom
17-03-10 18:06:37 ERROR (Thread-4) [custom_components.emulated_hue] hue masterbedroom
17-03-10 18:06:37 ERROR (Thread-4) [custom_components.emulated_hue] hue office

No big deal though. Everything still works fine. Wondering is it something can be fixed or I can safely ignore it.

Sorry - I used a debug log marked as “ERROR” so I could easily see it go by on my terminal. It shoes up as red text. This is just notifications. I’ll update the code on git later today.

1 Like

Hi,

I made a new installation of hassbian, and I am having problem with your component (my fault).

Can you help me out?

I have this error in log

17-04-21 21:55:48 ERROR (MainThread) [homeassistant.config] Invalid config for [emulated_hue]: [hue1] is an invalid option for [emulated_hue]. Check: emulated_hue->emulated_hue->hue1. (See /home/homeassistant/.homeassistant/configuration.yaml, line 78). Please check the docs at https://home-assistant.io/components/emulated_hue/
17-04-21 21:55:48 ERROR (MainThread) [homeassistant.setup] Setup failed for emulated_hue: Invalid config.

# Emulated Hue per Alexa`e Google Home
emulated_hue:
  hue1:
    type: alexa
    listen_port: 8301
    target_ip: 192.168.1.92
    exposed_domains:
      - switch
      - script
      - light
  hue2:
    type: alexa
    listen_port: 8302
    target_ip: 192.168.1.92
    exposed_domains:
      - scene
  hue3:
    type: alexa
    listen_port: 8303
    target_ip: 192.168.1.92
    exposed_domains:
      - group
  hue4:
    type: google_home
    listen_port: 80
    target_ip: 192.168.1.91
    exposed_domains:
      - switch
      - script
      - light
#
#

@shenning00

my fault I did not copy all the files in the custom_components.
Now Alexa works fine. I do have a problem with Google Home, it does not learn anything from emulated_hue.

Maybe I did something wrong, how to troubleshoot?

Too bad it stopped working

for google I should put 80?

Now in HASSBIAN the solution is not working??

pi@hassbian:~ $ sudo setcap 'cap_net_bind_service=+ep'  /srv/homeassistant/bin/python3
Failed to set capabilities on file `/srv/homeassistant/bin/python3' (Invalid argument)
The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file
pi@hassbian:~ $

In hassbian installation I did this, and it works!!!

sudo setcap ‘cap_net_bind_service=+ep’ /usr/bin/python3.4

1 Like

Cool - I’m glad it worked out.

This needs to be added to the component page - finally got everything working when I found this! Using the Hasspian 1.1 image.

I just need to copy these 4 files into my custom_components directory and then hue1, hue2 should work?

emulated_hue:
  hue1:
    type: alexa
    host_ip: 192.168.2.100
    listen_port: 8300
    expose_by_default: false
#  exposed_domains:
#    - light
  hue2:
    type: google_home
    host_ip: 192.168.2.100
    listen_port: 80

Yes, now I can’t check, but yes under custom_components
Also check my previous message if you have hassbian, some messages before if you have AIO