Yes, if you search in recent topics, you will find that the Amazon Echo Control binding is broken for some of the users. Apparently Amazon is deploying a change of’ API.
@miazza multiple users confirmed that Amazon’s service works as before (might need a disable/enable of the bridge) can you confirm this issue can be considered fixed?
That is very unfortunate. Could you share your configuration?
Are you able to upgrade to openHAB 5 and use the bundled amazonechocontrol binding ? This would make it easier to troubleshoot and work on a potential fix.
JFTR could you restart openHAB? There have been reports, that for some, the binding came back online today, only after a full openHAB restart.
Thanks, will look into it, thanks for the confirmation. Please provide details when you have the opportunity, it might help to further track this down.
Hi all. Sorry it took some time but I was on holiday till the end of august.
I made two fresh reintall of openhabian 5.0 and at the second attempt I restored a backup from 4.3 and suddenly all the smrthome devices are now recognised and working.
The only issue now it that I have all things doubled becasue all the things already installed from the backup are now also discovered by the binding.
I guess the only solution is to delete all smarthome things and create new things form the new discovery.
Anyhow the issue of this topic is solved (even if I do not know how) and the topic can be closed.