FutureTense / keymaster

Home Assistant integration for managing Z-Wave enabled locks
MIT License
238 stars 44 forks source link

ISSUE: PIN Status stays on "Adding" & Lock and lock, but sees error "Entity not found" #252

Closed nicocoetzee closed 1 year ago

nicocoetzee commented 3 years ago

Describe the bug I installed this via HACS and cannot get it to work properly. The PIN Status stays on "Adding" & Lock and lock, but sees error "Entity not found" and this means non of the user pins are getting registered. I can lock and unlock the lock from Lovelace.

Logs General Server Controls Logs Info Failed connecting to recently alive device at http://192.168.1.4:8091/XD/BO5EBO5E-F00D-F00D-FEED-08DF1F07DE60.xml: UpnpError('Could not find service state table element') 6:48:59 PM – (WARNING) DLNA Digital Media Renderer - message first occurred at 6:19:57 PM and shows up 57 times boltchecked_yeal_deadbolt: Already running 6:42:09 PM – (WARNING) helpers/script.py - message first occurred at 6:42:04 PM and shows up 3 times Unable to find referenced entities timer.keymaster_yeal_deadbolt_autolock 6:27:43 PM – (WARNING) helpers/service.py Template warning: 'int' got invalid input 'unkno' when rendering template '{## This template checks whether the PIN should be considered active based on ##} {## all of the different ways the PIN can be conditionally enabled/disabled ##} {## Get current date and time ##} {% set now = now() %} {## Get current day of week, date (integer yyyymmdd), and time (integer hhmm) ##} {% set current_day = now.strftime('%a')[0:3] | lower %} {% set current_date = now.strftime('%Y%m%d') | int %} {% set current_time = now.strftime('%H%M') | int %} {% set current_timestamp = as_timestamp(now) | int %} {## Get whether date range toggle is enabled as well as start and end date (integer yyyymmdd) ##} {## Determine whether current date is within date range using integer (yyyymmdd) comparison ##} {% set is_date_range_enabled = is_state('input_boolean.daterange_yeal_deadbolt_4', 'on') %} {% set start_date = state_attr('input_datetime.start_date_yeal_deadbolt_4', 'timestamp') | int %} {% set end_date = state_attr('input_datetime.end_date_yeal_deadbolt_4', 'timestamp') | int %} {## Only active if within the full datetime range. To get a single day both start and stop times must be set ##} {% set is_in_date_range = (start_date < end_date and current_timestamp >= start_date and current_timestamp <= end_date) %} {## Get current days start and end time (integer hhmm). Assume time range is considered enabled if start time != end time. ##} {## If time range is inclusive, check if current time is between start and end times. If exclusive, check if current time is before start time or after end time. ##} {% set current_day_start_time = (states('input_datetime.' + current_day + '_start_date_yeal_deadbolt_4')[0:5]).replace(':', '') | int %} {% set current_day_end_time = (states('input_datetime.' + current_day + '_end_date_yeal_deadbolt_4')[0:5]).replace(':', '') | int %} {% set is_time_range_enabled = (current_day_start_time != current_day_end_time) %} {% set is_time_range_inclusive = is_state('input_boolean.' + current_day + '_inc_yeal_deadbolt_4', 'on') %} {% set is_in_time_range = ( (is_time_range_inclusive and (current_time >= current_day_start_time and current_time <= current_day_end_time)) or (not is_time_range_inclusive and (current_time < current_day_start_time or current_time > current_day_end_time)) ) %} {## Get whether code slot is active and current day is enabled ##} {% set is_slot_enabled = is_state('input_boolean.enabled_yeal_deadbolt_4', 'on') %} {% set is_current_day_enabled = is_state('input_boolean.' + current_day + '_yeal_deadbolt_4', 'on') %} {## Check if access limit is enabled and if there are access counts left. ##} {% set is_access_limit_enabled = is_state('input_boolean.accesslimit_yeal_deadbolt_4', 'on') %} {% set is_access_count_valid = states('input_number.accesscount_yeal_deadbolt_4') | int > 0 %} {## Code slot is active if slot is enabled + current day is enabled + date range is not enabled or current date is within date range ##} {## + time range is not enabled or current time is within time range (based on include/exclude) + access limit is not enabled or there are more access counts left ##} {{ is_slot_enabled and is_current_day_enabled and (not is_date_range_enabled or is_in_date_range) and (not is_time_range_enabled or is_in_time_range) and (not is_access_limit_enabled or is_access_count_valid) }}' but no default was specified. Currently 'int' will return '0', however this template will fail to render in Home Assistant core 2022.1 6:27:13 PM – (WARNING) helpers/template.py - message first occurred at 6:27:13 PM and shows up 105 times Cannot add automation.keymaster_front_door_lock_unlocked_start_autolock as this would exceed the 150 device limit. Consider using the filter option 6:20:00 PM – (WARNING) HomeKit - message first occurred at 6:20:00 PM and shows up 190 times Discovery for value Value(value_id='14-49-0-UNKNOWN (0x00)') on device 'Motion - Office' (Node(node_id=14)) will be skipped: Value Value(value_id='14-49-0-UNKNOWN (0x00)') has unknown data in the following location: metadata.cc_specific.sensorType. A reinterview of node Node(node_id=14) may correct this issue, but if it doesn't, please report this issue as it may be caused by either an upstream issue with the driver or missing support for this data in the library 6:19:56 PM – (ERROR) Z-Wave JS

