Warning (message first occurred)

PickOne · June 10, 2021, 12:44pm

Hello

Anybody knows what is about with this warning?

15:36:39 – (WARNING) Automation - message first occurred at June 9, 2021, 13:28:38 and shows up 4270 times

Should I do something?

Troon · June 10, 2021, 12:52pm

At that rate of message generation, yes. What’s in the full logs?

PickOne · June 10, 2021, 12:55pm

many many lines like this

2021-06-09 14:55:38 WARNING (MainThread) [homeassistant.components.automation.data2var_rooms_temperature] Data2Var - Rooms Temperature: Already running
2021-06-09 14:55:38 WARNING (MainThread) [homeassistant.components.automation.data2var_rooms_humidity] Data2Var - Rooms Humidity: Already running
2021-06-09 14:55:38 WARNING (MainThread) [homeassistant.components.automation.data2var_rooms_temperature] Data2Var - Rooms Temperature: Already running
2021-06-09 14:55:38 WARNING (MainThread) [homeassistant.components.automation.data2var_rooms_humidity] Data2Var - Rooms Humidity: Already running
2021-06-09 14:55:38 WARNING (MainThread) [homeassistant.components.automation.data2var_rooms_temperature] Data2Var - Rooms Temperature: Already running
2021-06-09 14:55:38 WARNING (MainThread) [homeassistant.components.automation.data2var_rooms_humidity] Data2Var - Rooms Humidity: Already running
2021-06-09 14:56:38 WARNING (MainThread) [homeassistant.components.automation.data2var_rooms_temperature] Data2Var - Rooms Temperature: Already running
2021-06-09 14:56:38 WARNING (MainThread) [homeassistant.components.automation.data2var_rooms_humidity] Data2Var - Rooms Humidity: Already running
2021-06-09 14:56:38 WARNING (MainThread) [homeassistant.components.automation.data2var_rooms_temperature] Data2Var - Rooms Temperature: Already running
2021-06-09 14:56:38 WARNING (MainThread) [homeassistant.components.automation.data2var_rooms_humidity] Data2Var - Rooms Humidity: Already running
2021-06-09 14:56:38 WARNING (MainThread) [homeassistant.components.automation.data2var_rooms_temperature] Data2Var - Rooms Temperature: Already running

and some like this

2021-06-09 15:01:19 WARNING (MainThread) [homeassistant.helpers.script] Error in ‘choose[0]’ evaluation: In ‘template’ condition: UndefinedError: ‘dict object’ has no attribute ‘Computer_TempHum_Sensor’

koying · June 10, 2021, 1:05pm

That means that the data2var_rooms_temperature and data2var_rooms_humidity automations are being triggered while the previous execution is still running.

You can alter the mode of the automation to remove the warning, but it most certainly means something is flawed in the logic.

PickOne · June 10, 2021, 1:07pm

Well… yes, there are many triggers for that automation… then, every action is running depending of which trigger has ben triggered

I am trying to avoid many automations and I put many similar, into a single one… with conditions

koying · June 10, 2021, 1:12pm

Maybe try mode: parallel, then Automation Modes - Home Assistant

But you’re better be sure of what you’re doing (triggering at least 11 times in the same second seems much) or you might kill HA.

Troon · June 10, 2021, 1:13pm

Or see the throttled example:

But agreed: review your triggers, that’s a crazy rate. Room temperature will be affected by your burning HA machine.

PickOne · June 10, 2021, 1:15pm

I understand! Thank you both. I will see what I can do

PickOne · June 10, 2021, 1:19pm

If I have 20 sensors in the same automation and all will trigger in the same time, I will have already 20 times If the sensors are refreshing every 5 seconds… imagine I can’t do anything just maybe that thing with silent, which will not register as log warning, but in the back, it will trigger in the same way… many times

Troon · June 10, 2021, 1:24pm

Options:

Trigger every minute with a time_pattern trigger or state of sensor.time
Turn the refresh rate down: does your room really change that fast?

koying · June 10, 2021, 1:24pm

Well, actually, they won’t be executed, by default
The default mode, single, prevents a new instance of the automation to be executed while one is already running, so your “mega-automation” is currently not running as you think it is…

PickOne · June 10, 2021, 1:27pm

I was thinking that even if is set on single, an automation should run in miliseconds, very fast… which means that a new “session” of the same automation, can start again and again… But yes, if I want to be sure that all the sensors are registering into that automation, I should use something else than single…

PickOne · June 10, 2021, 1:28pm

No, no need to change that fast, of course. I just let the sensors to triggers everytime when they want.

I will try to see how that time_pattern works. Thank you!

koying · June 10, 2021, 1:32pm

The warnings you see tell you exactly that the automation was still running and that something else triggered it. The new trigger is then ignored.

PickOne · June 10, 2021, 1:34pm

I understand, so… this means that every time I get a similar warning, the automation have not been executed…

Wow… that is something :))) 4000 from yesterday, ok…

PickOne · June 10, 2021, 1:40pm

I think that I should create sensors than using automations… in my case.
I have an automation which receive signal from every zigbee device, than turning that datas to values for some variables…
I thought that is easier to use an automation which does this, than create sensor to receive data into them…

koying · June 10, 2021, 1:48pm

There is the Event Sensor custom integration that does exactly that: GitHub - azogue/eventsensor: HomeAssistant custom sensor to track specific events

PickOne · June 10, 2021, 4:15pm

I was thinking to do this with the mqtt sensors, i’m using a tasmota zigbee bridge

koying · June 10, 2021, 4:20pm

Well, it depends what you mean by “signal”…
I understood it as “events”.

PickOne · June 10, 2021, 4:23pm

I am trying to test the Event Sensor right not, maybe could be what I try to achieve Hope I will learn fast how to use it . Thanks