Skip to content

DSHMv3 does not allow setting LEDs states from config file #260

@Kanuan

Description

@Kanuan

Context

In DS3's output report, there are:

  • 1 ) 1 byte that sets LED states
  • 2 ) 4 groups of 5 bytes, each one for each LED, that sets custom effects the associated LED should execute
    • Effects are only executed if the related LED has been enabled via (1)

Issue:

Currently, DSHMv3 allows settings (2), but not (1), so that means the LEDs are always off and no effects are shown

Proposed solution:

  1. Allow dshidmini to read from a property in the .json file called "LEDsState" that sets the corresponding LEDs states byte in the output report
  2. Rename the "Enabled" properties in LEDsCustoms to "EffectsEnabled" to make things clearer.

image

Metadata

Metadata

Assignees

Labels

CoreCore/Common Driver TopicbugSomething isn't working

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions