Logic behind automatic control

[MUN0X]

First of all, I really like the idea behind this device.
Especially the auto-mode and the fact that you can couple an external BLE sensor directly to faikin and have faiking calculate a dynamic setpoint for the daikin unit.

For the last few days I have been racking my brain on how I should set this up correctly but the automode seems to have I mind of his own. Can someone help me understand how this works exactly?
I was under the assumption that you would set a setpoint (autot) and a range (autor) and faiking would then just run the AC (in heating) until the max value is reached. Then it would switch the unit off by lowering the calculated setpoint until the temperature drops below the min value again.
This is exactly what I'm after as this would give long and steady "burns" in heating mode which improves the COP (dramatically)!

In practice this does not appear to be the case and the unit just switches on/off rather randomly around the desired temperature.
If i look at the info via mqtt, the automation never goes "beyond".

Is there a way to get the behaviour that I described above?

I figured out how the setpoint value for the AC is calculated and set tpredictt = 0 to disable the prediction stuff.
I played around with the offsets and so on but I cant figure it out.
Edit: I just noticed that the unit started to oscillate around the minimum temperature. Switching heating on when bletemp < min and switching off when bletemp > min. With the BLE sensor reporting with a resolution of 0.01°C this means that this occurs every 30s or so...

(On a sidenote, I also don't understand why push10 is a positive value.)

[revk]

OK, the range is what you want, so it heats when below min, not heating until it hits max. When cooling it cools when above max, not cooling until it hits min. It should not go "beyond" ideally. That probably is some of the confusion. The idea is you are comfortable between min and max. The wider you make that the less heating or cooling needed.

push10 is added to min when heating, and subtracted from `max when cooling.

[MUN0X]

I just had a look at the new code.
I'm not a programmer but I think the issue lies with the state of daiking.thermostat Once the current temperature goes above max, the daiking.thermostat flag starts alternating. This flag is also switched when the min value is crossed.

Would the following fix it?
Inserting the following below line 3027:
if (thermostat && !daikin.thermostat) daikin.thermostat = 1;
Replacing the if statement on line 3030 with:
if (thermostat && (daikin.thermostat &&((hot && current > max) || (!hot && current < min))))

[revk]

I'll take another look.

[revk]

Yeh, not quite, I think I have it now - new code in a few minutes.

[MUN0X]

New code works great! 🥇
Exactly what I wanted and indeed much simpler then what I suggested.

[MUN0X]

Thermostat without prediction offers maximum efficiency.
Enabling prediction will dampen the fluctuations somewhat which could be useful to deal with milder weather.
The original is still there to offer maximum comfort at the expense of some efficiency (especially with multi-splits).

[MUN0X]

Sorry to come back to this but in the meantime I installed Faikins in all of my units.
I've been playing around with the various options for the automatic controls.

Just to confirm? Whats the best way to disable the prediction and advanced automation to just run the basic thermostat functionality?

I see the following lines in the code:
2927 if (tpredicts && !isnan (measured_temp)) ==> tpredicts = 0 to disable prediction?
3041 if (!isnan (measured_temp) && !isnan (min) && !isnan (max) && tsample) ==> tsample = 0 to disable advanced logic?

Is that logic correct or am i overlooking something?

[revk]

There is a thermostat setting. And the prediction stuff all has settings that can be set to zeros.

Maybe I need to write up more on it.

[revk]

OK each of the settings has a description if you look in the Advanced tab in settings on the web control.

Yes, setting some of these to zero stops the prediction logic.