Hue emulation stopped working, all devices are of type "various" now

Apps & Services 3rd Party
78

if you report your problems in this thread, the developers might be able to use the information to fix the problem

1 Like
79

@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.

80

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.

1 Like
81

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.

  • Thomas
1 Like
82

I’m in the USA (west coast). Please report back after you test Hue Emulation on 2.5m3.

  • Thomas
83

Can’t wait for the results.

btw. shouldn’t it be possible to use the 2.5 binding with OH2.4?

84

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.

85

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.

  • Thomas
86

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.

1 Like
87

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.

3 Likes
88

Thank you soooooo much!!! I had the same issue and had to redirect to port 8080. This solved the problem i had.

again, thank you!!

89

Anybody got it (fully) working again?

90

My Hue Emulation still doesn’t work. Devices are detected as type “various” (“Sonstiges”). No control via app and no control via voice.
I am running openHAB 2.5.0.M4. Port redirection and various times deleting and searching didn’t help.

91

@haribo I have retained myself on 2.5m1 as the m2 and m3 release seemed to cause problems for me.

I have not tried the m4 release yet.

@lopez1de 2.5m1 works for me. Have you tried it?

92

I don’t know how to downgrade. Would the M1-Version of hueemulation be compatible to a M4 openhab system and where would I find the file (org.openhab.io.hueemulation-2.5.0.M1.jar)?
I found https://openhab.jfrog.io/openhab/libs-milestone-local/org/openhab/addons/bundles/org.openhab.io.hueemulation/ but only M2,M3 and M4 are listed.

93

I know you can install the full package using apt. Don’t remember the exact command right now.

Not sure if you can do just the jar file.

Your m4 setup should work on m1, unless you are using something that was added or fixed in m4.

94

Have a look here

95

Hi all,

just for your Info as it might be interesting for other 2.4 Stable (2.4.0-1) Users as well……

I only had to apply the port forwarding from Port 80 to 8080 as described in various comments before
sudo iptables -A PREROUTING -t nat -p tcp --dport 80 -j REDIRECT --to-ports 8080
(See for example the post from 1st Oct 6:37 from ThomasOH).
Afterwards in PaperUI -> Configuration -> Services -> Hue Emulation -> Configure
Pairing timeout = 90
Optional discovery web port = 80
Device Paring = Activate
And Click on “Save”. Now you have about 30 Seconds ( or prepere before) to logon to
https://alexa.amazon.de (or appropriate .com etc.). Click on Smart Home, Geräte/Devices -> Suche/Search. (via App it was not working)

Items defined in /etc/openhab2/items like
Switch Jalousie “Jalosie” [ “Lighting” ]
were discovered without issues again.

Yes I still had issues with some items only defined in PaperUI but not sure what was/is the problem here. I also still have issues with “German umlaut“ like Küche (Kitchen) but this is something I can manage.

I.e. NO manual update of HueEmulation Binding from default OH 2.4 was required! Maybe this was already known to you but but by reading all the previous post it was at least not clear to me.

Regards, Thomas

PS: Using an Echo Dot Gen 1. (Sw 647642120) + Gen 3. but it is working with both.

96

Thank you for the summary. But does it fix the problem that alexa says that something is wrong with the device after setting a light (dimmer) to a specific value?

97

I don’t have dimmers in use but as short test I added

Dimmer myDimmer “myDimmer1” [ “Lighting” ]

to hue-test.items

  • Enabled Pairing

  • I could see the new item myDimmer1 in http:///api/status.xml (just for verification purpose)

  • Enabled Parining

  • Did a search in alexa.amazon.de

  • Discovered new Device

  • Renamed myDimmer1 to Dimmer in AlexaApp (myDimmer1 was not a good idea as name to be recognized by Alexa)

  • Switch off/on via Alexa works fine

  • Command to set to 50% does work but still get a message from Alexa like “does not work” although value 50% was received by OH as seen in event.log

Regards Thomas

1 Like