0.115: B-Day release! Media browser, tags, automations & WTH

Blog
164

You probably have templates that listen to all states or are listening to their own changes or making loops.

165

I most definitely do, but wasnā€™t an issue previously, and I didnā€™t see any changes that relates, or did I miss that?

166

Check the templates section of the breaking changes.
We will now update the template on every change of states you used in your template. If you use all states in multiple template sensors that will end in a loop.

167

Will do, does this only apply to scripts / automations, or sensors as well?

168

Sensors too.

169

well that is not very desirable and rather underlines my thoughts about that here

previously, entity_id: was a great tool to define ā€˜globalā€™ entities for the full sensor, And limiting the updating of the sensor to only that entity_id.
Hope we can get that back.

170

Is there a simple way to track these down?

Iā€™m not sure I truly understand what needs to be changed here.

171

I have absolutely no idea which change did it, but my IKEA Tradfri bulb which is managed by ZHA does finally report its state back to HASS, even if it was changed by the connected TRadfri remote. This makes me more happy than anyone here could possibly imagine. :slight_smile:

1 Like
172

Hi, anybody knows what append with sonoff integration ?

173

Also is it normal for HA to log errors while evaluating templates in the Template Editor in Developer Tools?

For example, just for testing purposes, entering the following, logs the error below.
{{% states.system_log_event %}}

Logger: homeassistant.components.websocket_api.http.connection.881958896
Source: components/websocket_api/connection.py:126
Integration: Home Assistant WebSocket API ([documentation](https://www.home-assistant.io/integrations/websocket_api), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+websocket_api%22))
First occurred: 6:39:30 AM (2 occurrences)
Last logged: 6:39:31 AM

* Error handling message: invalid template (TemplateSyntaxError: unexpected 'end of print statement') for dictionary value @ data['template']. Got '{{states.system_log_event %}}'
* Error handling message: invalid template (TemplateSyntaxError: unexpected '%') for dictionary value @ data['template']. Got '{{% states.system_log_event %}}'
174

Yes you can!
You have to make an Automation and select Device as trigger,
It should give you a drop down with turning on or off.

And as action select service wake_on_lan.send_magic_packet, just like you did before.

Works fine here!

Only thing I canā€™t figure out is how to make a correct automation for turning off my kodi instance.

1 Like
175

I did, not solving the issue.

177

The real_ip stuff has been removed in this release indeed, are you using emulated_hue as a custom component? As the code that is reference that error, does not existing in the Home Assistant code base.

178

907Ɨ1360 248 KB

:seven:
is a lucky number :slight_smile: from the whole :heart: I wish the entire HA / Nabucasa team to quickly, turn this project into a beautiful Unicornā€¦ like on the card :wink: you have potential for this!

What this project has achieved is incredible! Thank you, guys!!!

4 Likes
179

iā€™ve this warning in the log:

Logger: homeassistant.components.template.sensor
Source: helpers/config_validation.py:752
Integration: template (documentation, issues)
First occurred: 11:58:11 (2 occurrences)
Last logged: 12:14:00

The ā€˜entity_idā€™ option is deprecated, please remove it from your configuration

could be related to this template switch?

  - platform: template
    switches:
      camera_citofono:
        value_template: "false"
        turn_on:
          - service: media_player.play_media
            data_template:
              entity_id: media_player.nesthub0150
              media_content_id: http://192.168.1.12:8081
              media_content_type: "image/jpg" 
        turn_off:
          - service: media_player.turn_off
            entity_id: media_player.nesthub0150
180

Seems to be an issue with a python module.

Not sure how to fix

181

ItĀ“s true. I tried automation for turning off and nothing Working. Log is without error and the same in Development tools (turn_off not working). This is my automations:

- id: '1600429708808'
  alias: Vypnout Kodi
  description: ''
  trigger:
  - platform: device
    device_id: a357f157f92111ea9fa40********
    domain: kodi
    entity_id: media_player.coreelec
    type: turn_off
  condition: []
  action:
  - service: kodi.call_method
    data:
      method: System.Shutdown
    entity_id: media_player.coreelec
  mode: single
182

I have the same issue and it seems it breaks google cloud tts. Are you using the docker image, because it look likes itā€™s missing a library on the OS.

183

First of all: Happy birthday and thanks a lot for another awesome release. Great work by everyone involved indeed!

And now for a quick question: Is the ā€œstreamā€ integration now a part of the default_config?

The reason I ask is that I see it is loaded on my test instance, which is fairly stock/default.
However I cannot see it listed here: https://www.home-assistant.io/integrations/default_config/

I dont use default_config as it includes some element I donā€™t want to enable, so I try to keep track of what it contains so I can manually add what I need. Perhaps the new Media Player Browser use it or something like that?

Thanks.

184

The dev of the custom integration needs to update it to work with 0.115, although the last update was a few months back so hopefully still active
Suggest logging an issue on its github repository

1 Like