[BUG] Daikin-target temp too low in auto-mode about esp32-faikin HOT 36 CLOSED

I'm asking because in my multi-split AC the demand settings of the individual indoor units interfere with each other. The indoor with the lowest setting can limit the heat output from the outdoor unit even if indoor unit is in standby. The Daikin cloud does it's own mess up by pushing "demand" values unidirectional. So I just want to make sure that demand was changed on purpose and not by accident. If the indoor units have still access to the cloud, I recommend turning off the demand setting in the Onecta app for each unit.

from esp32-faikin.

There are some other debug logs that you can get that may explain it.

from esp32-faikin.

If I just add increase my BLE-target temp by 0.5 it behaves normal again by adjusting the daikin temp to 28
Maybe that gives an idea?

I would expect the heating to be slowed down only if the BLE-temp has reached 19 but not already when going beyond 18.5

from esp32-faikin.

Yeh I suspect you need the debug enabled to show what it is playing at. It is close so may be predicting it going in to range.

from esp32-faikin.

I have enabled the debug so where do I find the data? on mqtt?

from esp32-faikin.

Yeh MQTT should show all sorts. One status should have "approaching" and "beyond" and stuff in it.

from esp32-faikin.

As you can see... it does not stay to high daikin target temps long enough to do something about the temp changes in the room. Was there any change in last betas?

from esp32-faikin.

Nothing radical, well not that should have been.

Worth double checking the settings in the new "advanced" tab.

from esp32-faikin.

{"hot":true,"approaching":52,"beyond":0,"samples":400,"period":600,"temp":18.63,"min":18.50,"max":20.00}
(i have set switchtemp to 0.5 again as another unit is doing it fine with these settings)

The approaching seems to behave not correctly or?
Why is samples = 400 ? I do see samples = 1200 on my other faikins

from esp32-faikin.

I can double check the code and maybe add more clarity to that report. Worth watching for a bit and seeing it it makes any more sense.

from esp32-faikin.

Just added 0.5 to the BLE-target (19.5 now) and immediately temps do increase to 28 on daikin-target (as expected)
{"hot":true,"approaching":93,"beyond":0,"samples":518,"period":600,"temp":18.66,"min":19.00,"max":20.50}

from esp32-faikin.

now the automation looks fine (samples etc)
{"hot":true,"approaching":1200,"beyond":0,"samples":1200,"period":600,"temp":18.74,"min":19.00,"max":20.50}

from esp32-faikin.

Just added 0.5 to the BLE-target (19.5 now) and immediately temps do increase to 28 on daikin-target (as expected) {"hot":true,"approaching":93,"beyond":0,"samples":518,"period":600,"temp":18.66,"min":19.00,"max":20.50}

Obviously, you changed the "mode" and gave it a push. In your previous data, temp was above min, now it's below.

from esp32-faikin.

I have found one issue with coolback/coolover may have been wrongly applied, given the defaults this would not have made any difference, but without the defaults, e.g. 0, this might matter. Latest beta fixes.

from esp32-faikin.

Could you check why this is being seen as beyond?
BLE temp is set to 19.5. I would assume that beyond is only when its above temp-max (20)?
Why does it consider 18.75 as beyond? Its not even in te range of 19 to 20 already

{"hot":true,"approaching":569,"beyond":12,"initial-samples":600,"period":600,"temp":18.75,"min":19.00,"max":20.00}

from esp32-faikin.

It uses prediction of temp, and if it is going up it can predict as beyond.

Also that is temp now but beyond, etc, relates to the last 600 seconds.

from esp32-faikin.

ok got it. so that means in the last period it was 12 seconds beyond and 569 in approaching?

from esp32-faikin.

Yes

from esp32-faikin.

Are we any better with latest beta?

from esp32-faikin.

I am not really sure and will monitor a little more
{"hot":true,"approaching":954,"beyond":0,"samples":1200,"period":600,"temp":19.02,"min":19.00,"max":20.00}
and still targetting with daikin temp = 29

from esp32-faikin.

still the same for me. when the min temp is reached the faikin does lower the target daikin-temp too much
{"hot":true,"approaching":963,"beyond":2,"samples":1200,"period":600,"temp":18.88,"min":19.00,"max":20.00}
{"hot":true,"approaching":485,"beyond":0,"initial-samples":600,"period":600,"temp":19.06,"min":19.00,"max":20.00}

target is still 19.5
but just now it has reached 19.05 (BLE) and now faikin only heats with daikin-target of 19.5 which is too low
as home is already 22.5. So this means it will go down on temps now although it only reached the min temp

from esp32-faikin.

why does it stop heating on reaching the min temp only?
It needs to heat until 19.5 and then try to keep this temp coz thats my target.

from esp32-faikin.

Sorry the logic is to aim for the window, reaching min is good enough. There is a thermostat mode now that aims for max and then cools to min. Try that.

from esp32-faikin.

why does it stop heating on reaching the min temp only? It needs to heat until 19.5 and then try to keep this temp coz thats my target.

Please try modifying heatback. Just to see what happens.

from esp32-faikin.

Sorry the logic is to aim for the window, reaching min is good enough. There is a thermostat mode now that aims for max and then cools to min. Try that.

The thermostat toggle on the advanced Page?

from esp32-faikin.

why does it stop heating on reaching the min temp only? It needs to heat until 19.5 and then try to keep this temp coz thats my target.

Please try modifying heatback. Just to see what happens.

Heatback? Thats the lowering Temp once it has reached the target Window Not sure why this should Do anything other than cooling down

from esp32-faikin.

Changed it to this now
tpredictt":0,"tmin":10,"switchtemp":0,"pushtemp":0,"heatback":6,"heatover":6,"coolback":6,"coolover":6,"tmax":31,"tsample":900

from esp32-faikin.

and will check on thermostat mode.
stay tuned tommorrow :-)

from esp32-faikin.

@revk
Could there be a mode in faikin where I only use the BLE temp for the daikin algorithm? Something like faikin-no-auto mode but still use the BLE-temp
e.g. replacing the Home-temp with the BLE-temp so that the Daikin only sees the BLE Temp as Home-temp?
Does that make sense?

from esp32-faikin.

There is no way to send an external reference to the Daikin, sorry. If I could, yes, that would be great.

from esp32-faikin.

@turbolooser
Did you change the "demand" slider on purpose or is your "Wohnzimmer" part of a Multi-Split AC?

from esp32-faikin.

I change range and steps, what do you need, I can change or make a setting.

from esp32-faikin.

@turbolooser Did you change the "demand" slider on purpose or is your "Wohnzimmer" part of a Multi-Split AC?

I have only 1 multisplit with 3 inside units and Wohnzimmer is Part of that

from esp32-faikin.

I know about this behaviour and change the demand control using ha for all units the same

from esp32-faikin.

Thanks,
I did not know that this can now be controlled via HA.
Last time I checked it was only available via MQTT and I started learning Node-Red to use it.

from esp32-faikin.

Thanks, I did not know that this can now be controlled via HA. Last time I checked it was only available via MQTT and I started learning Node-Red to use it.

I am still setting demand control using the altherma hacs addon

from esp32-faikin.