Fix LUEFT_XXX_STUFE units and use as number

[kr0ner]

Requesting these values makes little to no sense, they are usually set once and then selected via LUEFT_STUFE_XXX. It might make sense to be able to set the values via HA, but this requires number entities.

@croessi please reconsider, if those values are really of any use ... I want to avoid having 500 entities that no one uses in the end

[Hotdogxxxx]

These values also work for the 504, and I would prefer to keep them. By comparing the ‘ABLUFT_SOLL’ with the LUEFT_XXX_STUFE values, you can generate a sensor for the frontend to show the current state. This also fixes the ‘LUEFTUNG’ boolean issue. I have noticed that this boolean never changes state when you turn off the ventilation.

[kr0ner]

The LUEFTER entity is broken and the workaround only works in some cases. IMHO what you try to achieve can be done by looking at the LUEFT_STUFE_XXX without the need to look at the settings.

In any case settings should be number entities and not sensors. They will never change without action

[Hotdogxxxx]

I’m not sure what the correct behavior is in this regard. You’re absolutely right that these values are numbers. But is it the right approach to edit such values from the settings via Home Assistant? If you’re not careful, you could easily misconfigure the heat pump, and I also don’t want to mess up considering the high price. Listening to the values is one thing but enabling to set up the value which are hidden behind a password ment only for technician is another.

[kr0ner]

I don't think you can break the heatpump this way. It has built in protection mechanisms.

Also If anyone plays with settings and has no clue what it does, he should most probably not use this repo at all. In my case I need access to everything in the base to adjust my heatpump to my needs. The defaults were so far off from the ideal settings. Maybe there could be a read only mode for settings that requires explicit deactivation. You can create an issue and I will implement it at some point.

[croessi]

yes my intention was to set these values via Homeassistant, because currently I manually reconfigure the pump during summer to pump out more air than it sucks in to allow better aiflow through the windows. Worked quite good. So yes @kr0ner the change you are proposing here would have been proposed by me in the near future, anyhow. --> I like it. Units are m³/h

[kr0ner]

yes my intention was to set these values via Homeassistant, because currently I manually reconfigure the pump during summer to pump out more air than it sucks in to allow better aiflow through the windows. Worked quite good. So yes @kr0ner the change you are proposing here would have been proposed by me in the near future, anyhow. --> I like it. Units are m³/h

Have you seen the PASSIVKUEHLUNG setting? This seems to be the thing you want and it is implemented already :wink:

[sascha-egerer]

yes my intention was to set these values via Homeassistant, because currently I manually reconfigure the pump during summer to pump out more air than it sucks in to allow better aiflow through the windows. Worked quite good. So yes @kr0ner the change you are proposing here would have been proposed by me in the near future, anyhow. --> I like it. Units are m³/h

Have you seen the PASSIVKUEHLUNG setting? This seems to be the thing you want and it is implemented already 😉

Ah thats interesting... I always thought it's related to the optional "floor cooling system" but It's related to the air system?

[kr0ner]

That one would be active cooling via floor and/or air ;)

Passive turns off the ZULUFT so that air gets sucked in via the windows. Works well, but it is annoying that the heatpump has this weird preparation phase (shrug)

[kr0ner]

And there is also this one https://www.tecalor.de/de/produkte/lueftung/zubehoer/lwf-ar-1-5/lwf-ar-1-5.html

Will install this next years to cool/heat the air instead of going via the FBH, cause cooling does not work nicely