4 ms·

Has Home Assistant settled on what you can configure via YAML and what needs to be done via the web UI yet? I left the ecosystem last year after the split beca

Has Home Assistant settled on what you can configure via YAML and what needs to be done via the web UI yet? I left the ecosystem last year after the split became too hard to mentally keep track of.

altano 5y ago
nope
balloob 5y ago
It’s all clearly defined in ADR-007 https://github.com/home-assistant/architecture/blob/master/adr/0007-integration-config-yaml-structure.md https://github.com/home-assistant/architecture/blob/master/a... The TL;DR: Authentication for devices and services are via the UI only (to deal with OAuth2, refresh tokens, auto-updating IPs via mDNS). Automations/scripts/scenes are both YAML or UI.
johntash 5y ago
What did you switch to, if anything? I eventually just stopped updating altogether due to the constant breaking changes, but haven't settled on anything else yet.
- snapetom 5y ago
  I bought a Hubitat earlier this year. It just works. GUI's a bit dated, and you kind of have to get used to the philosophy. However, once you get the hang of it, it's reliable, easy, and flexible enough for my needs.
- Kstile 5y ago
  Not OP, but in the same boat. One by one my integration’s have been failing over the last 4 years. I have no idea how my alexa integration worked originally, less idea now. My kids enjoyed “alexa, TV off” while it lasted. Started by moving all of my automations to node-red. Most of my z-wave devices I’m interacting with directly over MQTT. After the bumpy switch to z-wavejs everything has been stable.
a254613e 5y ago
Officially yes, practically no. It's defined, but it's still a total mess as not everything is updated completely to support UI configuration.
snapetom 5y ago
Of course not. Now there's a third way - Blueprints. I've bitched about HA before and won't rehash all of it. The project requires a lot of time investment and the devs care mainly about playing with the latest tooling. From introducing and sunsetting a major installation method in the span of ~4 years to dropping Python 3.7 despite it not being EOL until 2023, I don't have time or patience to relearn everything with every little release. Switched to Hubitat earlier this year. The GUI is ugly and there's a small learning curve. However it just works.
- etedor 5y ago
  I’ve been increasingly annoyed by the forced migrations from yaml-configured components to the terrible integration system and have started thinking about alternatives. Can you expand on your move to Hubitat? How’s the support for non-native integrations?
  - robalfonso 5y ago
    Hubitat user here as well, It's ugly but has been pretty solid for me. It's definitely punching above it's weight class in terms of what it cost. Hubitat has a groovy ide so you can write your own integration if necessary and the community is pretty good, I've rarely found something that doesn't already have an integration.

Has Home Assistant settled on what you can configure via YAML and what needs to be done via the web UI yet? I left the ecosystem last year after the split became too hard to mentally keep track of.

altano 5y ago

nope

balloob 5y ago

It’s all clearly defined in ADR-007 https://github.com/home-assistant/architecture/blob/master/adr/0007-integration-config-yaml-structure.md https://github.com/home-assistant/architecture/blob/master/a... The TL;DR: Authentication for devices and services are via the UI only (to deal with OAuth2, refresh tokens, auto-updating IPs via mDNS). Automations/scripts/scenes are both YAML or UI.

johntash 5y ago

What did you switch to, if anything? I eventually just stopped updating altogether due to the constant breaking changes, but haven't settled on anything else yet.

snapetom 5y ago
I bought a Hubitat earlier this year. It just works. GUI's a bit dated, and you kind of have to get used to the philosophy. However, once you get the hang of it, it's reliable, easy, and flexible enough for my needs.
Kstile 5y ago
Not OP, but in the same boat. One by one my integration’s have been failing over the last 4 years. I have no idea how my alexa integration worked originally, less idea now. My kids enjoyed “alexa, TV off” while it lasted. Started by moving all of my automations to node-red. Most of my z-wave devices I’m interacting with directly over MQTT. After the bumpy switch to z-wavejs everything has been stable.

a254613e 5y ago

Officially yes, practically no. It's defined, but it's still a total mess as not everything is updated completely to support UI configuration.

snapetom 5y ago

Of course not. Now there's a third way - Blueprints. I've bitched about HA before and won't rehash all of it. The project requires a lot of time investment and the devs care mainly about playing with the latest tooling. From introducing and sunsetting a major installation method in the span of ~4 years to dropping Python 3.7 despite it not being EOL until 2023, I don't have time or patience to relearn everything with every little release. Switched to Hubitat earlier this year. The GUI is ugly and there's a small learning curve. However it just works.

etedor 5y ago
I’ve been increasingly annoyed by the forced migrations from yaml-configured components to the terrible integration system and have started thinking about alternatives. Can you expand on your move to Hubitat? How’s the support for non-native integrations?
- robalfonso 5y ago
  Hubitat user here as well, It's ugly but has been pretty solid for me. It's definitely punching above it's weight class in terms of what it cost. Hubitat has a groovy ide so you can write your own integration if necessary and the community is pretty good, I've rarely found something that doesn't already have an integration.