Hello anyone who has used or is thinking about using this package. I’ve made some updates to the Yaml and my lock and sensor names. based on feedback, my entities has names that were a bit long. I did not have the time to update my automations to use shorter names, but finally did. If you are using my previous package files, and they are working, I would ignore this post. No real changes other than the entity names.
So if you have a look at the latest github
Some people have asked which files to use, and I get it there are a lot of unneeded files, that I kept in the packages folder to try to account for various configurations. At this point I recommend using these
common_lock_config.yaml - Needed regardless of how many locks you have
and then
back_door_lock.yaml and/or front_door_lock.yaml depending on how many locks you have
if you have an FE599, use the garage door lock.yaml file and edit if needed.
Bottom line if you take the front, back, garage yaml files and put them in your packages folder, and rename your entities accordingly (the names are in shown in the comment of each yaml, but basically lock.front_door, lock.back.door, etc) Overall you need to rename three entities for each lock. One for the lock, and two sensors (alarm type and alarm level). No other editing should need to be done to the lock.yaml files. For the common lock config, the only real editing needed is to remove the unused entities if needed. For example if you only have one lock, remove the few places where there other locks are referenced. It’s pretty minimal editing.
One change I made that works well for me is that I decided to move to a google calendar for lock scheduling. It allows you to be as detailed for a schedule as needed.
Here is my google_calendar.yamls
- cal_id: [email protected]
entities:
- device_id: door_lock_schedule
ignore_availability: true
name: Door Lock Schedule
track: true
- device_id: lock_code_1_schedule
ignore_availability: true
name: Door Code 1 Schedule
track: true
search: "#Door Code 1"
- device_id: lock_code_2_schedule
ignore_availability: true
name: Door Code 2 Schedule
track: true
search: "#Door Code 2"
- device_id: lock_code_3_schedule
ignore_availability: true
name: Door Code 3 Schedule
track: true
search: "#Door Code 3"
- device_id: lock_code_4_schedule
ignore_availability: true
name: Door Code 4 Schedule
track: true
search: "#Door Code 4"
- device_id: lock_code_5_schedule
ignore_availability: true
name: Door Code 5 Schedule
track: true
search: "#Door Code 5"
- device_id: lock_code_6_schedule
ignore_availability: true
name: Door Code 6 Schedule
track: true
search: "#Door Code 6"
- device_id: lock_code_7_schedule
ignore_availability: true
name: Door Code 7 Schedule
track: true
search: "#Door Code 7"
- device_id: lock_code_8_schedule
ignore_availability: true
name: Door Code 8 Schedule
track: true
search: "#Door Code 8"
- device_id: lock_code_9_schedule
ignore_availability: true
name: Door Code 9 Schedule
track: true
search: "#Door Code 9"
- device_id: lock_code_10_schedule
ignore_availability: true
name: Door Code 10 Schedule
track: true
search: "#Door Code 10"
- device_id: lock_code_11_schedule
ignore_availability: true
name: Door Code 11 Schedule
track: true
search: "#Door Code 11"
- device_id: lock_code_12_schedule
ignore_availability: true
name: Door Code 12 Schedule
track: true
search: "#Door Code 12"
- device_id: lock_code_13_schedule
ignore_availability: true
name: Door Code 13 Schedule
track: true
search: "#Door Code 13"
- device_id: lock_code_14_schedule
ignore_availability: true
name: Door Code 14 Schedule
track: true
search: "#Door Code 14"
- device_id: lock_code_15_schedule
ignore_availability: true
name: Door Code 15 Schedule
track: true
search: "#Door Code 15"
I’m not going to go into details on how to set up the integration, but the way this works is to set up your schedule however you want and have The code slot as the name of the event, for example “Door Code 5”, in google calendar as the event name, will enable and disable the code slot based on whatever schedule you set. Could be one time, every M-F 8-5, every other Sunday, whatever you’d like.
I’ve also set up my lovelace panel to include some conditional settings to that it does not show things that are unneeded. For example if a slot is unused, no need to show all the switches, etc. I am also using the atomic calendar addon (added via HACS) to show the current lock/slot calendar schedules.
The lovelace is in github too. and named packages/lock_lovelace.txt
