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 Reset Cached Accessories operation, the node sends a request to reset the cached accessories on the Homebridge server. This can be useful when accessory data is stale or corrupted, and you want to force Homebridge to refresh its accessory cache.
Practical scenarios include:
- After updating or removing accessories manually in the Homebridge configuration.
- Troubleshooting issues where accessories do not appear correctly in HomeKit.
- Forcing a refresh of accessory states without restarting the entire Homebridge server.
Properties
| Name | Meaning |
|---|---|
| Access Token | An access token obtained from a prior login operation or entered manually if not using login. It authenticates the request to the Homebridge server. |
Output
The node outputs JSON data representing the response from the Homebridge API after attempting to reset the cached accessories. The structure typically includes status information about the reset operation. There is no indication that binary data is output by this node.
Dependencies
- Requires an active connection to a Homebridge server with API access enabled.
- Needs an API authentication token (access token) to authorize requests.
- The node expects the base URL of the Homebridge server to be configured in credentials or environment variables.
- No additional external services are required beyond the Homebridge API.
Troubleshooting
- Invalid or missing access token: The node will fail if the access token is incorrect or absent. Ensure the token is valid and corresponds to a logged-in session or manually provided.
- Connection errors: If the Homebridge server URL is incorrect or unreachable, the node cannot perform the reset. Verify network connectivity and server address.
- API permission issues: The token used must have sufficient permissions to reset cached accessories; otherwise, the API may reject the request.
- Unexpected API responses: If the Homebridge server version is incompatible or the API changes, the node might receive unexpected responses. Check for updates to the node or Homebridge API documentation.
Links and References
- Homebridge Official Website
- Homebridge API Documentation (if available)
- n8n Documentation on Creating Custom Nodes