- Thu Jun 18, 2020 2:03 pm
#87578
btidey wrote:You can create your own Google SmartHome action to do this but it is reasonably complicated to do.
https://developers.google.com/actions/smarthome/
I use Amazon for my home control and I find their SDK and example templates makes this fairly straightforward to do.
Can you tell us what you did with Amazon Alexa that you can communicate straight to ESP8266?
I have some knowledge about Amazon Lambda. From what I know Amazon won't talk to you unless you use SSL https and Certificate Authority. With embedded controller and price control of less than 20 bucks, you won't be able to do that. I think the closest you can do is to copy the key certificate and save it in your ESP8266. But if the key changes, your Thing won't communicate. Never tried this, but testaments say this is as good as regular SSL communication.
IFTTT though is more open and less restrictive. But as an embedded programmer and front end developer, you can install some really reliable security measures, that run in the Local Area Network of the household. I think IFTTT has open possibilities for the front end developers to increase their security. The back end cloud should not restrict the endpoint devices. It is up to the front end developers to make a unique security measures that is dynamic and could be shared to the cloud such as IFTTT.
I have read a blog from a senior Google programmer that embedded SoC nowadays can sustain 40,000 messages in one second without any loss of data! This is UDP server they tested. This is powerful enough to block any DoS attack.
I believe that security does not rest alone on Certificate Authority and big cloud companies. The real security starts in the endpoint local area network. Who knows later on Routers will have capabilities to be programmed and police its own ports.
