Homebridge G4S Alarm (Risco)

Control a G4S alarm panel that now lives on freecontrolweb.com / RISCO Cloud directly from HomeKit.

This fork replaces the old w-mit.g4severhome.dk API with the current RISCO Cloud web API (www.riscocloud.com/webapi/api) via risco-cloud-client. It is published under a different package name to avoid colliding with the original plugin.

Requirements

• Node.js 18+
• RISCO/FreeControl credentials: username, password, and the panel PIN you use on freecontrolweb.com.
• Optional: siteId (if your account has multiple sites) and partitionId (if you want a specific partition).

Installation

npm install -g homebridge-g4s-alarm-risco

Configuration

Add the platform to your Homebridge config:

{
  "platform": "G4S",
  "name": "G4S Alarm",
  "username": "[email protected]",
  "password": "yourPassword",
  "pin": "1234",
  "languageId": 1,           // optional, defaults to 1 (English)
  "siteId": "",              // optional, first site is used when blank
  "partitionId": "",         // optional, first partition is used when blank
  "pollInterval": 10000      // optional, ms between status polls (min 3000)
}

• Away arms fully, Stay/Night arms partially, Disarm disarms.
• Alarm state is polled periodically; a recent manual action pauses polling for ~15s to avoid flipping states.

How this differs from the original

• Package name is homebridge-g4s-alarm-risco (to avoid clashes).
• Uses RISCO Cloud (freecontrolweb.com) endpoints instead of the legacy G4S host.
• Adds PIN, siteId/partition selection, languageId, and configurable polling to the schema.

Notes & Limitations

• Uses the official RISCO Cloud web endpoints that back freecontrolweb.com; credentials are never sent to the old G4S host.
• Alarm-trigger detection depends on the partition state reported by RISCO; some panels may not expose a distinct alarm flag via the cloud API.
• Not affiliated with G4S or RISCO. Use at your own risk.