Open steffenweber opened 6 months ago
If raise data_entry_flow.AbortFlow(error)
is the expected code-flow when a device is already configured then maybe the issue is that Luxtronik catches it in the first place (instead of letting Home Assistant catch and handle it itself)?
First of all, thank you very much for this integration!
I've just migrated from version 2023.03.24 to 2023.11.30-Beta which seems to have worked fine. However, there is one error logged after each Home Assistant startup (I've redacted the
macaddress
):I've searched for other issues mentioning this error:
I've then tried to understand what could be causing this error. This integration's
async_step_dhcp
function calls Home Assistant's function_abort_if_unique_id_configured
which in turn raises anAbortFlow('already_configured')
exception.According to https://developers.home-assistant.io/docs/config_entries_config_flow_handler/#discovery-steps, an
async_step_dhcp
function needs to "make sure that the device is not already set up". Where does Luxtronik2'sasync_step_dhcp
function check this?It seems to me like Luxtronik2 doesn't check whether the device is already configured or not before calling
_abort_if_unique_id_configured
. But maybe I'm wrong?The luxtronik2 entry in my
config/.storage/core.config_entries
file:The luxtronik2 entries in my
config/.storage/core.device_registry
file: