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, specifically allowing users to interact with various Homebridge resources. For the "Server" resource and the "Get Pairing Info" operation, it retrieves pairing information from a Homebridge server. This is useful for scenarios where you need to programmatically access or verify the pairing details of your Homebridge server, such as when managing HomeKit accessory connections or troubleshooting server setups.
Practical examples include:
- Fetching current pairing data to display in a dashboard.
- Automating verification of server pairing status during deployment or maintenance.
- Integrating pairing info retrieval into larger home automation workflows.
Properties
| Name | Meaning |
|---|---|
| Access Token | Access token obtained from a prior login operation or entered manually if not connected. |
Output
The node outputs JSON data containing the pairing information retrieved from the Homebridge server. This typically includes details about paired devices, their identifiers, and related metadata necessary for managing or verifying Homebridge pairings.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to a Homebridge server API endpoint.
- Needs an API authentication token (access token) which can be provided either by connecting a Login node or manually entering it.
- The base URL for the Homebridge server must be configured in the node credentials or environment.
Troubleshooting
- Invalid or missing access token: If the access token is incorrect or absent, the node will fail to authenticate with the Homebridge server. Ensure the token is valid and correctly supplied.
- Connection issues: Network problems or incorrect server URLs will prevent successful API calls. Verify the server URL and network connectivity.
- API changes or version mismatches: If the Homebridge API changes, the node might not retrieve pairing info correctly. Check compatibility and update the node or credentials accordingly.
Links and References
- Homebridge Official Website
- Homebridge API Documentation (if available)
- n8n documentation on creating and using API credential nodes