The installed udev rule uses GROUP="plugdev", which is a debian-specific group

I'd like to suggest using TAG+="uaccess" instead of MODE/GROUP.

This is even the suggested usage from Debian, and works anywhere udev is supported, instead of just debian-based distributions. Adding TAG+="udev-acl" as well would support old versions of Debian/Ubuntu as well, but I don't believe anything that old (<=13.04) is still supported

Hello! I'm using macOS 10.15.4, VIA 1.2.7. My PCB is the Wilba WT-60D (came with the Mekanisk Klippe S). When I launch VIA, it just sits in the "Searching for devices..." screen. The key tester tab works just fine, however. I'm able to successfully flash firmware with QMK toolbox, and I'm able to use the board. I'm also able to use the configure tab in Windows 10, so it must be a problem with macOS of some sort.

I'm a software engineer - let me know if I can be of assistance in fixing this. Happy to lend a hand if you've got an idea of where to start, or some docs/code I could read. Otherwise just let me know if there's any more info you need about my system. Thank you!

Attempting to add MT(MOD_RSFT,KC_SLSH) to the keymap of a BIOI G60BLE. Adding this code via the ANY key does not take. Instead, when I export and inspect the .JSON, it appears the next keycode in line is added in it's place.

I am able to add MT(MOD_RSFT,KC_SLSH) to the JSON manually and import it and the keycode will work.

Can't add {KC_PMNS} in a macro. It says:

Whoops! Invalid keycodes detected inside {}: KC_PMNS

The longer variant for that key, KC_KP_MINUS is also not accepted.

VIA 1.2.7, OS X 10.13.6.

Add capability to create text macros using the send string functionality from here: https://beta.docs.qmk.fm/using-qmk/advanced-keycodes/feature_macros

Would simplify text-only macros, I think. Right now there's no simple way to add these.

Using Pop!_OS 19.10 and the configurator can't find my WT-60D which is recognised in the windows version.

It is really weird to configure keycodes in VIA right now. The available keycodes are sorted in alphabetic way (I guess), so finding a right now is not very convenient.

I believe it would be better if keycodes were aligned into default ansi 104 layout. Kinda like it is now on https://config.qmk.fm

So, right now it is:

Much better way:

Hi,

I am running the latest release for Windows and using the TMOv2 PCB.

When I configure the keyboard, it works and still works after I close the VIA software. However, when I unplug the keyboard and replug it, the configuration is back to the default one that I had when I flashed the VIA compatible firmware.

I don't have any other VIA compatible PCB for now so I can't test it with something else.

Let me know if you want me to test anything else!

Thanks

If the keyboard firmware is built with MOUSEKEY_ENABLE = yes, it is possible to use Mouse Keys in the keymap. However, VIA 1.2.7 does not support these key codes even with the “Any” feature (names such as KC_MS_UP are not recognized), unless raw hex codes like 0xf0 are used (then the mappings work as they should, but finding those raw codes is cumbersome).

Would it be possible to add some support for these key codes?

There are layer keys MO(0) through MO(7), however I can't seem to figure out how to define layers above no 3. The number of layers seems stuck at four: {0,1,2,3}..

For reference: I'm using the_royal/liminal keyboard

Do you plan on adding support for reactive RGB lighting effects? These are supported by QMK, but not by VIA.

I've 2 MX-11800 modified and running QMK. When I use VIA I can't distinguish wich is the 1st and the 2nd one. This is special useful if you are using multiple POS Keyboards as macropads.
If the SERIAL_NUMBER is added to the name the problem is solved.

I'm trying to create a macro for my M60-A but when I enter a chord in the specified format I get an error. It's quite possible I'm doing something wrong but I'm not completely sure.

Also, are you accepting contributions?

https://caniusevia.com/docs/supported_keyboards/ lists HHKB and HHKB JP as supported, but the firmware is nowhere in the downloads.

Would it be possible, if you choose to assign "Any" to a key that is already assigned "Any", to edit that value? or to have a separate "Edit" button somewhere?

Sometimes I just want to do a slight modification to an assignment that I've already made, or to copy it to a different key without having to retype. (right click + copy keycode?)

I'd be happy to contribute a PR for this if possible.
I have a few other requests that I would be happy to contribute if found useful.

When mapping my Equinox WKL layout, I discovered that assigning a key Left Ctrl causes it to be mapped to LWin, and vice versa.

I reproduced this in several different positions to verify it wasn't a switch/pad specific issue.

Right Ctrl and Rwin do not have this problem.

This is with Release 1.2.5

Attached please find a screenshot of the configurator and the corresponding JSON output; despite the bottom left key showing LWin in both the GUI and in the JSON file, the key is mapped to Left Ctrl on the keboard.

equinox.json.txt

People using it are most likely doing so to test functionality of individual keys before soldering or while debugging. Having the tester display the position of the pressed switch regardless of keycode is, as far as I'm concerned, more suitable for that.

I'd contribute a GMK Explorer one.

FIY, via can now be installed using brew: Homebrew/homebrew-cask#83663

brew cask install via

If you want to add it to the documentation or something else !

I've Tap Dance configured on my keyboard and I've to use keycodes of this. If is posible use TD(nn) instead of 0x57nn will be nice.

https://github.com/jkutianski/qmk_compaq_mx-11800/blob/master/keymaps/via/keymap.c

I am unable to add keycodes to my board use the red Any button. I was trying to add LT(1,KC_BSPC), and after some troubleshooting, even something simple like KC_L was not working. I've tried on 1.2.4 and 1.2.6. The key is just remapped to LSHIFT instead.

Via is crashing when I flash a Quefrency with the default rev1 firmware with the via keymap. I'm not sure what is missing, but I see this in my log:

  constructor: 'TypeError',
  stack: "TypeError: Cannot read property 'replace' of undefined\n" +
    '    at J (file:///C:/Users/frank/AppData/Local/Programs/via/resources/app.asar/app/dist/renderer.prod.js:154:19)\n' +
    '    at file:///C:/Users/frank/AppData/Local/Programs/via/resources/app.asar/app/dist/renderer.prod.js:154:1831\n' +
    '    at renderWithHooks (C:\\Users\\frank\\AppData\\Local\\Programs\\via\\resources\\app.asar\\node_modules\\react-dom\\cjs\\react-dom.development.js:16260:18)\n' +

This error is making me think I the default firmware is missing a value somewhere, but since the app has already been bundled I can't open the devtools for context about what variable is undefined. Is it possible to compile my own dev version of Via? If not can someone help me figure out why the default firmware doesn't work? Everything is fine except that when I try to configure it in Via the screen just turns blue.

Hi VIA team,

I've switched to using VIA over QMK as of late because it is so much quicker and convenient.
That being said, one thing I miss from QMK is the ability to change screen brightness for laptops.

Maybe I'm just looking in the wrong places but I cannot find any screen brightness keycodes for the life of me.

Would it be possible to add these keycodes into via? Or point me to where they are if I am totally missing them?

Thanks!

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).

Having the ability to activate a layer by pressing a combination of Fn and a number (0,1,2,3) would be a great feature for smaller keyboards instead of having to dedicate multiple keys in order to have multiple layers.
Holding the key combo for a momentary layer would be fine but cumbersome.
Entering the key combo for a toggle to that layer would be preferred.

Whenever Tilda (~) is mapped to something, it triggers left shift with it. If I map the key off of tilda it works fine. Ie Key will input 1 'T'. If i change the T key to Tilda, it will activate tilda and left shift together.

Currently using VIA 1.2.7 on a Polaris by Ai03.
Firmware flashed was ai03_polaris_via.hex

First Image. I have esc mapped to layer 0. On layer 1 it is mapped to tilda.

Second image, I have tilda on layer 0. Where the B key is.

Key tester on VIA shows identical results.

https://beta.docs.qmk.fm/using-qmk/hardware-features/feature_encoders

Would it be possible to show a number in addition to the slider for the 'Disable LEDs after timeout (mins)' setting? Right now, I can't tell how long it's actually set for.

Upon flashing the Unikorn pcb with the new via hex file, the overall matrix of the keyboard seems to be non-functional.

Layout:
-Split backspace
-split right shift
-tsangan bottom row

Issues:

• "Q" on row one registers for both Q and W on matrix, and everything is shifted to the right
  (i.e. W => Q, E => W, etc.)
• similar issues are detected on home row
• bottom row (spacebar row) is shifted as well.

The quefrency/rev1 keyboard was setting a wrong value for VIA_EEPROM_LAYOUT_OPTIONS_DEFAULT (probably the error was made because the assignment of bits in that field is not really documented anywhere): qmk/qmk_firmware#9618. The value which was set apparently was interpreted by VIA as setting the value of 3 for the JSON-defined layout option

["Right Shift", "Standard", "1.75u Shift", "1.75u /"]

which has only 3 values (0, 1, 2) defined, so 3 was out of range. In this case the VIA app just shows a blank window (even without any possibility to switch tabs) instead of the “CONFIGURE” tab (I tested on Linux, but other people encountered the same problem on Windows and Mac). If another tab was active when the keyboard is attached, the app continues to work until the “CONFIGURE” tab is selected, then the window becomes completely blank.

The VIA app should handle such errors more gracefully (maybe it should put an error message somewhere, then reset the bad layout option to some existing value). At the moment the app just becomes unusable if the layout options field was corrupted for some reason.

When enabling layer/caps lock indicator on an rgb board, every single led illuminates. It would be better to let the user choose specific leds.

Hello, I'm looking for a firmware/hex file for levinson. Levinson is compatible with QMK, I've flashed it using the QMK online configurator and its working.

Does anyone know how to make it compatible with VIA?

The firmware of candybar_lefty_via.bin has a problem with the right space bar (for split space bars) where the changes in via do not register and it is stuck as backspace.

If there firmware open-source? I would be happy to try and have a look at it myself to see if I can fix it, but I cannot find it anywhere.

For instance, Quefrency has a macropad section in the layout I'd like to have on by default. Right now as a workaround, I use ["Macropad", "On", "Off"] in my JSON file.

The key diagram for my Iris Rev. 4 has the thumb keys in the wrong order. The key diagram is rotated from how the physical keys are. See the attached image to see exactly how the keys are swapped.

