I just wish more of these companies would add support for a locally runnable IFTTT equivalent, or at least something like MQTT support so you can bake your own.
Google rolls out “If This Then That” support for its $200 OnHub router
31–40 of 196 posts
Re: Google rolls out “If This Then That” support for its $200 OnHub router
#32Earlier quoted context omitted.
Curious: what do you do with the management app? I have an Apple Airport thing and had a similar experience - years of buying cheap routers then suddenly I had one that "just works". To the point that I haven't had to open/use the administration panel in an absolute age.
The app also gives you insights into what's happening with your OnHub -- per device traffic sums, speed tests, alerts, etc. And we're constantly improving it. IMHO that's the real win with the OnHub; the router itself is constantly upgraded with up to date firmware with security updates and new features. And the mobile app that administrates it is constantly getting new features. Maybe I should transfer to marketing.
What kind of firmware / security updates do you get with OnHub? Aren't firmware updates dangerous if everything is working perfectly (the possibility to introduce issues)?
Re: Google rolls out “If This Then That” support for its $200 OnHub router
#33Until they discontinue support and turn the service off in a 18 months. It's hard to put any faith in google products anymore, especially with the new alphabet revenue strategy put into place.
The opinions stated here are my own, not necessarily those of Google. If you are referring to Revolv, Nest/Revolv stopped selling the device the day Nest acquired them (Oct 2014), and they are also issuing refunds to anyone that contacts them[0]. The other major hardware cancel I know about was the Nexus Q which Google also provided a full refund for anyone that contacts them. Sure, Google could cancel it, but they s…
Re: Google rolls out “If This Then That” support for its $200 OnHub router
#34Re: Google rolls out “If This Then That” support for its $200 OnHub router
#35Until they discontinue support and turn the service off in a 18 months. It's hard to put any faith in google products anymore, especially with the new alphabet revenue strategy put into place.
The opinions stated here are my own, not necessarily those of Google. If you are referring to Revolv, Nest/Revolv stopped selling the device the day Nest acquired them (Oct 2014), and they are also issuing refunds to anyone that contacts them[0]. The other major hardware cancel I know about was the Nexus Q which Google also provided a full refund for anyone that contacts them. Sure, Google could cancel it, but they s…
That's an image thing, and I'm sure you can come up with all kinds of historical facts on why that image is not right, or not right anymore, but that hardly helps fix the image.
I think that if Google really wanted to fix that image, they could do revolutionary stuff like promise long term support, or publish a phone number.
EDIT! westernmostcoy pointed out that actually they do, clearly, publish a phone number, which is pretty decent of them. I got the HN points anyway so it's too late now, but still, good to see! Maybe I should read a site before I criticize it.
Re: Google rolls out “If This Then That” support for its $200 OnHub router
#36I'm happy that routers are finally getting the UX treatment they deserve, and their target market isn't for people who know the difference between the two, but OnHub should keep the nitty-gritty details accessible to power users if they so wish. I eventually had to return the router and go back to forcing 5Ghz on my old one.
Re: Google rolls out “If This Then That” support for its $200 OnHub router
#37Re: Google rolls out “If This Then That” support for its $200 OnHub router
#38How does IFTTT make money? I can't figure it out.
Re: Google rolls out “If This Then That” support for its $200 OnHub router
#39I just wish more of these companies would add support for a locally runnable IFTTT equivalent, or at least something like MQTT support so you can bake your own.
It ended up working, but because the comms had to go through IFTTT servers, the lag was something like 10-15 seconds, which is awful when you want to just turn on a light.