Warning that luxtronik2 Beta 2023.11.30 does not work with HA 2024.10.0

[HAMASTER1]

The user-defined integration “luxtronik2” implements the property “is_aux_heat” or uses the additional heating methods in a subclass of ClimateEntity.

In addition the following warnings are listed after HA restart in system - logs.

1) Could not handle config_flow.async_step_dhcp DhcpServiceInfo(ip='192.168.x.xx', hostname='xx', macaddress='xx') Logger: custom_components.luxtronik2 Source: custom_components/luxtronik2/config_flow.py:268

Traceback (most recent call last):
  File "/config/custom_components/luxtronik2/config_flow.py", line 268, in async_step_dhcp
    await self.async_set_unique_id(coordinator.unique_id)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2275, in async_set_unique_id
    raise data_entry_flow.AbortFlow("already_in_progress")
homeassistant.data_entry_flow.AbortFlow: Flow aborted: already_in_progress

2) Could not handle config_flow.async_step_dhcp DhcpServiceInfo(ip='192.168.x.xx', hostname='xx', macaddress='xx') Logger: custom_components.luxtronik2 Source: custom_components/luxtronik2/config_flow.py:269

Traceback (most recent call last):
  File "/config/custom_components/luxtronik2/config_flow.py", line 269, in async_step_dhcp
    self._abort_if_unique_id_configured()
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2258, in _abort_if_unique_id_configured
    raise data_entry_flow.AbortFlow(error)
homeassistant.data_entry_flow.AbortFlow: Flow aborted: already_configured

3) Could not load visibility visibilities.Unknown_Parameter_357 Logger: custom_components.luxtronik2 Source: custom_components/luxtronik2/coordinator.py:344

4) Visibility 'Unknown_Parameter_357' not found Logger: Luxtronik.Visibilities Source: custom_components/luxtronik2/coordinator.py:427

5) luxtronik2::LuxtronikThermostat implements the is_aux_heat property or uses the auxiliary heater methods in a subclass of ClimateEntity which is deprecated and will be unsupported from Home Assistant 2024.10. Please create a bug report at https://github.com/BenPru/luxtronik/issues Logger: homeassistant.components.climate Source: components/climate/init.py:424 luxtronik2::LuxtronikThermostat implements theis_aux_heatproperty or uses the auxiliary heater methods in a subclass of ClimateEntity which is deprecated and will be unsupported from Home Assistant 2024.10. Please create a bug report at https://github.com/BenPru/luxtronik/issues

6) Entity climate.luxtronik_270404_00_heating (<class 'custom_components.luxtronik2.climate.LuxtronikThermostat'>) implements HVACMode(s): heat, off and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/BenPru/luxtronik/issues Logger: homeassistant.components.climate Source: components/climate/init.py:371 Entity climate.luxtronik_270404_00_heating (<class 'custom_components.luxtronik2.climate.LuxtronikThermostat'>) implements HVACMode(s): heat, off and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/BenPru/luxtronik/issues

8) StrEnum was used from luxtronik2, this is a deprecated alias which will be removed in HA Core 2025.5. Use enum.StrEnum instead, please report it to the author of the 'luxtronik2' custom integration Logger: homeassistant.backports.enum Source: helpers/deprecation.py:197 StrEnum was used from luxtronik2, this is a deprecated alias which will be removed in HA Core 2025.5. Use enum.StrEnum instead, please report it to the author of the 'luxtronik2' custom integration

[rfcdejong]

Same warning here, if not fixed it will prevent us to update to 2024.10 whenever that version is released. Would be nice to see the beta going to release status as well. Works without real issues other than this warning here.

[DrPain911]

+1

[DonPrimo12]

Any update on this? Cant integrate my heat pump until this gets fixed... 😔

[AJediIAm]

I'm pledging a €10 bug bounty to have this fixed.

Hopefully more will join. Even a €1 pledge is a showing of appreciation which hopefully encourages people with knowledge to pick this up. I simply don't have the skills to fix the code myself.

[Guenni9]

Hi @rfcdejong @AJediIAm @DrPain911 @DrPain911 @HAMASTER1 @DonPrimo12 @BenPru @steffenweber

I understand really no word with Pyton. I don't know anything about programming. But I found out, editing Line 8 in the base.py:

from homeassistant.backports.enum import StrEnum

to

from enum import StrEnum

removes this issue😇. I made a backup before editing this line of coarse. After restarting Home Assistant, the warning disappears in the log💪!

Maybe somebody is able to change this in the repository?

[DrPain911]

Well, does this solve the problem or does it only get rid of the notification? 🤣 Since I don’t understand what’s going on there any feedback on what this does is appreciated

[Guenni9]

Hm AFAIK, this should solve the problem and not only suppress the warning.. . Regarding to this, what I found: https://developers.home-assistant.io/blog/2024/04/08/deprecated-backports-and-typing-aliases/

And another one solved a similar issue here: https://github.com/fuatakgun/eufy_security/pull/1147/commits/12d8652c59921709a0e8d116230961ad83e725e9

But maybe, I'm wrong, perhaps anyone else could help better..

[Guenni9]

@HAMASTER1 Ah, me again, I see you are using Beta 2023.11.30. Here I use 2024.01.10-Beta and everything is fine. My post only solves the "StrEnum was used from luxtronik2" issue. I think using the actually beta solves your problem

[Kars-de-Jong]

Any update on this? Cant integrate my heat pump until this gets fixed... 😔

Why not? All these issues are just warnings at this stage. The first deprecation to kick in will be 2024.10. Having said that, I do wonder whether @BenPru is still actively working on this...

[BenPru]

@Kars-de-Jong Yes, I will correct this before HA 2024.10.0 will be realesed. But for now I don't have the time for this. @HAMASTER1, @DonPrimo12 and others: I think the problem is the caching from HACS. Some users doesn't see the latest beta versions and installs old stuff. Perhaps clearing the browser cache could help.

[BenPru]

@HAMASTER1 Regarding "Unknown_Parameter_357": Which firmware version and which heatpump do you use? Is it the latest firmware for your hp? A diagnostic file dump in an issue is always a good idea. See "4 Support Tickets" in documentation.

[AJediIAm]

I wasn't aware of 2024.01.10, so we can upgrade HA 2024.07 while still being able to use this integration.

Bug bounty still stands. This integration saves me a good amount of money and energy. It's only fair to kick some of it back to BenPru and anyone else who keeps making this possible. <3

[rhammen]

@HAMASTER1 Regarding "Unknown_Parameter_357": Which firmware version and which heatpump do you use? Is it the latest firmware for your hp? A diagnostic file dump in an issue is always a good idea. See "4 Support Tickets" in documentation.

Quite likely the same issue as #186 ...

[Guenni9]

@rhammen, @BenPru FYI, I had also the "Unknown_Parameter_357" warning. Only cosmetic, to remove it from the log, I commented it out in the source... I have the very rare, obsolete WWB21 pdf, manual latest firmware WWB1.65. I suppose, this warm water booster doesn't support V0357_SILENT_MODE_TIME_MENU

Maybe it helps?