hid-remapper
hid-remapper copied to clipboard
Monitor Tab doesn't show anything
i saw one of the first issue that people had regarding the interactive remapping funcionality, and i saw the author last message on it saying that they added the monitor tab but i can't seems to see what i am pressing there. Am i missing something?
What device are you using? Does it work otherwise?
sorry for the lack of information, i'm using the Seeed Studio Xiao nRF52840 with a bluetooth numpad (an huion k20). it does work very well apart from the monitoring tab and i need it to remap the dial, otherwise i will need to search for the right hex value but there's hundreds of them. is this an issue because i'm using the bluetooth microcontroller? (because i read in the changelog of an older version that the bluetooth doesn't support some of the feature but it's not listed which ones don't work. Hence my question)
PS: just to clarify i don't want to sound ungrateful, this is an awesome tool and it's practically the only solution to have a layered macropad without spending an egregious amount of money for a QMK keyboard. You have my sincere gratitude for giving it away for people to use it.
Yeah, the monitor function doesn't work on the Bluetooth version, perhaps I could have made that more clear.
There's no technical reason preventing it from happening, I just didn't get around to implementing it yet. Hopefully soon.
Also if the dial is Surface Dial-compatible then it likely uses 0x00010037 code.
that's very nice to hear! Would the codes be the same with the usb version (with the Adafruit Feather RP2040 with USB Type A Host) because i'm also planning to use it for my keyboard and/or other devices and i could just check the HEX code with the usb version.
the dial is surface compatible (i think) as windows does detect it natively, but that code isn't in the list, It's also weird because a red light flash on the XIAO whenever i press on a key but it doesn't when i operate the dial (i presume because every key is by default set as something while the dial is not). Not a big deal, i could solve it by finding the Hex so in the meantime i will try HIDtools you mentioned on the old issue post. And if i'm unlucky i will see when the usb controller arrive.
I thank you a lot for the clarification tho!
The codes will probably be the same over USB, but it's strange that the light doesn't blink when you operate the dial. It should blink every time it receives something, even if it doesn't know what to do with it.
no idea, if i'll get to know why i'll post it here in the future
You can try this test build, it should have the monitor tab working in the Bluetooth versions (click on artifacts at the bottom):
https://github.com/jfedor2/hid-remapper/actions/runs/5882479664
Though I suspect that the dial might still not show up if the LED isn't blinking.
i tested it and it works wonderfully! and i figured the problem about the dial.
Somehow huion made it so that the dial only works with the official software running, I suppose the internal firmware detect if it's connected directly or not. i came to that conclusion by quickly swap between the bluetooth connection and the XIAO and i discovered that it works for a couple of seconds, after that it will stop working.
I have no idea why huion decided to do that, it seems very stupid so i'll search for another bluetooth numpad/macropad.
thank again for the very quick solution to the monitoring!
actually i checked again, the codes that the monitor gives me doesn't seems to match with the ones that i have in input (https://imgur.com/a/3ddlohf) is that a problem on my part? not that i matters too much since i can just use the key but i was curious on to why is that.
Not sure if I understand the question. The hex codes at the bottom are only for inputs that are not listed above. If a code is known (has a name in the UI) then it won't be listed again in the extra section at the bottom. Is that what you meant? The monitor tab gives you both the hex code and the name (if it knows it).
that's what i meant yes, i just wanted to be sure, thanks a lot again, i promise this was the last question lmao.