The problem has disappeared, after I rolled back the configuration.yaml to the default one and piece by piece added my stuff back in again. Now I’m back to my recent set-up and everything seems to work. This is really weird…
The KeyError issue happens if you’re exposing input booleans to emulated hue but they do not contain a friendly name. This has been fixed and should* be part of the next release.
I’m a bit confused. The emulated_hue component doesn’t need Home Automation Bridge. Correct ?
1 Like
Correct. Home Automation Bridge is unrelated to HASS, but it can achieve some of the same things.
Hm, still not working here… After what I described above, I though I was fine and it was Alexa’s fault not to discover any devices, but she’ll find anything else, only not the emulated_hue of home assistant.
Hue itself and some fauxmo emulated devices work fine.
Now I gave up on emulated hue and set up HA Bridge, but I don’t get that to work either… I configured a sample device, but using the “Test ON/OFF” buttons does not show any reaction. How do I debug HA Bridge in such case?
And is there a better way of configuring devices in HA Bridge that exist in HASS? It is so annoying to configure everything in two places… I really wish I could get emulated_hue to work again…
Not sure if this helps anyone else but every time I make a change to Hass using emulated hue (like adding a new device or changing a name), Alexa won’t see it…Until I reboot my wifi (Aruba Instant in this case). After the wifi comes back up, Alexa sees all the devices and I can add the new changes to her. If an hour goes by and I make another device change I have to repeat the process. Like everyone else, this is never an issue with my actual Hue bridge. I haven’t checked if HA Bridge behaves the same way yet.
and just running discovery devices on alexa app?
My Echo finds the new devices defined by HA Bridge, but can’t switch them on or off - same as the Test ON/OFF buttons within HA Bridge.
Yes after restarting wifi I run the find devices option on the alexa app.
Restarting my router / wifi didn’t change anything.
Just an FYI, my issues with discovery were solved when I moved my RAspberry Pi running HA off wifi and on to a wired Ethernet cable. Everything worked great after that.
Could someone be so kind and post a sample configuration of a HASS device in HA Bridge?
I have followed the fearoffish tutorial, but as he is using https and password and I’m not, I’m not sure what to put in http headers.
Here’s my config of a device:
Name: Stehlampe
Target: Encapsulated
Device Type: Custom
Map-Type: none (“please select”)
Requester-access: empty
On URL: http://raspberrypi:8123/api/services/homeassistant/turn__on
Dim URL: none
Off URL: http://raspberrypi:8123/api/services/homeassistant/turn__off
[{“name”:“X-HA-Access”, “value”:""}]
Http Verb: Post
Content Type: application/json
Content Body On: {“entity_id”:“light.schalter_stehlampe”}
Content Body Dim: empty
Content Body Off: {“entity_id”:“light.schalter_stehlampe”}
When I use the “Test O” or “Off” buttons on the Tab “Bridge Devices”, nothing happens. The greenish success message box on the top right of the screen appears about 5s after the button press…
Ok, I git HA Bridge working now - the URLs provided in the fearoffish blogpost didn’t work, these work:
http://raspberrypi:8123/api/services/light/turn_on
http://raspberrypi:8123/api/services/light/turn_off
I.e. domain name instead of “homeassistant” and only one underscore in “turn_on”.
Thanks Klaus, your post help me solve the issue.
I am thinking of using HA Bridge for Alexa and Emulated Hue ( HA) for working with Google Home.
Any Suggestions or advice ?
After i have discovered the habridge switches on Google Home, i am seeing two devices for each entry.
And i confirmed it is not from HA config , since when i delete the switch from Habridge 2 devices get deleted.
What does this mean???
If you go to the webinterface of HA Bridge you will see that there is an option to do this
