GPIO sensor automation not triggering on boot

[e3e6]

Hi community, I need help to troubleshoot my automation.

My Setup:

• Home Assistant Operation System installed on RPi4B and connected to UPS
• relay connected to GPIO 7

I have few chained automations which does not work on home assistant start

1. GPIO Sensor

binary_sensor:
  - platform: gpiod
    sensors:
    - name: "GPIO Button 7"
      port: 7
      active_low: true
      debounce: 500

2. Automation [1] – State trigger based on GPIO sensor, this automation toggle input_boolean sensor

automation:
    - alias: Power Grid State
      id: power_grid_state_changed
      trigger:
        - platform: state
          entity_id: binary_sensor.gpiod_gpiod_7_gpio_button_7
      action:
      - choose:
          - conditions:
              - condition: state
                entity_id: binary_sensor.gpiod_gpiod_7_gpio_button_7
                state: "on"
            sequence:
              - service: homeassistant.turn_on
                entity_id: input_boolean.power_grid_state_helper
          - conditions:
              - condition: state
                entity_id: binary_sensor.gpiod_gpiod_7_gpio_button_7
                state: "off"
            sequence:
              - service: homeassistant.turn_off
                entity_id: input_boolean.power_grid_state_helper

2. Automation [2] – State trigger based on Input Boolean sensor which sends a telegram message

    - alias: Power Grid Telegram Notify
      trigger:
        - platform: state
          entity_id:
            - input_boolean.power_grid_state_helper
      action:
        - service: notify.telegram
          data:
              message: Power State

This automation works fine when Home Assistant is up and running.

But failing when GPIO state was changed offline, so Automation [1] is not triggering despite GPIO sensor reports state change

I was managed to “fix” Automation [1] by adding Home Assistant Started trigger, but the Automation [2] is not triggering.

Any ideas of how to troubleshoot this?

[tom_l]

@e3e6

hassio installed on RPi4B

Hassio was retired four and a half years ago.

Pretty sure you do not have “hassio” installed. You have a Home Assistant OS installation.

[e3e6]

OK, let me fix that.

[Patrch]

I am quite new to this and probably a bit late but I found reading logs was the most beneficial. I put even in some automations extra logfile writes to track what exactly was happening and i found out early on that alot of things are errored and warned in the logs that do not come out at all in the configuration checks.

One other thing is restarting… some things work it seems by just updating the configuration.yaml and doing a reload of it … sometimes it works when doing quick reload, sometimes soft restart and finally when all else fails i do a full reboot which solves some other issues that it seems the restart does not fix. … here is something i found interesting around that

Changes to configuration.yaml, do I need to restart HA every time?

No you do not. Reboot and restart are two very different things. Do not use the words interchangeably. The only time you need to reboot the host machine is when making changes to or upgrades of the host operating system. i.e. very rarely. A restart of Home Assistant is required when adding never before used yaml integrations. i.e. this is the first time you have used a particular yaml configured integration. If you have already got an instance of a yaml integration and you add another (or yo…

Additionally you have in the developer tools not just YAML checks but states area that I also found to be very helpful.