[Release] Nyckelharpa, an HSM Extension

d_man97 · February 17, 2021, 2:36pm

I am having trouble getting beeps when a door contact is open and for a countdown when the system is armed. I am using Piezo buzzers with a Konnected alarm board. These are what I have in global settings:

And this is my log around the time I opened a door to test:

app:682021-02-17 09:14:30.394 am traceIn cmdHandler...

app:682021-02-17 09:14:30.060 am traceIn updateMembers - (2.6.0)

dev:1132021-02-17 09:14:27.281 am infoDining Room-Motion is active

dev:92021-02-17 09:14:25.967 am infoFront Door Lock was manually locked [physical][6:1]

dev:92021-02-17 09:14:25.965 am debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:21, eventParameter:, numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:1, zwaveAlarmStatus:255, zwaveAlarmType:6)

dev:92021-02-17 09:14:25.960 am debugparse: zw device: 09, command: 7105, payload: 15 01 00 FF 06 01 00 00 , isMulticast: false

dev:12021-02-17 09:14:25.752 am infoDen Motion is inactive

dev:1052021-02-17 09:14:20.800 am infoFront Door-Sensor is closed

dev:1052021-02-17 09:14:15.870 am infoFront Door-Sensor is open

dev:92021-02-17 09:14:15.336 am infoFront Door Lock battery is 100%

dev:92021-02-17 09:14:15.334 am debugBatteryReport: BatteryReport(batteryLevel:100)

dev:92021-02-17 09:14:15.304 am debugparse: zw device: 09, command: 8003, payload: 64 , isMulticast: false

dev:92021-02-17 09:14:14.795 am infoFront Door Lock was manually unlocked [physical][6:2]

dev:92021-02-17 09:14:14.792 am debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:22, eventParameter:, numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:2, zwaveAlarmStatus:255, zwaveAlarmType:6)

dev:92021-02-17 09:14:14.715 am debugparse: zw device: 09, command: 7105, payload: 16 01 00 FF 06 02 00 00 , isMulticast: false

dev:1132021-02-17 09:14:14.545 am infoDining Room-Motion is inactive

dev:1132021-02-17 09:14:07.208 am infoDining Room-Motion is active

dev:12021-02-17 09:14:04.488 am infoDen Motion is active

app:682021-02-17 09:14:00.453 am traceIn cmdHandler...

arnb · February 17, 2021, 2:54pm

Suggest removing the keypad from this setting since it kills any countdown tones on the keypad device. Also which keypad model is installed? Does the Alarm Panel beep?

d_man97 · February 17, 2021, 3:53pm

I do not have an actual keypad. I have a FireHD tablet that I use to arm/disarm my alarm that I call a keypad. That device listed is Piezo buzzer that is located near my tablet.

I can remove it if necessary. I thought it would not matter since it was not a keypad.

arnb · February 17, 2021, 4:56pm

If it's not a real keypad, then it should be OK.

How is the "Beep" tone created on the tablet and does it sound without using the Nyckelharpa app? Also are you using the built-in HE dashboard authorization keypad or something else?

I use two Fire tablets and two old Android phones for dashboards, announcements and tones. The devices use the Fully Kiosk Browser, Fully Kiosk Browser Controller device app, and some sound files loaded onto the devices for sounds and tones.

d_man97 · February 17, 2021, 5:48pm

I do not have the tone created by the tablet. I have a buzzer near the tablet make the sound. The buzzer is part of my Konnected alarm system. It is setup similar to this:

Through the konnected alarm app a device is created called Keypad-Beep. That is what I selected to use for the beep in the Nyckelharpa Global settings. I can get the buzzer to beep turning it on in the device settings.

I do not have any keypad set-up in Hubitat. I am using the dashboard and hubitat safety monitor to activate and deactivate the alarm.

These are the device options I have for the buzzer, is there something in here I need to change?

MARK7 · June 24, 2021, 7:56pm

Everything had been working fine, but then I updated to Nyckelharpa v1.2.1 and I lost the ability to arm HSM from my Centralitex keypad model 3405-L which I think is Iris V2. I was using the Nyckelharpa Centralite-Keypad driver version 1.0.3. I upgraded the driver to 1.0.5 and now I can arm the system, but I still don't have exit delay tones when the system is armed.

I tried removing Nyckelharpa ModeFix and reinstalling (no settings) which didn't work. In my keypad device, I can enter 15 for the "Set Exit Away" command and I get the normal beeping. When I try to enter 15 for the "Set Exit Delay", I get nothing.

