New keyboard not detected in Via about releases HOT 33 OPEN

I've had this same problem (on macOS, at least).

from releases.

Hi there

I'm trying to get my custom board to work with VIA. The board uses a pro micro and runs on QMK fine.

For some reason, it seems that Via never detects the board, I'm not sure why.

• PCB config is there: https://github.com/LouWii/qmk_firmware/tree/ergomax-keyboard/keyboards/ergomax/rev1_right
• Keymap: https://github.com/LouWii/qmk_firmware/tree/ergomax-keyboard/keyboards/ergomax/keymaps/default_right_via
• Via config file https://github.com/LouWii/qmk_firmware/blob/ergomax-keyboard/keyboards/ergomax/via_right.json

I know the board has been flashed correctly with the new firmware, and I do see the correct vendor and product id in QMK toolkit HID device connected: LouWii Ergomax Right (1140:1202:0001)

I can load the config file fine in VIA. But it's not finding my keyboard. Tried unplugging-plugging while VIA is running. Tried rebooting with keyboard plugged in, launching Via, nothing.

My board does work in Via's key tester.

I'm out of ideas, not sure what's going on. Tried on Windows 10 and Linux Mint (Ubuntu distro).

Hello All,

I know this is way late but I had the same issue and found out what was going on. At first my keyboard would work in the key tester but wouldn't show up in the configurator. The problem is, VIA doesn't have a reference to the actual layout and matrix of your keyboard. To have full VIA compatibility, you need 3 files in the VIA folder in your QMK firmware. These files are:

Keymap - Needs to have 4 layers (first layer properly filled out and the other 3 can all be filled in with "KC_TRNS"
Rules - VIA_ENABLE = yes
"Keyboard".json - The file you need to create to allow VIA to view your layout

What you need to do is make the VIA .json file using the Keyboard Layout Editor. Everything required in the VIA .json can be found at https://caniusevia.com/docs/specification

Open up your browser and go to http://www.keyboard-layout-editor.com/
Create your layout and instead of inputting letters, numbers, and Mods onto the keys you will need to label each key to correspond with the Rows and columns in your pin matrix. First number is the Row and second is the column.
Example Below:

Once finished, download the .json and open it in a text editor. At the beginning of the text in the file is where you will want to start copying over and filling out the required information from VIA's site I mentioned earlier. When done, all of the original information that was in the text file originally should start after "keymap":

At the very bottom of all of the text add this:
}
}

Save the file and open up VIA. Go to the settings tab and turn on the "Design" Tab. Open the Design tab and click "Load". Select your new .json file and if you have done everything correctly your layout will show up in VIA. If you get an error VIA usually prompts what the issue is (you may have to troubleshoot).

If your layout does load then you can proceed to copy the .json file to the VIA folder in your QMK firmware. Compile the QMK firmware as you normally would and flash to your keyboard. Unplug and plug in your USB cable and open up VIA. Your keyboard should now show up in VIA (May take a minute).

I hope this helps some of you out as this is what fixed my issue and I haven't seen many guides on how to properly add VIA compatibility.

from releases.

For me the issue was that the firmware available for download from VIA was not actually VIA compatible. You need to check supported keyboards to see if your board is actually supported. If it's not you'll have to port it yourself or complain to someone who will. If another version of your board is supported for VIA this is not the most difficult thing to do if you can program, can recommend. Don't install firmware for a different version of your board onto your board though, even if it supports VIA. Trust me, that doesn't go well.

Hello @gaycodegal,

We all can appreciate your frustration and that is the reason behind me continuing this thread. I have posted the steps on how to port your firmware into VIA. If the firmware for your keyboard is listed in VIA's downloadable section but you have a "Different" model, it should be as straight forward as changing a few values in each of the configuration files to match your board specifically. Then a successful flash should become possible.

from releases.

@LouWii @ToniWonKanobi Did you guys find a solution to this?

from releases.

@LouWii @ToniWonKanobi Did you guys find a solution to this?

I think I just found it in QMK instead. I dunno. via in general is kind of buggy sometimes. ¯_(ツ)_/¯

from releases.

I've never tried again.

from releases.

i have this same exact issue, I even reflashed on qmk but it still wont work.

from releases.

Thanks @SnippyStockins ! This should definitely go into VIA's documentation.

from releases.

