Hi Tom,
how could I make this work in a docker Environment?
Thanks, Budo
Hi Tom,
how could I make this work in a docker Environment?
Thanks, Budo
There are more of those subtle differences. I guess it is 1. that makes all DIY solutions struggle at the moment.
@David_Graeff thank you for pointing this out - I wasnât aware of that.
I understand these two differences as being binary: you either use HTTPS or you donât. You either choke on malformed content or you donât.
Do you have any suspicion how this could lead to the problem described in https://github.com/openhab/openhab-addons/issues/6690?
Because that problem is not happening all the time, only most of it.
Itâs not that easy. From a specific hue api version onwards the real bridge only allows https. Alexa Echoes might try https first, fallback to http for the command but will return a âfailed to communicateâ spoken response.
Regarding the http headers: This issue happened mid 2019 already. Hue emulation strictly expected âjsonâ formatted content as specified by the Hue specification. Alexa Echos were sending json but an http content header of âtextâ which resulted in non working communications.
This probably has happened again with another http header. Alexa is expecting something, that we do not send yet or send in an unexpected way and that leads to a âdevice not respondingâ spoken message. I do not have time to debug that though.
Cheers, David
@David_Graeff - thank you for the explanation.
I wish I had more experience with debugging & coding, so I knew better how to investigate this some more myself.
If I want to analyse the communication between the binding and Alexa, how would I set that up? If I had to do it right away, I would install wireshark on my desktop with the goal to grab communications between Alexa and my (productive) OH (which run on the same network but not on my desktop). I doubt that that would work though, as I think the communications on a switched network will not involve my desktop machineâŠ
You donât need to invest much time in answering this, as I might not find the time I need to get up to speed with this. But if you can give me some hints or just names of tools/procedures I can google, that would be much appreciated.
Cheers! -bastian
Iâve submitted a PR which resolves the issue of Alexa complaining about the device malfunctioning when setting to a percentage, e.g. set room to 50%
I have the same issue here. On Top Alexa canât handle âĂŒĂ€Ă¶â anymore
Can i install the hue emulation from 2.5M1 on my 2.5.1 Openhab ?
This one worked fine.
Could anyone provide me a link to the 2.5M1 hue-emulation addon - canât find the jar anywhere
Would try if it works and report back
Simply rename the devices with the broken Ă€Ă¶ĂŒ in the Alexa App. Umlauts are working there
I canât control the devices anymore - even if I rename them.
I can see them in the Alexa app as:
Verbunden ĂŒber: Hue Hub
Beschreibung: Royal Philips Electronics intelligentes GerÀt
Typ: sonstiges (various)
No way to control it
@ChrisW If you updated openHAB you will have to delete devices one by one and rescan. Once alexa gets confused this is the only way to fix. Most of these problems appear to be with how amazon identifies and links things behind the scenes.
I did that already.
It will discover the Items but they will show up as
Beschreibung: Royal Philips Electronics intelligentes GerÀt
Typ: sonstiges (various)
and I canât control them (tried using voice commands and the app)
Also it isnât just Alexa which isnât working any more
Logitech Harmony Hub also canât control my openhab items through the emulation anymore
Tried the https://openhab.jfrog.io/openhab/libs-milestone-local/org/openhab/addons/bundles/org.openhab.io.hueemulation/
2.5.0.M2 from here (which also needed org.jupnp bundle , but it did not change the results.
(Hue Emulation was uninstalled from PaperUI before)
Iâm pretty much out of ideas and might to have go back to my 2.5M1 backup.
Hi there
1st off all, thanks Mike for submitting the issue. They seem to have it fixed, but how would I patch it on my local system? Iâm on stable 2.5.0. Also I donât understand if this is an error of OH or hue emulation.
Iâve setup my rollershutters (which are actually dimmer items) to be controlled by Alexa over hue emulation.
Dimmer JA1_R1_Level "KĂŒchenfenster" ["Lighting"] {channel="homematic:HmIPW-DRBL4:XXX:YYY:2#LEVEL"}
So when I give commands like âAlexa KĂŒchenfenster 25%â or âAlexa KĂŒchenfenster 90â - it does work but Alexa very often replys: ââKĂŒchenfensterâ scheint nicht richtig zu funktionierenâ
Thank you
Would it help if we used nginx as a HTTPS-to-plain converter?
Itâs already setup for a number of people to redirect port 80 to openhab.
Guys take a look here, this seems to allow the hueemulation module to load properly
https://community.openhab.org/t/solved-no-opencloud-when-upgrading-from-2-4-to-2-5m4/85348/41