Automation triggering reliability

Configuration
,
1

Hi all,

I’m wondering if others also having stability issues triggering automations.
I have about 90 wifi devices. 45 devices configured as latest MQTT tasmota FW, and all the rest are Shelly’s FW also configured as MQTT.

In general, most of the time all are working with no issues and triggering all automations as expected, but sometimes, without any errors or warnings - one or several automations will not be activated, although the HA indicate that they are triggered.

Using simple Automation for my devices: using 4 schedule timers for each of my devices(2 for ON and 2 for OFF).

one of my rollers config:

cover:

#shelly25 family room mqtt roller
 - platform: mqtt
   name: "Family garden exit"
   state_topic: "shellies/shellyswitch25-688AC3/roller/0"
   command_topic: "shellies/shellyswitch25-688AC3/roller/0/command"
   position_topic: "shellies/shellyswitch25-688AC3/roller/0/pos"
   set_position_topic: "shellies/shellyswitch25-688AC3/roller/0/command/pos"
   payload_open: "open"
   payload_close: "close"
   payload_stop: "stop"
   qos: 2
   retain: false
   optimistic: false
   position_open: 100
   position_closed: 0


input_datetime:
# 4 timers
  timer_1_on:
    name: ON timer 1
    has_time: true
    has_date: false
  timer_1_off:
    name: OFF timer 1
    has_time: true
    has_date: false
  timer_2_on:
    name: ON timer 2
    has_time: true
    has_date: false
  timer_2_off:
    name: OFF timer 2
    has_time: true
    has_date: false

and this is a simple automation for the relevant roller for one of the timers:

- id: family_roller_timer_on #FAmily room roller timer 1 automation
  alias: Family Exit roller ON 1
  trigger:
  - platform: template
    value_template: '{{ states.sensor.time.state == (states.input_datetime.timer_1_on.attributes.timestamp
      | int | timestamp_custom(''%H:%M'', False)) }}'
  condition: []
  action:
  - data:
      entity_id: cover.family_exit
      position: 100
    service: cover.set_cover_position
- id: family_roller_timer_off
  alias: Family exit roller OFF 1
  trigger:
  - platform: template
    value_template: '{{ states.sensor.time.state == (states.input_datetime.timer_1_off.attributes.timestamp
      | int | timestamp_custom(''%H:%M'', False)) }}'
  action:
  - data:
      entity_id: cover.family_exit
      position: 0
    service: cover.set_cover_position

All my MQTT qos are level 2 also in Shelly FW and tasmota configuration.
using the latest HA version on raspberry 3b+.
other than the the automation issues all my devices has stable WIFI connection - no disconnections at all for weeks between power downs. completely clean logs.

seems like the automation trigger is not always executing its action.

Did anybody else had similar issues with automations stability?

2

As an experiment, try this shorter version:

    value_template: '{{ states.sensor.time.state == states.input_datetime.timer_1_on.state[0:5] }}'
3

updated my automation file. will try it for a few days…

4

Hi Taras,

Can’t explain it, but i have test it for some time and it seems to work great with no miss-triggering.

Thanks!

5

couldn’t it be even one digit shorter? :slight_smile: (and a few characters because of the states() format )

{{states('sensor.time') == states('input_datetime.timer_1_on')[:5] }}
6

Yes, you’re right. It can even be three characters shorter if you remove all the spaces:

{{states('sensor.time')==states('input_datetime.timer_1_on')[:5]}}

:slight_smile: