The player exposes a command service on the LAN (WebSocket main channel + HTTP fallback), so same-network systems can send commands directly without the cloud MQTT path.
Endpoints

The player listens on its LAN interface, port 9756 and up (+1..+9 when occupied; /ping reports the actual port).

EndpointNotes
GET /pingDevice summary (no token needed, for discovery): {"id":597391,"name":"SuperScreen","version":"1.0.0","bench":1685,"status":"online","mode":"platform","lip":"192.168.3.125","port":9756,"ws":true} (mode: platform / gateway / broker)
WS /orderMain channel (WebSocket long connection). Handshake auth: ws://<lip>:<port>/order?token=<6-digit control code>&rid=<remote id>&rname=<name> (or X-SS-Token / X-SS-Remote-Id / X-SS-Remote-Name headers); wrong code or banned remote → 403. Command frame {"mid":"...","data":{command},"ts":...}; replies carry the original mid; events/progress are server-initiated uplink frames
POST /orderHTTP compatibility channel (being phased out — prefer WS). Header X-SS-Token: <control code>, body {"mid":"...","data":{command}}, synchronous reply

Command format is identical to the MQTT downlink data (screen/web/plugin/control/cache/speech/bgm/image/document/video/audio/text wrapper keys plus system:"info"|"reg"). Responses carry CORS headers (for the cross-origin web remote).

Control Code

The LAN credential is the device's 6-digit control code (generated on first launch; visible and refreshable on the console/remote settings page; empty = code control disabled, LAN always answers 403). The code syncs via the cloud config item ctrlcode and takes effect immediately; regenerating it on the device invalidates the old one at once.

Use Cases & Limits
  • Good for: in-store local control, POS integration, latency-sensitive linking, emergency control during WAN outages;
  • LAN system commands support info and reg; the rest go through the cloud;
  • HTTPS pages (browsers) fetching LAN http URLs are blocked by mixed-content policy — the web remote only uses LAN inside the SuperScreen App's remote mode (mixed content allowed there). Your own non-browser systems are unaffected;
  • Media files sent from the App's remote mode travel over LAN: the App hosts the file at http://<phone-IP>:9757/f/<id>/ and the player pulls it into its media cache;
  • While the device is in remote mode, display-family commands answer {"ret":"error","msg":"device is in remote mode"}.