Alarm system 'wiki'

[heggink]

So you're doing similar things that I (am trying to) do. 2 comments: 1) I found that trying to make things too complex introduces states that I did not think of and messes up my scripts. Say someone forgets his phone at home (my daughter or wife) then that may prevent my alarm from arming altogether. 2) I never test the zipato keypad. It's just a device that arms/disarms like many others (one being my nuki door lock: open it and the alarm is shut off). I test the TAO switch and/or the domoticz alarm state. TAO 1:1 triggers domoticz alarm state (difference is the configurable time before alarm is armed). Makes sense?

Verstuurd vanaf mijn HUAWEI NXT-L29 met Tapatalk

[tyfoon]

My objective was just that, to keep it as simple as possible.. In my case I actually mean; I want to avoid that my family needs to do anything when it comes to the alarms.

Up till now I actually have very little wrong alarms. The combinations of the phones (presence via router & owntracks for all phones) + no motion in the house (I have 7 motion sensors) for 20 min + Nest presence detection >>> I'm sure nobody is home and alarm can be armed. I also get a notification when the alarm gets armed (which only happens when all above true). So also less concerned when alarm would not be armed.

Still not sure what you do in your setup in the case I describe; You rfid panel says disarmed but your alarm is armed and somebody enters the house and wants to disarm via the panel; this will not work (panel is already disarmed so no status change in Domoticz) so no change will happen in your controller (causing the alarm to be tripped).

[heggink]

Interesting. I DO want to know more about your setup and how you handle stuff. You seem to have a bunch of similar approaches (and devices such as Nest) although your approach is a bit different.

As to the keypad, since the keypad cannot switch the domoticz security state through a blocky, I use lua to trigger the security state change. The good thing with the keypad is that it triggers EVERY time so if it's off and you switch it off again, it will send another off to domiticz which I track. That way, I can arm domoticz via my TAO dummy device and can disarm via the keypad. If I arm via the keypad, TAO in on and I can disarm with both again. Sweet and simple.

I'll PM you to better understand your setup. May learn a thing or 2 from you .

H

[remb0]

My siren and zipato keypad arrived.
I'm reading and thinking about my scripts and blockies.

In the example scipts i read: MCS_ where stand this for?

I think it's good to replace the simple blocky scripts with lua.
Because lua is more flexible and some blockies can be put in less scipts ?
more devicechange events in 1 script.

Instead of the virtual switches I will place an $ in the name.
So it will not make my screens full of switches. and in the roomplan I make a room: Alarm where I put the hidden switches.

other actions:
When alarm is armed Every light must turned off.

[heggink]

Hi Remb0,

I used MCS_ for the door/window sensors (no idea why I used MCS btw, alzheimer light...). Starting with MCS_ and PIR_ allows me to add devices without having to change the lua scripts.

Agree with the $ in front of dummy switches. Over time, I did put some more logic into some of these dummy devices. Downside of a $ in the name is that you have to un-$ them to edit.

Wrt the zipato keypad, realise that it cannot be accessed once in sleep (which is fast) so do not expect to be able to change its state to disarmed remotely. I now only use it as a trigger device to switch the alarm on/off but I do not check it at all. I have my own device that triggers alarm on/off (called TAO aka TurnAlarmOn of Off). Everything goes through TAO.

Based on an exchange with @tyfoon, I also adopted an auto activate/deactivate so arming is done automatically within a certain period of no-device (geofence, Wifi)/no-activity. Works really well!

In terms of lua vs blocky, that's a choice. My initial thought was that most people are less comfortable logging in on systems, doing bash/lua stuff and could get away with blocky much easier so if I provide the base PIR/MCS/Zipato scripts, everything else could be done by any end user themselves without a real need for linux expertise. Again, choices .

I really should update the wiki BUT I have changed my scripts so much that I have no idea how to get that done in a manageable way ATM.

H

[heggink]

btw, I also put my NEST to away when the alarm gets armed.

