Pairing the joy-con on emunand and sysnand

ndeadly · Jan 2, 2026

I think the code i shared requires some additional synchronisation to work reliably, I can see that the "response" to the memory read command is actually the response to an earlier command because of an unexpected input report that came in. I only used this code to test a theory so I wasn't super concerned with its reliability. You could try running the script a few times and see if it gives any different looking output. You could also try removing some of the other commands during controller initialisation, I can't remember whether they're necessary or not. Lastly, you could try doing a few extra calls to response = controller.read_input()to make sure it's reading a potentially delayed response

Fyrus · Jan 2, 2026

ndeadly said:
I think the code i shared requires some additional synchronisation to work reliably, I can see that the "response" to the memory read command is actually the response to an earlier command because of an unexpected input report that came in. I only used this code to test a theory so I wasn't super concerned with its reliability. You could try running the script a few times and see if it gives any different looking output. You could also try removing some of the other commands during controller initialisation, I can't remember whether they're necessary or not. Lastly, you could try doing a few extra calls to response = controller.read_input()to make sure it's reading a potentially delayed response

Okay, I've tried a few more times and one with only the extra call

It seems the first part of the ltk doesn't change, the latter parts do
You can find that in this archive

Jereming · 2026-08-16T02:30:32+0100

is this still working? I found my switch emunand backed to introduction (red big Switch logo animation) and had to redo the initial setup again after I ran the script. Luckily my installed contents are intact it seems. However the controller connected in sysnand is not synced to emunand.

Post automatically merged: Today at 2:45 AM

impeeza said:
On Atmosphère 1.5.1 A feature was added to optionally mirror the bluetooth pairing database to the SD card (thanks @ndeadly).
This allows device pairings to be automatically kept in-sync across sysmmc/all emummcs.
This is opt-in, and can be controlled by setting: atmosphere!enable_external_bluetooth_db = u8!0x1.
When enabled, the pairing database will be synchronized to /atmosphere/bluetooth_devices.db.

first, turn off your console, then on your "SDMC:/atmosphere/config/system_settings.ini" file be sure you have ONLY A LINE with the text:
enable_external_bluetooth_db
and what that line is inside the [atmosphere] section

Be sure that line have the value u8!0x1 at end:
enable_external_bluetooth_db = u8!0x1

Delete the file "SDMC:/atmosphere/bluetooth_devices.db"

Then start one of your *NANDs, then go to HOS settings -> Controllers and Sensors -> Disconnect Controllers and keep X pressed.

Restart your console to the same *NAND and test/pair all your wireless controllers.

Turn off your console and start another *NAND then verify all your controllers are already synced

You have to take in account: if any of your *NANDs have firmware less than 13, when you boot that firmware the database will be trunk to the 10 first entries.

*NAND refers to SysNAND or EmuNAND booting with the CFW, if you boot without CFW (OFW) the database will not be synced.

Post automatically merged: Jul 22, 2024

@0bvious did worked?

Thanks! This worked!

Attachments

Well-Known Member

Artilleur Carmin

Attachments

Member

Similar threads

Popular threads in this forum