Looks like someone saw something in the code, and has submitted a fix!!! Huzzah!!!
Great news! Maybe now the newer 2.5 versions will work for me also.
@KidSquid I tried the jar file on 2.5m5 and it worked for my test item.
I will try to restore a backup of more items tomorrow.
1 Like
Yes the new jar file works, but alexa gives an error. I have been using anyway even though she says I am sorry something happened.
@lopez1de I am running 2.5m6 emulation.
I am working, some commands receive an error from alexa but work fine. Could be a sluggish network connection because it is intermittent.
Good news is it does function.
Bad news to get it to work, I had to rebuild from the ground up. Meaning I manually moved my config files over one at a time. No matter how hard I tried if I did a restore of my backup zip file I could not get a working system. If you use paper ui I suspect thing may be ok.
2.5 is out. Any good news for this topic?
2.5 is working for me. I still have the port redirection in use, but Iâm not sure if it is still needed.
Dimmer-/Lighting-Devices still lead to the âdevice is not working properlyâ message.
Upgraded to OH 2.5. Itâs still exactly the same problem. I need to use port forward 80 to 8080. Devices are discovered as âRoyal Philips Electronics intelligentes GerĂ€tâ and I can use them, but Alex says â***** scheint nicht richtig zu funktionierenâ (eng: â**** is not working properlyâ.
Same with me on 2.5. (Rasp 3B+, openhabian, Echo Dot Gen 2)
Even Controlling the Rollershutter (Dimmer item) works properly, but Alexa responds with âdoes not work properlyâ.
One more thing.
I have a Harmony hub and can switch the lamps OFF with the home control buttons on the remote (long button press), but cannot switch them ON (short button press).
This used to be working, because they are found as Hue Devices as well.
After my update to 2.5:
I still get the âdevice is not working properlyâ problem for dimmers - apart from that everything works as it should.
Post update, I removed every device (one by one) via the alexa.amazon.com web UI and then rediscovered them all.
My OH setup runs on port 80 and I changed the âOptional Discovery Web Portâ in the Hue Emulation settting to port 80 to reflect that.
I have no port-forwarding to 8080.
Do you know - is there already an issue raised in Git to reflect the âdevice not working properly problemâ?
1 Like
I have done some further playing around, to see if I can gather some information which might be helpful.
My test setup:
- a dummy Dimmer item
Dimmer DTest "Test" (GDebug) ["Lighting"] - this item can be controlled via Alexa via voice
- I can verify via the JSON from the API (http://192.168.2.200/api/testuser/lights/69), that the
bri-value changes according to voice
{
"state": {
"bri": 206,
"ct": 500,
"on": true,
"reachable": true,
"mode": "homeautomation",
"alert": "none"
},
"type": "Color temperature light",
"modelid": "LTW001",
"uniqueid": "02c09d5c-3116-4074-9720-0b2ba01cbf3f-69",
"manufacturername": "Philips",
"swversion": "66012040",
"friendsOfHue": true,
"colorGamut": "2200K-6500K",
"hascolor": false,
"name": "Test",
"config": {
"archetype": "classicbulb",
"function": "functional",
"direction": "omnidirectional"
},
"capabilities": {
"certified": true,
"streaming": {
"renderer": false,
"proxy": false
},
"control": {}
}
}
- I can also see the change in the slider representation in the HTML sitemap
The following is a list of voice commands // the log statement // the JSON // the response from Alexa:
- âAlexa, schalte Test einâ // log: DTest changed from 0 to 100 // JSON: âbriâ:254 // no error from Alexa
- âAlexa, Test auf 50%â // log: DTest changed from 100 to 50 // JSON: âbriâ:127 // âTest scheint nicht richtig zu funktionierenâ
- âAlexa, Test auf 51%â // log: DTest changed from 50 to 51 // JSON: âbriâ:130 // no error from Alexa
- âAlexa, Test auf 52%â // log: DTest changed from 51 to 52 // JSON: âbriâ:132 // âTest scheint nicht richtig zu funktionierenâ
- âAlexa, schalte Test einâ // log: DTest changed from 0 to 100 // JSON: âbriâ:254 // no error from Alexa
- âAlexa, Test auf 51%â // log: DTest changed from 50 to 51 // JSON: âbriâ:130 // no error from Alexa
- âAlexa, Test auf 0%â // log: DTest changed from 51 to 0 // JSON: âbriâ:0 // âDer Wert liegt auĂerhalb des Bereichs fĂŒr das GerĂ€t Testâ
- âAlexa, Test auf 1%â // log: DTest changed from 0 to 2 // JSON: âbriâ:5 // âTest scheint nicht richtig zu funktionierenâ
What do I take from that?
- all commands make the item itself do what it should
- but most of the time, Alexa claims that something went wrong
- many âset Test to xx%â values result in Alexa claiming: â⊠appears to be malfunctioningâ (note: this may not be the correct English translation, I am only sure about the german voice output)
â but some values (51%, also 74% - probably others too) do not result in such an error output - when setting the value to 0%, Alexa claims: âthis value is outside the range of the deviceâ (again: this may not be the correct English translation)
As some numbers work and others donât, I suspect that the problem could be connected to some rounding issues, but that is for someone else to really inspect and find out - my coding skills are way to bad to do it myself.
If you have any hints what more research I can do and also where to properly raise this issue, please let me know, @Thedannymullen, @lopez1de, @NCO, et al.
1 Like
I checked all open issues for hueemulation and as I did not find anything covering this topic, I raised a new issue:
1 Like
I had some issues persist through an upgrade as well - I removed the hue emulation service, deleted all associated json files, unplugged echo dots for a few hours, removed all devices from Alexa web page, and finally reinstalled the hue emulation service. Once it was reinstalled I plugged in one echo and ran discovery. Everything seems ok now.
Iâm on 2.5 too and can reproduce all these errors as described.
Like described by @bastian?
(Alexa complaining even though itâs working properly)?
I also removed all devices and added them again, but this issue is thiss there.
@bastian great debug. Your translations were correct I get those responses from time to time.
From what I can tell this is an Amazon issue. I saw a video the other day about using node red for alexa local control. In that live stream she return the same response even though it worked. The video maker said thatâs normal right now.
@Thedannymullen How can this be an Alexa issue? Alexa doesnât show this behaviour with a Philipps Hue bridge v2.
@lopez1de True statement! I did not think of that. Then I am lost! I do however know this for sure. Mine is intermittent in when it does it. I from time to time on 2.5m6 get it. Now that I am done with holiday travel I will put the release version on. But on this version the error messages are only there 10-20% of time.