Announce: CastBridge = integrate Chromecast players with LMS (squeeze2cast)

[Paul Webster]

Perhaps should make it possible to disable the sending of the JavaScript app to the ChromeCast device just in case this becomes a feature on other Google devices after a firmware update.

[slartibartfast]

I'm having trouble getting a Nest Mini to work with the new 2.2.x version

A separate Chromecast Audio works great with 2.2.x but the Nest Mini won't play anything, consistently reports a launch error trying to start the new CC app

[08:13:44.846933] SendCastMessage:125 [0x7f4cf002cfd0]: Cast sending: {"type":"CONNECT"}
[08:13:55.874108] SendCastMessage:125 [0x7f4cf002cfd0]: Cast sending: {"type":"LAUNCH","requestId":1,"appId":"46C1A81 9"}
[08:13:55.943777] CastSocketThread:603 [0xb3fc20]: type:LAUNCH_ERROR (id:1)
[08:15:42.008275] SendCastMessage:125 [0x7f4cf002cfd0]: Cast sending: {"type":"LAUNCH","requestId":2,"appId":"46C1A81 9"}
[08:15:42.070500] CastSocketThread:603 [0xb3fc20]: type:LAUNCH_ERROR (id:2)

It's been power cycled many times but doesn't seem to want to play ball

Cast firmware 1.56.348702
LMS 8.4.0
Chromecast bridge 2.2.6

Any ideas why the Nest Mini would object to the new CC app ?

At the moment still having to use 2.1.16 in order to cast to the Nest Mini

My Nest Mini seems to be fine with 2.2.6.

[The Groundsman]

My Nest Mini seems to be fine with 2.2.6.

Me too - may be something to do with your network setup?

[SteveBamber]

Me too - may be something to do with your network setup?

If it was the network then you would expect it to affect the Chromecast Audio as well - but that has no problem launching the new app.

It's only the Nest Mini that's affected - presume your Nest Mini is running the same firmware version ?

[slartibartfast]

If it was the network then you would expect it to affect the Chromecast Audio as well - but that has no problem launching the new app.

It's only the Nest Mini that's affected - presume your Nest Mini is running the same firmware version ?

Same firmware for me. I also have transcode set to FLAC and flow mode enabled if that makes a difference.

[SteveBamber]

Same firmware for me. I also have transcode set to FLAC and flow mode enabled if that makes a difference.

Thanks - no luck with or without transcode set, it's a bit of a head scratcher

Nest Mini - fail

[15:08:37.003345] CastLoad:177 [0xb3fc20]: Queuing LOAD
[15:08:37.003359] sq_callback:336 [0xb3fc20]: current URI (s:0) http://192.168.0.10:37521/bridge-1.flac
[15:08:37.003367] process_start:1245 [0xaa5260]: codec:f, ch:0, s:0, r:0
[15:08:37.003424] sendSTAT:159 [0xaa5260]: STAT:[STMc] msplayed 0
[15:08:37.003453] sq_callback:389 [0xb3fc20]: LMS volume (0..128) 2 => CC 0.0600
[15:08:37.060311] SendCastMessage:125 [0x7fb58002cfc0]: Cast sending: {"type":"LAUNCH","requestId":1,"appId":"46C1A81 9"}
[15:08:37.060335] CastSocketThread:631 [0xb3fc20]: Launching receiver 1
[15:08:37.088794] CastSetDeviceVolume:375 [0xb3fc20]: Queuing SET_VOLUME
[15:08:37.088832] CastPlay:264 [0xb3fc20]: Queuing PLAY
[15:08:37.119698] CastSocketThread:603 [0xb3fc20]: type:LAUNCH_ERROR (id:1)

Chromecast Audio - no issues