[lost]

Hello,

I'm waiting for a few motion detectors & other stuff to add some alarm functionality to my domoticz setup (only managing heaters for now).
In fact, to avoid false alarms, I'm wondering what would be the best way to detect family presence to disarm.

I saw the zipato keyboard+rfid (easy for childs to use a tag, possibility to use code if you forgot your tag... but must not forget to arm when leaving!), but looking at rfid standards supported, looks this device does not support secured tags standards. So in Domoticz that'll be just a tag ID that will show up without any secured verification from the keyboard/rfid-reader.

Problem is nowadays a lot of smartphones have rfid and it's very easy to get the software that can read tags... and imitate them! So you're security vs someone who noticed your tag is up to him never getting close to you with his phone.

In fact, I did not found any good solution. BT detection using MAC adresses can also be spoofed: That's again just an ID(=MAC) check. The only added security would be that a phone is not supposed to be used as an access control device like a rfid tag on your home keys ring. Maybe IP presence check using wifi is better (if associated to a secured network!) but will most of the time cause problems with devices power-saving strategies (wifi on 100% of the time would drain battery quickly ; on the BT side it's not a problem, especially if the device is configured for no broadcasting = undetectable setting, usually).

Only remains IMO using a true external burglar resistant keyboard or a secured tag reader, directly connected to the PI or relayed by some radio (Z-Wave for instance, but with a crypto key the user will have changed, before the first device association, from the default 00:01:02... that sits in most controllers!) if wiring is a problem.

If anyone have anyone found a cost-effective solution, but reasonably secure, please let me know...

At the moment, I plan to use BT... but with an added security compared to just the MAC presence query (without association) that sits in most scripts: Once device if found, add checks on it or even associate the device (thus using native BT association security), even just a few seconds, when seen back home.

That'll use a mix of phones and for instance Xiaomi Mi low cost activity trackers/watches (for childrens).

BR

[remb0]

It the folowing true? The scripts in this topic uses a virtual switch to trigger a blocky, and that blocky turns on the siren in x second.
This is because when the scripts are written the 'on for x' command wasn't available?

I had the samples from heggings and I try to create 1 massive script to handle everything (if possible)
So you have one place to change settings, less memory consumption, less complex.
On the other hand it would be easier to adopt by other users (I must implement this system also by familiy:P)

I have a lot to do:
- enter the speaking options (thanks to heggink)
- auto arm alarm
- making documentation complete

[heggink]

Hey Remb0,

Not sure I understand. If motion is detected (MCS/PIR lua scripts -> AlarmDetected='On') and the alarm is armed (AlarmMelding Blocky) then SoundSiren is set to On after 90 seconds. This is to allow someone to enter the door and disarm in a regular way. If the system is not disarmed then the SoundSiren blocky will sound the alarm for 3 minutes (set Sirene = 'On' for 3 minutes).

So this was implemented using "on for xx minutes". I am probably missing your point. Feel free to pm me.

H

[lost]

I'm currently using alarm scripts from the wiki as a basis, combined with some custom python stuff runned as a service (mostly on the presence detection side) & notifying some domoticz virtual switches. That's OK for now, but I'm willing to minimize false alarms & handle some possible sensor failures (especially the "always on" case), so I wonder what would be the best way to do so: Is there an easy way, for instance using domoticz logged statistics/history, to filter-out a sensor/switch that sends too much detections per unit of time or looks to be locked?

[korniza]

I'm currently using alarm scripts from the wiki as a basis, combined with some custom python stuff runned as a service (mostly on the presence detection side) & notifying some domoticz virtual switches. That's OK for now, but I'm willing to minimize false alarms & handle some possible sensor failures (especially the "always on" case), so I wonder what would be the best way to do so: Is there an easy way, for instance using domoticz logged statistics/history, to filter-out a sensor/switch that sends too much detections per unit of time or looks to be locked?

