Govee 3.1.1: API load, brightness, status fixes

A patched Govee node server for PG3x/eISY is up to 3.1.1. This version fixes the API-heavy polling, wrong brightness values and misleading status of the original. It builds on Jean-Francois Tremblay's (AutomationGeek) node server and the govee-api-laggat library. 💡

Source: github.com/superflytnt/udi-govee-nodeserver
Latest release: v3.1.1

What this version fixes

• One shared, long-lived Govee client and a single state sweep per poll, instead of every light fetching the device list plus each light's state. An 8-light setup drops from roughly 72 requests per cycle to 8.

• An API-budget check before each polling request leaves headroom for commands, and commands use the warm device cache, so you burn far less of Govee's per-minute limit.

• Correct 0-254 to percentage brightness conversion, including the first brightness command after startup.

• Offline devices show last-known status with an offline notice instead of stale data posing as a fresh reading.

• Failed commands report a notice instead of an optimistic success status.

• Optional heartbeat monitoring: set the heartbeat_url custom parameter to any heartbeat/cron-monitor URL for missed-poll alerts (pings on short polls, at most once per 60 seconds).

Polling: the tested setup is a 900-second short poll and 1800-second long poll; the published defaults are 90/600 seconds. Match your heartbeat monitor's expected interval to your actual cadence.

This fork still uses Govee's legacy developer API, so app groups, sync boxes and new-API-only devices are out of scope. Tested on six reachable lights.

Give it a try and post your device models and results here.

Edited Sunday at 04:49 PM3 days by kaplansa