Websocket APIs to communicate with samsung smart tv

By -

I am trying to communicate with my Samsung smart TV and I found on internet that it works with HTTP request.

There is some Samsung smart TV API on GitHub (even some in python) but they didn't work with my TV. Apparently, I have a not so common TV model.

Currently, I am stuck because I don't have the same answer from my TV when I am trying to do the same thing with two different websocket API.

WSCAT

$ wscat -c wss://192.168.1.20:8002/api/v2/channels/samsung.remote.control?name=dGVzdA== -n --no-color
(node:4547) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.

A pop-up appears on my TV asking me for the remote control authorization. Then I received a token in my terminal but I don't understand how I can retrieve it in bash.

Connected (press CTRL+C to quit)
< {"data":{"clients":[{"attributes":{"name":"dGVzdA=="},"connectTime":1601072715580,"deviceName":"dGVzdA==","id":"84a3df72-1910-447d-9b62-084b8435f1d","isHost":false}],"id":"84a3df72-1910-447d-9b62-084b8435f1d","token":"11235326"},"event":"ms.channel.connect"}
>

Python API

>>> import websocket, ssl
>>> uri = 'wss://192.168.1.20:8002/api/v2/channels/samsung.remote.control?name=dGVzdA=='
>>> ws = websocket.create_connection(uri, sslopt={"cert_reqs": ssl.CERT_NONE})

No pop-up appears on my TV. I tried the recv method on websocket but it never ends. So I tried the send method with a payload to decrease TV's sound volume.

>>> payload = '{"method":"ms.remote.control","params":{"Cmd":"Click","DataOfCmd":"KEY_VOLDOWN","Option":False,"TypeOfRemote":"SendRemoteKey"}}'
>>> ws.send(payload)
145

It answers me the code 145 and nothing is done on my TV.

Python API & WSCAT

First, I connect to my TV using wscat, I accept the connection on my TV.
Then, I connect using Python websocket API.
Finally, when I send the Volume down payload to the TV, the Python3 console still answers me the code 145, but my TV accepts my payload and the volume decrease.
No need of the token received with wscat ¯\_(ツ)_/¯ ?

Is there someone here able to understand and explain me this madness ?



from Recent Questions - Stack Overflow https://ift.tt/2S3CFip
https://ift.tt/eA8V8J

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more