4Q support?

[vprimachenko]

node-hid.devices() did list

{ vendorId: 9456,
  productId: 8247,
  path:
   '\\\\?\\hid#vid_24f0&pid_2037&mi_00#7&cf6c84a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}',
  serialNumber: '\t',
  manufacturer: 'Metadot - Das Keyboard',
  product: 'Keyboard',
  release: 256,
  interface: 0,
  usagePage: 1,
  usage: 6 },
{ vendorId: 9456,
  productId: 8247,
  path:
   '\\\\?\\hid#vid_24f0&pid_2037&mi_01&col01#7&2026e488&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}',
  serialNumber: '\t',
  manufacturer: 'Metadot - Das Keyboard',
  product: 'System Control',
  release: 256,
  interface: 1,
  usagePage: 1,
  usage: 128 },
{ vendorId: 9456,
  productId: 8247,
  path:
   '\\\\?\\hid#vid_24f0&pid_2037&mi_01&col02#7&2026e488&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}',
  serialNumber: '\t',
  manufacturer: 'Metadot - Das Keyboard',
  product: 'System Control',
  release: 256,
  interface: 1,
  usagePage: 12,
  usage: 1 },

but both

const hidDevice = keyboard.find(9456, 8247, 1, 128);

and

const hidDevice = keyboard.find(9456, 8247, 1, 1);

failed with

Error: feature report errored too quickly; device is probably not there anymore: 0

so, how can i help get it running on 4Q?

[chris13524]

This library was developed and tested for the 5Q only. Support for the 4Q would need to be developed independently (i.e. unless they use similar protocols).

We hoped this library (and the other "cloud connected" libraries in this organization) would eventually be extended to support a wider variety of keyboards. As such, you're free to work on support for the 4Q and submit a PR.

You might try a wider variety of interface and usage numbers, see if you're lucky and can control the 4Q with the same protocol?

[vprimachenko]

ok, so to get started, how do i even begin?

as i see, the lib does not even get connected to the 4Q HID handle, what were your steps to get it runnning in the first place?

I have prepared Wireshark with USBPcap to log the packages, what was your process to gather the data?

[chris13524]

Honestly, you just have to look at the Wireshark output and see if you can replicate behavior with your own code. These are the packets we use to control the 5Q. Just a bunch of magic numbers, ya know?

[octo]

Hi all,

I recently bought the 4Q and started tinkering with it. Unfortunately it turns out that it uses a completely different wire protocol, which I have started to document at https://github.com/octo/das/wiki/Set-Key-State-message. I'm writing an implementation of the protocol in Go; currently it is able to set individual keys but setting many keys seems to overload the keyboard.

From reading your implementation and spending way too much time with the USB traces of the 4Q, I'd say adding support for the 4Q keyboard to this project is as much work as writing a new implementation from scratch. There is very very little you could reuse.

HTH and best regards,
—octo