Ewelink icon

Ewelink

Consume Ewelink API

Overview

The Ewelink custom n8n node allows you to interact with devices managed by the eWeLink API. Specifically, for the Device resource and the Get Firmware Version operation, this node retrieves the current firmware version of a specified device. This is useful in scenarios where you need to monitor device software versions, automate update checks, or ensure compatibility across your IoT fleet.

Practical examples:

  • Automatically check if any device in your smart home setup requires a firmware update.
  • Log firmware versions for compliance or inventory management.
  • Trigger alerts or workflows when a device is running outdated firmware.

Properties

Name Type Meaning
Device ID String The unique identifier of the device whose firmware version you want to retrieve.

Output

The output will be a JSON object containing information about the firmware version of the specified device. While the exact structure depends on the response from the eWeLink API, it typically includes fields such as:

{
  "deviceid": "1000abcdef",
  "fwVersion": "3.5.0",
  // ...other device details
}
  • deviceid: The unique ID of the device queried.
  • fwVersion: The current firmware version installed on the device.
  • Additional fields may be present depending on the API's response.

Dependencies

  • External Service: Requires access to the eWeLink API.
  • Credentials: You must configure valid eWeLink account credentials (email and password) in n8n under the credential type ewelinkApi.
  • Node Dependency: Uses the ewelink-api npm package.

Troubleshooting

Common Issues:

  • Authentication failed: If credentials are incorrect or expired, you may see an error like Auth settings are not valid: Authentication failed - status 406. Double-check your email and password in the n8n credentials.
  • Invalid Device ID: If the provided Device ID does not exist or is not accessible, the node may return an error message indicating the device was not found.
  • API Rate Limits or Connectivity: Network issues or hitting API rate limits can cause failures; retry after some time or check your network connection.

Error Handling:

  • If "Continue On Fail" is enabled, errors will be returned in the output as { "error": "<error message>" }.

Links and References

Discussion