If the RGB write doesn't work as expected on a tester's G522, we now get enough trace info at INFO level to see exactly what happened: - Color chosen + RGB values + target zone IDs (hex) - Each of the 3 feature requests logged with payload hex and response hex: SetHostModeState(1), SetRgbZonesSingleValue, FrameEnd - Zone discovery: logs raw GetRGBZoneInfo response when it succeeds, WARNING when response shape is unexpected and we fall back to [0x01, 0x02] - WARNING on exceptions with color name context Existing ERROR logs in base.py already surface device-returned error responses (OUT_OF_RANGE, UNSUPPORTED etc.) for the individual feature calls, so a stack of ERROR + our INFO context tells us which of the three steps failed. |
||
|---|---|---|
| .. | ||
| hid_parser | ||
| hidapi | ||
| keysyms | ||
| logitech_receiver | ||
| solaar | ||