States not updating when running for low temperatures

[dan-riley]

The states of each feature seem to only reflect manually entered or scheduled states, and not those triggered for low temperatures. The remote Hayward HACS integration reflects these properly. I have a pool pump, waterfall pump, and spa jets pump, all of which are currently running due to low temperatures. Only the pool pump is showing as running via this integration, likely because it's scheduled to be on anyway. The waterfall and jets show off, although they are on, and the other integration shows that. This integration does update when I turn them on via the Hayward app.

[cryptk]

I had a bit of a design choice to make with this, and I agree that it isn't consistent. The integration DOES know that the system is in freeze protect mode, if you look at the attributes of the filter, you should see a WhyOn attribute that is set to "Freeze Protect".

There is probably a better way to handle this, but my thought process was to have the valve actuators follow the "intent" of the user (you intend them to be off), the fact that they are on anyway because of freeze protect mode was something that I was going to leave to the internal handling of the OmniLogic.

I am working on getting a lot more status reporting into the integration, so I will leave this open so that I can think about how to best represent "it's on, but only because of freeze protect, not because you asked it to be on". Especially since "on because freeze protect" and "on because of user choice" and "on because of a schedule" are all different states of "on" according to the OmniLogic.

If the valve were "on" because of freeze protect, that would somewhat lead a user to believe that they could then turn that valve off, which they can't. The alternative is to have the valve "off", which leads the user to believe that they can turn the valve on, which they also can't. Home Assistant doesn't have a great way of indicating "here is the on/off state, and I know the on/off state, but you temporarily cannot alter the state".

It might be worth adding a sensor or diagnostic entity (potentially disabled by default) to indicate that the system or BOW is in freeze protect mode.

I should be getting below my freeze protect temperature tonight, I'll make sure to pull some telemetry and configs from my controller to see what I can do about surfacing this a bit better.

[dan-riley]

I kind of get the logic, but not sure I agree with having it just represent the user intended state and not the actual state. The OmniLogic app even shows a button with the current actual state that you can toggle (though I don't think it does anything during freeze protect). Biggest difference is that it has another indication that it's on due to freeze protect.

In any case, the reason I noticed is I'm building energy sensors for all of my pumps to track usage. This works fine on the main pump because it's a VSP and reports power, regardless of the "intended" mode. But for my other features, they're on single speed pumps with no power reporting, so I was building helpers (later switched to Powercalc when I found out about it) to record a fixed power output when they're on. But since it's not reporting on, I can't do anything with it. I still have the cloud integration installed so could use it for this purpose, but I'd rather switch to using your integration only. So far I think this is the only thing preventing that.

[cryptk]

Can you get me the diagnostic output from the integration for your pool? I'll see what I can surface about those relays and single speed pumps. I'm not opposed to changing it to have the valves/relays show as on when they are in freeze protect mode, I just need to also surface the "whyOn" data better as opposed to just giving a number (which is what the API returns)

[dan-riley]

Here you go! It happens to be on right now. Hopefully tomorrow we warm back up and this is the last time it's on freeze protect but who knows! Thanks for checking this out. You should see the VSP on freeze protect, plus Waterfall and Jets single-speed.

config_entry-omnilogic_local-01JGN1C77MSHSAPSN322SC9YAX.json