Mira Device List All

Get all device connections from Mira App Server

Mira Device List All

AI-generated

Overview

The node "Mira Device List All" retrieves a list of all device connections from the Mira App Server. It is useful in scenarios where you need to fetch and process information about all devices currently connected or registered with the Mira system. For example, this node can be used to monitor device status, inventory devices for management purposes, or trigger workflows based on the presence or attributes of these devices.

Properties

Name Meaning
Token Source Choose where to get the access token from: either from stored credentials ("From Credentials") or from input data / direct entry ("From Input Data").
Server URL The URL of the Mira App Server to connect to (required if Token Source is "From Input Data").
Access Token The access token used for authentication, either provided via input data or entered directly (required if Token Source is "From Input Data").

Output

The node outputs JSON data with the following structure:

  • devices: An array containing all device connection objects retrieved from the Mira App Server.
  • count: The total number of devices returned.
  • timestamp: The ISO string timestamp indicating when the data was fetched.
  • operation: A string indicating the operation performed, here always "listAll".

This output allows downstream nodes to easily iterate over devices, count them, or log the retrieval time.

Dependencies

  • Requires an active Mira App Server accessible via HTTP.
  • Requires an access token for authentication, which can be supplied either through stored credentials or dynamically via input data.
  • No additional external services or environment variables are explicitly required beyond the API endpoint and token.

Troubleshooting

  • Common issues:
    • Incorrect or expired access token will cause authentication failures.
    • Wrong server URL or network connectivity issues will prevent fetching device data.
  • Error messages:
    • Authentication errors typically indicate invalid or missing tokens; verify token source and validity.
    • Network errors suggest checking the server URL and network accessibility.
  • To resolve, ensure the correct token is provided and the Mira App Server URL is reachable.

Links and References

  • Mira App Server API documentation (not provided here) would be helpful to understand device object structure and authentication details.
  • n8n documentation on using credentials and input data for dynamic authentication.

Discussion