I don*t use amazonechocontrol, but maybe the key expired? or, even worse, maybe the API changed? So you would have to upgrade (minimum to OH3.4.5 as a first step - should be painless)
means that it is not supported ( at this moment ) at the amazon end.
If information is not made available by amazon/alexa/push messages it can not be shown in the binding.
Question would be if that is intended or by accident. This is something that you can ask amazon support.
Some of the problems seem to have vanished without any change, others persist. Unfortunately this seems to have been removed permanently. We are looking into ways to improve that.
@J-N-K Just to clarify, when you say âWe are looking for ways to improve thatâ, do you mean that you or other Maintainers have contacts at Amazon to reach out to for things like this?
It would be a huge shame if Amazon decide to permanently remove this feature. Iâve got Sonos Ones all over the house and I use the lastVoiceCommand hook to do all manner of funky things!
I see. I did attempt to contact Amazon via chat today, but spent an hour repeating that it wasnât an issue with my echo device. The rep simply kept telling me to power cycle my Sonos Ones to see if it fixed the problem
Will try again next week and hope to get through to the right person.
jwiseman
(Mr. Wiseman (OH 4.2 Snapshot on Pi4))
13
Hey Alex,
This is a lost cause; you would need to have a contact within the Alexa development department (which will be a worldwide development team is my guess). No C/S representative will ever be able to get to you to correct person nor will they even understand what your asking them.
If you really want to go down that route, look at LinkedIn.
I believe two things happened with this last voice command issue.
it was a security issue
they realized that other systems (like OH, Homekit, etc.) was using this field to trigger stuff externally from the Amazon eco system and they want everything to flow through their eco system.
How much delay is acceptable for lastVoiceCommand and lastSpokenText? I have a solution, but it currently has a 15 second delay between the start of the conversation (i.e. the detected wake word âAlexaâ) and the update of the channel.
The reason is that Amazon sends an event when Alexa starts recording something, but no event when the conversation ends, so the binding needs to actively request the activity record from the server. For me 15 seconds is a compromise that works fine, nearly every conversation (e.g. âWhat time is itâ - âIt is five minutes past eightâ) is shorter, but it does not produce a delay that is too large.
3 Likes
jwiseman
(Mr. Wiseman (OH 4.2 Snapshot on Pi4))
15
Iâm fine with a 15 second delay, itâs about triggering rules based on certain words/phrases said.
Iâd rather have a delay than it NOT working at all.
Those on openHAB 4 can try to download this file, uninstall the binding and then drop the kar in the addons folder. Please note that some Browsers rename .kar files to .mid during download, please make sure the file extension is .kar when dropping the file in the addons folder.
3 Likes
jwiseman
(Mr. Wiseman (OH 4.2 Snapshot on Pi4))
19
I upgraded to openHAB 4 so I could give this .kar package a go. Thank you for taking the time to put it together. Unfortunately I canât get it to work as you have described. There doesnât seem to be any change in behaviour i.e. lastVoiceCommand does not receive updates, even after 15s.
lastSpokenText was a new one for me, and I canât see it in the binding documentation (is it brand new?) âŠanyway, I added an Item for it but itâs not getting any updates either. Have I missed a configuration step?