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 "Deactivate OTP" operation, it enables deactivating the One-Time Password (OTP) feature for a user account. This is useful in scenarios where a user wants to disable two-factor authentication temporarily or permanently, such as when changing devices or troubleshooting login issues.
Practical examples include:
- Disabling OTP after losing access to the authenticator app.
- Temporarily turning off OTP during maintenance or configuration changes.
- Managing user security settings programmatically within an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Access Token | The access token obtained from a prior login operation. If not connected to a login node, enter manually. Used to authenticate the request. |
| Password (for OTP Deactivation) | The user's password required to confirm and authorize the deactivation of OTP. This is sent securely in the request body. |
Output
The node outputs JSON data representing the response from the Homebridge API after attempting to deactivate OTP for the user. This typically includes confirmation of success or details about any errors encountered.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Homebridge API server.
- Needs an API key credential that provides the base URL and authorization headers.
- The "Access Token" must be valid and associated with the user whose OTP is being deactivated.
- Proper permissions on the Homebridge server to perform user management operations.
Troubleshooting
- Invalid or expired access token: The operation will fail if the provided access token is invalid or expired. Ensure the token is current and correctly entered.
- Incorrect password: The password used for OTP deactivation must be correct; otherwise, the API will reject the request.
- Insufficient permissions: The authenticated user must have rights to modify OTP settings. Lack of permissions will result in authorization errors.
- API connectivity issues: Network problems or incorrect server URLs can cause failures. Verify the Homebridge server URL and network accessibility.
- Missing required fields: The password field is mandatory; omitting it will cause validation errors.
Links and References
- Homebridge Official Documentation
- Homebridge API Reference (if available)
- n8n documentation on HTTP Request Node for understanding API interactions