Fix: offline device could stop a sensor (and other entities) updating (#83)
When a Govee device goes offline, the cloud returns an empty string ("") for some capability values. An unguarded int("") in the state parser raised ValueError and failed the entire device-state fetch — so the affected device silently stopped updating (seen in logs as Failed to fetch state for …: invalid literal for int() with base 10: '').
This is a real cause of "temperature not updating" — distinct from, and in addition to, the Govee cloud's 15–60 min batching for gateway-bridged sensors covered in v2026.5.14.
Empty / null / non-numeric capability values (brightness, hdmiSource, MQTT brightness) are now tolerated, and the rest of the device's state still parses. Thanks @mattdengler — your v2026.5.13 diagnostics pinned this down.
Full changelog: v2026.5.14...v2026.5.15