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] lock_code_manager_lock_state_changed event no longer firing #278

Open
inphinitizeit opened this issue Jun 28, 2024 · 4 comments
Open
Labels
bug Something isn't working

Comments

@inphinitizeit
Copy link

What happened?

I'm using the latest 0.5.1 with this blueprint https://community.home-assistant.io/t/lock-management-blueprint/723413

The blueprint depends on lock_code_manager_lock_state_changed which is not being fired when the door is locked/unlocked.

Steps to reproduce the issue

  1. Unlock door

Expected: lock_code_manager_lock_state_changed should be fired with relevant data
Actual: lock_code_manager_lock_state_changed is not fired.
Verified that the lock is reporting state changes correctly in the logbook.

Home Assistant Version

2024.6.4

What version of Lock Code Manager are you running?

0.5.1

Lock make and model

Schlage BE469

Relevant log output

No response

Screenshots

No response

Anything else?

No response

@inphinitizeit inphinitizeit added the bug Something isn't working label Jun 28, 2024
@asucrews
Copy link

asucrews commented Jun 28, 2024

To add more to this, the view strategy seems to be broken as well. could be unrelated
Error loading the view strategy:

TypeError: Cannot read properties of undefined (reading 'entity_id')

@inphinitizeit
Copy link
Author

Something strange is going on, after about an hour, these notifications start firing again.

@inphinitizeit
Copy link
Author

To add more to this, the view strategy seems to be broken as well. could be unrelated Error loading the view strategy:

TypeError: Cannot read properties of undefined (reading 'entity_id')

Seeing this as well

@broyuken
Copy link

I just installed this today, and I am getting the same TypeError.

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

3 participants