AircoBridge v1.4.0

Highlights

• Add a graphical automation workspace with temperature, power, mode, time, AND/OR, preset and power blocks.
• Persist automations and activity history, with manual-control overrides and clear live evaluation feedback.
• Add minimum power-state durations. The temperature-control template now waits for 30 minutes of runtime, then runs a 30-minute Clean cycle before switching off.
• Decode live WF-RAC operation data for outdoor-unit power, compressor, valve and coil telemetry.
• Correct per-session energy accounting and preserve totals across restarts and counter resets.

Upgrade

Compose installations can update with make update. The release publishes ghcr.io/crazyhenk44/aircobridge:1.4.0, :1.4 and the refreshed :latest image through GitHub Actions.

AircoBridge v1.3.0

What’s new

• Discover WF-RAC air conditioners through _beaver._tcp.local directly in the setup wizard, with manual address entry retained as a fallback.
• Store a SHA-256 discovery identity instead of exposing or persisting the underlying mDNS service name or MAC address.
• Follow DHCP address changes automatically: the bridge re-resolves a unit after connection failures, updates the runtime and file configuration, and retries the request once.
• Migrate existing file-based configurations at startup when the mDNS mapping is unambiguous.
• Mark already configured units in discovery results and expose addressManaged in air-conditioner snapshots.
• Add multi-interface IPv4 browsing, concurrent-scan coalescing, Linux multicast reply handling, API documentation and automated coverage.

Upgrade notes

• Existing config/aircos.json installations are linked automatically on startup when a unit can be matched safely. The stored discoveryId is a hash; the original service identity is not written to disk.
• Keep AIRCO_MDNS_ENABLED=1 and use host networking so _beaver._tcp.local remains reachable. Set AIRCO_MDNS_INTERFACE to the physical LAN interface on multi-homed hosts.
• Units with addressManaged: true no longer require a static DHCP lease.
• Environment-only configuration cannot be rewritten. Use file-based configuration when learned address changes must survive restarts.

Verified with the complete Node.js test suite, a production Docker build and a live WF-RAC mDNS discovery test.

AircoBridge v1.2.0

What's new

• Added automatic LAN discovery through mDNS-SD as _aircobridge._tcp.local.
• Added a persistent bridge identity in data/bridge-id, allowing integrations such as Homey to recognize the same bridge after its IP address changes.
• Added bridgeId and discovery capability information to GET /api/info.
• Added AIRCO_MDNS_ENABLED and AIRCO_MDNS_INTERFACE configuration options.
• Changed the recommended Docker Compose setup to host networking so link-local multicast discovery reaches the physical LAN.
• Added graceful mDNS startup and shutdown handling, interface validation, automated tests and deployment documentation.

Upgrade notes

• Docker Compose now uses host networking. AIRCO_HTTP_PORT must therefore be available directly on the host.
• Existing installations may still have AIRCO_HTTP_BIND=127.0.0.1 in .env. Change it to 0.0.0.0 or the host's physical LAN IP so Homey and other LAN clients can connect.
• On hosts with NetBird, a VPN, macvlan or other virtual interfaces, set AIRCO_MDNS_INTERFACE to the physical LAN interface or address, for example eth0.
• Preserve the data directory during upgrades. It contains the stable discovery identity in data/bridge-id.
• Docker Desktop users need host networking enabled in Docker Desktop 4.34 or newer. Native Docker Engine on Linux supports it directly.

After updating the configuration, recreate the container with make update for the published image or make up-local for a local build.

v1.1.0

Full Changelog: v1.0.0...v1.1.0

v1.0.0

Full Changelog: https://github.com/CrazyHenk44/AircoBridge/commits/v1.0.0