0.113: Automations & Scripts, and even more performance!

naamah75 · July 25, 2020, 6:37am

Same issue for me, but tried a lot of time without success.

phairplay · July 25, 2020, 7:22am

Thank you but this didn’t help I had 100’s of line but nothing said why at the time it failed.

Jonah1970 · July 25, 2020, 9:33am

Hi @KennethLavrsen, you mention that you like having a standard yaml structure as you have many remotes. I would like to offer this variation which works well if you have multiple remotes performing the same function. This uses the Trigger State Object from https://www.home-assistant.io/docs/automation/templating/#zone to determine which entity triggered the automation.

- id: '1595451341852'
  alias: Kitchen Lights Remote
  description: ''
  trigger:
  - entity_id: sensor.remote2
    platform: state
  - entity_id: sensor.remote4
    platform: state
  action:
    - choose:
      - conditions:
          - condition: template
            value_template: "{{ states[trigger.to_state.domain][trigger.to_state.object_id].state  == 'Button A' }}"
        sequence:
        - device_id: 5320c28c7c1e45c580aa9a5ad9bc4432
          domain: light
          entity_id: light.kitchen_lights
          type: toggle
      - conditions:
          - condition: template
            value_template: "{{ states[trigger.to_state.domain][trigger.to_state.object_id].state  == 'Button B' }}"
        sequence:
        - entity_id: input_select.kitchen_scenes
          service: input_select.select_next
      - conditions:
          - condition: template
            value_template: "{{ states[trigger.to_state.domain][trigger.to_state.object_id].state  == 'Button C' }}"
        sequence:
        - entity_id: input_select.kitchen_scenes
          service: input_select.select_previous
      - conditions:
          - condition: template
            value_template: "{{ states[trigger.to_state.domain][trigger.to_state.object_id].state  == 'Button D' }}"
        sequence:
        - device_id: 92c52b6d053e42e5a472e7b017c60032
          domain: switch
          entity_id: switch.sonoff03
          type: toggle

Dayve67 · July 25, 2020, 9:44am

Not a big deal but I’m seeing this error in my logs since upgrading to 0.113
I do have the Add-on installed for Visual Studio code. Looked every where to change the mdi to the right one. is anyone else seeing the same?

jdbrookes · July 25, 2020, 9:46am

I had the same issue with home assistant never completing startup, so I rolled back to previous version.

I now suspect it was due to kodi in my config: https://github.com/home-assistant/core/issues/38160

There also seems to be an issue with 0.113 if you use tensorflow or onvif.

tom_l · July 25, 2020, 9:54am

I’m guessing that is from the VSCode add-on being added to the sidebar. You will have to wait for an update.

I have the same addon but I have not added it to the the sidebar so don’t see the warning.

Kanishkaz · July 25, 2020, 10:25am

Hi All,

I implemented the following automation using the new Choose action to turn on/ off lights based on a door sensor. I’m wondering if there’s a way to add a ‘for’ condition for the sensor on state to turn off the lights when the door is opened for 5 mins?

Right now I have it configured using a delay.

  trigger:
    - platform: state
      entity_id:
        - binary_sensor.laundry_door_sensor
  action:
    - choose:
      - conditions:
          - condition: state
            entity_id: binary_sensor.laundry_door_sensor
            state: "on"
        sequence:
          - service: light.turn_on
            entity_id: light.laundry_lights
          - delay: 00:05:00
          - service: light.turn_off
            entity_id: light.laundry_lights
      - conditions:
          - condition: state
            entity_id: binary_sensor.laundry_door_sensor
            state: "off"
        sequence:
          - service: light.turn_off
            entity_id: light.laundry_lights

JurajNyiri · July 25, 2020, 11:04am

Thank you, this helped narrow down the problem.

I think it is related to onvif cameras.

I created ticket with logs here.

CineMAC · July 25, 2020, 11:27am

Hi @all

I have a Problem with all the wonderful new features. In all the automations I received in visual studio the error message “property not allowed”. Uninstall and install again was no solution. When I check the configuration, the System display no errors. I guess the is a problem on my Visual Studio. Any Idea what can I do?

Many thanks
Frank

stephack · July 25, 2020, 11:31am

Correct. I added it to my sidebar as a test and it generated the error. Will probably be fixed with the next VScode update as mentioned.

tom_l · July 25, 2020, 11:41am

You can ask the author of the extension to update the schema to include the new features.

Here: https://github.com/keesschollaart81/vscode-home-assistant/issues

Or you can do it yourself locally: https://github.com/keesschollaart81/vscode-home-assistant/wiki/HowTo:-Update-the-schema's

valet · July 25, 2020, 11:44am

Hey guys,

I noticed some strange German translations within the “Server Management”-Page:

“Reload Input Booleans”
“Reload Input Numbers”
“Reload Input DateTime”
etc.

They’re called
“Eingabe-Booleans neu laden”
“Eingabenummern neu laden”
“Eingabe-Datums- und Zeitfelder neu laden”
etc…

In my opinion this is a strange german wording:

My suggestion here is:

“Umschalt-Helfer neu laden”
“Nummern-Helfer neu laden”
“Text-Helfer neu laden”
“Datum & Uhrzeit-Helfer neu laden”
“Dropdown-Helfer neu laden”

The functions are already translated within the "Helpers-Menu, the current translation kind of differs from these “Helpers-Menu”-translations in strange ways.

Am I the only one?

orange-assistant · July 25, 2020, 12:16pm

New bug introduced in this release. I would post it on github but I was blocked (by @balloob) because of my last feature request for the android app to make it accesible for more people - sad but true. Wonder what the Code of Conduct is actually for…

The bug is the following (reproduced on two different hass servers and various clients, mobile & desktop as well with various browsers and the android app Libre Assistant)

Opening any entity in lovelace, for example this one:

And clicking the wheel up right:

followed by a click on the tab “related” will give you this nice list of related entities:

they are clickable and in the past (prior to this release 0.113) they opened the entity directly.

The new behavior is that it’s not presented in front of this modal but behind - which is quite useless

francisp · July 25, 2020, 12:45pm

Just tried it out. It opens indeed behind the modal. Tested on 0.113.1.

123 · July 25, 2020, 1:26pm

Or just this:

            value_template: "{{ trigger.to_state.state  == 'Button B' }}"

orange-assistant · July 25, 2020, 1:36pm

Thank’s for confirming… hope some one will see this one day…

Mutt · July 25, 2020, 1:39pm

Just to be clear; this means a few idiots willing to break their test instances (with alpha code)
And does not refer to the quality of those testers

Jonah1970 · July 25, 2020, 1:53pm

Thank you @123 , that works great!

Mariusthvdb · July 25, 2020, 2:00pm

the more-info pop-ups on AirVisual card no longer work. Anyone else seeing this?

kejXero · July 25, 2020, 2:17pm

IKEA integrations - Any body else having isues with the ikea integration? in 0.113 i need to re-integrate my two ikea gateways to have connection to the lights. this has to be done again after a while.