HKC Alarm SW1070 adding Konnected for HomeAssistant

shaun c p

Sharing the how to connect these three together as I saw lots of conversation but struggled to see an end to end picture of how and whether this works.

It does work, took me longer than expected on the ESP32 configuration.

Prerequisite: 

1: HKC : Need two spare zones to use as key inputs on HKC (to allow PartSet & FullSet)

2: HKC : 2 default spare outputs on HKC SW1070 (to get the status of hte alarm)

3: Need to make a plastic mounting bracket to sit over the HKC, alarm 

Connected Configuration:

Konnected : Konnected Pro for me with 2 interface zone modules.

Konnected: Output 1 to relay 1 input on konnected Interface Module

Konnected Output 2 to relay 2 input on konnected Interface Module (& enable output2 on Konnected Pro board

Wire Konnected to HKC SW1070 Wiring

1: Connect the Konnected Interface Zones to the corresponding HKC SW1070 zones

2: Connect the two relays to two spare zones (zone9 & 10 in my case)

3: Connect the strobe output to a free Konnected zone to provide a view of when the alarm is going off

Tuning Zone.

Zone tunning, potentiometer tunning worked by triggering from Closed to Open on one board, the other board could only tune it from Open to Closed ? Fiddly but got it consistently working in the end. The only output that I couldn't get working with the potentiometer output zone was the internal siren but achieved same result out of the strobe outputs, inorder to determine when the alarm had been triggered

 

HKC Alarm Settings:

1234 then User Code to to access Engineering

To set the outputs to inform HomeAssistant of state, do the following:

Service Menu -> Zone Menu -> Outputs Menu -> Panel Outputs -> Panel1 -> Select 'Partset'

Service Menu -> Zone Menu -> Outputs Menu -> Panel Outputs -> Panel1 -> Select  'Armdisarm'

To setup the inputs to allow homeassistant to set the alarm do the following:

Service Menu -> Zone Menu -> Zone Name - Zone<9>   -> Set name to 'PartSet'

Service Menu -> Zone Menu -> Zone Type  - Zone<9>   -> Select type to 'PSA'

Service Menu -> Zone Menu -> Zone Name - Zone<10>  -> Set name to 'FullSet'

Service Menu -> Zone Menu -> Zone Type  - Zone<10>  -> Select type to 'Key'

Then load the ESPHome and modify the Konnected ESP32 chip to HKC

I added the 'ESPHome' 'Add-ones' to my HomeAssistant

Modify the YAML to:

1: Create two momentary switches for arm/disarming the alarm

 Commented out the unused alarm beep #- packages/warning-beep.yaml

 Added two switches to the yaml ,(i.e)

switch: 

- platform: gpio

   id: btnArmDisarmFull

   pin: $out1

   name: 'btn-do-ArmDisarm-Full'

   on_turn_on:

   - delay: 400ms

   - switch.turn_off: btnArmDisarmFull

Note: It was only 375ms pulse that worked consistently for the Partial set/unset

2: Capture the HKC outputs for status by

  renamed zone3 to  out-AlarmIsPartSet

  renamed zone4 to  out-alarmIsSet

  renamed zone 6 to  out4-StrobesActivated one and inverted the binary output

 (i.e)

binary_sensor: 

- id: zone5

    name: out3-AlarmIsSounding

    pin:

      number: $zone5

      mode: INPUT_PULLUP

      inverted: true

2: Consistent reconnects, made the IP static on the device itself

wifi:

  ssid: !secret wifi_ssid

  password: !secret wifi_password

  manual_ip:

    static_ip: 192.168.1.151

    gateway: 192.168.1.1

    subnet: 255.255.255.0

Then ran ESPHome to flash the device with the setting

In Home assistant (Briefly)

 To capture the delay between the alarm setting & give U.I feedback

 I created 3 helper 'buttons' : Arm-FullSet, Aarm-PartSart, Disarm

 I added 2 'helper' timmrs (A setting and an unsetting timer)

SW1070 cabinet, showing the fitting, part way through the install

YAML configuration to support the ESP32 modifications

AlarmESP32.txt

kub

What version of software is that 10/70 panel please and are you happy that what you have done to that panel, still keeps it within the confines of EN 50131 as it was originally designed to be ?

shaun c p

Re Firmware version. It's 4.2

Re: EN 50131 standards. As a private user, not a consideration, its my insurance policy I need to stay within.

Missing declaring goals for the alarm konnected integration too.

1: Secure alarm perimeter nightly by removing barriers to setting it by integration with rest of home automation. Also automatic conditional unsetting.

2: alarm notifications to remote users when alarm is triggered. Original app was slow to alert.

3: actions on alarm. Open architecture and integration. Ability to power on video surveillance and light sequences when alarm is tripped

4. Alarm life extension. False alarms. Old system when alarm is false positive , capability to build the smarts in to do the diagnosis and shut down the alarm rather than fumbling around in the small hours of the morning.

5. Heating. Perimeter zones feed into heating and ventilation conditions

italianfella

hi, thanks for sharing

Have a problem,can’t get the tuning working.

If solid orange it will not go off when i open the door/window

If tune it just when the light blinks on and off, it goes off when i open the door/window so it reads zone open correctly on the app.

But the problem is that when is close the door/window, the app constantly see the zone as opening and closing no stop .

any suggestions or please?