Mismatch in eco temperature for AtlanticElectricalHeaterWithAdjustableTemperatureSetpoint (io:AtlanticElectricalHeaterWithAdjustableTemperatureSetpointIOComponent)

[spanska]

The problem

The Atlantic Heater eco temperature setter is design to take the number of degrees bellow the comfort temperature and not an absolute value despite what is shown on the Atlantic Cozytouch App.

ie :

• if comfort tempature is set to 17.5°C
• we need to send 2.5 to eco temperature endpoint to set eco temperature to 15°C

currently, the overkiz integration doesn't work that way and try to set an absolute value between 6 and 29 to the eco temperature endpoint. Furthemore, the eco temperature getter is also false as shown bellow :

For your information, the eco temperature is set to 15°C in this case in the cozytouch app.

What version of Home Assistant Core has the issue?

2023.1.6

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

Overkiz

Link to integration documentation on our website

https://www.home-assistant.io/integrations/overkiz/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2023-01-20 20:15:21.844 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547209121168] Error handling message: Unknown error (unknown_error) from 176.145.91.18 (Mozilla/5.0 (Linux; Android 11; ONEPLUS A6003 Build/RKQ1.201217.002; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/108.0.5359.128 Mobile Safari/537.36 Home Assistant/2022.12.0-3026 (Android 11; ONEPLUS A6003))
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 27, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 646, in handle_execute_script
    await script_obj.async_run(msg.get("variables"), context=context)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1524, in async_run
    await asyncio.shield(run.async_run())
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 409, in async_run
    await self._async_step(log_exceptions=False)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 453, in _async_step
    self._handle_exception(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 476, in _handle_exception
    raise exception
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 451, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 692, in _async_device_step
    await device_action.async_call_action_from_config(
  File "/usr/src/homeassistant/homeassistant/components/device_automation/action.py", line 76, in async_call_action_from_config
    await platform.async_call_action_from_config(hass, config, variables, context)
  File "/usr/src/homeassistant/homeassistant/components/number/device_action.py", line 62, in async_call_action_from_config
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1755, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1792, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
    await service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 678, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 958, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 715, in _handle_entity_call
    await result
  File "/usr/src/homeassistant/homeassistant/components/number/__init__.py", line 378, in async_set_value
    raise ValueError(
ValueError: Value 3.5 for Eco room temperature is outside valid range 6 - 29

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 Change the title of 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.

_{^{(message by CodeOwnersMention)}}

---

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

[eichenlauba]

Same behavior here.. The eco temperature isn't match between cozytouch app and home assistant.. Here an example : In my coytouch app i have my kitchen heater on eco mode with 17.5°, in home assistant the temperature is 21° ..

[iMicknl]

@eichenlauba please share you diagnostics information. (together with the screenshot, so that the values do match).

[eichenlauba]

here is the diagnostic file: overkiz-fe7bcbf6f6d304fb3798674282057fdf-Radiateur-5da9e9c5939c04159f322ac6136217ca.json.1.txt

[eichenlauba]

Hi! Any news about that?

[spanska]

Hi ! Any news ? :)

[iMicknl]

No news or ETA. If someone could work with me via Discord (iMick#1903) in the coming weeks, I can see if we can speed up a fix for this issue.

[spanska]

Thanks iMicknl ! :) I don't have so many free time at the moment but i could manage to get some in a few weeks (end of August). Would it be good for you to work together during this period ?

[iMicknl]

So it seems that core:EcoRoomTemperatureState is indeed the off-set between core:ComfortRoomTemperatureState and core:EcoRoomTemperatureState. I will need to see how we can implement this. The difficulty here is that for SomfyHeatingTemperatureInterface this same state is used in a normal way...

            {
              "name": "core:ComfortRoomTemperatureState",
              "type": 2,
              "value": 17.5
            },
            {
              "name": "core:EcoRoomTemperatureState",
              "type": 2,
              "value": 2.5
            },

@spanska, besides the number entity that is incorrect, does the climate entity show the right values?

[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.

[spanska]

Still a problem even with the latest home assistant version.

Le lun. 5 févr. 2024, 18:13, issue-triage-workflows[bot] < @.***> a écrit :

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.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/86322#issuecomment-1927504308, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEHIDX6USW3Q6OE4VQSWKETYSEHLBAVCNFSM6AAAAAAUCATKPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRXGUYDIMZQHA . You are receiving this because you were mentioned.Message ID: @.***>

[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.

[spanska]

Still a problem... @iMicknl, Do you think a correction will be available one day ? This integration is not very useful with this bug...