you got it 
Could be, but here it is identical on Chrome desktop too.
we did see other interface elements toggle back and forth like this before waiting for the final feedback of the actual device (not sure which but they were actual switch toggles ). because of that timing issue people kept toggling and ofc that lead to the incorrect outcome…
all I am saying is, this could actually be considered a frontend issue rather than a backend.
otoh, if that cooldown doesnt hurt performance, and it helps syncing these thermostats that would be good too.
we should draw attention to the precision issue too though, and again ask for user configurability. I remember Frenck btw discussing this on the exact device. So maybe just an oversight
btw I just found the custom:numberbox-card which has a configurable precision and seems a bit more modern and configurable that simple thermostat
- type: custom:numberbox-card
style: |
card_mod:
style: |
ha-card .info {
font-weight: bold;
}
entity: climate.voorkamer
service: climate.set_temperature
param: temperature
state: temperature
min: 5
max: 21
step: 0.5
secondary_info: >
Actueel:<b style="color:green"> %climate.voorkamer:attributes:current_temperature </b><br />
Preset:<b style="color:green"> %climate.voorkamer:attributes:preset_mode </b><br />
Mode:<b style="color:grey"> %climate.voorkamer:attributes:hvac_action </b><br />
combined with my own preset buttons results in something like
far from prefect yet, need some stylings to be changed, but quick test seems to work properly, and no UI feedback issues
