LG WebOS TV added Actuator capability

Added code following as line 57 to LG WebOS TV.groovy:
capability "Actuator"
This allows the RM to set driver action command parameters using:
Set Variable, Mode or File, Run Custom Action/Run Custom Action/Actuator

There’s more than one custom driver for LG TVs, I think.

It would help if you posted this is a thread for one of those drivers.

I which I understood what you mean...
Does each driver have its own community thread?
If so, how are the threads located?
Is there a community road map?

It’s sort of up to the dev that made the code. There’s no hard and fast rules, although there are forum categories to try to keep things somewhat organized.

Let’s start with, where did you find the driver code that you edited? Shouldn’t be difficult to determine which dev wrote it, and from there, whether the dev has an active thread here in the community.

Not really. There are a couple threads that are kept as wiki posts so that anyone can edit them. But they’re only as accurate/up to date as users like you and me want to maintain them. There’s one for device drivers and one for apps.

There is only one driver called: "LG WebOS TV" "v0.3.0" provided by "Andrew Stanley-Jones".
I had difficulty setting the driver parameters in RM for that driver because it did not have: "capability "Actuator"
So added that on line 57.| Then in My "Front motion" rule, I used:


Maybe there is another way to accomplish the task, however this method seemed more consistent to me. I thought I should let others know what I did.
I do not know the best method to contact the script author.

:point_up:

I see. There are a few similar drivers floating around out there. @asj wrote the version you're referencing, but I don't know how active he still is here.

Why not just use the notification capability the driver already has? No need to run a custom action for that.

But in general, if you want to use a custom action in rule machine, you can first select any available capability the device supports, which will then allow you to select it and expose all its custom commands. In the case of this driver, "switch" would work just the same as actuator.

I'm not a developer so it's possible I've misunderstood something. But I'm not sure adding the actuator capability accomplishes anything the driver can't already do. @syepes has a similar driver and could probably explain if I've misunderstood something, since he's actually a developer.

Download the Hubitat app