Issue with away mode for Atlantic DomesticHotWaterProduction in Overkiz

[jonathanroze]

The problem

Hello,

I am experiencing an issue with integrating my Thermor Malicio 3 water heater into Home Assistant via OverKiz, specifically regarding setting it to 'AWAY' mode. I have successfully integrated the device, but I cannot seem to activate the 'AWAY' mode.

Environment:

Home Assistant Version: 2023.10.3 Device: Thermor Malicio 3 Water Heater

Expected Behavior: The 'AWAY' mode should be activatable via Home Assistant, allowing the water heater to enter a lower power state or standby mode during periods of non-use (such as when on vacation).

Current Behavior: The 'AWAY' mode cannot be activated through Home Assistant. It seems like the integration does not support this mode, or there is an issue in the command or configuration.

Steps to Reproduce:

Integrate Thermor Malicio 3 with Home Assistant via OverKiz. Try to set the device to 'AWAY' mode. The mode does not activate or is not available.

What version of Home Assistant Core has the issue?

2023.10.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @imicknl, @vlebourl, @tetienne, @nyrodev, mind taking a look at this issue as it has been labeled with an integration (overkiz) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `overkiz` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign overkiz` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

overkiz documentation overkiz source _{^{(message by IssueLinks)}}

[pentzlin]

Hi there, I have an issue that is most likely related. If it's not or if someone else is code owner for the respective integration, I'd be grateful to @iMicknl, @vlebourl, @tetienne, @nyroDev or others to direct me to the correct people or place to report the issue. Thank you very much!

I have an Atlantic Explorer Heat-Pump Water Heater, connected to an Atlantic Cozytouch Bridge. The Overkiz integration works as expected (sensor data, boost mode) with the exception of the Away Mode.

The Overkiz inegration provides an entity "number.dhwp_actuator_away_mode_duration" associated with the device "DHWP Actuator" (the actual water heater). The entity is displayed as a slider with selectable values from "0" to "6". Selecting any value does not have any effect on the device (actual mode of the water heater) or the values displayed/selected in the cozytouch app.

When I change the Away Mode on the device panel or in the cozytouch app, the entity in Homeassistant seems to take on the values "off" and "always", respectively (i.e. not numeric values). More profoundly, the cozytouch app seems to apply a different logic to the Away Mode than what the Overkiz integration presents: The Cozytouch app allows activating the Away Mode globally for all connected devices (this is an assumption taken from the app's UI; I only have one device connected, so I can't test that). Also, when activating the AWAY mode, both the app and the device (display panel on the water heater) require selecting a start date and an end-date). Therefore, the entity value range (from 0 to 6) that the Overkiz integration presents does not make sense, unless it is assumed that any setting assumes the current date ("now") as the start date, and that the value "0" represents "Away Mode Off" and the values "1" to "6" represent end dates 1 to 6 days from the current date ("now"). That would be sufficient (but as said, it doesn't work.

Attached are screenshots of the app and the device and entity overview in Homeassistant. Please let me know if I can provide any additional information. Note also that there seem to be several related discussions in various fora that describe this or similar issues dating back to 2020/2021/2022 and partly relating to earlier integrations before Overkiz became an HA core integration.

Thank you very much for your help! Kindly,

[iMicknl]

@jonathanroze @pentzlin can you please add your diagnostics?

1. If your device already shows up in Home Assistant, go to your integrations page and select Overkiz, your hub and the device. Press the 3 dots and select "Download diagnostics. Otherwise, go to your integrations page and select Overkiz. Next to your hub, click the 3 dots and select "Download diagnostics".

2. Attach your diagnostics (JSON file) to this issue by uploading the file in a new comment (drag and drop supported).

[pentzlin]

Thanks for your swift reply @iMicknl ! Find my Overkiz diagnostics file attached. config_entry-overkiz-a52f7cd1de2d0c4c0b193637192676a4.json.txt

[pentzlin]

@iMicknl I have activated and deactivated the Away Mode through the cozytouch App and looked for these events in the Overkiz diagnostics history section. I think I found the events. This might be useful for you. New diagnostics attached. config_entry-overkiz-a52f7cd1de2d0c4c0b193637192676a4.json (1).txt

      "HistoryExecution(id='06f21ac8-0a1b-4481-51dd-23f19f326bf8', event_time=1705218546379, owner=GACOMA_Production_613902, source='mobile:mobile', end_time=1705218547201, effective_start_time=1705218546380, duration=821, label='Cozytouch iOS: 3.7.8 (68) - Stop absence', type='Immediate execution - MANUAL_CONTROL', state=<ExecutionState.COMPLETED: 'COMPLETED'>, failure_type='NO_FAILURE', commands=[HistoryExecutionCommand(device_url=io://****-****-5986/14185534#1, command='setCurrentOperatingMode', rank=0, dynamic=False, state=<ExecutionState.COMPLETED: 'COMPLETED'>, failure_type='NO_FAILURE', parameters=[{'relaunch': 'off', 'absence': 'off'}]), HistoryExecutionCommand(device_url=io://****-****-5986/14185534#1, command='setAwayModeDuration', rank=1, dynamic=False, state=<ExecutionState.COMPLETED: 'COMPLETED'>, failure_type='NO_FAILURE', parameters=[0])], execution_type=<ExecutionType.IMMEDIATE_EXECUTION: 'Immediate execution'>, execution_sub_type=<ExecutionSubType.MANUAL_CONTROL: 'MANUAL_CONTROL'>)",
      "HistoryExecution(id='03429662-0a1b-4481-51dd-23f1bfb7bd9a', event_time=1705156712038, owner=GACOMA_Production_613902, source='mobile:mobile', end_time=1705156712970, effective_start_time=1705156712038, duration=932, label='Cozytouch iOS: 3.7.8 (68) - Absence until 22 January 2024 15 48', type='Immediate execution - MANUAL_CONTROL', state=<ExecutionState.COMPLETED: 'COMPLETED'>, failure_type='NO_FAILURE', commands=[HistoryExecutionCommand(device_url=io://****-****-5986/14185534#1, command='setCurrentOperatingMode', rank=0, dynamic=False, state=<ExecutionState.COMPLETED: 'COMPLETED'>, failure_type='NO_FAILURE', parameters=[{'relaunch': 'off', 'absence': 'on'}]), HistoryExecutionCommand(device_url=io://****-****-5986/14185534#1, command='setAwayModeDuration', rank=1, dynamic=False, state=<ExecutionState.COMPLETED: 'COMPLETED'>, failure_type='NO_FAILURE', parameters=[9])], execution_type=<ExecutionType.IMMEDIATE_EXECUTION: 'Immediate execution'>, execution_sub_type=<ExecutionSubType.MANUAL_CONTROL: 'MANUAL_CONTROL'>)",

[jonathanroze]

Here my diagnostic

config_entry-overkiz-a369d756fdb89bade0d7d04a28721d84.json.txt

And entity

Thanks

[hAMMERlized]

@iMicknl I am facing the exact same issue(s) like @pentzlin with the exact same device. Only thing i can adjust is the water temeperature. No away Mode, no boost mode either eco mode or auto mode etc.

[migube]

HI Same issue for me on Atlantic Waterheater cozytouch.

Also the Eco mode button is failed to call service water_heater/set_opeation_mode.manualEcoActive (or inactive) tx!

[hAMMERlized]

Seems the developer is not interested in solving the issue as this is opened and not touched since months already. Too bad.

[pentzlin]

@hAMMERlized please don't put unfair pressure on the developers of this (and suchlike) integrations. Most work is done pro-bono by integration enthusiasts in their free time. I acknowledge that it is hard work to respond to frequent changes of the hardware manufacturers' APIs and their general unwillingness to support standardisation and open integration. @iMicknl I'm thankful for your pioneer work and I wish I could contribute in any way – let me know if there's something a non-developer / non-coder can do, and I'll spare some time.

[jonathanroze]

@hAMMERlized One of code owners respond few days ago! Please describe your issue and provide diagnostic in order to help them to fix this issue 😃

[iMicknl]

@hAMMERlized at the moment I am the only active contributor to this integration, and very busy with my day-job at the moment. With over 4500 users of the integration, with many different devices (especially these climate devices are hard to use), a lot of issues are created. We have 47 open issues, many that are way older than this issue, and I don't have access to such devices.

TLDR: you will need to wait

[hAMMERlized]

Thanks for the response and info. Keep up the good work.

[migube]

@iMicknl I have activated and deactivated the Away Mode through the cozytouch App and looked for these events in the Overkiz diagnostics history section. I think I found the events. This might be useful for you. New diagnostics attached. config_entry-overkiz-a52f7cd1de2d0c4c0b193637192676a4.json (1).txt

      "HistoryExecution(id='

Hi @iMicknl

Don't think the issue is with the communication to Overkiz?, as if you try to change e.g. Eco mode, the error in debugging is related to:

  File "/usr/src/homeassistant/homeassistant/components/overkiz/water_heater_entities/domestic_hot_water_production.py", line 327, in async_set_operation_mode
    OverkizCommand.SET_DHW_MODE, self.operation_mode_to_overkiz[operation_mode]
                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
KeyError: 'manualEcoActive'

assuming the error is due to a received "manualEcoActive",; while the dictionary expects

OVERKIZ_TO_OPERATION_MODE: dict[str, str] = {
    OverkizCommandParam.MANUAL_ECO_ACTIVE: STATE_ECO,

https://github.com/home-assistant/core/blob/dev/homeassistant/components/overkiz/water_heater_entities/domestic_hot_water_production.py#L11

?

[Jmayormayu]

Hi there, I have an issue that is most likely related. If it's not or if someone else is code owner for the respective integration, I'd be grateful to @iMicknl, @vlebourl, @tetienne, @nyroDev or others to direct me to the correct people or place to report the issue. Thank you very much!

I have an Atlantic Explorer Heat-Pump Water Heater, connected to an Atlantic Cozytouch Bridge. The Overkiz integration works as expected (sensor data, boost mode) with the exception of the Away Mode.

The Overkiz inegration provides an entity "number.dhwp_actuator_away_mode_duration" associated with the device "DHWP Actuator" (the actual water heater). The entity is displayed as a slider with selectable values from "0" to "6". Selecting any value does not have any effect on the device (actual mode of the water heater) or the values displayed/selected in the cozytouch app.

When I change the Away Mode on the device panel or in the cozytouch app, the entity in Homeassistant seems to take on the values "off" and "always", respectively (i.e. not numeric values). More profoundly, the cozytouch app seems to apply a different logic to the Away Mode than what the Overkiz integration presents: The Cozytouch app allows activating the Away Mode globally for all connected devices (this is an assumption taken from the app's UI; I only have one device connected, so I can't test that). Also, when activating the AWAY mode, both the app and the device (display panel on the water heater) require selecting a start date and an end-date). Therefore, the entity value range (from 0 to 6) that the Overkiz integration presents does not make sense, unless it is assumed that any setting assumes the current date ("now") as the start date, and that the value "0" represents "Away Mode Off" and the values "1" to "6" represent end dates 1 to 6 days from the current date ("now"). That would be sufficient (but as said, it doesn't work.

Attached are screenshots of the app and the device and entity overview in Homeassistant. Please let me know if I can provide any additional information. Note also that there seem to be several related discussions in various fora that describe this or similar issues dating back to 2020/2021/2022 and partly relating to earlier integrations before Overkiz became an HA core integration.

Thank you very much for your help! Kindly,

Hello, Thanks you guys for your contributions ! +1 I'm facing exctly the same issue with same device like @pentzlin @hAMMERlize. Here is my contribution with my diagnostic : overkiz-39dd256d9ac08f5a2c3d56be4ff6585c-DHWP Actuator-41a9a92e1f331c0a2e38d0f38a68e50f(2).json

[kilkenny44]

Sale problem for me with thermor malicio 2 Away mode doesn't work Boost mode doesn't work Setting temperature doesn't work Changing operating mode : dosen't work

Seems It is like only readonly

See attach logs For the "Too many requests, try again later." I tried at various hour in the day : it always the same (even in the middle of the night) Hope someone can correct the away mode : this is the most function I need (to use with automations)

home-assistant-overkiz.log overkiz-5d5ac053095f4835304a4ab20dafdfcf-Cozytouch V2-bfef07f23f110916178a5b1158a76fb7.json overkiz-5d5ac053095f4835304a4ab20dafdfcf-DHWP Actuator-5af803daab0d7647998b036cb7f0c04b.json

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[pentzlin]

Hi @iMicknl and others, the issue is still persistent. I have an Atlantic Explorer Heat Pump Water Heater, integrated with the Cozytouch Bridge. HA is up to date. Please find attached the last diagnostics of the "Cozytouch V2" and "DHWP Actuator" Devices in the Overkiz Integration. Note the following error messages in HA when attempting to change the values for the Away Mode or the Boost Mode:

Away Mode: Failed to call service number/set_value. core:TargetTemperatureState is not a float Boost Mode: Failed to call service number/set_value. core:TargetTemperatureState is not a float

overkiz-a52f7cd1de2d0c4c0b193637192676a4-DHWP Actuator-0f2af48ffe0e01695aa51e4471d59e65.json overkiz-a52f7cd1de2d0c4c0b193637192676a4-Cozytouch V2-fb392a0ab379f328cf496323daadf7f8.json

[ALERTua]

114184 is now in stable, and it should have fixed this issue :)

[jonathanroze]

114184 is now in stable, and it should have fixed this issue :)

It doesn't means that it available in production build ?

[anasiot]

114184 is now in stable, and it should have fixed this issue :)

I just installed the 2024 07 HA release and I didn’t see any changes still the same error can you please advise ?