I'm surprised I haven't seen anyone mention this issue yet, but if you tap to change the temperature multiple times in quick succession, openhab will receive the temperature change from the first request and relay it back to the frontend and cause the temperature to bounce back.
For example:
Temperature is 70.
Increment to 71... increment to 72...
OpenHab receives 71 and sends this temperature back to the frontend
The screen shows the temperature bounce from 72 backwards to 71
In some cases I've even seen it bounce between 71<->72 stuck in an infinite loop.
@gulliverrr I'd like to hear your thoughts on how to handle this, but two solutions I see that could fix this:
Implement a debounce on the decrement/increment functions so that tapping the screen many times in a row only sends one event to OpenHab
On the OpenHab side when sending the event to change the temperature, also send an ID of the client the message originated from. If the client sees the ID of origin is itself it knows to ignore the message.
I'm surprised I haven't seen anyone mention this issue yet, but if you tap to change the temperature multiple times in quick succession, openhab will receive the temperature change from the first request and relay it back to the frontend and cause the temperature to bounce back.
For example:
In some cases I've even seen it bounce between 71<->72 stuck in an infinite loop.
@gulliverrr I'd like to hear your thoughts on how to handle this, but two solutions I see that could fix this: