Skip to content
Home Assistant TestFlight
Media & entertainment

SlimProto (Squeezebox players)

slimproto

Built inLocal push

The SlimProto integration allows you to control a Squeezebox music player directly from Home Assistant, without the need for an external Media Server such as Logitech Media Server. This lets you control Squeezebox hardware like the Classic, Transporter, Duet, Boom, Radio, and Touch and software players like Squeezelite, PiCorePlayer or Max2Play. For the real DIY enthusiast, there even is a player for the ESP32.

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

EntityShows up asNote
media_playerMedia player (as switches)Only TVs and receivers get a TV tile; other players show as power and play switches; Needs its own HomeKit Bridge in accessory mode

What people report

Squeezebox hardware players had connection errors in the HA SlimProto server; the integration is mainly tested with Squeezelite.

  • Not working3
DeviceIn Home AssistantIn Apple HomeWhat they saidSource
Squeezebox BoomNot working LocalCannot connect; utf-8 decode errors in discovery
Saved copy
The problem I am testing the slimproto integration with a Squeezebox Boom player. The player is not able to connect to the server (HA) and no device or entities gets added to the slimproto integration The homeassistant log file has a lot of entries like 2022-06-16 21:42:56 ERROR (MainThread) [aioslimproto.discovery] 'utf-8' codec can't decode byte 0xe3 in position 16: invalid continuation byte Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/aioslimproto/discovery.py", line 202, in datagram_received data = data.decode() UnicodeDecodeError: 'utf-8' codec can't …

Excerpt saved from GitHub on 2026-10-23.

Issue #73611 · 2022-06
Squeezebox DuetNot working LocalSimilar discovery decode errors
Saved copy
This is what I get after rebooting HA and powering on a Squeezebox Duet and try to connect it to SlimProto: After HA Reboot: 2022-07-03 09:26:19 INFO (MainThread) [homeassistant.setup] Setting up slimproto 2022-07-03 09:26:19 INFO (MainThread) [homeassistant.setup] Setup of domain slimproto took 0.0 seconds 2022-07-03 09:26:22 INFO (MainThread) [aioslimproto.server] Starting SLIMProto server on port 3483 2022-07-03 09:26:24 INFO (MainThread) [aioslimproto.server.jsonrpc] Starting (legacy/telnet) SLIMProto CLI on port 9090 2022-07-03 09:26:27 INFO (MainThread) [aioslimproto.server.jsonrpc] …

Excerpt saved from GitHub on 2026-10-23.

Issue #73611 · 2022-06
Squeezebox RadioNot working LocalErrors when connecting to SlimProto
Saved copy
This is the Squeezebox Radio trying to connect to SlimProto: Logger: homeassistant Source: /usr/src/homeassistant/homeassistant/runner.py:96 First occurred: 09.54.06 (7 occurrences) Last logged: 09.54.41 Error doing job: Exception in callback SlimClient._process_stat_stmt(b'\x00\x00\x0...0\x00\x00\x00') Traceback (most recent call last): File "/usr/local/lib/python3.9/asyncio/events.py", line 80, in _run self._context.run(self._callback, *self._args) File "/usr/local/lib/python3.9/site-packages/aioslimproto/client.py", line 559, in _process_stat_stmt ) = struct.unpack("!BBBLLLLHLLLLHLLH", …

Excerpt saved from GitHub on 2026-10-23.

Issue #73611 · 2022-07

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Local push

Talks to the device on your network, and the device tells Home Assistant the moment something changes.

Details

Installs (analytics)597 (0.08%)
Added inHome Assistant 2022.5
Set up in the UIYes
Maintainers@marcelveldt

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.