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

When many T2s are on LAN, yours might not be listed #743

Open
Frijol opened this Issue May 17, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@Frijol
Member

Frijol commented May 17, 2016

If you have ~15 or more T2s on the same Wifi and run T2 list, the command might time out before it gets to your Tessel.

Adding a timeout of 10 seconds fixed this

@johnnyman727

This comment has been minimized.

Show comment
Hide comment
@johnnyman727

johnnyman727 Aug 9, 2016

Contributor

The ultimate fix here might be to programmatically increase the timeout when lots of devices are detected. This is still useful for hackathon scenarios.

Contributor

johnnyman727 commented Aug 9, 2016

The ultimate fix here might be to programmatically increase the timeout when lots of devices are detected. This is still useful for hackathon scenarios.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment