KeyMaster Z-Wave lock manager and scheduler

Share your Projects!
402

Sorry, I am using terminal addon on hassos itself to run setup.sh

403

Give the command apk add awk or apk add gawk a try from the terminal addon see what it comes back with.

404

Mostly just curious since I dont have these locks. Can you factory reset via zwave? I know with schalge there are several options you can do via zwave commands.

405

Nope it’s a manual process on the lock itself.

406

Is anyone using the Advanced Options? I had a code set for our house cleaners, that only worked on Wednesday from 9am to 11:30am. However I did a reboot last night and when I go into the lock manager now their code is enabled for everyday. Has anyone else seen this revert back to enabled all the time?

407

What version of Home Assistant?
There was a bug that was fix for this in 0.111.4

408

0.111.4

I can make some changes and then reboot again. I did notice it kept the time values I filled out.

409

ok renabled schedule. Rebooted HA, and when I log back in, the lock is set back to connected and every day is set back to on…

410

That’s odd, the state should restore. Have you tinkered with your recorder settings by chance?

411

Just set to MySql, but I don’t have any issues with other settings keeping their status. I have a number of virtual switches, and input fields that hold value through reboot.

recorder:
  db_url: !secret db_mysql
412

I found the issue. I’ll update this post with how to fix.

You’ll need to modify the <whatever>_lock_manager_#.yaml and remove initial: on from all the days of the week bools:

  sun_frontdoor_1:
    name: 'Sunday'
    initial: on

  mon_frontdoor_1:
    name: 'Monday'
    initial: on

  tue_frontdoor_1:
    name: 'Tuesday'
    initial: on

  wed_frontdoor_1:
    name: 'Wednesday'
    initial: on

  thu_frontdoor_1:
    name: 'Thursday'
    initial: on

  fri_frontdoor_1:
    name: 'Friday'
    initial: on

  sat_frontdoor_1:
    name: 'Saturday'
    initial: on

to

  sun_frontdoor_1:
    name: 'Sunday'

  mon_frontdoor_1:
    name: 'Monday'

  tue_frontdoor_1:
    name: 'Tuesday'

  wed_frontdoor_1:
    name: 'Wednesday'
 
  thu_frontdoor_1:
    name: 'Thursday'

  fri_frontdoor_1:
    name: 'Friday'

  sat_frontdoor_1:
    name: 'Saturday'
2 Likes
413

Ahh yes, that makes a lot of sense. Thanks for digging into that, I will do that later today.

1 Like
414

So that solves it, but shouldn’t the intial: on be removed from the script that generates the yaml files? I mean the function is unusable if you can’t reboot HA and have things keep working.

415

the script only generates when you execute setup.sh so you’re fine for now, but yes, you’d want to modify the file or wait for a PR to fix it in the repo :wink:

1 Like
416

What does that actually do? e.g. you have slot 1 with PIN 1234 and then you change the type to 255 for slot 1, does 1234 (assuming its active) control the deadbolt?

417

It should disable the code from being able to be used.

418

So in this case 1234?

ETA: Part of me wishes they would have spent the extra 20 cents per unit and added memory to handle code slots natively. But if they did that, they’d probably try to attempt to force customers to buy into a subscription model. The holy grail of get rich quick schemes.

1 Like
419

Right it wouldn’t work unless it was also in another slot. These are per slot settings.

420

Do you know if the 6-4 and 4-6 PIN length setting can be changed via code? That could serve as a “delete all codes” function which would work well for what I have in mind.

421

Kwikset locks do not have a PIN length setting, they just take 4-8 length codes. For Schlege according to @ptdalen the 4-6 and 6-4 change wipes ALL codes.