WiiM streamer control (IP / HTTPS)

MyURemote controls WiiM streamers using the WiiM HTTP API over a secure HTTPS connection. No IR blasters, no serial cables, and no external controllers are required.


Overview

WiiM control in MyURemote works by sending HTTP API commands over the local network. Commands are routed through the local MyURemote proxy and then forwarded to the WiiM device over HTTPS/TLS.

This integration supports playback control, volume control, source switching, presets and status feedback such as current title, artist, source and playback state.

Connection type (important)

  • Protocol: WiiM HTTP API
  • Transport: HTTPS / TLS
  • Technology in MyURemote: IP

MyURemote sends commands through its local proxy. The proxy handles the secure connection to the WiiM device, including self-signed certificates used by WiiM.

First-time use

Configure the correct IP address

WiiM control requires the correct local IP address of the device. Make sure the WiiM and the MyURemote app are connected to the same network.

The default connection uses port 443 and requires a secure connection.

Unlike Samsung SmartView control, WiiM does not require an on-screen pairing confirmation.

How it works

MyURemote builds a standard HTTP request such as:

GET /httpapi.asp?command=getPlayerStatus HTTP/1.1 Host: 192.168.0.104 Connection: close User-Agent: MyURemote Accept: */*

This request is sent to the local MyURemote proxy, which upgrades the transport to HTTPS and forwards it securely to the WiiM device.

Status feedback

WiiM can return status information such as:

  • Playback state (play, pause, stop)
  • Current volume
  • Current source / vendor
  • Track title, artist and album

Some metadata fields are returned in hexadecimal format. MyURemote can decode these values and show them on the display.

{ “status”:”play”, “vol”:”100″, “vendor”:”newTuneIn”, “Title”:”416C74696A642062656E6965757764″ }

In this example, the title is returned as hexadecimal text and can be decoded to the readable title.

Command behaviour

WiiM commands in MyURemote are usually grouped into two categories:

Action commands

  • Play
  • Pause
  • Next / Previous
  • Preset selection
  • Input switching
  • Mute on / off

Query commands

  • STATUS QUERY
  • TITLE QUERY
  • ARTIST QUERY
  • VOL QUERY
  • SRC QUERY

Query commands ask the device for information and return data to the MyURemote interface.

Volume handling

WiiM supports absolute volume values (0–100). In MyURemote, VOL+ and VOL- are handled virtually: MyURemote keeps track of the last known volume and converts those buttons into an absolute volume command.

This allows responsive volume control while staying compatible with the WiiM API.

Input switching

WiiM source switching is supported through API commands such as:

  • wifi
  • line-in
  • bluetooth
  • optical
  • udisk

In MyURemote these can be mapped to user-friendly labels such as Input WIFI, Input AUX, Input Bluetooth, etc.

Playback state vs power state

WiiM does not behave like a classic amplifier or TV with a simple on/off power model. Instead, it returns a playback state such as:

  • play
  • pause
  • stop

In MyURemote this can be used to approximate a power state if desired. For example, stop or pause may be treated as “off” in custom feedback logic.

Troubleshooting

No response from the WiiM

  • Verify the configured IP address
  • Verify the configured port (normally 443)
  • Make sure the WiiM and MyURemote are on the same network
  • Check that secure mode / HTTPS is enabled in the proxy path

Commands work in browser but not in MyURemote

  • Make sure the MyURemote proxy is using HTTPS/TLS and not raw TCP
  • WiiM rejects plain HTTP requests sent to port 443
  • The proxy must handle the secure connection on behalf of the frontend

Display text is unreadable

  • The returned field may be hexadecimal
  • Make sure the command feedback is configured with the correct HEX setting
  • Check the configured prefix and stop sign carefully

Wrong source or state shown

  • WiiM may return platform/vendor names rather than friendly labels
  • Map returned values in your command feedback configuration if needed

Supported WiiM devices

  • WiiM streamers supporting the local HTTP API
  • Devices reachable on the local network over HTTPS