#Frontend errors and HA integration

1 messages · Page 1 of 1 (latest)

fallow falcon
#

I'm getting a lot of really frustrating error messages - I can only guess it's a frontend issue because most things are still functioning ok in the background but a lot of bits of the webserver aren't working as they should. The only error message in the logs is:
2025-12-29 13:49:04.105 ERROR (MainThread) [music_assistant.webserver] Error handling message: config/players: 'provider'
Usually accompanied by "🚫 provider" red popup. I get the message when clicking settings > providers and settings > players, but none of the providers themselves are showing any errors. The Players page shows no players, and the homepage was previously not listing any of the home-screen stuff (although that seems to be working now). I can go through artists/albums, I can search, and I can play music correctly and I can access the player settings pages from the player bar and that works fine.
My HA integration is also reporting errors, which are clearly related, looking at the error messages:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 761, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/music_assistant/__init__.py", line 238, in async_setup_entry
    all_player_configs = await mass.config.get_player_configs()
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/music_assistant_client/config.py", line 133, in get_player_configs

music_assistant_models.errors.MusicAssistantError: 'provider'```

I'm on 2.8.0b3, using Sendspin, Squeezelite, Jellyfin, BBC Sounds and Tidal providers. I've tried disabling/enabling providers, restarting MA, restarting the whole server, no change.
hidden gust
#

I have a hunch this happens during an update (e.g. 2.7.1 > 2.7.2) and we have an error in the migration logic somewhere. Do you have any idea where in the beta chain you got into this state? (eg. after 2.8.0b1>b2)

fallow falcon
#

Could be - I'll have a dig through the logs when I get chance and see if that's when it started.

hidden gust
#

I tried reproducing this on my dev setup by a fresh install of 2.6.3 and upgrading all the way to the latest beta, but no popups on my side 🙁