Sky moved its set-top boxes onto IP and left the control integrations behind. Most Control4 projects still drive a Sky Stream with infrared — a flasher taped to a box, no feedback about what the box is actually doing, and a remote that works until somebody moves the furniture.
This driver speaks Sky’s own protocol over the network. It discovers the box on the LAN, pairs with it, and holds an authenticated session open, so commands are acknowledged rather than fired into the air. It wakes a sleeping box rather than needing one left on.
Because the session is real, the driver knows the box’s state. Control4 gets a device that reports back, not a one-way blaster.
| Protocol | Sky RICS over WebSocket, mutual TLS on port 8091 |
|---|---|
| Discovery | mDNS on the local network |
| Power | Wake-on-LAN, with pair / bind / keyatomic session handling |
| Proxy | Two variants from one Lua core — satellite, and media player |
| Hardware | Sky Stream and Sky Glass |
| Transport | IP only. No infrared, no serial, no flasher |
| Platform | Control4 DriverWorks |
The box and the controller on the same network segment, and the box reachable by mDNS.
Nothing else: no additional hardware, no cloud account, no port forwarding, and no account credentials held by the controller.
One licence per Control4 project, held against the project’s controller — not per set-top box. A project driving four Sky Streams takes the same single licence as a project driving one.
The driver is delivered as a .c4z.