The Ophira Voice Button adds a one-tap voice shortcut to T4 touch screens and other Control4 navigators. When pressed, it tells the .Ophira service to initiate an outbound voice call to a specified intercom endpoint — allowing the homeowner to start a voice conversation with Ophira from any navigator in the home.
The button itself does not carry audio. It sends an HTTP request to the Ophira service, which then places an outbound voice call to the configured device. The audio path is handled entirely by the Ophira Voice Intercom driver and the Controller's intercom agent.
One Driver Per Room / Device (touch screen, intercom, mobile app user)
Each instance of this driver targets a single callback device. Add one driver per room or device you want to enable:
| Location | Callback Target |
|---|---|
| Kitchen | Kitchen T4 voice extension |
| Master Bedroom | Master T5 voice extension |
| Mobile (any room) | [homeowner@gmail.com] |
This ensures Ophira calls back the correct device for each room. A button in the kitchen calls the kitchen T4; a button in the primary calls the primary. For the Control4 mobile app, place the driver in whichever room makes sense for the homeowner's workflow.
Add one instance of this driver per room where you want the button. Set each instance's Callback Voice Extension to the appropriate device for that room.
Current driver version.
Enable diagnostic output in the Lua Output tab.
IP address of the machine running the .Ophira service. Must be reachable from the Controller.
HTTP port for the Ophira service API.
The voice extension that Ophira should call when the button is pressed. This is typically the extension of the T4 or intercom device in the room where you want the voice conversation to take place.
| Target | Format | Example |
|---|---|---|
| T4 Touch Screen | voice extension name = ST# | ST2539045F355F1F |
| Control4 Mobile App | voice extension name = Email@domain.com | email.domain.com |
To call the Control4 mobile app, set the Callback Voice Extension to a Control4 user account holder's email wrapped in brackets — e.g., [example@gmail.com = example.gmail.com]. The email must match the account registered to the Control4 app.
Fires when the Ophira button is tapped on a navigator. Useful for dealer programming (e.g., flash a light to confirm the press, log usage, or trigger additional automation).
/api/intercom/button_press on the Ophira service.| Symptom | Check |
|---|---|
| Nothing happens when button is pressed | Verify Ophira IP and HTTP Port are correct. Enable Debug Mode and check Lua Output. |
| Button pressed but no call | Verify the Callback Voice Extension is set and matches a valid voice endpoint registered on the Controller. |
| Call starts but no audio | This is an Ophira Voice Intercom issue, not a button issue. Check the Intercom driver's troubleshooting section. |
| Button not visible on navigator | Confirm the driver is placed in the correct room in Composer and that the navigator is assigned to that room. Refresh navigators. |
| Debug shows "Ophira call failed" | Check that the Ophira service is running and the HTTP port is not blocked by firewall. |