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
This applies to sync_all, refresh_all, join_all and any others
I think our initial thought had been that these messages would be cached for battery devices, but that doesn't seem to work out correctly. I have to revisit why I concluded this isn't working, but the solution was just to skip battery devices in the all commands.
Edit
I remember why this is an issue again.
The command sequence used for the *_all commands runs sequentially. When it hits a battery device, the entire sequence halts until that device wakes up. This isn't ideal as the user doesn't get to see the command run to completion. The command could take ages to run to completion or never happen.
Alternatives
The only alternative I can see are to fire off each request the the battery devices without using a sequence assuming they are asleep.
This isn't ideal as if they are awake the commands will get sent and could collide with each other.
I think they best answer is for the user to call these commands on each battery device as needed.
The text was updated successfully, but these errors were encountered:
This applies to sync_all, refresh_all, join_all and any others
I think our initial thought had been that these messages would be cached for battery devices, but that doesn't seem to work out correctly. I have to revisit why I concluded this isn't working, but the solution was just to skip battery devices in the all commands.
Edit
I remember why this is an issue again.
The command sequence used for the
*_all
commands runs sequentially. When it hits a battery device, the entire sequence halts until that device wakes up. This isn't ideal as the user doesn't get to see the command run to completion. The command could take ages to run to completion or never happen.Alternatives
The only alternative I can see are to fire off each request the the battery devices without using a sequence assuming they are asleep.
This isn't ideal as if they are awake the commands will get sent and could collide with each other.
I think they best answer is for the user to call these commands on each battery device as needed.
The text was updated successfully, but these errors were encountered: