0.113: Automations & Scripts, and even more performance!

[JurajNyiri (Juraj Nyíri)]

Thank you, this helped narrow down the problem.

I think it is related to onvif cameras.

I created ticket with logs here.

[CineMAC (Frank)]

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]

@tom_l

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

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]

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]

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 (the real one)]

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 (Francis)]

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

[123 (Taras)]

@Jonah1970

            value_template: "{{ states[trigger.to_state.domain][trigger.to_state.object_id].state  == 'Button B' }}"

Or just this:

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

[orange-assistant (the real one)]

@francisp

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

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

[Mutt (Muttley)]

@pnbruckner

with the help of some “alpha” testers

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 (Mark)]

Thank you @123 , that works great!

[Mariusthvdb (Marius)]

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

dnguyen800/air-visual-card

[kejXero (Henrik Næsby)]

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.

[pnbruckner (Phil)]

A couple of quick optimizations:

  trigger:
  - entity_id: sensor.remote2
    platform: state
  - entity_id: sensor.remote4
    platform: state

can be:

  trigger:
  - entity_id:
    - sensor.remote2
    - sensor.remote4
    platform: state

          - condition: template
            value_template: "{{ states[trigger.to_state.domain][trigger.to_state.object_id].state  == 'Button A' }}"

can be:

          - condition: template
            value_template: "{{ trigger.to_state.state == 'Button A' }}"

[123 (Taras)]

Partial echo.

[pnbruckner (Phil)]

Probably a better way to implement this is:

- trigger:
  - platform: state
    entity_id: binary_sensor.laundry_door_sensor
    to: 'on'
  action:
  - service: light.turn_on
    entity_id: light.laundry_lights
- trigger:
  - platform: state
    entity_id: binary_sensor.laundry_door_sensor
    to: 'on'
    for: '00:05'
  - platform: state
    entity_id: binary_sensor.laundry_door_sensor
    to: 'off'
  action:
  - service: light.turn_off
    entity_id: light.laundry_lights

[Jonah1970 (Mark)]

Thank you, I appreciate the feedback.

[123 (Taras)]

That’s the first time I’ve seen multiple triggers defined that way. That’s always been available? How have missed this?!? I’m going to have to experiment with it.

[pnbruckner (Phil)]

No, those are two automations.

[pergola.fabio]

Great tip!!