With the hot weather we’ve been having lately I have started to use the cooling function of my Vaillant heat pump to shave off a couple of degrees on the hottest of days. As it stands, those cooling cycles are treated as defrosts in the MyHeatPump app and essentially reduce overall heat output and COP. It would be great to have a “Cooling” flag in addition to the CH and DHW flags for the MyHeatPump app. I guess I could internally just set the power to zero for the cooling periods and use a separate instance of the App to look at cooling but it would be very useful to have everything in one app. What are your thoughts on this?
Not yet but I would just use the space heating flag together with outdoor temperature. If it’s more than 15°C outside and there’s still “heating” going on then it must be cooling. Potentially, the 4-way-valve status could also be used on top of that.
Yes, sensor.ebusd_hmu_ebusd_hmu_setmode_releasecooling = 1 when cooling is active. I’m using it to make heat output negative as Vaillant publish it positive for both heating and cooling
+1 for this one too please! Enabled cooling on my Ecodan this morning. I have a flag from Home Assistant to goes 1 when cooling, so could potentially see it working like the the ones for DHW and CH?
I am looking at doing the same and trying to use my_home_circuit_0_state from the myPillant integration for Vaillant. How did you get your flag to work if i may be so bold?
@HannoZ - Sounds like it’s a bit easier for me than you I’m afraid. I get the “Ecodan System Operation Mode” from my ASHP controller which returns values like “DHW”, “Heating”, “Cooling”, “Defrost” etc. Home Assistant generates a 0/1 binary sensor for me based on these that goes high when the mode changes to cooling. This is then fed back into EmonCMS via the EmonCMS history integration.
@jamespreedy Thanks. Just found a binary sensor that looks like it would do the same job my_home_circuit_0_cooling_allowed. Will play with that and see what happens.
Cooling allowed will be always 1 when you allow cooling and not just when the cooling is actually running I think. The mypyllant status variables will also have a potentially significant delay as they go through the cloud so that could cause issues.
@Andre_K Yes I believe you are correct. I haven’t looked at time delays yet or played around with this enough to see what happens when one zone is in cooling and another calls for heating. Wanted to see about getting the status into emoncms first - which seems to be ok. Looks like I need a helper to convert the status entity to get emoncms to accept the input.
This separation will be mandatory because it influences the general classification, the production of negative power influencing the COP. We notice it with this system of Italy, Emoncms - app view according to the selection of the number of days taken into account very logically.
but my cooling feed starts around August 22nd.
I tried to upload CSV feed from July 19 but nothing pop up.
Is it because my feed 507700:1:heatpump_cooling () start on
Hello @Ulric if you started the feed initially with august upload that will set the start date. If you clear the feed and upload the July csv first and then the august one that should sort it!
Next step on my list is to integrate cooling in the daily view
Wow this is great! I’ll try it out. Does it detect the whole block of cooling, as initially i get a spike of positive heat, followed by a long block of negative and at the end a positive peak again. Does it matter that the heating flag was always set for this?
:
