Hi,
I want to see the state of entities in the history. Works fine for a device (relay in a Shelly plus 1), fails for a timer or an input_boolean.
I think, if I can choose items to compose a diagram, this item should show its state, or is this not true for helpers?
First row, relay at Shelly device, seecond row a timer which starts running when the pump starts and is stopped together with the pump or expireres after 7 minutes.
Third row an input_booleean, triggered by a switch (custom.button_card) or a time pattern.
Whole automation works fine now, so at least the input_boolean has to change. It do that, I checked the traces of my automation.
Ok, if there is no special thing to config elswhere , something is interesting.
Oh, lot of answers.
First of all, the automation works. In one of my screenshots you can see, the pump starts AND the temperatures start changing, cause the hot water starts to circulate. This is the best proof I can think about.
The automation has 4 triggers, the first one fires when my input_boolean changes from âOffâ to âonâ and in this case the timer gets started and the Shelly 1 plus closes the contacts of its relay.
As far as I know, the input_boolean has the state âonâ and ⌠nothing happens in the histrory.
The timer runs 7 minutes if the temperature didnât reach 25°C within this time. Normally, it takes ~ 5 minutes to get over 25°C, so the automation is triggered (trigger number 3) and in this case, the input_boolean is switched off. This isnât reflected in the UI too. The automation is a queued one, so the âswitch the input_boolean offâ trigger is queued up and processed during the next lap. In the next lap, the state changes from âonâ to âoffâ and this time the timer is canceled and the relay is opened (trigger 2).
This works all fine with manual starts and stops, or triggered by a timee pattern.
I also have anotheer input_boolean âHoliday-Modeâ or in german âUrlaubsmodusâ. I add it to the histrory and switched it on/off manually, and this time no problem.
BUT: There is a little difference between this two items. The input_boolean I used for the pump has a reference to a speech assistant I will add later, the âUrlaubsmodeâ not.
With best regards
Gerhard
PS: Will start the timer manually and check out âŚ
Hi all,
so I started the timer just as Ildar_Gabdullin told me, and wait for about 10 minutes, nothing happens in the histrory, timer shows âIdleâ nothing elsee âŚ
Start a timer from itâs more-info window, then press a corr button on the right part of the window to show a History for the timer - does it show the started timer?
Also, I already suggested to do the same with input boolean.
If manual changes of timer & boolean are reflected in History - then sort out why these entities are not changed by automation.
After ~ 5 minutes the temperature in the system is high enough, and so the state of my input_boolean is set to âoffâ. This results in a trigger which is queued up for the moment.
In the next lap, the timer is canceled and the pump is switched off.
Thats it, no more triggers in the queue.
This is exactly I want to do and I am pretty sure it works out.
And here you can see, that the temperatures physically raises, so this is the best proof I can think off, it works.
And you can see, no reaction in the histrory plot, for what reason ever.
The automation is triggered and set the input_boolean to âoffâ. As the input_boolean was already in âoffâ state, there is no listener in the automation for a state âchangeâ from âoffâ to âoffâ, so no more trigger queued and the automation finishing at that point.
It may happen only for entities excluded from Recorder.
But there are no mentions in ârecorder.yamlâ (which has âexcludeâ rules) for the timer.
On another test HA setup - which has no ârecorder.yamlâ specified - the history of the timer is shown.
Maybe you already answered this, but I do not see any input_boolean.turn_on service calls in the automation, so I have no idea how it would ever be on.