I tried exactly that: All smartHomeDevice things are deleted, I cleaned he cache, the device discovery result, backups, etc. When I restart, I don’t get an error. In the moment I add the things after discovery again, the Channel type ‘amazonechocontrol:humidity’ is not known message appears in logs.
Binding version is the official 5.0.1. I used the smarthomej before. Thanks for further ideas…
Could you verify the exact version of the bundle from the console ? bundle:list
I’m a bit lost as no others seem to have this with the recent fixes.
This bug should be fixed with [amazonechocontrol] Fix `IllegalArgumentException` for devices with humidity by lsiepel · Pull Request #19212 · openhab/openhab-addons · GitHub. However, that was cherry-picked into the 5.0.x branch on August 21st: Fix type (#19212) · openhab/openhab-addons@163c601 · GitHub. And 5.0.1 was released two days before that: Release openHAB 5.0.1 · openhab/openhab-distro · GitHub. So it will be part of 5.0.2.
Thnx @laursen
thanks for the info. Then let’s wait a little bit and see when we can expect the release.
…and works, THX!
I am on 5.0.2 via docker, just freshly installed and its not working, the pheonix api bug is back again.
COMMUNICATION_ERROR
GET url ‘You've received an Alexa Link failed: null
Same on latest.
Can you share the exact log you see?
Double check; no jar file left in your addons folder?
Environment: OH 5.0.2 - Openhabian
My Alexa binding went suppenly offline yesterday after a reboot and did not came back.
I tried to login in the account again but it failes with chrome and firefox.
After I entered the password, I can reach the two factor aouthenthication. It says always:
Invalid redirect to 'https://www.amazon.com/ap/mfa?ie=UTF8&arb=XXXXXXX-XXX-XXXX-XXXX-e8fe00403430&mfa.arb.value=XXXXXXXX-XXXX-461d-a10c-e8fe00403430&mfa.arb.key=arb'
Try again
Any clue how to fix this? Does it work for others?
No:
Thanks for the hint! And sorry that I did not see that other thread.
Unfortunately i had to reboot.
Now i have the same problem.
Amazon sends me an OTP but there is no place to put it in
openhabian 5.0.2 on Rasbee. All updates done
same error after reboot.
Probably due to the 2-factor authorization I recently enabled.
I have the same problem here for few days, all echocontrol things offline, and not able to re-register/login the plugin.
I tried many times, even received OTPs but no luck.
I enabled 2FA but does change nothing.
Same here.. all devices now off line cannot relogin.
Same issue here
strange thing, it works AMA to OH. if i say alexa turn on lights, its working.
All requests to AMA do not work.
Same here, after OH reboot the amazon account thing is stuck in config pending state and shows link to the echo control servlet:
CONFIGURATION_PENDING
Please login in through servlet: http://openhabian:8080/amazonechocontrol/51bb1c10f3
Link takes me to a login page where I enter my amazon credential and then get returned:
Invalid redirect to 'https://www.amazon.com/ap/signin?arb=
However control of openhab things through my echo devices seems to work normally so the skill still works. It appears to be the echo control binding specifically that is hooped.
Amazon has removed the semi-official bootstrap API. As a result, the Echo binding is broken
@lsiepel is working on a solution👏, but it’s a bigger undertaking
For now, the options are to use Home Assistant or Node-RED and connect to openhab. I went the Node-RED way. It doesn’t cover 100% yet but if somebody wants to participate and improve I’m happy to show the current solution.
