you are viewing a single comment's thread
view the rest of the comments
[+] -8 points 1 year ago (12 children)

Home assistant is horrible from a software and configurability perspective but it's the best tool out there in its class

  • source
  • parent
  • hideshow 12 child comments
  • [–] 5 points 1 year ago (6 children)

    Genuine question: what makes you label it as "horrible" - which is quite a strong word - and what should it be doing differently, in your opinion?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 2 points 1 year ago (5 children)

    Completely overhaul the complex configuration, it's incredibly difficult to do simple things like creating a button on my dashboard to stop my fish tank pump for 15 minutes. Or to take photos when unifi protect camera AI detects a human, and display that on the dashboard. They are already sensors but building controls for any of these actions and automations relies on bizarre hacks and insanely complex yaml. Or creating morning routines for my lights based on a number of factors, you need countless plugins for basic configurability or basing lighting on sunrise/set times. It should be easy to create controls to do things like disable a routine for a few days.

    The programmability is poor, it's like it was built by a bunch of hobbyists instead of software engineers.

    And stop deprecating built in features with extremely short notice.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 4 points 1 year ago* (4 children)

    Sure it can improve in some places but saying it is horrible is really over stating it.. It was never meant to be 'programmable' but configurable.

    Now for your fish tank issue... That seems like the easiest automation to make..

    • Trigger on button helper press
    • Turn off pump
    • Wait for 15m delay
    • Turn on pump

    And then just add it to dashboard. Not really sure how that's horrible or difficult?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 0 points 1 year ago (3 children)

    Ran into issues with it conflicting with other routines that control the fish tank pump too

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 1 year ago (2 children)

    Not sure how that would conflict with anything.. Maybe a schedule? Then just add an override toggle helper that you check in your schedule.

    I feel like you're trying to use it in your specific way. Instead of using home assistant as intended. Sure that's a valid criticism for your use cases. But it doesn't make home assistant objectively terrible imho.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 1 year ago (1 child)

    How do you build controls to toggle automations as you described?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 year ago

    You can either directly disable an automation e.g. automation.turn_off: ... or set/read the state of a helper entity that you use to disable certain functionality in another automation. There are probably more tricks too. Though I try to make my automations as atomic as possible so they don't need to be connected this way.

  • source
  • parent
  • [–] 2 points 1 year ago (4 children)

    What? The first time I started homeassistant it autodiscovered 90% of my IoT stuff

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 1 year ago (3 children)

    Same for me, but any real automations are a massive pain. Like I said, nothing is better though

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 1 year ago (2 children)

    Ah yeah, YAML is definitely not the best tool to do that. I resorted to Node-RED for any more convoluted flows

  • source
  • parent
  • hideshow 2 child comments