Open lsxfhao opened 1 year ago
Update on release 3.0.0: The error still exists, but the keyboard is recognized, and basic feature is usable. So far it's enough for me. I'm not using any light or RGB on my keyboard, but VIA seems very insistent to get the light config, which seems unnecessary.
Same here. Getting these errors on a crkbd/rev1:via when RGBLIGHT_ENABLE is not defined.
Everything works fine but the errors are annoying. Is there a way to fix this?
I have the same issue with my kbdfans kbdpad mark ii
Same here with both R2G and rev1
I don't really mind not having "good" rgb, but it would be nice for this to get fixed to get some nicer effects and control with via
Same here with a R2G. But i could find out that this is a missmatch between the compiled firmware and the crkbd.json of the via app. In this config it says "qmk_rgblight" but this feature is not active in the firmware for the corne. so i changed this setting to "qmk_rgb_matrix" and the error is gone.
Describe the bug When I use the app online/offline version, my corne keyboard is not recognized. I have error message in the console:
Also the error message in VIA error tab
This only happens after the major UI change of VIA. I can use the old one couple of weeks before.
To Reproduce Steps to reproduce the behavior:
Expected behavior Keymap recognized.
Screenshots Don't know how to upload.
VIA Version
Keyboard firmware VIA protocol 12
Desktop (please complete the following information):
Custom json definition?
Sanity checks
Additional context I can use the default via keymap from qmk, but I cannot use my own keymap. I have checked the rules.mk and config.h, the only change I made is add "#define DYNAMIC_KEYMAP_LAYER_COUNT 5" to get more layer. It was working before.