Agreed. As someone in the market for a good heat pump, I'm already turned off by this offering. I don't want more features (air quality module) that are more points of failure and complexity. I just want an efficient heat pump that'll work reliably for a long time, integrate well with HA, and won't cost a kidney to install.
I appreciate that Tailscale runs the DNS server so it's one less thing for me to manage. Similarly, the built-in LE is just icing on the cake as it's one less thing to think about. Once https://github.com/hassio-addons/addon-tailscale/pull/89 is merged, running Home Assistant on a VPN with a LE certificate, would be such a quick setup for anyone.
Indeed, you can do all that yourself as you point out. Just last night I manually created a public domain to point to a ZeroTier address and ran the Lets Encrypt addon in Home Assistant to generate a certificate via the DNS challenge. Didn't take long, but there were many steps involved (creating a Google Cloud service account and configuring everything).
I've been having trouble adopting Tailscale. As so many others say, relying on another identity provider is unfortunate - I, too, worry what happens when Google decides to lock me out because some algorithm decided my account is fishy.
So instead of developing this SSH feature, I would have preferred to seen them work on their bug backlog.
In the meantime, I'm experimenting with ZeroTier. While it doesn't have the ease and cool magicDNS+LetsEncrypt feature, I think I'll survive with something more reliable.
One of the most frustrating aspects of being a software engineer is dealing with others that love to over-engineer. Unfortunately, they make enough noise that complex solutions are necessary that it gets managers scared about taking any easier, simpler solutions.
Thanks for the suggestion; I'm trying it out now. Looks like Chromecasts aren't supported, but they do have a Roku app. The Roku interface seems to be much better than Youtube TV's!
Agreed. Having to set up a raspberry pi or some other microcontroller is time consuming and the end product is ugly. I would like something small that connects to WiFi that operates off battery or could be plugged in permanently.
I recently purchased Wyze's sensor starter kit and have been quite impressed. The contactless sensors are tiny and have decent range to the corresponding bridge. Now Wyze just needs a documented, public API.
Hence why the above poster said different use cases and why comparing between them is ridiculous. Using ObjectEach() for every field to reach parity with json.Unmarshal is unconscionable.
I've been paying rent with www.rentpayment.com which unfortunately serves up their home page with multiple logins over http. Naturally, emails and tweets to their support go ignored. Maybe they'll finally respond after more people ask them why they're "non-secure".
I've been using this chrome app for many months and enjoy using it immensely. I do not need the bells and whistles of Plex. Furthermore, every time I attempted to stream a movie from Plex, chromecast had buffering issues.