I tried rolling back Nyckelharpa to v1.2.0 and then to v1.1.2 but that didn't fix it.

Any help is appreciated.

arnb · June 24, 2021, 8:42pm

Before doing a deep dive into this issue, please update all the Nykelharpa modules and keypad driver to the latest versions. I prefer using the Hubitat Package Manager, although it can be done manually.

Exit and entry delay times are set in HSM.

The 3405-L is the Iris V2, that has a few firmware versions and beep commands. Should it not beep please try setting the following in the device.

MARK7 · June 24, 2021, 9:49pm

Thanks for the help. I've updated via the packet manager. I'm on Nykelharpa version 1.2.1. My keypad is using the Nykelharpa driver version 1.0.5.

The keypad is beeping, just not getting beeps after the alarm has been set to let us know the system has been armed.

arnb · June 24, 2021, 10:13pm

I armed my system in away mode 30 second count down with an Iris V2 and after the last five seconds of fast beeps, it gave a long hardware generated beep when armed.
My suggestions are limited. They are:

Try with the Old Style Beep setting on and off
Turn up the keypad volume by holding the 2 key
Use a speaker/TTS device announcing the arming and disarming. The Talker module supports this.

MARK7 · June 24, 2021, 10:36pm

I tried it with the old style beep on and off. No luck.

I'm hearing the beeps just fine on the keypad.

In an earlier post you mentioned "the Exit Delay sound works when initiated from the device's settings page". For my keypad, I can enter 15 into "Set Exit Away" and I get the exit delay tones. When I enter 15 into "Set Exit Delay", I do not get the exit delay tones. Shouldn't that work too in the driver?

Is it possible I'm on some weird firmware version for my keypad? Here's what the device is telling me-

softwareBuild: 140B5310
driverVersion: 1.0.5
model: 3405-L
firmwareMT: 104E-0021-140B5310
manufacturer: CentraLite

Thank you.

arnb · June 24, 2021, 11:10pm

I actually have two 3405-L keypads, same software and firmware as your device.

Checked out the second one in my garage on my way out, it didn't give an an arm tone but does beep🤷

MARK7 · June 25, 2021, 12:40am

Ok, not sure what the problem was, but it's working again. I did a factory reset on the keypad, then I deleted the device, changed the batteries and re-added to Hubitat and it is working now. When I did re-add it, I needed to have the "old style beep" set to on. Thanks for the help troubleshooting.

Smartsmartsmart · July 27, 2021, 10:59pm

Installed the app through Hubitat Package Manager but not coming up in Apps. What could have I done wrong?

bill4 · December 9, 2021, 9:02pm

In case you haven't figured this part out....under apps click the add user apps. Then select nyckelharpa. Then configure the settings.

For those that have this up and working with Talker, can you confirm if you can get your Alexa devices to announce the message about intrusion where it should say something about disarm the system or the police will be alerted? For some reason I can only get the message after arming and disarming.

arnb · December 9, 2021, 9:36pm

That is the default entry/intrusion delay message. Assuming it's an uninvited guest / burglar, it says "Disarm system, or police will arrive shortly", but it can be anything you want. It is generated when the current HSM Status has an active intrusion delay.

I don't have Alexa output devices, but it works on my four tablets with the Fully Browser. Hope you get it working and post the solution here.

oldcomputerwiz · December 9, 2021, 10:12pm

It works on Google home devices too.

bill4 · December 9, 2021, 11:13pm

For some reason my exit and entry messages do not work. I tried changing the stock message to see if it just needed to be updated or something but when I tried to hit the next at the bottom of the page I get an error. ERROR: All TTS devices do not have Chime command, set 'Sound TTS Chimes' Off

The arm and disarm messages still work though. Very strange.

arnb · December 10, 2021, 3:57am

That error message is generated when a target TTS device does not have a chime command. Set the On / Off sliders for all the Sound TTS Chimes message to OFF, click/tap Next then Done, then retry.

Should you continue to encounter an issue, please check the logs and forward any Nyckelharpa app error messages.

arnb · December 14, 2021, 8:04pm

Should you be using an Iris V3 Keypad with a Data: softwareBuild less than 10046230, User Centralitex driver, and the keypad freezes after a self initiated arming with an open contact "arming canceled", you need to review the following thread for a solution.

markbellkosel84 · March 28, 2022, 10:14pm

@arnb I am using a virtual keypad. Is there anything particularly special I need to do configuration wise?