[No Longer Maintained] Squeezebox Integration (Logitech Media Server)

⚙️ Custom Apps and Drivers
162

Squeezebox Player v2.4 is released. This adds a new "activity" attribute which supports the "activityState" attribute in the Google Home mediaState device trait. It indicates if the player is in use and allows Google Home to identify if short commands "stop", "volume up" etc. are intended for the player.

To use this feature you need to be using the excellent Google Home Community integration rather than the built-in one. Define a device type to use for your players and add the Media State trait (I also added On/Off, Volume and Transport Control states which integrates the players' functions with Google more completely).

164

I'm thinking of removing the child power switch device for players. I implemented it for use by the built in Google home integration so players don't have to be directly included (as they are shown as lights due to their level attribute). However the Google Home Community integration is much more capable and doesn't require this extra device.

Is anyone using this feature? Please let me know if you are using it and would like me not to remove it!

165

I'm not using it. :slight_smile:

1 Like
166

I use the dimmer tile in dashboards... allows me on/off and volume control in one simple tile. No idea if this is the power you speak of... but i use these tiles many times a day and will cry (a little) if you take it away!

1 Like
167

That sounds like you've added the main player device to the dashboard rather than selected to have extra child device on/off switches. So that's all good, it won't change anything for you :smile:

168

I have released v2.3 of the Squeezebox Connect app, and v2.5 of the Squeezebox Player device. This release removes the extra child power switch. NB: The child switch for All Alarms on/off is unaffected.

Edit: There is currently an issue with Github's raw file cache which means updating via HPM may not work as HPM will not see the update until the problem is resolved.

169

Hey @xap , ive updated both the HE squeeze per your last, and recently also updated the LMS running in a docker container on a synology box... (so dont know which is the cause, but im starting here). Not sure exactly when it started, but "recently" HE has stopped working with the LMS and im seeing tgis error in logs. Rebooting HE has fixed the symtom, restarting the lms container has not. Any ideas? Error:

dev:8882023-02-25 04:50:24.860 PMerrorCLI Connection Failure (attempting to reconnect): receive error: Stream is closed

170

Hey @bikesquid. I also run LMS as a container on a Synology. I'm running LMS 8.3.2 with HE 2.3.4.153. The only time I see that error is if the Synology reboots or the network is down for some reason. In those cases the Squeezebox Server device should retry every minute and eventually reconnect. Here's an example of what I see in the logs in those cases.

image
image1166×146 30.4 KB

How does that compare to what you see in the logs?
I'm assuming that you've been running LMS as a container for some time? So all the docker port mappings are good (or you're running the container in host network mode)? How often does this error occur? And can you think of anything else that happens on the network at the same time as you've seen the error?

171

Thanks for the time mate. Always appreciate your efforts!.
My logs show more or less the same. But... totally different :wink:.
Even after it shows connected in logs it will show disconnected in apps/device screens and the server device won't 'turn on'... it quickly resets to off. Ditto initialize, nothing good comes of it. Rebooting the HE box seems to correct the problem for a while... but it disconnects again. (i.e. before reboot on/off stays off, after reboot on/off does on and off and back on and back off appropriate with button pushes etc) How long I donno, this one's like watching paint dry... with music on... so I wonder off... But the below logs will give you some idea of intervals at least related to refreshes showing it disconnected/reconnected. My network is stable and the synology setup (other than LMS version hasn't changed for "years". Restarting the container doesn't fix the problem... so I assume whatever is being reset with the HE reboot is where the problem is, but I have no other facts to hang that assumption on. It occurs

As to your host network mode question... If you're talking about the attached config screen cap, yes. If you speak of something else... idonno, point me in the right direction and I'm happy to dig. LMS server v8.3.1-1670817815 and HE 2.3.4.153 on a C-7 and this is running with a Netgear Orbi RBRE960 Mesh fully updated and all wired connections via TP-link smart-switch. NO network gliches (internet farts now and then, but local is rock solid.)

image
image1036×811 33.7 KB

Here's a longer log list in case that helps understand the issue (I'm not seeing "(Will reattempt in 1 minute)" like your log and there are NO unable to connect connection refused messages or telnet closed messages....

dev:8882023-02-26 09:24:07.793 AMinfoSqueezebox CLI Connected: 192.168.1.22:9090

dev:8882023-02-26 09:24:07.780 AMerrorCLI Connection Failure (attempting to reconnect): receive error: Stream is closed

dev:8882023-02-26 09:23:57.746 AMinfoSqueezebox CLI Connected: 192.168.1.22:9090

dev:8882023-02-26 09:23:57.735 AMerrorCLI Connection Failure (attempting to reconnect): receive error: Stream is closed

dev:8882023-02-26 09:23:47.702 AMinfoSqueezebox CLI Connected: 192.168.1.22:9090

dev:8882023-02-26 09:23:47.691 AMerrorCLI Connection Failure (attempting to reconnect): receive error: Stream is closed

dev:8882023-02-26 09:23:39.133 AMinfoSqueezebox CLI Connected: 192.168.1.22:9090

dev:8882023-02-26 09:23:37.651 AMerrorCLI Connection Failure (attempting to reconnect): receive error: Stream is closed

dev:8882023-02-26 09:23:34.658 AMinfoSqueezebox CLI Connected: 192.168.1.22:9090

dev:8882023-02-26 09:23:32.248 AMerrorCLI Connection Failure (attempting to reconnect): receive error: Stream is closed

dev:8882023-02-26 09:10:33.324 AMinfoSqueezebox CLI Connected: 192.168.1.22:9090

dev:8882023-02-26 09:08:41.461 AMinfoSqueezebox CLI Connected: 192.168.1.22:9090

dev:8882023-02-26 09:08:41.452 AMerrorCLI Connection Failure (attempting to reconnect): receive error: Stream is closed

dev:8882023-02-26 09:08:31.424 AMinfoSqueezebox CLI Connected: 192.168.1.22:9090

dev:8882023-02-26 09:08:31.416 AMerrorCLI Connection Failure (attempting to reconnect): receive error: Stream is closed

dev:8882023-02-26 09:08:21.388 AMinfoSqueezebox CLI Connected: 192.168.1.22:9090

dev:8882023-02-26 09:08:21.377 AMerrorCLI Connection Failure (attempting to reconnect): receive error: Stream is closed

dev:8882023-02-26 09:08:16.522 AMinfoSqueezebox CLI Connected: 192.168.1.22:9090

dev:8882023-02-26 09:08:16.513 AMerrorCLI Connection Failure (attempting to reconnect): receive error: Stream is closed

dev:8882023-02-26 09:08:06.480 AMinfoSqueezebox CLI Connected: 192.168.1.22:9090

dev:8882023-02-26 09:08:06.472 AMerrorCLI Connection Failure (attempting to reconnect): receive error: Stream is closed

dev:8882023-02-26 09:07:56.443 AMinfoSqueezebox CLI Connected: 192.168.1.22:9090

dev:8882023-02-26 09:07:56.434 AMerrorCLI Connection Failure (attempting to reconnect): receive error: Stream is closed

dev:8882023-02-26 09:07:46.379 AMinfoSqueezebox CLI Connected: 192.168.1.22:9090

dev:8882023-02-26 09:07:46.369 AMerrorCLI Connection Failure (attempting to reconnect): receive error: Stream is closed

dev:8882023-02-26 09:07:36.340 AMinfoSqueezebox CLI Connected: 192.168.1.22:9090

dev:8882023-02-26 09:07:36.332 AMerrorCLI Connection Failure (attempting to reconnect): receive error: Stream is closed

dev:8882023-02-26 09:07:34.481 AMwarnCannot send message while disconnected, connect using initialise() or on()

dev:8882023-02-26 09:07:34.455 AMwarnCannot send message while disconnected, connect using initialise() or on()

dev:8882023-02-26 09:07:34.429 AMwarnCannot send message while disconnected, connect using initialise() or on()

dev:8882023-02-26 09:07:34.399 AMwarnCannot send message while disconnected, connect using initialise() or on()

dev:8882023-02-26 09:07:34.373 AMwarnCannot send message while disconnected, connect using initialise() or on()

dev:8882023-02-26 09:07:34.344 AMwarnCannot send message while disconnected, connect using initialise() or on()

dev:8882023-02-26 09:07:34.271 AMwarnCannot send message while disconnected, connect using initialise() or on()

dev:8882023-02-26 09:07:26.300 AMinfoSqueezebox CLI Connected: 192.168.1.22:9090

dev:8882023-02-26 09:07:26.292 AMerrorCLI Connection Failure (attempting to reconnect): receive error: Stream is closed

dev:8882023-02-26 09:07:22.579 AMwarnCannot send message while disconnected, connect using initialise() or on()

dev:8882023-02-26 09:07:18.335 AMwarnCannot send message while disconnected, connect using initialise() or on()

dev:8882023-02-26 09:07:18.310 AMwarnCannot send message while disconnected, connect using initialise() or on()

dev:8882023-02-26 09:07:18.284 AMwarnCannot send message while disconnected, connect using initialise() or on()

172

And PS I have no idea what's trying to send a mesage... I'm not... on purpose anyway, so maybe related maybe not :man_shrugging:

173

Few questions to get a bit more info:

  • Are you installing the squeezebox controller direct from Github or are you using Hubitat Package Manager?
  • Can you confirm the version of your Squeezebox Server device code?
    Also:
  • Have you enabled password protection on your LMS server? If so, are the details correct in Squeezebox Connect?
  • Do you have any extra security or firewall setup on your nas box?
174

[quote="xap, post:173, topic:4489, full:true"]
Few questions to get a bit more info:

  • Are you installing the squeezebox controller direct from Github or are you using Hubitat Package Manager? Package Manager
  • Can you confirm the version of your Squeezebox Server device code? I don't see an explicit version #, from the code it looks the same as the github current... here's the changelog top line in my code

/ ChangeLog:*
** * 09/11/2021 - v2.2.2 - Catch any Exception for connection retry**

Also:

  • Have you enabled password protection on your LMS server? If so, are the details correct in Squeezebox Connect? NO password protection
  • Do you have any extra security or firewall setup on your nas box? NO, but don't tell anyone! Shhhh...
    [/quote] see bold above.
175

Can you see any errors or clues in the logs for the container?

176

Nope, just shows start container,... and wait for it... stop container...

177

Are you able to control the players ok via the LMS web UI?

178

Yes

179

And via several other apps...such as squeezer and squeezeplayer... donno if they us cli or regular web port.

180

Wow. I'm pretty stumped at this point. Updating LMS to the latest version may help. You could try to telnet from a pc to connect to 192.168.1.22:9090 directly (I use PuTTY on Windows). See if the command "players list" gives back data. If that works and doesn't drop the connection then it might indicate the issue is something else on the hub? Are you using any other telnet based drivers?

181

Ill have to drill into the HE hub later, life is about to overtake my sunday troubleshooting! Telnet session returns the list of players, I can do that repeatedly without it dropping me. I don't recall off hand if anything else is telnet on the hub, I'll look into it and let you know if I figure anything out. Thank you for the time and effort to help... Much Appreciated

182

No probs. If you enable debug logging in the app you might get some more logs which could give us an idea what's going on. If not I'll look into adding more logging.