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 search for plugins available in the Homebridge ecosystem. It is useful for scenarios where you want to programmatically find and retrieve information about Homebridge plugins based on a search term. For example, you might use this node to automate plugin discovery workflows or to build dashboards that display plugin options matching certain criteria.
Properties
| Name | Meaning |
|---|---|
| Access Token | An access token obtained from a prior login operation or entered manually for authentication with the Homebridge API. This token authorizes the request. |
| Search Query | The search term used to query Homebridge plugins. This is a required field specifying what plugins to look for. |
Output
The node outputs JSON data containing the results of the plugin search query. The structure typically includes details about each plugin matching the search term, such as plugin name, description, version, and other metadata provided by the Homebridge API.
If the node supports binary data output (not explicitly shown here), it would represent any plugin-related files or assets returned by the API, but this is not indicated in the provided code.
Dependencies
- Requires an active connection to the Homebridge API.
- Needs an API access token for authentication, which can be obtained via a separate login operation or entered manually.
- The base URL for the API is configured through credentials, which must include the Homebridge server URL.
- The node depends on standard HTTP headers for JSON communication (
Accept: application/jsonandContent-Type: application/json).
Troubleshooting
- Invalid or missing access token: If the access token is incorrect or absent, the API will reject requests. Ensure the token is valid and correctly supplied.
- Empty or invalid search query: Since the search query is required, leaving it empty will likely cause errors or no results. Always provide a meaningful search term.
- API connectivity issues: Verify that the Homebridge server URL is correct and reachable from your n8n instance.
- Unexpected API responses: If the API changes or returns unexpected data, the node may fail to parse results properly. Check for updates or API documentation changes.