Thanks @SnippyStockins I'll give it a go and see if this fixes my issue.

from releases.

Thanks @SnippyStockins ! This should definitely go into VIA's documentation.

Maybe Olivia will see this and add it in! Lol

from releases.

Thanks @SnippyStockins I'll give it a go and see if this fixes my issue.

Keep me posted and if you have any issues I'll try and troubleshoot with you!

from releases.

@SnippyStockins
Thanks for the help! Looks like that got it working. If anyone is curious on what a full config looks like here is my repo
https://github.com/luigi311/qmk_firmware-1/tree/luigi311/keyboards/handwired/stream_cheap/Zatarian
In the keymaps/via folder exists the 3 files that you need and an example of what they look like. You do have to go in to design and load that json every single time unless its in the via repo im assuming.

from releases.

@luigi311 @SnippyStockins Hi guys I just wanna ask I've got all 3 files in the via folder identical to the Luigi's ones, then it's time to "compile and flash", does this mean like i flash the hex file from qmk configurator that i usually use for my keeb (which is a KBD67 MKII) ? If yes then I have flashed it but VIA doesnt seem to recognize my keeb. Also tried unplugging and replugging. Are there any solutions for this? Tysm

from releases.

After you flash it with the new hex you then have to go to VIA design and feed it the json

from releases.

hmm this is weird, so what should i do after feeding the design tab it's json file, my keeb is still not recognized 😢 here's a picture, am I doing it right tho?

from releases.

@SnippyStockins
Thanks for the help! Looks like that got it working. If anyone is curious on what a full config looks like here is my repo
https://github.com/luigi311/qmk_firmware-1/tree/luigi311/keyboards/handwired/stream_cheap/Zatarian
In the keymaps/via folder exists the 3 files that you need and an example of what they look like. You do have to go in to design and load that json every single time unless its in the via repo im assuming.

@luigi311
I'm glad to hear my guide has worked for you! Depending on how accurate and to scale your design from the KLE is to your physical board and also how you coded the rest of your files will dictate if and how often you will need to load the json. I created my firmware custom to my own designed board so it does show up in VIA almost every time without loading the layout.

from releases.

@luigi311 @SnippyStockins Hi guys I just wanna ask I've got all 3 files in the via folder identical to the Luigi's ones, then it's time to "compile and flash", does this mean like i flash the hex file from qmk configurator that i usually use for my keeb (which is a KBD67 MKII) ? If yes then I have flashed it but VIA doesnt seem to recognize my keeb. Also tried unplugging and replugging. Are there any solutions for this? Tysm

@dekul1205
I am curious if you are trying to use the KBD67MKII firmware as it has the same layout as your board, or are you trying to load your KBD67 MKII into VIA? If you are trying to get your KBD67 into VIA, they actually already have a pre-compiled .hex for that board. Go to https://caniusevia.com/docs/download_firmware/ and find the exact model of your keeb. Download the firmware and flash with QMK and it will have full VIA support!

from releases.

@SnippyStockins Yes that's actually my intention but after i downloaded the firmware and flashed it on QMK Via still doesnt recognize my keeb, should I uninstall Via or something, also I have just uninstalled QMK firmware, does it have any affect on my progress? Thank you!

from releases.

@SnippyStockins Yes that's actually my intention but after i downloaded the firmware and flashed it on QMK Via still doesnt recognize my keeb, should I uninstall Via or something, also I have just uninstalled QMK firmware, does it have any affect on my progress? Thank you!

I am curious as to why you are having the issue in the first place, if I'm not mistaken most if not all of KDBfans keebs are via compatible out of the box 😳. That being said though, I would try uninstalling and reinstalling VIA and see if that fixes your issue. If not I will look into this and see if I am able to find a workaround / fix.

from releases.

@SnippyStockins Yes that's actually my intention but after i downloaded the firmware and flashed it on QMK Via still doesnt recognize my keeb, should I uninstall Via or something, also I have just uninstalled QMK firmware, does it have any affect on my progress? Thank you!

I am curious as to why you are having the issue in the first place, if I'm not mistaken most if not all of KDBfans keebs are via compatible out of the box 😳. That being said though, I would try uninstalling and reinstalling VIA and see if that fixes your issue. If not I will look into this and see if I am able to find a workaround / fix.

