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, for the "Server" resource and the "Restart Child Bridge" operation, it enables restarting a child bridge device within the Homebridge ecosystem. This is useful in scenarios where a child bridge becomes unresponsive or requires a reset without restarting the entire Homebridge server.
Practical examples include:
- Restarting a specific child bridge after configuration changes.
- Automating recovery procedures for child bridges that fail or disconnect.
- Managing multiple child bridges remotely via workflow automation.
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 to be restarted. |
Output
The node outputs JSON data representing the response from the Homebridge API after attempting to restart the specified child bridge. This typically includes status information about the restart operation, such as success confirmation or error details.
If the node supports binary data output (not evident from the provided code), it would relate to any files or media returned by the API, but this is not indicated here.
Dependencies
- Requires an active connection to a Homebridge server API endpoint.
- Needs an API access token for authentication, which can be supplied either by connecting a prior login node or manually entering the token.
- The base URL for the Homebridge server must be configured in the node credentials or environment.
Troubleshooting
Common Issues:
- Invalid or expired access token leading to authentication failures.
- Incorrect or missing device ID causing the API to reject the restart request.
- Network connectivity problems preventing communication with the Homebridge server.
Error Messages:
- Authentication errors indicating invalid tokens: Ensure the access token is current and correctly entered.
- Device not found or invalid device ID: Verify the device ID corresponds to an existing child bridge.
- Timeout or connection errors: Check network settings and server availability.
Links and References
- Homebridge Official Website
- Homebridge API Documentation (if available)
- n8n Documentation on Creating Custom Nodes