This repository was archived by the owner on Jan 8, 2024. It is now read-only.
This repository was archived by the owner on Jan 8, 2024. It is now read-only.
Z-Wave Door Lock Logging #24
Description
I can edit the HS Device Type String if need be.
I've moved my Vision door lock from HA back to HS since ozw cannot properly handle the logging records. Somehow it's current record is always one record behind the actual current record. Max stored records on the lock is 50 but since it last hit 50, the new current record is invalid record. I excluded it from ozw, added it to HS and the log record is okay now. No idea what ozw is doing!!!
Anyway, I had a sensor in HA from which I parsed the segments and converted the lock's UTC time to local time. It would be nice to have that back again!
# Door Locks
frontdoor_lock_log_date:
friendly_name: "Frontdoor Lock Log"
value_template: '{{ states.sensor.front_door_lock_logging.attributes["TimeStamp"] | timestamp_custom("%d/%m/%y %H:%M:%S") }}'
frontdoor_lock_log_message:
friendly_name: "Frontdoor Lock Log"
value_template: '{{ states.sensor.front_door_lock_logging.attributes["Value"].split("\t")[1].split(":")[1].strip() }}'
frontdoor_lock_log_user:
friendly_name: "Frontdoor Lock Log"
value_template: '{{ states.sensor.front_door_lock_logging.attributes["Value"].split("\t")[2].split(":")[1].strip() }}'
frontdoor_lock_log_code:
friendly_name: "Frontdoor Lock Log"
value_template: '{{ states.sensor.front_door_lock_logging.attributes["Value"].split("\t")[3].split(":")[1].strip() }}'