I am using this node:
node-red-contrib-samsung-tv-control
It says a token should show up on the debug window, but I see nothing.
Does anybody have any information is this node is working?
I am using this node:
It says a token should show up on the debug window, but I see nothing.
Does anybody have any information is this node is working?
that node does not work reliably
.. i had it working once but after an upgrade I never got it working again .. due to token issue.
I think the network comms or handshake with the TV is not properly implemented
Oh well... apparently you can try the Samsung API too...
With so many nodes in Node-RED, would be nice to have a way to know which ones are working and which ones are not..
Thank you!
How old is the TV?
Does it have Smart things?
I control my Samsung from the authentic Samsung automation studio nodes.
Etc etc
But they require a Samsung smart things TV
Yes it’s cloud - but I can’t fault their nodes
I use that node/thing and it works for most things.
To get the token you have to go into the TV's menu and find the option to allow network control and get a token.
I can help with more details if you want.
But it may depend on the TV model exactly where it is in the menu structure.
Yes, it is a newer TV and it is connected to smart things from Samsung. I might try it that way when I get a little time.
Just need a developer key from smart things website
As you are/were talking about the node-red-contrib-samsung-tv-contorol you navigate the TV's menu to the hdmi control (I think it is) and ask the TV for the token.
It is a number and you enter it in the config part of that node's config page.
Then all works.
There is/are problems - and I've got them - that if you don't use the nodes to control the TV for a long time, the go to sleep and the first command (usually) gets lost.
So if you are changing channels from.... say 123 to 456. The 4 gets lost.
My HACK is if it has been a long time between sending commands I send a volume up and volume down command(s) first. (that is actually TWO, but.....)
Then it seems to work better.
you just have to watch out for volume creep over a long time.
OH!
Something else - which isn't important but can catch you if you are trying to be too smart!!
BOTH devices have to be on the same LAN!