I can't find token about homebridge-samsungtv-control2 HOT 15 OPEN

I have the same issue. I cant find the token.

from homebridge-samsungtv-control2.

What do you mean with silent mode?

from homebridge-samsungtv-control2.

Hello, I will always show up the suggested method to obtain Token, but in the end it still cannot be obtained. And after I clicked Allow on my TV, nothing happened. Just keep repeating the above actions

1. Try another port npx homebridge-samsungtv-control pair2 192.168.1.xxx xx:xx:xx:xx:xx:xx --port 8001
2. Try another port npx homebridge-samsungtv-control pair2 192.168.1.xxx xx:xx:xx:xx:xx:xx --port 55000
3. Try the other pairing method npx homebridge-samsungtv-control pair1 192.168.1.xxx xx:xx:xx:xx:xx:xx
4. Try the legacy protocol npx homebridge-samsungtv-control legacy 192.168.1.xxx xx:xx:xx:xx:xx:xx

Keep repeating the prompt...but always can't find Token..

from homebridge-samsungtv-control2.

I have the same problem, clicking allow results in

That didn't work unfortunatelly. Here are some other possible solutions:
...

I've checked device connect manager on the tv and NodeJS Remote is set to allowed.

My model number is QN82Q65FN if that makes a difference.

from homebridge-samsungtv-control2.

I'm also having this issue - The "allow/deny" never comes up on my TV when trying to pair it. I've tried all of the above that everyone else has. And there's nothing in my connected devices.

When I connect my iPhone to the TV, I DO get the "allow/deny" popup on my TV. So, I know the TV is reachable on the network. I can also ping it.

from homebridge-samsungtv-control2.

I unfortunately don't have much influence on the actual libraries used to control the tv. If both of them are not able to control your tv chances are high that they just don't support your tv yet. The libraries being used are

• Option 1: samsung-tv-control ... used for pair2 and legacy
• Option 2: samsung-remote-models-2014-and-newer (my fork) ... used for pair1

...if one of these libraries works with your tv but this plugin doesn't please let me know so I can fix the problem.

I know this is not the most satisfying answer and I would also love to support every samsung tv out of the box but I unfortunately don't have the time to dive deeper into the control part of the plugin other than adding more library options to this plugin.

from homebridge-samsungtv-control2.

Oh, I know you can't support every single TV and I'd never expect that of you! My TV is a Q60R, which was released in 2019. So it's definitely a newer unit.

And yeah, I've tried those, unfortunately. I've tried all of those pairing options several times hoping they'd "just work".

from homebridge-samsungtv-control2.

Sorry to hear that it didn't work. I still hope that some day someone (or samsung themselves) publish a plugin that is able to control the whole samsung lineup.

from homebridge-samsungtv-control2.

Could the SmartThing page that generates tokens be used to obtain one and that works with the QLEDs of 2019?

from homebridge-samsungtv-control2.

It seems that my TV works with legacy mode (I was prompted to allow the connection and got the mute state on the TV) but didn't return any token

npx homebridge-samsungtv-control legacy 192.168.xxx.xx xx:xx:xx:xx:xx:xx
Sending the mute key to see if your device is controlable with the legacy protocol over port 55000.
Did the tv switch it's mute state? If yes then your tv supports the legacy protocol. Usually the plugin detects the appropriate port but you can also force this port by setting remoteControlPort to 55000

If it didn't work, here are some other possible solutions:
	1. Try pairing method 1 npx homebridge-samsungtv-control pair1 192.168.xxx.xx xx:xx:xx:xx:xx:xx
	2. Try pairing method 2 npx homebridge-samsungtv-control pair2 192.168.xxx.xx xx:xx:xx:xx:xx:xx

Obviously, I tried pair1 and 2 before legacy and got error on both (it's a 2012 TV model UE32D5500)

from homebridge-samsungtv-control2.

It seems that my TV works with legacy mode (I was prompted to allow the connection and got the mute state on the TV) but didn't return any token

npx homebridge-samsungtv-control legacy 192.168.xxx.xx xx:xx:xx:xx:xx:xx

Sending the mute key to see if your device is controlable with the legacy protocol over port 55000.

Did the tv switch it's mute state? If yes then your tv supports the legacy protocol. Usually the plugin detects the appropriate port but you can also force this port by setting remoteControlPort to 55000



If it didn't work, here are some other possible solutions:

	1. Try pairing method 1 npx homebridge-samsungtv-control pair1 192.168.xxx.xx xx:xx:xx:xx:xx:xx

	2. Try pairing method 2 npx homebridge-samsungtv-control pair2 192.168.xxx.xx xx:xx:xx:xx:xx:xx

Obviously, I tried pair1 and 2 before legacy and got error on both (it's a 2012 TV model UE32D5500)

Did you manage to get this to work with your tv?

from homebridge-samsungtv-control2.

from homebridge-samsungtv-control2.

@rafacampoamor did you end up figuring out how to enable/use legacy mode?!

from homebridge-samsungtv-control2.

@jat80 did you ever have any luck with this? Seems like it should work consider the legacy mode test is described but a mystery how to use it..

from homebridge-samsungtv-control2.

No sorry

from homebridge-samsungtv-control2.