Warning (message first occurred)

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?

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

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’

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.

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

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

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.

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.

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

If I have 20 sensors in the same automation and all will trigger in the same time, I will have already 20 times :smiley: If the sensors are refreshing every 5 seconds… imagine :smiley: 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 :slight_smile:

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?

Well, actually, they won’t be executed, by default :wink:
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…

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…

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!

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.

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… :slight_smile:

1 Like

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…

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

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

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

1 Like

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