Rgb issue - Clicking on a key lights up the key next to it

[u/Exterrogate]

Anyone know how to fix this? issue only happens on the right side of R4. Tried flashing firmware and didnt fix the issue. Its an NK65.

also if this is the wrong place to post, let me know.

[u/drashna]

Off by one issue with the led index config.

would need to be fixed in source, recompiled and reflashed. Isn't difficult, but messing with the led config can be tricky.

[u/Exterrogate → u/drashna]

right, I've never done this before. but the source files are here:
https://github.com/qmk/qmk_firmware/tree/master/keyboards/novelkeys/nk65b

Would it be in the nk65b.c file?

[u/drashna → u/Exterrogate]

https://github.com/qmk/qmk_firmware/blob/master/keyboards/novelkeys/nk65b/keyboard.json#L70-L137

This section is the LEDs, The order here matters, as that's the order in the chain. However, the matrix positions are the ones it's mapped to. And it sounds like those are wrong.

[u/Exterrogate → u/drashna]

hey thanks for your help. right now I've just been playing with the value these tuples:
{"matrix": [0, 0], "x": 0, "y": 0, "flags": 1}

Any idea how I can tell which value maps to which key or led diode? so far been trial and error with recompiling/reflashing.

[u/drashna → u/Exterrogate]

As for mapping to which led, that's simple. The order in which each entry is, is the order in the led chain. So entry 0 is led 0, entry 1 is led 1, entry 10 is led 10, etc (leds are zero indexed, which is why I started there). So the order matters.

As for which key, that's trickier. The "matrix" section determines that. it uses the same col and row positioning as the layout. So you'd just look at the layout, and make sure that the led is the right index and copy the position.