just a, perhabs silly, question about how to control a heating thermostat.
I could set the item (Homematic in my case) to number and set it in the sitemap as setpoint - then in the web ui my heating is shown with two buttons (one for up and one for down).
When I set the item as a dimmer and then use a slider in sitemap the sider is shown correct but the actual “level” (degrees in my case) is not shown.
How Could I combine the text and the slider?
In the screenshot I´ve attached you see on the right side the slider and on the left site the up/down buttons…
Thanks, now the slider is put to the correct position. Is there a solution to show the value like a “String” next to the slider? It should be like a combination of slider and string.
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
Autoupdate changes your Item to the new value.
Your binding changes it back to the old value a half second later.
The UI displays what it is told - not a UI issue.
Usually means the device responds to a command with it’s existing state, and then actions the command afterwards.
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.
Yes, the expected status after I do the command twice ie manipulate it via the slider. Sounds like @Paul_Smedley may have an idea as it may be binding specific
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