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, the "Server" resource with the "Get Cached Accessories" operation enables retrieval of cached accessory data from the Homebridge server. This is useful for scenarios where you want to quickly access the current state or configuration of accessories managed by Homebridge without querying each accessory individually.
Practical examples include:
- Fetching the list of cached accessories to display their status in a dashboard.
- Using cached accessory data as part of an automation workflow that reacts to device states.
- Debugging or monitoring Homebridge accessories by retrieving their cached information.
Properties
| Name | Meaning |
|---|---|
| Access Token | Access token obtained from the Login operation or entered manually if not connected to Login node. Used to authenticate requests to the Homebridge server API. |
Output
The node outputs JSON data representing the cached accessories retrieved from the Homebridge server. The structure typically includes details about each accessory such as its identifier, name, type, and current state or attributes as stored in the cache.
If the node supports binary data output (not indicated here), it would represent accessory-related files or media, but this node primarily deals with JSON data.
Dependencies
- Requires 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 prior login node or manually.
Troubleshooting
- Invalid or missing access token: The node will fail to authenticate if the access token is incorrect or absent. Ensure the token is valid and correctly provided.
- Connection issues: If the Homebridge server URL is unreachable, check network connectivity and server status.
- Unexpected response format: If the server returns unexpected data, verify that the Homebridge API version matches the node's expectations.
- Empty cached accessories: This might indicate no accessories are currently cached or the server has not yet populated the cache.
Links and References
- Homebridge Official Website
- Homebridge API Documentation (if available)
- n8n documentation on Creating Custom Nodes