Overview
The Tailwind Door Controller node allows users to interact with smart door devices managed by the Tailwind system. It supports operations to retrieve device status, control doors (open or close), and fetch event logs related to devices.
This node is beneficial in scenarios such as:
- Automating access control by remotely opening or closing doors.
- Monitoring door device statuses for security or maintenance.
- Retrieving recent events for audit or alerting purposes.
For example, a user can automate unlocking a specific door at scheduled times or query the current state of a door device before triggering other workflows.
Properties
| Name | Meaning |
|---|---|
| Device | Select the target device to operate on. Searchable list of available devices. |
| Door | Select the specific door within the device to control. Non-searchable list of doors. |
| Action | Choose the action to perform on the door: "Open Door" or "Close Door". |
Output
The node outputs JSON data representing the result of the requested operation:
- For Device - Get operation: JSON object(s) containing the status details of the specified device.
- For Device - Control operation: JSON object(s) confirming the success or failure of the door control action.
- For Event resource operation: JSON array of event objects related to the device, limited by the specified number.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Tailwind Connect API.
- The node communicates with the Tailwind cloud service at
https://connect.gotailwind.com. - Uses internal helper methods to fetch devices, doors, device status, control actions, and events via REST API calls.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Selecting a device or door that does not exist or is inaccessible may result in errors.
- Network connectivity issues can prevent communication with the Tailwind API.
Error Messages:
- Authentication errors typically indicate invalid or expired API tokens; verify and update credentials.
- "Device not found" or "Door not found" errors suggest incorrect selection; ensure the device and door IDs are valid.
- Timeout or network errors require checking internet connection and API availability.
Links and References
- Tailwind Connect API Documentation (for detailed API usage)
- n8n Documentation on Creating Custom Nodes