Yeah. [0.110.3] is out with Fix emulated_hue compatibility with older devices, but… still no discovery luck here. What about you? Are you having any luck?
Do you have the minimum requirements? Emulated hue requires an gen 1 or gen 2 echo on your network. Without it, it will not work.
Also, emulated hue is very finicky. It has a device limit (subject for debate but the general consensus is that it’s between 50 and 70 devices).
Hi, is there anny actual information about ECHO Dots? echo dot V2 does still work or is this one to new?
It did wok in the past but with the mess in autum it stopped and will also not work using port 80 (but different smart home tool) Just asking because here is the best information overview I could find…
Thanks
Boardy
Have anyone got a clue why the “appears to be malfunctioning” comes up 50% of the time when I use it with my zwave devices. I think it must be a timing issue that Alexa verify the outcome before HA has had time to actually show that it has turned on/off it. If it is a timing issue it seems it could be solved quite easy by just make Alexa wait a little longer before giving it the status. Any good codes that can check? 
OK, found a workaround for the “appears to be malfunctioning” message for devices responding a little slower, I created a input_boolean from Configuration -> Helpers and called it fake_switch. So after that I exposed the input_boolean.fake_switch in emulated_hue and named it “Fake Switch”. Next I renamed all my Zwave devices in emulated_hue . Ex. Old name “Bathroom Sink”, new name “Zware Bathroom Sink”. Now I removed all devices from Alexa and rediscovered them. Finally I created a group called “Bathroom Sink” and in that group I placed “Zware Bathroom Sink” and “Fake Switch” in that group. Done!
Now the fake switch respond right away making Alexa think all is good even if my zwave switch is lagging a second or two. And yeah, you have to create one group in Alexa for each slow device, sorta a pain but it works