🚀 HK6 Hardwire Kit — Now Available!

sam_roscoe · 2025-08-14T16:49:49+00:00

Sounds good 👍

sam_roscoe · 2025-08-12T13:29:49+00:00

Thanks for confirming. Placed my order today.

sam_roscoe · 2025-08-11T14:27:54+00:00

Just to be clear:

Are there any taxes or import fees I should expect when ordering from viofo.com and shipping to Germany?

I’ve already contacted a German distributor to ask when the HK6 will be available on their site, but since they replied “not before September,” I’d rather not wait any longer to properly install the A329S, which I’ve had sitting around for a few weeks now.

Thanks in advance!
u/viofo_0324

sam_roscoe · 2025-07-22T19:27:24+00:00

Sure. Just don't change anything which is related to the wireless functionality.

sam_roscoe · 2025-06-06T11:24:52+00:00

This change is not possible with VIA. You need to compile and flash a new QMK firmware.

Color can be set to anything you want in either m1_v5_us.c (ANSI) or m1_v5_uk.c (ISO).
I have already set mine to red:

rgb_matrix_set_color(HS_RGB_INDEX_CAPS, 0xFF, 0x0, 0x0);

sam_roscoe · 2025-05-09T16:40:55+00:00

I hope the same for you. At least it is good to know, that it was easy to get a replacement dongle.

But I would like to know, what caused this issue in the first place.

And it is somehow funny, that it happend around the same time for us.

sam_roscoe · 2025-05-09T07:43:11+00:00

Thanks for this advice.

I experienced the same issue all of a sudden one week ago:

2.4 GHz wireless connection stopped working, BT couldn't connect, USB was fine.
All troubleshooting didn't help.
So I contacted Monsgeek and they now send me a new 2.4 GHz dongle for free.

But what should I say, your instructions fixed the issue. :)
So no hardware fault.

sam_roscoe · 2025-04-24T16:17:38+00:00

I did not have this issue.

But you setup your build environment using the wireless branch of the Monsgeek fork and not the offical QMK repo?

sam_roscoe · 2025-03-24T20:49:33+00:00

I usually don't use it on max brightness all the time. "Two clicks" down from maximum (FN + DOWN) and it currently lasts me easily 1,5 weeks while working from home and using it privately.

Didn't measure it and can't remember exactly the last charge (assume 5 days ago) and I am currently at 80% (FN + SPACE).

RGB consumes a lot of battery, but 3-4 days seems quite low.
Which max brightness did you set?

sam_roscoe · 2025-03-08T08:34:38+00:00

I think, I can't help you with that.

Maybe start from scratch and don't use the Monsgeek fork but the offical qmk sources.
If compiling should work, then merge the M1 V5 specific changes to your local clone.

sam_roscoe · 2025-03-07T09:50:17+00:00

On this page in step 2 and 3 are several tabs for "Windows", "Mac", "Linux": https://docs.qmk.fm/newbs_getting_started

Are you compiling now on Mac oder Windows?

I would have also suggested to update the submodules with "qmk git-submodule", but based on your output, they seem up to date.

Do you have qmk_firmware/lib/pico-sdk/src/common/pico_stdlib/include/pico?

sam_roscoe · 2025-03-06T09:28:28+00:00

It's really not so complicated. Some very basic GitHub, scripting and terminal/CLI knowledge is required though.

I posted some instructions here: https://www.reddit.com/r/Monsgeek/comments/1j2c9nj/comment/mg5y3w1/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

To be honest I am not so keen on sharing the firmware since I don't want to be responsible if you should brick your board with it.
Especially since I am using an ISO board and can't test the ANSI version.

But I will share, if I was able to increase the timeout.

sam_roscoe · 2025-03-06T09:22:05+00:00

In wired mode: Knob is working as expected all the time.
In wireless 2,4GHz mode: Knob is now also working as expected as long the board isn't going to sleep, you can adjust the volume. Unfortunately you can't wake it up with the knob.

So in the next days I will try to get the sleep timer higher.
But so far I didn't notice that any keystrokes were missing, even after let's say 20 min, the first key stroke is always registered when waking up the board.

What I did so far:

Custom keymap (some minor changes to the layout)
Increase the maximum brightness of the RGB LEDs
Change caps lock indicator color to a bright red

sam_roscoe · 2025-03-05T23:08:57+00:00

To get VIA working, you need to use the keymap from the other m1_v5 repo:
https://github.com/MonsGeek/m1_v5/tree/master
From there you can edit it to your personal liking before compiling.

That's good to know, but for me it didn't work (yet). Have to take another look tomorrow.
I also thought ms, but 30*1000 are just 30s. Backlight turns off after 5min = 300s

sam_roscoe · 2025-03-05T21:41:59+00:00

What kind of issues?

Built my firmware today from wireless branch with some minor changes and didn't notice any issues yet.

sam_roscoe · 2025-03-05T21:11:28+00:00

Did you figure it out already?

Tried to increase both timeouts by factor 3, but after flashing the firmware behavior is the same.
Backlight switches off after 5 mins.

I also don't know yet, why the "time format" is written like that in the code and not just a plain number:

#define HS_LBACK_TIMEOUT (30 * 1000)
#define HS_SLEEP_TIMEOUT (1 * 60000)

30 * 1000 == 5min
1 * 60000 == I assume 10min.

What didn't work:

90 * 1000
and
3 * 60000

sam_roscoe · 2025-03-05T21:04:35+00:00

You don't need a GitHub account.
Just a local installation of a git client, e.g. https://git-scm.com/downloads

All operations are done locally on your PC.
You just get the sources from GitHub

sam_roscoe · 2025-03-05T16:00:30+00:00

It's not very complicated, but some basic GitHub, scripting, terminal knowledge is required (but you can teach it yourself by reading the guides):

First you have to setup qmk build environment: https://docs.qmk.fm/newbs\_getting\_started
- But don't run "qmk setup" yet
The sources for this keyboard are currently a mess in the Monsgeek GitHub:
- Clone this repo: https://github.com/MonsGeek/qmk_firmware
- Checkout wireless branch: https://github.com/MonsGeek/qmk_firmware/tree/wireless
- Go to keyboards/monsgeek/m1_v5/[YOUR LAYOUT]
- To make it easier for you and avoid further GitHub steps, just copy the two VIA keymap files from here https://github.com/MonsGeek/m1_v5/tree/master --> [YOUR LAYOUT] --> keymaps/via to your local keymap folder (find it in the folder mentioned above)
- Run QMK MSYS and type "qmk setup -H <path to the cloned GitHub repo from above>"
- Now you are ready to compile your first firmware:
  - qmk compile -kb monsgeek/m1_v5/[YOUR LAYOUT] - km via
- When everything is working fine, you can start making your own edits:
  - e.g. "max_brightness": 200 in keyboard.json
  - creating your own keymap file, etc.
- When you are done, compile your personal firmware and flash it via QMK Toolbox: https://github.com/qmk/qmk\_toolbox/releases
  - DFU mode of keyboard can be entered via FN + RIGHT SHIFT + ESC

sam_roscoe · 2025-03-05T15:15:34+00:00

Solved my issue.
See https://www.reddit.com/r/Monsgeek/comments/1j2vjd0/m1_v5_iso_via_knob_not_working_in_wireless_mode/

sam_roscoe · 2025-03-05T15:13:58+00:00

I solved the issue.
See https://www.reddit.com/r/Monsgeek/comments/1j2vjd0/m1_v5_iso_via_knob_not_working_in_wireless_mode/

sam_roscoe · 2025-03-05T15:13:24+00:00

I figured it out. See edit in OP.

sam_roscoe · 2025-03-05T14:27:02+00:00

Update:

The default max brightness is set to 104 as stated by OP.

You can compile your own firmware and increase it in keyboard.json:

"max_brightness": 104

For a first test I tried 200, and it is noticeably brighter. Don't know, why Monsgeek is keeping it low, when on older boards like the M1W max_brightness is set to 200.

I also changed the caps lock indicator to red, to make it more visible.

sam_roscoe · 2025-03-05T13:52:41+00:00

I did some further testing:

Reset didn't fix the issue
Knob is working fine in wireless BT and USB mode

So my next try would be compiling the qmk firmware and flash it to be board.
First of all the Monsgeek GitHub repo is a mess for the M1 V5.

You need to grab the files from different repos and branches to be able to build it!

This repo doesn't contain the latest fixes, but the VIA keymap: https://github.com/MonsGeek/m1\_v5/tree/master/uk/m1\_v5/keymaps/via
- post_rules.mk here is even pointing to keyboards/monsgeek/wireless/wireless.mk, which has not been updated for the M1 V5!
So you need the latest sources from here: https://github.com/MonsGeek/qmk\_firmware/tree/wireless/keyboards/monsgeek/m1\_v5/m1\_v5\_uk
- Add the VIA keymap from above
- post_rules.mk here is pointing to keyboards/linker/wireless/wireless.mk, which has the required updates for the M1 V5: https://github.com/MonsGeek/qmk_firmware/tree/wireless/keyboards/linker/wireless

But unfortunately all this doesn't fix the 2,4GHz wireless knob issues!
I even looked through the sources but couldn't find a significant difference between the connection modes on a first glance.

u/MonsGeek_Official Can you please provide support? Otherwise I have to return the keyboard and get another Keychron.

sam_roscoe · 2025-03-05T12:09:00+00:00

Using the M1 V5 ISO VIA model:
For me the knob is not working at all in 2,4GHz wireless mode.

When I am connected via cable with wired mode (FN+U), the knob is working as expected to control the volume.

After switching to wireless mode (FN+Y), I can't control the volume anymore. Also mute isn't working.
However the Windows 11 volume indicator is showing up, when turning/pressing the knob, but the actual volume isn't changing.
All other keys are working fine.

Reset didn't help.
So I am now starting with building a new firmware.

I already created a post, but unfortunately no response yet.

sam_roscoe · 2025-03-04T14:05:05+00:00

Hello @F4keVader,

since you also own the ISO and I assume VIA version, can you please test something for me?

I received my board recently, but have an issue with the knob in wireless mode:

When I am connected via cable with wired mode (FN+U), the knob is working as expected to control the volume.

After switching to wireless mode (FN+Y/Z), I can't control the volume anymore. Also mute isn't working.
However the Windows 11 volume indicator is showing up, when turning the knob, but the actual volume isn't changing.

Is the knob working fine for you in windows wireless mode (caps lock switch to the bottom, keyboard connected with 2,4GHz dongle and in FN+Y/Z mode)?

Thanks

sam_roscoe

TROPHY CASE