Issues with Madlions 68 Pro R

[Actiongomini]

Alr so basically im dumb, and i have absolutely no idea how im meant to set this up for a madlions 68he pro r. currently it doesnt work at all with any of the demos so i assume im doing something wrong.

things i have done:
moved the plugin into the folder its meant to be in
deleted the other two plugins (also tried with these plugins)
tested everything with the analogsense demo and woot-verlay

I assume this issue is due to the usb device being identified differently than the model/s inplemented, so what would be the best way to make sure it works, this keyboard is essentially the same as the normal version other than the keycaps

device info from hid explorer if that helps:

productName: MAD 68 Pro R
vendorId: 0x373B (14139) Unknown vendor
productId: 0x10D4 (4308)
opened: true
collections[0]
Usage: 0001:0006 (Generic Desktop > Keyboard)
collections[1]
Usage: 0001:0002 (Generic Desktop > Mouse)
collections[2]
Usage: 000C:0001 (Consumer > Consumer Control)
Input reports: 0x03
collections[3]
Usage: 0001:0080 (Generic Desktop > System Control)
collections[4]
Usage: 0001:000C (Generic Desktop > Wireless Radio Controls)
Input reports: 0x05
Input report 0x03
16 bits (bits 0 to 15)
Data,Ary,Abs
Usages: 000C:0001 (Consumer > Consumer Control) to 000C:02A0 (Consumer > AC Soft Key Left)
Logical bounds: 672 to 0
Input report 0x05
1 bit (bit 0)
Data,Var,Rel
Usage: 0001:000C (Generic Desktop > Wireless Radio Controls)
Logical bounds: 0 to 0
7 bits (bits 1 to 7)
Cnst,Ary,Abs
Logical bounds: 0 to 0

[Sainan]

Madlions 68 Pro is not on the list of supported devices so I don't know what your expectation is

[Actiongomini]

ohr sry i meant to say, like how would this be implemented, its essentially the same as the normal one with a nicer case

[Actiongomini]

also damn fast response times ( i was looking at another issue about the nano 68 to see if i could learn anything)

[Sainan]

If it's the same, then maybe just productId 0x10D4 would need to be added to the filters. You could try it by cloning AnalogSense.js and running the demo: https://github.com/AnalogSense/JavaScript-SDK/blob/senpai/AnalogSense.js#L715

[Actiongomini]

I've tried this and it doesnt detect the keyboard

[Actiongomini]

This does

, however nothing shows up (i assume something should idk)

[Sainan]

Then it's not basically the same with just a nicer case. Not buying any more of their keyboards until they improve their firmware enough to make supporting their keyboards worthwhile.

[Actiongomini]

ok, would there be any particular factor affecting this? As in why it wouldnt work

[Actiongomini]

they are specced slightly differently if that would be a reason, what is the proccess for implementing a new keyboard?

[Sainan]

Figure out how to read the analogue values from it and then implement that.

[Actiongomini]

ok thanks, idk anything abt that but ima do some research and see if it would be reasonable to attempt this

[Actiongomini]

this shows that it should be possible for the pc to read analogue values from it, but i'll have to do some research on how this works cus im new to it all

[Actiongomini]

oh yh i also have a nano68 pro similar to the other issue so i might check that first, was there any progress on that, and what was the primary issue with implementing it