Skip to main content
This page describes how the WiFi API exposes device information, live status, configuration settings, service commands, and debug data for the Melody hardware device. All examples here assume you are calling the WiFi-related endpoints on:
with standard headers:

Device Information (Read)

Static information about the connected Melody device. These values are typically returned by a device info or status endpoint and rarely change during normal operation (except firmware version after OTA).

Device Status (Read)

Dynamic operational data from the Melody device. Use these fields to show battery state, thermal status, and connectivity health in your UI.

Device Settings (Read/Write)

Configurable parameters that control connectivity and naming. When updating settings, make sure your UI clearly reflects any changes that could disconnect the current control channel (for example, disabling WiFi while using WiFi).

Service Commands (Write)

Service commands trigger specific system-level actions on the device. Send them via POST /device/maintenance/command with a JSON body containing command and, where applicable, additional parameters.
Important: Calibration and OTA may move the stroker or restart the device. Always require explicit user confirmation before triggering these commands.
Example — navigate to WiFi screen:

Current Screen (Read)

Read the screen currently shown on the device display.
Response:
Available screen IDs:
IDs 1 (Intro), 4 (Playback), 16 (Battery Warning), and 17 (Overheat Warning) are intentionally omitted — these screens are shown automatically by the device and cannot be navigated to directly.

Firmware Update Info (Read)

Information about firmware update availability and state. You can use these fields to show firmware banners in your UI and decide when to surface “Update available” prompts.

Debug Information (Read)

Debug data is exposed for diagnostics and should not normally be shown to end users.
It is especially useful during development, QA, or support tooling.

Debug Logging (Write)

You can instruct a connected device to start emitting real-time log messages over WebSocket. The server captures and stores these messages, which you can then view in the CMS. See the full guide: Debug Logging
  • Show user-facing status from: batteryLevel, batteryVoltage, temperatureSensor*, wifiConnected, bleConnected.
  • Offer configuration UI for: deviceName, wifiEnabled, bleEnabled.
  • Gate service commands behind confirmation dialogs for: startCalibration, startOta, powerDown.
  • Use setCurrentScreen to programmatically drive the device UI (e.g. open Settings or WiFi screen from your app).
  • Surface firmware prompts based on: firmwareStatus and latestFirmwareVersion.
  • Use debug information only in internal tools, logs, or support dashboards.
  • Enable debug logging only during development or support — it is not persisted and does not survive reconnects.
For exact endpoint URLs, request/response schemas, and error codes, see the WiFi API section in the Melody API Reference.