Cloud and LAN integration

Choose the transport

Use the project cloud service for screens on different networks, or a LAN connection for a local controller on the same network. The command data is shared by both transports. Obtain the cloud endpoint, product identity and credentials with your deployment; the device API elsewhere on this website is a separate integration.

Messages carry an eight-character mid and a millisecond timestamp ts. Replies retain the original mid. Use it to correlate requests, replies and asynchronous events; do not treat an acknowledgement as proof that content is visible.

{"device":123,"mid":"ab12cd34","data":{"screen":{"action":"list"}},"ts":1793664000000}

Connect on the local network

The player tries port 9756, then the next nine ports if occupied. GET /ping reports the actual port. WebSocket /order is preferred; POST /order remains a legacy compatibility channel. The LAN control token is the device’s six-digit control code. An empty or disabled code rejects code-based access.

• Native clients may use X-SS-Token, X-SS-Remote-Id and X-SS-Remote-Name headers. Keep the control code private and do not expose the LAN listener to the public internet.
• An HTTPS webpage cannot assume access to an insecure HTTP or WS LAN endpoint: browser mixed-content restrictions apply. Use the supplied app or an appropriate local service. LAN system commands are limited to info and reg.

GET http://<device-ip>:<port>/ping
ws://<device-ip>:<port>/order?token=<control-code>&rid=<remote-id>&rname=<remote-name>

{"mid":"ab12cd34","data":{"screen":{"action":"list"}},"ts":1793664000000}

Replies and failures

Successful actions return ret: ok; queries may return data directly. Failures return ret: error with msg. Check for invalid param, invalid state, unsupported, queue full and device is in remote mode. Verify device state before retrying an action whose result is unknown.

{"mid":"ab12cd34","ret":"ok"}
{"mid":"ab12cd34","ret":"error","msg":"unsupported"}