No, you cant. Neither for the next example. Think of it like the AND and OR condition logic.
Only if you understand jinja.
ok thanks and yes, was confused there because conditions are being AND’ed by default so don’t need that kind of attention.
still if the single line
conditions:
were to be taken out, it would still be clear to be a set of conditions under the condition: not block?
sorry my bad: this is wrong:
needs to be:
- >
{{states('device_tracker.life360_marijn') != 'home'}}
or on 1 line:
- "{{states('device_tracker.life360_marijn') != 'home'}}"
well, yes, I guess you’re right there.
hope we can soon use the shorthand way for templates in triggers too! and the expand() on state.
Leading on from that (and I think this just exposes a lack of understanding on my part with the way things are expressed) does this work?
condition:
- condition: not
conditions:
- condition: state
entity_id: trigger.to_state
state: 'home'
Not sure, trigger.to_state is a state object not an entity. I’m going to say probably not. Try it and see.
Same here. Just filed a bug. Log is filled with errors about Pillow and PIL, and all sorts of nonsense. Had to roll back to a snapshot to recover.
It died on the same day as it’s birthday…
another one please…:
# trigger:
# -----
condition:
>
{{trigger.to_state.state|int in [0,1]}}
action:
- service: notify.notify
data:
title: All ok
message: Still fine
- condition: # <---- why is this wrong?
>
{{trigger.to_state.state|int == 0}}
The first condition (the condition block) works fine (that is, config check ok’s it). But when I try to use the same syntax in the action block, it wont go.
Only this works:
- condition: template
value_template: >
{{trigger.to_state.state|int == 0}}
I’ve also tried:
- >
{{trigger.to_state.state|int == 0}}
and
- condition: '{{trigger.to_state.state|int == 0}}'
doesnt the shorthand yet work in the listed action block?
- "{{trigger.to_state.state|int == 0}}"
(I had the same problem further up the thread, or maybe in a different thread)
Glad I’ve managed to get upgraded now smoothly after initial issues with broadlink and history stats. History stats is still in my custom components folder with just the unit_percentage changed to percentage nothing else.
But still unsure whether that is a custom component anymore and can get rid of it.
I apologize if this has been asked, I skimmed and searched but not find any answers. Prior to 115, Any cameras i displayed in lovelace using a picture entity card, could grow to full size by doing a long hold on my phone, or a click/hold on my browser. I notice that is not working anymore. I have two instances of HA running, but with the same cameras and same lovelace. 114.x works as before 115.2 does not. Is there a new option/feature/breaking change I need to read up on? Any assistance is appreciated
Is anyone else having trouble with the Xiaomi Vacuum component since 0.115?
2020-09-24 08:25:53 WARNING (SyncWorker_19) [homeassistant.components.xiaomi_miio.vacuum] Got exception while fetching the state: Unable to discover the device 192.168.0.152
I just updated to v115.
Does anyone know if the update breaks the custom variable component (rogro82/hass-variables)?
Thanks!
and there is even an easy fix. Even better!
1 Like
0.115.3 is out. Lots of fixes.
1 Like
yep, and now leave out data_template too 
does ‘had’ imply you have found a way to do it? Or should we wait for an update to use shorthand condition templates in the action block
Has anyone noticed the Supervisor pages not auto refreshing? When stopping a add-on, even when checking for a new release it doesn’t show until a ctrl+r is done. Never had to do that before.
impressively broke so many things that I cannot even start counting as webui is dead (404). hm
Yes, that happens to me too, I’m not sure if it was with v0.115 or it already happened in v.0.114
@frenck @balloob https://github.com/home-assistant/core/issues/40148
This broke my audio-based TTS automations, it’s affecting a ton of users, it has not been assigned to anybody, is there a maintainer? Please take a look, this will never be fixed by the looks of things, it’s been open for several days now, 0.115.0 broke the google_cloud tts integration.