I have an Inovelli White Series Matter+Thread light switch. It has a custom button called Config that you can use for automations. Config is listed under Events in Device Info. I’ve noticed some unexpected behavior whenever I run sudo docker compose restart.

Here’s what happens after compose restart exits.

  • Home Assistant WebUI comes up
  • Inovelli switch entities become unavailable
  • 5 minutes passes in the unavailable state
  • Inovelli switch comes back to life, setting all of its entity’s values back to what they were before
  • Config event fires

The Config event firing on reboot is really bad because it triggers an automation I have that listens for the Config event to fire…

How should I be coding the automation to ignore Config events from reboots? I found some Event docs and also a forum post, but they didn’t turn out too helpful.

Here’s the automation I came up with based on the links above. Unfortunately, this still triggers the automation on reboot.

alias: Inovelli switch 
description: ""
triggers:
  - trigger: state
    entity_id:
      - event.inovelli_on_off_switch_config
conditions:
  - condition: not
    conditions:
      - condition: state
        entity_id: event.inovelli_on_off_switch_config
        state: unavailable
      - condition: state
        entity_id: event.inovelli_on_off_switch_config
        state: unknown
actions:
  - choose:
      - conditions:
          - condition: state
            entity_id: event.inovelli_on_off_switch_config
            attribute: event_type
            state: multi_press_1
        sequence:
          - action: script.inovelli_switch_turn_on
            metadata: {}
            data: {}
mode: single

Running HA 2025.10.4 in Docker Compose.

  • paequ2@lemmy.todayOPEnglish
    2·
    1 day ago

    Aaaah, ok! Here’s what I added based on your uptime idea.

    conditions:
  - condition: state
    entity_id: switch.inovelli_on_off_switch_load_control
    state:
      - "on"
      - "off"
    for:
      hours: 0
      minutes: 3
      seconds: 0

    I’m using if the switch has been in the “on” or “off” state for 3 minutes or more as my gate. (Since during the reboot the state is either “unavailable” or “unknown”.)

    Seems to be working so far! Thanks!

    • Serinus@lemmy.worldEnglish
      2·
      23 hours ago

      Does that mean you can’t turn the light off and back on quickly, in the case of something like forgetting something in the room?

      • paequ2@lemmy.todayOPEnglish
        1·
        21 hours ago

        Uh, don’t think so. Here’s what the whole automation looks like.

        alias: Inovelli switch 
description: ""
triggers:
  - trigger: state
    entity_id:
      - event.inovelli_on_off_switch_config
conditions:
  - condition: state
    entity_id: switch.inovelli_on_off_switch_load_control
    state:
      - "on"
      - "off"
    for:
      hours: 0
      minutes: 3
      seconds: 0
actions:
  - choose:
      - conditions:
          - condition: state
            entity_id: event.inovelli_on_off_switch_config
            attribute: event_type
            state: multi_press_1
        sequence:
          - action: script.inovelli_switch_turn_on
            metadata: {}
            data: {}
mode: single
        • Wait for a Config button press (different than on/off rocker button)
        • Check if main rocker button has been in “on” or “off” state for at least 3 minutes
        • If yes, then run script

        The main on/off switch is unaffected by this automation. (Double checked to make sure I could turn on and off the fan quickly.)

        • Serinus@lemmy.worldEnglish
          1·
          21 hours ago

          I read that as “on state for 3 minutes” or “off state for 3 minutes” and not a combination of on/off for 3 minutes. Easy to test. Turn the light off. Turn the light back on.