Connect Apple Home to Eddy Bridge V2 with Homebridge

Eddy Bridge V2 brings Eddy’s device control to Windows, macOS and Linux, including Raspberry Pi. Its optional Homebridge plugin exposes configured televisions, switches and outlets to Apple Home while the bridge agent handles the device commands.

The plugin is available from Tiny Electrons on GitHub. Download the plugin archive from Releases and follow the installation guide. The 0.5.0 preview requires Eddy Bridge V2 on the same computer and an existing Homebridge 2.4 installation.

Where the work happens

Apple Home sends a request to Homebridge. The Eddy plugin forwards the device ID and action to the local Eddy Bridge V2 agent over an authenticated connection. The agent looks up the configured command, executes it and returns the result. Device addresses, IR codes, CEC sessions and protocol adapters stay in the agent.

This keeps the plugin small and gives HomeKit actions the same command ordering, timeouts and trace logs as website commands. A failed or uncertain action is not automatically sent again.

Power status comes from the device

A command being sent does not prove a television turned on. Each Homebridge device therefore needs a real power query: CEC, Roku TV, DirecTV or a device HTTP endpoint with explicit on/off response mappings. The agent queries power after actions and the plugin refreshes status periodically. When feedback fails, HomeKit reports the accessory unavailable instead of assuming it is off.

Televisions can expose configured inputs, remote keys and speaker commands. IR-only equipment needs a separate feedback source to report physical power. CEC requires compatible hardware; most Macs and Windows computers need a USB-CEC adapter.

Installing the optional plugin

Install Homebridge using its official platform instructions, then install the downloaded plugin archive in that Homebridge environment. Enable Homebridge access in Eddy Bridge V2, configure the devices in the agent and point the plugin to the agent’s private connection file. The README includes the platform configuration and an example television mapping.

For example, preserve the existing agent settings and add "homebridge_enabled": true to agent.json, then restart the agent. Save the provided example-devices.json as homebridge-devices.json beside the connection file; it includes a television controlled by CEC. Change the mappings to match your equipment.

Install the downloaded archive in Homebridge’s Node environment:

npm install -g /absolute/path/homebridge-eddy-bridge-v2-0.5.0.tgz

On Windows, use a quoted Windows path in the Homebridge terminal. Then add this platform entry to Homebridge’s configuration, replacing the connection path:

{"platforms":[{"platform":"EddyRPC","name":"Eddy Bridge V2","connection_file":"/absolute/path/homebridge-connection.json","poll_seconds":5}]}

For desktop installs the connection file is beside the private agent.json. The Pi service uses /var/lib/eddy-agent/homebridge-connection.json. Homebridge needs read access to that file and the referenced private token; use the same OS account or narrowly scoped ACLs. Do not make the token world-readable. Restart Homebridge after installing and configuring the plugin.

The plugin archive does not include the Eddy Bridge V2 agent. Agent installer downloads are paused during the server migration, so this preview is for users with the matching 0.5.0 agent already installed.

Televisions appear as external HomeKit accessories and are paired separately using Homebridge’s instructions. Existing pairings from the original Eddy bridge do not migrate automatically. Homebridge/config-ui-x manages its own service; the Eddy tray manages the bridge agent.

What changes from the original bridge

The original Homebridge integration shipped inside Eddy’s Raspberry Pi operating-system image. V2 separates the portable device-control agent from optional integrations. The plugin runs in Homebridge; the device logic runs in Eddy Bridge V2.

V2 includes command adapters for the existing entertainment protocols, persistent CEC and observed power feedback. Individual model support, authorization requirements and CEC hardware still matter. The 0.5.0 preview uses protocol fixtures and Homebridge service tests; real-device acceptance and Apple Home pairing across all supported platforms remain release checks.