Risco local binding [4.1.0;6.0.0)

Hi @Sim,

yes it is possible.
For Zones you can Bypass and Un-Bypass.
For Partitions you can Arm, Home Stay and Disarm.

For example, on the below screenshot from my phone, you can see the Bypass Toggle on the UI.

It is also possible to execute the actions from a rule.
Unfortunately i cannot give more information right now. Summer … Vacation time.

My plan is to wrap up the documentation and submit a PR for the binding sometime start of October.

1 Like

Hi Joshua,

Very nice job! I have been using the binding for around six months. It is very reliable. My only issue is that I cannot arm/disarm the partition, but I can omit zones.

thing:
Bridge risco:bridge:lightsys “Risco Alarm Panel” [
hostname=“x.x.x.x”,
password= “5678”,
id=1,
encoding= “UTF-8”,
port=1000,
connectionDelay=10000] {
/Panel/
//Thing system panel “Main Panel”
/Partition/
Thing partition p1 “Partition 1 Main House” [partitionNumber=1]
}

item:
/Partition/
Switch p1Alarm “Main House Alarm” (Partition) {channel=“risco:partition:lightsys:p1:alarm”}
//Switch p1Duress (Partition) {channel=“risco:partition:lightsys:p1:duress”}
//Switch p1FalseCode (Partition) {channel=“risco:partition:lightsys:p1:false-code”}
Switch p1Fire “Main House Fire” (Partition) {channel=“risco:partition:lightsys:p1:fire”}
Switch p1Arm “Main House Armed/Disarmed” (Partition) {channel=“risco:partition:lightsys:p1:arm”}

Hello @Theofylaktos_Pieri, @Sim, @stamate_viorel,

i had a look at the code in github.
One of the last things i did add to the binding was the definition of an user index in the partition configuration. The binding retrieves the pin of this user index and checks it against the passed pin on the arm, disarm, and stay actions.
That’s the reason why the arm/disarm is not working from the UI.
These channels will be marked as readonly in the next binding revision.

1 Like

Hi, Has anyone managed to get this to work with OH5. I have just installed and cannot get it to connect.
COMMUNICATION_ERROR
Communication cannot be initialized. java.net.ConnectException: Connection refused

Hello Lawrence,

I will install a test environment and check during next week.

What exactly OH version do you have installed?

Hi Georgios
Many thanks;

installed OH version is 5.02.
Installed Risco local is 4.1.0;6.0.0 from the marketplace
I also tried the 4.2 version of Risco local installed manually via the addons directory; it loaded correctly but it did not show up as an available binding in UI / Things / Add Thing

Hello Lawrence,

i upgraded my current OH4 installation, to the latest [5.0.3].

After a binding reinstall, the binding worked as expected.

I did not do it from scratch yet. Need to find a spare RPi for that.

Hi Thanks for confirming.. I have tried removing and reinstalling binding but still same error. I have also tried to turn on debug but so far have not got any useful information.
Can you confirm the “Risco Panel communication password” is the same as the panel PIN (Have tried this and also the binding default)

Hello Lawrence,

It is the panel access code. The default is 5678. (Could have been changed by the installer)

It is not the same as the pin you use to arm and disarm.

What panel do you have? Can you also send me the debug log?

Hi Georgios
Apologies I figured out the problem. I have a home assistant installation running along side OH and had configured the HA binding to use the local alarm device. The panel does not allow 2 connections simultaneously on port 1000. Many thanks for your help and apologies for wasting your time on my error.