Will this be the one smart home standard to rule them all or just another entry?
Read the whole story
Read the whole story
While I'd love for IPv4 to be in a position that it can realistically stop being supported, is Google planning to finance my ISP (Virgin Media in the UK) finally replacing its fleet of shitty-ass routers with ones actually capable of running IPv6 at all?
Although I'm in a position where I can (and am) using a separate router with my ISP supplied horror-show acting entirely as a modem, I'm not sure I'm going to be in the majority of people who will do this; most are going to still be using ISP supplied devices, most of which aren't going to use IPv6.
So what's the point of a standard that's already choosing to be unsupportable with most consumers?
It doesn't even really make sense; smart home devices are going to be behind a router no matter what anyway, and most won't (or shouldn't) be remotely accessible, and those that are just need a way to ensure they register a port that can be routed their way.
For a local network IPv6 local addresses are an unnecessary extravagance, and certainly not a widely supported one.
So yeah, I hope day two of this CHIP process is slapping Google upside the head and reminding them the dumbest thing a smart home standard can do is not work on most people's networks.
Since security is probably a total after thought for this effort I can't wait to see how this gets used in passive aggressive neighbor squabbles.
Already heard from other comments that highly educated Ars readers do in fact forget the washer because they are busy and have other things on their mind, that they in fact do not stay next to the washer when it is running, that connected washers are good for load shifting, that connected devices are good when dealing with disabilities.And I can download a smartphone app so they can let me know when loads are done, or nearing completion, because apparently I can't remember than when I started the load the machine said it would take 45 minutes, and that I would somehow miss the chime from the adjacent room.
Everybody loves to post that XKCD comic whenever something like this is tried. It's like they're saying "Ha, it's so futile. Don't even try to improve anything, losers!" (And I'm sure Munroe never intended to say that with the comic.)
But this has the biggest names in smarthome tech on board, and if this really happens, there's no way that this would just be another "standard" for the pile. This would be THE standard, period. This would be akin to the adoption of standard-gauge railways: everyone gets to use the same "tracks" to travel down, and everyone benefits.
Neither Apple nor Google is a big name in smarthome tech. They are big names in tech that have dabbled, poorly, in smarthome tech. They have not been able to translate their overall influence into home automation. Google in particular is just thrashing around killing its own products, as usual.
Of the long established smarthome protocols, there is Zigbee, Z-wave, UPB, and Insteon. Only one of those four is onboard. Getting Zigbee into the standard looks like an aggressive move to push out its competitors, not an attempt to work with them.
Of the new wave of smarthome devices, the most successful has been Philips Hue. Also not onboard.
I definitely see some advantages to interoperability and standardization here, but the effort isn't broad enough and isn't bringing in the companies that are actually important.
My issue is I want my home automation to function when my internet goes down. none of the current smart devices can function without internet access. I do have a small pile of wireless remotes for secondary light switches but they use regular 900mhz waves and have short range and are primarily used to control christmas lights.
if I could find a local only app that did wifi light control I might switch to that. but those don't exist unless you roll your own
Of the long established smarthome protocols, there is Zigbee, Z-wave, UPB, and Insteon. Only one of those four is onboard. Getting Zigbee into the standard looks like an aggressive move to push out its competitors, not an attempt to work with them.
Of the new wave of smarthome devices, the most successful has been Philips Hue. Also not onboard.
I definitely see some advantages to interoperability and standardization here, but the effort isn't broad enough and isn't bringing in the companies that are actually important.
I love that they continue to ignore AllJoyn and the Open Connectivity Foundation.
That's ok because all the software will be unable to support updates after 6 months! You know, just like current smart home devices... talk about blatant, in-your-face, planned/built-in obsolescence!I look forward to Google abandoning this project in 1-2 years.
Google, Amazon, Apple, and Zigbee. Three of these companies' business models depend on locking up your data to lock you into their products and ads. Sounds like a winner, just not for the user.
Anyone questioning the usefulness of smart home technology has not been disabled. When my leg was badly broken, it was so nice being able to control a few things (mainly lights) with my voice. Had I broken my leg 6 months earlier, that time would have been much more frustrating.
Home assistants and ancillary wares are reaching saturation. No doubt this holiday season was a huge drop in sales over last year because most of the people who wanted them bought them last year and fleshed out the rest over the following months.
Existing standards do all which is necessary and can be extended, but instead the angle presented is "we need a new standard".
Google, Amazon, Apple, and Zigbee. Three of these companies' business models depend on locking up your data to lock you into their products and ads. Sounds like a winner, just not for the user.
Well, fundamentally you exchange money for a good or service. Are you going to allege that as theft?
"Three of these companie's business models depend on stealing your money or information."?
Google, Amazon, Apple, and Zigbee. Three of these companies' business models depend on locking up your data to lock you into their products and ads. Sounds like a winner, just not for the user.
Well, fundamentally you exchange money for a good or service. Are you going to allege that as theft?
"Three of these companie's business models depend on stealing your money or information."?
It's theft (or at least fraud) if they don't properly disclose what they are going to take.
The big problem is configuring things, and for the users to put together both a useable interface, and linking stuff. And of course support for multiple users. And we need light sensors, that can help determine if we should turn on the light.
1) Extremely low-power equipment standards. It's hard to automate stuff that has to run on a battery for most its entire life, and built-in stuff with its own line power supply only takes you so far.
2) Mesh network standards, which go with low-power.
3) Security for all of this stuff is a huge problem, and very poorly addressed.
4) Peering and registration standards aren't great for a bunch of this stuff.
Neither Apple nor Google is a big name in smarthome tech. They are big names in tech that have dabbled, poorly, in smarthome tech. They have not been able to translate their overall influence into home automation. Google in particular is just thrashing around killing its own products, as usual.
Of the long established smarthome protocols, there is Zigbee, Z-wave, UPB, and Insteon. Only one of those four is onboard. Getting Zigbee into the standard looks like an aggressive move to push out its competitors, not an attempt to work with them.
Of the new wave of smarthome devices, the most successful has been Philips Hue. Also not onboard.
I definitely see some advantages to interoperability and standardization here, but the effort isn't broad enough and isn't bringing in the companies that are actually important.
Willing to bet 90% of all home automation is interfaced through an Apple or Google product. Apple was 0% of the payment market until they weren't. Nobody in the US at least could solve that space without Apple because the iPhone was the only viable interface for achieving payment ubiquity in the US. Apple was always going to be the party that chose the winning solution because system level integration was critical. Same will go for home automation.
I'm sure your 90% is true *if* you count systems where the only Apple or Google product is a phone running their OS. But that's a sucker's bet when 99% of phones are iOS or Android. I would not characterize Apple or Google's contribution to, say, a Hue system as meaningful just because the app runs on their OS.
Neither Apple nor Google is a big name in smarthome tech. They are big names in tech that have dabbled, poorly, in smarthome tech. They have not been able to translate their overall influence into home automation. Google in particular is just thrashing around killing its own products, as usual.
Of the long established smarthome protocols, there is Zigbee, Z-wave, UPB, and Insteon. Only one of those four is onboard. Getting Zigbee into the standard looks like an aggressive move to push out its competitors, not an attempt to work with them.
Of the new wave of smarthome devices, the most successful has been Philips Hue. Also not onboard.
I definitely see some advantages to interoperability and standardization here, but the effort isn't broad enough and isn't bringing in the companies that are actually important.
Willing to bet 90% of all home automation is interfaced through an Apple or Google product. Apple was 0% of the payment market until they weren't. Nobody in the US at least could solve that space without Apple because the iPhone was the only viable interface for achieving payment ubiquity in the US. Apple was always going to be the party that chose the winning solution because system level integration was critical. Same will go for home automation.
I'm sure your 90% is true *if* you count systems where the only Apple or Google product is a phone running their OS. But that's a sucker's bet when 99% of phones are iOS or Android. I would not characterize Apple or Google's contribution to, say, a Hue system as meaningful just because the app runs on their OS.
I guess I'll never be the target market for smart appliances. I just don't see the point.
The last year has seen a good deal of remodeling in the Degree's household, including new stove, 'fridge, washer and dryer, and other niceties. Not one of them is smart - although every company involved was hawking smart models. I particularly didn't understand the "smart" washer and dryer model - for nearly a grand more than we paid for our dumb set, you get a washer that uses WiFi to tell the dryer immediately next to it that it's getting near the end of a load, so it should turn itself on in prep to receive it. Just turn itself on. Which basically means light up the control panel - it's not like it even pre-heats or anything, just lights up. And I can download a smartphone app so they can let me know when loads are done, or nearing completion, because apparently I can't remember than when I started the load the machine said it would take 45 minutes, and that I would somehow miss the chime from the adjacent room.
I mean, I just don't see the point of any of this stuff, or understand what purpose it serves.
Hold on - there's some rotten kid out on my lawn I need to go yell at.
This trick won't work with IPv6, in which stateless auto-configuration and router discovery is mandatory. You will need to turn to a firewall.Just blackhole the traffic at the router, or stick it in a sandboxed/whitelisted-sites-only DMZ if it doesn't like being blackholed.I guess I'll never be the target market for smart appliances. I just don't see the point.
The last year has seen a good deal of remodeling in the Degree's household, including new stove, 'fridge, washer and dryer, and other niceties. Not one of them is smart - although every company involved was hawking smart models. I particularly didn't understand the "smart" washer and dryer model - for nearly a grand more than we paid for our dumb set, you get a washer that uses WiFi to tell the dryer immediately next to it that it's getting near the end of a load, so it should turn itself on in prep to receive it. Just turn itself on. Which basically means light up the control panel - it's not like it even pre-heats or anything, just lights up. And I can download a smartphone app so they can let me know when loads are done, or nearing completion, because apparently I can't remember than when I started the load the machine said it would take 45 minutes, and that I would somehow miss the chime from the adjacent room.
I mean, I just don't see the point of any of this stuff, or understand what purpose it serves.
Hold on - there's some rotten kid out on my lawn I need to go yell at.
Wait until you get a smart appliance that refuses to shut up. I thought I had shut down my range's wifi (along with the fridge - the builder loaded the house before we bought it). After spending several hours fiddling and searching I found the correct incantation. Which worked until I shut the power off. Then it popped up all happy and chatty again.
Another couple of hours of quality time with a pair of wire cutters will do the job, but what a PITA.
What I'm worried about is the fucking *everything* will be 'connected' (and chatty and insecure).
Oh well, wire cutters are cheap and I'm retired...
One trick I also like to use, above and beyond putting IoT devices on a separate 'untrusted' network, firewalled away from my main machines, is to assign static IPs, and then not give them default gateways.
(edit: without a default gateway, a device can talk on the local net, but it can't get to the broader internet. Firewalling it is better, but this is a trivial thing that will keep most devices off the main 'Net.)
But outside of some niche areas, electricity in the US is just really too cheap to bother. I'm not going to postpone laundry until 2AM to save 2 cents/kWh...
And what happens when the neighbourhood thief shouts, "Hey Siri, open the garage door" from outside your house? Or the neighbourhood kids shout, "Hey Siri, preheat the oven to 550 degrees" as a prank?But I can totally see, "Hey Siri, open the garage door", "Hey Siri, preheat the oven to 300 degrees", "Hey Siri, lock up the house", and related automatic options, like adjusting the thermostat, turning on and off lights, setting the water heater, etc, too.
Neither Apple nor Google is a big name in smarthome tech. They are big names in tech that have dabbled, poorly, in smarthome tech. They have not been able to translate their overall influence into home automation. Google in particular is just thrashing around killing its own products, as usual.
Of the long established smarthome protocols, there is Zigbee, Z-wave, UPB, and Insteon. Only one of those four is onboard. Getting Zigbee into the standard looks like an aggressive move to push out its competitors, not an attempt to work with them.
Of the new wave of smarthome devices, the most successful has been Philips Hue. Also not onboard.
I definitely see some advantages to interoperability and standardization here, but the effort isn't broad enough and isn't bringing in the companies that are actually important.
Willing to bet 90% of all home automation is interfaced through an Apple or Google product. Apple was 0% of the payment market until they weren't. Nobody in the US at least could solve that space without Apple because the iPhone was the only viable interface for achieving payment ubiquity in the US. Apple was always going to be the party that chose the winning solution because system level integration was critical. Same will go for home automation.
I'm sure your 90% is true *if* you count systems where the only Apple or Google product is a phone running their OS. But that's a sucker's bet when 99% of phones are iOS or Android. I would not characterize Apple or Google's contribution to, say, a Hue system as meaningful just because the app runs on their OS.
I don't know how you can say that; I'm assuming you saw the growth of the App Store ecosystem from 2006 onward; are you going to argue that "Apple's contribution to the Fitbit ecosystem as meaningful just because their app run on their OS"?
Or put another way, lack of iOS and Android support will kill any kind of lifestyle product today given, as you put it, 99% of phones are IOS or Android.
Zigbee/Z-Wave/etc did fine until now relying only on iOS or Android app or a dedicated remote/hardware controller, but at this point they also need extensive Homekit, Alexa, or Assistant support if we're going to see home automation be as ubiquitous as, say, Wifi.
Can you imagine Wifi existing today if Apple and Microsoft didn't support it in the year 2000?
And what happens when the neighbourhood thief shouts, "Hey Siri, open the garage door" from outside your house? Or the neighbourhood kids shout, "Hey Siri, preheat the oven to 550 degrees" as a prank?But I can totally see, "Hey Siri, open the garage door", "Hey Siri, preheat the oven to 300 degrees", "Hey Siri, lock up the house", and related automatic options, like adjusting the thermostat, turning on and off lights, setting the water heater, etc, too.
Neither Apple nor Google is a big name in smarthome tech. They are big names in tech that have dabbled, poorly, in smarthome tech. They have not been able to translate their overall influence into home automation. Google in particular is just thrashing around killing its own products, as usual.
Of the long established smarthome protocols, there is Zigbee, Z-wave, UPB, and Insteon. Only one of those four is onboard. Getting Zigbee into the standard looks like an aggressive move to push out its competitors, not an attempt to work with them.
Of the new wave of smarthome devices, the most successful has been Philips Hue. Also not onboard.
I definitely see some advantages to interoperability and standardization here, but the effort isn't broad enough and isn't bringing in the companies that are actually important.
Willing to bet 90% of all home automation is interfaced through an Apple or Google product. Apple was 0% of the payment market until they weren't. Nobody in the US at least could solve that space without Apple because the iPhone was the only viable interface for achieving payment ubiquity in the US. Apple was always going to be the party that chose the winning solution because system level integration was critical. Same will go for home automation.
I'm sure your 90% is true *if* you count systems where the only Apple or Google product is a phone running their OS. But that's a sucker's bet when 99% of phones are iOS or Android. I would not characterize Apple or Google's contribution to, say, a Hue system as meaningful just because the app runs on their OS.
I don't know how you can say that; I'm assuming you saw the growth of the App Store ecosystem from 2006 onward; are you going to argue that "Apple's contribution to the Fitbit ecosystem as meaningful just because their app run on their OS"?
Or put another way, lack of iOS and Android support will kill any kind of lifestyle product today given, as you put it, 99% of phones are IOS or Android.
Zigbee/Z-Wave/etc did fine until now relying only on iOS or Android app or a dedicated remote/hardware controller, but at this point they also need extensive Homekit, Alexa, or Assistant support if we're going to see home automation be as ubiquitous as, say, Wifi.
Can you imagine Wifi existing today if Apple and Microsoft didn't support it in the year 2000?
My point is, anyone can write an app that runs on iOS and Android. If you have a home automation hub that is on wifi, you can make an app for iOS and Android to work with it. (The other devices don't have to be on wifi, as long as they have some means of communicating with the hub.) At that point it's just software running on an arbitrary handheld device.
Actually building functionality beyond that into the OS has the real danger of taking away choices. I'm not going to buy hardware that only works with iOS, or hardware that only works with Android, because that takes away my choices in the future -- and it could be an especially big mistake if I'm building it into a house I hope to someday sell. It's better if the hub is OS agnostic.
Voice assistants and web services have started to broaden the scope and requirements of what it means to be device agnostic, so hopefully Apple and Google working together will create some space for interoperability without lock-in.
But outside of some niche areas, electricity in the US is just really too cheap to bother. I'm not going to postpone laundry until 2AM to save 2 cents/kWh...
For PG&E in northern CA, the cool season difference indeed is only 2 cents/kWh. However, the high season difference is 10 cents/kWh and up. If you have a EV plan you can save nearly $0.40/kWh off the awful peak rate of $0.52/kWh!
That is not the google way.I look forward to Google abandoning this project in 1-2 years.
... (commercial devices still needing a license). ...
Is there a cheaper alternative?... (commercial devices still needing a license). ...
Aaaand that killed it, right there. Has Apple learned nothing from the Firewire debacle?