v0.8.2 — the missing support link

Added the missing support link. Every Indigo plugin is meant to carry a web address inside its bundle — it is what the "About" item in the Plugins menu opens. This one had the entry but left it blank, so that menu item went nowhere. It now points at this repository. Nothing else changed.

Everything since v0.8.1

• v0.8.2 — add the required CFBundleURLTypes support URL
• ci: cap job runtime at 10 minutes and cancel superseded runs

Installing

Download ESPHomeBridge.indigoPlugin.zip, unzip it, and double-click ESPHomeBridge.indigoPlugin.

v0.8.1 — correcting an encryption key now reconnects

Correcting a node's encryption key now reconnects it, rather than leaving the plugin retrying with the old one. The README has also been reconciled with the one-device-per-node model introduced in 0.4.0, and the plugin now ships the IndigoSecrets_example.py template.

Everything since v0.8

• Ship the IndigoSecrets_example.py template
• docs: reconcile README with the v0.4.0 one-device-per-node model
• v0.8.1 — correcting an encryption key now reconnects the node

Installing

Download ESPHomeBridge.indigoPlugin.zip, unzip it, and double-click ESPHomeBridge.indigoPlugin.

v0.8.0 — ignore list

New: 'Ignore these devices' field in the Configure dialog.

Some hardware advertises ESPHome's mDNS service name and opens port 6053 without actually speaking the protocol — SMLIGHT's Zigbee coordinators are a known example. Since v0.7.0 the plugin parked such nodes rather than retrying forever, but it still warned about them once an hour, every hour.

You can now list MAC addresses, hostnames or IP addresses (comma or space separated) that the plugin should leave alone entirely: never connected to, never parked, never warned about. Ignored nodes show as [IGNORED] in the List Discovered Devices menu item, and changes apply as soon as you save the dialog — no plugin restart needed.

Installation: download ESPHomeBridge.indigoPlugin.zip, unzip it, double-click ESPHomeBridge.indigoPlugin and Indigo installs it automatically.

v0.7.0 — Bounded connect retries, plus the first deep-review batch

See the Recent changes section of the README for what changed and why.

Installation

1. Download ESPHomeBridge.indigoPlugin.zip below
2. Unzip it — you will get ESPHomeBridge.indigoPlugin
3. Double-click ESPHomeBridge.indigoPlugin and Indigo will install it

v0.5.4

ESPHomeBridge 0.5.4 — maintenance and improvement release.

Install: download the .indigoPlugin.zip below, unzip it, and double-click the .indigoPlugin — Indigo installs it. Upgrading from an earlier version works the same way and keeps your settings.

The full run of changes since the previous release is in the README's version history.

v0.5.3 — quieter logging for unadopted encrypted devices

A leftover ESPHome device on the network with API encryption enabled, but not
set up in Indigo, was logged as a red ERROR on every plugin restart. It is now
logged at INFO — the ERROR is kept only for a device you have actually
configured but left without a usable key. No change to device handling.

v0.5.2

Full Changelog: v0.5.0...v0.5.2

v0.5.0 — OTA firmware upload menu

New menu item: Plugins -> ESPHome Bridge -> Upload Firmware (OTA)... lets you push a compiled .bin straight to any ESPHome node from inside Indigo, no browser tab juggling.

• Target device dropdown lists adopted Indigo devices AND mDNS-discovered-but-not-adopted nodes (so encryption-locked devices can still be reflashed)
• Upload runs in a background thread; progress + timing logged to the Event Log
• Device reboots itself ~1 second after a successful upload; the plugin's reconnect loop picks it up automatically on next mDNS announce

Same /update endpoint the in-browser ESPHome web UI uses, just with the file picker and target inside Indigo.

v0.4.4 — auto-populate node info states (IP, MAC, board, firmware)

Every node device now exposes ipAddress, macAddress, boardModel, esphomeVersion as Custom States, populated from mDNS / device_info on every connect — no matter whether the firmware YAML exposes these as entities. If the firmware DOES expose them (e.g. Athom), those entity values take precedence on subsequent updates so DHCP re-leases stay accurate.

v0.4.3 — h:m:s formatting for seconds-unit sensors

Any numeric sensor with unit s (e.g. ESPHome platform: uptime) now gets a human-readable .ui value: uptime = 4295 shows as 1h 11m 35s on control pages. Raw value stays as integer seconds for scripting. Covers any duration/runtime sensor users might add, not just uptime.