A delay between keypresses is very useful when doing multi-key macros in programs. The currently supported macros do not have a delay between keypresses, leading to mis-typed keys or not "waiting" to be on the right menu before making a selection.

QMK supports a delay between keypresses using SS_DELAY(msecs) between presses. This is beyond the current scope because it's not a basic keycode, however it would be extremely useful to add this functionality.

I downloaded via-1.3.1-win.exe and via-1.3.1-win.msi. I tried running the installer and the program and nothing happens.

Keyboard : discipline65

I flashed the keyboard using provided firmware from VIA website. Everything works on the fly except media keys. The entire media keys is not responding (Vol-,Vol+,Play, etc).

What I've tried:

1. Restarting PC
2. Putting media keys on main layer
3. Tried multiple layer modes
4. Reset

However issue still persists

Using different keyboard (romac), the media key is working perfectly.

Hello! Is there any way I can help translating VIA into other languages? I saw an i18n repo but there isn't really any info in it.

When switching to the lighting tab with my Iris rev. 4 keyboard, VIA goes to a blank screen with no icons.

Running version 10.15.2. Confirmed spctl is disabled and Security setting set to "Allow apps downloaded from: Anywhere" just in case the app isn't signed.

Finder error is "The application 'VIA' can’t be opened."

Some logging I see in console:

Checking whether application is managed at file:///Applications/VIA.app/org.via.configurator

Received xpc stream event (distributed notification matching) with name: com.apple.LaunchServices.applicationRegistered user info: {
    CFBundleDisplayName = VIA;
    bundleIDs =     (
        "org.via.configurator"
    );
    isPlaceholder = 0;
}

LAUNCHING:0x0-0x5d15d1 VIA foreground=1 bringForward=1 seed=1738 userActivityCount=0

spawn_via_launchd() failed, errno=111 label=[0x0-0x5d15d1].org.via.configurator path=/Applications/VIA.app/Contents/MacOS/VIA flags=1

Hello,

Looking at the latest release there are no source code what so ever. source code (tar.gz) is empty except an empty README.md. Looking at your website https://caniusevia.com, it doesn't state any company behind this, nor any links to the source code.

What is the state on this project? Is it closed source? Is there a company behind it? Seems like installing this at it's current state would be the same as begging to get keylogger installed. 🤷‍♂️

Best regards

OS: Gentoo WM: BSPWM if it matters

Target: Input command / chord - [hold] Left Control + Page Up

Issue Reconstruction

1. Program chord: {KC_LCTL,KC_PGUP} for MACRO 0
2. Assign MACRO 0 to designated key
3. Press the designated key [MACRO 0]

Result: Left Shift + N (in other words, the macro types "N")

I've hackily worked around a lack of support using a custom lighting, and sharing command codes with RGB Light, but official support for RGB Matrix would be awesome.

I'd be happy to work with you to implement anything needed on the QMK side for this.

My initial command handler for QMK is here

kageurufu/qmk_firmware@f6a866a

And here is the accompanying JSON to make it function

    "lighting": {
        "extends": "qmk_rgblight",
        "underglowEffects": [
            ["All Off", 0],
            ["Solid Color", 1],
            ["Solid - Highlighted Mods", 1],
            ["Vertical Gradient", 1],
            ["Horizontal Gradient", 1],
            ["Breathing", 1],
            ["Colorband - Saturation", 1],
            ["Colorband - Brightness", 1],
            ["Pinwheel - Saturation", 1],
            ["Pinwheel - Brightness", 1],
            ["Spiral - Saturation", 1],
            ["Spiral - Brightness", 1],
            ["Cycle All", 0],
            ["Cycle Horizontal", 1],
            ["Cycle Vertical", 1],
            ["Rainbow Chevron", 1],
            ["Cycle - In/Out", 1],
            ["Cycle - In/Out Dual", 1],
            ["Cycle - Pinwheel", 1],
            ["Cycle - Spiral", 1],
            ["Dual Beacon", 1],
            ["Rainbow Beacon", 1],
            ["Rainbow Pinwheels", 1],
            ["Raindrops", 1],
            ["Jellybean Raindrops", 1]
        ]
    }

Hello, as far as I know, the lifetime of memory units on an MCU is finite, and now most of the keyboards are using atmega32u4. From the documentation of Atmega, it guarantees for the EEPROM to have 100,000 write/erase cycles.

Is it a better idea to change the logic that adds an update or store button to send the update event to the keyboard when finishing the whole configuration, instead of frequently updating the EEPROM when the GUI changes a key immediately?

On RGB boards like the zeal60, I'd like more control on which keys act as mods or alphas. Right now you can only toggle if you want to use the leds of some split or ISO keys, but you can't change its behavior.

I've a large keyboard defined on VIA and the resolution of my monitor is 1366 x 768. VIA only leave me 1 row of keycodes.

when I type in KC_MEH the screen closes and doesn't update key. My current work around is to use C(A(S(KC_NO))) It works, but I don't think that is the right way. For one it would be nice if there was some sort of error message or that the window stays open to let me know that key is not supported.