Create knowledge base¶
The Naya Create is a split ergonomic keyboard: two halves, each with its own USB-C port, Bluetooth radio and firmware, and a module dock on each inner edge that takes a Touch (touchpad), a Track (trackball) or a Tune (dial with a touch surface and haptics); a Speedlink dongle came in the box DOC12. The left half is the central that holds the keymap and talks to the host; the right half reaches it over a Bluetooth link between the halves MEASURED (owner's board, 3.41.0, 2026-09). This site documents its hardware, wire protocol, firmware, storage, recovery and host software, from our own measurements, static reading of the vendor's released software, and public filings.
Naya B.V. has ceased operations and no longer supports the Create. The naya.tech domain now belongs to another company, so this site never links live naya.tech pages: every vendor web page is cited through an archived copy (Wayback Machine), or not linked at all.
Writes can brick or wedge a board
Every write on this protocol takes effect at once and persists; there is no commit and no undo.
A firmware flash can leave a half in its bootloader, 30/10ca wipes the keymaps, some settings
and records stop every key or darken the board, and firmware 3.28.7 wedges on any write of three
frames. Read Recovery and the
never-send list before you send anything that is not a
read, check the firmware of both halves first (fe/1002), and make first attempts on a board
you can afford to lose.
Start here¶
- Overview: the Create and its family, how the pieces connect, the versions.
- Transport: the frame, the checksum, addressing, and the byte convention every protocol page uses.
- Command map: every known command by category, with its params and reply.
- Recovery: a dark board, a wedged half, a half stuck in its bootloader, lost bonds.
- Tools: OpenFlow, nayactl, Create Companion, create-legacy-firmware and the recipes.
How to read the evidence¶
Every fact that is not common knowledge carries a tag, and a footnote names its source.
| Tag | Meaning |
|---|---|
| MEASURED | observed on a real board; the firmware and date are given, for example "on 3.41.0, 2026-09-20" |
| STATIC | read from the vendor's released software: NayaFlow, NayaCore, the firmware images |
| DOC | vendor documents, manuals, FCC and ISED filings, Kickstarter updates, release notes |
| INFERRED | our reasoning; the reason is given |
| REPORTED | a third party states it and we have not verified it; the source is named. "Raw data checked" means we decoded that party's own published data and it agrees |
| OPEN | unknown; each one links to its row on Open questions |
Unless a page says otherwise, MEASURED means measured on the owner's boards: a daily-use board on 3.41.0, a donor board on 3.28.7, and a board flashed between 3.35.4 and 3.41.0.
Versions are written 3.41.0 (keyboard) and 2.3.3 (module); the four-part form a half reports on
the wire is explained once, on Versions. Byte strings are lower-case hex
with spaces, commands are named category/command (for example 30/1004), and a params or reply
string starts with the flag or status byte: the convention is declared on
Transport. An acknowledgement proves the keyboard parsed a
frame, not that it applied it: read back what you write
MEASURED (owner's board, 3.41.0, 2026-09-07).
Section map¶
| Section | What it covers |
|---|---|
| Product | Overview of the family and its versions; the vendor manuals, cited by version |
| Hardware | Board inventory, the keyboard half, module dock, Tune, Touch, Track, Speedlink dongle, power and batteries, layout and positions, regulatory records and the parts list |
| Open source modules | Overview: homemade modules for the bays, with their repositories and build guides (a placeholder; none published yet) |
| Connectivity | USB identities and ports, Bluetooth hosts and GATT, and the split link between the halves |
| Wire protocol | Transport, command map, keymap, layers, LEDs, settings and timing, modules, module fields and differences by firmware |
| Firmware | Image format and signing (images), the bootloader, every version, the measured flashing procedure, module firmware and the ZMK lineage |
| Storage | The flash layout, what survives what, and the factory reset command |
| Recovery and troubleshooting | A symptom-to-recipe recovery cookbook with safety levels; troubleshooting, vendor bugs by firmware and the never-send list |
| Host software | NayaFlow and NayaCore, app data, the release history and the disassembly method and results |
| Tools | Overview of community tools, tested Python and JavaScript recipes, and platform notes |
| Reference | Open questions with how to settle each, the glossary, and about |
How this knowledge base was built¶
From live work over USB on the owner's boards (reads, writes, captures of NayaFlow, firmware flashing), static reading of every NayaFlow release, the FCC filings, the vendor's manuals and release notes, and the public work of nayactl, createflow-dongle and Create Companion. Every fact first reported by another project was then checked against our own material where that was possible. About describes the methods, the sources, the credits, the license (pages CC BY 4.0, code snippets MIT) and how to send a correction.
Sources¶
-
Naya Create User Manual Version 1.1.0 (vendor PDF, 2025-11-10); see Manuals. ↩
-
Kickstarter campaign page, naya-create/naya-create (2023). ↩