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 interact with various aspects of a Homebridge server. Specifically, for the "Server" resource and the "Get Device Pairings" operation, it retrieves information about device pairings managed by the Homebridge server. This is useful for scenarios where you want to programmatically access or audit paired devices connected through Homebridge, such as smart home accessories linked to the server.
Practical examples include:
- Fetching a list of all paired devices to display in a dashboard.
- Verifying device pairings before performing further automation tasks.
- Auditing device connections for security or maintenance purposes.
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 representing the device pairings retrieved from the Homebridge server. The structure typically includes details about each paired device, such as identifiers, pairing status, and related metadata.
If the node supports binary data output (not indicated here), it would represent any associated files or media related to the device pairings, but this is not evident from the provided code.
Dependencies
- Requires an active connection to a Homebridge server API endpoint.
- Needs an API authentication token (access token) to authorize requests.
- The user must configure credentials including the server URL and provide the access token either via a connected Login node or manually.
Troubleshooting
Common issues:
- Invalid or missing access token leading to authorization errors.
- Incorrect server URL configuration causing connection failures.
- Network issues preventing communication with the Homebridge server.
Error messages and resolutions:
- Unauthorized / 401 errors: Verify that the access token is correct and has not expired.
- Connection timeout or network errors: Check network connectivity and server availability.
- Malformed response or parsing errors: Ensure the Homebridge server is running a compatible API version.
Links and References
- Homebridge Official Website
- Homebridge API Documentation (if available)
- n8n documentation on HTTP Request Node for understanding API integrations