wireless

A common protocol structure is to have a header containing a length field, followed by data of length bytes, followed by additional protocol fields such as a CRC. If the length field is variable, the position of subsequent URH-specified protocol fields defined by fixed position will not be in the correct location.

I do not know the best way to address this, but quick and easy way to support

What happened?

I was saving several screenshots of a flowgraph using the Screen Capture (Ctrl + P) function. After saving a few screenshots I noticed the filter dropdown menu looking like this:

I had expected to see only a single "All files" entry.

If the a single color backlight config setting ZMK_BACKLIGHT_AUTO_OFF_USB=y, and we start ZMK from battery, currently the backlight is initialized on, and doesn't turn off, even though USB isn't present. Came up when testing the equivalent behavior for RGB Underglow in #1010

Need to change the backlight init code to default the state based on the USB state in app/src/backlight.c.

Indicator CC V4 adds two new commands:

• Indicator Description Get Command
• Indicator Description Report Command

https://github.com/zwave-js/node-zwave-js/blob/master/specs/SDS13782%20Z-Wave%20Management%20Command%20Class%20Specification.pdf

TODOs:

• Implement the new commands
• Implement a getDescription method on IndicatorCCAPI
• update @implementedVersion decor