I have the same thought. On paper I designed sensors and put some user variables on every sensor (weights). So I design a script to add these weights in time of 5 minutes (let's say that external balcony PIR sensor has a weight of 2 and the internal camera that is looking on balcony door the weight of 4). if weight_sum gets bigger than 4 then I will get a verified alarm.
I used numbers on power of 2, so adding them you get the path of what sensors are triggered (as far I think it on paper).

any idea to make it solid are more than welcome!

[benotje]

Hello, I have a question I used the alarm wiki
but the var. Sound Siren is no 1 so I can not send me siren ?? Who wants to help me

Knipsel1.JPG (72.99 KiB) Viewed 5707 times

[heggink]

Hi Benotje,
As per one of my previous posts, domoticz no longer triggers of variable changes, It used to do that but that stopped working at some point. Replace your variables with dummy switches and test these on change.
H

[heggink]

@korniza: interesting concept. I don't use any weighting as I only check on devices that should trip the alarm immediately. I have a door sensor on the electric cabinet. If anyone opens that during arrmed state then the siren must go off immediately (not even after a while but straight). I have sensors around the house. If they trigger when armed then, again, I want the alarm to go off after 90 seconds (allowing anyone to disarm if need be).
I can imagine your system to work quite well as a perimeter defense system.
H

[korniza]

@korniza: interesting concept. I don't use any weighting as I only check on devices that should trip the alarm immediately. I have a door sensor on the electric cabinet. If anyone opens that during arrmed state then the siren must go off immediately (not even after a while but straight). I have sensors around the house. If they trigger when armed then, again, I want the alarm to go off after 90 seconds (allowing anyone to disarm if need be).
I can imagine your system to work quite well as a perimeter defense system.
H

I'm old school guy: first design on paper and after implement
The idea is to have an idea where the intrusion performed on first place and after follow the path using the weight_sum.
let's say that front balcony sensor has weight of 64, the 1st back door 128 and second back door 256 and the main door 512.
Inside house sensors can have low weights calculated according to the proximity of external sensor, smaller than 64 (2/4/16/32).
You can have an active alarm system on night when all family is inside, so weight_sum has to be bigger than 72 (2+4+16+32) to activate an intrusion detection, which indicates that intruder passed perimeter and is inside house. I can save this weight_sum for further investigation as it can easy indicate the movement inside house

Code: Select all

if weight_sum is 260 -> 256 + 4 ->  second back door + camera inside kitchen

I think is ideal even for pets inside house.

This concept has to do how you installed your sensors. Another positive is that you can change the weights on the fly, so you can create better scenarios.

For example:
I used external ip cams as motion sensors so when is windy outside, false alarms are increased due to trees movement. I like to decrease the weight on external ip cams and increase weight of PIR sensor.

[korniza]

Another idea for discussion is to use a selector switch. I used bluetooth proximity sensors to check if someone is home. I like to get manual arm/disarm (keypad), auto arm/disarm (bluetooth sensors), service mode (no siren will be trigggered) and off. My idea about OFF is to use a hidden NFC tag, so scanning with a device will send a OFF level on the selector switch.

[Egregius]

With 3 switches: away, sleep and notifications you can do already very much.

[korniza]

With 3 switches: away, sleep and notifications you can do already very much.

I had this problem when i use multiple switches: they can be active more than 1, so domoticz can have sleep and away active by mistake.

[Egregius]

Code: Select all

if( $s['sleep'] == 'On' && $s['away'] == 'On' ) sw($i['away'],'Off');
 

Problem solved
In my scripts it isn't even a problem if both are active.

[korniza]

Code: Select all

if( $s['sleep'] == 'On' && $s['away'] == 'On' ) sw($i['away'],'Off');

Problem solved
In my scripts it isn't even a problem if both are active.

Sorry for my question but I try to understand why do not use selector switch? Selector Switch is less complex that a script and there is no way to get conflicts on state.
Do you earn something extra (special use on status of alarm) from this setup or is it a another way to do it?