-
-
Notifications
You must be signed in to change notification settings - Fork 98
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 support for pairing #13
Conversation
3 similar comments
2 similar comments
I paired it but when using the login ID a 503 was thrown. |
What does the URLs look like? |
|
Try adding 0x in front of the login id. I should make that more clear. |
All good now. I figured that you were adding the |
Good 👍 For some reason I decided not to do that. I use a regex to decide if the identifier is a HSGID or pairing-guid, which requires 0x. Then I just pass the id along. Guess it was simple that way. |
Should work by using atvremote: atvremote pair And then add the remote on the Apple TV. Default pin is 1234 (which must be correctly entered) and name is "pyatv remote". These settings can be changed with parameters to atvremote. Currently a pairing timer is set to 60 seconds, so the process must be finished within that time.
By doing this and using a handler, it is much easier to test and the application is also responsible of aborting stopping the pairing process. Later, maybe a callback based API can be added so the user can be notified when pairing is done.
879c81a
to
85dbb71
Compare
Should work by using atvremote:
And then add the remote on the Apple TV. Default pin is 1234 (which
must be correctly entered) and name is "pyatv remote". These settings
can be changed with parameters to atvremote. Currently a pairing
timer is set to 60 seconds, so the process must be finished within
that time.
NOTE: Before merging this, some work must be done with tearing down the webserver and zeroconf after the paring period is done. It currently leaks.