Arnold-n / P1P2MQTT

Monitor and control Daikin/Rotex (hybrid/Altherma) heat pumps via the 2-wire P1/P2 thermostat interface with an ATmega328P, ESP8266, and electronics. The P1P2Serial library and P1P2Monitor program perform low-level bus operation, the P1P2-bridge-esp8266 program interprets data from/to MQTT supporting Home Assistant MQTT discovery. P1P2Serial may also be used for other Japanese Home Bus System based standards: DIII-NET (F1/F2) bus, Mitsubishi M-Net bus, Toshiba TCC-Link, Hitachi H-link, Panasonic/Sanyo SIII-Net, Haier, York, and others.
Other
326 stars 62 forks source link

Problem set heat temperature #128

Open mochitoju opened 2 months ago

mochitoju commented 2 months ago

Hi there,

i've the "modul" now since 2 month for my Daikin Altherma 3 (new model) and now its the first time to start testing heating. i can not set any heating temperature (Room Room_Heating) above 20,4 degrees. -> "only allowed between 12 and 20,4 degrees"

in cooling i can set temperature till 27 degrees.

anybody who can help? in Daikin Onecta HomeAssistant it would be possible to set the correct temperature till 32 degrees.

gtx, juergen

mochitoju commented 2 months ago

sensor.bridge1_fieldsettings_3_06_a3212_temp_range_room_heating_max = 20.4

so, its obtained from Daikin, but i cannot find where i can change it

Arnold-n commented 2 months ago

Hi Juergen,

You cannot change this value - by coincidence I learned yesterday that some field settings, in particular the stepsize for certain field settings, are not decoded properly on some systems, and I think this is the cause of your problem too.

Can you please share the MQTT reported values of the following 4 (or 8) settings?

P1P2/P/P1P2MQTT/bridge0/F/2/3_06_A3212_Temp_Range_Room_Heating_Max
P1P2/P/P1P2MQTT/bridge0/F/2/3_07_A3211_Temp_Range_Room_Heating_Min
P1P2/P/P1P2MQTT/bridge0/F/2/3_08_A3214_Temp_Range_Room_Cooling_Max
P1P2/P/P1P2MQTT/bridge0/F/2/3_09_A3213_Temp_Range_Room_Cooling_Min
P1P2/P/P1P2MQTT/bridge0/F/4/3_06_A3212_Temp_Range_Room_Heating_Max
P1P2/P/P1P2MQTT/bridge0/F/4/3_07_A3211_Temp_Range_Room_Heating_Min
P1P2/P/P1P2MQTT/bridge0/F/4/3_08_A3214_Temp_Range_Room_Cooling_Max
P1P2/P/P1P2MQTT/bridge0/F/4/3_09_A3213_Temp_Range_Room_Cooling_Min

On my system these report:

P1P2/P/P1P2MQTT/bridge0/F/2/3_06_A3212_Temp_Range_Room_Heating_Max {"val":30.0, "min":18, "max":30, "stepsize":0.5, "bits":"00", "bitsstep":"0x01"}
P1P2/P/P1P2MQTT/bridge0/F/2/3_07_A3211_Temp_Range_Room_Heating_Min {"val":12.5, "min":12, "max":18, "stepsize":0.5, "bits":"00", "bitsstep":"0x01"}
P1P2/P/P1P2MQTT/bridge0/F/2/3_08_A3214_Temp_Range_Room_Cooling_Max {"val":35.0, "min":25, "max":35, "stepsize":0.5, "bits":"00", "bitsstep":"0x01"}
P1P2/P/P1P2MQTT/bridge0/F/2/3_09_A3213_Temp_Range_Room_Cooling_Min {"val":15.0, "min":15, "max":25, "stepsize":0.5, "bits":"00", "bitsstep":"0x01"}

with a stepsize of 0.5C (which is configurable on my system as 0.5C or 1.0C). I think your system has a stepsize of 1.0C (fixed) whereas it seems to be wrongly decoded as 0.2C. I would be interested to see the value of your "bits" and "bitsstep" in these messages to see if they are needed in the field setting decoding.

mochitoju commented 2 months ago

3_06_A3212_Temp_Range_Room_Heating_Max = {"val":20.4, "min":18, "max":20, "stepsize":0.2, "bits":"00", "bitsstep":"0x40"} 3_07_A3211_Temp_Range_Room_Heating_Min = {"val":12.0, "min":12, "max":13, "stepsize":0.2, "bits":"00", "bitsstep":"0x40"} 3_08_A3214_Temp_Range_Room_Cooling_Max = {"val":27.0, "min":25, "max":27, "stepsize":0.2, "bits":"00", "bitsstep":"0x40"} 3_09_A3213_Temp_Range_Room_Cooling_Min = {"val":15.0, "min":15, "max":17, "stepsize":0.2, "bits":"00", "bitsstep":"0x40"}

mochitoju commented 2 months ago

mhm, i think i could change the value to more than 20 in the beginning (also a friend of mine have the same problem) - maybe something changed according a firmware update of Daikin?

Arnold-n commented 2 months ago

Quite possibly - it seems Daikin now uses a mantissa which can be 1.0 which I haven't seen in the past. I am updating the firmware and hope that will solve it.

mochitoju commented 2 months ago

little update.

Arnold-n commented 2 months ago

Seems weird, but I think this happens because the rebuild-mqtt action (with current 0.9.53) will work only for a few minutes (it uses 30 as a best-guess value, while waiting for the real max) before it then changes back to 20.4.

Just mailed you a new firmware 0.9.54, which should solve it. Daikin seems to use 10E-1 instead of 1E0 for certain step sizes.

Arnold-n commented 2 months ago

P1P2MQTT-bridge-v0.9.54rc1-Daikin-E.ino.bin should decode 10E-1 step size correctly.

mochitoju commented 2 months ago

Seems weird, but I think this happens because the rebuild-mqtt action (with current 0.9.53) will work only for a few minutes (it uses 30 as a best-guess value, while waiting for the real max) before it then changes back to 20.4.

Just mailed you a new firmware 0.9.54, which should solve it. Daikin seems to use 10E-1 instead of 1E0 for certain step sizes.

Problem seem to be solved.

P1P2MQTT-bridge-v0.9.54rc1-Daikin-E.ino.bin should decode 10E-1 step size correctly.

is this the same file or a diffferent one/version?

Thank you much for your quick solution!

Arnold-n commented 2 months ago

It's the same, except for the version itself.