Repeated LMS timeout errors in the logs

I keep getting timeout errors for the Lyrion/LMS integration:

2026-03-09 15:37:19.130 ERROR (MainThread) [pysqueezebox.server] Failed communicating with LMS(http://192.168.16.6:9000/jsonrpc.js): <class 'TimeoutError'>
2026-03-09 15:40:32.468 ERROR (MainThread) [pysqueezebox.server] Failed communicating with LMS(http://192.168.16.6:9000/jsonrpc.js): <class 'TimeoutError'>

The Lyrion server runs under Docker at 192.168.16.6 and is working fine. I have tried using network_mode: host in docker and redirecting ports in bridge, mode but it makes no difference. I have also removed and reinstalled the integration.
Trying to open the URL in the message (http://192.168.16.6:9000/jsonrpc.js) gives: 192.168.16.6 didn’t send any data. ERR_EMPTY_RESPONSE

Any ideas as to why I am seeing these errors?

The integration polls the LMS for status information periodically (and quite frequently). If the server isn’t available for some reason, you’ll see those timeouts - it just means that a poll has been missed most of the time. So, you’ll see this if you reboot your lms etc. However, I also sometimes see these when I haven’t rebooted my server (mine runs in an LXC on proxmox) and I’ve never been able to figure them out. I’ve just put it down the LMS just being upto something else and not responding on its json interface. You won’t see anything if you try and open that url directly unless you post the json data as well to tell it what you’re trying to do - but then you’d have to catch it in the few seconds it’s deciding not to respond. I actually just tell the logger to ignore those messages now - I’ve dug as much as I can into the library a while back and there’s nothing in there which says anything other than LMS isn’t responding for a few seconds so I’ve just parked it. If anyone has any views on what else we could look for, I’ll be happy to take another look of course.

1 Like

Thanks for the detailed reply. I’m going through my HA logs trying to clear up all the junk that is being spammed there, so this was one of the issues that needed sorting. It will make debugging easier in the future.
I’ve set the log level to fatal, which has solved the problem. For anyone else that has the problem, here’s the entry I put in my config.yaml:

# Silence the Squeezebox timeout errors..
logger:
  logs:
    homeassistant.components.squeezebox: fatal

You can be more selective with clearing up the logs using filtering. I do …

logger:
.....
  filters:
    pysqueezebox.server:
      - "Failed communicating with LMS(https://xxx:9000/jsonrpc.js): <class 'TimeoutError'>"

I didn’t know about the filter: parameter. That’s a neater solution :+1:.