Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ISSUE] don't clear slot and set slot on startup #101

Open
raman325 opened this issue Mar 24, 2024 · 2 comments · Fixed by #126
Open

[ISSUE] don't clear slot and set slot on startup #101

raman325 opened this issue Mar 24, 2024 · 2 comments · Fixed by #126
Labels
bug Something isn't working

Comments

@raman325
Copy link
Owner

What happened?

Every time HA is started with a LCM configuration, if the lock codes are supposed to be set, they are first cleared then set. Might be the same problem in the other direction

Steps to reproduce the issue

...

Home Assistant Version

n/a

What version of Lock Code Manager are you running?

n/a

Lock make and model

No response

Relevant log output

No response

Screenshots

No response

Anything else?

No response

@raman325 raman325 added the bug Something isn't working label Mar 24, 2024
@pdobrien3
Copy link

pdobrien3 commented Mar 26, 2024

plus 1 for this. I use zwavejs notifications for when codes are added and deleted. I am having a hard time dealing with spam notifications every time I restart HAss. Also, if it is possible, with locks that have slots for codes as well as enabling/disabling codes (Kwikset 916s) can you just disable/enable the slot instead of enabling/disabling the slot and deleting/adding the code?

@raman325
Copy link
Owner Author

raman325 commented Apr 5, 2024

still an issue I think

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants