Squeezebox.call_method -> 'Failed to call method playlist' 🤔

Since a few days one of my automations has been stopping at a certain point.

action: squeezebox.call_method
data:
  command: playlist
  parameters:
    - add
    - /Music/0_Playlists/1.m3u
target:
  entity_id: media_player.bedroom

This has been working without a problem for quite some time.

If I try this in Developer tools I see that error ‘Failed to call method playlist’ (and obviously also in the traces) but the action is executed.
I guess I could bypass it by enabling continue on error but I find that not good practice.

I’m on HA 2026.3.3

You’re sure that your media_player didn’t accidently got renamed to
media_player.bedroom_2 while there’s the original one besides which got unavailable?
You won’t easily realise that within lyrion itself but if you use that entity in dashboard cards or automations.

I do ask because the error doesn’t lead to the point that there’s typo in the filename or path to the playlist file and I can simply put your lines into
settings>devtools>actions, adjusting the playlist so it points to an existing one here and it works straight.

Hi, thanks for jumping in and your suggestion!

No:

I’ve been seeing this exact thing for a couple of versions., though not 100% sure when it started

As you say, the workaround is to put continue on error with every action.

Now we know it’s not just one of us, should we open an issue?

The recent change was, as part of getting our silver quality, we had to make sure we flag any errors. So, the reason this has started showing up recently is that we now flag the error, rather than it being a new problem. Chances are the error was there before but just hidden.

It means we’re getting an error code back from LMS. Turn on debug logging, run the action, and see what you get in the log, and maybe in the LMS log.

Hi Peter, thanks for this info!
I don’t mind improving the integration and possible consequences.

Does this also explain that the rest of the actions is not run?

`Yes - since we’re now raising the error, you’d need to mark it to continue on error. I can’t be 100% certain of course, but it seems very likely this is the cause of your new issue - i.e. the actual underyling error was there anyway but just not being raised. The next question of course is - what’s the underlying error… Is this error something wrong in the integration, or something with LMS. If you can get the debug logs, we can try and understand where the issue actually lies.

Hi

One of the issues now is that you cannot press the off button on the media card unless the track is first stopped. The interface complains “failed to turn off player”.

Is there no possibility to both stop and turn off on receiving turn off?

@wigster I guess that’s why the HA team want us to raise these errors, so things don’t happen in the background. I’ve never seen this one before - it certainly doesn’t do it in my setup. So, I’ll need debug logs and I’m happy to take a look.

I have the same problem: I cannot press the off button on the media card unless the track is first stopped. The interface complains “failed to turn off player”.

HA Integration Debug log:

2026-04-03 13:07:16.157 DEBUG (MainThread) [pysqueezebox.server] URL: http://192.168.1.51:9000/jsonrpc.js Data: {“id”: “1”, “method”: “slim.request”, “params”: [“00:04:20:2a:9b:0d”, [“power”, “0”]]}

2026-04-03 13:07:16.161 INFO (MainThread) [pysqueezebox.server] Query run on unknown player 00:04:20:2a:9b:0d, or invalid command

Lyrion Music Server Log File:

[26-04-03 13:29:55.2047] Slim::Control::Request::execute (1884) Error: While trying to run function coderef [Slim::Control::Commands::powerCommand]: [Modification of a read-only value attempted at /usr/share/perl5/Slim/Utils/Prefs/Base.pm line 122.
]
[26-04-03 13:29:55.2048] Slim::Web::JSONRPC::requestMethod (489) Request failed with error: Bad dispatch!

Thanks @tomber . OK, so that’s really weird. We’re just sending “power 0”, but the LMS thinks something is in a read only state. No idea what might cause that, but throwing the error looks legit - since LMS itself is throwing an error. I’ll ask over in LMS land and see what we can learn.

Michael thinks it’s an error already fixed on the LMS side in the currently nightlies

What version of LMS and perl are you running - Settings/Information. I’m running the latest 9.1.1 build and I don’t see it.

I am running Home Assistant App MS Lyrion Music Server(Formerly Logitech Media Server), Current version: 9.1.0.0

From log:

main::init (282) Starting Lyrion Music Server (v9.1.0, 1771315634, Thu Feb 19 13:51:07 UTC 2026) perl 5.040001 - x86_64-linux-gnu-thread-multi

Yep - 9.1.0 don’t have the fix. Michael only backported the fix into 9.1.1 from 9.2 a couple of weeks ago, but it won’t be in 9.1.0.

Will it help if I open an issue on Issues ¡ pssc/ha-addon-lms ¡ GitHub ?

I’d just post a question on his thread. It’s not an issue with the addin/app - it’s a bug in LMS. Typically, I think Phil only updates the stable versions, which is currently 9.1.0, but there may be a way to change to the stable/nightly option to get 9.1.x.

BTW, with the demise of Supervised, it looks like Phil isn’t planning to support the addin/app long term, so you might want to consider a different LMS platform at some point.

Ok, good to know. Btw, 9.1.1 is stable now.