[RELEASE] Konnected Garage Door Opener Official Driver

nate · July 30, 2026, 9:54pm

Great. Here is the actual fix. I’ll be pushing it thru ASAP:

github.com/bradsjm/hubitat-public

Declare API 1.14 and derive object_id when the device omits it

main ← konnected-io:pr/api-1.14-object-id-derivation

opened 09:46PM - 30 Jul 26 UTC

heythisisnate

+58 -5

## The problem ESPHome **2026.7.0 stopped sending `object_id` to every API clie…nt**, which breaks entity identification for any driver that keys off it. Six of the bundled example drivers in this repo are affected and will silently match nothing against 2026.7+ firmware: `ESPHome-AthomHumanPresenceSensor`, `ESPHome-EverythingPresenceOne`, `ESPHome-MultiSwitch`, `ESPHome-MultiSwitchSensor`, `ESPHome-MultiContactSensor`, `ESPHome-UpsyDesky` ### How we got here `espHomeHelloRequest()` only ever sent `client_info` (field 1) — never `api_version_major` (2) or `api_version_minor` (3). Devices therefore recorded this client as API **0.0** and, since 2026.1, log: ``` '<client>' using outdated API 0.0, update to 1.14+ ``` That was cosmetic until it wasn't: - ESPHome **2026.1** ([esphome#12698](https://github.com/esphome/esphome/pull/12698)) removed `object_id` from the protocol and bumped the API to 1.14, but kept sending it to sub-1.14 clients behind a backward-compat branch. Reporting 0.0 put us in that branch — the only reason this library kept working. - ESPHome **2026.7.0** ([esphome#17108](https://github.com/esphome/esphome/pull/17108), merged 2026-06-21) deleted that branch. `fill_and_encode_entity_info` no longer sets `object_id` for anyone, so it now arrives empty **regardless of the version a client declares**. ## The fix **FIX-16** — send `api_version_major`/`minor` in `HelloRequest`. I checked all 33 files of the `api` component at tag `2026.7.3`: `client_supports_api_version()` is referenced in exactly one place — the deprecation warning itself — so declaring 1.14 changes no other device behavior. **FIX-17** — `parseEntity()` derives `objectId` from the entity name when the wire field is empty, mirroring ESPHome's `str_sanitize(str_snake_case(name))`. The wire value still wins when present, so one path covers pre-2026.1, 2026.1–2026.6, and 2026.7+ firmware. > ⚠️ The two changes are **only correct together**. On 2026.1–2026.6, declaring 1.14 without the derivation would tell devices to stop sending `object_id` and break firmware that currently works. The derivation is deliberately byte-wise rather than `name.toLowerCase().replaceAll(...)`, which is wrong twice: ESPHome walks the UTF-8 *bytes* (a multi-byte character becomes one underscore **per byte**), and `String.toLowerCase()` is locale-sensitive. ## Why this may not look broken yet Existing installs can appear unaffected — drivers persist entity keys in `state`, and the `key` (an `object_id` *hash* computed on-device) is unchanged. The failure surfaces on a fresh pair, a driver reinstall, or any driver that re-resolves `objectId` → `key` on reconnect. ## Verification No hub in the loop, since Hubitat's injected symbols don't exist offline: - Full-file parse to `Phases.CONVERSION` under Groovy **2.4.21 and 3.0.21** — both clean. - `deriveObjectId()` type-checks under `@CompileStatic` on both and passes 13 cases, cross-checked against an independent port of the C++ algorithm. Covers awkward real-world names (`'Security+ Protocol'` → `security__protocol`, `'Pre-close warning'` → `pre-close_warning`) and multi-byte UTF-8. - `HelloRequest` encodes to `000F010A09<client>1001180E` — `10 01` = major 1, `18 0E` = minor 14, confirming `protobufEncode`'s falsy-skip doesn't drop them. **Confirmed on hardware:** a garage door controller on ESPHome 2026.7.x that was looping connect → 30s → disconnect now stays connected. That 30s was `SEND_RETRY_SECONDS * (SEND_RETRY_COUNT + 1)` — the supervision give-up in `sendMessageQueue()`, reached because a command sent with an unlearned entity key matches nothing on the device, so the expected state response never arrives and `closeSocket()` tears it down. ## Notes - Bumps `API_HELPER_VERSION` to `1.3.2`. - The second commit regenerating `ESPHome-API-Library-Bundle.zip` was produced automatically by `update-bundle.yml`, which runs on a push to any branch — not hand-edited. Verified the entry name is still `esphome.espHomeApiHelper.groovy`. Happy to drop that commit if you'd rather regenerate it on merge. 🤖 Generated with [Claude Code](https://claude.com/claude-code)