Google Home and Hue Emulator Problems

Configuration
21

Do you have hassbian or hassio?
hassio has a issue raised already: https://github.com/home-assistant/home-assistant/issues/8740
For me that error stooped when i fallowed the description that af950833 gave above although his second line in his description did not work for me.
But it recognize the hue in HA although it have nothing in it.
i am doing a fresh install and see what will happen.
Update
same error in the fresh install oh hassbian

22

I am running hassbian at the moment, i tried af950833 process but no change. I think his line 2 is wrong the inverted comma before cap and after ep should be an accent ’

23

Did you copied and pasted the sencond line from this post?
When I did it, it showed me a error.
But when I write it down manually, it works well.

pi@Tommy:~ $
pi@Tommy:~ $ sudo setcap ‘cap_net_bind_service=+ep’ /usr/bin/python3.4
sudo: unable to resolve host Tommy
fatal error: Invalid argument
usage: setcap [-q] [-v] (-r|-|) [ … (-r|-|) ]

Note must be a regular (non-symlink) file.
pi@Tommy:~ $
pi@Tommy:~ $
pi@Tommy:~ $
pi@Tommy:~ $ sudo setcap ‘cap_net_bind_service=+ep’ /usr/bin/python3.4
sudo: unable to resolve host Tommy
pi@Tommy:~ $
pi@Tommy:~ $

The first issue is from copy & paste and the sencond is done by manual.
Please try it manually and be careful for single quotation mark.

24

It works well for me.
I am running the Hassbian 0.50.2 at this time.
See the upper the result that I issued it a few mins ago.

25

Inserting manually worked no error at all.
And it it worked to add it to the Google Home only problem is that can’t see any device.
Any suggestion how to fix this problem?
in my configuration . yaml i have:

emulated_hue:
type: google_home
expose_by_default: false
host_ip: 192.168.1.12
listen_port: 80
exposed_domains:
- light
- switch
- script

26

I don’t know what shall you do more.

Please refer to my config.

–configuration.yaml–
discovery:
emulated_hue:
host_ip: 192.168.0.4
listen_port: 80
off_maps_to_on_domains:
- script
expose_by_default: false
exposed_domains:
- switch
- script

–customize.yaml–
switch.bathroom_light:
emulated_hue: true
emulated_hue_name: “Bathroom Light”
friendly_name: “Bathroom Light”
icon: mdi:switch
switch.bedroom_light_1:
emulated_hue: true
emulated_hue_name: “Bedroom”
friendly_name: “Bedroom”

27

This will show nothing in the hue unless you explicitly specify each device you want exposed to the hue emulator.
If you remove those lines EVERYTHING should show up.

28

Hi
thanks again for your help.
So far i tried every single version possible, with exposed domain and without, same with the host IP and type and expose_by_default: false,
So if i access http://192.168.1.12/api/root/lights i get flowing tabs:
JSON that is empty
Raw Data with {}
Headers with:

Response Headers
Content-Length 2
Content-Type application/json
Date Wed, 09 Aug 2017 15:18:31 GMT
Server Python/3.4 aiohttp/2.2.3

Request Headers
Accept text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8
Accept-Encoding gzip, deflate
Accept-Language en-US,en;q=0.5
Connection keep-alive
Host 192.168.1.12
Upgrade-Insecure-Requests 1
User-Agent Mozilla/5.0 (Windows NT 6.1; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0

I have a filing that is a binding problem of homeasistant with hue emulator.
Thanks again.

29

What shows up if you hit http://192.168.1.12:8300/api/pi/lights ?

30

i get nothing on 8300
Just Unable to connect

31

That’s again because Google Home uses 80, not 8300. You would expect to see nothing using 8300.

32

Technically incorrect, I use port 8300 with my Google Home devices just fine.

I use

emulated_hue:
  type: google_home
  listen_port: 8300
  advertise_port: 80

and have an iptables rule that redirects incoming requests to port 80 to port 8300. Works like a champ.

1 Like