Tysm man, you're a great guy. Tho i have tried un/reinstalling Via but it still didnt work, dammit LMAO, there's gotta be sth wrong with my keeb. But tks anyway <3 ^^

from releases.

@SnippyStockins Hey, how are you? I've tried to flash my KBDFANS x MAJA with qmk to no avail, VIA won't detect it (had this keyboard for quite a while and not being able to change the layout is quite frustrating lol). I've tried your solution and others and either it's me not having enough prior knowledge of code or just the software, if you could would you be able to hop on a discord call and help me with this? Thanks, appreciate it if you could.

from releases.

@SnippyStockins Hey, how are you? I've tried to flash my KBDFANS x MAJA with qmk to no avail, VIA won't detect it (had this keyboard for quite a while and not being able to change the layout is quite frustrating lol). I've tried your solution and others and either it's me not having enough prior knowledge of code or just the software, if you could would you be able to hop on a discord call and help me with this? Thanks, appreciate it if you could.

Hey there @JoJoMcFearson,
I'm good! Thanks for reaching out. You actually don't need to create your own VIA JSON as there is already a VIA firmware available for the Maja. I have one as well! Is yours hotswap or soldered?

from releases.

@SnippyStockins I've tried that as well, but my keyboard never comes up on the configure page, and doesn't work on the design one. It's hotswap. It gives me this

from releases.

@SnippyStockins I've tried that as well, but my keyboard never comes up on the configure page, and doesn't work on the design one. It's hotswap. It gives me this

@SnippyStockins I've tried that as well, but my keyboard never comes up on the configure page, and doesn't work on the design one. It's hotswap. It gives me this

Try flashing this firmware and if it doesn't work I would look into that error for you!

https://caniusevia.com/docs/download_firmware#0

from releases.

@SnippyStockins Flash in qmk toolbox? If so I've done that already with no results. I always get the error "Atmel DFU device disconnected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)" or just no device showing up. Thank you for all the help so far though!

from releases.

@SnippyStockins Flash in qmk toolbox? If so I've done that already with no results. I always get the error "Atmel DFU device disconnected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)" or just no device showing up. Thank you for all the help so far though!

If that's the case, there is a chance your EPROM, usb connector, or another component is failing... How long have you owned the board for?

from releases.

from releases.

@SnippyStockins is there a way I can clear my EPROM/reset it? Maybe that could help...?

from releases.

Never mind @SnippyStockins, solved the issue! Thank you for the time and help you provided.

from releases.

I can't figure this out for the life of me. I've mapped out my keyboard, downloaded the JSON, and then added the VIA rules but my keyboard still won't configure in VIA. I'm confused about the other two files we need and I know I've definitely done something wrong when adding the rules into the JSON, but I'm not sure how to fix it. I'm honestly pretty clueless when it comes to coding (I'm new to all this) so if anyone has the time or is willing to help I would really appreciate it!

my layout: http://www.keyboard-layout-editor.com/#/gists/ea128d08f2a0b3df2012cae2d8f37d71

from releases.

For me the issue was that the firmware available for download from VIA was not actually VIA compatible. You need to check supported keyboards to see if your board is actually supported. If it's not you'll have to port it yourself or complain to someone who will. If another version of your board is supported for VIA this is not the most difficult thing to do if you can program, can recommend. Don't install firmware for a different version of your board onto your board though, even if it supports VIA. Trust me, that doesn't go well.

from releases.

I can't figure this out for the life of me. I've mapped out my keyboard, downloaded the JSON, and then added the VIA rules but my keyboard still won't configure in VIA. I'm confused about the other two files we need and I know I've definitely done something wrong when adding the rules into the JSON, but I'm not sure how to fix it. I'm honestly pretty clueless when it comes to coding (I'm new to all this) so if anyone has the time or is willing to help I would really appreciate it!

my layout: http://www.keyboard-layout-editor.com/#/gists/ea128d08f2a0b3df2012cae2d8f37d71

Hello @NAmico99,

My apologies, I didn't see this message. Did you end up figuring out what was going on? If not, I'd be happy to look into this for you.

from releases.

Never mind @SnippyStockins, solved the issue! Thank you for the time and help you provided.

Hello @JoJoMcFearson,

My apologies for not getting back to you, I have had quite a few transitions happening in my career and life in general. If you don't mind me asking, what was the solution to your issue? I would appreciate if you could post as it may help someone with similar issues in the future!

from releases.