LGTV Youtube Node Usage (broken?)

Hi, I want to start a Youtube video on my TV so I tried the Youtube node and sent a URL as the payload. As a result, I get the video played but it looks like this:

[{"id":"058086768f40d082","type":"tab","label":"Scene: Cozy Ambient","disabled":false,"info":"","env":[]},{"id":"a52dcf69c3feb8fa","type":"change","z":"058086768f40d082","name":"Fireplace","rules":[{"t":"set","p":"payload","pt":"msg","to":"https://www.youtube.com/watch?v=RbAJEhylvn4","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":340,"y":240,"wires":[["8e2b1c3c48580be9"]]},{"id":"8e2b1c3c48580be9","type":"lgtv-youtube","z":"058086768f40d082","tv":"262df58758352518","name":"","x":480,"y":240,"wires":[]},{"id":"3746f3a0fbb8b090","type":"inject","z":"058086768f40d082","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payloadType":"str","x":210,"y":240,"wires":[["a52dcf69c3feb8fa"]]},{"id":"262df58758352518","type":"lgtv-config","host":""}]

The only way to get the Youtube App back to normal is to uninstall it from the TV and reinstall it again.

I thought maybe passing the full URL is wrong and it expects just the ID (RbAJEhylvn4 in this case) but with that the TV just does nothing.

What's the correct way of using this node?

Contrib node in question: node-red-contrib-lgtv

It would help if you specitide what the contrib node is:: node-red-contrib-?????

Oh sorry. That would be node-red-contrib-lgtv

I’d go open an issue on the nodes GitHub page, `but the node hasn’t been updated in over 3 years so it might be abandoned.

In looking thru some of the different lgtv nodes someone said that YouTube changed it’s API and that might be the issue.

You could fork the node and see if you could fix it yourself. :smiley:

Good point. I found the problem in the code and have a fix. But creating a PR is probably useless. Look at the date of the last commit ... What do you suggest how to proceed in such a case? I guess I could put in some hours to maintain the repo but having a single maintainer isn't great for node red in general.

Probably worth a try. The author used to be quite active/responsive (back in the day)


1 Like

As we feared: Nothing is happening.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.