Visual Editor or Yaml

Configuration
1

Can someone explain to me why some integrations can only be added to Yaml ? In other words, why not using the Visual Editor for everything, which is so much easier for low-level techies like me ?

2

This is the important section: https://www.home-assistant.io/blog/2020/04/14/the-future-of-yaml/#the-future-of-yaml

So all new integrations that communicates with devices and/or services will use UI configuration. Existing ones are slowly being moved over.

These ones will always have YAML available (but may also have a UI method):

  • Integrations that integrate transports. These integrations allow users to define their own protocol, e.g., MQTT, serial, GPIO.
  • Integrations that process Home Assistant data and make this available to other integrations, e.g., template, stats, derivative, utility meter.
  • Integrations that provide automations, e.g., automation, device_sun_light_trigger, alert.
  • Integrations that help controlling devices and services, e.g., script, scene.
  • Integrations that expose Home Assistant data to other services, e.g., Google Assistant, HomeKit.

Most things a setf described “low-level techie” such as yourself wants to do can be done in the UI.

For people who prefer the power of YAML (there are a lot of them) these advanced features can still be used.

Don’t think of YAML as a programming language. It is more like a recipe.

give_me_this_integration:
  - configure_it_with: this
  - also: this_thing_as_well

It is relatively easy to learn. Here are some tips:

http://thomasloven.com/blog/2018/08/YAML-For-Nonprogrammers/

3

Thanks for the explanation and also for Thomas Lovén - YAML for Non-programmers

4

Embrace the power of the YAML and come to the dark side…

:laughing: