-
Notifications
You must be signed in to change notification settings - Fork 6
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
will the pi 3 a+ work? #7
Comments
I don’t think it is a Pi issue. Did you use mastersetup script to get everything configured or did you do it manually? Often times these type of onboarding problems can be traced back to the only manual part of the setup process, which is the profile definition in the Developer Workspace. Be 100% certain that you didn’t deviate from the config guide and double check that the keys you entered don’t have any typos. |
i modded out the board check in your mastersetup and SoftApConfig scripts so it would work |
I had the same issue. I was launching the QR code from the directory. I launched it from the mastersetup and it worked. Maybe that's it? |
Have you gotten things working OK? If you can confirm that you have your 3a+ working, I'll add the model number to the supported list. Just let me know what the model is. Thanks. FYI, one thing that I've discovered recently is that the path you take in the mobile app can make a difference if your QR code is even recognized. I've experienced cases where if you take the path of Add device, then immediately 'Scan QR code' it won't work. But if you - instead of selecting the Scan QR code from the Add device page - select the 'By device type' tab, scroll to the bottom to find 'My Testing Device' (or so it is listed for me), and then proceed through THAT path, then the QR code will be recognized. |
just a quick question to see if its already known before i spend time on it. will source different board if needed.
The text was updated successfully, but these errors were encountered: