I have upgraded from 2.3 to 2.4 and after some troubles managed to get the Hue binding to work with Alexa again (using „Lighting“ instead of „Switchable“ - Switchable simply did not work at all).
I am using cheap 433 MHz switches that I switch on and off using a script launched by the old 1.x exec binding OR a 433MHz remote.
The switches do not provide any information on their ON/OFF State.
What changed since the upgrade/reconfiguration is that I cannot switch an item that has been switched „externally“ before (i.e. Using a 433MHz remote completely separately from OpenHab)
So turning on and off using Openhab and Alexa works fine, as long as I do not use the remote (which I sometimes need to do).
When an item is actually on but Openhab thinks it is off, it doesn‘t launch the off script when I tell Alexa to turn it off. I need to tell Alexa to turn on „again“ and then I can turn it off. (Or vice versa)
This has changed from previous behaviour, where it just fired the script regardless of Openhab state.
Is this a known phenomenon? Maybe intentional?
May this be due to the new Hue binding, due to the change to „Lighting“ or is it changed behaviour in OpenHab?
Is there any idea for a workaround? Maybe a simple rule?
Thanks for any hint!