I have a non- HAOS implementation of HA in docker.
I want to add MA.
easy enough, setup the docker container,
start customize the settings to link the HA instance.
I have esphome players, they are found in the MA server. (player provider and all)
I can play music from MA, just fine.
have MA in the HA left nav.. all good..
but I want to write some automations to use voice to play music
first use MA search to find content id of the media (on spotify)
the automation fails,
Music Assistant 'Search Music Assistant'
Executed: August 30, 2025 at 9:57:44 AM
Error: Entry not found
the integration shows
Failed setup, will retry: Failed to connect to music assistant server http://192.168.2.32
if I give a bad address, it knows.. that is the URL of the MA server that I can use its web page from
I setup a VM with HA supervised and the addon, and it works as expected.
so something in the addon is confused..
I see HA log entries unable to connect
the HA instance auto discovered the MA instance in the virtual machine,
but did not auto discover the MA instance in the same docker container
the HA instance in docker does not have the custom_components folder. (as I assume this is built/added to when the integration add is processed. )
I added the discovery ports(5353 and 1900) to the HA docker instance. but shouldn't need to as it discovered the VM instance ok.
I understand its really supported in HAOS/Supervised.. but I can't get there on my synology system
note that I am using http on my local network, so ssl verify should be off.. I'think' this is the root cause , similar to
https://github.com/home-assistant/core/issues/132742
I am on
Installation method
Unsupported Third Party Container
Core
2025.8.3
Frontend
20250811.1
any guidance welcomed