Automations (that use state conditions?) broke with 0.115.3 upgrade

I’m running HA in a python venv on a raspi 3b+. I upgraded HA from 0.114.4 to 0.115.3 on Friday evening, and a bunch of different things broke. Rather than try to cover them all in one post, I’m hoping to get help with the most pressing issue.

I have Insteon switches throughout the house. I’ve been using insteon-mqtt for a couple years (no recent changes on that front). Most switches trigger automations to turn on hue lights. For example, if I toggle the Insteon switch named switch.kitchen_island from Off to On, it should trigger the following automation:

<snip>
  # Kitchen Island On
  - id: a_kitchen_island_on
    alias: Kitchen Island On
    initial_state: "on"
    trigger:
      - platform: state
        entity_id: switch.kitchen_island
        from: "off"
        to: "on"
    condition:
      - condition: state
        entity_id: input_boolean.kitchen_island_bool
        state: "off"
    action:
      - service: hue.hue_activate_scene
        data:
          group_name: 'Kitchen Island'
          scene_name: 'Concentrate'
      - service: light.turn_on
        data:
          entity_id: light.kitchen_island
          brightness_pct: 100
<snip>

I see the mqtt activity in the home-assistant.log when I enable debug…

<snip>
2020-09-26 17:09:01 DEBUG (Thread-5) [paho.mqtt.client] Received PUBLISH (d0, q0, r0, m0), 'insteon/<REDACTED>/state', ...  (2 bytes)
2020-09-26 17:09:01 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on insteon/<REDACTED>/state: b'ON'
2020-09-26 17:09:01 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=switch.kitchen_island, old_state=<state switch.kitchen_island=off; friendly_name=Kitchen Island @ 2020-09-26T16:55:18.723421-07:00>, new_state=<state switch.kitchen_island=on; friendly_name=Kitchen Island @ 2020-09-26T17:09:01.833860-07:00>>
<snip>

…so I don’t think the problem is with the insteon-mqtt integration.

If I go to Developer Tools > States in the the HA web frontend, click on the “i” symbol to the left of switch.kitchen_island, and then toggle the switch from off to on, the automation doesn’t trigger either… though the LEDs on the Insteon switch do indicate that the switch has been turned on via the GUI.

I’m stuck at this point, so figured I’d post here for some assistance.

A couple things to note, since I’m not sure if they are related to the problem above.

1. Since the upgrade to 0.115.3, Home Assistant hasn’t finished loading. I see “Home Assistant is starting, not everything will be available until it is finished.” in the GUI. I let HA run overnight, and it the message was still there Saturday morning. I’ve since rebooted many times throughout the day while attempting to troubleshoot these issues. I don’t see any obvious errors in home-assistant.log.

2. Since the upgrade to 0.115.3, the recorder no longer makes changes to the database. I had been running mariadb on my raspi prior to the upgrade. In an attempt to troubleshoot the issue, I created a new mariadb on a Synology NAS and updated HA to use the new db. Four tables were created by HA after I updated the config to point to the synology and restarted HA. HA adds a new row to the recorder_runs table with every reboot. The schema_changes table has a single row. The events table and states table have 0 rows, even though plenty of states have changed throughout the day.

Is it possible the automation is failing because of the state condition and the fact that the recorder doesn’t appear to be keeping track of state at the moment?

Anyone have any tips on how to proceed?

1 post - 1 participant

Read full topic