<\/p>\n
The short version: By changing the USB product ID<\/a> in a JSON<\/a> file for a similar keyboard, to that, for example, of a Keychron V6 Ultra 8K<\/a> ‘ISO<\/a>‘, it is possible to change keymappings, record macros, and execute macros from Via<\/a> for a ZMK<\/a>-based Keychron keyboard, including using the so-called standalone version of Via<\/a>!<\/p>\n The underlying reason is that Keychron has implemented the Via protocol for their ZMK<\/a>-based keyboards.<\/p>\n Example: Start JSON file: For V6 Max ISO<\/a> (from this page<\/a>). It has the exact same physical key layout as the V6 Ultra 8K ‘ISO’.<\/p>\n The first three lines:<\/p>\n The USB product ID for V6 Ultra 8K ‘ISO’ is 0x0C61 (it can, for example, be found in<\/a> the operating system somewhere). Thus, change it and the name, to:<\/p>\n But it isn’t sufficient. Even for a keyboard with the exact same physical key layout, there are differences, which must be expressed in the JSON file.<\/p>\n Compared to a QMK-based keyboard, there is a shift in some key positions, e.g., for the four extra keys above the numeric keypad.<\/p>\n Example 1: If a key is mapped (in Via) to the first in that group of four (according to the V6 JSON file\/QMK keymap), activation requires to use the key two to the right, the third key in that group of four…<\/p>\n Example 2: If a key is mapped to the fourth (last) in that group of four (according to the V6 JSON file\/QMK keymap), activation requires to use key 6 on the numpad<\/em><\/strong>(!) It is far away from anything that could be explained by a simple shift in the key order (the two keys are swapped).<\/p>\n Perhaps it is due to a keyboard firmware bug? That was tested with version 1.0.1<\/a>\/2025-11-28 (other notations are “1.01” and “1.1”) of the V6 Ultra 8K ‘ISO’ keyboard firmware. There is currently a version 1.0.2, but I haven’t tested it yet.<\/p>\n Order of keys: Vertical keys:<\/p>\n There isn’t any<\/em><\/strong> consistency between Keychron keyboards if a vertical key belongs to the upper or lower row when it comes to the key order<\/em><\/strong>. Thus, the original JSON file may not reflect the actual key order for the ‘Ultra’ keyboard. Or in other words, it is easiest to choose a JSON file to clone and change that has the same key order.<\/p>\nBase change: USB identity<\/h2>\n
\r\n "name": "Keychron V6 Max ISO Knob",\r\n "vendorId": "0x3434",\r\n "productId": "0x0961",\r\n<\/pre>\n
\r\n "name": "Keychron V6 Ultra 8K ISO",\r\n "vendorId": "0x3434",\r\n "productId": "0x0C61",\r\n<\/pre>\n
JSON files blues<\/h2>\n
ZMK blues<\/h2>\n
JSON files blues<\/h2>\n
\n