Skip to content
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

Open
erpadmin opened this issue Nov 28, 2022 · 5 comments
Open

will the pi 3 a+ work? #7

erpadmin opened this issue Nov 28, 2022 · 5 comments

Comments

@erpadmin
Copy link

just a quick question to see if its already known before i spend time on it. will source different board if needed.

@erpadmin
Copy link
Author

erpadmin commented Nov 29, 2022

the AP test works and the switch example ssid shows up when example is running but onboarding (phone side) sits at the Preparing screen (Press and hold power button for 5 seconds...)

eventually a timeout appears in the console output
image

@toddaustin07
Copy link
Owner

toddaustin07 commented Nov 29, 2022

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.

@erpadmin
Copy link
Author

i modded out the board check in your mastersetup and SoftApConfig scripts so it would work
ill go back through the config guide

@joecoolish
Copy link
Contributor

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?

@toddaustin07
Copy link
Owner

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.

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

No branches or pull requests

3 participants