Flow rate sensors same values?
Below 2 sensor entities are showing exactly the same value.
- sensor.luxtronik_######_####_heat_source_flow_rate has attribute: 0173 calculations.ID_WEB_Durchfluss_WQ
- sensor.luxtronik_######_####_heat_amount_flow_rate has attribute: 0155 calculations.ID_WEB_WMZ_Durchfluss
WQ = is the brine/water circuit if I'm correct. What is WMZ, and why are both identical? I was hoping to have the floor heating (HUP?) flow rate as well
Hi,
for me, they don't show exactly the same. Sometimes they are a bit different. (approx. 100 l/min) One is the flow rate out of the heat pumpe (heating circuit). The other, as u said, the brine/ water.
I would expect the heating pump would be something with HUP, not WMZ. And isn't it too much of a coincidence the values for both circuits are nearly identical?
I would expect the heating pump would be something with HUP, not WMZ. And isn't it too much of a coincidence the values for both circuits are nearly identical?
WMZ, from my understanding, means just "Wärmemengenzähler" naming from Luxtronik is not quite good. Actually I guess it is a good sign that both have nearly the same value. This is what the Luxtronik try to achieve. It's just my guess...
Still not sure about this.
In heatpump web interface: VBO is on 0%, HUP 65%. Flow shows 900L/hour.
In HA flow for the 2 sensors of WQ and WMZ show 900L as well:
How can this be if VBO is on 0%?
Yeah. Okay. I see. It looks like this is not okay. I mean I don't have "VBO" in my web interface. For me it's called "Ventil.-BOSUP" but actually I don't have a solution for you. Sry.
@w4iq3 @AJediIAm The HUP shows a percentage. I expect it may match with 241: Percent2("HUP_PWM"), so it indicates the PWM percentage. To me this suggests that different heatpumps may have different HUP-types, so the luxtronik controller does not know the flowrate. It only controls the PWM based on 242: Kelvin("HUP_Temp_Spread_Soll"), 243: Kelvin("HUP_Temp_Spread_Ist"), If there is no calculation in the luxtronik for the flowrate, we cannot add it in the integration. Then I propose to close this issue.