[15:11:59.433600] SendCastMessage:125 [0x7fb5800317a0]: Cast sending: {"type":"LAUNCH","requestId":1,"appId":"46C1A81 9"}
[15:11:59.433621] LaunchReceiver:188 [0xb40950]: Launching receiver 1
[15:11:59.433640] CastLoad:177 [0xb40950]: Queuing LOAD
[15:11:59.433645] sq_callback:336 [0xb40950]: current URI (s:0) http://192.168.0.10:58795/bridge-1.flac
[15:11:59.433650] process_start:1245 [0xaa9f98]: codec:c, ch:0, s:0, r:0
[15:11:59.433699] sendSTAT:159 [0xaa9f98]: STAT:[STMc] msplayed 0
[15:11:59.433728] sq_callback:389 [0xb40950]: LMS volume (0..128) 5 => CC 0.1000
[15:11:59.448718] CastSetDeviceVolume:375 [0xb40950]: Queuing SET_VOLUME
[15:11:59.448741] CastPlay:264 [0xb40950]: Queuing PLAY
[15:12:00.851231] CastSocketThread:603 [0xb40950]: type:RECEIVER_STATUS (id:1)
[15:12:00.851288] CastSocketThread:659 [0xb40950]: Receiver launched
[15:12:00.851365] SendCastMessage:125 [0x7fb5800317a0]: Cast sending: {"type":"CONNECT","origin":{}}
[15:12:00.851403] ProcessQueue:485 [0xb40950]: Processing LOAD (id:2)
[15:12:00.851499] SendCastMessage:125 [0x7fb5800317a0]: Cast sending: {

[SteveBamber]

Thanks - no luck with or without transcode set, it's a bit of a head scratcher

It was some kind of issue with the Nest Mini - not sure what, but a full factory reset seems to have fixed it.

It's now happy to cast with 2.2.6 - when in doubt hit it with a big stick...

[edw5]

I don't know how odd it is but I've also never experienced a problem like this with the UPNP bridge or with any other Windows app --- LMS plugin or otherwise. I wish my problem only required restarting the bridge instead of rebooting the machine though. I envy you.

I should have asked this before but didn't. How long do you give the restarted bridge before you decide it isn't going to detect any devices? Until recently I was restarting every couple of days, and it wasn't unusual for it to take 5 or 10 minutes before the first device was detected.

There's no indication that Philippe has seen my most recent post yet, but I'm confident that what I say there is correct. The bridge has been running successfully for more than 100 hours now, with all but one of my devices disabled through config.

[SamY]

I should have asked this before but didn't. How long do you give the restarted bridge before you decide it isn't going to detect any devices? Until recently I was restarting every couple of days, and it wasn't unusual for it to take 5 or 10 minutes before the first device was detected.

There's no indication that Philippe has seen my most recent post yet, but I'm confident that what I say there is correct. The bridge has been running successfully for more than 100 hours now, with all but one of my devices disabled through config.

Whenever the bridge is started (except when the problem is occurring, in which case I have to reboot), the devices are detected immediately. At the moment, the plugin has been running successfully for 7 days without a reboot, which might be a new record for me. During that time, however, I rebooted my router which is something I rarely do. The next time the CC devices go missing, I'll check the config file per your post.

[mikk64]

Hi to everybody!
big fan of this plugin! It saved my listening pleasure!
now, my problem...i have 1 chromecast audio, 2 nest audio and 1 nest hub, in my bedroom...and the last is the weak point
all of the others are well going, without any problem, the nest hub, almost each time i start playn' (let's, each night, one time a day, and each morning as an alarm), it stops about few seconds after, let's say usually 15-30"...and at the second attempt usually goes without any other problem (even not always)
this problem occurs 9 times on 10, so, as a workaround, as alarm, i set two alarm and the second do the job...
any idea?
i am on the last LMS, 8.4 always updated, picore player, wifi at home and CCB 2.2.6
thanks for helping!

[philippe_44]

Hi to everybody!
big fan of this plugin! It saved my listening pleasure!
now, my problem...i have 1 chromecast audio, 2 nest audio and 1 nest hub, in my bedroom...and the last is the weak point
all of the others are well going, without any problem, the nest hub, almost each time i start playn' (let's, each night, one time a day, and each morning as an alarm), it stops about few seconds after, let's say usually 15-30"...and at the second attempt usually goes without any other problem (even not always)
this problem occurs 9 times on 10, so, as a workaround, as alarm, i set two alarm and the second do the job...
any idea?
i am on the last LMS, 8.4 always updated, picore player, wifi at home and CCB 2.2.6
thanks for helping!

It's probably the loading of the dedicated apps in the CC device (it was a generic player before 2.2.x but now to have metadata displayed, I needed a custom "receiver"). I don't know why this happens from time to time.

[mikk64]

It's probably the loading of the dedicated apps in the CC device (it was a generic player before 2.2.x but now to have metadata displayed, I needed a custom "receiver"). I don't know why this happens from time to time.

thanks for answering, Philippe
as i said, not a big deal, really
and, during the last days, it's not happening anymore....fingers crossed!

[philippe_44]

thanks for answering, Philippe
as i said, not a big deal, really
and, during the last days, it's not happening anymore....fingers crossed!

It's probably a timing issue, I might have an idea why, but I can investigate for now

[maurizio53]

