New feature Auto Clear Remote Temp for MiElHVAC

[grzegorz914]

Description:

• This PR add auto clear remote temperature function
• This function is called on first run and also 10sec after the remote temperature stop updating its value
• Send clear manually is also available
• The auto clear time is in (ms), default is 10000ms, can be changed with command HVACRemoteTempClearTime

Related issue (if applicable): fixes #22365

Checklist:

• The pull request is done against the latest development branch
• Only relevant files were touched
• Only one feature/fix was added per PR and the code change compiles without warnings
• The code change is tested and works with Tasmota core ESP8266 V.2.7.8
• The code change is tested and works with Tasmota core ESP32 V.3.1.0.241023
• I accept the CLA.

NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass

[mamrai1]

I think 10sec are not enough. Maybe set the time to follow teleperiod ? Or 60 sec are more realistic

[grzegorz914]

Why is not realistic? you can call Remote Temp every 1 sec or quickly.

[mamrai1]

I mean realistic for an Hvac operation… the shortest time i think should be >30sec. No need to send remote temp less than 10-15 sec

[grzegorz914]

10 sec is very long time, the microcontroller respond time is in milliseconds. Where You see the problem to send data for example every 5 sec. I think the data need to be operated as quickly as possible.

[mamrai1]

Ok. Let imagine 2 scenarios:

1. The remote temperature sensor is on the same microcontroller: yes 10 sec is more than enough but
2. The remote temperature sensor is on another controller (in the same room of course) and sends the data via the mqtt server or directly on the controller on the unit: it does make sense to send the readings at teleperiod ….

[grzegorz914]

I use PLC to communicate with my microcontrollers, the 10sec is very long time where my loop in code is 7ms. Update data every few seconds is not a problem and also is nothing for CPU load. I don’t understand where is the problem, You can send the Remote Temp every 1sec, 2sec, 500ms etc. This technically is not a problem.

[mamrai1]

Many users use wifi/mqtt… Would be ok only a check in the mqtt loop if there is disconnection from the mqtt server?

[mamrai1]

Also in looked at mitsubishi2mqtt project and the time is set at 5 minutes ! (lines ~ 1350)

https://github.com/gysmo38/mitsubishi2MQTT/blob/master/src/mitsubishi2mqtt/mitsubishi2mqtt.ino

[grzegorz914]

This is wrong, in 5min the temp can changed from 20 to 25 grad. What happened if set temp is set to 23? nothing, just heating because the remote temp was not refreshed.

[mamrai1]

I do agree that in some situations the 5min is too long but also in some situations the 10sec is too short. :)

[grzegorz914]

What is the benefit to get longer time?
Why the 10sec time is not OK?, for me shorter time is always better because get more real time data to the device.

[grzegorz914]

I can make the auto clear time configurable but I have not enough skill with Tasmota to store it in non-volatile memory. In other case will always revert to default after restart. May be someone can help.

[arendst]

Make it a command.

This can then be used in a persistent rule during restart/boot and set the desired parameter like it was persistent.

This way no additional resources are needed.