bad response from Command DYNAMIC_KEYMAP_GET_ENCODER about releases HOT 12 OPEN

I'm getting the same issue on the Keychron V6, 8 pairs of errors when saving the layout.

from releases.

Okay, so I found the discord conversation kamikazeedriver was talking about, and was able to fix the issue I was having.
Here is the link to the first message of the original conversation.

I'm not too familiar with driver stuff, but in my case, it seems like the PC inadvertently uses an unrelated driver called "Guillemot" to drive(?) the keyboard. This causes the error we're seeing (I think).

Steps I took

Diagnosis

1. Go thru the instructions to factory reset the keyboard, up to Step 7, putting the keyboard into DFU mode. (I'll use the V6 instructions, since that's what I have)
2. At this point, in QMK Toolbox, the keyboard should display as STMicroelectronics STM32 BOOTLOADER, but mine shows as Guillemot STM DFU Device.
   

Solution

To resolve the issue, we need to delete the Guillemot driver. I derived these steps from this Pimax forum post; funnily enough, it seems like they ran into the same issue we're having.

1. First, delete these two folders:
   C:\Program Files\Guillemot
C:\Program Files(x86)\Guillemot
2. Go to Device Manager and uninstall Guillemot STM DFU Device under Sound, video and game controllers. Make sure Delete the driver software for this device is checked.
   
3. Go back and follow steps 3 thru 7 of the Keychron factory reset instructions (unplug -> open QMK -> install drivers -> put keyboard in DFU mode)
4. If the driver was deleted successfully, QMK Toolbox should now display the keyboard as STMicroelectronics STM32 BOOTLOADER
   
5. You can now flash the keyboard and continue with the factory reset instructions.
6. At this point, I was able to save my layout in VIA without errors.

Hopefully this helps. Happy Halloween :)

from releases.

I am using a dock to connect my laptop to a monitor and ethernet etc, and I fixed this error by plugging my keyboard directly in my laptops USB ports instead of the dock.

from releases.

I'm also getting this plus another 19 errors.

Device: Keychron Q2
Vid: 0x3434
Pid: 0x0111

from releases.

Same problem with a new Q1, 16 errors. Web or Desktop doesn't matter and does not save the layout. I wanted to remap caps to left ctrl, does not work.

Command Name: DYNAMIC_KEYMAP_GET_ENCODER
Command: 20 0 0 0
Response: 255 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Device: Keychron Q1
Vid: 0x3434
Pid: 0x0107

from releases.

Same problem Q1, 16 errors

Command Name: DYNAMIC_KEYMAP_GET_ENCODER
Command: 20 0 0 0
Response: 255 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Device: Keychron Q1
Vid: 0x3434
Pid: 0x0107

from releases.

Same here with a Q2:

Command Name: DYNAMIC_KEYMAP_GET_ENCODER
Command: 20 0 0 0
Response: 255 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Device: Keychron Q2
Vid: 0x3434
Pid: 0x0113

from releases.

Same list of errors on a Keychron V6 with knob.

I've also noticed that on Lighting, the Rainbow Beacon, and all the settings after it, are the same.

My V5 works great, but this v6, I'm not convinced yet.

from releases.

Hey just want to add I have the same issue on a Keychron Q8.

It used to work like a few months ago, maybe a year ago, last time I edited it.
I tried using both AppImage and browser version using chromium

VIA-app-errors.csv

from releases.

I was able to fix my problem with a firmware flash, but I can't remember how I was able right now.
All I remember is after getting no assistance from Keychron, I joined their discord, and searched the comments for my problem.
One of the results was from one of the Keychron team saying to do something, which would allow me to install the firmware.
After installing the firmware, all was well.

from releases.

Hey just want to add I have the same issue on a Keychron Q8.

It used to work like a few months ago, maybe a year ago, last time I edited it. I tried using both AppImage and browser version using chromium

VIA-app-errors.csv

Ok I remember more about what happened.
So yeah, you do the firmware and that fixes the problem.
The only problem is, some people run into an issue when installing the firmware.

So first, for your keyboard, go here:

I did all this, but then on STEP 7, I kept encountering an error.
That was when I reached out to Keychron, but got no reply.

If you also encounter an error on Step 7. You'll know it because the yellow text in that window won't say what the keychron website says it should say.

So then I went to their discord, searched for the Error I was getting, and saw others had encountered it to, and one of them was answered by some Keychron team member about some utility or something you had to do.
I think it was uninstalling some driver that seems to affect many systems. Just search though, you'll find it.

Once I uninstalled that driver, everything worked fine, I was able to update the firmware, and use my keyboard like normal.
That was months ago.

from releases.

When I used my Keychron Q2, I encountered the same problem, but I was able to solve it!
I simply flashed the firmware by referring to this document.

from releases.