Suddenly all my chromecasts stopped to play any song. Where i can begin to understand what happens? Where to see the logs of the chromecast bridge plugin?
This is the log i see:

Starting Squeeze2cast: /usr/local/slimserver/Cache/InstalledPlugins/Plugins/CastBridge/Bin/squeeze2cast-linux-arm -Z -I -f /usr/local/slimserver/Logs/castbridge.log -d cast=debug -x /usr/local/slimserver/prefs/castbridge.xml
[13:25:29.168356] main:1290 Starting squeeze2cast version: v2.2.6 (May 14 2023 @ 01:30:55)
[13:25:29.177016] Start:1049 Binding to 192.168.1.84 (http:0)
[13:25:29.352053] AddCastDevice:989 [0x1f09d0]: adding renderer (Salotto Audio) with mac CCCC-8EEB5CBE
[13:25:29.359934] mDNSsearchCallback:865 Updating configuration /usr/local/slimserver/prefs/castbridge.xml
[13:25:29.361316] slimproto:878 squeezelite [0x15d078] <=> player [0x1f09d0]
[13:25:29.361383] slimproto:879 [0x15d078] connecting to 192.168.1.84:3483
[13:25:29.362154] slimproto:909 [0x15d078] connected
[13:25:29.362383] sendHELO:125 [0x15d078] cap: CanHTTPS=1,Model=squeezelite,ModelName=CastBridge, AccuratePlayPoints=0,HasDigitalOut=1,MaxSampleRate =96000,aac,ogg,ops,ogf,flc,alc,wav,aif,pcm,mp3
[13:25:29.362874] AddCastDevice:989 [0x1f16c0]: adding renderer (Google Home) with mac CCCC-EFE7AA2E
[13:25:29.367031] mDNSsearchCallback:865 Updating configuration /usr/local/slimserver/prefs/castbridge.xml
[13:25:29.398374] slimproto:878 squeezelite [0x161a38] <=> player [0x1f16c0]
[13:25:29.398434] slimproto:879 [0x161a38] connecting to 192.168.1.84:3483
[13:25:29.398709] slimproto:909 [0x161a38] connected
[13:25:29.398937] sendHELO:125 [0x161a38] cap: CanHTTPS=1,Model=squeezelite,ModelName=CastBridge, AccuratePlayPoints=0,HasDigitalOut=1,MaxSampleRate =96000,aac,ogg,ops,ogf,flc,alc,wav,aif,pcm,mp3
[13:26:05.404200] slimproto_run:574 [0x15d078] No messages from server - connection dead
[13:26:05.436401] slimproto_run:574 [0x161a38] No messages from server - connection dead
[13:26:05.505008] slimproto:909 [0x15d078] connected
[13:26:05.505099] sendHELO:125 [0x15d078] cap: CanHTTPS=1,Model=squeezelite,ModelName=CastBridge, AccuratePlayPoints=0,HasDigitalOut=1,MaxSampleRate =96000,aac,ogg,ops,ogf,flc,alc,wav,aif,pcm,mp3
[13:26:05.536926] slimproto:909 [0x161a38] connected
[13:26:05.537005] sendHELO:125 [0x161a38] cap: CanHTTPS=1,Model=squeezelite,ModelName=CastBridge, AccuratePlayPoints=0,HasDigitalOut=1,MaxSampleRate =96000,aac,ogg,ops,ogf,flc,alc,wav,aif,pcm,mp3
[13:26:05.648582] CastConnect:239 [0x1f09d0]: SSL connection opened [0x7580d970]
[13:26:05.648808] SendCastMessage:125 [0x7580d970]: Cast sending: {"type":"CONNECT"}
[13:26:05.649416] sq_callback:389 [0x1f09d0]: LMS volume (0..128) 54 => CC 0.5500
[13:26:05.651524] CastConnect:239 [0x1f16c0]: SSL connection opened [0x758139e8]
[13:26:05.651662] SendCastMessage:125 [0x758139e8]: Cast sending: {"type":"CONNECT"}
[13:26:05.652194] sq_callback:389 [0x1f16c0]: LMS volume (0..128) 75 => CC 0.6900
[13:26:16.967636] CastStop:311 [0x1f09d0]: Stop w/o session or connect

Can somebody help me ? I am not so expert....

[philippe_44]

Suddenly all my chromecasts stopped to play any song. Where i can begin to understand what happens? Where to see the logs of the chromecast bridge plugin?

In the plugin's settings (in LMS settings, tab "advanced", dropdown menu "Chromecast Bridge"