Describe the bug
Alright, back at home and attempting to use 0.1.0b3
When I add the first lock, everything works as expected.
When I add a child lock I get an error in the config workflow and then it shows "Failed to setup, check logs" on the device on the integration page. Same thing after reloading the device.
I tried deleting devices, integration, and reinstalling. When I set up locks the second time I disabled the advanced date/day fields (thanks to whomever added that option).
Now I get the logs that are below.
Thanks for advancing this project. Excited to see the recent progress. 🤙🏼
Environment (please complete the following information):
- OS: HassOS
- Type of system that HA is running on: Proxmox
- Home Assistant version: 2025.8.2
- Component version: [e.g. 0.1.2]
- Z-Wave integration name: ZwaveJS UI
- Lock make and model: Schlage BE469ZP
Logs
Logger: homeassistant.config_entries
Source: config_entries.py:749
First occurred: 11:10:41 (2 occurrences)
Last logged: 11:10:44
Error setting up entry Dining Room Door for keymaster
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/keymaster/__init__.py", line 168, in async_setup_entry
await generate_lovelace(
...<10 lines>...
)
File "/config/custom_components/keymaster/lovelace.py", line 63, in generate_lovelace
code_slot_dict: MutableMapping[str, Any] = await _generate_child_code_slot_dict(
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
code_slot_num=code_slot_num,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
advanced_date_range=advanced_date_range,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
advanced_day_of_week=advanced_day_of_week,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
TypeError: _generate_child_code_slot_dict() got an unexpected keyword argument 'advanced_date_range'
Logger: homeassistant.config_entries
Source: config_entries.py:749
First occurred: 11:10:41 (16 occurrences)
Last logged: 11:10:44
Error setting up entry Dining Room Door for number
Error setting up entry Dining Room Door for sensor
Error setting up entry Dining Room Door for switch
Error setting up entry Dining Room Door for text
Error setting up entry Dining Room Door for time
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/binary_sensor/__init__.py", line 139, in async_setup_entry
return await hass.data[DATA_COMPONENT].async_setup_entry(entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 219, in async_setup_entry
raise ValueError(
...<2 lines>...
)
ValueError: Config entry Dining Room Door (01K2QENQNRDE9ZAX917WSKT5MT) for keymaster.binary_sensor has already been setup!
Describe the bug
Alright, back at home and attempting to use 0.1.0b3
When I add the first lock, everything works as expected.
When I add a child lock I get an error in the config workflow and then it shows "Failed to setup, check logs" on the device on the integration page. Same thing after reloading the device.
I tried deleting devices, integration, and reinstalling. When I set up locks the second time I disabled the advanced date/day fields (thanks to whomever added that option).
Now I get the logs that are below.
Thanks for advancing this project. Excited to see the recent progress. 🤙🏼
Environment (please complete the following information):
Logs