ESPAltherma
ESPAltherma copied to clipboard
Stalled values - was Altherma not send the current value for attributes
Hi All,
I am owner of Altherma LT ERLQ014CAW1 + EHVH16S26CB9W + daikin lan adapter BRP069A62 +
ESPAltherma on board Wemos D1 Mini ESP32.
I have struggle with problem wrong value for some attributes.
Currently I pull below attributes every 30s:
"Operation Mode": "Heating", "Thermostat ON/OFF": "ON", "Defrost Operation": "ON", "Liquid pipe temp.(R6T)": 36.4, "Outdoor air temp.(R1T)": "-8.7", "INV frequency (rps)": 103, "I/U operation mode": "DHW", "BUH Step1": "OFF", "BUH Step2": "OFF", "Water pump operation": "ON", "Leaving water temp. before BUH (R1T)": 43.2, "Leaving water temp. after BUH (R2T)": 42.2, "Inlet water temp.(R4T)": 37.6, "DHW tank temp. (R5T)": 28.4, "Flow sensor (l/min)": 29.6
Unfortunately from time to time some above attributes are not true it seems like like the value freeze.
In above case "Defrost Operation" is ON from few hours
The same situation happen very often for "Outdoor air temp.(R1T)", "Thermostat ON/OFF", rarely for "INV frequency (rps)". Problem occoures even pump is working so it should not be the problem mentioned in issue #28
If someone have any idea what could I try i will do :)
I have the same problem. In my case Outdoor air temp.(R1T) is one of the attributes that freezes. Same with the attribute defrost.
When you have an optional external temp. sensor installed and the ext. unit is in standby mode the data from the external unit are no longer transmitted to the internal unit. This is a power saving feature. You must read the optional sensor instead.
I not use optional external temp sensor, so my problem is not related with power saving feature.
Hmm strange. Can you have a look at the logs when you witness this behaviour?
Logs are posted on MQTT topic: espaltherma/log
You can view them with HA:
Config -> Integration -> MQTT -> Config -> Listen to a topic
This is what you should see:
Hi Raomi, I use mqtt on separate server (not addon in Home Assistant), however I analyzed logs from espaltherma and I have not noticed any difference. Logs looks like the same for working and not working case. I will try to check it again when issue occure and I upload log.
Hi Raomi
Now I have seen the case when INV frequency (rps) freeze.
and logs not show enything unsual
Registers are properly queried, no issue with the checksum. But that's strange that the attribute is not updated! (4 hours ago). Can you listen to "espaltherma/#" and see the content of the message with the all the attributes...?
{"Operation Mode":"Heating","Thermostat ON/OFF":"ON","Defrost Operation":"OFF","Outdoor air temp.(R1T)":"-2.6","INV frequency (rps)":31,"I/U operation mode":"Heating","BUH Step1":"OFF","BUH Step2":"OFF","Water pump operation":"ON","Leaving water temp. before BUH (R1T)":29.3,"Leaving water temp. after BUH (R2T)":28.8,"Inlet water temp.(R4T)":22.9,"DHW tank temp. (R5T)":39.3,"Flow sensor (l/min)":30.3}
{"Operation Mode":"Heating","Thermostat ON/OFF":"ON","Defrost Operation":"OFF","Outdoor air temp.(R1T)":"-2.5","INV frequency (rps)":31,"I/U operation mode":"Heating","BUH Step1":"OFF","BUH Step2":"OFF","Water pump operation":"ON","Leaving water temp. before BUH (R1T)":30.1,"Leaving water temp. after BUH (R2T)":29.7,"Inlet water temp.(R4T)":23.2,"DHW tank temp. (R5T)":39.3,"Flow sensor (l/min)":29.9}
Now my pump is working however INV frequency (rps) is still freezed.
It's weird. ESPAltherma is getting these stuck values from the HP. There is no way that the value is kept from one cycle to the other. Could you check on the HP interface to see if you have stuck values too?
I will check it however I think that in HP panel it did not hangs but we will see.
During last two days I saw problem with defrost information and Outdoor air temp.(R1T) and both are displayed correctly on HP panel.
Today,
I have noticed problem with "Outdoor air temp.(R1T)"
{ "Operation Mode": "Heating", "Thermostat ON/OFF": "ON", "Defrost Operation": "OFF", "Outdoor air temp.(R1T)": 0.8, "INV frequency (rps)": 24, "I/U operation mode": "Heating", "BUH Step1": "OFF", "BUH Step2": "OFF", "Water pump operation": "ON", "Leaving water temp. before BUH (R1T)": 32, "Leaving water temp. after BUH (R2T)": 31.7, "Inlet water temp.(R4T)": 26.7, "DHW tank temp. (R5T)": 42.4, "Flow sensor (l/min)": 12.9 }
OK, same just happened to me with outdoor temperature. Querying of other values is still OK. Temperature on the Altherma's display was displayed correctly (around -5 in the morning). I do read values from Altherma every 30 seconds, what I noticed in the logs is that values are probably updated only when there is a change, so I don't get values every 30 seconds, but since around 8 pm yesterday, there is gap until 7 AM today.
I did unplug ESP from 5V (I power it via Altherma) and let battery discharge for about hour (I found no other way how to reset it?), without any difference. I also tried to upload code to it, again, no change. In MQTT info under espaltherma device in HA, I see MQTT info, but temperature reading is just 0.
The only thing that actually helped me was to cut the power to the Altherma, and restore it back. That helped and I am now getting correct readings. I guess that would mean the issue is not in ESP Altherma, but the serial output from heatpump?
I don't want to mix up things, but today I found out that I was getting no data at all through my M5stickC. I looked at the display and there was no output. Shutting down my daikin and powering it back on resurrected the stick. Pulling 5V pin would probably do the same. Anyone has same experience? Could this be issue with code, M5 or daikin?
Really, the log from ESPAltherma says it's getting this from the Altherma. So I would more go for a bug on the Altherma, or maybe a communication bug between the outdoor unit and the inner one, although, the displayed information should be frozen too... There are firmeware updates available maybe they fix it, @fmode updated his, maybe he can tell a bit more on the process.
Thanks. However what I have experienced today is actually M5StickC being completely turned off (nothing on display, no reaction to buttons) while Altherma was operating fine. Right now, I disconnected 5V from Daikin and hooked it up on USB-C charger, to see if that could fix those occasional strange behavior.
Hi @stomko11, did you have some success with the external charger?
I have experienced 2 types of issues:
- found out that ESP was dead, nothing on the display, while everything works normally on HeatPump. Of course, no values from ESP in HA, as it was dead. Pulling 5V and reinserting it back resurrects M5.
- found out that just external temperature was not updating, all other sensors were updated. M5 seems to operate normally. Disconnecting M5 from 5V, letting it to discharge, and powering it back on from 5V does not bring the value back. I restarted indoor unit and things started to work instantly.
These 2 issues were observed by me ~11 days ago, day or so apart from each other. I can't see how issue number 2 could be related to M5 and looks like issue in the heatpump (although control unit shows correct outdoor temperature). Issue nr.1 could be potentially related to M5 stick, and is also easy to spot as all values I use in HA dashboard just show "unknown" Since then, I have decided to disconnect it from 5V and am powering it now with USB-C charger. So far, so good. But truth is that I am usually running it OK for months. So ask me in a year, I might be able to tell you :)
Hi, I have updated my firmware in Daikin Unit and unfortunately the issue is still exists. Some parmaeters are still freeze in espaltherma. I have also checked that even i restart espaltherma the value which Altherma send to espaltherma are incorret.
@stomko11, just re-thinking at your temp stuck at 0 when it was -5... are you sure your receiving part can read negative values properly?
@mpietrusa Do you still have this issue? Did you manage to get more info on this?
@raomin I read even negative values at other times without any issues.
@stomko11, ok, just found surprising it would stop at 0. BTW, do you still have frozen values with your external charger?
I haven't had issues since then (so far)
@raomin
Unfrotunately yes.
Did you try to use an external power supply like @stomko11?
I actually noticed I still had issues. However I stopped using external temperature from Altherma but use different source, that's why I did not realize. Here are last 2 weeks - there is clearly some issue, even with external power supply.
At the same time as there is flat line for outside temperature, i read and get other updates from altherma (like leaving water temperature, inlet water temperature, etc.)
Did you try to use an external power supply like @stomko11?
No I did not. You know, everythink else works fine. Problem is always on the same attributes: "Outdoor air temp.(R1T)", "Thermostat ON/OFF", rarely for "INV frequency (rps)". From time when I installed my Wemos D1 Mini ESP32 (few months ago) I have not need to restart anything. I remotely restart esp32 by upload new firmware but it did not help. After few hours attributes were reported correctly.
Maybe it need to be from time to time send some magic command that Altherma will know that need to update these attributes. Do you have information how to decode the original service tool from Daikin?
Hi, I just wanted to mention, same issue happening here with outdoor temp.
ERGA08EAV3 + EHVH08S18EJ6V
Same issue here, using an Altherma EHVX16S26CB9W. The MQQT is reporting the same value for hours, and I can see the logs that the ESP is reading the registries without problem (and reporting wrong values).
Maybe the bus needs some kind of reset from time to time.
Temperature also shows flat readings (Left is daikin, right is external sensor independent from Daikin unit):
To those that may or may not experience issues with M5StickC like me. It happened to me ocasionally that I would not get any data from heatpump, discovering M5StickC totally off, blank screen, no reaction to any button. Pulling 5V and reinserting it back restored it. This was the case regardless if I used power from HP or dedicated charger. For me, it started to happen more and more often, even exchanging for another M5StickC did not resolve it. I have recently switched to other ESP32 board and so far, I have not had any outages. I hope it stays that way.