Updates to Works with Nest
blog.google
blog.google
Home Assistant [1] has been a Github-topping repo for a while. You've seen it here on HN several times [2]. It's a Python 3 open-source home automation platform that runs on a Raspberry Pi or other home server. Local data, local control. It's been being bootstrapped by tinkerers who can handle YAML config files for a while but is getting much fancier these days.
When Google shut down Revolv hubs in 2016, they posted rationale about why your hub should be open and local [3]. This kind of move further justifies the argument.
As big companies clamor over access to your home, let's take a stand by demanding open standards, local data options, and local control.
[1] https://www.home-assistant.io/
[2] https://news.ycombinator.com/item?id=15521743
[3] https://www.home-assistant.io/blog/2016/04/05/your-hub-shoul...
[4] https://www.home-assistant.io/blog/2018/09/17/thinking-big/
Both perspectives have their validity of course. Your description is more applicable to someone interested in moving to Home Assistant after already having bought a bunch of proprietary devices. These network effects are exactly why it's so damn important that open protocols and projects are adopted and become standard, rather than these dead end "service" worlds of Google et al.
As HA approaches version 1.0, I hope more people will jump onboard.
> One of the most popular WWN features is to automatically trigger routines based on Home/Away status. Later this year, we'll bring that same functionality to the Google Assistant and provide more device options for you to choose from.
I'm sorry, but... What?
You're sorry that you've caught developers and users by surprise, but the main functionality that they want won't appear until some unknown time in the future? And they should just trust you that this will actually happen after you yanked the carpet out from under them once already?
Coming from the company that promised geoqueries on Firestore two years ago but still hasn't delivered
"Google. Don't believe a single word"
Background: I was the author of a mildly popular Google Buzz client.
Woah, woah, woah, hold up, I don't recall reading they said they were sorry at all.
[1]: https://support.google.com/youtube/forum/AAAAiuErobUSpDf7fr3...
Is there an app for "nearby houses with good stuff where nobody is home".
I am a heavy user of Nest (7 cameras, other accessories). I've fully bought into the ecosystem. I literally have no idea what's going on. It sounds to me who is only casually paying attention that they're killing off Nest and the Nest brand. Whether that may or may not be true, they need to understand the perception of their actions to their users. Do they really expect most people to say "Okay, I need to spend 10 minutes and read through exactly what this all means."
Now I'm left with the dreaded feeling that my Dropcams and Nestcams will no longer work in the near future.
Google has really damaged their brand because I no longer consider them reliable. If I buy a brand that is associated with Google, I expect that it will get changed in the next year or so into something that I can't comprehend or don't want, and it makes me want to search for alternatives.
I don't want to "merge" my accouns with Google Home. I want to keep my single account on Nest like I have for many years now, and I just want alerts and to be able to see my cameras. All this other nonsense that they're trying to pull me into is not what I want as a consumer, and it upsets me that Google is becoming this kind of company.
They are in many ways worse than Microsoft was at their worst. Before Microsoft used to be a monopoly on the desktop, but Google is now turning into a monopoly in my entire life.
Meanwhile, Nest has been dormant for most of its existence, releasing only a few features. But in terms of cameras it's the most reliable which is why I stick with it. But there are so many opportunities for them to improve this service and it feels abandoned. Instead of adding features, like animal detection or car detection, they are worried about how I log in or who my account is? That's just stupid.
https://appleinsider.com/articles/13/06/18/googles-nexus-7-t...
Hardware is hard, I get it. But just the handling of the Nexus 5X was inexcusably bad--to ship firmware that crippled the entire deployed fleet, and then shrug. Shame on me for buying more of their hardware.
And the compensation didn't happen until a lawsuit.
At best, I'd consider Google hardware to be disposable. That's how I treat my Chromecast devices that I still use. I'm not buying anything new from them if it costs more than making them disposable.
In HN's thoughts, how should Google have approached this?
(I do not work with or for Google in any capacity).
Google have a responsibility to their customers. In this case, the customers are the people that actually buy the hardware. It's not "Temperature As A Service".
Coincidentally, this was a few years after they backpedaled on a decision to disallow control of non-Hue bulbs (https://www.home-assistant.io/blog/2015/12/12/philips-hue-bl...) after public outcry.
I'm more annoyed by the API changes they've made over time that broke my integration with the bridge. At least there is a local LAN integration option though, and you aren't forced to integrate with a remote service that might be shut down unexpectedly.
It seems like product management and engineering wanted to do it quickly and didn't do enough customer homework.
Then they had to backtrack, still sounding like douches because of their "if we change our minds we will keep you informed" tidbit.
I'm genuinely curious about their Alexa support through the transition. Seems they are willing to give away customers who want nest and nothing else.
It sounds like they're going to keep a tight control of their relationship with Amazon on this one - I imagine the negotiations are going to be extremely tedious.
Google/Nest created an API for developers to use with an associated slogan to for marketing if end-user devices which people buy with a 10+ year plan of ownership because it’s built into their bloody homes.
That obligates Google to keep this stuff working for 10+ years, as is, no weasel words. No exceptions. Anything else is a scam.
Edit: looking at Google’s history they clearly don’t have the intention nor ability to do this. Im not buying anything Nest/Google Assistant ever. I’m not interested in time-bombed devices.
Update: consumers realized this years ago. This is why Google has to announce messaging apps two at a time and cancel them next year. This is why Microsoft products are so extremely popular on Android.
I wonder if the courts will agree this applies to content that web servers transmit to google’s crawler. If so, can I add such an agreement to my homepage, and claim it applies to all the http requests I initiate?:
> When you upload, submit, store, send or receive content to or through our Services, you give Google (and those we work with) a worldwide license to use, host, store, reproduce, modify, create derivative works (such as those resulting from translations, adaptations or other changes we make so that your content works better with our Services), communicate, publish, publicly perform, publicly display and distribute such content. The rights you grant in this license are for the limited purpose of operating, promoting, and improving our Services, and to develop new ones. This license continues even if you stop using our Services (for example, for a business listing you have added to Google Maps). Some Services may offer you ways to access and remove content that has been provided to that Service. Also, in some of our Services, there are terms or settings that narrow the scope of our use of the content submitted in those Services. Make sure you have the necessary rights to grant us this license for any content that you submit to our Services.
On the other side of the fence Apple breaks compatibility all the time (see OpenGL vs Metal 2). Yet you can run Windows 10 on comparatively lower specced hardware while still being able to run apps developed for Windows XP.
Do those binaries actually import OpenGL symbols?
The new Microsoft just cancelled UWP. Their latest attempt to scare the hell away all developers.
UWP is alive and well, just go check the BUILD 2019 sessions.
Apparently some keep missing the point that all new Windows APIs are based on UWP.
There is much so more to UWP that the store.
The only thing that are doing is bringing the legacy stacks (Win32, Forms, WPF) and the modern one (WinUI, UWP) under the same umbrella.
You see, they don't have the courage to admit defeat. Just let it die and pretend it never existed.
Those never got any traction to begin with. If people aren't using it, they wont miss it.
Guess what happened to those platforms?
Their new from-scratch rewrite is based on Python and web standards.
UWP was the fix to WinRT and UAP changes introduced by Sinosfky's team.
Again, UWP is not only for Windows Phone, all Windows 10 new APIs are UWP based, there isn't any Win32 version of them.
People are able to keep using their legacy skills to write new apps, because Microsoft seldom plays an Apple move, killing any possibility to keep using legacy stacks on modern OSes.
If you miss XNA you can go use MonoGame, which Microsoft even advises on MSDN nowadays.
And Blazor for Silverlight like use cases.
When WP needed 3rd party games to have a chance in the consumer market Microsoft killed their fully functioning and very popular xna platform without explanation. For a while there was no replacement and the standard response from Microsoft was silence.
Later Microsoft pointed to mono as a replacement. At that time, mono was slow, buggy and incomplete. In fact, for a long time mono was missing the asset pipeline tools. According to their official tutorials you had to dig up an old copy of xna and use their asset tools.
UWP was never about Windows Phone only, rather Windows Phone, HoloLens, XBox ONE, 2-1 devices and Windows 10 desktops.
So Windows Phone failed, plenty of scenarios still available on Windows 10 deployments.
How many companies that still care about the desktop at all are going to invest resources in Windows only frameworks and not something like Electron? How many of those that are writing native Windows apps are going to use UWP instead of Win32?
macOS is largely insignificant in many countries over here outside iOS shops, GNU/Linux hardly matters for consumers, the Web still fails short of many native scenarios and mobile devices are mainly for consumption.
I’m nowhere near Silicon Valley, but I can say that hardly any money is going into desktop software development. Companies are following Microsoft’s lead. Even c# shops are strategizing how to get rid of their Windows dependencies by going to .Net Core.
this is a bad metric, since a million user using the service for all of 1 minute at the same time is not the same as 1 user using it for a million minutes. As a business, i would rather the latter.
Time to live is the "proper" metric.
Edit: disagreement apparently but I’ve never seen a serious company that wasn’t in danger or recovering from a breech using it. Maybe it’s just coincidence.
In the all examples you mention, was it specifically Gsuite that was breached? I've always belived Gmail had fantastic security, so I'd be very interested to learn more about any breaches in their core gmail/gsuite offerings.
Just a slightly more reasonable timeline for switchover, but still Assistant-based.
At least they do jot hide their politics.
...until 18 months from now when the Android team has more political sway and we announce “Android Home”, a new unified home automation platform to bring all your devices together in one easy to use system, which will allow you to turn your lights off by simply blinking into one of the many Google cameras mounted in your home.
This will be followed in 2022 with the new “Chrome@Home” platform, which will revolutionize home automation by letting you send and receive Morse code messagess with your neighbors via innovative light-turning-off-and-on technology.
Finally, in 2025 we will announce the revolutionary “GoogleOne” home automation system which will allow you to set minimum reading-light thresholds for your teenage children who insist on reading in too-dark rooms simply by yelling “how can you even read in this room?? You’ll go blind if you don’t turn on a light!!” while standing in the appropriate room of your home.
If anything, some of these products will overlap in time causing great confusion.
Sorry Google, I need my house to work for the next 30+ years. Honeywell sucks, but they at least understand that.
I really wonder whether, if someone with any clout at Google read your comment, they would get the joke or not understand.
One example, the whole story with fragments, then now that they finally have a good story with constraint layout, after three years in the making, they are introducing a Kotlin based DSL.
At least the Chrome team gets a solid story with their PWAs, also supported by other vendors.
First they screw Sun and then don't bother to buy Sun's assets when given the opportunity.
Lots of third party JVM vendors are able to deliver improvements into the Java world, while staying in peace with Sun, now Oracle. Google being the exception.
https://en.m.wikipedia.org/wiki/List_of_Java_virtual_machine...
The Java community doesn't need Android J++.
Either he outbids you and then had the legal right to fuck with you for decades
Or he bids you up to some ungodly number, and you have to live with the fact that Larry Ellison forced you to burn billions of dollars for his personal gratification.
Either way, you just feel dirty.
I’ve understood this to be a pretty fundamental cultural thing with Google, where people are more likely to get promoted for shipping something new (rather than improving something that already exists). If this is indeed the case, it’s likely not something that a few employees reading HN can solve, but rather needs a big shift in process from the very top of the organization.
Ironically this agrees pretty well with what your parent comment said:
> the Google employees that read HN understand and even agree with this sentiment ... people are more likely to get promoted for shipping something new (rather than improving something that already exists)
If the Google elite like your product, it gets integrated into everything and you get promoted. You probably stay at Google long term. If your products are the ones that get cut, are you likely to be a long term Googler? Google is an exercise in selection bias for a group of people who don't understand supporting a product long-term.
Also: you can get promoted for a cancelled project, unless you're at the level where keeping the VP from cancelling it is within your duties.
Survivor bas.
See the other thread: https://news.ycombinator.com/item?id=19952069
In which some of the commentators seem to be arguing that openly expressing your opinion on Google's product strategy is treason, or at the very least above your pay grade.
Also, did no one at Google ever get the memo you never remove APIs, you deprecate - precisely because people depend on them?
Building anything on a Google platform is like building a house on sand.
Going forward, I will be very reluctant to build anything on a Google API.
25% Google Chrome for Android
25% Google Android for Chrome
50% Android Legacy Edition (deprecated)