-
Notifications
You must be signed in to change notification settings - Fork 283
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
Add a Multiple Device Troubleshooting Section #755
Conversation
- Add information / tips to help with: - Connection issues to multiple devices - Pass more parameters to notify callback function Fixes #754
This seems like two unrelated problems, so I would expect two separate sections in the docs.
I'm wondering if we should fix this in code instead of "fixing" it in documentation. See my previous comment at #754 (comment). |
I opened #759 to discuss this separately. |
My goal was not to "fix" here, but to possibly save someone the hours and hours this cost me until the better action, something like #759 is complete. It's not very clear, are you interested in improving the docs here or do you want to leave this not addresses and just fix the API to handle this? Your response is not very clear and easy to interpret to action(s). |
OK, I will try again.
These are two unrelated issues, so combining them into one troubleshooting section seems like it would make it harder to find the answer for one or the other.
There is no debate about this issue. Having a troubleshooting section that explains that you should use a separate
I don't have a strong opinion one way or the other if we include this now or wait to see what the resolution of #759 is. But if we include it now, it should be a separate section from the scanning issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for updating. I just have a few suggestions.
Thanks! |
Fixes #754