Emulated Hue suddenly stopped working with Echo Dot V2

Configuration
21

Nope, never signed up for any beta testing. Wondering if there’s a contact I can ask on Amazon’s side stating my firmware is not listed on the website.

22

I am in US and have not signed up for beta testing. Can’t be that we are the only people experiencing this problem… Unless we are guinea pigs for new FW rollout.

23

I’m not experiencing the problem. I’m running all V2. All my dots have sv 641575220.

You all have the same setup except running sv644580020. You all have the same issue. I’d be willing to bet you guys are the only ones having the issue.

24

Have any of you @rrshep100 @swiftvic @PCRx ran logger on debug and viewed the communication process in HA?

25

I do have a logger running for some components. How should I set up my logger for emulated hue?

logger:
  default: warning
  logs:
    homeassistant.components.mqtt: debug
    homeassistant.components.device_tracker: critical
    homeassistant.components.switch: critical

Add homeassistant.components.emulated_hue?

26

I believe so.

27

Entered debug for homeassistant.components.emulated_hue and ran overnight. No associated debug messages.

28

you’ll only get debug information when you try to turn a light on or off using emulated hue. You’ll also get them if something attempts to talk to it. Leaving it on overnight isn’t going to do anything if nothing is communicating with it.

29

Got it. I actually did attempt use Alexa to turn on lights and to learn devices. Nothing worked and no debug messages related to emulated hue.

30

If that’s the case, then alexa doesn’t see the endpoint. I.E. it doesn’t see http://<HA IP Address>:8300/api/pi/lights.

31

edit. Alexa is still linked to my Nexia thermostat and now linked directly to a LIFX bulb. Alexa can control both properly. I removed all of the devices known by Alexa through emulated hue and Alexa now cannot discover them.

32

Discovery requires UPnP is that on in your router?

33

Thank you for the info @petro. Yes, UPnP is turned on and for good measure, temporarily turned off router firewall.

34

Ok, so been talking in a few other threads. Seems like they are rolling out new firmware. Anyways, in another thread, it was mentioned that adding listen port 80 helped with discovery with the new firmware.

35

No dice, tried it and it broke Harmony hub as well from connecting to emulated hue.

I also wasn’t able to list the components via link http://<HA IP Address>:80/description.xml. It just said that server refused the request. Do I need to forward Port 80 on my router?

Logs didn’t show anything either.

36

I don’t think you would. This is all done locally.

37

Hi all. Had to register to comment that I’m also experiencing this issue with both my V2 (software version: 644580520) and V3 (software: 2785572740) Dots. They were working fine until 2 days ago.

38

Hi. Try this:

http://< HA IP Address >:8300/description.xml

Mine responds fine to that. It’s all probably Amazon messing about with new and innovative “features”. Hopefully there are enough Philips Hue users complaining to Amazon about this so they can fix it quickly.

Regards,
JR

39

Yep the 8300 works. I was just trying Port 80 as @petro was suggesting to try.

I did contact Amazon and they gave me a canned message about contacting their tech support for help. Not sure if they’ll do anything useful since it’s a third party integration and not an off the shelf product.

40

I submitted a case with Amazon here: https://developer.amazon.com/support/contact-us. They also suggest to post on their forum: https://forums.developer.amazon.com/index.html.

While Amazon may have changed/broken something that makes calls to HA differently, I suspect this is an issue with any Philips Hue-compatible system. There’s a good chance Alexa can’t tell HA from a Philips hub. Perhaps a HA Dev can tell if Alexa is making a different call than before.