hue emulation 2.5m1+m2 had this problem and it is fixed since m3.
That is fantastic. Since I’m still on OH 2.4, any chance there’s a public repository with the compiled m3 jar I can download?
So can anyone speak to why the 2.3 version of Hue Emulation has gone dead? Was there a change in firmware of the Amazon/Alexa side that preventing communication? I have an almost 2 year stable install go silent and unable to communicate with Alexa.
That’s an interesting question. I’m on 2.4 and questioning the same. Is it enough to install hue emulation binding 2.5 M3 to fix the issues? Are the devs aware of the issues?
I have posted on GitHub with the issue…over 2 weeks with no comments.
Still looking for a M3 jar to try out. BTW, I did some digging and a recent discussion has comments that suggests that all 2.5 milestones have hue emulation problems. See the dialog deep in this:
Can someone confirm that the m3 hue binding is a winner?
The new code is a rewrite. It does behave different (emulating a V2 hue bridge with a 2018 firmware). But at some point you just don’t have a choice. The V1 bridge is EOL and Alexa and Co might not support that anymore at some point.
Because the hue V2 bridge supports https encryption, which requires a few specific keys to be set in the certificate, it is not necessarily easier to set that up. https is not yet required though as far as I know.
Then 2.5 M3 hue emulation and following release is the way to go? And where do we get it manualy, for a 2.4 stable install? Or do we have to install OH 2.5 betas?
I do not use Hue emulation and can not confirm that the version in 2.5M3 would fix your problem. If you decide to try the latest version (at your own risk), I would strongly suggest you make a full back up of your 2.4 installation before trying in case you need to revert back to your old version.
I decided to upgrade my 2.4.0 snapshot (build 1412) to 2.5 m3. Spoiler alert: I failed miserably.
Not a fresh install; I used OH2’s config to upgrade to the latest testing branch. This was my process:
- Stopped OpenHab2.
- Cleared the cache.
- Installed the 2.5 m3 update from config.
- Checked all my files in /etc/openhab2 and made sure they were still there.
- Manually set iptables (port 80 fix).
- Confirmed boot screen showed new version.
I could not get MQTT v1.x to work (MQTT broker was fine, but OH ignores it). And although Hue Emulation found all my devices after discovery, it still assigned two names to many devices. And none of the devices respond (echo dots respond with the frustrating “check the device” message).
After a couple hours of hair pulling I abandoned the 2.5m3 upgrade. Next I copied its Hue Emulation jar file to my local drive. Then restored my old OH 2.4 system and replaced the existing 2.5 snapshot (22.214.171.124901011334) jar file with the new 2.5 m3 jar.
My 2.4 Snapshot system will not run the 2.5 m3 jar that was extracted from the upgrade. It breaks the web interface so I can’t load paperUI.
I’m back to my old 2.4 Snapshot. Hue Emulation was fixed two weeks ago (after manually installing a 2.5 snapshot jar). Then it broke again a couple days ago. Today’s efforts didn’t get me any closer to a fix.
At this point I think the solution is to start with a fresh install of 2.5m3. But I don’t have confidence that Hue Emulation is working correctly on it. As far as I know there’s no authority with a answer on that.
So the big question: Are there any 2.5 m3 Hue emulation users out there with a fully working system? I mean, a system that works as well as we had a month ago before Jeff B’s coders messed up the API?
if you report your problems in this thread, the developers might be able to use the information to fix the problem
@ThomasOH my hue emulation works on 2.5m1. I had trouble on 2.4.
I tried m2 and m3 but had issues with hue emulation. I have been tied up but plan on setting up a dev box soon(2weeks) to test m3 on a fresh install with no other bindings.
I have not seen anyone else complain, but I don’t know who else has tried Emulation on m3, except you. Also I am in the US where r u? Curious I am thinking this may make a difference also.
Regarding the duplicate devices showing up: I found out that (non-functioning) devices re-appear if you do not deleted them one by one via the web-interface. As long as you use “delete all” they come back as duplicates and mess up your setup. Delete them device by device.
It still works for me with the old 2.5 version of the Hue emulation addon.
Thank you (again)! That tip is gold. I deleted over 90 devices and a new discovery found 50. That’s a more realistic count.
And I’m back to the working state I had two weeks ago. I still have the bug where Alexa responds to dimming commands with “Sorry, [device name] appears to be malfunctioning.” But the lights reliably dim, so it’s not a big deal. On/Off commands work without any issue (no complaints from the echo dots).
It’s still a mystery why my Hue Emulation went wacky on its own. As I mentioned before, I saw a nearby echo do the ring of light dance late at night. Then the next morning I found Hue Emulation was broken again. My best guess is that something triggered a discovery that went badly.
I’m in the USA (west coast). Please report back after you test Hue Emulation on 2.5m3.
Can’t wait for the results.
btw. shouldn’t it be possible to use the 2.5 binding with OH2.4?
Thomas, can you let everyone know what you ended up doing to get it working? Your previous post explained what you did that did NOT work, but now it seems you’ve figured it out. So for instance, what version of OH and the Hue binding are you using? And did you have to do anything else besides the port 80 fix and manually deleting/re-adding the devices through the Alexa web interface? Thanks.
Please see my Sep-30-2019 post. It explains everything I did to get Hue Emulation working before the new issue appeared a couple days ago. But that is fixed too, per the new post you read.
BTW, five minutes ago I witnessed a nearby Echo dot do a firmware update. It was on Version 645584020, now it is 647591020. I don’t dare try a new discovery since it seems Jeff B. and his coding friends are out to get me.
There are also encoding problems in the discovered device names now: German umlauts (ä, ü, ö) are broken und Alexa then does not understand the names.
A workaround is to manually fix the broken names in the Alexa App.
The situation seems to get worse day by day.
Philips added window blinds and wall sockets to the protocol. So Amazon needed to upgrade their Hue support. That’s my guess.
German umlauts (ä, ü, ö) are broken
Hm. Hue emulation does not send any encoding header, but it will send utf8 characters. That’s usually java’s default. Maybe we should start to send a utf8 encoding header.
btw. shouldn’t it be possible to use the 2.5 binding with OH2.4?
No. 2.4 and 2.5 are mostly incompatible. The dependencies have changed too much.