[aagha]

What utter BS!

> "After that, your router will still work, but it will not receive any new software features or security updates, and performance cannot be guaranteed. You will not be able to use any Google Home app features to do things like update network settings, add devices, or run speed tests. And Google Assistant commands like “Hey Google, pause my Wi-Fi” will also not be available." [0]

It'll work, but you won't be able to control it in any way!

0 - From the email I received telling me support was ending

[cube00]

Speaking of BS

> Since OnHub routers were introduced 6 years ago, a lot has changed. In 2022, support for these older devices will end.

Given the devices were over spec'ed to allow for future expansion I highly doubt they're outdated already.

[ineedasername]

My router is about the same age, and with a 200Mbs dl speed and ~20 devices attached (no more than 6-8 actually in active use at the same time) everything still works fine all these years later. No one every complains when a few of us are streaming video and someone starts downloading > 20GB Steam game-- the router adjusts, streams continue, Steam uses whatever is left over, etc.

[ocdtrekkie]

Reminds me of my Nexus Q: An extremely high quality, overspecced device, that Google deleted in order to replace the functionality with Chromecast, a drastically weaker, much poorer quality product. But hey, it sold better.

[dmitrygr]

That story is not as simple as you make it sound...

<dissolve/fade to flashback>

The team was "android at home" and the year was 2012. This was google's first effort at home automation, and besides $60 lightbulbs you could turn off wirelessly that nobody at the time needed, we had the Q. The main focus for Q was audio. Fancy, high quality audio. It had a very nice amp. It even had very fancy hardware to allow synchronized audio playback without software resampling (an oscillator we could change the frequency of to pull it to master's freq). There was a second device in the works - a cheaper one, since Q was not at all cheap to make. We had a huge TV in our area of the building. And one day, on said TV, we saw the announcement of chromecast. By google. This was the first any of us heard of it. It did 90% of what our device did, but we were targeting $xxx and it was $15... At this point in time, the android and the non-android parts of google did not communicate much, and kept many secrets from each other. I doubt the folks in the chrome team even knew of our project. At google IO we took preorders for the Q, but given this new "chromecast" thing, it made no sense to continue, so everyone who pre-ordered one got one for free, and no support was ever provided, nor were any updates. In theory, the android bits for it are published and you can build android for it just fine.

[ocdtrekkie]

Obviously that is an example of incredible corporate dysfunction. But perhaps you would know, because it always blew my mind: Is there any reason the Nexus Q couldn't have been adapted to at least... be a Chromecast? The Nexus Q's function in YouTube and such was directly replaced by the Chromecast function... and I presume processing power wasn't an issue...

It feels like if there wasn't an insurmountable incompatibility issue, the Nexus Q could've/should've been able to run alongside Chromecast as a high-end version... and probably still work today if a single "convert to Chromecast" sort of update had been developed for it.

I still have it somewhere... easily the nicest piece of hardware I ever owned, and disappointingly, the one that lasted the shortest time.

[dmitrygr]

Its successor (now android tv) do have this ability. All work on q stopped at that time

[kingcharles]

Work. Now defined as simply "it will absorb power and gently warm the surface upon which it is placed."