Ground truth for Govee Flow Plus Light Bars (H6056): phantom segments, bar-to-segment mapping, API auth and rate limits.
100
100%
Does it follow best practices?
Impact
100%
3.84xAverage score across 6 eval scenarios
Passed
No known issues
{
"context": "Tests whether the agent correctly handles the RGB (0,0,0) no-op firmware quirk by using near-black (1,1,1) for segment clearing, ensures all 12 physical segments are addressed at shutdown, and avoids phantom segments.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Near-black for shutdown",
"description": "The shutdown/clear function uses rgb=(1,1,1) or equivalent near-black (any non-zero RGB tuple where all components are > 0, matching the plugin's recommendation of (1,1,1)) instead of rgb=(0,0,0) when clearing segments at session end",
"max_score": 30
},
{
"name": "All 12 segments cleared",
"description": "The shutdown call targets all physical segments 0..11 (e.g. range(12) or [0,1,2,...,11]) — does NOT stop at fewer than 12 or include indices 12+",
"max_score": 25
},
{
"name": "Zero-value quirk explained",
"description": "A comment, docstring, or notes section explains that rgb=(0,0,0) may be treated as a no-op by some firmware and that non-zero near-black is used to reliably darken segments",
"max_score": 20
},
{
"name": "No phantom segments",
"description": "No API call in the script includes segment indices 12, 13, or 14",
"max_score": 15
},
{
"name": "Shutdown on interrupt/exception",
"description": "The script uses try/finally (or atexit or signal handler) so that the near-black clear-all call executes even when KeyboardInterrupt or an exception terminates the loop",
"max_score": 10
}
]
}