Repository: music-assistant/support

Issue #2333: Port disappearing from Integration URL
Created: 2024-05-19T14:36:26Z
What version of Music Assistant has the issue?
2.0.0b141
What version of the Home Assistant Integration have you got installed?
2024.5.4
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

 Yes

The problem
I'm running a docker version of the  MA Server:
docker run -d --name=music_assistant --network host --privileged -v /home/music-assistant:/data ghcr.io/music-assistant/server
Now I used the Adresse: http://192.168.1.123:8095 to integrate this server as a new device in HA withe the MA integration.
The URL is accesible from HA.
But I get the Error: "Failed setup, will retry"
In the log I see:
Logger: homeassistant
Source: /usr/src/homeassistant/homeassistant/runner.py:147
First occurred: 4:04:17 PM (42 occurrences)
Last logged: 4:29:59 PM

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/music_assistant/client/client.py", line 297, in fetch_initial_state
    await self._player_queues.fetch_state()
  File "/usr/local/lib/python3.12/site-packages/music_assistant/client/player_queues.py", line 228, in fetch_state
    for queue in await self._get_player_queues():
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/music_assistant/client/player_queues.py", line 223, in _get_player_queues
    for item in await self.client.send_command("player_queues/all")
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/music_assistant/client/client.py", line 254, in send_command
    return await future
           ^^^^^^^^^^^^
music_assistant.common.models.errors.InvalidCommand: Invalid command: player_queues/all

How to reproduce
as described above
Music Providers



Player Providers
Chromecast Player
Full log output
No response
Additional information
No response
What version of Home Assistant Core are your running
2024.5.4
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Linux

Duplicate issue #2924: Adding a Music Assistant server on non-standard port fails
Created: 2024-09-15T08:44:54Z
What version of Music Assistant has the issue?
2.2.4
What version of the Home Assistant Integration have you got installed?
2024.9.1
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

 Yes

The problem
After successfully configuring MASS on a non-standard HTTP port (in my case I used :8093) I can browse the Web UI with no problems by visiting http://my.server.ip.address:8093.
However, attempting to add the Music Assistant Server to my Home Assistant this URL gives an error message Unexpected Error.

How to reproduce

In Home Assistant, navigate to Settings > Integrations
Click Add Integration
Search for Music Assistant, and enter the HTTP address of the server on a custom port
Click Submit
Observe integration is not added, and error message is displayed.

Music Providers



Player Providers



Full log output
No response
Additional information
When the submit button is pressed to trigger the error, the Home Assistance logs produces the following output:
2024-09-15 18:27:27.061 ERROR (MainThread) [custom_components.mass] Unexpected exception
Traceback (most recent call last):
  File "/config/custom_components/mass/config_flow.py", line 74, in async_step_manual
    await self.async_set_unique_id(self.server_info.server_id)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2389, in async_set_unique_id
    raise data_entry_flow.AbortFlow("already_in_progress")
homeassistant.data_entry_flow.AbortFlow: Flow aborted: already_in_progress

What version of Home Assistant Core are your running
2024.8.2
What type of installation are you running?
Home Assistant Container
On what type of hardware are you running?
Linux

Closing comment (2024-09-15T08:46:39Z): Potentially related to #2333