You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 10, 2024. It is now read-only.
Hi everybody. My office has me investigating a couple TVs for a large installation here. One is the Samsung QB65H-N, one of their commercial panels, and we'd hope it would be network controllable.
Sadly, not so much.
samsungctl looks promising, but doesn't seem to interface with the screen at all. It can get it up on the network, and an nmap reveals this:
Starting Nmap 7.40 ( https://nmap.org ) at 2019-09-16 12:38 EDT
Nmap scan report for 192.168.1.209
Host is up (0.0045s latency).
Not shown: 65531 closed ports
PORT STATE SERVICE
1515/tcp open ifor-protocol
9197/tcp open unknown
38485/tcp open unknown
40000/tcp open safetynetp
Nmap done: 1 IP address (1 host up) scanned in 5.26 seconds
Okay, potentially promising. However, none of those ports responds to samsungctl for either legacy or websocket control. If I curl them, I only get a SOAP reply on port 9197.
This seems to tell me this unit just doesn't support the type of control samsungctl does? Or is there some magic dance I need to do to enable it? Any guidance is appreciated. Our other option is an LG unit that supports SNMP (yay) but requires an NDA to get any documentation on it (BOO!)
The text was updated successfully, but these errors were encountered:
This could be a UPNP API (Assuming on the xml tags)
Have you tried to control the panel via a UPNP software/requests ?
Some UDP Broadcasts from that display?
Also what are you want to do with the Smart Signage panel ?
They can be controlled via "MagicInfo Server" from samsung.
Perhaps you can do some reverse engineering...?
Hi! I had the same issue with my home info display (Samsung QB13R-T). I tried also the free (up to 25 devices) "Magicinfo Server" but that didn't seem to fit my purpose. Samsung has actually quite good documentation on MDC protocol and I ended up using that one to control my display power state. If you're interested in more details, I have written a blog post about this:
Hi everybody. My office has me investigating a couple TVs for a large installation here. One is the Samsung QB65H-N, one of their commercial panels, and we'd hope it would be network controllable.
Sadly, not so much.
samsungctl looks promising, but doesn't seem to interface with the screen at all. It can get it up on the network, and an nmap reveals this:
Okay, potentially promising. However, none of those ports responds to samsungctl for either legacy or websocket control. If I curl them, I only get a SOAP reply on port 9197.
This seems to tell me this unit just doesn't support the type of control samsungctl does? Or is there some magic dance I need to do to enable it? Any guidance is appreciated. Our other option is an LG unit that supports SNMP (yay) but requires an NDA to get any documentation on it (BOO!)
The text was updated successfully, but these errors were encountered: