Skip to content

Added shield temper_dongle + BLE/USB toggle keys#72

Open
niiico69 wants to merge 2 commits into
OneDeadKey:mainfrom
niiico69:pr/bluetooth-dongle
Open

Added shield temper_dongle + BLE/USB toggle keys#72
niiico69 wants to merge 2 commits into
OneDeadKey:mainfrom
niiico69:pr/bluetooth-dongle

Conversation

@niiico69

Copy link
Copy Markdown

No description provided.

- boards/shields/temper_dongle: shield dongle autonome (central, 2 peripheriques, BT_MAX_CONN/PAIRED=7); keymap resolu vers config/temper.keymap
- zephyr/module.yml: board_root pour exposer le shield local
- build.yaml: 4 entrees dongle sur nice_nano@2//zmk (variante zmk requise pour BLE/USB sur ZMK recent), artifact-names distincts
- selenium.keymap: &out OUT_BLE/OUT_USB/OUT_TOG sur la couche FnMedia
- settings.h: prefs layout (hote AZERTY + emulation ErgoL, macOS)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

@Nuclear-Squid Nuclear-Squid left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks pretty good ! There are a couple of things I’d like to go over with you though. The main one is the firmware for the dongle itself. I trust that it works well, but I’d rather not having any custom board or shield in this repo, that way we can completely separate the concerns of the keymap from the electronics (while also providing the community hardware support that isn’t specifically for this project ^^).

What this entails, is that you create a new GitHub repository for your driver (you can fork the zmk-module-template repo for this), then add your repo to the list of imports Ækeynox does by editing the config/west.yml file.

If you want an example of this kind of thing in action, we’ve done this for the support of the Chocofi Temper some time ago : #58

Comment thread include/aekeynox/selenium.keymap Outdated
Comment on lines +116 to +118
&trans , &kp F1 &kp F2 &kp F3 &kp F4 &out OUT_BLE , &bt BT_SEL 2 &kp C_NEXT &kp C_VOL_UP &kp C_BRI_UP &kp SLCK , &trans ,
&trans , &kp F5 &kp F6 &kp F7 &kp F8 &out OUT_USB , &bt_sel1_clr H_J C_PP H_K C_MUTE H_L C_AL_LOCK H_SEMI PSCRN , &trans ,
&trans , &kp F9 &kp F10 &kp F11 &kp F12 &out OUT_TOG , &bt BT_SEL 0 &kp C_PREV &kp C_VOL_DN &kp C_BRI_DN &kp INS , &trans ,

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having all three of the output selection behaviors seems a bit redundant to me, as you can have the same functionality with just OUT_TOG or OUT_BLE + OUT_USB.

I guess we leave the choice to use whichever we want, but leaving empty spaces in the keymap helps the user make smaller adjustments later, if needed. I’m summoning @Ashenfae on this issue, as they own a BLE keeb (while I don’t).

@niiico69 niiico69 Jun 17, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated the PR, kept TOG in front of CLEAR

Import the temper_dongle shield from its standalone module
(niiico69/zmk-keyboard-temper-dongle) via config/west.yml, add the three
dongle/peripheral builds to build.yaml, and wire BLE/USB output toggles
(&out OUT_BLE / OUT_USB / OUT_TOG) on the Fn/Media layer.

The hardware definition lives in the external module so the keymap repo
stays free of custom boards/shields.
@niiico69

Copy link
Copy Markdown
Author

Done

@niiico69 niiico69 requested a review from Nuclear-Squid June 17, 2026 16:11
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

Successfully merging this pull request may close these issues.

2 participants