-
Notifications
You must be signed in to change notification settings - Fork 784
autoupdate #1194
Comments
Yes, your summary is more or less correct. Note #595 - in this context, we can discuss that by default the auto-update should be set to off for a channel and that a binding can decide for certain channels that it should be turned on. Does that make sense to you? P.S.: Isn't the forum a better place for such questions? |
Will add a topic there this evening. |
Does this mean I didn't answer your question in total? |
I don't know, perhaps. |
I am a little bit indecisive about the autoupdate bundle.
If I understand it correctly it updates the state of an item if a command is received (and it is assignable).
If the bundle is activated all items are updated (default = true).
Someone could implement an AutoUpdateBindingConfigProvider to prevent that for special items.
If I use an UI and send a command to an item, the thing handler for the thing that channels are linked to that item receive that command.
Now it is up to the binding to execute the command (perhaps delegate something to the device) and if a channel is updated, the binding calls updateState.
The framework will update all linked items.
Is that correct?
If e.g. the command is dropped by the binding and so no state is updated, the item that is linked to the channel does not contain the correct state.
What is the use case of the autoupdate bundle? For demos and items that are not linked to channels?
But in this case I would prefer a default of false and someone could activate that for some bundles.
Perhaps someone could give me some more informations about that bundle.
The text was updated successfully, but these errors were encountered: