Fix and evolution for mts960 bernardpe

[bernardpe]

• mode Cycle/count down on/off is reported as Fan_only HACMode
• Fix Min Mac for HACMode need to use KEYCTL_MIN and KEY_CTLMAX for MTS960 instead of KEY_MIN, KEY_MAX
• Set display precision of 1 on generic Current Temperature Entity
• Add entity Output Power State to report when output Power is On or Off
• Fix Issue for MTS960 Configuration like Lock switch (MTS960 needs array of parameter)
• Fix Multiple Generic Calendar issue
  • Management of number of schedule par days (using section entry)
  • Issue when updating the last schedule of the day (update is internally delete and add but delete the last is not allowed)
  • bad temperature scaling using 10 instead of climate.device_scale when data is send to device
  • one some case the last schedule added is replicated to all next days (we generated empty schedule when schedule is send to schedule
  • When received MQTT message, update calendar is not performed because reference copy of data instead of deepcopy
  • Now Management of event FREQ=week and we can set some days (BYDAYS) ==> Create a event for multiple selected days of the week
• Add a entity to reported Device Mode Status Report Cooling/Heating/Schedule Cool/Scheduling Heat/Countdown On/Countdown Off/Cycle/Off
• Management of namespace NS_APPLIANCE_CONTROL_THERMOSTAT_TIMER to reported Countdown on/off and cycle
• Change Config Label Forst_switch to Frost Alarm
• Set entity Frost (Temperature) to unavailable when Frost_switch is off ==> Issue to update temperature when Forst is off
• Move scheduleb entity Config to Diagnostic panel

[bernardpe]

Hi

Thanks for the update

I will continue to make changes on config fist implement alarm low and alarm high

After I will try to complete evolution by adding configuration of timer count down on/off and cycle

Let me know if you prefer a PR per evolution ?

Bernard