[ISSUE] "Lock is not connected to Home Assistant yet"

[chelming]

What happened?

I add a lock but no entities ever get created. I'm able to call the lock service and update codes manually and lock/unlock doors, even though the log message says "Lock is not connected to Home Assistant yet."

Steps to reproduce the issue

1. Create new configuration
2. Add locks
3. Add yaml
4. Submit
5. Check logs

Home Assistant Version

2024.7.1

What version of Lock Code Manager are you running?

0.5.1

Lock make and model

Yale Assure

Relevant log output

2024-07-08 16:19:56.745 DEBUG (MainThread) [custom_components.lock_code_manager] Finished setting up websocket API
2024-07-08 16:19:56.749 INFO (MainThread) [custom_components.lock_code_manager] 01J2A01H61QAAC9X1H73XG4KVN (Exterior Locks): Creating and/or updating entities
2024-07-08 16:19:56.762 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'lock_code_manager' calls async_forward_entry_setup for integration, lock_code_manager with title: Exterior Locks and entry_id: 01J2A01H61QAAC9X1H73XG4KVN, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/lock_code_manager/__init__.py, line 368: setup_tasks[platform] = config_entry.async_create_task(, please create a bug report at https://github.com/raman325/lock_code_manager/issues
2024-07-08 16:19:56.789 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration lock_code_manager with title: Exterior Locks and entry_id: 01J2A01H61QAAC9X1H73XG4KVN, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2122, in async_forward_entry_setup
    _report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1175, in _report_non_awaited_platform_forwards
    report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
    _LOGGER.warning(msg, stack_info=True)
2024-07-08 16:19:56.790 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration lock_code_manager with title: Exterior Locks and entry_id: 01J2A01H61QAAC9X1H73XG4KVN, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2122, in async_forward_entry_setup
    _report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1175, in _report_non_awaited_platform_forwards
    report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
    _LOGGER.warning(msg, stack_info=True)
2024-07-08 16:19:56.790 DEBUG (MainThread) [custom_components.lock_code_manager] 01J2A01H61QAAC9X1H73XG4KVN (Exterior Locks): Adding following locks: ['lock.back_door_deadbolt', 'lock.front_door_deadbolt', 'lock.side_door_deadbolt']
2024-07-08 16:19:56.790 DEBUG (MainThread) [custom_components.lock_code_manager.helpers] 01J2A01H61QAAC9X1H73XG4KVN (Exterior Locks): Created lock instance ZWaveJSLock(domain=zwave_js, lock=lock.back_door_deadbolt)
2024-07-08 16:19:56.790 DEBUG (MainThread) [custom_components.lock_code_manager] 01J2A01H61QAAC9X1H73XG4KVN (Exterior Locks): Creating lock instance for lock ZWaveJSLock(domain=zwave_js, lock=lock.back_door_deadbolt)
2024-07-08 16:19:56.790 DEBUG (MainThread) [custom_components.lock_code_manager] 01J2A01H61QAAC9X1H73XG4KVN (Exterior Locks): Lock lock.back_door_deadbolt is not connected to Home Assistant yet, waiting 1 seconds before retrying
2024-07-08 16:19:57.793 DEBUG (MainThread) [custom_components.lock_code_manager] 01J2A01H61QAAC9X1H73XG4KVN (Exterior Locks): Lock lock.back_door_deadbolt is not connected to Home Assistant yet, waiting 2 seconds before retrying
2024-07-08 16:19:59.795 DEBUG (MainThread) [custom_components.lock_code_manager] 01J2A01H61QAAC9X1H73XG4KVN (Exterior Locks): Lock lock.back_door_deadbolt is not connected to Home Assistant yet, waiting 4 seconds before retrying
2024-07-08 16:20:03.795 DEBUG (MainThread) [custom_components.lock_code_manager] 01J2A01H61QAAC9X1H73XG4KVN (Exterior Locks): Lock lock.back_door_deadbolt is not connected to Home Assistant yet, waiting 8 seconds before retrying
2024-07-08 16:20:11.796 DEBUG (MainThread) [custom_components.lock_code_manager] 01J2A01H61QAAC9X1H73XG4KVN (Exterior Locks): Lock lock.back_door_deadbolt is not connected to Home Assistant yet, waiting 16 seconds before retrying
2024-07-08 16:20:27.798 DEBUG (MainThread) [custom_components.lock_code_manager] 01J2A01H61QAAC9X1H73XG4KVN (Exterior Locks): Lock lock.back_door_deadbolt is not connected to Home Assistant yet, waiting 32 seconds before retrying
2024-07-08 16:20:59.799 DEBUG (MainThread) [custom_components.lock_code_manager] 01J2A01H61QAAC9X1H73XG4KVN (Exterior Locks): Lock lock.back_door_deadbolt is not connected to Home Assistant yet, waiting 64 seconds before retrying

Screenshots

No response

Anything else?

No response

[bigjezza]

I've just moved to Home Assistant from a different system, I'm facing this on a Yale Assure lock too. I've tried removing the zwave node and re adding to no avail. Like @chelming I can unluck/lock etc.

[bwarden]

Maybe my notes in #139 (comment) are more relevant here.