It's mapped as BGR, not RGB, in our hardware.
Previously when you set red it would show as blue and vice versa.
Signed-off-by: Daniel Schaefer <dhs@frame.work>
Currently QMK can only react to one LED per key.
This looks wrong on wide keys with multiple LEDs.
Only a proble on animations that react to keypresses.
Signed-off-by: Daniel Schaefer <dhs@frame.work>
Current error:
```
1s
Run trilom/file-changes-action@v1.2.4
/usr/bin/docker exec e94fda2c6b79f2a3fda6ad3973fb2452092507da89442d782b39afc8b41f24a4 sh -c "cat /etc/*release | grep ^ID"
Warning: Received event from pull_request, but also received a before(50eff5af7d) or after(8bd0db74a7) value.
I am assuming you want to use a Push event but forgot something, so I'm giving you a message.
Error: undefined
Exception: {
"error": "403/Unknown Error:HttpError",
"from": "undefined/Error",
"message": "There was an error getting change files for repo:qmk_firmware owner:FrameworkComputer pr:1",
"payload": "Resource not accessible by integration"
}
(node:128) UnhandledPromiseRejectionWarning: Error: {"error":"403/Unknown Error:HttpError","from":"undefined/Error","message":"There was an error getting change files for repo:qmk_firmware owner:FrameworkComputer pr:1","payload":"Resource not accessible by integration"}
at run (/__w/_actions/trilom/file-changes-action/v1.2.4/dist/index.js:1:19989)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:128) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:128) [DEP0018] DeprecationWarning: Unhandled promise rejections
are deprecated. In the future, promise rejections that are not handled
will terminate the Node.js process with a non-zero exit code.
```
Signed-off-by: Daniel Schaefer <dhs@frame.work>
Co-authored-by: Wolf Van Herreweghe <wolfvh@getupgamesofficial.com>
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: jack <0x6a73@protonmail.com>
User reported that CAPS lock Led state was inverted after soldering a LED to their board.
LED_PIN_ON_STATE defaults to 1, so just swap to low.
Flashed board and now CAPS LED reflects the actual state
