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 node interacts with the Homebridge API, specifically providing access to system status information under the "Status" resource. The "Get Uptime" operation retrieves the current uptime of the Homebridge server, which indicates how long the server has been running without interruption.
This node is beneficial for monitoring and maintenance scenarios where users need to track the stability and availability of their Homebridge server. For example, it can be used in automation workflows that alert administrators if the server restarts unexpectedly or has been running for an unusually long time without a reboot.
Properties
| Name | Meaning |
|---|---|
| Access Token | Access token obtained from the Login operation or entered manually for authentication. |
Output
The node outputs JSON data containing the uptime information of the Homebridge server. This typically includes the duration the server has been active since the last start. The exact structure depends on the Homebridge API response but generally provides numeric or string values representing uptime in seconds, minutes, or a formatted time string.
No binary data output is expected from this operation.
Dependencies
- Requires an active connection to the Homebridge API.
- An API access token is necessary for authentication, which can be obtained via a prior login operation or entered manually.
- The node expects the base URL of the Homebridge server to be configured in credentials or environment settings.
Troubleshooting
- Invalid or missing access token: Ensure the access token is correctly provided either from a previous login node or manually. Authentication failures will prevent retrieving uptime.
- Connection issues: Verify that the Homebridge server URL is correct and accessible from the n8n instance.
- API changes: If the Homebridge API changes its endpoints or response formats, the node may fail to parse uptime data correctly. Check for updates or patches to the node.
- Timeouts or slow responses: Network latency or server load might cause delays; consider increasing timeout settings if available.
Links and References
- Homebridge Official Website
- Homebridge API Documentation (if publicly available)
- n8n Documentation on Creating Custom Nodes