History logging automations "activated" that did not actually run due to precondition

My History (old and latest version of app) is showing Automations having a time (e.g. every day at 11:30pm) are “activated” at 11:30pm even tho the location precondition is not met.

It is not actually running any of the THEN functions (i.e., it is not really activated) but it is certainly annoying to see this message, and no distinguishing between whether it actually ran or not due to the condition/pre-condition.

@smarthings this is not good/helpful IMO

I take a completely different view. I want to know that the Automation has been activated (i.e. has checked its conditions to see if it needs to do anything). It may be that the Automation is being activated when it shouldn’t be or isn’t being activated when it should be. Once I can see that it is activating only when I intend it to, I can then go on to assess if the conditions are being evaluated as I intend them to.

If all I know is when the Automation has activated in such a way that the conditions are true, that isn’t telling me so much.

You have a point… but can’t we have it both ways

Activated - for some condition evaluated true
Executed - for all conditions evaluated true

in the logs?

I guess the issue might be that Automations and Scenes are simple instances of Rules and ‘both ways’ doesn’t begin to describe the complexity Rules can reach. So it may be a simple record of activation is as far as the History could easily ago. However there certainly does seem to be a need for more thorough logging of Automations / Scenes / Rules somewhere, even if it isn’t in the History specifically.

User access to logging information has always been a bit of a weakness of SmartThings.

You’d think this would be an emphasis, because logging would allow users to self-diagnose issues better without having to open a ticket.

Which is exactly what I’m going to do now.

This is what I got back after opening a ticket:

Anup (SmartThings)

Sep 20, 2021, 4:51 PM MST

Hey there,

Thanks for your time and patience while working on your issue,

I am sorry for the inconvenience caused to you. I understand how it can be frustrating to have such a situation and we are very sorry for such destabilizing encounters you have been faced with. One of our strengths is the way we respond to our customers promptly.

This is a known issue that should be fixed in the next hub firmware update which should be released soon. What happens is that every time the local automation is checked to see if the conditions are met for it to run, it gets logged as it did execute. This will be resolved so that the message only appears when the automation is evaluated as meeting the conditions to trigger which is when it actually runs.

We kindly request you to please wait for the next firmware update and to check if the issue is resolved after that.

Samsung SmartThings Support

I hope they don’t do that. An extra message, or two different ones is fine. A message only when the ‘then’ executes would not be very helpful.

It is if there is any knock on effect on Rules in general that is my real worry. The only way to log those with one line is to log the conditions being checked.

I wonder if mention of hub firmware means that hubs and cloud were out of step. I hadn’t noticed that they were.

There would a lot to be said for a ‘log’ command.

1 Like