So, I’ve been responding in alot of threads so I don’t know if I asked you this: Have you turned debug logging (in logger) on and watched events firing in the log?
Did you ever get anywhere with this. Still looks like alarm_type never updates, but the used code changes, but as you stated only when a new code is entered, so not much to trigger on with this lock if you dont have a lot of different codes being used each day
@david202 did you give up on this or did you ever figure it out? I’m facing the same situation with my BE369 and I’d rather not just simply replace the lock if I don’t have to.
Someone posted some useful templates, automations, etc just the other day on this. I’m using it for my FE599, which is an odd ball lock as well. Bascially it’s a workaround that works pretty great.
Set’s up a sensor using a template that changes based on a timestamp. That is then used to change an input_select. I set this up last night, and it’s working great.
I’m able to basically track if the lock is locked or unlocked and then who unlocked.
1 Like
Yes, I’ve been using a method similar to the other post here - sorry for not responding earlier. It is clunky but works. Here’s my code:
- platform: template
sensors:
test_door_code:
friendly_name: 'Time based FE599 test'
value_template: >-
{% if as_timestamp(now()) - as_timestamp(states.sensor.schlage_fe599gr_wireless_door_lock_alarm_level.last_changed) < 5 and is_state('sensor.schlage_fe599gr_wireless_door_lock_alarm_type', '16') %}
{{ states.sensor.schlage_fe599gr_wireless_door_lock_alarm_level.state }}
{% else %}
0
{% endif %}