PID I-value not zero eventhough ki=0?

[DocGreg55]

Good day everybody,

I just recently changed from FHEM to HA to control my living room floor heater. The PID-controller is up and running in auto mode with debug switched on. I can now follow the different outputs from the controller to the switch. In order to tune the controlle I have only P activated to kp: 0.005. kd and ki are set to 0. I am scratching my head now why I see PID I-values different from 0?

Looking forward to your comments!

Greg

[Chupaka]

Can you show us?.. Ideally, a graph

[DocGreg55]

[Chupaka]

That's weird, because the only place where PID I is updated in your case is this line:

HASmartThermostat/custom_components/smart_thermostat/pid_controller/__init__.py

Line 219 in 4f2d423

self._integral += self._Ki * self._error * self._dt

Check what's in "Developer Tools -> States" for your thermostat...

[DocGreg55]

See attachment. I am going slightly mad! When I rmanually reset the I-value it is set to 0 but comes back after some time.--Gesendet mit der GMX Mail AppAm 14.01.25, 20:42 schrieb Pavel Skuratovich ***@***.***>: That's weird, because the only place where PID I is updated in your case is this line: https://github.com/ScratMan/HASmartThermostat/blob/4f2d42335885000315704316668dc47d024d5723/custom_components/smart_thermostat/pid_controller/__init__.py#L219 Check what's in "Developer Tools -> States" for your thermostat... —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[ScratMan]

Go to Development tools > states

Find your climate entity using the filter, click on the entity id, and look in the status shown at the top of page to verify the Ki gains is 0.

If no, you can use the set_pid_mode action to set the gains, as updates to yaml file are ignored after initial setup

[DocGreg55]

Adrien,thank you for your help! I tried it out yesterday evening and the ki-value is zero. I have only the kp- value and the controller is oscillating as expected. I will now tune in kd and ki. Just for my curiosity: as a newbie in HA, I assumed that a restart of the configuration.yaml results in a re-read of the amended parameters. This is not the case?Greg--Gesendet mit der GMX Mail AppAm 14.01.25, 22:24 schrieb Adrien Bonnat ***@***.***>: Go to Development tools > states Find your climate entity using the filter, click on the entity id, and look in the status shown at the top of page to verify the Ki gains is 0. If no, you can use the set_pid_mode action to set the gains, as updates to yaml file are ignored after initial setup —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[ScratMan]

Just for my curiosity: as a newbie in HA, I assumed that a restart of the configuration.yaml results in a re-read of the amended parameters. This is not the case?

It depends. The PID gains are restored from HA recorder database when restarted, the values in yaml are only considered at the creation of the climate entity, or if the system can't restore values (database corruption or deletion for example). This has been put in place to allow changing the gains through actions through the UI without requiring to restart HA when tuning the gains.

[DocGreg55]

Thank you for clarification.Now it works out. During tuning, I am running into trouble with the minimum possible i-value. Floor heating is very slow and even with the 0.001 it results in over shooting the set value due to the increasing integral over the long time. I switched the integrator off and accept minor deviations. Again, thank you for your efforts!--Gesendet mit der GMX Mail AppAm 15.01.25, 19:16 schrieb Adrien Bonnat ***@***.***>: Just for my curiosity: as a newbie in HA, I assumed that a restart of the configuration.yaml results in a re-read of the amended parameters. This is not the case? It depends. The PID gains are restored from HA recorder database when restarted, the values in yaml are only considered at the creation of the climate entity, or if the system can't restore values (database corruption or deletion for example). This has been put in place to allow changing the gains through actions through the UI without requiring to restart HA when tuning the gains. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[DocGreg55]

Adrien,I have it now up and running and I am very happy with the accuracy. Next step is a scheduled start and stop of the heating but I failed badly: I used the ui-automization tool which generates the following yaml for start of the heating in the afternoon:alias: Heizung Wohnzimmer andescription: ""triggers:  - trigger: time    at: "16:00:00"conditions: []actions:  - action: smart_thermostat.clear_integral    metadata: {}    data: {}    target:      entity_id: climate.thermostat_single_on_off_heater  - action: smart_thermostat.set_preset_temp    metadata: {}    data:      comfort_temp: 23.5    target:      entity_id: climate.thermostat_single_on_off_heater  - action: smart_thermostat.set_pid_mode    metadata: {}    data:      mode: auto    target:      entity_id: climate.thermostat_single_on_off_heatermode: singleThe log states processing of the code but nothing is happening. Am I damn wrong?Thanks for any kind of advise.Gregor--Gesendet mit der GMX Mail AppAm 15.01.25, 19:16 schrieb Adrien Bonnat ***@***.***>: Just for my curiosity: as a newbie in HA, I assumed that a restart of the configuration.yaml results in a re-read of the amended parameters. This is not the case? It depends. The PID gains are restored from HA recorder database when restarted, the values in yaml are only considered at the creation of the climate entity, or if the system can't restore values (database corruption or deletion for example). This has been put in place to allow changing the gains through actions through the UI without requiring to restart HA when tuning the gains. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[ScratMan]

Your automation sets the temperature requirement of the comfort preset, but it doesn't activate the preset.

If you want to adjust the temperature or select the preset depending on the time or day, I would rather recommend using the scheduler card with the scheduler custom integration.