[Release] Nyckelharpa, an HSM Extension

[Major Update] May 19, 2019 10:10AM EDT

Enhancements and Changes

  1. Improve Panic reliability by changing it to use an HSM Custom Rule allowing for Panic alerts no matter how the HSM app is armed or setup. Eliminated need for, and use of the virtual panic contact sensor

  2. Completed support for UEI keypad.

  3. Corrected references to Smartthings and other textual issues

I urge everyone to stay up to date, please update your system,

How to Install
There is one (5) modules associated with this update. All modules are updated.

Apps Code

  1. Nyckelharpa
  2. Nyckelharpa Modefix
  3. Nyckelharpa Talker
  4. Nyclelharpa User

Drivers Code
Centralite-Keypad

How to Convert from original version

  1. Update all modules

  2. For each device using the user provided Centralite Keypad driver
    review the settings, especially the Panic setting, then update the device's settings. (Important!)

  3. Review the Global Settings then save (Important!)

  4. Remove the NCKL-Panic Contact from use in HSM, then delete the device, or you may delete the device first which should auto remove it from wherever it's specified

  5. Create the HSM Custom PANIC rule as explained in README.md Documentation Section 12

Documentation
Updated and added How to create HSM Custom rule and uninstall sections

Thanks for the update, when reviewing global settings, it shows this, but you said to eliminate the contact from HE and HSM, correct?

Yes, it may be deleted from Devices, it is not automatically deleted and is no longer required

Verify you are running with Nyckelharpa V0.1.8, it no longer creates the NCKL-Panic Contact

1 Like

Stumbled across your app searching for info on the UEI keypad - this works perfectly. Still working on tweaking my system, but so far so good. Thank you!!!

Do you know if it's possible to use the UEI keypad to arm a mode without entering a code first?

Thank you for letting me know.

AFAIK only the Iris V2 and Iris V3 allow instant arming.

1 Like

[Update] May 24, 2019 12.01PM EDT

Enhancements and Changes

  1. When Nyckelharpa button is clicked/tapped on APPs page, verifies the version of active Nyckelharpa modules and keypad driver if used. Thanks to @Cobra for the idea and base code

  2. Change text: incorporate Hubitat PhoneApp as a notification device.

  3. Fixed Arming Canceled and Arming Forced messages: were not being sent to notification devices

I urge everyone to stay up to date, please update your system,

How to Install
There are three (3) modules associated with this update.

Apps Code

  1. Nyckelharpa V0.2.0
  2. Nyckelharpa Talker V0.0.8
  3. Centralitex Keypad V0.2.0

Documentation

  • Added message destinations
  • Added Known Issues section
2 Likes

First screen opening Nyckelharpa app

Clicking next, next page is fine.

Thank you

My apologies, forgot to update the Centraliex Keypad and include that in the update.

Please update the Centralitex Keypad driver, it's updated in Github

1 Like

Yep, that did the trick, thanks!

1 Like

Two questions...

  1. Anybody with a 3400-G not getting entry delay tones anymore, or the keypad acting funny? This happened within the last 6 weeks, after an update (I just haven't tried fixing it yet). I did try using the native Centralite driver from HE, but that didn't make a difference.

  2. I tried to uninstall/reinstall everything from Nyckelharpa, but how do you get Nyckelharpa loaded? I deleted and readded the app code again from Github, but it isn't showing up in the Apps section under Nyckelharpa, or as a user-app.

Thanks in advance...

Edit: I mean Nyckelharpa USER, not the main app.

Running OK here

I'm sure you know this, but have you tried holding the 2 key to raise the volume. Hold 5 key to lower volume.

I get tones when the door opens (so it's not a volume issue), but not the "entry delay" tones when the system is armed.

There is something wrong with the driver or hubitat. If I don't pair the keypad it will beep on every keypress. The beeping was working perfect for mine(3405-L w/ latest firmware) up till about Hubitat 2.06, after that people reported the "not beeping" issue many times.
I have it working on smartthings, but need it on hubitat.

@mike.maxwell knows about the issue and reported a fix is on the list, but @anon61068208 stated that himself & Mike could not figure it out.

In experimenting I have found the keypad needs time, if you try to rapidly unpair/reset/pair it does not respond properly, it needs some downtime. Not sure what's going on, possibly caps in circuit need to drain down before device can fully reset.

@mike.maxwell found a fix ? That's the first I heard about it.

excuse my english. I meant he stated it was on his issue list to be fixed

It's on mine as well but it's not a priority right now. The basic functions work so beeping is a luxury for it.

Did you ever get a chance to check into this "extension"? Sounds like a good add on just in case you need to bypass a sensor... Whats your thoughts?

I did not. I don't have that large a house, so checking for open windows is easy. Couldn't justify the overhead of another app on the hub.

...as you can tell, home automation is new to me and I surely don't know the capabilities of the hub. I installed a couple pretty large apps from github (echo speaks, DarkSky), along with some of the onboard apps for lighting and HSM, and have created ~20 RM rules so far. Everything seems to be working good.

I didn't even think about demands on the hub itself. Is there anything I need to be aware of about too many apps/devices/rules? ...and is there anything I can do to stay ahead of the power curve or at least know when I'm over-taxing the hub?

Well, the dark-sky driver is quite large but it is not very resource heavy since it doesn't really interact with anything but itself. Echo speaks isn't one that I personally use (I'm a Google Home guy) but others have reported it having a possible link to possible hub slowdowns. But i can't speak to how accurate that is.

There really isn't any need to be worried about it at this point for you but just being aware that some users are having issues is important. As you begin to expand your hub with new automations just be mindful about it and don't add complexity where it isn't necessary. That's all.