It seems you have Smart TV OS, which uses different and much simpler authentication mechanism than Tizen TV. There are tons of remote control apps available, even for smartphones. https://wiki.samygo.tv/index.php5?title ... l_protocol here is full protocol description. You can even write simple python script to do whatever you want.frankgeisler wrote:Excellent project! I tried to use the remote control exe from my Windows 7 Laptop to my Samsung SmartTV UE55H7080 but it's not found?
Also did a stealth scan for the ports:A call of http://192.168.1.104:8001/ms/1.0/ gives:Code: Select all
sudo nmap -v -p1-65535 -sS 192.168.1.104 Nmap scan report for samsung-tv.home (192.168.1.104) Host is up (0.0039s latency). Not shown: 65525 closed ports PORT STATE SERVICE 5053/tcp open rlm 7011/tcp open unknown 7676/tcp open imqbrokerd 8000/tcp open http-alt 8001/tcp open vcom-tunnel 8020/tcp open unknown 8080/tcp open http-proxy 8443/tcp open https-alt 9090/tcp open zeus-admin 15500/tcp open unknown MAC Address: xxxx (Samsung Electronics)
A call of http://192.168.1.104:8001/ws/apps/ gives:Code: Select all
{ "DUID": "07270e01-0078-1000-8cd0-5056bf79a13d", "Model": "14_GOLFS", "ModelName": "UE55H7000", "ModelDescription": "Samsung TV RCR", "NetworkType": "wired", "SSID": "", "IP": "192.168.1.104", "FirmwareVersion": "Unknown", "DeviceName": "[TV] Samsung", "DeviceID": "07270e01-0078-1000-8cd0-5056bf79a13d", "UDN": "07270e01-0078-1000-8cd0-5056bf79a13d", "Resolution": "1920x1080", "CountryCode": "CH", "SmartHubAgreement": "true", "ServiceURI": "http://192.168.1.104:8001/ms/1.0/", "DialURI": "http://192.168.1.104:8001/ws/apps/", "Capabilities": [ { "name": "samsung:multiscreen:1", "port": "8001", "location": "/ms/1.0/" } ] }
Ultimately I want to remote control my TV from my Fibaro SmartHome which is based on Linux and Lua - probably similar to what DieterKoblenz mentioned earlier in this topic.Code: Select all
This XML file does not appear to have any style information associated with it. The document tree is shown below. <root xmlns="urn:schemas-upnp-org:device-1-0" xmlns:sec="http://www.sec.co.kr/dlna"> <specVersion> <major>1</major> <minor>0</minor> </specVersion> <device> <deviceType>urn:dial-multiscreen-org:device:dialreceiver:1</deviceType> <friendlyName>[TV] Samsung</friendlyName> <manufacturer>Samsung Electronics</manufacturer> <manufacturerURL>http://www.samsung.com</manufacturerURL> <modelDescription>Samsung TV RCR</modelDescription> <modelName>14_GOLFS</modelName> <UDN>07270e01-0078-1000-8cd0-5056bf79a13d</UDN> <sec:Capabilities> <sec:Capability name="samsung:multiscreen:1" port="8001" location="/ms/1.0/"/> </sec:Capabilities> <serviceList> <service> <serviceType>urn:dial-multiscreen-org:service:dial:1</serviceType> <serviceId>urn:dial-multiscreen-org:service:dial:1</serviceId> <controlURL/> <eventSubURL/> <SCPDURL/> </service> </serviceList> <presentationURL>/</presentationURL> </device> </root>
I am not sure how to proceed from here - am I missing the point?
Cheers, Frank
HU Websockets receiveCommon protocol
Re: HU Websockets receiveCommon protocol
Re: HU Websockets receiveCommon protocol
Currently discussed "protocol" came with H series (as title says), wasn't Tizen yet
I do NOT receive any PM. Please use forum.
Re: HU Websockets receiveCommon protocol
Hi everybody,
I just found out that you can trigger the pin entering message on the tv by setting step to 0 in the pairing request:
Furthermore there is an upnp method sendKeyCode for the service urn:samsung.com:serviceId:MultiScreenService on my tizen tv that looks similar to the old network protocol except for the fact that a keyCode number and a keyDescription string are required. Unfortunately I could not get any upnp setter method to work but at least the getters work without any pairing or authentication.
I just found out that you can trigger the pin entering message on the tv by setting step to 0 in the pairing request:
Code: Select all
http://<ip>:8080/ws/pairing?step=0&app_id=my-app&device_id=my-device
Re: HU Websockets receiveCommon protocol
You need correct session_id, all pretty straightforward. Get some from official client. Then it should simply workmmende wrote:Hi everybody,
I just found out that you can trigger the pin entering message on the tv by setting step to 0 in the pairing request:Furthermore there is an upnp method sendKeyCode for the service urn:samsung.com:serviceId:MultiScreenService on my tizen tv that looks similar to the old network protocol except for the fact that a keyCode number and a keyDescription string are required. Unfortunately I could not get any upnp setter method to work but at least the getters work without any pairing or authentication.Code: Select all
http://<ip>:8080/ws/pairing?step=0&app_id=my-app&device_id=my-device
I do NOT support "latest fw" at ALL. If you have one you should block updates on router and wait for it to STOP being "latest":)
If you want me to help you please paste FULL log(s) to "spoiler"/"code" bbcodes or provide link(s) to pasted file(s) on https://pastebin.com Otherwise "NO HELP"!!!
If you want root DISABLE internet access to your device!!!!
DO NOT EVER INSTALL FIRMWARE UPGRADE !!!!
If you want me to help you please paste FULL log(s) to "spoiler"/"code" bbcodes or provide link(s) to pasted file(s) on https://pastebin.com Otherwise "NO HELP"!!!
If you want root DISABLE internet access to your device!!!!
DO NOT EVER INSTALL FIRMWARE UPGRADE !!!!
Re: HU Websockets receiveCommon protocol
Interestingly, there were recent contributions to https://github.com/Ape/samsungctl including some more keys mapping.
Tinkerer & owner of a UN48H6400