Submitted by radakul t3_119xekf in MechanicalKeyboards

Hey all,

Like many others, VIA was auto-upgraded on my machine (from 1.3.1 to 2.1.0) and the same keymap I had been using for several months suddenly no longer worked.

I opened a case with Keychron support (which is....slow, to say the least) and they actually linked me an archived blog post that contains several firmware files, as well as other .JSON keymap files.

I can confirm this JSON works on both 1.3.1 and 2.1.0 as well.

Many folks on GitHub are having similar issues with K8's and K6's asking VIA to make the 1.3.1 binary release available again on their repo, but they haven't done so yet. I found another repo who forked the releases and still has 1.3.1 available, for those who might need it.

I'm sharing this in the hopes that others don't run into the same issue that I did. Or maybe the community has a better workaround in place.

1

Comments

You must log in or register to comment.

AutoModerator t1_j9ohdv6 wrote

If you are posting a Review, Make sure you fully disclose any potential conflicts of interest such as whether you were sponsored for the product, received it for free, or sell similar products.

Guide posts should be novel to contribute to the community knowledge base - simple build / assembly videos should use photos flair, and reviews should use the review flair.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

ImproperEatenKitKat t1_j9qlsis wrote

This seems like something that could be avoided with the set-and-forget nature of QMK

1

radakul OP t1_j9qzacj wrote

I would agree. Unfortunately it seems that the upstream developers for QMK haven't yet accepted KeyChron for some reason or another (I saw mentions of it on github but don't claim to understand all of what was said), so until they do that we have to use the manual method

I asked KeyChron support and they said they have no plans for Keychrons definitions to get added upstream

1

ImproperEatenKitKat t1_j9r4y4e wrote

I haven't built a KeyChron yet, but I could've sworn they advertise QMK and VIA support

1

radakul OP t1_j9r56yg wrote

They do! And they DID have full VIA support until VIA updated to 2.1.0, which broke the keyboard definitions that worked on 1.3.1.

Thing is, it's not native support - you can't plug in your keyboard and get it automatically detected. You open via, plug the board, load the definition and THEN it works.

1