Echo (LineageOS) Device importing as Home Assistant Media Player #131
|
I have been struggling to get my Echo devices imported as Sendspin media players using AVA 0.6.0. They currently will import as HA Media Players. Each will work as HA Media Players. However, syncing multiple players is not supported. All of them (Echo LineageOS) import as Sendspin Media Players using SendspinDroid. These players can be synced. Does the Echo LineageOS running Knoop7 Ava import as Sendspin or HA Media Player? |
Replies: 12 comments 2 replies
|
Ava has Sendspin built-in, so no additional installation is needed. The reason you see it only importing as HA Media Player is because the Sendspin route isn't actually broadcasting—it's enabled by default, but either it's disabled or mDNS failed to register. The difference between the two routes (first figure out which one you're seeing):
Sendspin Player (Music Assistant Player) = This uses mDNS There's only one switch to enable: In Ava: Settings → Interaction → Media Player → "Music Assistant player" and turn it on. (The old path might be Settings → Extensions → Playback → Media Player. Version 0.6.0 has a redesigned menu; look for the group containing "Music Assistant".) Optional: Set a Sendspin Device Name for easier device recognition in Music Assistant. Leave Audio Format as Automatic; for older devices (less than 1GB RAM), enable Optimization Mode. No need to fill in IP address or port; Ava automatically discovers the Music Assistant server via mDNS. In Music Assistant: Open http://yourHA address:8123/music-assistant Ava devices will automatically appear in the player list (the name is the Sendspin Device Name set above; if not set, use the system device name). Group multiple Ava players into a sync group, and synchronization will occur. Synchronization is done on the Music Assistant side, not on the Ava player itself. If it's enabled but still doesn't appear in the MA, confirm that Ava and MA are on the same LAN (same subnet, mDNS doesn't cross VLANs). Update to version 0.6.2 |
|
If that doesn't work, check mDNS to see if If it's not there, the broadcast isn't starting, which is usually unlikely. If it's not there either, the problem lies with MA, usually related to your Docker or router gateway. Further explanation: Ava's features here don't include more functionality that requires writing to the complete MA, such as adding addresses and tokens. Other Sendspin applications have complete MA features, including music libraries, etc. Perhaps in the future, when MA is more stable, these features will be added, or not. Currently, MA is still evolving, so frequent updates to this code are unnecessary. Old and new versions conflict with each other, requiring numerous adaptation layers and becoming bloated. Implementing for the sake of implementation is counterproductive. From the beginning, including Ava Pro, we've always controlled two things:
However, currently, many features are too difficult to understand, making it quite challenging. Therefore, to reduce complexity, some exposed features have been disabled. Furthermore, it's not just the synchronization protocol that differs from theirs. Detailed observation reveals the differences. |
|
Knoop7, Thank you for the quick reply and the detailed explanation. I have upgraded AVA to 0.6.2 on two of my Echos (Echo 5 and Echo 8). However, I don't see this device registered in MA. With SendspinDroid client installed, I would the SendspinDroid entity registered. Would there be an mDNS issue if the SendspinDroid registered? |
|
I have a flat network. No VLANs. Ha (HAOS) is running as a virtual box on a Windows host. Both HA and MA is on the same box. |
|
I understand now Change the HAOS virtual machine to bridged networking (Bridged Adapter), do not use NAT. |
|
I'm at a total loss. I think this is sending my head spinning.
My haos virtual has been setup with bridge networking.
Running dns-sd -B _sendspin._top
Returns
Echo 5 AVA
Echo 5C AVA
Echo 8 AVA
I don't see any of these in MA.
…On Fri, Jul 24, 2026, 6:54 PM KNOOP ***@***.***> wrote:
I understand now
Change the HAOS virtual machine to bridged networking (Bridged Adapter),
do not use NAT.
VirtualBox → The VM → Settings → Network → Network mode: Select "Bridged
Adapter" and choose your Windows host's physical network adapter.
After bridging, HAOS obtains a real LAN IP address and becomes a formal
member of the LAN, allowing mDNS to communicate.
Multicast is not forwarded at all in NAT mode; this path is dead, so don't
waste time on NAT.
After bridging, mDNS was verified to be working:
Run dns-sd -B _sendspin._tcp on a Windows host (or use Bonjour Browser)
to see if you can see _sendspin._tcp broadcast by Echo.
If you can't see it, it means that multicast is being blocked on the
Windows side—check the inbound rules of the Windows Firewall for the
VirtualBox bridging driver and see if multicast is allowed; or temporarily
turn off the firewall and test to confirm if it's the firewall's fault.
@Wex005 <https://github.com/Wex005>
—
Reply to this email directly, view it on GitHub
<#131>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7GRGM7YXAHLSMPFUVBO27L5GPZKFAVCNFSNUABJKJSXA33TNF2G64TZHMYTCMJYHA2TIMZQGQ5UI2LTMN2XG43JN5XDWMJQGQ4TAMZYGWQXMAQ>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/A7GRGM4YX43D33AXOYKNKDT5GPZKFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXG4ZTKMBVUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ>
and Android
<https://github.com/notifications/mobile/android/A7GRGM7KTMIJHVMFN6LNSFD5GPZKFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXG4ZTKMBVUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
It's okay if you find it difficult to use and not worth the effort. You can consider using other protocol-based software in conjunction with it. Virtual machines themselves have difficulty automatically resolving MDNS discovery. Ava Pro is a modular utility class; disabling this feature will prevent any functions from running. Afterwards, please use: https://github.com/pantherale0/sendspinlite This project is one of the benchmarks for lightweight multi-room synchronization protocols. |
|
Knoop,
Please, don't misunderstand. I think your product is great and you have
spent a lot of time developing and refining your product. I think it what I
need to accomplish my objectives, repurposing my Echos into at minimum
speakers and voice satellites.
If you are willing to assist this old man, I'm willing to put in the time.
I can understand your time is valuable.
Thank you for your assistance,
…On Fri, Jul 24, 2026, 9:37 PM KNOOP ***@***.***> wrote:
It's okay if you find it difficult to use and not worth the effort.
You can consider using other protocol-based software in conjunction with
it. Virtual machines themselves have difficulty automatically resolving
MDNS discovery.
Ava Pro is a modular utility class; disabling this feature will prevent
any functions from running. Afterwards, please use:
https://github.com/pantherale0/sendspinlite
This project is one of the benchmarks for lightweight multi-room
synchronization protocols.
@Wex005 <https://github.com/Wex005>
—
Reply to this email directly, view it on GitHub
<#131>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7GRGMYEG6DELYSBLYLQUK35GQMOZAVCNFSNUABJKJSXA33TNF2G64TZHMYTCMJYHA2TIMZQGQ5UI2LTMN2XG43JN5XDWMJQGQ4TAMZYGWQXMAQ>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/A7GRGM2CG34X5MON54R36Y35GQMOZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXG42DQMBUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ>
and Android
<https://github.com/notifications/mobile/android/A7GRGM7MJP6PAD6DJDM7MZT5GQMOZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXG42DQMBUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@Wex005 I've had this problem a couple of weeks ago with an Echo 5 running LineageOS and Ava 5.x. Still not sure how I fixed it but what you can try is:
Just a question for you: do your Echo clients sync properly? Mine tend to drift apart (from each other and from other wired/wireless Sendspin clients) and no matter what I try, they still won't stay synced over longer stretches of time. |
|
Knoop,
I really do think your AVA is well worth the effort! I would prefer using 1
app for all of my needs. Especially on low powered devices, like the Echos.
I think my issue is with my setup and my limited understanding of how
things should work.
I did install the Sendspin lite app on all of my Echos. Each immediately
imported into Music Assistant. Playback is perfectly synced with no drift.
I did noticed, that all of the Echo 5s imported with same name. Could this
be a reason I was struggling with AVA? Could it be that the Echos imported
under a different name from what I set in the AVA app and I overlooked them?
I had named them Echo 5, Echo 5B and Echo 5C. All of which I never saw in
MA.
Just for reference, I have attached a screenshot of two Echo 5s, imported
with the same name, using the Sendspin lite.
Thank you so much for your time and assistance. I will continue to use your
AVA app.
…On Fri, Jul 24, 2026, 9:37 PM KNOOP ***@***.***> wrote:
It's okay if you find it difficult to use and not worth the effort.
You can consider using other protocol-based software in conjunction with
it. Virtual machines themselves have difficulty automatically resolving
MDNS discovery.
Ava Pro is a modular utility class; disabling this feature will prevent
any functions from running. Afterwards, please use:
https://github.com/pantherale0/sendspinlite
This project is one of the benchmarks for lightweight multi-room
synchronization protocols.
@Wex005 <https://github.com/Wex005>
—
Reply to this email directly, view it on GitHub
<#131>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7GRGMYEG6DELYSBLYLQUK35GQMOZAVCNFSNUABJKJSXA33TNF2G64TZHMYTCMJYHA2TIMZQGQ5UI2LTMN2XG43JN5XDWMJQGQ4TAMZYGWQXMAQ>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/A7GRGM2CG34X5MON54R36Y35GQMOZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXG42DQMBUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ>
and Android
<https://github.com/notifications/mobile/android/A7GRGM7MJP6PAD6DJDM7MZT5GQMOZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXG42DQMBUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Yes, the Echo 5 import using the SendspinDroid app. However, like you, none
of the Echo 5s would maintain sync.
Knoop, suggested using Sendspin Lite. Using this app, all Echo 5s and my
Echo 8 stay synced.
Thank you for your suggestions,
…On Sat, Jul 25, 2026, 8:05 PM zmd22 ***@***.***> wrote:
@Wex005 <https://github.com/Wex005> I've had this problem a couple of
weeks ago with an Echo 5 running LineageOS and Ava 5.x. Still not sure how
I fixed it but what you can try is:
- remove any other APK like Sendspindroid from your Echo device (and
the corresponding client from within MA)
- manually add the device IP under "Manual IP adresses for discovery"
in your Sendspin advanced settings (under Settings>Player
providers>Sendspin>Show advanced settings)
- restart the MA app/reload the Sendspin provider
Just a question for you: do your Echo clients sync properly? Mine tend to
drift apart (from each other and from other wired/wireless Sendspin
clients) and no matter what I try, they still won't stay synced over longer
stretches of time.
—
Reply to this email directly, view it on GitHub
<#131>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7GRGMYKC55M4LXJLRUQKJL5GVKODAVCNFSNUABJKJSXA33TNF2G64TZHMYTCMJYHA2TIMZQGQ5UI2LTMN2XG43JN5XDWMJQGQ4TAMZYGWQXMAQ>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/A7GRGMYQ7WFRMFLCTQARSRT5GVKODA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXHAZTANZZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ>
and Android
<https://github.com/notifications/mobile/android/A7GRGMZDLMMMDQR4JYI2PU35GVKODA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXHAZTANZZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I'm running batch tests to recreate your scenario and have made progress. A beta version will be released soon; you can try it and see if you find the issue. It's indeed a name conflict; this can be fixed by customizing the name. Thank you for your test logs; I will reinforce this feature. Thank you for your praise. It's true that many features are quite complex and difficult to understand. To add some context: Because AVA Pro's content in this area is indeed different from other conventional solutions, they are following the official path. Therefore, AVA's development path has been somewhat bumpy. and for performance and long-term operation, they've developed their own C++ and audio drivers. |
|
Happy for you to take and use the guts of SendspinLite if it helps at all. The protocol is implemented via a JNI bridge to the official c++ implementation of Sendspin. There are still a few bugs around audio starvation that can happen on some devices, I think that is merely some locking/sync problems between the audio playout and bridge, but I'm not 100% sure yet. It could also be some brief network blip too. |
|
That's great! I'll learn how to handle some synchronization issues. I'm also using it for learning. |
Happy for you to take and use the guts of SendspinLite if it helps at all. The protocol is implemented via a JNI bridge to the official c++ implementation of Sendspin.
There are still a few bugs around audio starvation that can happen on some devices, I think that is merely some locking/sync problems between the audio playout and bridge, but I'm not 100% sure yet. It could also be some brief network blip too.