4 ms·
I got burned by Google "sunsetting" custom actions on assistant [1]. I'm not trusting Google to keep this open for 3rd parties. [1] https://developers.google.c
by advisedwang 2y ago
I got burned by Google "sunsetting" custom actions on assistant [1]. I'm not trusting Google to keep this open for 3rd parties.
[1] https://developers.google.com/assistant/ca-sunset https://developers.google.com/assistant/ca-sunset
- afavour 2y agoBetween this and Google removing the ability for you to use any shopping list other than their own Keep app my Google Home has become little more than a jukebox.
- mateus1 2y agoI won’t be surprised if they shut down Nest and people find themselves with bricked Carbon Monoxide Sensors…
- iFire 2y agoI wonder if that's a legal liability with bricked Carbon Monoxide sensors.
- mikeyouse 2y agoFor whatever other issues people are rightly concerned about - when sensors like this 'brick', it's just the weird superfluous cloud features that are turned off and the core functionality still works fine. Though on the smoke detectors, modern code is that they all need to communicate and alarm at once, so depending on how that's architected on the Nest devices, could prove problematic to lose all of that.
- packetlost 2y agoThat sounds like class-action lawsuit levels of bad. That being said, I'm actually not that worried about Nest getting killed.
- solardev 2y agoThey already forced a transition through several apps (Google Wifi, Nest, Home) and shut down some product lines (Nest Secure).
- Marsymars 2y agoAlarm interconnect has to be local; I don't think it would code-compliant anywhere otherwise. (Even wireless interconnect has only become code-compliant relatively recently - e.g. in my jurisdiction, code has only allowed wireless interconnect since 2019.)