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

I had the same issue with my MP1ā€™s, disabling my existing broadlink integration (removed the yaml) and restarting HA fixed the problem for me.

1 Like

Happy Birthday! Quite the Home Assistant birthday present! We all get to enjoy and participate in the celebration! Took the weekend opportunity to read the full release documentation and excited to do the update (unwrap the present)!
GO TEAM GO! Fantastic work and THANK YOU for all that everyone contributes!

Also seeing quite a few errors while using the mobile app.

['components/mobile_app/webhook.py', 202]

Anyone knows what I need to set to see my videos and movies when Kodi is selected as Media Player? I only see music library but only Artists and Albums categories.

Shutter Card issue now. Fixed everything else with 0.115.2. Then this pops up:

Custom element doesn't exist: shutter-card.
entities:
  - buttons_position: left
    entity: cover.living_room_cover
    name: Living Room
    title_position: bottom
title: Living Blind
type: 'custom:shutter-card'

Update: removed the entity_id and created the home assistant update identity id. Seems to be working now

It is ā€œjust workingā€ here.

Because 59/59==0 and 00/59==0

The / format asks if the number divided by what you specified results in ZERO.
It is not a time thing, itā€™s a number pattern thing.

Quickie answer: -
Because 0/59 has no remainder and 59/59 has no remainder
Wrap your head round that
:rofl:
Cheers
:+1:

1 Like

I held off updating until 0.115.2 but Iā€™ve discovered today that you can no longer force restart HA if there is a config error. I guess a reboot will be a workaround but the problem with this is that HACS wants me to restart after updating components there and HA wonā€™t let me.

Sadly, the config error report below is not the least bit helpful.

Invalid config for [automation]: invalid template (TemplateSyntaxError: unexpected '}', expected ')') for dictionary value @ data['action'][1]['data']. Got None. (See ?, line ?). 
Invalid config for [automation]: invalid template (TemplateSyntaxError: unexpected '}', expected ')') for dictionary value @ data['action'][1]['data']. Got None. (See ?, line ?). 
Invalid config for [automation]: invalid template (TemplateSyntaxError: unexpected '}', expected ')') for dictionary value @ data['action'][1]['data']. Got None. (See ?, line ?). 
Invalid config for [automation]: invalid template (TemplateSyntaxError: unexpected '}', expected ')') for dictionary value @ data['action'][1]['data']. Got None. (See ?, line ?). 
``
Where the heck do I start looking in my very extensive configuration files to resolve the above without any actual useful information?

So that means that every time pattern trigger will trigger at x:00?

so ā€˜/11ā€™ will fire at minutes 00, 11, 22, 33, 44, 55, 00, 11ā€¦?

That doesnā€™t seem like it meets the expected behavior.

if thatā€™s the case then the only time pattern triggers that make complete sense would be /1, /5, /10, /15, /20, /30. Everything else will end up with a spurious (and probably undesired) trigger at x:00.

1 Like

Happy Birthday and thank you all for a great job giving all of us such a great product.

The new media browser is fantastic. Can it also work with lms?

11 will as well. I agree this is unexpected and undesiredā€¦

Yep, 10 char min

No, this has pretty much always been the case, they have just banned /60

right. I put the ā€œ00ā€ in there but didnā€™t make it obvious. fixedā€¦kind ofā€¦

edit: fixed it better. :wink:

I must be honest though, I donā€™t understand *5

??

Iā€™m not sure what you meanā€¦

  - alias: random_test  # carry-on joke 
    trigger:
      - platform: time
        minutes: '*5'

But then Iā€™ve not needed it (I donā€™t think) so Iā€™ve never researched it

Edit: Iā€™m on my phone, I think the platform should be ā€˜time_patternā€™

Then I donā€™t understand /1. Anything divided by 1 never returns 0 (except 0), so hours: /1 only runs at midnight, and not every hour as I thought ?

1 Like

I could be mistaken but I believe going by the latest round of revelations that itā€™s not the result of the division. Itā€™s the remainder. As long as the remainder is 0 then it satisfies the trigger.

so 0/1 = 0 with no remainder, 1/1 = 1 with no remainder, 2/1 = 2 with no remainder, etc. all of these will trigger the pattern. So will 0/59 = 0 no remainder, 59/59 = 1 no remainder.

But 55/59 = not an integer so it has a remainder so will not trigger the pattern. neither will 61/60.

Someone please correct me if Iā€™m wrong.

1 Like