Add support for Manual / Automatic mode

[antibill51]

Hi.

Is it possible to add manual support on this component?

Maybe, we can have a button with OFF / Manual / Confort, and an other button with heating times active?

Else we need a button with modes : Off Manual Automatic

Confort without heating time Confort with heating time

Maybe we can use multiples climate devices, and a lovelace card changing in fonction of an input select Manual / Confort.

Manual with off/ Manual / Automatic ( manual with heating times active) and the actual climate device for Confort mode (Off / Confort / Confort with heating time)

Thanks.

[antibill51]

Hi

After some thought, I'm not sure that the manual function is really useful, since you can play on the "room_power_request" parameter. Not using the manual mode would be safer in the event of failure of the firenet service, the stove will stop anyway at the target temperature.

[antibill51]

Hi. I allowed myself to create a fork. I hope it does not bother you. You can of course use the points that seem interesting to you for your project. In this one, I added some sensors, such as the quantity of pellet before service, the speed of the motors, etc.

I also modified the automatic / manual part, and the management of heating times. The climate component always has 3 functions: off / manual / auto. I also added a switch to activate the heating times in these 2 modes.

• Manual / heating time off: equivalent to manual mode on the stove.
• Manual / heating time on: equivalent to automatic mode on the stove.
• Auto / heating time off: equivalent to comfort mode on the stove, with inactive heating times
• Auto / heating time on: equivalent to comfort mode on the stove, with active heating times

I also created automation directly on home assistant in order to vary the power according to several factors, and this in all modes, including for multiair.

The factors are:

• Current zone temperature
• Setpoint temperature
• Outside temperature
• Heating coefficient.
• Insulation coefficient
• Offset to manage the lag between the start of heating and the rise in temperature.
• Time between 2 power value updates.

I still have to clean this up, but it's functional.

As soon as it's done, I'll share the code, unless of course it's possible to integrate everything directly into the component.

I saw in your code a part with images associated with the different states of the stove, and also a start of management of preset mode. Can you tell me more?

Thank you

[Fockaert]

Hi @antibill51 ,

Sure go ahead with the fork, let's see later once final on your end, which parts we can port back. Your ideas look very interesting, especially the vary of power as I'm switching manually multiple times during the winter.

Thanks, Jan

[t0bse]

any news on this?

[helmi55]

HI Friends. I#m new in HA and I wud look very forward to your Project antibill51 Thanks Helmut

[antibill51]

Hi. My fork is here : https://github.com/antibill51/rika-firenet-custom-component

@helmi55

[helmi55]

Many thanks meanwhile I found it. @antibill51 I just have a problem: as you show in your add-on above, when click on the icon of stove thermostat you can change the temperature. This is not possible for me.

[helmi55]

Hi again forget it. It was the sensor "climate" But a last question: Where can I change the language. I saw there is a German file?

Best regards Helmut

[helmi55]

Hi again @antibill51 A very good project thanks. I'm ver new in HA and therefore I have again a question: Is it possible to see the schedules of heating times from Monday to Sunday as it is in the stove and can I change this heating times in HA and send it to the stove?

Many thanks in advance Regards Helmut

[antibill51]

Hi @helmi55. To start, regarding the fork, try asking your questions directly here: https://github.com/antibill51/rika-firenet-custom-component/issues

For your questions: As said in the fork page, I bypass Rika built'in thermostat with PID Thermostat. So, temperature on the lovelace card is for a template climate entity, not for the stove. Nevertheless I removed this part on another HA install, so, when possible, I give you what to do for that. ( But, before, create an issue on my fork ;) ) The language files are automatically managed by HA, but, for me too, sometimes a return to English is done. I did not take the time to find out why, and if it is possible to improve this point.

Last point, as explained on my fork, the internal management of the stove is bypassed in my case. It is therefore HA, with automations, which defines the heating ranges, the temperature setpoint, heating time, multiair, etc.

The stove limits to 2 ranges per day, HA has no limit. The disadvantage is that without the RIKA cloud, the lockers do not pass. But unfortunately, unless @kiddouk (https://github.com/iero/Rika-Stove/issues/1#issuecomment-566966989) has succeeded or shares these advances to control the stove without cloud, I'm afraid the situation will remain as it is..

{ 'controls': { 'heatingTimeMon1': '00000000', 'heatingTimeMon2': '00000000', 'heatingTimeTue1': '00000000', 'heatingTimeTue2': '00000000', 'heatingTimeWed1': '00000000', 'heatingTimeWed2': '00000000', 'heatingTimeThu1': '00000000', 'heatingTimeThu2': '00000000', 'heatingTimeFri1': '00000000', 'heatingTimeFri2': '00000000', 'heatingTimeSat1': '00000000', 'heatingTimeSat2': '00000000', 'heatingTimeSun1': '00000000', 'heatingTimeSun2': '00000000', 'heatingTimesActiveForComfort': False } 'sensors': {'statusHeatingTimesNotProgrammed': True}