It’s pretty easy if you just follow the directions. They are spot on without any holes. I went though it last week myself and didn’t get tripped up.
As for the easiest, that would be the cloud. But it costs money.
I really think you should just give it a go. It might take a few hours but it probably won’t change. I setup haaska 3 years ago before I moved to emulated hue. That old version of haaska is still running without any changes. I forgot it was still running and turned it off when I moved to Alexa Smart Home Skill.
Emulated hue still works great. Just doesn’t work with alexa. It still works with everything else that talks to a gen 1 hue. In fact, I still use it for my harmony remote.
Nothing to be fixed on home assistant’s side. The problem is that amazon no longer looks at port 8300, amazon only looks at port 80. Port 80 is not accessible to home assistant. Hopefully amazon will fix it, but I doubt it.
Has anyone actually identified what the issue is? If it’s just that emulated_hue is returning nulls for a property, that can’t be that difficult to change to an actual integer.
Yeah because it was local. Also they had the same functionality at the time. I.e. everything was a light, nothing else. In that time hue stayed the same and haaska grew. Which makes sense because gen1 hue bridges haven’t changed.
Uh, that’s not the issue at all. Half the people in this thread have switched emulated_hue to use port 80 and the problem still persists. Please delete your reply as it’s just adding noise to the thread. In fact pretty much all your replies have focused on using workarounds versus actually addressing the issue.
It IS the issue. Amazon switched to port 80 which started all this trouble, then people switched HA to have emulated hue to be on port 80 via one of the various methods listed in this thread which allowed emulated hue to “talk” to Alexa devices again, but some people had other issues (device out of range, device not responding–even though it was)
No, it’s actually not. If you debug the emulated_hue response versus an actual Hue bridge, the JSON is failing on very specific things that are NOT light bulbs, because it’s expecting certain parameters based on the device type. See the actual bug report on this.
It has barely anything to do with port 80, which is a simple fix either via proxy, or by configuring emulated_hue to use port 80 directly. Port 80 might’ve been one of the initial problems, but it’s not the actual underlying issue.
I don’t have a bridge to compare to and frankly I don’t care. An Amazon firmware update broke HA hue emulation talking to Alexa devices. My Hue emulation listening on port 8300 was no longer detected by my Alexa devices. I used iptable to port forward port 80 requests to port 8300, my devices were all detected once again, but Alexa complained about various things. Without the listening on port 80, Alexa never detects my devices. So once again, this is what broke it initially.The other stuff you mention is also a problem, but not same issue.
If you look at the thread, the exact error responses people are getting from their Alexa devices are what’s in the bug report. So yes, it’s the actual issue.
I have been in this thread for over a week and posted several of my experiences with my setup, so yeah I know what the thread says. If you don’t set hue emulation to listen on port 80, IT WONT WORK… PERIOD. Have you tested this on your setup? I spent hours testing this and when you have some like @petro who is very knowledgeable saying over and over that its a problem, its a problem. The problem you mention IS ALSO a problem. Trust me, none of my switches worked even after I set hue emulation to listen on port 80, that is why I moved to Haaska
I don’t know if you’re actually reading my responses, but to borrow petro’s phrase, for the millionth time, port 80 isn’t the ultimate problem. Once you switch to it your devices can all be discovered, however certain devices which are emulated as binary (on / off) vs brightness (0 - 254) and have specific types of attributes (such as scripts and automations) will not function because Alexa is expecting certain non-null values after the initial state is set. This is the error that has Alexa saying that the device is unresponsive after you switch to port 80.
It’s nice that you switched to Haaska, and while that is useful to some people as a workaround, there are plenty of people in this thread (and reading it) who would actually like to know the root cause, not put a bandaid on it.
No. That’s the first thing anyone troubleshooting and debugging this would change. After that, you start digging into the JSON payloads, and you see that Alexa is asking for attributes it previously was not. The issue is that emulated_hue has to return those newly requested values (a REAL Hue bridge always had these values, but they were never requested prior).
The second issue that this Petro fellow keeps posting in every single emulated_hue + Alexa thread about how this is an issue that can’t be resolved in emulated_hue. It can be, and is being worked on (see PR 26541), but he keeps shutting everyone down, making for discussions that instantly come to a halt.
I get what you are saying. I feel like all these changes all happened when the firmware was updated by Amazon though and for me personally, I just switched to a different method that HA supports and works far better than emulated hue ever did (for me personally with my devices and setup)
That is a good point. I would also bet there are just as many people in this thread that just want their devices to work with Alexa and don’t care how/why, etc
Did you read the top of the thread? The very first post?? Did you read the solution? This thread is 100% about the port issue. Any other issue in the thread is just a side issue that has nothing to do with the original post. I hope you understand that while you’re combatting us.
It’s most likely that as soon as you switch to port 80, provided you have certain types of devices, you will immediately run into the second problem brought up the firmware change.
While the problem posted at the top is directly related to port 80, the ENTIRE issue goes further than that. Not to mention when people are reading this thread with similar issues, they want more than just the initial problem. In order for it to be helpful to the most people, the solution and problem should not only be as comprehensive as possible, but as clear as possible.
That’s not really an exclusive either/or situation. If you understand the root cause, you understand why it’s broken, and can therefor a) fix it or b) understand why a different workaround may be better.
That’s the thing, one of those issues linked in the PR is 3 months old. Way before the firmware update existed. I highly doubt that the communication process changed. People have been making changes to emulated hue platform over the past 5 months, and those changes are likely the cause of the problem. That doesn’t change the fact that the firmware broke my 0.84 build of home assistant. I’m able to put that on port 80 and it works great. No communication issues what so ever. I really doubt that this pr is anyway related to the firmware update. Second point being that hue hasn’t updated it’s firmware for the v1 hue bridge since Nov 28, 2016. Which is what emulated_hue emulates.