Add dhwFlow and centralHeatingFlow

[barryvdh]

I see that dhwFlow and centralHeatingFlow have been added to the portal. Can we add this to this library (and HA).

I think values are added to the model but we need to convert them still to m3/h right?

Not sure what the actual conversion rate is, looking at my very limited I would expect something like the 0-255 value * 0.0275 but don't know if it's linear

[jesperraemaekers]

https://cms.media.wilo.com/cdndoc/wilo429191/4683951/wilo429191.pdf page 15
it is the feedback number. So:
0%: None
1-4%: 0m3/h
5-75%: linear scale from 0 to 2.1m3/h
75-99%: 0m3/h
100%+: None

[barryvdh]

Ok so should we make a flow with m3/h value with None when it's outside that range, or also add the other states?

[jesperraemaekers]

i would put None when the value is 0% or 100%, since those are invalid.
Any percentage that is not in the 'flow' range both bigger than zero and smaller than 100 should represent 0m3/h. I would not add specific states, in terms of flow it is then zero. The percentage may tell you a reason, but that seems out of scope for a flow sensor.

[barryvdh]

Hmm not sure if I do this correctly. I assumed the value was from 0..255, but I guess 255 is just invalid/off, and the value is the actual percentage? Something like this?

    @property
    def dhw_flow_volume(self) -> Union[float, None]:
        """The DHW Flow in m3/h."""
        flow_pwm = self._if_available("dhw_flow")
        print(f'flow_pwm: {flow_pwm}')

        if flow_pwm is None or flow_pwm < 1 or flow_pwm > 100:
            return None

        if flow_pwm < 5 or flow_pwm > 75:
            return 0

        return ((flow_pwm - 5) / 70)  * 2.1

    @property
    def central_heating_flow_volume(self) -> Union[float, None]:
        """The Central Heating Flow in m3/h."""
        flow_pwm = self._if_available("central_heating_flow")
        print(f'flow_pwm: {flow_pwm}')

        if flow_pwm is None or flow_pwm < 1 or flow_pwm > 100:
            return None

        if flow_pwm < 5 or flow_pwm > 75:
            return 0
        
        return ((flow_pwm - 5) / 70)  * 2.1

[kirvis13]

This seems to correspond with the values from the portal and the corresponding JS code.

Oddly: all values seem to be in the percentage value that is in the documentation, except when the pump is turned off. It then returns 255, which corresponds with a PWM signal of 100%.

[kirvis13]

@barryvdh Perhaps you can add a pump status property that is separate from the flow based on the values from the Wilo documentation.

It could include the states "off, standby, running, error" (or be more specific with the error based on the code below).

This could be helpful in detecting errors with the system, but it could also be a choice based on the expected number of support requests if you want to include this in the integration.

    18090: function(e, n, t) {
        t.d(n, {
            b: function() {
                return r
            }
        });
        var o = t(18022)
          , a = t(93343);
        let r = () => {
            let {t: e} = (0,
            o.$G)()
              , n = e => -1 !== e && 0 !== e && 100 !== e;
            return {
                translateCirculationPump: t => {
                    let {activated: o, pwmFlow: r} = t
                      , u = o ? e("common:activated") : e("common:deactivated")
                      , l = "";
                    if (!(0,
                    a.hj)(r) || !n(r))
                        return {
                            value: u,
                            unitOfMeasure: l
                        };
                    if (u = r.toString(),
                    l = "%",
                    2 === r && (u = e("heatPump:log.pwmFlow.standby"),
                    l = "(".concat(r, "%)")),
                    5 === r && (u = e("heatPump:log.pwmFlow.motorBlocked"),
                    l = "(".concat(r, "%)")),
                    r > 5 && r <= 75) {
                        let e = (0,
                        a.ZP)(r).lerp([0, 2.1], [5, 75]);
                        u = (0,
                        a.ZP)(e).toFixedLocale(1),
                        l = "m\xb3/h"
                    }
                    return 80 === r && (u = e("heatPump:log.pwmFlow.runningSuboptimal"),
                    l = "(".concat(r, "%)")),
                    r >= 85 && r <= 90 && (u = e("heatPump:log.pwmFlow.stoppedMomentarily"),
                    l = "(".concat(r, "%)")),
                    95 === r && (u = e("heatPump:log.pwmFlow.stoppedPermanentDamage"),
                    l = "(".concat(r, "%)")),
                    255 === r && (u = e("common:deactivated"),
                    l = ""),
                    {
                        value: u,
                        unitOfMeasure: l
                    }
                }
                ,
                hasPwm: n
            }
        }
    }

[barryvdh]

Flow should be here: #30

[jesperraemaekers]

Thanks barry, I'll tets it as well. I think with the status we're going into the territory that some people might not want than in HA. Maybe we can hide some of the more detailed stuff behind an option that is disabled by default. So we can enable it, but not clutter HA with many entities that are less relevant for the less experienced heat pump owner/ home assistant users.

[erikgeurts]

I see that dhwFlow and centralHeatingFlow have been added to the portal. Can we add this to this library (and HA).

I think values are added to the model but we need to convert them still to m3/h right?

Not sure what the actual conversion rate is, looking at my very limited I would expect something like the 0-255 value * 0.0275 but don't know if it's linear

I'm really pleased to see that new things are being added by Weheat, but meanwhile we've had the Energy logs API out of order for 3 weeks now. Perhaps it would be better if the developers at Weheat spend their precious time fixing what was working before...

[barryvdh]

I see that dhwFlow and centralHeatingFlow have been added to the portal. Can we add this to this library (and HA).
I think values are added to the model but we need to convert them still to m3/h right?
Not sure what the actual conversion rate is, looking at my very limited I would expect something like the 0-255 value * 0.0275 but don't know if it's linear

I'm really pleased to see that new things are being added by Weheat, but meanwhile we've had the Energy logs API out of order for 3 weeks now. Perhaps it would be better if the developers at Weheat spend their precious time fixing what was working before...

There is a PR or the Energy logs here: home-assistant/core#139211

[erikgeurts]

I know, I've seen that too, but it's not a fix for the 429 too many requests on the actual energy API that's blocking me and everyone else from retrieving their energy data. Even though my own REST integration (self-coded) isn't causing any harm because it tries to retrieve energy data just once per hour and not with every call to the status API, I'm still being blocked from accessing my data. I realize that this issue in the HA integration is bogging down the energy API, so I'd say let Weheat focus all attention and effort on fixing that before Weheat starts working on new things.

[jesperraemaekers]

I can tell you now that the rate limiting, as is in place now, is here to stay with the current settings.
The flow values being available is a "lucky catch" for HA as @barryvdh was very on point with his observations and I just pointed him in the right direction.

[jesperraemaekers]

@barryvdh I just released 2025.2.27 so feel free to integrate it.