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
The "Get Accessory" operation of the Homebridge node allows users to retrieve detailed information about a specific HomeKit accessory managed by the Homebridge server. This operation is useful in scenarios where you want to query the current state, configuration, or metadata of an accessory identified by its unique ID. For example, you might use this node to fetch the status of a smart light bulb or thermostat connected through Homebridge to integrate with other automation workflows.
Properties
| Name | Meaning |
|---|---|
| Access Token | An access token obtained from a prior login operation or entered manually for authentication. |
| Unique ID | The unique identifier of the accessory you want to retrieve information about. |
Output
The output JSON contains the data returned by the Homebridge API for the specified accessory. This typically includes all relevant details such as accessory name, type, current characteristics (e.g., on/off state, brightness), and other metadata. The structure mirrors the Homebridge API response for an accessory object.
If the accessory has any binary data (e.g., images or firmware blobs), it would be included in the binary output field, but this operation primarily returns JSON data describing the accessory.
Dependencies
- Requires connection to a Homebridge server with API access enabled.
- Needs an API authentication token (access token) which can be obtained via a login operation or provided manually.
- The node depends on proper configuration of the Homebridge server URL and valid credentials within n8n.
Troubleshooting
- Invalid or missing access token: If the access token is incorrect or expired, the node will fail to authenticate. Ensure the token is valid and refreshed if necessary.
- Incorrect unique ID: Providing a non-existent or malformed unique ID will result in errors or empty responses. Verify the unique ID corresponds exactly to an existing accessory.
- Server connectivity issues: Network problems or incorrect server URL configurations can cause request failures. Confirm that the Homebridge server is reachable from the n8n environment.
- Permission errors: The API user associated with the access token must have sufficient permissions to read accessory data.
Links and References
- Homebridge API Documentation (for detailed API endpoints and accessory data structures)
- n8n Documentation (for general usage of custom nodes and credential management)