Control4 Driver - Siri TCP
INTEGRATE SIRI WITH CONTROL4
The Chowmain Generic TCP Command driver for Control4 provides integrators the ability to expand IP control within Control4 without requiring them to develop drivers with driverworks. This is done by providing access to send TCP / UDP / HTTP commands to 3rd party devices or services via the programming tab. It also allows Control4 to receive HTTP commands allowing for 3rd party control of Control4. This can be used by cameras providing motion detection, line trips and other alarms and can even be utilised by iPhones to provide shortcut control or Siri based control.
FEATURES
- HTTP commands
-
Supports URL encoded usernames, passwords and ports eg http://192.168.1.131:32400/library
-
Support for HTTP GET and HTTP Post
-
-
HTTP events
-
Control Control4 with an infinite number of web events. Integrate camera motion detection, camera line crossing, iPhone shortcuts, iPhone Siri and more.
-
-
TCP commands
-
Definable IP Address, Port and Command
-
Command can contain special character delimiters such as carriage returns or line feeds (eg \r\n).
-
-
Wake-On LAN command
-
Can be used to wake up a sleeping or powered off device that supports wake on lan (eg computers or NAS drives).
-
-
Can be used to quickly integrate devices not normally integrated within Control4’s driver wizard by adding tcp commands to their events page.
FAQ
Can you give us some examples of how we could use this driver?
This driver is useful to fire commands to shut down NAS drives, fire off camera triggers, fire off commands to your PC using event ghost.
It is also useful for controlling Control4 via HTTP commands limited to the programming the programmer does. Excellent for firing macros from 3rd party systems (EG IP cameras firing commands to Control4)
Are there any other cool things we can do with this driver?
- Clients with iPhones can now use Siri to control Control4 or utilise shortcuts via the widgets view to fire quick commands.
- You can also create quick simple IP based AV devices by firing off commands on the AV event. Though this is not substitution for a real IP driver it allows non driverworks developers to create simple drivers for their jobs where they cannot afford to hire a driverworks developer.
