Documentation of the twitch chromecast options

gtmanfred · September 14, 2015, 4:58am

Hey!

I am working on making a program that runs and watches for streams that I specify to start, and when they start to automatically launch it on my chromecast.

Unfortunately I can’t seem to find any documentation on what to send to the chromecast for the twitch app, I can successfully launch it using pychromecast and the Receiver class

github.com

balloob/pychromecast/blob/master/pychromecast/socket_client.py#L548


    # now read the payload
    payload = self._read_bytes_from_socket(read_len)


    # pylint: disable=no-member
    message = cast_channel_pb2.CastMessage()
    message.ParseFromString(payload)


    return message


# pylint: disable=too-many-arguments
def send_message(self, destination_id, namespace, data,
                 inc_session_id=False, callback_function=False,
                 no_add_request_id=False, force=False):
    """ Send a message to the Chromecast. """


    # namespace is a string containing namespace
    # data is a dict that will be converted to json
    # wait_for_response only works if we have a request id


    # If channel is not open yet, connect to it.
    self._ensure_channel_connected(destination_id)

By specifying yalls app_id from here http://clients3.google.com/cast/chromecast/device/baseconfig

But I can’t seem to find anything documenting what to send once the app is launched.

In [14]: cast.socket_client.receiver_controller.send_message({‘url’: ‘http://www.twitch.tv/gsl’})

In [15]: WARNING:pychromecast.socket_client:Message unhandled: Message urn:x-cast:com.google.cast.receiver from receiver-0 to sender-0: {u’reason’: u’INVALID_PARAMS’, u’type’: u’INVALID_REQUEST’, u’requestId’: 34}

I tried using just url: and the twitch stream, but that doesn’t work, but there are no hints for how to get it to work.

Any help would be appreciated.

Thanks!
Daniel

gtmanfred · September 15, 2015, 2:25am

Looks like I might be able to reverse engineer it from the reciever.js here.

system · October 15, 2015, 2:25am

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.