Interest in Edge Driver for Roku devices?

This is that API documentation that I assume @TAustin is referring:

I used that documentation to achieve most of the requests mentioned using a dashboard on a competing hub. Pushing buttons on dashboard simply sends the HTTP request. If using a Roku device plugged into a TV, I don’t think you can use the API to turn on/off the TV. It can only turn on/off Roku TVs.

1 Like

Some TVs will turn on if Roku turns on, depending on Roku > TV connection
I have Roku sticks, Roku Ultra devices and RokuTVs.
With one of previous Groovy integrations I was able to set automation to turn on Roku and to select channel.

@TAustin what design control elements can you use for Roku device details?

Just in the exploring stage, but I’m thinking tV, mediaPlayback, mediaPresets. Other things may need to be accomplished with custom capabilities.

Yea, I’m a little confused by the on/off needs. I only have Roku sticks, and one of them doesn’t even have a power button on the remote. It’s on all the time. The other one does have a power button and it turns the stick on and off, but also somehow seems to turn the TV on and off, even though I don’t remember ever programming it in any way to control my TV. Is it doing this through its HDMI connection??

Then there are what people are referring to as Roku TVs: I assume these are any brand TV that has Roku embedded in their features. So I can see where if you send a power off command then it could turn off the TV itself.

Curiously, in Roku’s API documentation they only show a PowerOff command available for Roku TV; no PowerOn. And for their ‘keypress’ command options available for all Roku devices, there is no power-related key. However I was experimenting sending my stick keypress commands and I sent it ‘power’ (even though it’s not documented) and it seems to power on and off as if I pressed it on the remote. I haven’t tried on the older stick that doesn’t have a power button, but I’m betting it will probably be ignored.

Yes, it seems pretty straightforward. See my comments above regarding on/off.

Anyone can control their Roku locally through SmartThings today using my Edge driver to send POST/GET web requests. You can save up to 50 url strings and trigger them through automations.

I think the purpose of creating a dedicated Roku device driver would be to formalize it into one standard device using (mostly) standard capabilities.

The reason I am interested in a Roku driver is that with the current Roku Smartapp I can use the remote to control the TV and it syncs with the Roku device in the app. I can then use the ST devices in automations/scenes to turn TV on or off.
For instance when bedtime automation or away away automations run, if TV is On they turn off.

If I understand from another conversation, using web requester will not GET the device status however you can POST power command which does turn TV on/off. I have not tried this yet so correct me if I’m wrong but if I send POST power command and the TV is off then wouldn’t it turn on?

I know there are other ways to control Roku TVs/settings using Alexa and Harmony hub but they don’t stay in sync when the remotes. ST or dashboard only use isn’t realistic when family/friends are visiting.

I am completely open to any other suggestions. And as mentioned, the current DTH does not work with my older streaming stick on a dumb TV.

@TAustin I took liberty to come up with some proposed layout, however any suggestions are welcome


Most of Roku devices can turn TV on through HDMI, but that one also depends on the TV
RokuTV is like @Terri_Baker described, and I was able to turn it on/off with automations

1 Like

I can only try this on a Roku stick, and for that, since the stick itself is turned off, it’s never sees the power on request via the LAN. I think this is why there is only a PowerOff command in the API.

And yes, GET requests from web requestor do not yet do anything with returned data, although I’m looking at this now.

Hey @TAustin I am very interested in this also.

I have 4 of the Roku 4k sticks and would like to see the following features:

  • On/Off as this switches the TV on/off also
  • Volume controls for when th kids have their TVs to loud and I am too lazy to get up and tell them
  • media controls play/pause/skip etc…

Plus if this is even possible YouTube/Netflix shortcuts…

Edit: that layout suggested by @milandjurovic71 would be perfect

May want to hold off on YouTube as google may pull it off roku in early November. But still too early to say as they are still in talks but they have been fighting over terms since spring.

Wow! This is fantastic

1 Like

This are some old screenshots from Classic app. It might help with what was available before



Just to set everyone’s expectations, we all need to remember that the proposal was just for an Edge device, not a SmartApp. :grin:

3 Likes

People are getting a little excited :rofl: and not too many p’s and q’s I see!

This is always an issue with IR commands, I use a smart plug on the tv for power. Or you can poll the tv with a device like a nodemcu and the Host Pinger smart app for certainty.

1 Like

Absolutely. TCL, Premeire and Stick would all be great. On/Off, volume and app selection would be the goal. The “Netflix and Chill” scene would finally be complete :slight_smile:

@jkp good point! I had forgotten about that.

I was incorrect. I ​just tried the following commands in Web Requestor and all work as expceted
keypress/power - turns TV on/off
keypress/powerOff - only turns off
keypress/powerOn - only turns on

1 Like

OK everybody, you’ve convinced me there’s enough interest. Keep the comments coming on highest priority controls; meanwhile I’ll get started on the driver. I’ll try to have a first pass for you all to look at by sometime next week.

6 Likes

Very cool! Thanks for confirming.