Much appreciated.

darrylb83 commented 2 years ago

I believe I resolved this issue through multiple heals and interviews. Noticing properties were missing in 2 of the 3 locks, once I had the properties loaded, all topics/etc, it looks like its working. More to come.

On Tue, Jan 18, 2022 at 11:01 AM Darryl Barney @.***> wrote:

Understood, I'll gather any and all info I can. But I dont have any errors showing in the log.

On Mon, Jan 17, 2022 at 6:53 PM Chris @.***> wrote:

I'd need to see the full error message to accurately tell you what the problem is.

— Reply to this email directly, view it on GitHub https://github.com/FutureTense/keymaster/issues/252#issuecomment-1014960266, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADKNZ4FGJ5HVIZ5ZLHIR3BTUWSTZBANCNFSM5HWZQGJA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

-- Darryl K Barney Jr 407-421-8495

-- Darryl K Barney Jr 407-421-8495

nicocoetzee commented 2 years ago

That's awesome news. Please let us know your steps to get this working.

On Mon, Jan 24, 2022, 06:23 darrylb83 @.***> wrote:

I believe I resolved this issue through multiple heals and interviews. Noticing properties were missing in 2 of the 3 locks, once I had the properties loaded, all topics/etc, it looks like its working. More to come.

On Tue, Jan 18, 2022 at 11:01 AM Darryl Barney @.***> wrote:

Understood, I'll gather any and all info I can. But I dont have any errors showing in the log.

On Mon, Jan 17, 2022 at 6:53 PM Chris @.***> wrote:

I'd need to see the full error message to accurately tell you what the problem is.

— Reply to this email directly, view it on GitHub < https://github.com/FutureTense/keymaster/issues/252#issuecomment-1014960266 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ADKNZ4FGJ5HVIZ5ZLHIR3BTUWSTZBANCNFSM5HWZQGJA

. Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

You are receiving this because you commented.Message ID: @.***>

-- Darryl K Barney Jr 407-421-8495

-- Darryl K Barney Jr 407-421-8495

— Reply to this email directly, view it on GitHub https://github.com/FutureTense/keymaster/issues/252#issuecomment-1020153534, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBGIY4FEBB7HD2UZJ3UVNTUXVOH5ANCNFSM5HWZQGJA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

darrylb83 commented 2 years ago

Purely what was mentioned before.

