ISSUE: Creating child lock causes error on automations

[grosejon]

Describe the bug
When creating a child lock, HA shows errors stating that there is a service being called by the automation that doesn't exist.

Environment (please complete the following information):

• OS: DSM 7
• Type of system that HA is running on: Docker on Synology NAS
• Home Assistant version: 2022.10.0
• Hassio/Docker/Core? Docker
• Component version: Not sure what this means
• Z-Wave integration name: Z-Wave JS UI
• Lock make and model: Schlage BE469ZP

Screenshots

[chasebolt]

i just created my first child lock and i am also getting this error.

[firstof9]

Make sure you've done the pre-installation step.

[grosejon]

Thanks! I did follow those steps before proceeding and still received the errors.

[chasebolt]

yup i did as well. i clicked submit on the repairs and it hasn't came back yet 🤷‍♂️

…

On Sun, Oct 9, 2022 at 18:38 grosejon ***@***.***> wrote: Thanks! I did follow those steps before proceeding and still received the errors. — Reply to this email directly, view it on GitHub <#304 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJKSSA6ABJM4B3WHMB45ULWCNXPTANCNFSM6AAAAAARARGNUY> . You are receiving this because you commented.Message ID: ***@***.***>

[Fox350]

I am also getting those automation errors for the override scripts. Thanks

[Fox350]

yup i did as well. i clicked submit on the repairs and it hasn't came back
yet 🤷‍♂️

On Sun, Oct 9, 2022 at 18:38 grosejon @.***> wrote:

Thanks! I did follow those steps before proceeding and still received the
errors.

—
Reply to this email directly, view it on GitHub
#304 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJKSSA6ABJM4B3WHMB45ULWCNXPTANCNFSM6AAAAAARARGNUY
.
You are receiving this because you commented.Message ID:
@.***>

Did your child lock inherit your master lock pin? I doubt it if the automation is not running fine. This only hide the problem.

[grosejon]

Yes my child lock has copied the pins. I haven’t done anything with the errors though because I didn’t want to break anything.

[Gibby]

I encountered the same issue. However, my pins never sync to any of the child locks. Looking at the automations they were never triggered. Even after waiting a day the pins never sync.

[firstof9]

Do the script/automation trace to see why.

[roborobp]

Also getting this error after deleting and recreating my locks (swapped from a zwave 500 to a 800 controller).

the error specifically says it is looking for a service called "script.keymaster_basementdoor_copy_from_parent_1" and cannot find it. i go to the scripts under the automations section and see them listed with the correct name "keymaster_basementdoor_copy_from_parent_1" created 19 min ago.

Are these scripts not registering as a "service" properly? I don't want to use the auto fix because it just removes it from the automation and would break the copy from parent function.

[firstof9]

Check the traceback error in the home-assistant.log

[roborobp]

Not sure if I'm finding what you are looking for but this is in my home-assistant.log when I search for the basementdoor string.

2023-07-16 14:12:33.614 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities timer.keymaster_basementdoor_autolock or it is/they are currently not available

2023-07-16 14:12:33.627 ERROR (MainThread) [homeassistant.components.automation.keymaster_override_parent_basementdoor_1_state_change] keymaster_override_parent_basementdoor_1_state_change: Error executing script. Service not found for call_service at pos 1: Unable to find service script.keymaster_basementdoor_copy_from_parent_1

2023-07-16 14:12:33.628 ERROR (MainThread) [homeassistant.components.automation.keymaster_override_parent_basementdoor_2_state_change] keymaster_override_parent_basementdoor_2_state_change: Error executing script. Service not found for call_service at pos 1: Unable to find service script.keymaster_basementdoor_copy_from_parent_2

2023-07-16 14:12:33.631 ERROR (MainThread) [homeassistant.components.automation.keymaster_override_parent_basementdoor_3_state_change] keymaster_override_parent_basementdoor_3_state_change: Error executing script. Service not found for call_service at pos 1: Unable to find service script.keymaster_basementdoor_copy_from_parent_3

2023-07-16 14:12:33.633 ERROR (MainThread) [homeassistant.components.automation.keymaster_override_parent_basementdoor_4_state_change] keymaster_override_parent_basementdoor_4_state_change: Error executing script. Service not found for call_service at pos 1: Unable to find service script.keymaster_basementdoor_copy_from_parent_4

2023-07-16 14:12:33.634 ERROR (MainThread) [homeassistant.components.automation.keymaster_override_parent_basementdoor_5_state_change] keymaster_override_parent_basementdoor_5_state_change: Error executing script. Service not found for call_service at pos 1: Unable to find service script.keymaster_basementdoor_copy_from_parent_5

2023-07-16 14:12:33.636 ERROR (MainThread) [homeassistant.components.automation.keymaster_override_parent_basementdoor_6_state_change] keymaster_override_parent_basementdoor_6_state_change: Error executing script. Service not found for call_service at pos 1: Unable to find service script.keymaster_basementdoor_copy_from_parent_6

Running trace on the automation that calls the scripts gets me:
Triggered by the state of input_boolean.override_parent_basementdoor_1 at July 16, 2023 at 2:12:33 PM
Script: keymaster_basementdoor_copy_from_parent_1
Stopped because an error was encountered at July 16, 2023 at 2:12:33 PM (runtime: 0.12 seconds)

Unable to find service script.keymaster_basementdoor_copy_from_parent_1

Also went to services and can find the script in there

[safetymonkey]

This is happening to me as well. Another interesting thing is that when Keymaster is in this state it loses the ability to update code slots on the parent lock, it just sittings in "Adding" or "Deleting" forever. After I deleted all the entities created by Keymaster for the child lock (basically removed it from Keymaster) the parent lock started working again.

[YankoIvanov]

I experienced the same exact issue, the "keymaster_override_parent_..." error appeared for each of the code numbers I specified for the lock (e.g. available code slots = 8 errors). Been tracking it down and I was able to narrow it down. I must have changed the name of the parent lock after it was originally created (say back_door_lock to back_door) through the standard CONFIGURATION popup of the back door lock integration. However, that does not seem to update the name somewhere, specifically where child locks take the parent lock name to create their respective scripts.
In other words, after re-generating the scripts for both locks, the child lock was still referencing "back_door_lock", i.e. the old name, in the scripts.

I tested this theory by manually updating the old "back_door_lock" name to the new "back_door" name everywhere it was referenced in the script and that seemed to have worked. I was able to see changes trickle down from the parent lock to the child lock.

Now I will just wipe keymaster out and start from scratch, and avoid renaming locks in keymaster after they've been created.