Keymaster does not seem to be working anymore. all PIN status say disconnected

[Menz01]

Describe the bug Have had keymaster installed and configured for well over a year or more now. not sure exactly when, but it does not seem to be working anymore. all my code slots say PIN Status is Disconnected. i have tried my pins on my lock and 2 seem to be working while the other 2 code slots are not working at all. debug logs show slots 3 and 4 as being not configured as well when they are configured.

Environment (please complete the following information):

• OS: HassOS
• Type of system that HA is running on: VM
• Home Assistant version: 2024.7.4
• Hassio
• Component version: 0.0.98
• Z-Wave integration name: Zwave
• Lock make and model: Schlage BE469

Logs home-assistant_keymaster_2024-08-06T14-42-08.415Z.log

[Menz01]

can anyone help me find a place to start troubleshooting this??

[firstof9]

Please review https://github.com/FutureTense/keymaster/issues/270 for troubleshooting steps.

[Menz01]

Please review #270 for troubleshooting steps.

mine is not stuck on "deleting" or "adding". mine says "disconnected" and never changes or even tries to change when i enable/disable a PIN

[firstof9]

when you vie w the node in ZwaveJS UI do you see the User Codes V1 command class?

[Menz01]

when you vie w the node in ZwaveJS UI do you see the User Codes V1 command class?

ZwaveJS UI? Isn't that the addon in addon store? I use the built in default ZwaveJS but never added that addon

[Menz01]

Hello??

[firstof9]

Install ZwaveJS UI otherwise you can't really do troubleshooting.

[raman325]

Hello??

Wish we could work through this more quickly but we all have lives, and we are also involved in core integration development, other integration development, etc. If you aren't getting the answers you need, it's most likely because we are distracted working on other issues. You are welcome to comment on a thread to "bump" it but please try to sound less demanding

[Menz01]

Install ZwaveJS UI otherwise you can't really do troubleshooting.

I did try installing it and it didn't show me anything at all. it did not see any of my nodes at all. i followed the directions and when it was done and i opened it there was nothing to see. i rebooted my server as well. i looked at my ZwaveJS integration and everything was still there

Hello??

Wish we could work through this more quickly but we all have lives, and we are also involved in core integration development, other integration development, etc. If you aren't getting the answers you need, it's most likely because we are distracted working on other issues. You are welcome to comment on a thread to "bump" it but please try to sound less demanding

my apologies for sounding demanding. I just felt stressed that this is not working and i cannot manage my lock to my main door of my house anymore. i will try and sound less demanding. thank you for the advice

[firstof9]

I did try installing it and it didn't show me anything at all. it did not see any of my nodes at all. i followed the directions and when it was done and i opened it there was nothing to see. i rebooted my server as well. i looked at my ZwaveJS integration and everything was still there

You'll need to follow the directions here: https://www.home-assistant.io/integrations/zwave_js/#how-do-i-switch-between-the-official-z-wave-js-add-on-and-the-z-wave-js-ui-add-on

[Menz01]

I did try installing it and it didn't show me anything at all. it did not see any of my nodes at all. i followed the directions and when it was done and i opened it there was nothing to see. i rebooted my server as well. i looked at my ZwaveJS integration and everything was still there

You'll need to follow the directions here: https://www.home-assistant.io/integrations/zwave_js/#how-do-i-switch-between-the-official-z-wave-js-add-on-and-the-z-wave-js-ui-add-on

so thank you for that and i was able to get a little farther but now on the page you sent me i am stuck at step 6. i added z-wave back and i unchecked the box for the supervisor but apparantly i do not know the correct address to put in the community add on URL. the default in is not accepted. i tried the IP to my HA and that did not work either

UPDATE i found the correct address and was able to complete the steps. i am able to access the Z-waveJS UI now and i had 5 devices (1 being the controller stick) and now in this new control panel it sees my locy (yay) and the controller stick but the other 3 devices show as unknown

UPDATE 2 i was able to fix the other 3 devices by waking them up manually so now all devices show in the control panel

[Menz01]

when you vie w the node in ZwaveJS UI do you see the User Codes V1 command class?

is this what you were talking about?

[firstof9]

is this what you were talking about?

Yes please make sure entities are shown under User Code v1, if nothing's under that drop down, hit the refresh button.

[Menz01]

is this what you were talking about?

