Thanks @F1p I’ll install later and let you know if that solves it.
@F1p unfortunately different errors
2025-11-28 19:37:22.095 ERROR (MainThread) [homeassistant.components.mqtt.climate] Could not parse temperature_state_template from {"QTY":7,"Power":"On","SystemOperationMode":"Hot Water","Zone1OperationMode":"Heating Fixed Flow","Zone2OperationMode":"Heating Fixed Flow","TimerProhibit":"None","Z1ActiveInput":0,"Z2ActiveInput":0,"Z1Setpoint":20.5,"Z2Setpoint":0,"ErrorCode":0,"DHWForce":"Off","Holiday":"Off","HolidayHrs":0,"RC1Input":19.9,"RC2Input":20.5,"RC3Input":20.8,"RC4Input":20.6,"RC5Input":20.1,"RC6Input":19.8,"RC7Input":19.9,"RC8Input":18,"HB_ID":2}
2025-11-28 19:37:22.096 WARNING (MainThread) [homeassistant.components.mqtt.climate] Invalid modes mode: {“QTY”:7,“Power”:“On”,“SystemOperationMode”:“Hot Water”,“Zone1OperationMode”:“Heating Fixed Flow”,“Zone2OperationMode”:“Heating Fixed Flow”,“TimerProhibit”:“None”,“Z1ActiveInput”:0,“Z2ActiveInput”:0,“Z1Setpoint”:20.5,“Z2Setpoint”:0,“ErrorCode”:0,“DHWForce”:“Off”,“Holiday”:“Off”,“HolidayHrs”:0,“RC1Input”:19.9,“RC2Input”:20.5,“RC3Input”:20.8,“RC4Input”:20.6,“RC5Input”:20.1,“RC6Input”:19.8,“RC7Input”:19.9,“RC8Input”:18,“HB_ID”:2}
Ohh could it be the funny character at the end of the state_topic?
Unable to parse JSON 5fd504ak: ‘{“device”:{“identifiers”:“CNRFBridge-5fd504”},“unique_id”:“ashp_cnrf_rc8_5fd504”,“name”:“RC8 Input”,“min”:0,“max”:50,“mode”:“box”,“platform”:“number”,“step”:0.01,“unit_of_measurement”:“°C”,“command_topic”:“Ecodan/CNRF/Command/RC”,“command_template”:“{ ‘type’:‘rc’, ‘action’:8, ‘value’: {{ value }} }”,“state_topic”:“Ecodan/CNRF”,“value_template”:“{{ value_json.RC8Input }}”,“icon”:“mdi:thermometer”,“availability”:{“topic”:“Ecodan/CNRF/LWT”}}’
Could be yes, updated to -h2
I’m just a bit confused as to where these came about..
1 Like
Hello, after the latest 2 updates I have been experiencing a decrease in wifi connection quality and especially much more on/offs during the morning heating. Before it was working better with almost zero to max 1 on/off in heating mode. Same outside temps as the previous days. Anyone else experiencing the same issues? Any tip? Thanks a lot
Plot wifi signal strength.
I upgraded to ESPHome 2025.11.0 - November 2025 - ESPHome - Smart Home Made Simple and it has improved wifi. But it seems worse for you ? Do you have the unit inside or outside the inside unit?
Wifi should remain stable, one disconnect per day is also not okay. So you probably need to spent some time fixing wifi stability.
I believe it’s the latest esphome update as I’m having that issue since then. Unit is outside the machine and never had any disconnection.
The one per day you mentioned referred to the compressor’s on/off. Also the one/offs are much more after updating.
Try an older version if you can pin point which one made it worse. Are you sure it’s not the weather that is different ? Cause I do see defrosts, those are normal when it around -2 .. +3c with high humidity.
what version is this? (nothing has been changed regarding short cycle handling for couple of releases already, so I assume its really the weather difference). No disconnect does not say a lot, wifi signal is a better indicator.
Are you using a wireless thermostat and does the short cycle start after going over room setpoint? Then you might be affected by the reduce to min delta T when setpoint has been reached. What profile are you using?
Ye I’m using a Bticino Smarther 2 to get data from the main room in the house.
Firmware: esp32s3-z1-en-2025-11-29.01 (ESPHome 2025.11.2)
the esphome 2025.11.x releases have been included since 20.04 so its weird that the latest would behave different (regarding network).
As for starts stop, I think you had defrost weather, just monitor the defrost sensor.
New release
- upgrade to esphome 2025.12.0
- AA: Added smart boost to increase comfort. See documentation esphome-ecodan-hp/docs/auto-adaptive.md at main · gekkekoe/esphome-ecodan-hp · GitHub . Default off.
I am working on a custom pcb for the ecodan with proxy and relay ports (to control in1/in6)
Is will be used for the Vrekkie optimizer. More info
1 Like
Hello, I just successfully upgraded my FTC6 from fw 1900 to 2001.
After that most of the sensors are not working anymore: unknown.
Also the server control mode is not set in the FTC6 display but seems it is in the dashboard and the system date is reporting 1900-01-00.
Any clue?
@gekkekoe are you on fw 2001 as well?
Yes, I am on latest firmware. I had no issues when upgrading. Try to power unit off and turn on again.
It seems that it could not connect to heatpump, try to post some logging
Thanks for replying. Did the switch on off twice but still no difference.
What specific log do you need?
just 1 or 2 mins of output, it probably complains about not able to connect. Did you change anything in between the firmware upgrade?
No didn’t change anything, just upgraded the fw .I see this that might be the issue but not sure what to do:
Logger: aioesphomeapi.reconnect_logic
Source: runner.py:289
First occurred: January 16, 2026 at 9:48:16 PM (3 occurrences)
Last logged: 3:29:02 AM
- Can’t connect to ESPHome API for ecodan-heatpump @ 192.168.10.52: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address=‘192.168.10.52’, port=6053))]: [Errno 113] Connect call failed (‘192.168.10.52’, 6053) (SocketAPIError
I did not use esphome in HA, so difficult to get logs.
If I connect directly to the m5 stack s3 lite via webserver the only log I see is:
| 09:27:19 | [W] | [ecodan.component:134] |
|---|
No reply received from the heatpump in the last 2 minutes, going to reconnect...
| 09:27:53 | [D] | [auto_adaptive:362] |
|---|
Zone 1 is not in a fixed flow mode. Exiting.
| 09:28:49 | [W] | [ecodan.component:134] |
|---|
No reply received from the heatpump in the last 2 minutes, going to reconnect...
| 09:30:00 | [W] | [ecodan.component:351] |
|---|
Command timed out. Retrying (attempt 3/30)...[8]
| 09:30:19 | [W] | [ecodan.component:134] |
|---|
No reply received from the heatpump in the last 2 minutes, going to reconnect...
| 09:31:49 | [W] | [ecodan.component:134] |
|---|
No reply received from the heatpump in the last 2 minutes, going to reconnect...
| 09:32:53 | [D] | [auto_adaptive:362] |
|---|
Zone 1 is not in a fixed flow mode. Exiting.
| 09:33:19 | [W] | [ecodan.component:134] |
|---|
No reply received from the heatpump in the last 2 minutes, going to reconnect...
| 09:34:49 | [W] | [ecodan.component:134] |
|---|
No reply received from the heatpump in the last 2 minutes, going to reconnect...
| 09:35:00 | [W] | [ecodan.component:351] |
|---|
Command timed out. Retrying (attempt 4/30)...[12]
| 09:36:19 | [W] | [ecodan.component:134] |
|---|
No reply received from the heatpump in the last 2 minutes, going to reconnect...
| 09:37:49 | [W] | [ecodan.component:134] |
|---|
No reply received from the heatpump in the last 2 minutes, going to reconnect...
| 09:37:53 | [D] | [auto_adaptive:362] |
|---|
Zone 1 is not in a fixed flow mode. Exiting.
is not in a fixed flow mode as it is the ftc6 manual setting
it looks like pins are not correctly configured, did you update to the wrong binary file?
you are running plain atom s3 (no proxy)? Did you also upgrade the atom firmware? if yes what file was used?