H705D: Individual segment commands report success but render as whole-string change

[hearter20176]

Govee Device SKU: H705D
Device name: House Eaves Garage
Govee2MQTT Version: 2026.03.25-ab9deb66

Describe the issue

Sending individual segment color/brightness commands via light.turn_on on the
per-segment light entities (e.g. light.house_eaves_garage_segment_011) returns a
successful response from the Platform API for that specific segment index, but the
physical LED string does not render the segment in isolation — the whole string
appears to update together instead of just the targeted segment.

I've confirmed this is not a hardware limitation: the official Govee app can
control individual segments correctly on this same device. The issue only appears
when controlling segments through Govee2MQTT.

Steps to reproduce

1. Call light.turn_on targeting a single segment entity (e.g. segment 11) with a
   distinct color/brightness
2. Wait, then call light.turn_off on that same segment, and repeat for the next
   segment in sequence
3. Expected: only the targeted segment changes each time
4. Actual: the entire string appears to change together

Log excerpt (segments 11–13 shown; same pattern continues through all 27 segments)

b9845f46_govee2mqtt_2026-07-18T17-32-11.825Z.log

Additional context

Each request is scoped to a single segment index and receives a distinct successful
response, so this doesn't appear to be a command-formatting issue on the
Govee2MQTT/Home Assistant side — the physical rendering just doesn't match what the
API confirms was set. Happy to provide more logs or test specific command formats if
that's useful for narrowing this down.