Basic Home Alarm Setup with Zipato Keypad

Share your Projects!
56

@smi First you must get the shell commands to show up in the font end. Check your logs to debug. I needed to escape the double quotes.

The commands I posted above (#54) only replaces the AppDaemon part. You still need the basic automations to arm/disarm the alarm based on the state of sensor.alarm_keypad_alarm_level (either 255=armed and 0=disarmed).

I have these as:

- action:
  - data:
      entity_id: alarm_control_panel.ha_alarm
    service: alarm_control_panel.alarm_arm_away
  alias: Alarm to Armed
  condition: []
  id: '1513634400284'
  trigger:
  - above: '254'
    entity_id: sensor.schlage_link_mini_keypad_rfid_alarm_level
    platform: numeric_state

- action:
  - data:
      entity_id: alarm_control_panel.ha_alarm
    service: alarm_control_panel.alarm_disarm
  alias: Alarm to Home
  condition: []
  id: '1513671114417'
  trigger:
  - below: '1'
    entity_id: sensor.schlage_link_mini_keypad_rfid_alarm_level
    platform: numeric_state
57

Hi!

Thanks, I also have that basic automation thing; will try the appdeamon replacement (the script) without double quotes, with and without sudo and so on.

Regards

58

Great. Just to be clear, I have this as a shell command which I think is different from a script. See here.

I have been testing all day and it seems to work fine. I will post a complete config with instructions when I have finalised everything :+1:

59

Yeah, mixed scripts and shell commands up. :confused:
That’s also the reason why it doesn’t appear in frontend.

Unfortunately the shell command still doesn’t set the keypad alarm level even after various changes on the shell command …

60

Thanks @skptic for the examples to help me with my keypad.

What I have working is;

  • Away/home button with enrolled-keypad-code or enrolled-rfid-tag results in double-beep success indicator sound (only when HA cache for sensor.schlage_link_mini_keypad_rfid_access_control is in disarmed/armed state respectively, otherwise 4-beep error)
  • Away/home button with wrong code results in 4-beep error indicator sound
  • Switch to change HA state cache for keypad (contrary to above, I don’t think you can set the state of the keypad itself, there are no command classes to achieve that, rather you can change the state cache of HA so that when the keypad sends a correct arm/disarm, HA can trigger an automation. I used the shell_command: curl config to change HA state, thanks!)
  • Automation to toggle Dome Siren primary/secondary siren/chime based on armed/disarmed states respectively.

The keypad indicator sounds were achieved thanks to https://github.com/OpenZWave/open-zwave/pull/1315/files/b14932f945415907c1e871af9c6b0b808df867bc applying the source file changes to a master git clone, and installed via pip uninstall python_openzwave and pip install python_openzwave --install-option="--flavor=dev". The dev flavor enabled me to softlink my custom open-zwave directory so that pip install picked it up.

My HA version is 0.60, my python_openzwave is v0.4.0.35, my open-zwave is custom ontop of 1.5, which results in sensor.schlage_link_mini_keypad_rfid_access_control as my state to trigger upon, state of 6=disarmed and 5=armed. The differences could also be because my keypad identifies as 6131:5501 instead of 6131:4501

I’ve yet to employ my siren set-off automations with door/motion sensors. Going to wait until I can find time to test and not scare the kids…

61

Dear all, I’ve been following this thread with interest.

Right now I’m in the process of getting my HA based alarm system up and running, Fibaro motion sensors working like a charm. Currently triggering my Sonos to play an alarm sound until my siren comes (in back-order duh). Actually using the alternative alarm setup as described here: Alternative Home Assistant Alarm

I also ordered 2 of the Zipato (Benext) Tag readers and frankly am having a bit of trouble.

I managed to securely connect one to my HA setup, renamed the node to Tag_Reader_I. So far so good, but when I press any of the buttons on the keypad (‘home’ or ‘away’) I seem to only get errors in the logfile:

> 2018-01-13 19:09:19.759 Detail, Node007,   Received: 0x01, 0x0d, 0x00, 0x04, 0x00, 0x07, 0x07, 0x88, 0x03, 0x66, 0x00, 0x00, 0x01, 0x2c, 0x36
> 2018-01-13 19:09:19.760 Detail, 
> 2018-01-13 19:09:19.761 Info, Node007, ApplicationCommandHandler - Unhandled Command Class 0x88

So not even at the point of figuring out how to get the codes/tags recognized. Let alone syncing with the HA alarm state :-).

Does anybody recognise this behaviour? suggestions?

Many thanks in advance!

Setup: HA 0.60.1 / PI3 / Python 3.6.4.

62

If you are using openzwave, could you look in your openzwave cache xml file, locate your Node007 entry and list here the manufacturer id and product id? That would tell us what your openzwave thinks Node007 is.

63

Hi @merredin thanks for your reply. I made some progress in the meanwhile:

It turns out one of the tag readers is defective, I cannot get the ‘set code’ segments to display for this device. When I tried the other one it does register. So that was a day and a half gone before I figured that out :-). I think this caused the ‘unhandled command class error’.

Following your guidance (loading the lock zwave platform and changing the lock/zwave.py code) I am able to register tags via HA. So that is great as well, many thanks for that. One question around setting pin codes, suppose you want to set the pin to 1234, do you simply register 0x31 0x32 0x33 0x34 + trailing 0x00’s through HA? I was having some trouble with that, but need to try again tonight.

So next step is making sure the reader syncs status as described in this thread.

Thanks for you help, I’ll let you know once it’s all up & running.

64

@merredin Thanks for pointing to the Pull Request. I have to check that. My instalaltion is using the Dev branch since I have the Eurotronic Spirits. Unfortunately the PR is not merged yet, so I will have to use the dev flavor instead of ozwdev.

Considering the sync state I have a very simple approach in my setup.
I use sensor.keypad_access_control as the trigger. This has states “Access Control - KeyPad Unlock” or “Access Control - KeyPad Lock”.

The keypad always sends an event to HA when a button has been send, no matter if it was the same button again or not. The reason why the automation is not triggered is that trigger trigger only fires if the state is different from the old state. So if you press the same button again, then you do get an event in HA, but the automnation is not triggered since the state has not changed.

The solution here is to use a state trigger and only define the entity_id and not define to and from. Then check the state in a condition.

- alias: Set Alarm Home
  trigger:
    - platform: state
      entity_id: sensor.keypad_access_control
  condition:
    - condition: state
      entity_id: sensor.keypad_access_control
      state: Access Control - KeyPad Unlock
  action:
    - service: alarm_control_panel.alarm_disarm
      entity_id: alarm_control_panel.ha_alarm

- alias: Set Alarm Away
  trigger:
    - platform: state
      entity_id: sensor.keypad_access_control
  condition:
    - condition: state
      entity_id: sensor.keypad_access_control
      state: Access Control - KeyPad Lock
  action:
    - service: alarm_control_panel.alarm_arm_away
      entity_id: alarm_control_panel.ha_alarm

This is also mentioned in the documentation for the state trigger

Triggers when the state of tracked entities change. If only entity_id given will match all state changes, even if only state attributes change.

1 Like
65

Woah looks like this has moved on a far bit since I last checked :smiley:

Did you guys manage to get the keypad to start beeping once say the door opens, to give you an audible warning that you need to go over and disarm? Or is that still not possible as the keypad is asleep and HA can’t send it messages?

66

What’s this syntax? All my automations start with a trigger and the action is last.

67

Ooh is this a siren that can do chimes as well as sirens based on different actions? I’ve been trying to find one as my Neo Coolcam one seems to only be able to do one or the other once it’s set up.

edit having googled it, it looks like it’s identical to my Neo! So how do you make it do different noises? Mine only has 1 switch which sets off the siren.

68

Copy/pasted from my automations that I have been built using the automation editor in the web interface.

I believe it is a dictionary so the order of each level (trigger/action) makes no difference. But I agree it is counter-intuitive to read.

1 Like
69

Ahh interesting - I’ve always built my by hand so I’d not seen it done that way before :smiley:

70

Hi,
I managed to edit my zwave.py file by using your changes but when I reboot HA I get this in the log:

Error while setting up platform zwave
Traceback (most recent call last):
File “/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py”, line 82, in async_setup
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File “/usr/lib/python3.6/asyncio/tasks.py”, line 358, in wait_for
return fut.result()
File “/usr/lib/python3.6/asyncio/futures.py”, line 245, in result
raise self._exception
File “/usr/lib/python3.6/asyncio/tasks.py”, line 180, in _step
result = coro.send(None)
File “/usr/lib/python3.6/site-packages/homeassistant/components/lock/zwave.py”, line 130, in async_setup_platform
descriptions = load_yaml_config_file(
NameError: name ‘load_yaml_config_file’ is not defined

I have also added this to the configurations.yaml file:
lock:

  • platform: zwave

I am running this under Hass.io 0.65.5

Do you know what my be causing this?

71

Hi again,

I added this to the the zwave.py file:

import os
from homeassistant.config import load_yaml_config_file

then I changed to this:

descriptions = load_yaml_config_file(
os.path.join(os.path.dirname(file), ‘services.yaml’))

Now it continues but stops with this error:

  File "/usr/lib/python3.6/site-packages/homeassistant/components/lock/zwave.py", line 193, in async_setup_platform
    descriptions.get(SERVICE_SET_USERCODE), schema=SET_USERCODE_SCHEMA)
TypeError: async_register() got multiple values for argument 'schema'

Does someone know what’s causing this in this section of the code:

hass.services.async_register(
    DOMAIN, SERVICE_SET_USERCODE, set_usercode,
    descriptions.get(SERVICE_SET_USERCODE), schema=SET_USERCODE_SCHEMA)
hass.services.async_register(
    DOMAIN, SERVICE_GET_USERCODE, get_usercode,
    descriptions.get(SERVICE_GET_USERCODE), schema=GET_USERCODE_SCHEMA)
hass.services.async_register(
    DOMAIN, SERVICE_CLEAR_USERCODE, clear_usercode,
    descriptions.get(SERVICE_CLEAR_USERCODE), schema=CLEAR_USERCODE_SCHEMA)
72

hi @souI I have the Neo Coolcam sirene and use it to play different sounds based on the state of the alarm (ie.disarming, arming, succesfully armed etc).

I use the following in my script to change the sound before switching it on (example):

- service: zwave.set_config_parameter
  data_template: {
    "node_id": 10,
    "parameter": 5,
    "value": "Alert"
    }

The different values you can use are:

"Doorbell"
"Fur Elise"
"Doorbell Extended"
"Alert"
"William Tell"
"Rondo Alla Turca"
"Police Siren"
"Evacuation"
"Beep Beep"
"Beep"
2 Likes
73

hI @anasazi I also implemented the changes to the lock/zwave.py as indicated by @merredin but did not encounter these issues. Also not after upgrading to 0.65.

You should not have to alter anything else in the zwave.py file, just be very careful not to miss anything. Essentially you comment out the “network = hass.data[zwave.const.DATA_NETWORK]” line at 130 and then add the same line in the 3 functions (set_usercode(), get_usercode() and clear_usercode()).

Be careful with using ‘tabs’ instead of spaces for indenting your code, python is finicky about that.

74

Mate that’s fantastic thank you! Will give it a go :smiley:

75

Hi,

Is it possible for you to share your complete zwave.py so that I can compare with mine?