Amazon Echo SmartJ Binding Last Voice Command not working anymore

mjcumming · December 23, 2023, 7:19pm

Is the fix in the RC1 or do I need to download one of the JARs above?

jwiseman · December 23, 2023, 11:34pm

Hey Jan,

I’m 100% sure that this type → Echo Plus 4.Gen ← (the bigger size one that has zWave and Matter built in) does NOT work with the lastVoiceCommand consistently.

Here’s the unit I’m talking about

Living Room Echo ONLINE [Echo Living Room] Echo Plus 4.Gen

What can I provide you to prove there is an issue with lastVoiceCommand with Echo Plus 4.Gen unit types.

Best, Jay

J-N-K · December 25, 2023, 8:50am

Please all use addons.json only. I have merged all versions to one file. And please also disable “show incompatible addons” in the addon management section. You’ll get a wrong version otherwise.

Cplant · December 25, 2023, 9:57am

I have the same question and kind of lost track of the details of this thread. Is there a possibility to achieve the same near-real-time results on the lastvoicecommand-item again?

J-N-K · December 25, 2023, 11:31am

The latest SmartHome/J is the best you can get ATM.

Cplant · December 25, 2023, 12:15pm

Will this also be included in any future regular release of OH?

J-N-K · December 25, 2023, 1:41pm

Probably not. When I tried to re-integrate the http binding ([http] Improve binding by J-N-K · Pull Request #15376 · openhab/openhab-addons · GitHub), the reviewer decided that the channel-types of newly added channels need to follow the new openHAB naming scheme and have to be re-named. Since this is a breaking change for all users that already use these channels (which is not justified by any technical reason and there are tons of binding with “wrong” channel-type naming in the codebase anyway), I decided to decline that and closed the PR.

The amazonechocontrol binding would face the same issue, so I don’t think that will happen.

Cplant · December 25, 2023, 2:29pm

Sorry for asking a really dumb question here: Does this mean that the LastVoiceCommand is not expected to work again any time soon with any regular release of OH due to this being a breaking change to everyone else?

Larsen · December 25, 2023, 2:54pm

But that would be really sad if the latest version of one of the most important bindings (at least imho) is not anymore part of the OH-release.
I wouldn’t mind to re-link my items if the channels change. I think most (probably all) that use the SmartHome/J-version are quite skilled and don’t have a problem to re-link, too.
So please, please, release (what a rhyme). You did such a great job to realise this solution, it would be a shame if only the minority of this thread would/could use it.

Cplant · December 25, 2023, 2:59pm

sign. I guess I’m not the only one who uses the binding for precisely two things:

Switch on devices
Use the LastVoiceCommand-item to trigger all sorts of custom functions.

If the latter does not work anymore, and in case it’s as described (“breaking change” for the maintainer more severe than “one of two use cases not being functional anymore”) maybe there’s something else that can be done.

J-N-K · December 25, 2023, 3:17pm

You wouldn’t mind, I do. There is NO good reason to require users to delete, re-add, re-configure and re-link channels for all things just because myChannelTypeId changes to my-channel-type-id. It’s especially ridiculous if 50%+ of the binding-defined channel-types don’t follow the naming scheme and it’s some internal id (i.e. no user will ever have any benefit from that change). Therefore: no, won’t happen.

Cplant · December 25, 2023, 9:09pm

As someone who probably only understands half of the underlying root causes and discussions around declined PRs: Is there an alternative way forward hat brings back a working LastVoiceCommand-function?

Larsen · December 25, 2023, 9:31pm

We have the best working last-voice-command-function that is currently possible due to restrictions of the Amazon interface. It works well but needs triggering from openhab side.
But this binding does not get part of the official release due to changes of formal requirements. I still can’t believe that due to the importance of this binding for many users. Of course it’s possible to use the unofficial one but that feels awkward for openhab as the world’s best smart home platform

Cplant · December 25, 2023, 10:00pm

I assume having two versions in the official release isn’t an option either?

J-N-K · December 25, 2023, 10:36pm

The issue would be the same: the channel-types would not be allowed.

Lamerjack · December 27, 2023, 11:25am

At the moment on openhab 4.1 doesn’t work. But probably i have an old binding.
Whit 4.1 i have to use the beta or the normal.
There is a way to understand wich version of binding i have and wich one is the latest to understand that i have to update?
Thanks Enrico.

J-N-K · December 27, 2023, 12:08pm

Always use the version from the JSON 3rd Party Add-ons. Use https://download.smarthomej.org/addons.json as source and disable “Show incompatible add-ons” on the “Addon management” settings page (that’s not the “JSON 3rd Party Add-on service” settings page!). At this time it should be version 4.1.0 for openHAB 4.1, 4.0.2 for openHAB 4.0 and 4.2.0-SNAPSHOT for openHAB 4.2.

jpalo · December 28, 2023, 5:39pm

This is one of the reasons I define everything in item and thing files - updates such as this would be quick and easy.

J-N-K · December 28, 2023, 6:54pm

It would also be absolutely painless if rules would not be enforced just for the sake of the rule. As I said: if this would be the only exemption and there would be any benefit from that (apart from “looks better to the developer”), I would agree. But that is not the case here.

Larsen · January 1, 2024, 2:59pm

you maybe already noticed that the review-comments on github were now marked as resolved (thanks @laursen ).
So could you reopen the PR to get it into the release?