-
Notifications
You must be signed in to change notification settings - Fork 17
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
TypeError: Cannot convert undefined or null to object when reading lockKeypadProperties #86
Comments
Message that will be displayed on users' first issue |
I am also seeing this. New install of Homebridge and the plugin. |
I am also seeing the same error. |
This is good to know. I will have to exclude this lock by default. |
I see this error too. I have the standalone lock with no keypad and get this error which causes restart. It was working fine until a couple weeks or so ago. I want to be able to use the lock and don't want to exclude the lock. Any way to fix this? I've tried most of the recent versions of the plugin, and they all have this issue. |
Can we confirm if version 0.5.28 fixes the issue? |
It fixed it for me. I can now add my lock again. |
Describe The Bug:
I have the newer Wyze Lock that has a built-in keypad. I'm not sure if that's significant, but that's the only lock in my Wyze account, and it uses Bluetooth to actually connect to the lock.
When I set this plugin up in Homebridge, and don't exclude the Lock type, the Wyze plugin container keeps restarting indefinitely with the following error:
If I uninstall the plugin, then reinstall it and exclude the "lock" type, it seems to work OK.
To Reproduce:
Expected behavior:
The plugin should fully load instead of crashing and restarting from this error.
Logs:
Plugin Config:
Screenshots:
Environment:
The text was updated successfully, but these errors were encountered: