Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
(00:00):
Let' s see first. Ihave seven chapters that the truth is not
bad for the short time I have. There' s something I want to
make very clear, because I'm getting a lot of emails from people
asking about homasist and domestic systems.This is a podcast and, as such,
submission is to divulge around home automation, cacharreo and also about Arduino.
It' s impossible for you tolearn everything you need to automate your home
(00:23):
by just listening to a podcast.And this is basically because this is all
very visual and requires a step-by- step system so that you can
configure your home automation system. Thisis what I' m going to talk
about shortly. In the easy programsubscription list, just enter into easy com
programming and sign up for the minihome automation course. You just have to
do that. You may thus haveaccess to a content that will see the
(00:44):
light in a very short time andmay help you set up your own home
automation system. That said, let' s go with today' s chapter
because I' m going to talkabout the integrations of eystan homas but first
let me tell you the story ofthe good American friend Jack, good of
those sleeping with the revolver under thepillow. It turns out that on a
spring day of two thousand twenty-two, poor Jack got up to go
(01:07):
to work, put some water onhis face and went down to the kitchen
for breakfast, hoping that his homeautomation system would have prepared him a good
cup of coffee, because, ashe did every morning but that day there
was no coffee or hostess and aftereating pancakes, the veicon and eggs,
shitting himself under the garage, alreadyon the stairs, he realized that the
lights did not light themselves and hebegan to gnash when he had to open
(01:30):
the door like the wild ones,pushing something was not right and when he
got to work and connected to hishome automation system, he could see what
was going on. It' ssomething that has to do with your automatic
devices and something related to this.That' s what I heard in this
new chapter, because there are smartdevices for home in many forms and manufacturers.
(01:52):
All absolutely all can be divided intotwo large groups, those that depend
on the Internet, the manufacturers andtheir servers and those that do not,
in other words, those that subjectyou and that you can subject guesses to.
What kind of devices Jack had,you' ll find out now.
(02:14):
Welcome to technology, but all thepodcast where I talk about arduin, not
home automation programming and everything related tothe maker movement. My name is Luis
del Valle. You can find meon my blog in program easy com do.
(02:35):
I' m going to go onwith Jack' s story because when
he entered his home automation system,he discovered that the company behind him had
evaporated. This company is called Histeonand closed in April of two thousand twenty
- two without notice. He disappearedforever, leaving no trace and without warning
his clients to see. This isnothing new. I mean, companies appear
and disappear. I think we're already used to it, because whoever
(02:59):
remembers terra, read appreciated or readsixteen daily that is, when the company
that disappears is the one behind yourhome automation system. What do you want
me to say to me, nofag or fucking grace, and you might
think it was a company from aWisconsin neighborhood, but hyston still had a
trajectory of over twenty years selling domesticdevices all over the planet and overnight shut
down and although it may be normalfor a company to shut down due to
(03:23):
economic problems, we are used toseeing it on the news. What'
s not so normal anymore is thatI' m not the only one who
' s done it. I mean, it' s not the only case
because companies like Rebolve, Google's affiliated company, which closed in the
two thousand sixteen, or Charter inSamsung' s two thousand twenty or Smarthings,
which shut down support for automation centersin the two thousand twenty- one,
(03:45):
are also cases like hysteon, allof them also left thousands of automatic
systems thrown away and also their users. And this is why when you'
re going to buy a home automationdevice, it would be a good time
to ask which of the two groupsbelong to those that depend on the manufacturers
and they can leave you lying downand those that don' t, because
(04:06):
to see how I explain it toyou. When your home automation system is
like JAGG' s and depends onthe manufacturers, you run the risk that
if the company closes because the zealor ceo retires or the servers fall your
home automation system goes after your dataare not in good health, because sending
them to a Vietnam jungle ten zerokilometers away. Aside from the fact that
it' s absurd to have thelight bulb within two meters, it'
(04:29):
s more insecure than if they don' t leave your house and the manufacturers
know when I get up at nightto eat cookies if you' ve eaten
cauliflower or when you' re shopping, what you want me to say to
me It' s not that funny. Hence the importance of using a home
automation controller as a homasist so thatif the manufacturer closes you don' t
get any more laid than a butt. But what to do with all those
(04:49):
devices that depend on the manufacturers andthat we already have installed at home.
We throw them to the clean spotin which container they go, since tranquility
does not dissist anything, because ifthere is a characteristic that differentiates homosist in
the rest of automatic controllers, thatis its flexibility. Now you see,
why I' m saying that,we' ve already seen in the home
(05:11):
intelligence chapter how devices that depend onmanufacturers interact with homasista. Basically what it
does is use cloud servers as agateway. When you want to control a
device that depends on the homas manufacturersare sending the command to their servers over
the Internet and these get in touchwith the device and although having to send
information thousands of miles to turn ona light that is one meter away is
(05:33):
absurd. Apart from privacy, it' s the solution that Homas Eastan offers
us so we don' t haveto throw all those devices into a clean
spot container. But how capable homasare to control these devices, as this
is achieved thanks to Homasistant integrations.The integrations are nothing more than pieces of
software that expand Homasistant' s operationis as if they were the Chrome plugins
(05:57):
or plugins of any other software.It allows us to add extra functions to
HOMASISTAN and what functions we can add. The truth is that there are countless
integrations that make everything, from beingable to calculate the average or the derivative
of a sensor to integrating motorcycle carsor the rumba vacuum cleaner. You can
see all the integrations of homas ifthey are categorized on the official website today,
(06:20):
when I am recording this chapter,there are two thousand four hundred twenty
- four integrations, although this numbermost likely will continue to grow. This
is because Eastan Homa Popularity is growinga lot and manufacturers will be anything but
fools not and know that if theirproducts are compatible with Instan Homas, they
will sell more. Hence, Homasistant' s offer of integrations is so varied.
(06:45):
Many of the most important manufacturers arecompatible with Instan homas. Examples include
Shaomi, Phillips Ness and kalg OSonos, among others. They all have
integrations so that their dyspositis s nn r s s s s two from
Homasistant. And this, apart frommaking everything much more flexible, allows us
to do things like having a singleapplication where we can control all the devices
(07:10):
that are branded and so forget abouthaving an application for each of them,
create automations where devices from different manufacturersare involved. That is, that a
Shaomi sensor hates a person' spresence and can turn on a Phillips Hough
bulb, for example, and eventhough you' re still going to depend
on their servers and the Internet,you can have them all integrated into homas
(07:33):
install until the company or device bursts. All this in terms of controlling domestic
devices such as relays, plugs orsensors or bulbs, you know the typical
ones, because besides, there areother types of devices or rather are electrical
devices that can also be connected thanksto the integrations of homasista. I mean
(07:53):
devices like the vacuum robot, smartspeakers like Alexa or Google hom or connected
cars like Tesla, for example.Many of these devices also have interactions of
eastan homas with which you will beable to do crazy things. But things
like that while you' re havingbreakfast Alexa can tell you to come out
(08:13):
ten minutes early, because you haveto put broth in the car, that
the vacuum robot comes out to cleanonly when there' s no one home,
or that at nine and twelve o' clock it stops the TV and
sounds Casimiro' s song in Alexaso that the kids go to sleep shitting
milk. And although the ideal wouldbe to have a home automation system completely
independent of manufacturers so they won't let you go, as happened to
Jack today. It is quite difficultto achieve this, because even though all
(08:37):
automatic devices, such as relays,light bulbs or sensors, are independent,
the other chapter will talk about thistype of devices. You may have a
car, a vacuum robot, ora washing machine that will continue to depend
on manufacturers' servers. But ifwe stick to domotic devices like relays,
light bulbs or sensors, how toidentify which are independent dependents. Well,
(08:58):
I' ll talk about this inanother chapter of the podcast. For now
we' re going to see howto integrate a home automation device dependent on
Homasistant. Once you have installed Instanhomas by one of the official methods we
already saw in a chapter. Addingintegrations is pretty simple, but before you
see where you have to access,it' s important to know whether or
(09:20):
not your devices are compatible with aJoker. The quickest thing is to go
to the official website where you willfind all the integrations of homasista and search
by the name of the manufacturer.For example, imagine that you have a
Tepeling plug at home that you controlwith the manufacturer app. You enter the
integrations website and search for Teppeling youwill see three integrations, one of which
(09:41):
is called Teppelin Casa smar Always beforeadding an interaction to Homasistant, it is
advisable to read the official documentation ofthe integration. In the event that an
integration by the manufacturer' s namedoes not appear, it will most likely
not be good compatible. It's not really officially compatible, because there
is an unofficial integration repository called Jacks, but using their integrations can carry risks
(10:05):
in terms of Honmasistan' s performanceand performance. You can also search for
devices on the website h device,where a repository of all Homasistant- compatible
devices is being created and once youhave localized integration. You know your devices
(10:26):
are compatible and you' ve accessedofficial documentation. There are two ways to
add integration. The first series throughthe website of the official Homasta documentation.
There you will find a button thatputs at integration. If you press it
open a your homs installation are andinstall it automatically. The second option is
(10:46):
in the integrations section of the graphicalinterface, where you will be able to
access if you are going to adjustdevices and services, there you will have
another button that puts adding integration.This will open a panel, a new
pantan where you' re going tolook for integration and install it anyway,
before you add any integration, beit depelin or any other manufacturer, it
(11:07):
' s going to ask you toconfigure access to the cloud of the device,
if it depends on the manufacturers.In the end it is usually through
a user, a password with theone you do in the application or through
an api key that the manufacturer willprovide you with. Each integration has its
own configuration. There is nothing standardand hence it is so important to review
(11:28):
the official documentation before installing any integration. This concludes this chapter. But first
I' m going to make asummary of everything we' ve seen so
far. In this chapter we haveseen the risks that we face when our
home automation system depends on manufacturers.If the company shuts down your system goes
to hell, having to connect toa server that' s thousands of miles
(11:50):
away. Apart from being absurd,it' s much more insecure and although
there' s probably no one watchingto know when you eat cookies, go
out of the house or save yourdata that you know are not private.
Therefore, the ideal would be tohave a totally independent home automation system.
But this today is quite complicated,because in many cases we already start with
(12:11):
automatic devices that depend on manufacturers,but whether they are real in chufes or
sensors. Even if they depend onthe manufacturers, you may be able to
control them from the same tomotic controllerthanks to the integrations of homasista. These
integrations are nothing more than pieces ofsoftware that are installed in homassins so to
provide extra functionality to our home automationsystem, and integrations there are many and
(12:35):
allow us to control from bulbs tovacuum cleaners through cars. This is why,
if you have domotic devices, itwould be bullshit to get rid of
them without first checking if they arecompatible with Jomists. Now, whenever you
go to buy new devices, youtry to make them independent, but how
to differentiate them from each other.Well, I' ll talk about this
(12:58):
in another chapter We' ll heareach other next week. Don' t
miss the date and remember to behappy