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 interacts with the Homebridge API, specifically allowing users to retrieve system status information such as CPU details. It is useful for monitoring the health and performance of a Homebridge server by fetching real-time CPU info. Practical applications include automated system diagnostics, alerting on high CPU usage, or integrating Homebridge status into broader home automation dashboards.
Properties
| Name | Meaning |
|---|---|
| Access Token | Access token obtained from a prior login operation or entered manually to authenticate API requests. |
Output
The node outputs JSON data containing the CPU information retrieved from the Homebridge server's status endpoint. This typically includes metrics such as CPU load, usage percentages, core counts, or other relevant CPU statistics provided by the Homebridge API. The output does not include binary data.
Dependencies
- Requires an active connection to a Homebridge server.
- Needs an access token for authentication, which can be obtained via a login operation or entered manually.
- The node expects the Homebridge server URL to be configured in credentials or environment settings.
Troubleshooting
- Invalid or missing access token: Ensure the access token is correctly provided either from a login node or manually. Authentication failures will prevent data retrieval.
- Connection issues: Verify that the Homebridge server URL is correct and accessible from the n8n instance.
- API changes: If the Homebridge API changes, the node might fail to parse CPU info correctly; check for updates to the node or API documentation.
- Empty or unexpected output: Confirm that the Homebridge server is running and reporting status data.
Links and References
- Homebridge Official Website
- Homebridge API Documentation (if available)
- n8n documentation on creating and using custom nodes