@voltagex
I feel like this is the most accurate description of Home Assistant ever uttered.
@thechrisdantes it frustrates me, it could be so much better and so much more accessible.
@voltagex One of those cases: "this is shit, surely there's something better" only there really isn't
@fwaggle @voltagex yes! I dream of home automation software that is a stable and reliable core that supported 1 protocol (probably the ESPHome Protobuf one). It would would have maybe 1 or 2 releases a year, and would aim to have strong backwards compat guarantees. It would not be implemented in Python.
@wezm @fwaggle @voltagex home assistant is the 2000s windows of home automation - it is truly terrible but it has drivers for everything
@wezm @fwaggle @voltagex I often think it would be viable to run HA as a dumb driver host, and do all the automations in a nicer system which sits atop and uses the HA websocket to control stuff. But the activation energy of doing that is simply too high compared to keeping on doing stuff in my HA instance
@hailey @fwaggle @voltagex how do you picture a nicer automation system?
@wezm @fwaggle @voltagex all my HA stuff is basically functional reactive programming with templates + an automation at the end of the chain which applies some desired state template across to the actual entity. So a nicer system in my view would be something that just lets me do all that in a fit-for-purpose programming language (not jinja-in-yaml) that I can just edit as source code and commit to a normal git repo, rather than doing clickops for it all

@wezm @hailey @fwaggle

Independent components and progressive enhancement is the best way I can put it.

Like right now my HA system is complaining I've fucked up the DNS configuration somehow and this is stopping something??? working.

Also, LTS releases for HA and smaller, less frequent releases.

Monitoring built in to the system - it's running my house, it needs reliability, alerting and failover built in. It needs to act like building management appliance instead of a FOSS toy.

@voltagex @hailey @fwaggle "it's running my house, it needs reliability, alerting and failover built in. It needs to act like building management appliance instead of a FOSS toy." 1000% it needs to be more like hardware/firmware and less like a web browser (constant releases, kitchen sink of code).

@hailey @wezm @voltagex Yeah HA is *just* above my threshold for "this is terrible, fuck this". It mostly works, it's only about every couple of months that I end up in a "oh what now" scenario.

It's easier to just have angry tears every few months than to think about actually replacing/fixing it.

@hailey @wezm @fwaggle @voltagex I've considered this, and it would be very doable. HA has a decent event bus you can listen to, then you just call the HA services via the API
@chendo @hailey @wezm @fwaggle @voltagex appdaemon does this. You just write python classes. But, debugging is painful. (HA isn’t great but it’s definately better)
@chendo @hailey @wezm @fwaggle @voltagex getting the right combination of state names and attributes is also a pain, though I wonder if a code server that was state/attribute aware would make it better
@voltagex i regret i have only one fave to give this toot.