Been waiting for Google Assistant for over a year. Bought my Sonos system because of the promise from Sonos that Google Assistsnt would be available in late 2018. Very disappointed.
Moderator Note: Google Assistant is now available for use on Sonos. Read more here.
Page 2 / 3
One has to wonder if that's one of the reasons that Google is dragging their feet on this implementation. They certainly make more money selling their own hardware, and no money when Sonos sells a speaker.
I doubt they make much on their hardware. Their big moneymaker is data about you, so that they can sell targeted ads to you. The Sonos owner demographic is surely one that they covet.
I imagine there is a small licensing fee Google might be getting for each piece of hardware sold that using Google tech in some way, not to mention that users will be much more likely to pay for google services and buying other google hardware once they are in the eco-system.
i know people are not going to be happy with what i'm going to say, and this is third hand news, so dismiss it if you will.
but i know from a reliable source who was at Google I/O, that Google are blocking the release of assistant on sonos as it doesn't fit with their smart home strategy. details i don't know. but sonos are leaning on google hard to change their mind. it's otherwise ready for release.
the opinion from the insider was that it's just not going to happen anymore.
but i know from a reliable source who was at Google I/O, that Google are blocking the release of assistant on sonos as it doesn't fit with their smart home strategy. details i don't know. but sonos are leaning on google hard to change their mind. it's otherwise ready for release.
the opinion from the insider was that it's just not going to happen anymore.
Distressing, if true. But I have to imagine that there had to be some sort of legal agreement signed by both parties before Sonos would announce the plan, as they did. Seems like it would be expensive for Google to back out at this point, although not impossible.
but i know from a reliable source who was at Google I/O, that Google are blocking the release of assistant on sonos as it doesn't fit with their smart home strategy. details i don't know. but sonos are leaning on google hard to change their mind. it's otherwise ready for release.
the opinion from the insider was that it's just not going to happen anymore.
LOL. "reliable source"
If that was the case, blogosphere would be going nuts over it.
but i know from a reliable source who was at Google I/O, that Google are blocking the release of assistant on sonos as it doesn't fit with their smart home strategy. details i don't know. but sonos are leaning on google hard to change their mind. it's otherwise ready for release.
the opinion from the insider was that it's just not going to happen anymore.
LOL. "reliable source"
If that was the case, blogosphere would be going nuts over it.
Indeed. There are already plenty of 3rd party speakers that sport GA. Sonos may be asking Google to add features that Google is slow rolling, but this "reliable source" is BS.
https://www.tomsguide.com/us/pictures-story/1612-best-google-home-smart-speakers.html
The number of 3rd party speakers that integrate with GA is tiny compared to the number of products that integrate with Nest thermostats and yet Google is disabling that API on August 31st as part of their new product strategy. Also new GA products will come under the Nest brand going forward so it is not that far fetched to think the Sonos integration might also fall victim to this new reorganization. It will be interesting to see just how far Google will go with locking everything down.
Google is ADDING dozens of new devices to GA. They're doing just the opposite of "locking down". They want GA to control everything in the home.
https://www.cnet.com/news/google-assistant-quietly-gets-native-controls-for-a-bunch-of-new-devices/
https://www.cnet.com/news/google-assistant-quietly-gets-native-controls-for-a-bunch-of-new-devices/
https://www.cnet.com/news/google-assistant-quietly-gets-native-controls-for-a-bunch-of-new-devices/
Exactly. They want to control everything in the home by locking down the API that currently allows 3rd parties to control their stuff. By ending the "Works with Nest" program and associated API they prevent things like IFTTT from working with their products, As I understand it the replacement "Works wirh Google" API will not allow any third party be the master or central control for Google Nest products but will only allow control requests sent through a Google Nest Home Hub. The requirements are also going to be different for developers to get into the "Works with Google" program which is going to be intentionally limited to a small number of approved partners "to ensure better security". There is already speculation that the Amazon Echo is unlikely to get that approval (or will be unable to accept the restrictive requirements that will be imposed) and therefore may not be able to control Nest thermostats and cameras after August. Since Nest and Home Assistant are now part of the same Google Nest division it is unclear if these changes could extend to things like Google Home enabled speakers or if any of the new API restrictions impact the integration between Sonos and Google Nest voice assistants. It is just interesting that all of these things seem to align with the statement posted earlier from the "reliable source".
As a person who has invested heavily in Sonos and the Google echo-system I suspect, but hope I'm wrong, that come the end of the year there will be no announcement from Sonos about GA integration with a blog dated 1st November 2018 there gathering dust. I believe, opinion only, that Google will go there own way and cut Sonos out.
Google are slowly but surely expanding their product line espically those that dovetail with music listening. Hope I'm wrong but if I were Sonos I would be worried.
Google are slowly but surely expanding their product line espically those that dovetail with music listening. Hope I'm wrong but if I were Sonos I would be worried.
A couple problems with this rumor
- Google (not Sonos) stated that the integration was happening back in January. While that could change, you would think this change would have been thought out enough to not make the announcement if it was not a sure thing.
- The public beta is currently ongoing, at least according to the most recent reports. Why would beta continue if the project was being dropped? Although folks are not supossed to talk about beta, I think you there would definitely be news about it if it happened.
- Remember, part of the deal with the integration is that Sonos agreed not to sue Google for theft of intellectual property if they agreed to integrate with Sonos. If the integration is off, that means a lawsuit would be back on. Given the deep pockets of Google and the volume of google assistance in the wild, that's a lot of money.
- On the surface anyway, it seems like a very bad strategy. There are certainly advantages to having a closed system, but it's proven to fail in the long run when competitors catch up. Google doesn't have that big of an advantage where customers will shun all others in dedication to google. It's worked for Apple for a time, but not so much anymore.
- The 'works with Nest' policy appears to be more of a merging Nest with Google type a move more than a closing the system type of move. Google also isn't doing this till August, which makes me think they are trying to get an idea of public reaction to the move before they do anything. If they did the same sort of thing with Sonos, there would be no chance to gauge public reaction.
- Google (not Sonos) stated that the integration was happening back in January. While that could change, you would think this change would have been thought out enough to not make the announcement if it was not a sure thing.
- The public beta is currently ongoing, at least according to the most recent reports. Why would beta continue if the project was being dropped? Although folks are not supossed to talk about beta, I think you there would definitely be news about it if it happened.
- Remember, part of the deal with the integration is that Sonos agreed not to sue Google for theft of intellectual property if they agreed to integrate with Sonos. If the integration is off, that means a lawsuit would be back on. Given the deep pockets of Google and the volume of google assistance in the wild, that's a lot of money.
- On the surface anyway, it seems like a very bad strategy. There are certainly advantages to having a closed system, but it's proven to fail in the long run when competitors catch up. Google doesn't have that big of an advantage where customers will shun all others in dedication to google. It's worked for Apple for a time, but not so much anymore.
- The 'works with Nest' policy appears to be more of a merging Nest with Google type a move more than a closing the system type of move. Google also isn't doing this till August, which makes me think they are trying to get an idea of public reaction to the move before they do anything. If they did the same sort of thing with Sonos, there would be no chance to gauge public reaction.
What’s clear from all this is that Google is responsible for the delays, as it has been evolving its APIs and SDKs. The idea that Google wants to “lock out” Sonos, though, seems counter to their massive expansion to new devices. I think we’ll see GA control of Sonos soon, perhaps even using Local Home.
https://techcrunch.com/2019/05/07/google-launches-new-developer-tools-for-the-google-assistant/
https://techcrunch.com/2019/05/07/google-launches-new-developer-tools-for-the-google-assistant/
https://techcrunch.com/2019/05/07/google-launches-new-developer-tools-for-the-google-assistant/
I disagree. I don't think we can clearly state the cause of delays at all. Thee has only been speculation. Regarding the SDKs mentioned in your link they do not really look like good fits for Sonos. They don't mention music at all, mostly referring to native apps. I don't think Sonos wants to use native apps, or the local home, at least not initially, because it won't be of any use for their own speaker products, the Sonos One and Beam. Using Sonos already existing cloud service is the way to go. The Local Home would be a good option for those using google VAs with Sonos speakers, but it isn't the broad solution for all scenarios like cloud is. And it doesn't help sell new speakers for Sonos as well.
The local home looks like it will be a great push for selling Google's home hub stuff. Really good push, and I can see it being the top product next Christmas season. And maybe Sonos will work to integrate with that better in a phase 2, for lots of different reasons. I just don't see that happening right now.
I personally don't see much value in guessing whether to blame Google or Sonos. It seems like it only serves as a target for frustration. Why not just be frustrated without concern for who's to blame? Neither company has much to gain by accepting blame, or throwing the other under the bus, so we will unlikely know the truth anyway.
In the mean time you can lean back and enjoy the sound of one of the best sounding compact speakers on the market. Because sound is what this is all about, right ? And whats wrong with the software ? From time to time people complain, but honestly, I don't hear much complaints about the Sonos app.
I would never buy such an expensive speaker just because it supports (or doesn't) Google Assistant or Alexa. I trust Sonos they will keep delivering one of the best/most reliable wifi speaker systems on the market, but I wouldn't put my bets on Google. They have a history of starting and stopping products when it suits them.
I dunno. As I've said before, I'd have been perfectly happy had Sonos simply added Chromecast, so that a phone, tablet, or any of Google's range of devices, especially the Home Hub, could handle the GA. It would have been simple and done ages ago.
The display on the Hub adds immeasurably to the experience, especially on third-party playlists where you can see at a glance what's playing, without the need to interrupt the song by asking. Since any of Google's assistant devices can play by default to a Chromecast device, it's seamless. I honestly spend more time these days casting from the Hub to high quality systems than I use Sonos. And that's a shame.
The display on the Hub adds immeasurably to the experience, especially on third-party playlists where you can see at a glance what's playing, without the need to interrupt the song by asking. Since any of Google's assistant devices can play by default to a Chromecast device, it's seamless. I honestly spend more time these days casting from the Hub to high quality systems than I use Sonos. And that's a shame.
The display on the Hub adds immeasurably to the experience, especially on third-party playlists where you can see at a glance what's playing, without the need to interrupt the song by asking. Since any of Google's assistant devices can play by default to a Chromecast device, it's seamless. I honestly spend more time these days casting from the Hub to high quality systems than I use Sonos. And that's a shame.
You could say the same thing about Alexa integration, If Sonos had just added a line-in across their product line and offered bundles that include an Echo Dot the integration would have been done months earlier and would have supported all of the calling features, multiple wake words, and other features that the integration still does not have today. If you use a Spot instead of a Dot you can even have lyrics displayed as your music plays. I know there is a grand plan that supposedly will make the longer road worthwhile but by the time it is delivered will it still be relevant? Or will the voice assistant landscape have shifted so much that the original vision no longer makes sense?
Exactly. Sonos will always be playing catch-up in this game. The big AI guys can and will evolve their strategies. Sonos doesn't have the resources they have. Chromecast, Airplay 2, Alexa Cast and Spotify Connect support (all are currently supported except Chromecast) would allow support of virtually all streaming providers from a phone/tablet, Dot, Spot, Show, Home Hub, etc. Chromecast is the only missing piece right now.
Exactly. Sonos will always be playing catch-up in this game. The big AI guys can and will evolve their strategies. Sonos doesn't have the resources they have. Chromecast, Airplay 2, Alexa Cast and Spotify Connect support (all are currently supported except Chromecast) would allow support of virtually all streaming providers from a phone/tablet, Dot, Spot, Show, Home Hub, etc. Chromecast is the only missing piece right now.
I don't disagree with this from a functionality standpoint, adding in Alexa/GA support in terms of using a non-Sonos VA to command Sonos. I don't think having an aux input is really the equivalent though, as it limits functionality and essentially reduces Sonos to dumb active speakers. Having on-board mics on the Sonos One and Beam may be more trouble than their worth, as they'll always be behind as you pointed out.
However, putting mics helped get the whole system relevant in a way. It's easier to sell someone on an all-in-one device than it is to explain how your system works with Amazon (and eventually Google). People can see it and understand.
I do like having the all-in-one devices, and don't personally miss any features from echos...right now. If a new feature comes up that I think I can definitely use, then, I'll turn off the Sonos mics and throw an echo dot in the room.
Says Sonos:
This quarter we would like to highlight the much-anticipated launch of the Google Assistant on Sonos. We've been working on this for quite a while and are thrilled to be rolling it out next week. Through a software upgrade, Sonos One and Beam will support the Google Assistant in the U.S., with more markets to come over the next few months. This feature will truly elevate the customer experience and marks the first time that consumers will be able to buy a single smart speaker and get to choose which voice assistant they want to use. We think giving consumers choice is always the right decision, and we anticipate this philosophy will be adopted in the industry over time.
https://www.androidcentral.com/google-assistant-finally-headed-sonos-one-and-sonos-beam
This quarter we would like to highlight the much-anticipated launch of the Google Assistant on Sonos. We've been working on this for quite a while and are thrilled to be rolling it out next week. Through a software upgrade, Sonos One and Beam will support the Google Assistant in the U.S., with more markets to come over the next few months. This feature will truly elevate the customer experience and marks the first time that consumers will be able to buy a single smart speaker and get to choose which voice assistant they want to use. We think giving consumers choice is always the right decision, and we anticipate this philosophy will be adopted in the industry over time.
https://www.androidcentral.com/google-assistant-finally-headed-sonos-one-and-sonos-beam
In the mean time you can lean back and enjoy the sound of one of the best sounding compact speakers on the market. Because sound is what this is all about, right ? And whats wrong with the software ? From time to time people complain, but honestly, I don't hear much complaints about the Sonos app.
I would never buy such an expensive speaker just because it supports (or doesn't) Google Assistant or Alexa. I trust Sonos they will keep delivering one of the best/most reliable wifi speaker systems on the market, but I wouldn't put my bets on Google. They have a history of starting and stopping products when it suits them.
Except for i did buy them for GA support. 9 of them to be exact.
I had bought google homes for every room in the house when sonos announced GA support woupd be coming 2 weeks later. Still within my return period i returned the google homes and bought sonos ones instead. Now nearly 2 years later i sit here with a system that sounds good but doesnt do what i bought it to do. The waiting is getting tiresome.. And if infact the project geys scraped then the quewtion becomes will sonos issue refunds or will a class action be required? Im out about 5 thousand.
Just going to drop this here....
https://www.theverge.com/2019/5/9/18563413/sonos-google-assistant-smart-speakers-coming-next-week
Looks like Ha1337's "reliable source" isn't so reliable.
https://www.theverge.com/2019/5/9/18563413/sonos-google-assistant-smart-speakers-coming-next-week
Looks like Ha1337's "reliable source" isn't so reliable.
but i know from a reliable source who was at Google I/O, that Google are blocking the release of assistant on sonos as it doesn't fit with their smart home strategy. details i don't know. but sonos are leaning on google hard to change their mind. it's otherwise ready for release.
the opinion from the insider was that it's just not going to happen anymore.
I'm curious if you've reached out to your reliable source to ask him/her for a reaction to today's news. I'd be fascinated to hear what reaction they have.
I'm curious if you've reached out to your reliable source to ask him/her for a reaction to today's news. I'd be fascinated to hear what reaction they have.
Seriously.
My guess is we wont hear back from them.
Now how the heck am I gonna get this working in Canada?
This is moderately frustrating. I really hope it's available there by default, if not, might have to look into spoofing location or something 😠
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.