Did something change in away/home/device trackers after HA .39?

Configuration
1

As I’m using Vera to control most of my zwave stuff I was holding of to do the upgrade from .39.x. Yesterday I did upgrade to 43.1 and renamed my over 70 Vera devices.

All works fine and I’m enjoying all the latest and greatest again. However my home/away automation (see below) stopped working. I did not find any breaking changes relate to this in the docs from .39 > .43 and any of the versions in between.

I can still trigger them manually and it works. Also the device trackers all still work individually.

Any ideas?

  - alias: "Someone home"
    trigger:
      - platform: state
        entity_id: group.all_devices
        from: "not_home"
        to: "home"
    action:
      - service: input_select.select_option
        data:
          entity_id: input_select.Occupancy
          option: "Home"
      - service: input_select.select_option
        data:
          entity_id: input_select.alarm
          option: "None"
      - service: switch.turn_on
        data:
          entity_id: switch.vera_home_mode
      - service: alarm_control_panel.alarm_disarm
        data:
          entity_id: alarm_control_panel.ha_alarm
      - service: switch.turn_on
        data:
          entity_id: switch.otg_resume
      - delay:
          minutes: 1
      - service: switch.turn_off
        data:
          entity_id: switch.otg_resume

  - alias: "Away"
    trigger:
      - platform: state
        entity_id: group.all_devices
        from: "home"
        to: "not_home"
        for:
          minutes: 3
    action:
      - service: notify.mypushover
        data:
          title: "Presence"
          message: "All Away"
          target: ""
      - service: input_select.select_option
        data:
          entity_id: input_select.Occupancy
          option: "Away"
      - service: input_select.select_option
        data:
          entity_id: input_select.alarm
          option: "Away"
      - service: scene.turn_on
        data:
          entity_id: scene.all_away
      - service: climate.set_temperature
        data:
          entity_id: climate.opentherm_gateway_117
          temperature: '15'
      - service: switch.turn_off
        data:
          entity_id: switch.vera_home_mode
      - service: alarm_control_panel.alarm_arm_away
        data:
          entity_id: alarm_control_panel.ha_alarm
      - service: tts.google_say
        entity_id: media_player.family_room_home, media_player.kitchen_home
        data_template:
          message: "Alarm has been armed. Alarm will sound when motion is detected"
          cache: false
2

I would make sure your trigger is workings, perhaps group.all_device state is not making it from “not_home”. I would try with just one device_tracker for testing or try removing from: “not_home” in case it goes to “home” from unknown state.

  - alias: "Someone home"
    trigger:
      - platform: state
        entity_id: group.all_devices
        to: "home"
3

I would double check the group.all_devices state in the dev tools when you think it should be ‘not_home’. I had a group of devices that also had an input_boolean in it that I was using for an automation, and it stopped working after an upgrade (can’t remember which version exactly, but around .39ish). I noticed that instead of ‘home’ and ‘not_home’, it started reporting as ‘home’ and ‘off’. Once I removed the input_boolean from the group it switched back to ‘home’ ‘not_home’

4

Ok, solved.

For some reason I now have a group.all_devices and a group.all_devices_2. The first one was the original I created by creating a ‘real’ group (in groupviews.yaml) and had a typo in 1 of the devices. No idea why this was working before.

5

Something changed with the vera component in .40 that appended the vera device id to the HA device id to avoid collisions in naming

example:
switch.overhead_lamp
became
switch.overhead_lamp_23