Yo'av Moshe

Ah okay! The error message made me think like I'm misunderstanding how to set the certificate. Glad to hear it will be added!

Thanks @greghesp ! I'm not sure how to use this though... Did you manage to get Catt to start casting the Spotify playlist using this track id? or am I...

What technically prevents Catt from sending the API connection to the casting device then? I mean, how is that different from casting a youtube video with Catt?

So I've tried a couple of things - first I tried using wireshark to see what kind of requests the browser sends to my Google Home when it makes it...

Just to clarify, I was trying to Wireshark the chrome browser when casting from the tidal website, not some native app. However, I'm not suggesting adding any Spotify/Tidal specific support....

Updating that I managed to decrypt the data sent using the instructions on the PyChromecast project (https://github.com/home-assistant-libs/pychromecast/issues/403) and added a pull request that allows queuing media (https://github.com/home-assistant-libs/pychromecast/pull/404). Hopefully once this...

Do you think we can add `catt next` and `catt prev` to go along `media_controller.queue_next()` and `media_controller.queue_prev()`? Let me know if you want me to open a new issue for...

The "enqueue" support was now released with Pychromecast 7.3.0. Should I submit a pull request for "add", "next" and "prev"? It seems like the whole Pychromecast 7 support is on...

Awesome! The `enqueue` isn't specific to Tidal, you can send it any media you want exactly like the `play_media()` was working before. It's just `play_media(URL, enqueue=True)`, which makes the Chromecast...

I'm sorry but I'm not sure what you mean... I honestly don't know much about the spec versions. All I know is that Pychromecast's `play_media()` method takes a URL as...