Start Free Trial

Platform Documentation

Data Push

Data Push sends a payload on demand from NEQTO.ai to an MQTT or WebSocket Device Endpoint. Use the Data Push screen for one-off sends and access to transmission history. For commands you use often, add a Data Push widget to a dashboard.

Supported endpoints: Data Push is available for MQTT and WebSocket endpoints. HTTP/HTTPS endpoints cannot receive a push, so the Data Push action is not available for them. A WebSocket endpoint must have at least one active connection when you submit the push.
Permissions: opening the Data Push screen and sending requires Edit Device Endpoints. Loading destinations and history also requires View Device Endpoints. Creating or editing a Data Push widget requires Create widgets or Edit widgets, respectively. A control may be hidden, or its request may fail, when your role does not provide the required access.
Plan limits: Data Push is subject to the account’s monthly push allowance and per-minute push rate. Each payload that passes validation and the plan checks is counted before delivery is attempted, so a later Failed status still counts. A multi-command Button widget submits each command as a separate push.

Supported Data

Enter the payload as text. NEQTO.ai determines whether to send it as Text, JSON, or Binary data. The 4,096-character input limit includes formatting spaces, line breaks, and binary separators.

Format How NEQTO.ai recognizes and sends it Input limit
Text Any input not recognized as JSON or Binary. Leading and trailing whitespace is removed before transmission. 4,096 characters
JSON A valid JSON object or array whose first character is { or [. NEQTO.ai parses the value and removes formatting whitespace before transmission. 4,096 input characters, before minification
Binary A nonempty, even-length sequence of hexadecimal digits. Internal spaces and hyphens are ignored when the value is converted to bytes. 2,048 bytes when entered as 4,096 hexadecimal digits without spaces or hyphens
Format detection details:
  • If the input begins or ends with whitespace, NEQTO.ai trims that whitespace and sends the remaining value as Text. It does not then try to interpret the value as JSON or Binary.
  • To send an even-length, hexadecimal-only value such as 1234 as Text, add a trailing space. The space forces Text classification and is removed before transmission.
  • Top-level JSON primitives such as "ready", true, or 12 are not classified as JSON. They are handled as Text or, when the value is an even-length hexadecimal sequence, as Binary.
WebSocket protocol compatibility: a JSON-protocol WebSocket connection can receive Text, JSON, or Binary frames. WebSocket connections using the ArubaOS 8 or ArubaOS 10 protobuf protocols accept Binary payloads only. Text and JSON payloads are not sent to those clients, so enter the payload as hexadecimal data.

Send from the Data Push Screen

You open this screen from an endpoint’s Action menu on the Devices > Device Endpoints list. One dialog holds the payload field, the send action, and the transmission history for that endpoint.

Open the Data Push screen

  • 1
    Open Devices > Device Endpoints. Find the target endpoint, open its three-dot Action menu, and select Data Push.
    Device Endpoints list with the three-dot Action menu open for a WebSocket endpoint. The menu contains View Details, Data Push, Delete, and Edit, with Data Push highlighted.
    Open Data Push from the target endpoint’s Action menu.
  • 2
    Confirm the Destination device endpoint. The Payload field shows a character counter, such as 0 / 4096.
    Data Push dialog for a WebSocket endpoint with a Destination device endpoint field; an empty Payload field whose placeholder says String, JSON, or binary data as a hexadecimal string; a 0 / 4096 counter; History and Help buttons; and Cancel and Submit buttons.
    Confirm the endpoint before entering a payload.
MQTT destination: for an MQTT endpoint, the dialog also shows the read-only control topic where the payload will be published. Data Push widgets use the same endpoint control topic; the user interface does not provide a topic override.
Data Push dialog for an MQTT endpoint with a Destination topic field showing a ctrl/v1 control topic between the endpoint and Payload fields.
The MQTT destination topic is shown before you send.

Enter and send a payload

Enter the payload and select Submit. A success toast means NEQTO.ai accepted the request. Transmission runs asynchronously, so the toast is not a device-level acknowledgement. Use transmission history to check whether processing is Pending, Succeeded, or Failed.

Data Push dialog with the text Hello, this is a test message from NEQTO ai. in the Payload field, a 44 / 4096 counter, the Submit button highlighted, and a Success! Data has been pushed toast.
The success toast confirms that the push request was accepted.

JSON and Binary examples

JSON can include spaces and line breaks inside the object or array for readability. NEQTO.ai sends the parsed value in compact form.

Data Push dialog containing a multiline JSON object with temperature, humidity, and mode fields, a 59 / 4096 counter, and a Success! Data has been pushed toast.
A valid JSON object is minified before transmission.

Enter Binary data as hexadecimal byte pairs. For example, 010300000002C40B is eight bytes. Letter case does not matter. You may place spaces or hyphens between byte pairs, but do not add whitespace before the first digit or after the last digit.

Data Push dialog containing the hexadecimal Binary payload 010300000002C40B, a 16 / 4096 counter, and a Success! Data has been pushed toast.
Binary data is entered as an even number of hexadecimal digits.

View and reuse transmission history

History includes pushes sent to this endpoint from the Data Push screen and from dashboard widgets. Entries are retained according to the account plan.

  • 1
    Select the History button at the top right of the dialog.
    History button highlighted at the top right of the Data Push dialog beside the Help button.
    Open transmission history from the History button.
  • 2
    Review the entries, with the newest first. Each row shows a TEXT, JSON, or BIN badge; the send time in your local time zone; and a Pending, Succeeded, or Failed status. When a reason is available, hover over the status to read it.
    Data Push history table with Payload, Sent, and Status columns. Rows have BIN, JSON, and TEXT badges and Succeeded or Failed statuses. Pagination at the bottom reads Page 1 of 15.
    History shows the format and processing result of each push.
How to read status: Pending means the push is queued, running, or waiting for a retry. Succeeded means the platform completed its send operation, not that the device application acknowledged or acted on the payload. Failed means the platform could not complete the send. A WebSocket push with no active connection fails immediately.

From the history view, you can:

  • Return to payload entry: select the back button at the top of the dialog.
    Back arrow button highlighted at the top right of the Data Push history view.
    Return to the Payload field without closing the dialog.
  • Navigate history: each page contains up to 10 entries. Use Previous or Next, or select the page indicator to jump to a specific page.
    Data Push history with the Page 1 of 15 indicator highlighted and a selector listing pages 1 through 15.
    Use the page controls to browse older entries.
  • Reuse a payload: select its payload in the history table. NEQTO.ai returns to the input view and fills the Payload field. JSON is formatted for readability, and Binary data is restored as hexadecimal digits.
    A TEXT history row beginning Hello, this is a test message from, highlighted for reuse.
    Select a payload to reuse it.
    Payload field filled with the reused text Hello, this is a test message from NEQTO ai. and a 45 / 4096 counter.
    The selected value is ready to review or resend.
    Reused Text may show one extra character: NEQTO.ai adds a trailing space when it restores Text so that a hexadecimal-looking value is not reclassified as Binary. The space is stripped if you submit the payload, so it does not change the transmitted Text.

Send from a Widget

A Data Push widget places a reusable Form or Button control on a dashboard.

Create a Data Push widget

  • 1
    Open the dashboard and select Create Widget (+) in the toolbar.
    Create Widget plus button highlighted in the dashboard toolbar with its Create Widget tooltip visible.
    Start from the dashboard’s Create Widget button.
    Create Widget dialog with a locked Dashboard field, Widget Title set to demo, an optional Description field, a Widget Type menu, and a Preview panel.
    Enter the widget’s shared settings before choosing its type.
  • 2
    Under Widget Type, select Data Push.
    Widget Type menu listing Chart, Single Status, Multi Status, Data Push, and XY-Chart, with Data Push highlighted.
    Select Data Push as the widget type.
  • 3
    Under Style, select Form or Button.
    Style menu for a Data Push widget with Form selected and Button available. Button Label and Default Payload fields appear below, with a Form-style widget in Preview.
    Choose whether users enter a payload or run saved commands.
  • 4
    Select the destination Device Endpoint. MQTT and WebSocket endpoints are available; HTTPS endpoints are shown as unsupported and cannot be selected.
    Destination device endpoint menu with demo HTTP marked HTTPS not supported and disabled, demo MQTT available, and demo Websocket selected.
    Select an MQTT or WebSocket destination.
  • 5
    Enter the required Button Label, then configure the selected Style:
    • Form: optionally enter a Default Payload. It pre-fills the dashboard field, and the person using the widget can edit it before each send.
    • Button: enter the saved command payloads. A Button has at least one command slot and supports up to four. Use + to add a command or the delete button to remove one when more than one exists.
    Form-style Data Push widget configuration with Hello, this is a test message from NEQTO ai in Default Payload and the same editable text in Preview.
    Form Style can start with an optional default payload.
    Button-style Data Push widget configuration with Command 1 set to Hello, this is a test message from NEQTO ai., an Add command button, and a large Submit button in Preview.
    Button Style stores up to four command payloads.
  • 6
    Select Save. The widget is added to the dashboard.
    Completed Form-style Data Push widget configuration with Save highlighted at the bottom right.
    Save the configured widget.
    Saved demo Form-style Data Push widget on a dashboard, showing its default payload and Submit button.
    The saved widget is ready to use from the dashboard.
The editor Preview never sends data: the control in Preview looks and behaves like the saved widget, but selecting its button does not make a push request. Hover over the button to see the Preview only — no data is sent hint.

Send from the saved widget

  • Form: review or edit the payload, then select its submit button. The current field value is sent once.
  • Button: select the button once to send every configured command sequentially in the displayed order. If one request fails, the remaining commands are not attempted.
No confirmation dialog: a saved widget starts sending as soon as you select its button. The button is disabled while its request or command sequence is running. Each Button command creates a separate history entry. A four-command Button can therefore make up to four pushes with one selection.

A success toast means each attempted push request was accepted. Check the endpoint’s Data Push history for the final processing status, especially when the endpoint’s connection may have changed.

Dashboard with demo Form-style and Button-style Data Push widgets and a Success! Command pushed toast after a send.
A saved Form or Button widget sends without a confirmation dialog.
Start Free Trial