I tried setting it to listen to port 80 butt after reboot, nothing’s changed.
If I run sudo iptables -t nat -A PREROUTING -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 8300, will this break my Google mini since it’s running on port 80?
I wonder if that’s why I can’t get it to work running on port 80.
@swiftvic best guess is you have something else running on 80 or you ran in to permission problems. Connecting to the port or running netstat on the server may help you debug.
@Jonde I had an interesting evening messing with my “working” system.
The voice notes from Alexa about either:
That value is out of range for device DEVICE_NAME
or:
Sorry, DEVICE_NAME appears to be malfunctioning
Even though they did work as expected was starting to bother me.
I ended up removing a bunch of (emulated hue) devices from the Alexa application by deleting them - I could not find a way to do that easily en-masse.
I also ended up removing the config/emulated_hue_ids.json file and re-discovering my devices. I ended up with duplicates 
I did not find a wonderful solution to that so kept cleaning up manually (https://community.smartthings.com/t/alexa-duplicating-hue-lights-but-philips-skill-disabled/111570/2) .
I also switched one of my highly used devices from a switch to a light - in case that had an impact.
After a few restarts and deletes I ended with the wrong names in Alexa app (and checking logs Alexa was still attempting to access old Hue ids, that no longer existed). So finally deleted almost every emulated hue device from Alex and renaming the ones I needed to the correct name and I’m back up and running withOUT the annoying voice problem.
With the older release of the emulated hue I’m seeing Tracebacks where Alexa is sending in old hue ids and then the lookup fails. These seem benign (I added a None check to homeassistant/components/emulated_hue/hue_api.py to supress the traceback (in HueOneLightStateView().get, the hass.states.get(entity_id) call can accidentally pass in None - this is a non-issue in headrevs as this is reported correctly https://github.com/home-assistant/home-assistant/blob/1bd22a129bc7db7babf2e9c2b85ef1af0885b7f0/homeassistant/components/emulated_hue/hue_api.py#L202 ).
I’m now wishing I’d not originally made use of the expose_by_default=true option, hindsight is 20-20 
That is really interesting! Thank you for sharing this. Will have to take a look at my setup also 
In the beginning I had expose_by_Default=true too 
You say adding port 80. Remove port 8300 or just add a second listen port on 80?
@clach04 so I was able to get it to work after running the line:
sudo setcap 'cap_net_bind_service=+ep' /usr/bin/python3.5 ,
Thank goodness. 
That’s the good news, bad news I’m still getting the “device is not working, please check it’s power supply”. Even though the switch did turn on, it’s just not showing in the Alexa app that it turned on.
I did try the following:
emulated_hue_ids.json file.Everything looked good up until I click on them to “turn ON”.
Light turns on but I get the “Server is unresponsive” text, and I can’t turn off the light from the Alexa app… (not a huge deal since I use HA for everything. However, if I speak to the Alexa app, it will turn off the light with no issues.
I mean I can live with this… for now I guess. Just a bit annoying. 
I removed port 8300 and added 80. The default is port 8300 even if you did not add: listen_port: 8300. So just add listen_port: 80
As @swiftvic noted, adding port 80 actually replaces the default of 8300. Emulated hue does not support listening on multiple ports but you can make emulate that with an iptables mapping like @swiftvic’s previous post.
I thought I could live with it too and then got fed up with the annoying voice which is why I ended up purging my old devices from Alexa. Its a day later and the annoying voices have not come back after the cleanup
I posted Getting Amazon Echo/Alexa to forget emulated Philips Hue components to see if anyone has tips for removing old Hue devices but web interface and manually removing was my best option.
I have the same issue but I have Echo v2 firmware 645583020. Is there any reliable solution how to solve it? I have read this post and suggestions, but no is working for me. I replaced port 8300 to 80 and something like Xiaomi plugs sometimes works but hue bulb not, so quite unstable.
My v2 dots updated yesterday morning and hue stopped working. I changed
listen_port: 8300 to listen_port: 80, restarted HA then went to the alexa.amazon.com website, not the app, and forgot all devices. Rediscovered devices and everything seems good. Glad this post was here 
thanks
I tried this, but there’s still the voice complaining how the device is not supporting this (but obviously it does).
I am already using port 80 for a Webserver, so the fix didn’t work for me. Am I lost now with this’s issue? Or is there still a possibility?
I use the virtualenv installation on a Rpi but run also a Webserver (Port 80) on it with a regular webpage.
(MainThread) [homeassistant.components.emulated_hue] Failed to create HTTP server at port 80: [Errno 13] error while attempting to bind on address ('192.168.31.39', 80): permission denied
any idea?
That’s exactly the same issue i have. You have already a web server running that uses Port 80
yes also 8300 did not working any more idea?
For me last night everything stopped working again… and suddenly there was old copies of all my lights (Royal Philips Electronics) deleting these using the Alexa website (“forget” them) and running discovery again added back working copies of each light.
so, i changed the listen port to 80 and restarted. no luck. Went to the alexa website and forgot all the devices. did a rediscover and now i have nothing. This really sucks…
Yes, no solution without a cloud… 
Maybe I should add… I did not change the listen port and also on 0.98.5