I tried to 'heal all', but failed. So I healed everything until every (34) devices were "rock solid". In investigating the differences between the 3 Schlage locks, I found that most of my configuration items in ZwaveJS (MQTT gui) were showing as things such as Configuration v0, or Version v0. But on the 1 working lock, they would show as v2, or v3, or what-have you.

So I kept running Re-interview and value refreshes until everything looked proper/complete in comparison (well, relatively complete). I was watching the logs for timeouts or data that wasn't coming back during the interview, and focusing on ensuring those items would get complete.

Note: as most of my network are now 700 series, I am starting to think the Schlage I have are 300 series, which makes distance an issue, and probably related to some failure of the interview. Not to say this has always been my issue, but was at least this time.

On Mon, Jan 24, 2022 at 9:35 AM nicocoetzee @.***> wrote:

That's awesome news. Please let us know your steps to get this working.

On Mon, Jan 24, 2022, 06:23 darrylb83 @.***> wrote:

I believe I resolved this issue through multiple heals and interviews. Noticing properties were missing in 2 of the 3 locks, once I had the properties loaded, all topics/etc, it looks like its working. More to come.

On Tue, Jan 18, 2022 at 11:01 AM Darryl Barney @.***> wrote:

Understood, I'll gather any and all info I can. But I dont have any errors showing in the log.

On Mon, Jan 17, 2022 at 6:53 PM Chris @.***> wrote:

I'd need to see the full error message to accurately tell you what the problem is.

— Reply to this email directly, view it on GitHub <

https://github.com/FutureTense/keymaster/issues/252#issuecomment-1014960266

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/ADKNZ4FGJ5HVIZ5ZLHIR3BTUWSTZBANCNFSM5HWZQGJA

. Triage notifications on the go with GitHub Mobile for iOS <

https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android <

https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

.

You are receiving this because you commented.Message ID: @.***>

-- Darryl K Barney Jr 407-421-8495

-- Darryl K Barney Jr 407-421-8495

— Reply to this email directly, view it on GitHub < https://github.com/FutureTense/keymaster/issues/252#issuecomment-1020153534 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AFBGIY4FEBB7HD2UZJ3UVNTUXVOH5ANCNFSM5HWZQGJA

. Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/FutureTense/keymaster/issues/252#issuecomment-1020165336, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADKNZ4AWJGWLLIIEDBF72ELUXVPUXANCNFSM5HWZQGJA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

-- Darryl K Barney Jr 407-421-8495

firstof9 commented 2 years ago

The BE469 locks should be a 500 series zwave chip.

bkvargyas commented 2 years ago

So I'm having a similar issue with this integration. I've changed over the ZwaveJS2MQTT integration for more debugging. However, from the testing I've done... If you manually entered a code into the keypad when programming it, that code cannot be used anywhere with this integration on ANY slots. Even if you entered the code on slot1 and try to program slot 2 with that same 4 digit pin, it won't work. The only way it seems is to remove all the codes from the keypad OR using the zwave service clear user command.

Brian

firstof9 commented 2 years ago

If you manually entered a code into the keypad when programming it, that code cannot be used anywhere with this integration on ANY slots.

Correct, this is because you can't have the same PIN in a slot. The integration assumes you are using it to completely manage the codes not manually entering codes.

icygame commented 4 months ago

Pity this was closed as it still happens.

I have found that looking at the user code status in zwave js is helpful - usually a code stuck on ‘adding’ in keymaster will show the correct status in zwave js.

restarting the zwave js add-on then results in everything showing correctly .

jessevallaro commented 1 month ago

Just resolved the user code 1&2 issue where it gets stuck at adding by setting the user state to available instead of enabled for those 2 in Zwave JS.

image

Roomba5 commented 4 days ago

zwave_js.clear_lock_usercode

Where did you find this setting in the zwaveJS menu? I have the same issue and cant find where I can set the userid Status you mention above.

firstof9 commented 4 days ago

It's under the User Code command class.