I am trying to troubleshoot changes to the thermostat on one of my heaters.
Currently I’m using both HA automations, Node-Red in addition to the HomeKit integration to do temperature changes to my heaters.
This heater is supposed to be set to a lower temperature at night, but something is adjusting the temperature back up.
WTH is there no information in the logbook about what automation or integration that changed the temperature?
That’s the change in the start of the graph, at 11:37AM. However, the changes around 9pm, both up and down, are not shown in the logbook display. Nor are the brief spike around midnight, or the short up and down at 5 or 6 am.
To the OP: you say it is supposed to go down at night, and something turns it back up . Whatever turns it down does not seem to be recorded either. Which integration/automation should be doing that?
@tom_l , don’t forget that to most users, it is not clear that addons are outside HA. I don’t use NR, but the add-ons I use do keep their own logs accessible from HA. @ricmik If you go to settings/system/logs and in the top right, can you select Node Red? If so, what does the logbook say?
Graph is not a logbook. I specifically said logbook. Graph just confirms HA did get the change from the device. I don’t have any thermostats in HA, I’m guessing the temp is not state, but an attribute, and that’s why it’s not logged (at all, not just for external causes). Same as a light entity doesn’t report brightness change in the logbook.
As you can see here, I used two scripts: One script to turn the temp down to 10 degrees, then up to 29 degrees. Nothing in the logbook. It might as well never have happened
Then I used the script “Test Script Turn Off” and that one is showing in the logbook.
Let’s say I’m doing a couple of automations and scripts towards the same climate entity. To see which automation or script that did a temperature change, I will have to go into each and one of them to see which of them that triggered the change. Not especially user friendly in my opinion.
The likely hood of someone adding “Show just this one attribute in logbook” is extremely low. It would be all attributes or nothing. And right now, there is no filter for the logbook outside the entity_id filter. Which would be flooded for some entities if the entity contains a ton of attributes.