[ISSUE] Upgrading....

[MYeager1967]

What happened?

I am currently on 3.3.0 and had to roll back to it after updating to the latest. One lock gets carried in just fine but ther other loses all access to the user codes. Can't even add them back. Any suggestions to get caught up to the current version?

Steps to reproduce the issue

...

Home Assistant Version

2026.6.2

What version of Lock Code Manager are you running?

3.3.0

Lock make and model

Schlage Connect (Z-Wave)

Debug logs (paste)

Debug logs (upload)

No response

Lock Code Manager diagnostics (upload)

No response

Lock integration diagnostics (upload)

No response

Diagnostics (paste)

Browser console logs (paste)

Browser console logs (upload)

No response

Screenshots

No response

Anything else?

No response

[raman325]

is there a difference between the underlying technologies for the locks - like Z-Wave works but Matter doesn't?

and are you saying that the one lock works fine, but the other lock won't work for existing codes or new codes?

last question - can you please share debug logs for the integration(s). I'd need lock code manager as well as the integrations your locks are supported through: https://github.com/raman325/lock_code_manager/wiki/Troubleshooting-Debug-Logs

I may need device diagnostics as well but the first three answers will help a ton

[MYeager1967]

They are both the same lock. I'll try to get more information to you over the weekend but my work schedule is pretty rough. I may try updating one version at a time to see where it breaks. At one point, it simply wouldn't load so I stopped updating. 😐

[raman325]

OK but what's the underlying technology you are using? I assume it's Z-Wave because that's where all the major changes were in 4.0.0. We are discovering some upstream bugs from our users so you might have run into another one.

Take your time, your issue may end up getting addressed by fixing one of the other open issues anyway

[MYeager1967]

Sorry, yes it's z-wave. It's funny because one lock shows up fine where the other doesn't. Rolling back to 3.3.0 returns it to fully functional.

[raman325]

all good, actually I will need the device diagnostics for the logs too at this point because I am digging into zwave-js internals while investigating

[MYeager1967]

Let me know how to get what you need and where to post it and I'll get it when I have a chance.

…

On Fri, Jul 3, 2026, 2:41 PM Raman Gupta ***@***.***> wrote: *raman325* left a comment (raman325/lock_code_manager#1320) <#1320 (comment)> all good, actually I will need the device diagnostics for the logs too at this point because I am digging into zwave-js internals while investigating — Reply to this email directly, view it on GitHub <#1320?email_source=notifications&email_token=ABGBF5VWLTGGIAP5NTOWJM35C746RA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBXHA3DQNZVGY32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4878687567>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGBF5QXPCQ3T7Q3ASTYCJD5C746RAVCNFSNUABFKJSXA33TNF2G64TZHM3DMNRQGAZDGNRQHNEXG43VMU5TINZZG44TOMZWGQ2KC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ABGBF5QER2JPGDSBSFQSVKD5C746RA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBXHA3DQNZVGY32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/ABGBF5XAXR633RUM4LGOJYL5C746RA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBXHA3DQNZVGY32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[MYeager1967]

Upgrading from 3.3.0 to 4.0.0 disabled half of my lock codes... On Sat, Jul 4, 2026 at 12:46 PM Michael Yeager ***@***.***> wrote:

…

Let me know how to get what you need and where to post it and I'll get it when I have a chance. On Fri, Jul 3, 2026, 2:41 PM Raman Gupta ***@***.***> wrote: > *raman325* left a comment (raman325/lock_code_manager#1320) > <#1320 (comment)> > > all good, actually I will need the device diagnostics for the logs too at > this point because I am digging into zwave-js internals while investigating > > — > Reply to this email directly, view it on GitHub > <#1320?email_source=notifications&email_token=ABGBF5VWLTGGIAP5NTOWJM35C746RA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBXHA3DQNZVGY32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4878687567>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABGBF5QXPCQ3T7Q3ASTYCJD5C746RAVCNFSNUABFKJSXA33TNF2G64TZHM3DMNRQGAZDGNRQHNEXG43VMU5TINZZG44TOMZWGQ2KC5QC> > . > Triage notifications, keep track of coding agent tasks and review pull > requests on the go with GitHub Mobile for iOS > <https://github.com/notifications/mobile/ios/ABGBF5QER2JPGDSBSFQSVKD5C746RA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBXHA3DQNZVGY32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> > and Android > <https://github.com/notifications/mobile/android/ABGBF5XAXR633RUM4LGOJYL5C746RA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBXHA3DQNZVGY32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. > Download it today! > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[raman325]

the link for the debug logs is in a previous comment and the device diagnostics is here: https://github.com/raman325/lock_code_manager/wiki/Troubleshooting-Device-Diagnostics

Sorry to hear about your lock codes. They should remain intact if you downgrade again which you can do through HACS.

Unfortunately without logs it's not possible for me to diagnose what's going on. I am hoping that one of the upstream fixes coming from investigating #1307 resolves your issue, but if you get a chance to pull those logs/diagnostics (and you may have to accept some temporary downtime while you do this) then I can confirm.