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

Loader23 · September 19, 2020, 10:42am

Yep, thats one reason why I dont understand why it is not working.
My plugs that I controll over frontend are also not working anymore.

With that its working fine:

  - platform: template
    value_template: "{{ states('sensor.time') == states('input_datetime.start')[:5] }}"
  - platform: template
    value_template: "{{ states('sensor.time') == states('input_datetime.ende')[:5] }}"

New style it does’t do anything, not even logs:

  - platform: time
    at: input_datetime.start
  - platform: time
    at: input_datetime.ende

Its like HA does not see the values I set on frontend

Borwolf · September 19, 2020, 10:46am

First Happy Birthday Home Assistant! Thank you all for this awesome release.

My “media browser” can’t find any items. I added the map “media” using “Samba” and already edited the configuration.yaml to add “media_source:” but still no success.

Any body the same problem? Does somebody has an solution?

tom_l · September 19, 2020, 10:54am

Check Configuration / info and make sure you have actually updated to 0.115.

Your update could have failed.

rs443 · September 19, 2020, 10:55am

So I added my camera folder into homeassistant, but Media Browser panel is not showing up, am I missing something? I want to be able to play my camera recordings in the browser.

media_dirs:
  camera: /config/camera

2020-09-19 10:24:35 INFO (SyncWorker_5) [homeassistant.loader] Loaded media_source from homeassistant.components.media_source

Browser cache has been purged.

tom_l · September 19, 2020, 10:56am

That was not a reply to you. See the top right corner of my post.

Burningstone · September 19, 2020, 10:58am

You have a link to this app? I’d like to take a look at it as well, just out of interest.

Loader23 · September 19, 2020, 10:58am

Have 0.115.1. Also easy to see because he did not accept the seconds: /60 in the automation anymore. So the update was succesfull.

Mariusthvdb · September 19, 2020, 11:05am

I can post them if that’s ok (have 2, sorry) in a separate thread maybe? Must be a post on it on the Community for at least one of them… here’s a Home Assistant Community Add-on: AppDaemon 4 on this script

and the other one is made by Azogue, but I cant find it online any longer. could post that too

tried to reinstall AD3, but now I can not find it any longer… grr

here’s a new post: How to update these AppDaemon 3 scripts to AD 4

Coolie1101 · September 19, 2020, 11:12am

Thanks, but at this point I really don’t know what the issue is, but it’s a known issue as it was also reported by @philhawthorne and many others in different threads in the community, I think it’s core related but still unable to track it down, my resources is up by an average of 20%, and I’m at a loss as to where to look next, I mite just revert back to 114 until it gets sorted.

Maybe everyone experiencing this can compare integration in an effort to identify similarities?

Burningstone · September 19, 2020, 11:16am

Yes, please open a thread and mention me there. You can also send me a PM, whatever you prefer.

Could even be that AppDaemon 3 is not compatible with newer HA versions anymore.

thisIO · September 19, 2020, 12:56pm

The same! And TTS do to work!!!

Platform error tts.google_cloud - Error relocating /usr/local/lib/python3.8/site-packages/grpc/_cython/cygrpc.cpython-38-arm-linux-gnueabihf.so: backtrace: symbol not found

How to fix it?

inkblotadmirer · September 19, 2020, 1:00pm

Regarding my issues with getting Kodi running on 0.115:

Weekends (free time) are great – I fixed the issue in my setup with Kodi in 0.115. When originally setting up media centers I opened up port 8080 on the firewall, but neglected port 9090.

I vaguely remember an issue in a recent prior release where blocking port 9090 caused an issue but it was fixed on a point release – but it seems to matter now, even during initial setup (yaml or integration).

Perhaps a few clarifications in the documentation? There are 3 requirements for my setup:

port 8080 and port 9090 must both be open
allow remote control from applications on this system (specified already in the docs)
allow remote control from applications on other systems (only required if Kodi is running on a different network from HA – with this enabled Kodi listens on 0.0.0.0 for port 9090 instead of localhost)

With these changes the integration pretty much instantly finds Kodi and brings up the configuration dialog. Nice work on the integration!

Michel · September 19, 2020, 1:19pm

Anyone know why the Brother printer changed the uptime?
I don’t mind the change to a new format, but it now reads like: “Printermodel Uptime: 15 weeks ago”

It seems like it should be called something like “time since last startup” instead of “uptime” (which should be a timespan e.g. “15 weeks”)

yonny24 · September 19, 2020, 1:19pm

Trying to fix history stats on 0.115.1. Fixed the Percentage but now get:

Platform error sensor.history_stats - cannot import name 'DOMAIN' from 'custom_components.history_stats' (unknown location).

I’ve updated the init to:

DOMAIN = "history_stats"
PLATFORMS = ["sensor"]

Stuck. Please help

Do I need to remove it completely from custom components? Is it part of the core instead?

Thanks

anon43302295 · September 19, 2020, 1:25pm

Anyone tried changing their template conditions to the new ‘shorthand’ and done so successfully?

As an example:

condition:
  condition: template 
  value_template: "{{ trigger.to_state.state != 'off' }}"

I’ve tried it as

condition:
  condition: "{{ trigger.to_state.state != 'off' }}"

and

condition:
  conditions: "{{ trigger.to_state.state != 'off' }}"

Neither passes the configuration check

Loader23 · September 19, 2020, 2:12pm

I did some more testing. This is working:

- id: 'Test'
  alias: Test
  trigger:
  - platform: time
    at: input_datetime.start
  action:
  - service: switch.turn_on
    entity_id: switch.stecker_1

And this not:

- id: 'Test'
  alias: Test
  trigger:
  - platform: time
    at: input_datetime.start
  action:
  - service: >
      {% if states('sensor.time') == states('input_datetime.start')[:5] %}
        switch.turn_on
      {% else %}
        switch.turn_off
      {% endif %}
    entity_id: switch.stecker_1

Any Ideas how to make it work? Still in one automation of course.^^

tom_l · September 19, 2020, 2:14pm

No idea sorry. It looks right according to what I read in the release notes.

If the features of this release aren’t functioning as advertised hopefully a developer will take notice. If not please open an issue.

pav · September 19, 2020, 2:23pm

Just

condition: "{{ trigger.to_state.state != 'off' }}"

should do the trick …

anon43302295 · September 19, 2020, 2:26pm

As stated, that does not pass configuration check.

(I guess it could be an issue with the configuration checker not correctly identifying that this is now valid? But I’d rather not risk it tbh)

pav · September 19, 2020, 2:42pm

‘As stated’ ? My suggestion is different from your 2 trials. Just use the SINGLE line - works here …