Some TV models are not working

[Random-Stack-Random-Day]

Edited by @Ape:
I hijacked this issue to collect all instances where some random TV model does not work, but we don't know what is the cause or how it could be fixed. Some TV models might not simply support TCP/IP control at all, and some models may require a whole new protocol. When you have techinical details about a specific case that could be fixed please open a new issue.

---

Original message:
I'm wondering if anyone can confirm if this works for their JS9000 or H5203? Getting 'Connection refused' from the 9000 and no response from the 5203.

[davorf]

Hello!

I have H series TV too (H6500) and it doesn't work for me. No error message is shown and nothing is displayed on the TV.

Best regards,
Davor

[jessiewestlake]

Have you tried using the --method websocket parameter?

[ProZsolt]

Sadly H and J series TVs are using websockets, but a different protocol.

[riemers]

Newer models need to authorize the device first no? Do we have the new protocol, sounds like someone normally does :)

https://github.com/timelery/Samsung-RemoteControl

Although .net, i tried it and it can control my t.v. perhaps you can look at the code?

[Ape]

@riemers Which TV models did you test? I would be happy to merge new protocol support to samsungctl.

[riemers]

My tv is a UE55HU7500 above .net repo did seem to work with my t.v. i tried all combo's with your library but i never got a pincode. Perhaps yours has the 'authorize' only button and the pincode is newer? Just speculation here. But ofcourse, more then happy to help with testing on this particular model.

[phd1963]

Hello,

@riemers Thanks a lot for the link for remote control app! It works for my UE50H6400 model. However I need some more commands like the source changing (HDMI1, HDMI2...). Did you succeed to send such commands to your TV ?
@Ape I confirm that unfortunately your app doesn't work with my TV, with any parameter (port, protocol). If I can support in any way, feel free to contact me.

Friendly

Philippe

[jonny190]

Is there any progress on this?
Browsing to my TV http://192.168.5.91:8001/api/v2/ outputs :
{
"id": "09896801-00a0-1000-b47c-fc8f9080e621",
"name": "[TV]Samsung LED40",
"version": "2.0.24",
"device": {
"type": "Samsung SmartTV",
"duid": "09896801-00a0-1000-b47c-fc8f9080e621",
"model": "14_NT14U_2D_BT",
"modelName": "UE40HU6900",
"description": "Samsung TV RCR",
"networkType": "wired",
"ssid": "",
"ip": "192.168.5.91",
"firmwareVersion": "Unknown",
"name": "[TV]Samsung LED40",
"id": "09896801-00a0-1000-b47c-fc8f9080e621",
"udn": "09896801-00a0-1000-b47c-fc8f9080e621",
"resolution": "1920x1080",
"countryCode": "GB",
"msfVersion": "2.0.24",
"smartHubAgreement": "true",
"developerMode": "1",
"developerIP": "173.230.139.54"
},
"type": "Samsung SmartTV",
"uri": "http://192.168.5.91:8001/api/v2/"
}

[onemico]

Hi,

Anyone have any updates or ideas on this, the Windows .NET works on my TV too and I am 99% sure it is due to the PIN request for authentication, so is there any method to replicate that PIN input within this application.

I don't want to have to use a Windows system to do this, when i have multiple Pis setup that should be able to.

Any assistance greatly appreciated. my model is UE55H6200

[dextorer]

I tried both protocols (legacy/websocket), but no way of communicating with my UE55JU6000. I haven't had the chance of trying the .NET library, but it would be great if support could be added!

[Ape]

I'm hijacking this issue for all the cases where there is some random TV model that nobody has been able to get working.

There is no way for me to support all possible TV models. Some might not just support TCP/IP control at all, some probably use a different protocol, and there are probably some issues reported here that are just user errors and could be fixed with a correct configuration. The point is I cannot really help unless you can debug the issue to some specific cause. In that case, please open a new issue with technical details.