Fockaert / rika-firenet-custom-component

MIT License
20 stars 17 forks source link

Add support for Multi Air #9

Open antibill51 opened 3 years ago

antibill51 commented 3 years ago

Hi.

Can you add support for Multi Air?

values :

convectionFan1Active : false / true convectionFan1Level : 0(auto) / 1 / 2 / 3 / 4 / 5 convectionFan1Area : from '-30' to '+30' (%) convectionFan2Active : false / true convectionFan2Level : 0(auto) / 1 / 2 / 3 / 4 / 5 convectionFan2Area : from '-30' to '+30' (%)

f015ad7a5c6d979fc9fe2cdc0f4e9045d7631d45

I want to make a thermostat with an external sensor for each multi air zone, adjusting convectionFanXActive and convectionFanXLevel compared to difference between target temperature and sensor, and maybe ( also for the main thermostat, a variable adjusted by external temp, or PID)

Thanks.

Fockaert commented 3 years ago

Committed the support for multi-air please try it out on Rika stove, when looking at Rika firenet website I see all properties changing successfully.

antibill51 commented 3 years ago

Hi.

It work, but when I change the state of Rika DOMO convection fan (on / off), it return immediatly to the old state, and move to the new few second after.

Maybe it's possible to add in config flow an option to select temperature sensor for each multiair, and then create a climate device per multiair, only with on off function.

And why not a function to modify power in manual / confort / Multiair modes in terms of actual temp / target temp, and why not, also external temperature? This function could either be integrated into the component, or carried out by a hassio automation.

Thank you for everything.

Fockaert commented 3 years ago

With latest commit on Master the change state delay is fixed, so please try again.

As far I'm aware the climate device is only for temperatures and not other values so we need to find different solution.

Could you explain in more concrete examples about the modifying modes, not clear for me. I'll try to find solution to select multiple modes with a single input.

antibill51 commented 3 years ago

It's ok for the delay.

For me it can work. As the heating power is not managed by climate component, it turns the stove on and off always according to the temperature in relation to the target temperature, the only change being that it would be done in manual mode. Just on off. What do you think ? And roughly the same for multiair, but with external temperature sensors specified via configflow.

antibill51 commented 3 years ago

Hi.

I create a Generic_thermostat for multiair, with this caracteristics : `

Do you think it is possible to create it automatically via your custom component?

Otherwise it does not matter.

I am also thinking about a formula that can give a percentage of power according to the difference between the current temperature, the target temperature, and a coefficient in relation to the external climatic conditions.

This would allow the power to be varied, both for the stove itself, but also for the multiair.

I don't know if it would be possible to integrate it into the component, or if it is better to go through an external script?

Once done, the management will be really superior to what the stove can do without your component.