Skip to content

Conversation

@interfect
Copy link

This should fix #575 and also fix #576.

At least for the boards I have and a local serial connection. Other boards may need to be fed data even more slowly, and config restore over the mesh really can't avoid handling a lost packet and either resending it or knowing to fail the transaction.

# When config restore can handle and recover from dropped
# packets, or rate-limit based on acknowledgements, we can
# remove this.
time.sleep(2.0)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like a very heavy change since it'll apply to all writes on serial and TCP both, and not just configuration. Would it work to increase the sleeps in the handling for --configure specifically (and perhaps --export-config too if needed), rather than adding a forced delay to all interactions with the radio?

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

Successfully merging this pull request may close these issues.

[BUG]: --configure not effective with .yaml and some options [Bug]: export -import function not include some parameter

2 participants