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
This node integrates with the Homebridge API, allowing users to control and manage various aspects of a Homebridge server environment. Specifically, the "Stop Child Bridge" operation under the "Server" resource enables stopping a child bridge device within the Homebridge ecosystem. This is useful for administrators or automation workflows that need to programmatically stop specific child bridges, for example, during maintenance, troubleshooting, or automated system management.
Practical examples include:
- Automatically stopping a child bridge before applying configuration changes.
- Temporarily disabling a child bridge when certain conditions are met (e.g., no presence detected).
- Integrating with broader home automation workflows that require dynamic control over Homebridge components.
Properties
| Name | Meaning |
|---|---|
| Access Token | An access token obtained from a prior login operation. If not using a connected login node, enter the token manually here. This token authenticates requests to the Homebridge API. |
| Device ID | The unique identifier of the child bridge device you want to stop. This is required to specify which child bridge to target. |
Output
The node outputs JSON data representing the response from the Homebridge API after attempting to stop the specified child bridge. This typically includes status information about the operation's success or failure.
If the node supports binary data output, it would relate to any binary content returned by the API, but based on the provided code and context, the primary output is JSON structured data reflecting the API response.
Dependencies
- Requires an active connection to a Homebridge server API endpoint.
- Needs an API authentication token (access token) to authorize requests.
- The node expects the user to provide the Homebridge server URL via credentials or environment configuration.
- No additional external services beyond the Homebridge API are required.
Troubleshooting
- Invalid or missing access token: The node will fail if the access token is incorrect or expired. Ensure the token is valid and refreshed as needed.
- Incorrect Device ID: Providing an invalid or non-existent device ID will cause the operation to fail. Verify the device ID corresponds to an existing child bridge.
- Network issues: Connectivity problems to the Homebridge server will prevent the node from executing successfully. Check network settings and server availability.
- API errors: The Homebridge API may return error messages if the server is busy, the child bridge cannot be stopped, or permissions are insufficient. Review the API response message for details.
Links and References
- Homebridge Official Website
- Homebridge API Documentation (if available)
- n8n documentation on Creating Custom Nodes