‹ BackHN Continuity

Thread

Big Tech ruined the cloud, so we're renaming ours

212 points · 108 comments · 2sf5

  1. voidnullvalue · · focus · HN ↗
    Nabu Kasa keeps ignoring the elephant in the room of security and permissions. They have no native ability to set user groups and permissions. There is no serious RBAC. I guess it doesn't sell cloud subscriptions. I cant keep my children from affecting devices they shouldn't. I ended up replacing my automation with mqtt
    1. frantathefranta · · focus · HN ↗
      Their ethos is that Home Assistant should be deployed in a non-complicated way and that many things that "IT people" want to do with HA are not actually necessary. I can't find the source but I recall frenck (one of the lead devs) explaining that people ask him about stuff like setting up HA using Terraform and he just wonders why someone would want that.
      1. hobofan · · focus · HN ↗
        That the default should be non-complicated isn't necessarily in conflict with features for power users, and I feel like in the HA forums it often is portrayed as an unresolvable conflict, when it isn't.

        I do think the maintainers are getting better about it. The releases over the past year have reworked a lot of things to be more intuitive for casual users while also being more flexible for power users, but there is still a lot of ground left to cover.

        I think with the growing popularity, and expansion of fields of use, this is something they'll ultimately have to reckon with. I've seen quite a few posts on the the HA subreddit, where it's being used for controls in e.g. hotels or other bigger buildings, because it has a great feature set and prevents vendor lock-in. There is no harm in also catering to those people & organizations.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.