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

Strange interaction on UI between Enabled switch and PIN active status #199

Open
kingswindsor opened this issue May 10, 2024 · 3 comments
Open
Labels
bug Something isn't working

Comments

@kingswindsor
Copy link

kingswindsor commented May 10, 2024

What happened?

I have 5 filled slots. let's call them Slots A, B, C D & E.
They are all enabled, but PIN active status for Slot B is Off. All other slots show PIN active as On.

If I disable Slot C it makes the Slot B's PIN active status go from Off to On.

If I re-enable Slot C, it turns Slot C's PIN active to Off

This is an example, it's consistent across all slots. One slot is always inactive unless I disable it, then they are all active. When I enable any slot, it becomes inactive and makes the previously inactive slot active.

Lock function fails when a slot's PIN is inactive, and the PIN drops out of the Code Slot Sensor field. So to get all 5 slots to function, I need to disable the slot with the inactive PIN in order to make the PIN active.

Steps to reproduce the issue

As described in What happened?

Home Assistant Version

2024.5.2

What version of Lock Code Manager are you running?

0.4.6

Lock make and model

Yale Keyless Connected with z-wave module

Relevant log output

None

Screenshots

No response

Anything else?

No response

@kingswindsor kingswindsor added the bug Something isn't working label May 10, 2024
@raman325
Copy link
Owner

is this still an issue on the latest version?

@kingswindsor
Copy link
Author

I’m travelling today, but will check tomorrow. I was also suffering from the other recent issue others were reporting but will re-install from scratch. Thanks for this integration, it’s been great - just what I need.

@kingswindsor
Copy link
Author

is this still an issue on the latest version?

I don't know.

I've tried to check but unfortunately the reinstall of the integration is not working properly. I'm just getting one device but no entities, despite the yaml code detailing more. Similar problem to the closed issue #241?

HA Core 2024.6.3 and LCM 0.5.1 Yale lock with zero-wave module

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

No branches or pull requests

2 participants