-
Notifications
You must be signed in to change notification settings - Fork 401
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
[Friend V2] Friend uses NFC for pairing ($500) #568
Comments
I want to take this task, need a little more information, do I also need to add NFC connection functionality to the Friend Firmware or just on Flutter App. |
Is there a particular NFC antenna we should use? |
Not working on this but iOS does not support NFC (OOB) pairing last I saw |
Submitted initial PR #610 We can make iOS and Android pairing work using App Links which will pickup on the URL link and pull into app and start pairing, otherwise you end up on website with a lost and found style message and setup instructions. This is how most airtags etc work in the easy way. |
We are missing antennas on devices so this is also something that needs to be resolved, but will not need code/pin/overlay change for that. |
This is a partial resolution to #568 - My thinking is we can use "app links" in flutter for Google and iOS based on the friend website. This is how airtags etc all work, it also means you can do a "found" or setup instructions if it dose not go to the site. Issue is there is no NFC antenna on V1 or V2, so I will solder one on once Im back in Sydney or someone has one to test they can give this a spin. Once reviewed I can close out the additional changes.
NFC feature (firmware) completed. #610. App side will be developed later. |
Is your feature request related to a problem? Please describe.
I want to be able to pair my Friend by using NFC instead of bluetooth discovery.
Describe the solution you'd like
Connection, reconnection logic should remain the same, but the devices list should simply include the id of the device you NFC to.
The text was updated successfully, but these errors were encountered: