This is a server (NodeJS) that connect to Risco Cloud Alarm Security System. Integration works only when proper Ethernet module is added to your Risco Unit and you are able to arm & disarm your system via https://www.riscocloud.com/ELAS/WebUI.

The purpose of this service was to separate Risco API endpoints from Homebridge. During my tests Homebridge was quite unresponsive and prone to strange behaviours / delays. If you're already have a hardware where you run Homebridge, you can also install separate service for Risco Alarm, that handle all logic inside and expose only http endpoint where from Homebridge / any other platform you can read / arm / disarm your Risco. Polling is enabled by default.

Service by default saves last known status (if changed) into file. That way even if service is restarted - last status from file is read.

• GET /alarm/check - get Risco Status (3 - disarmed, 1 - armed)
• GET /alarm/arm/:state - set :state to away to arm your Risco, set to any other to disarm.
• GET /alarm/bypass/:id/state - set sensor with provided id to be omitted during next arm cycle
• GET /alarm/bypass/:id - get bypass value for requested sensor

For this we should create new service in /lib/systemd/system/ Instructions can be found here: https://www.paulaikman.co.uk/nodejs-services-raspberrypi/

sudo systemctl start|stop|restart risco.service sudo systemctl restart risco.service

Before you run this service, make sure you update config.json file.

  "RISCO_USER":   Risco User, usually your email address
  "RISCO_PASS":   Your Password to Risco system
  "RISCO_PIN":    Your PIN
  "RISCO_SITEID": Your Risco SiteID

To get your riscoSiteId, login to riscocloud via ChromeBrowser (first login screen), and before providing your PIN (second login page), display source of the page and find string: <div class="site-name" ... it will look like:

<div class="site-name" id="site_12345_div"></div>

In that case "12345" is your siteId which should be placed in new config file.

Docker compose could be used, a docker-compose.yml for development is included. The service can also be installed from Docker Hub, see examples below.

For example, docker compose for local development (docker build not needed):

docker compose up

For example, manual building and running:

docker build -t risco-service .
docker run --init --name my-risco-service -p 8889:8889 -v $(pwd)/config.json:/home/node/code/config.json risco-service

For example, installing from Docker Hub (make sure to set up config.json first):

docker run -d --restart unless-stopped --name my-risco-service -p 8889:8889 -v $(pwd)/config.json:/home/node/code/config.json mdworld/risco-service

Based on: https://gabor.heja.hu/blog/2020/01/16/domoticz-http-https-poller-and-json/

• Setup > Hardware > Add a device:
  • name Risco Cloud
  • type HTTP/HTTPS poller
  • method GET
  • ContentType: application/json
  • URL: http://localhost:8889/alarm/check
  • Command: risco_cloud.lua
  • Refresh: 60 This is in seconds, do not set to lower than 12 seconds
• Setup > Hardware > Risco Cloud > Create Virtual Sensors
  • Name Risco State
  • Sensor Type: Selector Switch
• Setup > Devices > Search Risco State should show it, copy the Idx, e.g. 2053
• Switches > Find Risco State and edit it.
  • Rename selector levels:
    • 0 disconnected
    • 10 disarmed
    • 20 partarmed
    • 30 armed
    • 40 ALARM
  • Set Protected to true
  • Change "Switch Icon" to Generic On/Off switch
• On the filesystem, in the Domoticz dir create config/scripts/lua_parsers/risco_cloud.lua with:

local idx = 2053
local alarm_status = request['content']

-- 0 -  Characteristic.SecuritySystemTargetState.STAY_ARM:
-- 1 -  Characteristic.SecuritySystemTargetState.AWAY_ARM:
-- 2 -  Characteristic.SecuritySystemTargetState.NIGHT_ARM:
-- 3 -  Characteristic.SecuritySystemTargetState.DISARM:
-- 4 -  OngoingAlarm

if (alarm_status == "0")
then
  print ("0=stay_arm, setting to 30")
  domoticz_updateDevice(idx, '' , 30)
elseif (alarm_status == "1")
then
  print ("1=away_arm, setting to 30")
  domoticz_updateDevice(idx, '' , 30)
elseif (alarm_status == "2")
then
  print ("2=night_arm, setting to 20")
  domoticz_updateDevice(idx, '' , 20)
elseif (alarm_status == "3")
then
  print ("3=disarm, setting to 10")
  domoticz_updateDevice(idx, '' , 10)
elseif (alarm_status == "4")
then
  print ("4=ongoing_alarm, setting to 40")
  domoticz_updateDevice(idx, '' , 40)
else
  print ("invalid state, setting to 0, state was:", alarm_status)
  domoticz_updateDevice(idx, '' , 0)
end

I use this service with Http-SecuritySystem npm package dedicated for Homebridge https://www.npmjs.com/package/homebridge-http-securitysystem

My config for this plugin:

  "accessory": "Http-SecuritySystem",
  "name": "Home security",
  "debug": false,
  "username": "",
  "password": "",
  "immediately": false,
  "polling": true,
  "pollInterval": 10000,
  "http_method": "GET",
  "urls": {
      "stay": {
          "url": "http://localhost:8889/alarm/arm/stay",
          "body": "stay"
      },
      "away": {
          "url": "http://localhost:8889/alarm/arm/away",
          "body": "away"
      },
      "night": {
          "url": "http://localhost:8889/alarm/arm/night",
          "body": "night"
      },
      "disarm": {
          "url": "http://localhost:8889/alarm/arm/disarm",
          "body": ""
      },
      "readCurrentState": {
          "url": "http://localhost:8889/alarm/check",
          "body": ""
      },
      "readTargetState": {
          "url": "http://localhost:8889/alarm/check",
          "body": ""
      }
  }

If you like it, any BTC donation will be great. My BTC Wallet: 3Ma1KEEfvNbvfAEyvRvmGHxNs61qZE7Jew