Risco Lightsys Alarm component

Feature Requests
21

Step 1/12 : FROM node:8-alpine

—> 516f4a377940

Step 2/12 : ARG TZ=Europe/Rome

—> Running in 590ddf464fa9

Removing intermediate container 590ddf464fa9

—> 4e3ef1ff894d

Step 3/12 : RUN apk --no-cache update && apk --no-cache upgrade && apk --update add tzdata && cp /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone && apk del tzdata

—> Running in 3674d7bbecfe

fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/main/armhf/APKINDEX.tar.gz

fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/community/armhf/APKINDEX.tar.gz

v3.8.4-32-gafcf91b319 [http://dl-cdn.alpinelinux.org/alpine/v3.8/main]
v3.8.4-23-g3c27aa9aec [http://dl-cdn.alpinelinux.org/alpine/v3.8/community]
OK: 9325 distinct packages available

fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/main/armhf/APKINDEX.tar.gz

fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/community/armhf/APKINDEX.tar.gz

OK: 5 MiB in 15 packages

fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/main/armhf/APKINDEX.tar.gz

fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/community/armhf/APKINDEX.tar.gz

(1/1) Installing tzdata (2018f-r0)

Executing busybox-1.28.4-r3.trigger

OK: 8 MiB in 16 packages

(1/1) Purging tzdata (2018f-r0)

Executing busybox-1.28.4-r3.trigger

OK: 5 MiB in 15 packages

Removing intermediate container 3674d7bbecfe

—> 696a074884da

Step 4/12 : RUN mkdir -p /app/node_modules && chown -R node:node /app

—> Running in 4e69f128f304

Removing intermediate container 4e69f128f304

—> 9bfc0ac29a1d

Step 5/12 : WORKDIR /app

—> Running in bfb19c2fde36

Removing intermediate container bfb19c2fde36

—> 02fe84e2c8c4

Step 6/12 : COPY package*.json ./

COPY failed: no source files were specified

22

someone could do a guide for run this on hass.io i could pay for it.

23

I can make some screenshots later

24

Please, if you can…

25

Do you already have mqtt running?

26

Yes, and the panel control Mqtt created with topics like say the creator

  • platform: mqtt
    state_topic: “riscopanel/armstatus”
    command_topic: “riscopanel/armstatus/SET”
    payload_disarm: “disarmed”
    payload_arm_home: “partially”
    payload_arm_away: “armed”
27

Ok, so you have a working mqtt server… So you only need the screenshots of the docker config from Risco

28

yes i have it running,im not sure what i need,im on hassio and portainer installed,that only
sorry

29

ok, first of all, download this file : https://github.com/lucacalcaterra/risco-mqtt-bridge/blob/master/config/config-example.js

place it somewhere in your config directory, rename to config.js

change according to this readme in your config.js : https://github.com/lucacalcaterra/risco-mqtt-bridge/blob/master/README.md#configuration

  • the risco section (user/pass/code/siteid)
  • the mqtt section (your mqtt server)
  • the home assistant part

then go to portainer, download the image : lucacalcaterra/risco-mqtt-bridge

make a new container in portainer, the most important is that you need to mount the config.js to that container offcourse

see screenshot here :

so path in container = /app/config/config.js , dont change it
so host volume = /mnt/data/supervisor/homeassistant/risco-mqtt-bridge/config.js (change this)

/mnt/data/supervisor/homeassistant/ => this is actually the /config dir from the hassio container
so if you placed the config.js file directly in /config dir ; change it to : /mnt/data/supervisor/homeassistant/config.js

i just placed my config.js file in a directory called “risco-mqtt-bridge” inside /config

then start the container , look in the log/terminal if you dont see any errors there about

  • connecting to risco , connecting to mqtt , getting the state …

see screen here : https://www.dropbox.com/s/xq34bilhrlv6hf3/ha-risco2.JPG?dl=0

to see debug logging, see my first sreenshot , in container details, make a new environment :

NODE_ENV => development
if all is OK , change “development” afterwards to “production”

done

30

which is config directory?hassio config dir?

31

yes /config

32

how download the image : lucacalcaterra/risco-mqtt-bridge?
import image…risco-mqtt-bridge-master .zip?
i cant download the image : lucacalcaterra/risco-mqtt-bridge,i dont know how
im trying to import,build new image,url to a file and cant
im so silly,i know…please help
portainer tell me upload succesfull but i dont see the image

33

No…

In portainer, just use the search tool, and type in the image name, it will find it automatically

34

This is great thanks Fabio. I’ve gotten to the point of deploying the container but I’m getting an error while creating mount source path ‘/config/risc-mqtt-bridge/config.js’ : mkdir /config: read-only file system.

I’m running hassio on a raspberry pi. What do you suggest I do now. Do I need to edit the file permissions manually?

35

That config.js should be already an excisting file on your PI, that’s your configuration file, you just need to point to that file from your container

36

Yes I already have the config.js created and it’s in the risco-mqtt-bridge folder. Am I creating the container the right way then, with the volume mapping at the bottom? or do I create it without volume mapping and somehow create those afterwards?

Capture
Capture1638×922 93.6 KB

37

stupid me, I didn’t realise I had to use the same path you had in your example. Once I used that when creating the container it worked. Now to figure out what I need to do to setup a card on the home screen.

38

Ok good :wink:

Yeah, just add a mqtt alarm, like in readme

39

I finally got it started, thanks a lot to pergola.fabio for the inconvenience and patience, thanks to luca for creating this

40

Yeh, I’ve got a lot to learn. Don’t really know anything about MQTT or Portainer, so it’s all a bit confusing for me right now, but at least the instructions were clear enough to follow, that it didn’t even matter.

I have found, interestingly yesterday after having disarmed my alarm from within HA, the entity in HA didn’t show it as disarmed. I had to manually set the state. I can only assume HA wasn’t able to poll Risco Cloud and get the disarmed state. @pergola.fabio, how do I confirm where it fell apart? Is there a specific log I can check?