You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the binding is restarted, or when the bridge thing is disabled and re-enabled, some windows may take 2..3 minutes for their position values to be updated. Specifically the first two responses to the GW_GET_NODE_INFORMATION_REQ message will return invalid position values.
Future
The position values should update faster.
Possible Solution
Perhaps call GW_GET_NODE_INFORMATION_REQ more frequently on start up
Or send a STOP command to the actuator on start up
Or use a new API call to fetch the position status on start up
EDIT: from manual tests it seems that sending a STOP command does the trick.
The text was updated successfully, but these errors were encountered:
Background
When the binding is restarted, or when the bridge thing is disabled and re-enabled, some windows may take 2..3 minutes for their position values to be updated. Specifically the first two responses to the GW_GET_NODE_INFORMATION_REQ message will return invalid position values.
Future
The position values should update faster.
Possible Solution
EDIT: from manual tests it seems that sending a STOP command does the trick.
The text was updated successfully, but these errors were encountered: