Also on OH 5 it is not. Same behaviour as 4.3
Then I’m out of the game. It has not worked several weeks for me under 4.3.6.
My account and my echo thing was not more getting online.
After updating my first system from 4.3.6 to 5.0.0 the same offical amazon binding was used.
And it worked after the first reboot after the update on my RPI4. The same works now on two other systems with RPI4 and RPI5.
Text-to-speech works as it should. So I get all my notifications over rules when something happens, like rain, thunderstorm etc…
Text to speech works also for me if I select “None” in the binding configuration for objects to be discovered by the binding. If I try any other of the configuration options I also loose the Text to speech (this behaviour the same on 4.3 or 5.0). In no way I have smarthome devices connected to Alexa via skill working in OH even if all things are green.
I expect to do some work on this binding the next week. @sihui has sent me an echo dot to help troubleshoot and see what i can do.
It would be highly appreciated to have several cases that i can work on.
Could those of you who have issues provide me with fully stripped down minimal examples that show the problem you experience and is reproducible?
With that i mean a textual or ui configuration without unrelated settings, things or items. And log or screenshot that shows the issue.
Maybe a lot is already available in this thread, but providing it this would make me able to focus on a quick fix!
I still on version 4.3 and located in Brazil. Everything is working fine. The account thing was showing the same error Failed: null reported here bur as soon as a changed discoverSmartHome parameter to 0 it is on line and no more error on the Thing. If I’m not mistaken the default for version 5 is also 0 that could be the reason some people does not have the error after migrating.
The page used to configure the thing was and has always been working even with the account Thing in an error state (http://openhab:8080/amazonechocontrol/).
@lsiepel I started having this Amazon Echo binding problem from version 4.3 itself. I have upgraded to 5.0 but the same issue still persists. Following is the error I am getting since beginning. I have tried logging off and logging in, with 2FA disabled and enabled, but the same error. Seems the said URL is not reachable.
I have followed many other threads on the similar subject and found that most of the users are getting the same error.
I can share more info around this if required. Let me know please.
Edit: While it stays Offline for me, Text to speech is working fine for me. Basic Amazon Echo functionalities are working, but all my smart home devices connected to Amazon account are not working through OpenHab connected to AmazonEcho through this binding. All Amazon connected smart devices says “Bridge Offline”.
Here my feedback to the Amazon issue.
My focus is only on text-to-spreech function from my Amazon Echo.
I have had 4.3.6 running until the issue started, that the Amazon Account and the Echo Thing, was not more online. No way for me to bring them back somehow under OH 4.3.6
The only way was to update OH to 5.0.0 in the same timeframe, were OH5 was released.
Meanwhile the Amazon Account and the Echo Thing is online back (green) and I’m getting
text-to-spreech out of my Echo.
When I try to change the configuration from the four values (current none is selected)
to any other, save it and close the thing, it show, me short red, than a sec later green.
But after that the text-to-spreech is not working anymore.
When I save it again to (none), the text-to-spreech is not more working.
I HAVE TO REBOOT THE OH SYSTEM.
After reboot it works and the Echo tells me stuff which I send him via rules.
Very clear example, i don’t think this is hard to fix and have some thoughts on how to. What i have now:
Issue 1:
Multiple users reported when the discovery is set to none it works, other values make the binding fail.
issue 2:
Changing the discovery value is not reliable. It takes a reboot to take effect (this makes issue 1 more hard to diagnose, false positives)
Issue 3:
The bridge shows offline while other things show online. Issue is not fully clear yet. Needs reports/investigation
Issue 4:
The api changed both authentication and endpoints for getting lists. The authentication might be the cause of issue 1. The lists should still work as the old endpoints are not removed but marked deprecated. Nevertheless a change is needed.
Issue 5 (edit)
in OH5 lastVoiceCommand is not working at all
I think there is one more issue, with:
“in OH5 lastVoiceCommand is not working at all (which is not worse than sporadically)”
As I do not use this, I cannot verify that.
1 Like
Seems Amazon has changed something at their end which has fixed the issue at my end. My Amazon Account is also green and when I select discoversmarthome to 3, then also it remains green. All my Amazon connected smart home devices are also online now.
1 Like
I turned my bridge thing back on and now see all green. It would seem that whatever broke before has been reverted.
@lsiepel Issue 1 resolved for me
Issue 2 I never faced. Even today when I changed it, it changed immediately without any reboot.
Issue 3 Everything is online for me. Bridge is online, things are online, Amazon Echo Devices are online, Connected smart home devices are online.
Issue 4 - No impact to me now. Previously I tried with and without 2FA and it didn’t work. Now it went online on its own without me changing anything at Openhab or Amazon Account.
Issue 5 - Not using it.
For me everything works as intended.
1 Like
Interesting….
After read this thread, I also changed from 0 to 4, and to 3 in the configuration of the account binding.
In the middle of this week, only 0 as settings was working for me with my testrule which uses text-to-speech…
Just tested, and it works in all configuration….
It seems Amazon changed something on their end sometime yesterday. Most reports are that the binding is working again.
Also first time tried the last-spoken-command. This channel is now also filled.
I only see a channel for lastVoiceCommand and for lastSpokenText. The missing feature is the first one. Can you confirm that in your case it works with OH5 with the standard binding? But maybe it’s better to resume this conversation in the other topic which is specific for lastVoiceCommand.
Yes, I can confirm, that under OH 5.0.0 the default Amazon Binding, with settings #4, and my echo as a thing, the channel
- last command ( volume 1)
- Last spoken text ( I ask her what day today is )
Gets in OH an update, when I talk to Alexa.
I can also confirm all seems to be working for me.
My issue was “Number 1” - i.e. smarthome discovery would fail if set to anything other than 0 and therefore I couldn’t use things like the built in temperature sensors on my Alexas.
But all is working now, no errors and temperatures are being reported back.
All good.
@lsiepel and everybody,
I got the same issue again. The same Amazon account error and the connected Smart home devices are offline. I did not change anything at my end.