Yes please make sure entities are shown under User Code v1, if nothing's under that drop down, hit the refresh button.

i do see stuff there but when i make a change, for example... if i go to my lovelace dashboard, enable slot 5 and add a name and a pin, it does not change in user code section in the ZwaveJS-UI

[firstof9]

do your user code slots say 'disabled' in ZwaveJS UI?

[Menz01]

no 4 say enabled and the others all say available and code slot 5 shouldn't have anything. here is the zwave-js ui

and here is my lovelace

[firstof9]

Ah horrible schlege locks.

Try using the service call:

  - service: zwave_js.invoke_cc_api
    target:
      entity_id: lock.assure_2_keyless_touch_screen_deadbolt
    data:
      command_class: "99"
      method_name: get
      parameters:
        - 1

And see if your slot 1 goes "connected". Change the entity_id to the entity of your lock.

[Menz01]

Ah horrible schlege locks.

Try using the service call:

  - service: zwave_js.invoke_cc_api
    target:
      entity_id: lock.assure_2_keyless_touch_screen_deadbolt
    data:
      command_class: "99"
      method_name: get
      parameters:
        - 1

And see if your slot 1 goes "connected". Change the entity_id to the entity of your lock.

this did not work or i have something wrong

[Menz01]

i am pretty sure i put the service call in correctly?

[firstof9]

No that was incorrect, put in parameters [ 1 ]

Edit: here's what it looks like in YAML mode:

[Menz01]

ok so i put it in like you said and it ran and i got the green checkmark, however when i look at my lovelace the slot still shows as disconnected

[firstof9]

What are you seeing in the debug logs?

[Menz01]

i honestly do not know how to read these debug logs but here it is if you wouldn't mind looking at it

home-assistant_keymaster_2024-08-25T17-29-42.610Z.log

[firstof9]

2024-08-25 13:29:39.075 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 1
2024-08-25 13:29:39.075 DEBUG (MainThread) [custom_components.keymaster] Work around code in use.
2024-08-25 13:29:39.075 DEBUG (MainThread) [custom_components.keymaster] Utilizing FE599 work around code.
2024-08-25 13:29:39.075 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 2
2024-08-25 13:29:39.075 DEBUG (MainThread) [custom_components.keymaster] Work around code in use.
2024-08-25 13:29:39.076 DEBUG (MainThread) [custom_components.keymaster] Utilizing FE599 work around code.
2024-08-25 13:29:39.076 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 3
2024-08-25 13:29:39.076 DEBUG (MainThread) [custom_components.keymaster] Work around code in use.
2024-08-25 13:29:39.076 DEBUG (MainThread) [custom_components.keymaster] Utilizing FE599 work around code.
2024-08-25 13:29:39.076 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 4 not enabled
2024-08-25 13:29:39.076 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 5
2024-08-25 13:29:39.076 DEBUG (MainThread) [custom_components.keymaster] Work around code in use.
2024-08-25 13:29:39.076 DEBUG (MainThread) [custom_components.keymaster] Utilizing FE599 work around code.

Looks like you should be able to toggle the Enabled toggle then re-enable and it should work.

[Menz01]

Wish I could say that was the case but I toggled the toggle on my Lovelace dashboard and nothing happened

[firstof9]

Try re-generating the package files via the service call:

Then restart HA.

[Menz01]

i really wanted to come back here and report everything was good and working now but its not. all the current slots still say disconnected. however they do work on the lock itself. so i thought maybe the dashboard is just broke so i added a code to slot 4 and tried it on the lock and it did not work. so i am confused now. really don't get why some work and others do not and why the dashboard just doesn't seem to work at all

[firstof9]

Maybe give lock-code-manager a try:

https://github.com/raman325/lock_code_manager

It's like keymaster but lighter, all the heavy lifting is done by the integration rather than scripts/automations/etc.

[Menz01]

Thanks for the suggestion. This integration was one of the first ones I ever installed and has worked flawlessly for a long time. I just don't understand why it stopped

On Mon, Aug 26, 2024, 6:33 PM Chris @.***> wrote:

Maybe give lock-code-manager a try:

https://github.com/raman325/lock_code_manager

It's like keymaster but lighter, all the heavy lifting is done by the integration rather than scripts/automations/etc.

