Closed falconws closed 5 months ago
I thought that triggering pairing is required on device before starting pairing, but after trying it on a keyboard I have, seems that unpairing of Apple device also tells it that it is unpaired, so it automatically switches to pairing mode. It will still probably be frustrating if you need to switch often, as you need to type a random pin on keyboard with every pairing.
About scripts - sleeps should not be needed, also I think connect will happen automatically after pairing, so no need to do it explicitly and no need to disconnect explicitly before unpairing.
@toy Thank you for your advice. I recognized the following.
--connect
and --disconnect
. Just need --pair
and --unpair
onlyIs that correct?
Yes, you just need variables for device ids/addresses and pair/unpair commands.
I can also suggest that maybe generating a 6 digit number for pin (instead of coming up with one or using a fixed one) will make it easier.
@toy Thanks. But Apple Magic Keyboard and Apple Magic Trackpad aren't need pin for pairing 😄 Thanks to toy. Solved my problem!!
Hm, Magic Trackpad doesn't have an option to display or input a pin, but all keyboards should require a pin for pairing and my old Apple keyboard does require one.
I'm glad that I was able to help
Magic Trackpad doesn't have an option to display or input a pin, but all keyboards should require a pin for pairing
Hm.. 🤔 Why Apple Magic Trackpad can pairing without pin?
Why Apple Magic Trackpad can pairing without pin?
It has no display or keypad, so it can neither display nor receive numeric input.
I am switching between a MacBook Pro 2017 (Ventura 13.6.6) and an M3 MacBook Pro (Sonoma 14.4.1) with a genuine Apple Magic Keyboard and Magic Trackpad. The script used is as follows.
pair.sh
unpair.sh
(Do I need sleep command?)
I run unpair.sh at the source and pair.sh at the destination. When pair.sh is executed,
and
are outputted and it does not switch over properly. Am I using something wrong? Any advice would be appreciated.