Overview
This node, named "Tailwind Door Controller," allows users to interact with devices and events related to Tailwind door systems. Specifically, for the Device - Get operation, it retrieves the current status of a selected device. This is useful in scenarios where you want to monitor the state or condition of a door controller device remotely, such as checking if a door is open, closed, or locked.
Practical examples include:
- Automating alerts when a door's status changes.
- Integrating door status into broader home or building automation workflows.
- Logging device status periodically for audit or maintenance purposes.
Properties
| Name | Meaning |
|---|---|
| Device | Select the specific device to retrieve information from. The device can be searched and chosen from a list of available devices. |
Output
The output is a JSON array containing the status information of the requested device. Each item in the output corresponds to one device status object returned by the API. The exact structure depends on the device status data but typically includes fields describing the device's current state.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential to authenticate requests to the Tailwind Connect API.
- The node communicates with the Tailwind Connect service at
https://connect.gotailwind.com. - It depends on internal helper methods to fetch device status and construct execution metadata.
Troubleshooting
Common issues:
- If the device ID is invalid or not found, the node may return an empty result or an error.
- Network connectivity problems can cause request failures.
- Missing or incorrect API credentials will prevent successful authentication.
Error messages:
- Authentication errors indicate invalid or missing API keys; ensure the correct API key credential is configured.
- "Device not found" or similar errors suggest the selected device does not exist or is inaccessible; verify the device selection.
- Timeout or network errors require checking internet connectivity and API availability.
Links and References
- Tailwind Connect API Documentation (for detailed API capabilities)
- n8n documentation on creating custom nodes