Missing climate thermostat events in logbook

Configuration
1

I have two custom thermostats that aren’t showing up in the logbook. Can anyone see what I’m doing wrong?

Config is:

logbook:
  include:
    domains:
      - sensor
      - switch
      - binary_sensor
      - utility_meter
      - timer
      - climate
      
recorder:
  purge_keep_days: 5
  commit_interval: 15
  include:
    domains:
      - sensor
      - switch
      - binary_sensor
      - utility_meter
      - timer
      - climate
      
   
      
history:
  use_include_order: true
  include:
    entities:
      - sensor.fridge_temperature
      - sensor.freezer_temperature
      - sensor.dinning_hall_temperature
      - sensor.dinning_hall_boiler_temperature
      - sensor.washroom_temperature
      - sensor.waterbuilding_temperature
      - climate.dinning_hall_floor_heat
      - climate.dinning_hall_furnace
      - timer.dinning_hall_furnace_timer
      - switch.furnace_fan_switch
      - switch.dinning_hall_furnace_heat
      - switch.dinning_hall_floor_heat
      - sensor.myups_input_voltage

Screen Shot 2022-03-12 at 9.50.28 AM

1 Like
2

I thought I had this issue as well until I realized that history graph is tracking the temperature but the logbook tracks the current mode of the thermostat (cooling/auto/heating).

So if you change your thermostat from Cooling to Heating it will show up in the logbook. But if you change the temperature for the target temperature or thermostat’s preset that won’t be logged.

I think it would be WAY more useful if the state of the thermostat is the target temperature. That way I can see who changed it and what they changed it to. I don’t think many people change their thermostat mode often.

3 Likes
3

Yes I agree. In my case I would like to know who changed the set point.

1 Like
4

Agree. I would love additional logging (who changed setpoint and what temperature it was set to).

5

Maybe we need to create a feature request for this? So that more people can vote on this :slight_smile:

6 Likes
6

If you’re looking for a way to get around this, you can use a number helper as a proxy to the climate entity’s set point (i.e. create a number helper and an automation that adjusts the set temperature of the climate when the number is changed). You’ll be able to see who changed the temp via the number helper logs.

We have guests at home right now and the climate keeps changing. Since I can’t tell what’s changing it, I’ve set up alerts so if it goes crazy high/low I can fix it.

7

Care to share your yaml?

8

I would create both the number helper and the automation via the UI. The automation YAML would look something like this:

trigger:
  - platform: state
    entity_id: input_number.radiator_set_temp
action:
  - service: climate.set_temperature
    data:
      temperature: "{{ trigger.to_state.state }}"
    target:
      entity_id: climate.radiators

Whenever the input number changes, it updates the climate entity set point. You’d see the changes to the input number in the logs, along with who changed it.

3 Likes
9

Hi @higbyk, I just added this automation and I see the setpoint change but it shows up as “changed to 14.0 triggered by service Input number: Set”
So the user is service Input number?
Are you still using this automation?