#Yamaha MusicCast Integration no longer responsive

1 messages · Page 1 of 1 (latest)

agile lark
#

Have been using the MusicCast integration for a few years very reliably, but the entities for the receivers became unavailable, and now I'm not able to add them back to the integration after deleting. I can still ping the receiver ane receive JSON response back, the MusicCast iOS app still works fine, but something with the integration seems messed up?

Logger: homeassistant.components.yamaha_musiccast.config_flow
Source: components/yamaha_musiccast/config_flow.py:52
integration: MusicCast (documentation, issues)

Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/yamaha_musiccast/config_flow.py", line 52, in async_step_user
info = await MusicCastDevice.get_device_info(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
host, async_get_clientsession(self.hass)
)
^
File "/usr/local/lib/python3.13/site-packages/aiomusiccast/musiccast_device.py", line 98, in get_device_info
return await device.request_json(System.get_device_info())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiomusiccast/pyamaha.py", line 253, in request_json
return await self.build_json(response)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiomusiccast/pyamaha.py", line 234, in build_json
return json.loads(text)
~~~~~~~~~~^^^^^^
File "/usr/local/lib/python3.13/json/init.py", line 346, in loads
return _default_decoder.decode(s)
~~~~~~~~~~~~~~~~~~~~~~~^^^
File "/usr/local/lib/python3.13/json/decoder.py", line 345, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/json/decoder.py", line 363, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

olive elm
#

I have the same issue. I restored HA version 2025.5.2 from backup and MusicCast is back to normal.

south prairie
#

with 2 of you having the same issue it seems like it may be a problem that's not currently tracked.

@agile lark @olive elm could one of you create an issue on the core repo issue tracker
if you could both add any logs you have to that issue it would be great.