Roku TV (IP) Control4 Driver
Log-In or Register to view pricing.
This driver enables you to get complete control of a Roku based TV from many of the popular brands like TCL, Hisense, Insignia, Sharp and more all over ethernet or wifi. If the TV runs the Roku operating system there is a 99% chance this driver will control the tv.
- Discrete Power Control
- Volume Control
- Discrete Input Selection
- Supports Control4 Universal Mini Apps
Easily have your favorite Roku channels displayed on navigators. No more custom programming, custom buttons or button mapping. Just add the desired channel to the project and let the driver do the rest.
HTI Customs is a registered and authorized Roku App Developer. This driver uses public API commands available directly from Roku
- Auto discovery of your Roku device!
- Easily have your favorite Roku channels displayed on navigators. No more custom programming, custom buttons or button mapping. Just add the desired channel to the project and let the driver do the rest.
- Driver Variables
- Current channel
- channel id
- mac address
- model
- model number
- ip address
- Roku name
- serial number
- software build
- software version
- UUID drag and drop identification
- Volume control
- Input selection
- Power Control
When deploying a brand new Roku to a project you must ensure that the Roku has been COMPLETELY set up and linked to Roku account before moving forward with this driver.
IMPORTANT: On the TV go to Settings – Power – Fast Start and enable that service. If you do not enable this setting you will not have proper control of the tvs power functions.
Roku’s will not be discovered until this is done!
Step 1: Install Roku TV Driver.
Step 2: Put in your BlackWire License Key
Step 3: Go to Connections – Network and then drag the RokuTV UUID from the right column of composer to the TV driver line. This will ensure if the device changes IP address the driver will continue to be able to control it.
On the Available Devices column look for urn:roku-com
IMPORTANT: Composer 3.1.1 has broken the ability to ID the tv via UUID. Please enter the IP address and ensure you have a DHCP reservation in your router.
Download Link
Release Notes
Removed- “Discovered Rokus” property. Fixed- RokuTV not turning on when selecting RokuTV as first source from room off state
Version 2.0.8 - (August 12, 2019)Removed- Volume slider in navigator. Changed- XML to remove auto-connect on IP
Version 2.0.7 - (June 11, 2019)Fixed- Issues when driver will fail to initialize after a Director reboot.
Version 2.0.6 - (May 29, 2019)Fixed- Minor bugs
Version 2.0.4 - (May 01, 2019)Fixed compatibility issues with C4OS 2.10.0 and below
Version 2.0.3 - (April 25, 2019)Reverted back to old licensing code
Version 2.0.2 - (April 23, 2019)Fixed- Problem licensing with C4OS 2.9.1 and below
Version 2.0.0 - (February 28, 2019)Added- Pixie Dust!
Version 1.9.9 - (February 25, 2019)Added- Update to documentation to state that audio is not 2 way, so navigator will not display volume percentage Added- Function to “Actions” drop down. Print HTI Customs Debug Added- Full app tracking. If an app selected outside of Control4 environment AND the mini driver is installed and bound to the RokuTV the driver will select the mini app for proper navigator tracking *Auto Room On feature must be used. **This feature does not work with HTI Customs mini apps due to the construct of the drivers. If you wish to use this feature you must use Control4 Universal Mini Apps
Version 1.9.8 - (February 21, 2019)Fixed- Carry over bug with HTICustoms mini apps not launching but Control4 mini apps do Fixed- Auto Room On function Added- Analog audio binding for component
Version 1.9.7 - (February 19, 2019) Version 1.9.6 - (February 06, 2019)Added- Tuners for OTA programming
Version 1.9.4 - (January 29, 2019)Added- Brand new Roku TV driver using TV Proxy using existing our existing base code for our Roku driver. Added- Control4 Universal Mini App support. Fixed- Licensing issue if internet connectivity has not been established when director initializes.
HTI Customs started making drivers in 2014 when we needed niche drivers for the projects we were working on. We built in the features we needed and thought what other integrators would want and need. Today we keep that same mindset with every driver we develop. We keep the integrator in mind. Because hey at the end of the day we are installers too.