New experimental "Sendspin protocol" (formerly "Resonate") for streaming synchronized multi-room audio and HiFi music playback to multiple media player appliances and smart speakers running ESPHome on ESP32 or Linux on Raspberry Pi (Zero)

Hedda · January 6, 2026, 8:22am

But that pull request which will add the initial Sendspin component to upstream ESPHome has not even been merged into the mainline ESPHome codebase yet, the pull request is still open as a draft with a WIP (Work-in-Progress) flag. So why would you not report any issues directly to developers via that pull request on GitHub as long as it has not yet been merged? Regardless, I am pretty sure that Sendspin developers and ESPHome developers working on that code do not read this forum thread and it is therefore unlikley they see reports here, which does not help anyone. Again, suggest you report issues directly to GitHub in that pull request while it is still open and unmerged, that could help many people if issues gets fixed there.

github.com/esphome/esphome

[sendspin] (WIP) Add Sendspin synced audio protocol support

dev ← kahrendt:sendspin-dev-snapshot1

opened 05:45PM - 04 Dec 25 UTC

kahrendt

+5455 -4

# What does this implement/fix? This PR introduces a development snapshot of …the Sendspin component for ESPHome, enabling synchronized audio playback and control across multiple devices using the [Sendspin protocol](https://github.com/Sendspin-Protocol/spec). It adds a hub component and optional child components: - Sendspin ``media_player`` exposes a new media player to HA that controls a Sendspin group (no audio playback) - Sendspin ``media_source`` plays synchronized audio and controls a Sendspin group (requires #12429) - Sendspin ``text_sensor`` exposes text metadata like track title or album artist - Sendspin ``generic_image`` exposes a ``generic_image`` component for display artwork (album or artist) - Sendspin ``sensor`` exposes numerical sensors used for debugging It is currently a work in progress! Expect changes to how this works, especially related to how the ``media_player`` works. ## Types of changes - [ ] Bugfix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Developer breaking change (an API change that could break external components) - [ ] Code quality improvements to existing code or addition of tests - [ ] Other **Related issue or feature (if applicable):** not applicable **Pull request in [esphome-docs](https://github.com/esphome/esphome-docs) with documentation (if applicable):** not available yet ## Test Environment - [ ] ESP32 - [x] ESP32 IDF - [ ] ESP8266 - [ ] RP2040 - [ ] BK72xx - [ ] RTL87xx - [ ] nRF52840 ## Example entry for `config.yaml`: Example Voice Preview Edition firmware is available here: https://github.com/esphome/home-assistant-voice-pe-alpha/blob/alpha/home-assistant-voice.yaml (requires building with ESPHome dev branch) Example artwork, controller, and metadata displayer for an ESP32-S3 Box 3 is here: https://gist.github.com/kahrendt/a86b20601f02df9f3861a48cedc98e17 **Requires Music Assistant 2.7.0 beta 19 or later to serve audio.** ```yaml # Example config.yaml external_components: - source: github://pr#12284 components: [generic_image, mdns, sendspin] refresh: 1h - source: github://pr#12253 components: [ mixer ] - source: github://pr#12254 components: [ resampler ] - source: github://pr#12256 components: [ audio ] - source: github://pr#12258 components: [ media_player ] - source: github://pr#10212 components: [runtime_image, online_image] refresh: 0s - source: github://pr#12429 components: [media_source, speaker_source] sendspin: id: sendspin_hub # Optional. Used for playing synchronized audio when used with the speaker_source media player media_source: - platform: sendspin id: sendspin_source media_player: # Optional. Only used for controlling a Sendspin group - platform: sendspin id: sendspin_media_player name: Sendspin Group Media Player # Required to play audio (part of #12429) - platform: speaker_source name: Sendspin Media Player id: sendspin_media_player volume_min: 0.4 volume_max: 0.85 media_speaker: sendspin_mixing_input sources: - sendspin_source # Optional. Only needed for artwork generic_image: - platform: sendspin id: sendspin_cover_art format: jpg type: rgb565 resize: 320x240 image_source: ALBUM on_image_decoded: - lvgl.page.show: sendspin_page - lvgl.image.update: id: album_art_widget src: sendspin_cover_art on_image_error: - logger.log: "Failed to decode cover art image" # Optional. Only needed for text metadata text_sensor: - platform: sendspin type: title name: Track Title - platform: sendspin type: artist name: Artist - platform: sendspin type: album name: Album - platform: sendspin type: year name: Year - platform: sendspin type: track name: Track Number # Optional. Only needed for debugging. sensor: - platform: sendspin type: kalman_error name: "Kalman Error" # Time sync filter uncertainty estimate - platform: sendspin type: audible_syncs name: "Audible Syncs" # Major sync events that are audible ``` ## Checklist: - [x] The code change is tested and works locally. - [ ] Tests have been added to verify that the new code works (under `tests/` folder). If user exposed functionality or configuration variables are added/changed: - [ ] Documentation added/updated in [esphome-docs](https://github.com/esphome/esphome-docs).

Arh · January 6, 2026, 9:52am

well right now there are known memory issues with esp boards, which cause crashes. The causes of these crashes is proving difficult to identify, so the fix may be some time coming. As suggested this is all still in alpha and work is happening at pace.

The discord page is by far the best page / discussion to address these issues as this is where the developers and testers are discussing the issues. Bringing the issues up here may help some, but unless the developers here about these issues they will not be able to fix them.

allard77 · January 6, 2026, 1:17pm

Reporting an issue is not the same thing as asking around to see if others are trying the same thing as you. Reaching out to users is not the same as reaching out to developers. Sure, if you have a specific issue to report do it on GitHub. But when you’re still trying to figure out if you yourself are the root cause of the problem, or just want to know if anyone is working on a specific device, a forum seems like a good place to me.
I myself wouldn’t want to slow down the development because a code owner has to process an issue, spend time on it, only to find out I made a typo in my YAML somewhere.

andrew_NH · January 6, 2026, 6:46pm

Yes exactly, I will probably push this up the chain but I am interested to know if anybody has Sendspin working on a P4 or if anybody has even tried.

I have about 20 different ESP32 screens and the p4 screens are by far the best. They support LVGL features like “swipes”, They support large size high resolution screens well, and they work will with audio such as microphones and speakers. The P4 also has a lot more extra I/O lines for hardware development.

I plan to be doing most future ESPHome development on the P4.

SeByDocKy · January 9, 2026, 1:24pm

Hi, I don’t know if it’s the place to mention or related with, but since a couple of days when I compiled my MuseRadio with last ESPhome Dev and installed last HA release, got a lot gliched in the streaming (1s break, and often the ESP is rebooting)…

Arh · January 9, 2026, 1:31pm

This is a known issue, and apparently difficult to diagnose and therefore fix.

some discussion on the sendspin (wip) page linked above. Also some on the discord page.

Hedda · January 9, 2026, 3:49pm

Sendspin initial pull request has still not yet been merged into ESPHome dev so unless you specifically built it with that draft pull request then should not be related to Sendspin.