2 ms·

> Especially within a VM (or bare metal) it's a really good experience. I've been using the Docker container for a couple years without incident. Like you, the

by florbo 3y ago

> Especially within a VM (or bare metal) it's a really good experience. I've been using the Docker container for a couple years without incident. Like you, the only integrations that occasionally broke have been custom components. While I agree that automations and scripts have been very stable, I've never really been a fan of the new automations and scripts UI, though, so I just stick to editing the YAML definitions manually. Great to have that option.

alex3305 3y ago
> I've been using the Docker container for a couple years without incident. Before I ran HA Supervised [1], but that was a pretty poor experience. It broke every so often because of some sudden software incompatibility because Supervisor was silently updated in the background. And it really broke everything instead of having a grace period and/or sending me a notification. > I've never really been a fan of the new automations and scripts UI, though, so I just stick to editing the YAML definitions manually. Same here. Although things seem to improve in the next version with copy-paste support in the Automation Editor [2]. I would love being able to edit my YAML automations though. Did you also known about a little known feature that you can setup different automation sources? Just like this: automation: !include automations.yaml automation foo: !include_dir_merge_list automations/ automation bar: !include_dir_merge_list automations2/ Although not _best practice_ per se, you can have both UI and YAML automations at the same time. This is especially useful when you want to use Blueprints [3]. 1. https://www.home-assistant.io/installation/linux#install-home-assistant-supervised https://www.home-assistant.io/installation/linux#install-hom... 2. https://rc.home-assistant.io/blog/2023/05/31/release-20236/#copy-n-paste-support-in-the-automation-and-script-editors https://rc.home-assistant.io/blog/2023/05/31/release-20236/#... 3. https://www.home-assistant.io/docs/automation/using_blueprints/ https://www.home-assistant.io/docs/automation/using_blueprin...

by florbo 3y ago

alex3305 3y ago

> I've been using the Docker container for a couple years without incident. Before I ran HA Supervised [1], but that was a pretty poor experience. It broke every so often because of some sudden software incompatibility because Supervisor was silently updated in the background. And it really broke everything instead of having a grace period and/or sending me a notification. > I've never really been a fan of the new automations and scripts UI, though, so I just stick to editing the YAML definitions manually. Same here. Although things seem to improve in the next version with copy-paste support in the Automation Editor [2]. I would love being able to edit my YAML automations though. Did you also known about a little known feature that you can setup different automation sources? Just like this: automation: !include automations.yaml automation foo: !include_dir_merge_list automations/ automation bar: !include_dir_merge_list automations2/ Although not _best practice_ per se, you can have both UI and YAML automations at the same time. This is especially useful when you want to use Blueprints [3]. 1. https://www.home-assistant.io/installation/linux#install-home-assistant-supervised https://www.home-assistant.io/installation/linux#install-hom... 2. https://rc.home-assistant.io/blog/2023/05/31/release-20236/#copy-n-paste-support-in-the-automation-and-script-editors https://rc.home-assistant.io/blog/2023/05/31/release-20236/#... 3. https://www.home-assistant.io/docs/automation/using_blueprints/ https://www.home-assistant.io/docs/automation/using_blueprin...