Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distinguish between fast and slow device classes when doing optimistic value updates #3892

Open
AlCalzone opened this issue Dec 14, 2021 · 2 comments

Comments

@AlCalzone
Copy link
Member

We should distinguish between devices that do fast and device that do slow transitions and only do optimistic updates for fast ones.
This way, UIs could give immediate feedback about the state of lights but it would still be possible to wait for the slower ones like roller shutters.

Fast would be:

  • Lights without a specified transition time
  • Lights with a short transition time (< 5s for example)
  • Binary switches, etc.

Slow would be:

  • Motor control
  • Window Covering
@Nagskull
Copy link

Nagskull commented Nov 6, 2023

Hello,

Is there any chance that this change will be implemented in the foreseeable future? I have experimented with workarounds based on the predicted transition time, but they lead to erratic or much less responsive behaviors.

This change could be made easier, I guess, by simply letting users deactivate optimistic value updates manually, on a node-by-node or node-types basis. This way, there would be no need to update existing devices configuration files to specify whether they are slow or fast.

Thanks a lot for tour help!

@MaelDieudonne
Copy link

Sorry do I need to tag you @AlCalzone? Still hoping that one day this change could be implemented. Would be a game changer for me. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants