OnHub
231–240 of 641 posts
Re: OnHub
#232Very interesting. From looking at the specs, it looks like they're packaging a server and marketing it as a router. The configuration app is a very nice touch, routers have always a pain to configure. I'd love to stick this in my apartment (even though I can only receive a maximum of 10mb/s). As a side note, I'm surprised this isn't marketed alongside the Nest branch. It really has the look and feel of Nest products…
Basically this boils down to:
The average home router which has basic to no settings (many even lack channel selection) but usage is poor to suboptimal. I had a Netgear router which had broken internal static routing - and netgear's response was to buy a different router (even though you could set it inside the router...).
vs
Buying a higher power router or installing DD-WRT, Tomato or any of the other firmwares - now you have 1000 configuration items but you don't know which ones to tweak to give you good performance.
I believe most people fall into the middle - they want something that's easy to use with good performance but with the ability to adjust the 1000 configuration items if they wanted to.
Re: OnHub
#233So can I use it to do all the nerdy things I use my DD-WRT flashed router for? Like QoS, adblocking at the router, a separate guest WiFi, VPN support, MAC address filtering, etc?
Re: OnHub
#234From [1] Get started Welcome! To set up your OnHub, you’ll also need: Google account Android or iOS device Broadband connection Google account? That seems like an unnecessary requirement for a router. [1] https://on.google.com/hub/support/#get-started
(Disclaimer: I work for the same former-division-of-Google-and-now-Alphabet-subsidiary that built this, though I don't work on OnHub.) I think you need an account for cloud-based configuration, credential sharing, etc. Maybe it's not for everyone, but I think it makes sense as a product. I highly doubt they added a Google account requirement to improve ad targeting.
Re: OnHub
#235Earlier quoted context omitted.
If you have DSL, the modem and the router are the same box, so if you want your own, you have to throw out the one the ISP gave you, and configure yours by yourself. In practice, I bet you could just call up the ISP if you're having trouble, but I agree that an ISP has an incentive to give you a good unit to start with.
I haven't had DSL in a while, but when I did, the ISP just provided a modem with a phone line connector and a single ethernet connector. There's no requirement for DSL to bundle the modem and router.
Now, the ISPs that are using DSL (e.g., AT&T U-Verse which uses VDSL2 where it isn't FTTP) seem (from what I've experienced and seen with other people that have DSL-based service) to deploy all-in-one modem/routers (and, when they have services like TV and Phone as well as basic internet, to run them through the supplied all-in-one box, as well.)
> There's no requirement for DSL to bundle the modem and router.
Sure, its not a theoretical requirement, just practically what ISPs seem to do now.
Re: OnHub
#236Very interesting. From looking at the specs, it looks like they're packaging a server and marketing it as a router. The configuration app is a very nice touch, routers have always a pain to configure. I'd love to stick this in my apartment (even though I can only receive a maximum of 10mb/s). As a side note, I'm surprised this isn't marketed alongside the Nest branch. It really has the look and feel of Nest products…
To understand why certain products, which are seemingly unrelated to Google's core competency, have stayed with Google and haven't moved on to Alphabet, or why Google created a product such as OnHub and not Nest, you have to realize why all of these product are under Google - to track all the data that goes through them under the same generic/unified "privacy" policy, and then feed it into its advertising system. Tha…
Re: OnHub
#237Earlier quoted context omitted.
"As a side note, I'm surprised this isn't marketed alongside the Nest branch. It really has the look and feel of Nest products with the LEDs and the speaker aesthetic. Also surprised this isn't an "Alphabet" product." It pretty much is... it's their way of sneaking the 'home automation' core/aggregation box into people's homes masked as a wireless router (for now). I'm sure the capability you mention will come headin…
There are decent solutions to this already. INSTEON works great. It's got dual-band connectivity (wired and wireless) and you can either use a cloud hub if you want, or control it locally with a computer.
I know it's anecdotal, but the Insteon forums are filled with similar stories. I was a very early adopter and have been through several generations of devices, and I'm committed to using another platform when I start replacing the remaining Insteon switches that will inevitably die.
I wouldn't recommend Insteon to anyone. X-10 was more reliable in my house. I'm evaluating Zigbee options now.
Re: OnHub
#238Re: OnHub
#239Earlier quoted context omitted.
So not true, the RT-AC68U will walk circles around any eMTA an ISP will give you. The eMTA's cable companies give are expensive because a DOCSIS 3.0 modem is already $80 on average, adding a VoIP gateway and WLAN router plus a sufficient profit margin adds up.
Well, basically, a $200 home router will peak well before maxing out a 150 mbps connection unless you turn off all the QoS, UPnP and security features... but at that point you're better off just using the eMTA (which can handle the speed because it never had any of those features in the first place).
Once you start looking at the latency requirements to achieve 10GBps interconnects you're going to have issues with what you can reasonably expect from the $200 price range, but consumer networks have a long ways to go before that's going to even need to be thought about.
Re: OnHub
#240Am I the only one thinking this is Google's stealth echo competitor? It has all the right pieces. It's constantly connected to internet and power, zigbee/bluetooth/wifi, speaker, decent (enough) CPU, front end app. I'm sure they already have an API built into the back end. All they would need to do would be to build a gateway API for developers and add a mic.