Home automation - light switch
-
@DustinB3403 said in Home automation - light switch:
@wirestyle22 I thought Nest has had some major security issues with their equipment.
Yeah, i was recalling the same - that's why they aren't on my list.
It's sad, they are a Google company... and they have horrible security.
-
Here is one article on the Nest Thermostat (from March of 2015)
I'm not willing to dig to much further into the issues, but I thought they had some other very serious issues, like using a root password of password or 123123 among other issues.
-
@DustinB3403 said in Home automation - light switch:
@wirestyle22 I thought Nest has had some major security issues with their equipment.
I remember it being "bad" but didn't remember why. That makes sense.
-
Here is another article from earlier this year about Nest equipment leaking the whereabouts of the home owner..
-
I just found this from Blackhat study of the devices. It's a pdf.
-
@wirestyle22 said in Home automation - light switch:
@DustinB3403 said in Home automation - light switch:
@wirestyle22 I thought Nest has had some major security issues with their equipment.
I remember it being "bad" but didn't remember why. That makes sense.
Security but also cost and weird lack of control.
-
@scottalanmiller said in Home automation - light switch:
@wirestyle22 said in Home automation - light switch:
@DustinB3403 said in Home automation - light switch:
@wirestyle22 I thought Nest has had some major security issues with their equipment.
I remember it being "bad" but didn't remember why. That makes sense.
Security but also cost and weird lack of control.
That's why I suggested to build something on top of AMQP:
- Transport layer security (TLS, SSH/VPN tunnel, ...)
- Built-in authentication
- Can easily be extended (depending on what you are doing, a simple form of AMQP just sends plain strings (JSON for example) from A to B.
- Built-in message routing (one sender, multiple recipients): Sender invokes a message like "CMD|LIGHT|ON" to a "message exchange" with the following topic: "HOUSE1.KITCHEN.LIGHT". Topics are something multiple recipients can subscribe to. For example, the light switch in the kitchen subscribes to "HOUSE1.KITCHEN.LIGHT" while a central logger subscribes to ..LIGHT to log all messages regarding light switches.
-
@thwr said in Home automation - light switch:
@scottalanmiller said in Home automation - light switch:
@wirestyle22 said in Home automation - light switch:
@DustinB3403 said in Home automation - light switch:
@wirestyle22 I thought Nest has had some major security issues with their equipment.
I remember it being "bad" but didn't remember why. That makes sense.
Security but also cost and weird lack of control.
That's why I suggested to build something on top of AMQP:
- Transport layer security (TLS, SSH/VPN tunnel, ...)
- Built-in authentication
- Can easily be extended (depending on what you are doing, a simple form of AMQP just sends plain strings (JSON for example) from A to B.
- Built-in message routing (one sender, multiple recipients): Sender invokes a message like "CMD|LIGHT|ON" to a "message exchange" with the following topic: "HOUSE1.KITCHEN.LIGHT". Topics are something multiple recipients can subscribe to. For example, the light switch in the kitchen subscribes to "HOUSE1.KITCHEN.LIGHT" while a central logger subscribes to ..LIGHT to log all messages regarding light switches.
For you programming nerds, that's great, I'm not one
-
Too late, in my brain, Dash is now using clappers for every light in his house, and starring in infomercials.
-
@Dominica said in Home automation - light switch:
Too late, in my brain, Dash is now using clappers for every light in his house, and starring in infomercials.
And when he claps, the room he is in turns on the lights, but the room down the hall turns off where he wife was. Multiple clappers gets you into a crazy game of turning random things on and off.
