Music assistant core?

Trying to move to Music assistant core. I deleted all reverences to music assistant, rebooted then added music assistant integration but it fails with “failed to connect” http://mass.local:8095.

What am I missing?

1 Like

Sharing the Logs with us?

I am having the same issue. I tried looking in the logs like the instructions say but could not find the ip address in the logs. Which logs do you need to see? I went to settings, system, logs but wasn’t sure which one to choose. I checked them all and could not find an ip address.

The only logs I see mentioning the mass is the dns log (raw).

CoreDNS-1.8.7
linux/amd64, go1.22.2, a9adfd5-dirty
[INFO] 127.0.0.1:52931 - 40963 "HINFO IN 4382908691551342339.5691997803745100648. udp 68 true 2048" REFUSED qr,aa,rd 57 0.000340581s
[INFO] 127.0.0.1:37850 - 44518 "HINFO IN 4382908691551342339.5691997803745100648. udp 57 false 512" REFUSED qr,aa,rd 57 0.022736873s
[INFO] 172.30.32.1:41757 - 33495 "A IN mass.local.local.hass.io. udp 42 false 512" NXDOMAIN qr,aa,rd 42 0.000439847s
[INFO] 172.30.32.1:52442 - 32835 "A IN mass.local.local.hass.io. udp 42 false 512" NXDOMAIN qr,aa,rd 42 0.000289225s
[INFO] 172.30.32.1:36448 - 20986 "A IN mass.local.local.hass.io. udp 42 false 512" NXDOMAIN qr,aa,rd 42 0.000350213s
[INFO] 172.30.32.1:59262 - 50669 "A IN mass.local.local.hass.io. udp 42 false 512" NXDOMAIN qr,aa,rd 42 0.000436107s
[INFO] 172.30.32.1:43399 - 32928 "A IN mass.local.local.hass.io. udp 42 false 512" NXDOMAIN qr,aa,rd 42 0.000450884s
[INFO] 172.30.32.1:48642 - 54130 "A IN mass.local.local.hass.io. udp 42 false 512" NXDOMAIN qr,aa,rd 42 0.000334739s
[INFO] 172.30.32.1:53455 - 18608 "A IN mass.local.local.hass.io. udp 42 false 512" NXDOMAIN qr,aa,rd 42 0.00040217s
[INFO] 172.30.32.1:42579 - 15966 "A IN mass.local.local.hass.io. udp 42 false 512" NXDOMAIN qr,aa,rd 42 0.000398193s
[INFO] 172.30.32.1:57363 - 11675 "A IN mass.local.local.hass.io. udp 42 false 512" NXDOMAIN qr,aa,rd 42 0.000246952s
[INFO] 172.30.32.1:49540 - 34081 "A IN mass.local.local.hass.io. udp 42 false 512" NXDOMAIN qr,aa,rd 42 0.000218565s
[INFO] 172.30.32.1:57164 - 52604 "A IN mass.local.local.hass.io. udp 42 false 512" NXDOMAIN qr,aa,rd 42 0.000221769s

Found a warning too.
Logger: homeassistant.helpers.translation
Source: helpers/translation.py:226
First occurred: 12:34:23 PM (1 occurrences)
Last logged: 12:34:23 PM

Failed to load integration for translation: Integration ‘mass’ not found.

I have the exact same issue and I cannot get the new builtin intergration to load.

[INFO] 172.30.32.1:57170 - 33391 "A IN mass.local.local.hass.io. udp 42 false 512" NXDOMAIN qr,aa,rd 42 0.000142519s

I have the same thing happening here

image

The previous URL was http://172.30.32.1:8095 with CUSTOM.

The documents dont really help as far as where to go. The previous version has been removed. What are we missing?

I have the exact same

Try that same previous url. I expect that mass.local is not resolving

You guys all need to change http://mass.local:8095 to http://homeassistant.local:8095 or whatever your HA server is called. Even the HA ip address should work here.

Sorry that is not correct. If running in docker it will be the MA server IP. If running as an addon the docs explain

You will need to add the server IP and port (usually 8095). Search for the relevant line in the server logs. For example, Starting server on 172.30.32.1:8095.

Works just fine here running as an addon? I’d also be willing to bet that if any of the previous posters were experienced enough to run docker they would have figured this out…

I assume you have enabled the “Expose the web server (port 8095)” in the MA settings

Yep. And FWIW here’s my related mass log entry. Which is why I said the HA ip address should work as well.

2024-12-28 20:14:58.668 INFO (MainThread) [music_assistant.streams] Starting server on  0.0.0.0:8098 - base url: http://192.168.1.100:8098
2024-12-28 20:14:58.678 INFO (MainThread) [music_assistant.webserver] Starting server on  0.0.0.0:8095 - base url: http://192.168.1.100:8095

Yeah so people that don’t have that enabled, which isn’t by default, need to get the docker IP as the docs describe.

Ive tried the previous URL, Ive tried the HA IP, Ive tried `http://homeassistant.local:8095

None of the above work for setup, nor give any clues as to why

Gotcha. I didn’t realize you were talking about the built in HA docker. For some reason I never got the Music Assistant device discovered prompt until just now when I deleted my instance and restarted.

Was just playing around a bit with some different combinations. `http://homeassistant.local:8095’ does work for me even with the webserver not turned on. I assume mass.local:8095 is the default when not using the addon?

Good to know. I would have to ask the others about mass.local as it hasn’t worked for me in the past

Have you looked for the actual url in the MA log as described in the docs? Are you running the addon or docker?

Same issue here. No MA log, can’t see anything related to MASS in any log except the afrorementioned DNS log.

Historically:
All on HA Yellow.
Home Assistant HACS add on installed
Home Assistant (Beta) HACS add on installed and active
Removed the MA integration and the HACS add ons.
No Music assistant discovered.
Manually adding does not work.

The HA sidebar still shows Music Assistant !! Clicking on it says HA Beta is not running. It will not start - shows bad gateway.

Are there more uninstall steps?