🔥 Advanced Heating Control

[panhans]

In AHCv4 in the scheduler section.
In AHCv5 (current test version) it has an own prominent section.

[jonathanarcher]

@panhans

May you update to the latest version and check your log level. Set it to debug.

Hi, I’d love to do that just don’t know how without setting all my automations up once again. I have the blueprint from the “advanced heating control” repository which is still at that version. The newer one is in the “dev” repository but then I get a different blueprint…

[tco95ttocs (Mario)]

@panhans

But it works. In my test environment I am able to manipulate the climate temperature und sensor temperature and I can see the result in the thermostats temperature directly. Maybe it looks like it doesn’t have any impact because the aggressive mode equalize the new target temperatures a little. You can try to disable generic calibration for one day and compare the graph with the one you’ve posted.

i will try that, but its still strange, because the calibration delta is set to 0,3 and calibration timeout to 5min!

I had a look to the log section and figured out, that there is no log for the calibration with v5!

[panhans]

@jonathanarcher

Hi, I’d love to do that just don’t know how without setting all my automations up once again. I have the blueprint from the “advanced heating control” repository which is still at that version. The newer one is in the “dev” repository but then I get a different blueprint…

You can copy the content of the dev file and paste it in your local blueprint. Then just press c anywhere in home assistant and type automation for reloading the blueprint. But check the config please. Maybe there a some additional selectors.

@tco95ttocs

I had a look to the log section and figured out, that there is no log for the calibration with v5!

Yes, generic calibration runs over the normal set temperature branch. I’ve added some more logging information to the temperature change actions including trigger ids. Trigger ids for calibration or aggressive mode have the these key words in their IDs. Don’t forget to set debug level to warning if you haven’t done yet.

[tco95ttocs (Mario)]

@panhans

Don’t forget to set debug level to warning if you haven’t done yet.

yes that was the mistake in my v5 automation…

[Ohana_Means_family]

Advanced Heating Control

[grafik] I have and now?

What is this supposed to achieve?

[panhans]

@Ohana_Means_family

As I said. I have to know what action call produce the error in your thermostat. So maybe the numbers have the wrong step size or your calibration entity consumes integer only.
In AHC are only 3 service calls. One for calibration, one for setting the hvac mode and one for setting the temperature.
But remember here are a lot more users with your thermostat without any issues who using this blueprint.

@panhans

Disable your automation please. Bring your thermostat to a healthy condition and navigate to the service tab in the developer settings and try to call this command:

action: number.set_value
data:
  value: 21.7
target:
  entity_id: number.thermostat_kuche_og_external_temperature_input

If this produces the error please reset your thermostat again and try it again with 21.5 for the value if this also end in this error try an integer like 21, please.

[stephanschleichstr13]

here the logs:

{ “trace”: { “last_step”: “action/2/default/4/if/condition/0”, "run - Pastebin.com
{ “trace”: { “last_step”: “condition/0/conditions/3”, “run_id”: "e1 - Pastebin.com

[panhans]

Do you also can share the history graph of your thermostat and temperature sensor for the timestamp you’ve taken the trace logs?

[stephanschleichstr13]

Info: @6:30 o’clock we leaved

[panhans]

Yes, it’s the generic calibration. You see the difference of the measured temperature by thermostat and room temperature is around 3°C.

Your target is 18°C. 18°C + 3°C = 21°C. But as you can see the room temperature drops slowly. Just wonder if your radiator is warm at this point. If you want steeper heating curves, you can counteract this with the aggressive mode.

[stephanschleichstr13]

alright, thank you. i will test the aggressive mode

[panhans]

Maybe you go a little lower with the calibration delta, e.g. 0.3

//EDIT:
@ajb538
I’d tested it with v5 (current dev) and did some fixes. Feel free to test but I think I will release it as stable these days.

[CarstenJ (Carsten Jung)]

@panhans

Could you lower the temperature delta and heat up the sensor a little bit, e.g. by holding it in your hands in order to trigger the calibration?

I have now tried everything to trigger the calibration and it just doesn’t do anything:

• I have exchanged my blueprint to the latest dev version
• I have renamed the calibration entity (I’m quite confident that it is in fact the calibration entity) of my Ally so that it is absolutely unique, and then I have put part of this name in the blueprint as calibration keyword, so that there cannot be any confusion
• I have tried several settings, such as covered vs. uncovered mode, manually setting a calibration temperature, using float vs. integer input, etc.
• I reduced calibration timeout to 10 sec. and delta to 0,1 °C, so both are really low and should not prevent calibration. My external temperatures are way more off and sometimes don’t change over several hours.

…but the calibration value just never changes. It stays where I set it manually, without changing - ever.

Unfortunately, in the new AHC sensor that was issued with the dev version, there is no “last_calibration” attribute anymore, so I cannot verify a calibration date, but I assume that would be empty.

Calibration should work also while the scheduler is in Eco, not only during Comfort, right?

Could it be possible that the HA quirk in ZHA for the Allys causes some malfunction of the calibration? How can I make sure that it doesn’t?

Is anybody reading this thread with Danfoss Allys, so that we can compare settings?

Latest trace is here:
https://controlc.com/bb387653

Thank you very much - any help will be much appreciated!

[Ohana_Means_family]

I have now changed the measured room temperature. Is that what you want?

[panhans]

@CarstenJ

Unfortunately, in the new AHC sensor that was issued with the dev version, there is no “last_calibration” attribute anymore, so I cannot verify a calibration date, but I assume that would be empty.

I’ve improved the sensor and updates the dev version. Could you update both and refresh the automations and template entities?

@CarstenJ

Calibration should work also while the scheduler is in Eco, not only during Comfort, right?

Yes

@CarstenJ

Could it be possible that the HA quirk in ZHA for the Allys causes some malfunction of the calibration? How can I make sure that it doesn’t?

Maybe… Could you try to set a calibration value by an action call in dev settings? (Please check your entity_id) The execution button should flash green and after that please verify the entity value has changed to the value in the service call.

Could you also check if the entity consumes integers? Maybe there is something different. I think the person who test with me the calibration last year did use z2m. Maybe the calibration property gets exposed differently.

action: number.set_value
data:
  value: 2100
target:
  entity_id: number.thermostat_bad_externer_temperatursensor_2

//EDIT:
Also check the return value of your manufacturer please. (paste this in your template editor)

{{ device_attr('climate.thermostat_bad_thermostat_2', 'manufacturer') }}

[CarstenJ (Carsten Jung)]

@panhans

Could you try to set a calibration value by an action call in dev settings?

I could not set the calibration value using a four-digit integer “1700”, because that was out of the allowed range (-80 to 35).

But “17” worked and that set the value to 17,0 °C. A floating value was also possible, but it required a dot instead of a comma (17,5 did not work, 17.5 worked).

@panhans

Also check the return value of your manufacturer please.

The return value is: Danfoss

Thanks again!

[panhans]

Ok, thank you. Could you navigate here and filter for your number entity? A screenshot with all attributes would be helpful.

[CarstenJ (Carsten Jung)]

@panhans

A screenshot with all attributes would be helpful.

Sure:

[panhans]

Could you update to the latest version and test again?