DirectorLink · PIMA FORCE for Control4
A free, open-source Control4 driver for PIMA FORCE alarm panels (FORCE, FORCE 32C, FORCE 16). The panel connects to the driver on the controller the way it connects to a monitoring station, with PIMA's local JSON interface: arm and disarm from Control4, alarms, troubles, zones with their names, bypass and outputs. It works on your local network: no cloud, no extra hardware and no subscription.
Free. No subscription, no license key, no account with us.
Made by DirectorLink, the open-source management layer for Control4 homes. Works on its own: DirectorLink is not required.
Field reports wanted. Tested on a FORCE 32C with firmware 1.5.1, in receive-only mode: arming Away and disarming showed in the partition each time. The JSON interface (arming and disarming from Control4, zones, bypass) follows PIMA's specification and passes its tests against a simulated panel, but no panel with JSON firmware has reported on it yet. If yours has it, please send a report.
What you get
| Feature | With the JSON interface | Receive only (no JSON in the firmware) |
|---|---|---|
| The alarm's state | Armed Away, Home, Night or Shabbat, disarmed, the exit delay | Armed and disarmed, from the panel's reports |
| Arm and disarm from Control4 | Away is Full arm, Home is Home 1, Night is Home 2, Shabbat is PIMA's Shabbat arming. Disarming needs a typed code, which the panel checks | No |
| Alarms | Burglary, fire, gas, water, panic, medical and duress | The same |
| Troubles | AC loss, low battery, tamper, communication, from the panel's fault list | The same, from the panel's reports |
| Zones | Open and closed, live, with the names in the panel (Hebrew too); kept from Control4 while armed for Shabbat | Open and closed when the panel reports them; names set in Composer |
| Bypass and outputs | Bypass a zone; outputs 1 to 8 on and off | No |
| Programming | Communication Lost and Restored, Siren Active and Inactive, Access Denied, and the partitions' own events | The same |
In Composer the driver adds a Security Panel and four partitions, Control4's standard security devices, so every Control4 app shows the alarm. Each zone also has a Zone contact connection: bind a Control4 contact driver, such as Door Contact or Motion Sensor, to use the zone in rooms and programming. PIMA's interface has no command to raise a panic, fire or medical alarm, so the driver offers no such buttons.
Panel firmware
The JSON interface is a special FORCE firmware that PIMA provides (tested: 3.0.19 on a FORCE 32C). To check, press and hold 0 on the keypad: FW is the version, and a firmware with JSON names the system HAC Force (32 zones) or HA1 Force (144 zones). Without it, ask PIMA support or your installer for the JSON (smart home) firmware.
Older firmware, like 1.5.1, works in receive-only mode. The panel sends its normal monitoring reports (SIA DC-09, with Contact-ID or SIA codes and encryption off), and the driver shows arming, disarming, alarms, troubles and zones in Control4. It can't arm, disarm, bypass or read zone names, and the partition's state is unknown until the panel's first arm or disarm report. When JSON firmware arrives, set the CMS path to JSON: the driver switches to full control by itself.
What it needs
- A Control4 controller on OS 3.0 or newer, with a fixed IP address, and Composer Pro.
- A PIMA FORCE panel on the home network, with a free monitoring station path: CMS 1, 2 or 3, never one a monitoring company uses.
- For full control, panel firmware with the JSON interface. Older firmware works receive only.
- The panel reaching the controller on the driver's Listen Port, 7780 by default. The panel dials out: it opens no port of its own.
Setup in three steps
-
Point the panel at the controller
As PIMA's JSON guide gives it, with the installer code: System Programming → CMS & Communication → Monitoring Stations → CMS 1 (2 or 3 if a monitoring company uses 1). In Event Reporting, mark Zone/Output Change. Under Comm. Paths → Network (Ethernet): any account number, the controller's IP address and port 7780, then Protocol JSON with Disable Encryption marked and the life signal on. Back in CMS & Communication → General Settings, mark Remote Disarm.
-
Add the driver
In Composer Pro, add DirectorLink · PIMA FORCE to a room. Leave Account ID empty: the driver learns it from the panel's first report. Enter the master or Smart Home code in Panel User Code (not the installer code). From driver 1.2.4 there is no address to type: Panel IP Address shows the address the panel calls from, and the driver follows the panel if the router gives it a new one, refusing any other address while the panel is connected. A DHCP reservation for the panel keeps its address fixed.
-
Choose the partitions
Set Partitions In Use and each partition's zones, for example
1-8,12orall. Connection Status ends at Connected to the panel's address, or Receive only (SIA DC-09). Zones and their names load by themselves.
The panel may take a few minutes to dial. What each Connection Status means, and every property,
are on the driver's Documentation tab in Composer and in the
full guide. Composer lists the driver as
DirectorLink · PIMA FORCE; the file is DirectorLink-PIMA-Force.c4z.
With DirectorLink
The partitions are Control4's standard ones, so DirectorLink, with its Alarm Status property on, shows each partition's state on Home in the app, and the home's TVs with the LG TV or Android TV Notifications driver say when the alarm goes off.
From DirectorLink 1.15.0, with its Alarm Control property on too, admins and the members they allow can arm and disarm from the DirectorLink app. They type their alarm code each time: it goes to the panel as typed, the panel checks it, and DirectorLink never keeps it. The driver tells DirectorLink when arming and disarming can work: while the JSON interface is connected, not in receive-only mode or without the panel.
Driver 1.2.0 and 1.2.1 sealed each command from DirectorLink 1.16.0 to the driver, so that Control4's own debug log never saw the code. On a controller, opening it took about 14 seconds, so 1.2.2 takes the typed code again, as 1.1.0 did: like any command between Control4 drivers, it then passes through Control4's debug log, which only the controller's root user can read and which is gone within a few hours.
Shabbat
PIMA sells the FORCE in Israel as a Shabbat and holiday system, approved by the Zomet Institute. On such a panel the driver offers Shabbat next to Away, Home and Night. While a partition is armed for Shabbat, its zones opening and closing are not passed to Control4, so people moving in the house cause nothing in its programming; an alarm is still reported, and the zones are reported again once Shabbat arming ends.
Ideas for programming
-
Lights when the siren sounds
On Siren Active, turn on the lights inside and outside the house.
-
The panel went quiet
On Communication Lost, send a push notification, so a cut cable or a panel off the network does not go unnoticed.
-
A wrong code
On Access Denied, send a notification: the panel reported an invalid code, or a code used outside its allowed time.
Privacy and support
- The driver talks only to the panel on your home network. It sends nothing to DirectorLink or to PIMA's cloud and collects no usage data. Codes stay in your Control4 project, and no log line, status or report ever shows one.
- An alarm system protects people and property: test arming, disarming and alarms after installing, and keep the panel's own keypad and monitoring as they are.
- Keep the exact file name: a browser's
… (1).c4zcopy installs as a separate driver instead of updating. An update keeps the settings, connections and programming. The earlierPimaForce.c4ztest builds are a different driver for Composer: remove it, add DirectorLink · PIMA FORCE and set its properties again. - Community-supported, best effort. Report a problem with the panel model and firmware, your Control4 OS version, the Driver Version, Connection Status and Panel Info properties, and the log with Debug Mode on. Reports that a panel works are welcome too.