Sorry @cben0ist, that doesn’t work. If you tied two slots to the same calendar, events would turn both slots on. Feel free to ask for that as a feature request though!
1 Like
I must be missing something. I installed this and set the slots for 4 codes. I put in the code and left the calendar blank since I want them to always work. All of the slots are showing as unavailable and the codes do not work on the lock.
It would be cool to see this integration support MQTT locks (zigbee2mqtt) zigbee devices never seem to get any support for these cool plugins 
I figured it out. I had reset the lock and didn’t add any codes before I set this up. I thought it would setup the codes for me not just update and sync them. I setup the codes on the physical lock and they synced now.
Not sure what is missing. I installed via HACS and have setup the integration with 5 codes. All appears to be okay from that perspective. The problem arises when I try to create the dashboard. I have created a new dashboard from scratch and copied in the code from the Wiki.
strategy:
type: custom:lock-code-manager
include_code_slot_sensors: true // If set to true, the code slot sensors will be displayed in the UI, otherwise they will be hidden. This setting is optional and defaults to false
After saving I get the following error.
Error loading the dashboard strategy:
No strategy type found
I suspect something didn’t install with the integration but have been unable to determine what that is. I am using HA 2024.6.1 and Lock Code 0.4.6.
Can someone point me in the right direction to fix the error?
I also get the same error after installing and attempting to create the dashboard.
After digging around found the mushroom strategy frontend in HACS. This is the only reference to strategy I found and looks like it might be the missing piece. I loaded that along with the mini-graph frontend as the install directions found in the Wiki. I now get the following error;
Error loading the view strategy:
TypeError: e.pinActiveEntity is undefined
I think this is gettiing closer and will continue to dig around for a solution.
When I bring up the integration after configuring it, it shows no entities. Is this expected or is there a problem with it not creating the entities thus causing the error above.
I’m seeing the same thing here on both 0.5.0 and 0.5.1! The Lock Code Manager integration no longer seems to create the correct components for adding to the UI.
Can you put the integration into debug mode, reload it, and send me the resulting logs?
@raman325 Oops sorry for the delay, here are the relevant ones from creating a new Lock Code Manager
2024-06-18 09:55:12.896 INFO (MainThread) [custom_components.lock_code_manager] cd9b214b876072fe4afb73f82051eaf5 (House Locks): Creating and/or updating entities
2024-06-18 09:55:12.896 DEBUG (MainThread) [custom_components.lock_code_manager] cd9b214b876072fe4afb73f82051eaf5 (House Locks): Adding following locks: ['lock.u_bolt_pro_z_wave_smart_lock']
2024-06-18 09:55:12.896 DEBUG (MainThread) [custom_components.lock_code_manager.helpers] cd9b214b876072fe4afb73f82051eaf5 (House Locks): Created lock instance ZWaveJSLock(domain=zwave_js, lock=lock.u_bolt_pro_z_wave_smart_lock)
2024-06-18 09:55:12.896 DEBUG (MainThread) [custom_components.lock_code_manager] cd9b214b876072fe4afb73f82051eaf5 (House Locks): Creating lock instance for lock ZWaveJSLock(domain=zwave_js, lock=lock.u_bolt_pro_z_wave_smart_lock)
2024-06-18 09:55:12.896 DEBUG (MainThread) [custom_components.lock_code_manager] cd9b214b876072fe4afb73f82051eaf5 (House Locks): Lock lock.u_bolt_pro_z_wave_smart_lock is not connected to Home Assistant yet, waiting 1 seconds before retrying
2024-06-18 09:55:13.898 DEBUG (MainThread) [custom_components.lock_code_manager] cd9b214b876072fe4afb73f82051eaf5 (House Locks): Lock lock.u_bolt_pro_z_wave_smart_lock is not connected to Home Assistant yet, waiting 2 seconds before retrying
2024-06-18 09:55:15.899 DEBUG (MainThread) [custom_components.lock_code_manager] cd9b214b876072fe4afb73f82051eaf5 (House Locks): Lock lock.u_bolt_pro_z_wave_smart_lock is not connected to Home Assistant yet, waiting 4 seconds before retrying
2024-06-18 09:55:19.686 DEBUG (MainThread) [custom_components.lock_code_manager] 5f819289e1fb7ea3831fdde439ce7477 (House Locks): Lock lock.u_bolt_pro_z_wave_smart_lock is not connected to Home Assistant yet, waiting 180 seconds before retrying
2024-06-18 09:55:19.900 DEBUG (MainThread) [custom_components.lock_code_manager] cd9b214b876072fe4afb73f82051eaf5 (House Locks): Lock lock.u_bolt_pro_z_wave_smart_lock is not connected to Home Assistant yet, waiting 8 seconds before retrying
The lock is definitely connected to Home Assistant, as I can lock and unlock it directly using the lock services. It also used to work on a 0.4.x version of Lock Code Manager.
I just opened the manager for the first time in a month or so and everything is blank and showing unavailable. If I go into the Lock Manager Entity configuration the YAML shows my 6 pins. I’ve updated to the latest version and restarted HA, but still same issue?
Also, trying to figure out how to increase the number of pins to add new ones?
Here is the log file as requested. Sorry for the delay, have been out of town an unable to get access to system. Similar results as @ticknert posted. Lock works from within HA with no problem. Entity is lock.backdoor_deadbolt.
2024-06-25 00:16:30.588 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration lock_code_manager which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 00:16:40.457 DEBUG (MainThread) [custom_components.lock_code_manager] Exposed strategy module at /lock_code_manager_files/lock-code-manager-strategy.js
2024-06-25 00:16:40.457 DEBUG (MainThread) [custom_components.lock_code_manager] Strategy module already registered with resource ID d9a4197ef4ee4b9b81436191b63db45d
2024-06-25 00:16:40.457 DEBUG (MainThread) [custom_components.lock_code_manager] Finished setting up websocket API
2024-06-25 00:16:40.458 INFO (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Creating and/or updating entities
2024-06-25 00:16:40.591 DEBUG (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Adding following locks: ['lock.backdoor_deadbolt']
2024-06-25 00:16:40.592 DEBUG (MainThread) [custom_components.lock_code_manager.helpers] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Created lock instance ZWaveJSLock(domain=zwave_js, lock=lock.backdoor_deadbolt)
2024-06-25 00:16:40.592 DEBUG (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Creating lock instance for lock ZWaveJSLock(domain=zwave_js, lock=lock.backdoor_deadbolt)
2024-06-25 00:16:40.592 DEBUG (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Lock lock.backdoor_deadbolt is not connected to Home Assistant yet, waiting 1 seconds before retrying
2024-06-25 00:16:41.593 DEBUG (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Lock lock.backdoor_deadbolt is not connected to Home Assistant yet, waiting 2 seconds before retrying
2024-06-25 00:16:43.594 DEBUG (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Lock lock.backdoor_deadbolt is not connected to Home Assistant yet, waiting 4 seconds before retrying
2024-06-25 00:16:47.596 DEBUG (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Lock lock.backdoor_deadbolt is not connected to Home Assistant yet, waiting 8 seconds before retrying
2024-06-25 00:16:55.598 DEBUG (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Lock lock.backdoor_deadbolt is not connected to Home Assistant yet, waiting 16 seconds before retrying
2024-06-25 00:17:11.600 DEBUG (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Lock lock.backdoor_deadbolt is not connected to Home Assistant yet, waiting 32 seconds before retrying
2024-06-25 00:17:43.600 DEBUG (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Lock lock.backdoor_deadbolt is not connected to Home Assistant yet, waiting 64 seconds before retrying
2024-06-25 00:18:47.601 DEBUG (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Lock lock.backdoor_deadbolt is not connected to Home Assistant yet, waiting 128 seconds before retrying
2024-06-25 00:20:55.602 DEBUG (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Lock lock.backdoor_deadbolt is not connected to Home Assistant yet, waiting 180 seconds before retrying
2024-06-25 00:21:45.540 WARNING (MainThread) [homeassistant.bootstrap] Setup timed out for bootstrap waiting on {<Task pending name='Initial setup for entities for 060455e6754d66150f203ceeca36c8a8' coro=<async_update_listener() running at /config/custom_components/lock_code_manager/__init__.py:418> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>} - moving forward
2024-06-25 00:23:55.604 DEBUG (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Lock lock.backdoor_deadbolt is not connected to Home Assistant yet, waiting 180 seconds before retrying
2024-06-25 00:26:55.605 DEBUG (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Lock lock.backdoor_deadbolt is not connected to Home Assistant yet, waiting 180 seconds before retrying
2024-06-25 00:29:55.607 DEBUG (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Lock lock.backdoor_deadbolt is not connected to Home Assistant yet, waiting 180 seconds before retrying
2024-06-25 00:32:55.608 DEBUG (MainThread) [custom_components.lock_code_manager] 060455e6754d66150f203ceeca36c8a8 (Houe Locks): Lock lock.backdoor_deadbolt is not connected to Home Assistant yet, waiting 180 seconds before retrying
Same issue here unfortunately
I have the same issue as well.
2024-07-16 19:28:41.759 INFO (MainThread) [custom_components.lock_code_manager] 01J2Z3PE7RZD7WB8RV2M1K5AQC (House Locks): Creating and/or updating entities
2024-07-16 19:28:41.759 DEBUG (MainThread) [custom_components.lock_code_manager] 01J2Z3PE7RZD7WB8RV2M1K5AQC (House Locks): Adding following locks: ['lock.front_door_lock', 'lock.garage_door_lock']
2024-07-16 19:28:41.759 DEBUG (MainThread) [custom_components.lock_code_manager] 01J2Z3PE7RZD7WB8RV2M1K5AQC (House Locks): Reusing lock instance for lock ZWaveJSLock(domain=zwave_js, lock=lock.front_door_lock)
2024-07-16 19:28:41.759 DEBUG (MainThread) [custom_components.lock_code_manager] 01J2Z3PE7RZD7WB8RV2M1K5AQC (House Locks): Lock lock.front_door_lock is not connected to Home Assistant yet, waiting 1 seconds before retrying
2024-07-16 19:28:42.761 DEBUG (MainThread) [custom_components.lock_code_manager] 01J2Z3PE7RZD7WB8RV2M1K5AQC (House Locks): Lock lock.front_door_lock is not connected to Home Assistant yet, waiting 2 seconds before retrying
The locks are definitely connected as I can control them via HA.
Apologies all, there is a bug that is rendering the integration unusable. I’m a newly minted father and I have had less time than I expected to work on this but I hope to come back to it soon.
5 Likes
I just tried to add this repo to my HAOS box and it throw an error that the repo wasn’t valid.
The issue is, that this is not an Home Assistant Add-on.
This is a HACS Integration.
- Open HACS
++ Search for “Lock Code Manager”
++ Select the Integration
++ On the bottom right press the Download button
++ On the pop-up download the latest version.
++ Restart Home Assistant
And now it will be available.
1 Like
Trying to attach the config to a dashboard or view, i’m getting general errors stating “Timeout waiting for strategy element ll-strategy-dashboard-lock-code-manager to be registered”
Ultimately facing the same issue mentioned above, any idea if/when this might get resolved so I can give this seemingly awesome integration a run? 
2024-11-11 18:11:33.527 DEBUG (MainThread) [custom_components.lock_code_manager] 01JCEMMNJDV4CVSSQCJCJBH9P1 (House Lock Manager): Lock lock.prosl_key_free_keypad_deadbolt_with_z_wave_plus is not connected to Home Assistant yet, waiting 32 seconds before retrying
2024-11-11 18:11:35.352 INFO (MainThread) [custom_components.lock_code_manager] 01JCEMMNJDV4CVSSQCJCJBH9P1 (House Lock Manager): Creating and/or updating entities
2024-11-11 18:11:35.352 DEBUG (MainThread) [custom_components.lock_code_manager] 01JCEMMNJDV4CVSSQCJCJBH9P1 (House Lock Manager): Adding following locks: ['lock.prosl_key_free_keypad_deadbolt_with_z_wave_plus']
2024-11-11 18:11:35.352 DEBUG (MainThread) [custom_components.lock_code_manager] 01JCEMMNJDV4CVSSQCJCJBH9P1 (House Lock Manager): Reusing lock instance for lock ZWaveJSLock(domain=zwave_js, lock=lock.prosl_key_free_keypad_deadbolt_with_z_wave_plus)
2024-11-11 18:11:35.352 DEBUG (MainThread) [custom_components.lock_code_manager] 01JCEMMNJDV4CVSSQCJCJBH9P1 (House Lock Manager): Lock lock.prosl_key_free_keypad_deadbolt_with_z_wave_plus is not connected to Home Assistant yet, waiting 1 seconds before retrying
2024-11-11 18:11:36.353 DEBUG (MainThread) [custom_components.lock_code_manager] 01JCEMMNJDV4CVSSQCJCJBH9P1 (House Lock Manager): Lock lock.prosl_key_free_keypad_deadbolt_with_z_wave_plus is not connected to Home Assistant yet, waiting 2 seconds before retrying
2024-11-11 18:11:38.354 DEBUG (MainThread) [custom_components.lock_code_manager] 01JCEMMNJDV4CVSSQCJCJBH9P1 (House Lock Manager): Lock lock.prosl_key_free_keypad_deadbolt_with_z_wave_plus is not connected to Home Assistant yet, waiting 4 seconds before retrying
2024-11-11 18:11:42.355 DEBUG (MainThread) [custom_components.lock_code_manager] 01JCEMMNJDV4CVSSQCJCJBH9P1 (House Lock Manager): Lock lock.prosl_key_free_keypad_deadbolt_with_z_wave_plus is not connected to Home Assistant yet, waiting 8 seconds before retrying
2024-11-11 18:11:50.356 DEBUG (MainThread) [custom_components.lock_code_manager] 01JCEMMNJDV4CVSSQCJCJBH9P1 (House Lock Manager): Lock lock.prosl_key_free_keypad_deadbolt_with_z_wave_plus is not connected to Home Assistant yet, waiting 16 seconds before retrying
2024-11-11 18:12:38.359 DEBUG (MainThread) [custom_components.lock_code_manager] 01JCEMMNJDV4CVSSQCJCJBH9P1 (House Lock Manager): Lock lock.prosl_key_free_keypad_deadbolt_with_z_wave_plus is not connected to Home Assistant yet, waiting 64 seconds before retrying
2024-11-11 18:13:09.531 DEBUG (MainThread) [custom_components.lock_code_manager] 01JCEMMNJDV4CVSSQCJCJBH9P1 (House Lock Manager): Lock lock.prosl_key_free_keypad_deadbolt_with_z_wave_plus is not connected to Home Assistant yet, waiting 128 seconds before retrying