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 manage various aspects of their Homebridge server environment. Specifically, for the "User" resource and the "Activate OTP" operation, it enables activating a One-Time Password (OTP) code for user authentication purposes. This is useful in scenarios where two-factor authentication (2FA) or enhanced security measures are implemented, requiring users to verify their identity by entering an OTP code.
Practical examples include:
- Activating OTP after a user logs in to enhance account security.
- Enabling 2FA for user accounts managed through Homebridge.
- Automating OTP activation as part of a larger workflow involving user management.
Properties
| Name | Meaning |
|---|---|
| Access Token | An access token obtained from a prior login operation. If not using the Login node, enter manually. This token authenticates the request. |
| OTP Code | The one-time password code that needs to be activated for the user. This is required to complete the OTP activation process. |
Output
The node outputs JSON data representing the response from the Homebridge API after attempting to activate the OTP code. This typically includes confirmation of successful activation or error details if the activation failed.
If the node supports binary data output, it would relate to any files or media returned by the API, but based on the provided code and context, this operation deals solely with JSON responses.
Dependencies
- Requires an active connection to the Homebridge API.
- Needs an API key or access token credential to authenticate requests.
- The base URL for the Homebridge server must be configured in the node credentials.
- The "Access Token" property must be supplied either dynamically from a previous login node or manually.
Troubleshooting
- Invalid or missing access token: Ensure the access token is valid and has not expired. Re-authenticate if necessary.
- Incorrect OTP code: Verify the OTP code entered is correct and has not expired.
- API connectivity issues: Confirm the Homebridge server URL is reachable and the API service is running.
- Permission errors: Check that the access token has sufficient permissions to activate OTP for the user.
Common error messages might include authentication failures or invalid input errors related to the OTP code. Resolving these usually involves verifying credentials and input values.
Links and References
- Homebridge API Documentation (for detailed API endpoints and usage)
- Two-Factor Authentication Concepts (background on OTP and 2FA)