jwiseman
(Mr. Wiseman (OH 4.2 Snapshot on Pi4))
333
Hey Tom,
I’m running your latest JAR dated below for 24 hours and I’m seeing these entries now in the log file.
openhab> list -s | grep amazon
339 │ Active │ 80 │ 2.5.8.202008210340 │ org.openhab.binding.amazonecho
2020-08-21 21:10:24.934 [WARN ] [mazonechocontrol.internal.Connection] - Unable to wait for next call to https://alexa.amazon.com/api/behaviors/preview
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method) ~[?:?]
at org.openhab.binding.amazonechocontrol.internal.Connection.makeRequest(Connection.java:695) ~[?:?]
at org.openhab.binding.amazonechocontrol.internal.Connection.queuedExecuteSequenceNode(Connection.java:1621) ~[?:?]
at org.openhab.binding.amazonechocontrol.internal.Connection.executeSequenceNode(Connection.java:1582) ~[?:?]
at org.openhab.binding.amazonechocontrol.internal.Connection.executeSequenceNodes(Connection.java:1651) ~[?:?]
at org.openhab.binding.amazonechocontrol.internal.Connection.executeSequenceCommandWithVolume(Connection.java:1527) ~[?:?]
at org.openhab.binding.amazonechocontrol.internal.Connection.sendVolume(Connection.java:1474) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]
2020-08-21 21:10:38.894 [WARN ] [mazonechocontrol.internal.Connection] - Unable to wait for next call to https://alexa.amazon.com/api/behaviors/preview
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method) ~[?:?]
at org.openhab.binding.amazonechocontrol.internal.Connection.makeRequest(Connection.java:695) ~[?:?]
at org.openhab.binding.amazonechocontrol.internal.Connection.queuedExecuteSequenceNode(Connection.java:1621) ~[?:?]
at org.openhab.binding.amazonechocontrol.internal.Connection.executeSequenceNode(Connection.java:1582) ~[?:?]
at org.openhab.binding.amazonechocontrol.internal.Connection.executeSequenceNodes(Connection.java:1651) ~[?:?]
at org.openhab.binding.amazonechocontrol.internal.Connection.executeSequenceCommandWithVolume(Connection.java:1527) ~[?:?]
at org.openhab.binding.amazonechocontrol.internal.Connection.sendVolume(Connection.java:1474) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]
I removed the previous jar file from the addons folder and Amazon Account thing in paper UI
Then added the latest 2.5.8 and reset OH.
Added an Amazon Account using the inbox (make sure it has a different id)
Reset OH (might not be needed)
Signed in with two factor authentication at http://openhab:8080/amazonechocontrol/
All my Amazon devices were then found
I then updated my default.items file with the new thing id and restarted OH
I’ve not stored any jar files in the addons folder, I installed the 2.5.8 jar via karaf using bundle:update with the jar link provided above. Hope, that’s no important difference.
What did you do to reset openHAB? I did a reboot of the Raspberry which runs openHAB.
I’ve set up my Amazon account using a things file:
I restart the OH service with sudo systemctl restart openhab2.service
No need to restart the Pi
The things were found automatically when the Amazon Account re-connected but the id changed so I updated the items file amazonechocontrol:echo:**Account-Id-to-change**:serial number of device
The issue was giving the thing a new id. I did not even get a 2-factor-auth-dialog – the “regular” auth dialog came up. After login the connection was properly established.
The Echo things as well as the Account thing are now shown as online again and TTS works as expected!
Hello all,
with the 2.5.7 version of the binding, i can make an annoucement to my echo spot which is showing in the display (no speaking). with 2.5.8. and 2.5.9 versions of the binding this does not work anymore…nothing happens…no error in the log…
can anybody confirm this or have an idea what has changed in the binding?
Just delete your account thing and rediscover then make sure you use a new thingID - then change the gateway on your binding discovered things and your items file - done
I have been battling this same issue. I have finally got a new device ID and updated my assets to reflect that. Now when I send TTY to the echo instead of making an announcement it is receiving a message. The ring flashes yellow and you can ask for it to read the message. - This is not how it used to work. It would just announce whatever I sent it. - Anyone else having this issue?
Also, my Alexa has lost all of my devices, I think that is a separate issue but I will have to find the solution to that too.
Im quite new to OpenHAB ans like what I have done already.
I have added in my Amazon account and it has auto discovered 4 firesticks in my inbox.
These are in a unkown - state not found in paper UI. Im looking for a step by step guide to add one and then follow for the rest. Is there one anywhere?
My Amazon Echo Control Binding suddenly stopped working.
The account thing stays in state COMMUNICATION_ERROR with additional Info POST url 'https://api.amazon.com/auth/token' failed: Bad Request
Anyone also faced this and has a solution ???
Was running openHAB 2.5.4 and now tried latest 2.5.9 SNAPSHOT.
EDIT: Found the solution myself by resetting the account via KARAF console.
All Things are back online again.
To resolve login problems the connection settings of an account thing can be reset via the karaf console. The command amazonechocontrol listAccounts shows a list of all available account things. The command amazonechocontrol resetAccount <id> resets the device id and all other connection settings. After resetting a connection, a new login as described above is necessary.