Skip to content

Stalled values – Outdoor Temperature (0x20, 0, 105, 2, 1) – but: ONECTA is correct #511

@dexamenos

Description

@dexamenos

Hello,

I am running into another "stalled value" problem (see #75).

My HP is Altherma 3 R ECH2O / Model EHSX04P50EF

I am using Daikin Onecta integration (https://github.com/jwillemsen/daikin_onecta) from @jwillemsen in Home Assistant.

And I am using an ESP32 with ESPAltherma from @raomin. def file Altherma(ERGA E EHSH-X P30-50 E_EF series 04-08kW-ECH2O).h

In the following screenshot, top graph is the Outdoor Temperature, as reported by ONECTA API (sensor.altherma_climatecontrol_outdoor_temperature). Update frequency is once per 20 Minutes. However, I am using a custom python script to fold the Outdoor temperature as reported by ESPAltherma ((0x20, 0, 105, 2, 1)) onto the ONECTA integration entity. I am using MQTT to ATTR. (Yellow curve is weather forecast.)

Bottom graph is actual power consumption from the electricity counter just for the heat pump.

Image

Outdoor temperature stopped to be accurate two days ago! What happened? I stopped the heating, because it is getting warmer now, so just hot water is running. What can you see? The ESPAltherma outdoor temperature stalls, as soon as outdoor unit is turned off, however, ONECTA still knows the correct value (those 20 minute peaks). When hot water is beeing prepared, ESPAltherma sensor is back to the correct value.

Any ideas?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions