Actions77
- Accessory Actions
- Authentication Actions
- Backup & Restore Actions
- Config Editor Actions
- Platform Tool Actions
- Plugin Actions
- Server Actions
- Restart Server
- Restart Child Bridge
- Stop Child Bridge
- Start Child Bridge
- Get Pairing Info
- Reset Homebridge Accessory
- Reset Cached Accessories
- Get Cached Accessories
- Delete Cached Accessories
- Delete Cached Accessory
- Get Device Pairings
- Get Device Pairing
- Delete Device Pairing
- Get Unused Port
- Get Network Interfaces
- Get Bridge Network Interfaces
- Set Bridge Network Interfaces
- Setup Wizard Actions
- Status Actions
- User Actions
Overview
The "Homebridge" node allows interaction with the Homebridge API, which is used to control and manage Homebridge servers and their components. Specifically, the "Start Child Bridge" operation under the "Server" resource enables users to start a child bridge device within a Homebridge server environment. This is useful in scenarios where multiple child bridges are managed by a single Homebridge instance, and you want to programmatically start one of these child bridges.
Practical examples include:
- Automating the startup of specific child bridges after maintenance or updates.
- Integrating Homebridge child bridge management into larger home automation workflows.
- Restarting or starting child bridges remotely via n8n workflows.
Properties
| Name | Meaning |
|---|---|
| Access Token | An access token obtained from a prior login operation or entered manually for authentication. |
| Device ID | The unique identifier of the child bridge device that you want to start. |
Output
The node outputs JSON data representing the response from the Homebridge API when attempting to start the specified child bridge. This typically includes status information about the operation's success or failure and any relevant details about the child bridge state after the start command.
If the API returns binary data (not indicated here), it would represent raw data related to the child bridge, but this node primarily deals with JSON responses.
Dependencies
- Requires an active connection to a Homebridge server API.
- Needs an API key or access token for authentication, which can be provided either through a connected Login node or manually entered.
- The node expects the Homebridge server URL to be configured in credentials or environment variables.
Troubleshooting
Common Issues:
- Invalid or missing access token: Ensure the access token is correct and has not expired.
- Incorrect device ID: Verify the device ID corresponds to an existing child bridge.
- Network connectivity problems: Confirm that the Homebridge server is reachable from the n8n instance.
Error Messages:
- Authentication errors usually indicate invalid or missing tokens; re-authenticate or provide a valid token.
- "Device not found" errors suggest the device ID does not match any child bridge; double-check the ID.
- Timeout or connection refused errors imply network issues; verify server availability and firewall settings.
Links and References
- Homebridge Official Website
- Homebridge API Documentation (if available)
- n8n Documentation on Creating Custom Nodes