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 interacts with the Homebridge API, specifically focusing on managing the Homebridge configuration in this context. The "Get Config Backup" operation allows users to retrieve a backup of their Homebridge configuration by specifying a backup ID. This is useful for scenarios where you want to restore or inspect previous configurations, maintain version control over your setup, or migrate settings between different Homebridge instances.
Practical examples include:
- Automatically fetching a specific configuration backup before applying updates.
- Integrating configuration backups into a broader automation workflow for system maintenance.
- Auditing or exporting configuration states for troubleshooting or documentation purposes.
Properties
| Name | Meaning |
|---|---|
| Access Token | An access token obtained from a prior login operation or entered manually to authenticate requests to the Homebridge API. |
| Backup ID | The numeric identifier of the specific configuration backup to retrieve. This is required to specify which backup to fetch. |
Output
The node outputs JSON data representing the requested configuration backup. This JSON contains the full details of the Homebridge configuration as saved in that backup, allowing downstream nodes or workflows to process, analyze, or restore the configuration.
If the node supports binary data output (not explicitly shown here), it would typically represent the backup file or archive in binary form, but based on the provided code and properties, the output is JSON structured data.
Dependencies
- Requires an active connection to the Homebridge API server.
- Needs an API authentication token ("Access Token") to authorize the request.
- The base URL for the Homebridge API must be configured in the node credentials or environment.
- No additional external services are indicated beyond the Homebridge API itself.
Troubleshooting
- Invalid or missing Access Token: If the access token is incorrect or not provided, the API call will fail authorization. Ensure the token is valid and correctly input.
- Backup ID not found: Providing a non-existent backup ID will result in an error or empty response. Verify the backup ID exists on the Homebridge server.
- Network or connectivity issues: Failure to reach the Homebridge API endpoint can cause timeouts or connection errors. Check network settings and server availability.
- API changes or version mismatches: If the Homebridge API has changed, some operations might fail. Confirm compatibility between the node version and the Homebridge server version.
Links and References
- Homebridge Official Website
- Homebridge API Documentation (if available)
- n8n Documentation on Creating Custom Nodes