Does castblock work with casts to Youtube app from Samsung smart TV?

[garret]

I have a Samsung Smart TV with Youtube app installed. I installed castblock on my raspberry pi through Docker following the guide on another issue posted here. However, when I cast something from the Youtube app on my android phone to the Youtube app on the Samsung Smart TV, I can still see ads, thus indicating that castblock might not work.

So I ask: is it supposed to work or castblock only works with a chromecast (which I don't own) inserted?

If it should work with the Youtube Samsung app as well, is there a way to check that castblock is running smoothly? When I start the docker container on the raspberry pi I do not get any errors.

[stephen304]

I'm not sure if it works with built in chromecast, maybe try running go-chromecast status and see if it shows up. Depending on how the app works, you may need to have something playing for it to be detected, I'm not sure. Let me know if you manage to get it to work.

[garret]

It seems it does not work. When casting from my phone to the Youtube TV app I gave that command from inside the container and in the list of devices I don't see my TV :(

bash-5.0# go-chromecast status
Found 8 cast dns entries, select one:
[...list of devices...]
Enter selection:

[stephen304]

Bummer. You could see if the go-chromecast dev knows anything about those tv apps and whether it's possible to add support. I don't know much about the protocol which is why I used his code.

[she11sh0cked]

Any news here? There is no new issue at go-chromecast.

[0ddb0d]

Samsung TV's don't run the Chromecast built-in service, older devices used the DIAL (DIscovery And Launch) protocol for second screen playback with newer models using Samsung's proprietary Smart View.

[nullstalgia]

I wonder how the YouTube app finds the TV then. Probably some proprietary signaling, but I wouldn't be surprised if its been poked at by the likes of the Home Assistant team or similar