Im using a slider for a air con set point, I can get it to display fine, but when I click the slider to a position, it changes to it correctly, then changes back to the original set point. I have to do this twice to make it stick? Any thought as to why? Odd
11:22:54.654 [INFO ] [smarthome.event.ItemCommandEvent ] - Item 'DaikinACUnit_SetPoint' received command 24
11:22:54.655 [INFO ] [arthome.event.ItemStatePredictedEvent] - DaikinACUnit_SetPoint predicted to become 24
11:22:54.655 [INFO ] [smarthome.event.ItemStateChangedEvent] - DaikinACUnit_SetPoint changed from 31.0 °C to 24.0 °C
11:22:55.199 [INFO ] [smarthome.event.ItemStateChangedEvent] - DaikinACUnit_SetPoint changed from 24.0 °C to 31.0 °C
It’s not unknown for bindings to unwantedly force a cached state onto your Item. I’ve no reason to suspect Alexa here, but you may as well eliminate that possible source.
Just make another Item with the same daikin channel (only) and see when that gets updated to a new value (if ever).
I know nothing about daikin binding or the behaviour of your device.
This is a polling binding, isn’t it? Do you ever get your expected status?
What you might like is a poll-after-command feature, possibly with adjustable delay.
You might be able to simulate that in rules, if the binding honours REFRESH commands to channels for an arbitrary poll.
Can you add a dirty rule hack…
Ie you issue a send command but the binding probably issues an ‘Update’
So you could create a rule that’s triggered on command to override it and post the update a second later?
Don’t know about the Daikin binding but may be a workaround for now