Is the issue “Error when calling Sonos websocket: Connection timed out” just a fact of life? I see a lot of converstaion on the subject including the suggestion that increasing the scan to connect up to a 6 second will overcome the problem. 6 seconds is too long for fast moving sceans. Is there a better way to prevent the Error ?
That just means we made a call to the speaker and it didn’t respond. Usually means the network connection is poor/unstable, especially if you see it frequently.
Ah, thank you confirming what I thought I understood by that error message. I think it is Sonos’s dislike of being asked to run in my mesh network, although they are very stable in thier connections playing radio stations and music from my NAS. I wounder if hassio trys to get them to move ???