[bug] - hvac_action_reason empty after restart

[swingerman]

I'm not sure if it is related (or helpful) but hvac_action_reason doesn't get set to anything at all after a restart until the thermostat takes some 'action' again.

So if it was target_temp_reached and you restart (or reload the YAML from Developer tools) then it remains as an empty attribute until something gets changed and causes an action to occur that would change it.

I've been trying to use it to determine if an AC has been turned off by the integration or manually from a control panel and the 'blank' value has caused some issues with the logic

Originally posted by @cyberkryten in #245 (comment)

[swingerman]

@cyberkryten, @jacobw
Could you share your configuration please?

[jacobw]

  - platform: dual_smart_thermostat
    name: Lounge Climate
    unique_id: lounge_climate
    heater: switch.lounge_heatpump_heat
    cooler: switch.lounge_heatpump_cool
    target_sensor: sensor.yz_666e_temperature
    sensor_stale_duration: 0:05
    heat_cool_mode: true
    min_temp: 15
    max_temp: 26
    target_temp: 21.5
    target_temp_high: 21.5
    target_temp_low: 19
    cold_tolerance: 0.5
    hot_tolerance: 0
    precision: 0.1
    target_temp_step: 0.5

[cyberkryten]

Here's what I have:

`

• platform: dual_smart_thermostat
  name: Office Smart
  unique_id: office_smart
  heater: switch.virtual_office_heat
  cooler: switch.virtual_office_cool
  target_sensor: sensor.virtual_office_temperature
  heat_cool_mode: true # <-required
  cold_tolerance: 0.2
  hot_tolerance: 0.2
  precision: 0.1
  target_temp_step: 1
  min_temp: 12
  max_temp: 30
  target_temp_low: 16
  #target_temp: 23
  target_temp_high: 23
  min_cycle_duration:
  minutes: 5
  away:
  target_temp_low: 15
  target_temp_high: 29
  `

I'm not bothered about it being set the instant of restart (ie memory of what it was as I think that's hard in HA) - as I said, it also happens if you reload all YAML using Dev Tools, so just doing it after a full HA restart won't actually fix it.

I guess when making the 'do I do stuff' decision, checking if there's a value in there, and if not updating it to the current reason would fix both cases (and any others lurking).