Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding a Music Assistant server on non-standard port fails #2924

Closed
1 task done
aliask opened this issue Sep 15, 2024 · 4 comments
Closed
1 task done

Adding a Music Assistant server on non-standard port fails #2924

aliask opened this issue Sep 15, 2024 · 4 comments

Comments

@aliask
Copy link

aliask commented Sep 15, 2024

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.

Screenshot from 2024-09-15 18-27-49

How to reproduce

  1. In Home Assistant, navigate to Settings > Integrations
  2. Click Add Integration
  3. Search for Music Assistant, and enter the HTTP address of the server on a custom port
  4. Click Submit
  5. 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

@aliask aliask added the triage label Sep 15, 2024
@aliask
Copy link
Author

aliask commented Sep 15, 2024

Potentially related to #2333

@OzGav
Copy link
Contributor

OzGav commented Oct 15, 2024

Review the recent posts in the issue you linked and confirm you have MA setup correctly.

Copy link
Contributor

This issue is stale because it has been open 7 days with no activity after asking for more info. Comment or this will be closed in 3 days.

@github-actions github-actions bot added the Stale label Oct 22, 2024
Copy link
Contributor

This issue was closed because it has been stalled for 10 days with no activity. This can be reopened if additional information is provided.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants