You could do that before with a condition, or a choose action if you need to do other things in the leave home automation.
I still don’t understand the difference from Choose or why this is stated:
3 Likes
Love this release - so much work done 
Especially on YAML side - not only UI.
After we have seen so many things moving away from yaml in the last releases, I am happy to see that the focus is not only UI based 
Please keep this direction 
1 Like
There is no “direction” to or away from YAML.
Integrations will continue to be moved to the UI and YAML will continue to be improved. The reasoning is explained here:
https://www.home-assistant.io/blog/2020/04/14/the-future-of-yaml/#the-future-of-yaml
1 Like
thank you for your quick response !
Before I update I always check the list of new features and I didn’t found one in 2202.5 on KNX.
LOG Message is
No communication to KNX bus possible - everything else works fine.
sorry for the question - but how can I redo the update ?
It does appear any longer in the update list of the HA web userinterface.
You can’t comment out in HA YAML. That would solve the need for this.
Sometimes you just need to disable something for testing, or seasonally, without having to re-make it later.
Hi Tom,
If your response goes for me i was aware that i could use a condition to check if the window is open, however, i didn’t find any way to run actions in case the condition is met but also when it’s not met.
If i am not mistaken in case the condition was not met (window open), the automation would stop.
I have explained and shared my automation in another thread that i opened before. Here is the link:
Hope this helps
Hmm, when I tried to comment out stuff in Automations.yaml before, it just disappeared from it. That’s why I was calling for the Disable feature. Or maybe this is only for the YAML view on the UI editor? That would be very confusing.
sure i can…i’m using yaml to d my automations. not gui
If you uncomment something in UI, it will be deleted. If you uncomment sth. in a .yaml file (e.g. using packages or YAML mode, it’s been uncommented but not deleted.
1 Like
I understand but is it mentioned somewhere in the documentation? It should.
Yes you could have used nested Choose actions for that.
To update Home Assistant to a specific version, use the command:
ha core update --version x.y.z
1 Like
Frenck and Homeassistant Team! Congrats for your amazing work!
But … Netatmo integration still does not working after upgrade 2022.03 and that’s a lot of time for Netatmo users. I hope you can fix this soon. Thank you again for your excelent work!
Hi 
!
We’d need a full log and more info to see what the issue is there. Please consider opening a new thread or a GitHub Issue for this providing more information like a full log excerpt (especially the beginning of the discovery and connection), infos about your installation (how many gateways, routers etc.) and maybe even diagnostic information:
Feel free to @-tag me.
Appreciate this doesn’t help anyone having issues but Netatmo is working fine for me, running HAOS on 2022.05. Worth noting it was working on 03 and 04 as well 
AFAIK the ‘Check config’ is automated upon clicking ‘restart’, you cant restart if it doesnt check.
1 Like
I call “Check config” even without need to restart - to be sure that my changes are right:
- made changes
- checked
- made changes
- checked
- …
- restart
For me, the old page was absolutely OK.
1 Like
Developer Tools → YAML → Check Configuration
and if you want to restart HA the button is on the same page.
I do know where it is.
The issue is “why to hide it so deep”
1 Like
It’s actually two clicks less than it was before. Making it less hidden
3 Likes