
The Fonestar WA-225W is a compact Wi-Fi stereo amplifier that supports DLNA and AirPlay for network audio streaming. TapHome communicates with the device over HTTP using UPnP/SOAP XML envelopes sent to port 49152. The template targets the standard UPnP AV Media Renderer profile, so it should work with any Fonestar device that implements DLNA (WA-225W, FONCAST, and similar models).
The template provides volume control, mute, playback transport (play, pause, stop, next, previous), and a play mode selector. No cloud connection is required — all communication happens on the local network.
Configuration
During TapHome template import, enter the device’s IP address. The default placeholder is 192.168.0.1 and the device listens on port 49152 (the standard UPnP AV port).
To find the device’s IP address, check your router’s DHCP client list or use a UPnP/SSDP scanner app. The WA-225W announces itself as a UPnP MediaRenderer on the local network. The MUZO companion app (iOS/Android) also shows connected devices and their IP addresses.
UPnP devices use SSDP for discovery, not mDNS. If the device’s IP changes after a DHCP renewal, you will need to update the IP address in TapHome. Consider assigning a static IP or a DHCP reservation on your router to prevent connectivity issues.
Device capabilities
Volume control
The template exposes volume as a dimmer device. The UPnP GetVolume action returns a value in the 0–100 range, which the template normalizes to 0.0–1.0 for TapHome’s dimmer model (divides by 100 on read, multiplies by 100 on write). Setting the volume to 50% in TapHome sends DesiredVolume=50 to the device.
Mute
Mute is exposed as a switch device. It reads the current mute state via GetMute (returns 0 or 1) and writes via SetMute. Both operations target the Master audio channel on the RenderingControl:1 service.
Playback transport
The template provides five push-button devices for playback transport control:
- Play — sends the AVTransport:1
Playaction (resumes or starts playback) - Pause — sends the
Pauseaction (halts playback at the current position) - Stop — sends the
Stopaction (stops playback entirely) - Next Track — sends the
Nextaction (advances to the next track) - Previous Track — sends the
Previousaction (returns to the previous track)
These are write-only buttons. Playback must first be initiated from another source (e.g., the MUZO app or another DLNA controller) since the template does not include a SetAVTransportURI action for setting the media source.
Play mode
The play mode device is a multi-value switch that controls the repeat mode via GetTransportSettings and SetPlayMode. Three modes are functional:
| Position | TapHome label | UPnP PlayMode | Effect |
|---|---|---|---|
| 0 | Normal | NORMAL | Sequential playback, no repeat |
| 1 | Repeat All | REPEAT_ALL | Repeat the entire queue |
| 2 | Repeat One | REPEAT_TRACK | Repeat the current track |
The template defines 10 multi-value positions, but only positions 0–2 map to actual UPnP play modes. Positions 3–9 (labelled “Shuffle no repeat”, “Shuffle”, etc.) will default to NORMAL when written because the UPnP
SHUFFLEmode is not mapped in the template script. Use only the first three positions.
Additional capabilities
The UPnP AV standard also exposes transport state reporting (STOPPED, PLAYING, PAUSED), track position and duration info, media URI management (SetAVTransportURI for queuing tracks), seek functionality, volume control in decibels, loudness enhancement, and rendering presets. These capabilities can be added in a future template update.
Troubleshooting
Device not responding
- Verify the amplifier is powered on and connected to Wi-Fi (or Ethernet via RJ-45)
- Confirm the IP address in TapHome matches the device’s current IP — check your router’s DHCP client list
- Try accessing
http://{device-ip}:49152/in a browser — a UPnP device description XML should load if the device is reachable - Check that TapHome Core and the amplifier are on the same network / VLAN — UPnP traffic does not cross subnet boundaries by default
Playback buttons have no effect
The transport buttons (Play, Pause, Stop, Next, Previous) only work when media is already loaded on the device. The template does not include the SetAVTransportURI action, so playback must first be started from another source (e.g., the MUZO app, a DLNA media server, or another UPnP control point). Once media is playing, the TapHome buttons will control it.
Volume changes not reflected
If volume adjustments from TapHome do not take effect, verify that the device is not muted. Some DLNA renderers ignore volume changes while muted. Also confirm that no other control point (e.g., the MUZO app) is simultaneously sending conflicting commands.