— Reply to this email directly, view it on GitHub https://github.com/FutureTense/keymaster/issues/381#issuecomment-2311223430, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHOXQZ6RESPAD6JOEB4PWCLZTOUM5AVCNFSM6AAAAABMCQA2V6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJRGIZDGNBTGA . You are receiving this because you authored the thread.Message ID: @.***>

[firstof9]

I am unsure as well.

[Menz01]

so i was able to fix this but i actually do not know how i fixed it cause it literally makes no sense at all and when i describe the fix you won't believe me either.

so i was noticing that on my lovelace dashboard that the top badges all worked as expected and i thought that was odd that they worked and the "Enable" button for the PIN did not. so i went into the raw configuration for the dashboard and then copied only the keymaster parts of it (there are other things on my dashboard) and then created a new blank dashboard and in that raw configuration pasted my keymaster to it. i opened that "test" dashboard and all the values were blank (no names, no pins, nothing). so the first thing i did just to test was toggle the enable button on slot 1. and to my surprise the status lit up and then showed connected. i toggled it back and it went back to disconnected

stunned by what i saw, and since i literally changed NOTHING, all i did was copy and paste to a new dashboard i was curious and i went back to my original dashboard and again to my surprise, all my entries that were previously in there were blank, all my names and pins were gone and i never cleared them so i was confused by this. so i put my name back in slot 1 and my pin and then clicked enable and once again to my shock the pin status lit up and it showed connected.

so as you can see i literally did nothing at all. i copied and pasted the code to a new dashboard, played with one toggle and then went back to my original dashboard and re-entered all my values. so i do know how that fixed it but somehow it did.

[xyg0t3]

I have two instances or HA. Two separate houses. One system has slots stuck as disconnected. I attempted running the services and scripts to no avail. Finally what worked for me was quite simple. In KeyMaster

1. Advanced - Reset Code Slot
2. Enable Slot with no name/PIN
3. Disable Slot
4. Enter Name/PIN
5. Enable slot

I was able to clear out 12 slots successfully.

[danepowell]

I'm having the same issue, but it hasn't magically solved itself like it apparently did for other folks. The debug logs show that Keymaster is able to read the pins from the lock but there's nothing to indicate that it's even trying to update them when I update them in the UI:

2024-09-25 14:35:18.685 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 1 value: 1234
2024-09-25 14:35:18.685 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 2 value: 2345
2024-09-25 14:35:18.685 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 3 value: 3456
2024-09-25 14:35:18.685 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 4 not enabled
2024-09-25 14:35:18.685 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 5 not enabled
2024-09-25 14:35:18.685 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 6 not enabled
2024-09-25 14:35:18.686 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 7 not enabled
2024-09-25 14:35:18.686 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 8 not enabled
2024-09-25 14:35:18.686 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 9 not enabled
2024-09-25 14:35:18.686 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 10 not enabled
2024-09-25 14:35:18.686 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 11 not enabled
2024-09-25 14:35:18.686 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 12 not enabled
2024-09-25 14:35:18.686 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 13 not enabled
2024-09-25 14:35:18.686 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 14 not enabled
2024-09-25 14:35:18.686 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 15 not enabled
2024-09-25 14:35:18.686 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 16 not enabled
2024-09-25 14:35:18.687 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 17 not enabled
2024-09-25 14:35:18.687 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 18 not enabled
2024-09-25 14:35:18.687 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 19 not enabled
2024-09-25 14:35:18.687 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 20 not enabled
2024-09-25 14:35:18.687 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 21 not enabled
2024-09-25 14:35:18.687 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 22 not enabled
2024-09-25 14:35:18.687 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 23 not enabled
2024-09-25 14:35:18.687 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 24 not enabled
2024-09-25 14:35:18.687 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 25 not enabled
2024-09-25 14:35:18.687 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 26 not enabled
2024-09-25 14:35:18.687 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 27 not enabled
2024-09-25 14:35:18.687 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 28 not enabled
2024-09-25 14:35:18.688 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 29 not enabled
2024-09-25 14:35:18.688 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 30 not enabled
2024-09-25 14:35:18.688 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.004 seconds (success: True)

The codes returned here match what's actually on the lock and what's shown in the zwave-js UI under User Code v1.

[danepowell]

I used the zwave-js-ui to make sure all code slots were available and blank and suddenly it started working 🤷