So, keyboard.frame.work used to let me configure my keyboard. It worked great, and was fun to play around with and see the various lighting options (I use the clear/RGB keyboard and macropad). However, when I installed the most recent driver update pack, it seems to have broken that VIA connection, and it no longer shows up on that web utility.
I’ve tried reinstalling things as well as rolling back versions, but I’m leery of getting into the non-framework VIA controls because I don’t know how much of the setup is custom to this device and site. Obviously it’s not urgent, because it’s been a few months since that UI stopped working, but it would be nice to have that capability again.
What error(s) are you getting or what behavior are you seeing? A screenshot of the error(s) would be best.
Also, your OS, browser, browser version?
And if Linux, was the browser installed as a regular system package, snap, flatpack, etc. There can be permission issues sometimes with some.
It’s standard QMK/Via.
The only issue / reason we use FW’s locally hosted version of the Via GUI (keyboard.frame.work) is that the standard Via site doesn’t yet have the keyboard in it’s database, you’d have to sideload it.
I’m seeing no errors. As described, it simply no longer shows up on the Via GUI. It loads to the “authorize device” screen, but clicking that does nothing, and if I try to edit my keyboard, there is nothing available.
I am not running Linux. My usual browser is Vivaldi, which is a Chromium-based browser. It worked previously in this browser.
If I switch to regular Chrome, it does show up now (I swear it didn’t last time I was trying to make this work), but I’m curious why Vivaldi no longer connects.
It requires a browser with WebHID enabled. Sometimes chromium-based browsers screw up with their build & cause it to fail. Others have reported other chromium-based browser builds that should work but are broken. Here is a WebHID checker, webapicheck.com/apis/webhid-api
Ahhh that would be the problem, then! I can see other reports of WebHID having issues with the current version of my browser. Hopefully that dev team can get us a fix at some point, until then at least Chrome will let me talk to the keyboard.