Zidoo Media Player

Controls Zidoo media players for transport, navigation, and playback. It connects over the network or RS-232 serial, and the available commands depend on which transport you use.

Connection

Two transports:

• Network — HTTP on port 9529.
• RS-232 serial — 9600 baud.

Each transport exposes a different command set — a device gets only the commands for the transport it is connected over.

Setup

• Connection — network (HTTP) or serial.
• For network: the player’s host.
• For serial: the serial port.

What it can do

Over the network transport, the whole handset:

Command	What it does
power_on / power_off / standby / reboot	Power the player
transport	play, pause, play_pause, stop, next, previous, fast_forward, rewind, record, repeat
navigation	up, down, left, right, ok, back, cancel, home, menu, popup_menu, info, page_up, page_down, app_switch
volume	volume_up, volume_down, mute
media options	subtitle, audio_track, resolution, pip, mode_3d, hdmi_in, screenshot, mouse
digits	digit_0–digit_9, dash, star, pound
apps	app_movies, app_music, app_photos, app_files
sendkey	Send a named key directly (e.g. Key.UserDefine_A)
open	Play a file, a share path, or a stream URL

The network transport reports media-playback state, and ships a remote layout — d-pad, disc menu, transport, volume and page rockers, subtitle and audio track, and the number pad.

Playing something

open takes either kind of address, and the driver picks the endpoint by scheme:

• A path — smb://nas/Films/Arrival.mkv, nfs://…, /mnt/… — goes to ZidooFileControl/openFile.
• An http:// or https:// URL — a Jellyfin or Plex stream address — goes to ZidooFileControl/v2/openFile, which is the only endpoint on the box that will go and fetch something.

Caution

This distinction is not cosmetic. openFile is a path endpoint: handed an http:// URL it answers HTTP 200 and does nothing at all. The driver used to send every stream URL there, which is why a film sent from the library to a Zidoo never started and no error appeared anywhere.

Notes

Note

The serial transport exposes a different command set. It has things the network one does not — the four colour keys, DAC on/off, and app launchers — and lacks things the network one has: no track next/previous, no play/pause toggle, and no way to be handed a file at all. A serial Zidoo is therefore not offered as a destination for media.

Note

This player answers HTTP 200 to requests it has refused, with the real verdict in the body ({"status":…} for the main API, {"code":…} for the v2 calls). The driver reads the body, so a key the box does not have — or a path it cannot reach — is reported as a failed command rather than a silent success.

Note

sendkey reaches the keys that are not published as commands, because their meaning is not fixed: Key.UserDefine_A through _D are whatever their owner assigned them to, and Key.light is undocumented.