WEBVTT

1
00:00:00.080 --> 00:00:02.879
Let' s see if I can
give advice on homas urge. It'

2
00:00:02.919 --> 00:00:05.040
s not because I' m the
smartest guy in the place. On the

3
00:00:05.040 --> 00:00:09.519
contrary, I' m rather lazy
and very clumsy, but if I can

4
00:00:09.560 --> 00:00:11.519
do it by now, it'
s for two reasons. The first is

5
00:00:11.560 --> 00:00:15.279
because I have checked in my own
aupmotic system what is the easiest, easiest

6
00:00:15.400 --> 00:00:20.600
and most useful way to automate a
house, specifically mine. I' m

7
00:00:20.679 --> 00:00:24.440
saying this because I have two kids, a business to attend to, and

8
00:00:24.480 --> 00:00:26.679
that' s complicated my life right
now, because the truth isn' t

9
00:00:26.679 --> 00:00:29.960
with me. And second and most
importantly, I still know first hand what

10
00:00:30.399 --> 00:00:34.920
doesn' t work and what shouldn' t touch with a stick. This

11
00:00:34.960 --> 00:00:38.280
is why in this chapter I am
not going to give three hundred and fifty

12
00:00:38.439 --> 00:00:42.039
- one advices on Homa urge,
because they are only seven plus one,

13
00:00:42.439 --> 00:00:46.159
like dwarfs and white snows. And
look out for the plus one because it

14
00:00:46.240 --> 00:00:56.759
' s maybe the biggest headache you
can get with Hume. Welcome to a

15
00:00:56.759 --> 00:01:00.000
new chapter on technology for all.
The podcast where I speak of ardui and

16
00:01:00.079 --> 00:01:04.640
a home automation programming and everything related
to the maker movement. My name is

17
00:01:04.680 --> 00:01:07.840
the same as in the other chapters
you call it Luis del Valle and you

18
00:01:07.879 --> 00:01:14.120
can find me in programming easy com
The first advice I' m going to

19
00:01:14.159 --> 00:01:15.879
give is to think about hardware.
Without a doubt, a rasverry Pie is

20
00:01:15.920 --> 00:01:19.560
the simplest and most economical way to
enter the world of home automation and homa.

21
00:01:21.120 --> 00:01:23.719
If you have one at home,
don' t hesitate, take it

22
00:01:23.879 --> 00:01:26.319
out of the drawer and use it. Yes, if you' ve started

23
00:01:26.359 --> 00:01:30.439
on this Eastan Homa thing from now
on, you' ll probably start adding

24
00:01:30.519 --> 00:01:34.599
more and more devices. At first
it won' t be many, but

25
00:01:34.640 --> 00:01:38.799
since this gets you hooked you'
re going to want to automate even your

26
00:01:38.799 --> 00:01:42.480
kids to get the trash out.
Come on, in two Christmases, they

27
00:01:42.599 --> 00:01:45.200
' ve got the house full of
pots. In this sense, you have

28
00:01:45.280 --> 00:01:49.359
to consider two things, the server
and the data network. With respect to

29
00:01:49.439 --> 00:01:53.840
the server, incorporating more and more
devices into your home automation network means that

30
00:01:55.200 --> 00:02:00.079
Eastan Homas will have more devices,
entities, script automations and more components.

31
00:02:00.280 --> 00:02:05.640
If your server has limitations. As
for performance, how can you get to

32
00:02:05.760 --> 00:02:10.680
have a Rasberry Pine, your home
automation system will start going slow or directly

33
00:02:10.719 --> 00:02:14.960
to not working well. Doesn'
t mean you' re not gonna take

34
00:02:15.000 --> 00:02:15.159
advantage of the Pine rasverry. It' s not that. What I'

35
00:02:15.439 --> 00:02:20.039
m saying is that over time you
have to be aware that sooner or later

36
00:02:20.120 --> 00:02:23.879
you' ll have to switch machines
and buy a more powerful machine. It

37
00:02:23.919 --> 00:02:25.000
' s a matter of time.
I' m telling you for now.

38
00:02:25.199 --> 00:02:29.919
If you' ve got a rasverry
foot still with her, but keep this

39
00:02:29.919 --> 00:02:32.280
in mind. On the other hand, we have the WITHID data network that

40
00:02:32.400 --> 00:02:37.439
have limitations and are given by the
router we are using. In theory,

41
00:02:37.639 --> 00:02:42.080
a household rutter can manage up to
two hundred and fifty- four connected devices

42
00:02:42.080 --> 00:02:46.680
simultaneously. This is due to the
limit of addresses and pes. For example,

43
00:02:46.800 --> 00:02:49.520
in my case, the range is
one, one of two, one,

44
00:02:49.639 --> 00:02:52.639
six, eight, eighteen zero to
two hundred and fifty- five.

45
00:02:53.199 --> 00:02:58.000
Not all can be used, as
the rutter reserves some for internal use.

46
00:02:58.879 --> 00:03:01.719
The hipe range is almost every rooter
can be different, depending on the type

47
00:03:01.800 --> 00:03:06.800
of rutter and the model and how
it is configured. In my case,

48
00:03:07.199 --> 00:03:08.520
that' s the case, and
in addition, reserve the zero and the

49
00:03:08.520 --> 00:03:12.479
one. This gives me two hundred
and fifty- two and p available and,

50
00:03:13.039 --> 00:03:15.240
in theory, I could connect all
these devices. I say in theory

51
00:03:15.240 --> 00:03:20.759
because, as we will see later, it doesn' t just depend on

52
00:03:20.800 --> 00:03:22.919
the IPS to know all this information. In your specific case, you have

53
00:03:23.000 --> 00:03:25.120
to look within the rutter configuration,
which is usually provided by the Internet operator,

54
00:03:25.360 --> 00:03:30.120
which you have hired. If you
don' t know how to do

55
00:03:30.199 --> 00:03:32.639
it, I recommend you get in
touch with it. However, if you

56
00:03:32.840 --> 00:03:37.639
can as far as possible, I
try to use your own rooter. This

57
00:03:37.759 --> 00:03:40.520
will prevent when you change the operator, something very common, as your IP

58
00:03:40.599 --> 00:03:46.439
range changes and everything that involves reconfiguring
the rutter or the adopted system. Also

59
00:03:46.840 --> 00:03:50.919
regarding addresses and PS there is another
possibility and it is doing the same,

60
00:03:51.199 --> 00:03:54.960
but at the software level creating your
own DNSS server. In that sense,

61
00:03:55.120 --> 00:04:00.120
there are applications such as p HALL
or d NS. The more we get

62
00:04:00.199 --> 00:04:03.199
into all this in other chapters.
Although, as we have seen, the

63
00:04:03.240 --> 00:04:09.840
limitation with respect to IPS addressing allows
us to connect many devices, the reality

64
00:04:09.879 --> 00:04:13.759
is that the vast majority of rutters
have technical limitations. As for hardware,

65
00:04:14.400 --> 00:04:18.519
you can know what they are if
you look at the technical features sheet of

66
00:04:18.680 --> 00:04:24.319
your Rutter model and not just take
into account the automated devices connected to Homasis

67
00:04:24.439 --> 00:04:30.279
Other devices like phone, stable,
smart speakers or TVs. Or smart TVs

68
00:04:30.839 --> 00:04:35.879
also intervene in network saturation. Therefore, the limitations come in terms of the

69
00:04:35.920 --> 00:04:41.279
number of addresses and pes that we
have available that provides the rutter and the

70
00:04:41.360 --> 00:04:45.879
Rutter itself, i e the hardware. This makes the Wi- Fi network

71
00:04:46.000 --> 00:04:50.920
a great bottleneck. The solution,
therefore, involves using other data networks such

72
00:04:50.959 --> 00:04:57.399
as ZEWAP zipb or bluetooth. I
will talk about this in other chapters as

73
00:04:57.399 --> 00:05:00.399
well. I' ll talk about
these technologies. My advice is that at

74
00:05:00.439 --> 00:05:06.199
first you pull what you have and
gradually add other network technologies. In other

75
00:05:06.279 --> 00:05:12.199
words, don' t go into
the typical analysis paralysis syndrome to see if

76
00:05:12.240 --> 00:05:16.000
the WIFY network is going to give
me enough devices, because if you want

77
00:05:16.000 --> 00:05:19.439
to start with Eastan Homas, the
first thing you have to do is get

78
00:05:19.480 --> 00:05:21.759
into a nation and you have to
pull with the WITHI network you have.

79
00:05:23.800 --> 00:05:29.480
In relation to the previous point,
it is essential to use fixed ip on

80
00:05:29.560 --> 00:05:32.680
all elements of your home automation system. I' m talking about the server

81
00:05:32.680 --> 00:05:35.720
and any device that connects to your
home automation system. To see unless there

82
00:05:35.759 --> 00:05:41.199
is a prolonged power outage, something
serious happens on the net doesn' t

83
00:05:41.199 --> 00:05:44.959
have to happen at all. However, you can avoid many headaches and it

84
00:05:45.199 --> 00:05:48.199
can be done easily through the rutter
settings, although you can also do it

85
00:05:48.519 --> 00:05:51.800
at the software level, for example, with tasmota or mirror allow you to

86
00:05:51.879 --> 00:05:57.639
put a fixed IP on the nodes. And last but not least, try

87
00:05:57.680 --> 00:06:01.360
to have an ester sheet with all
the IPS of the devices and their names,

88
00:06:01.680 --> 00:06:10.040
and also their location within the house. Another tip custom components. I

89
00:06:10.040 --> 00:06:14.439
mean, when I talk about custom
components, I mean devices made by ourselves.

90
00:06:15.240 --> 00:06:17.879
We are very handy and we love
to do things and connect them to

91
00:06:17.879 --> 00:06:21.759
homas instam. This is a double- edged weapon if you don' t

92
00:06:21.839 --> 00:06:27.519
use Jomasista' s official integrations.
I mean complements like Jacks. Many people

93
00:06:27.639 --> 00:06:31.720
publish their own integrations and share them
on the Internet, even if they are

94
00:06:31.759 --> 00:06:36.399
in official forums, they are still
integrations made by third parties, and most

95
00:06:36.480 --> 00:06:40.240
importantly, they are not official.
The biggest problem you can find is that

96
00:06:40.279 --> 00:06:45.040
when you upgrade to a new version, two, three or four new versions

97
00:06:45.120 --> 00:06:50.240
come out each month. The custom
component or integration may stop working. As

98
00:06:50.279 --> 00:06:56.560
I have to assume, this will
make devices that depend on this custom component

99
00:06:56.680 --> 00:07:00.920
or this integration also stop working.
So, experiments with sodas whenever you can

100
00:07:01.079 --> 00:07:05.680
use official integrations And if it doesn' t exist, there' s another

101
00:07:06.000 --> 00:07:11.839
solution, and it' s using
standard protocols like MQTT and using its official

102
00:07:11.839 --> 00:07:15.639
integration. Let' s talk about
the release notes. I know it'

103
00:07:15.680 --> 00:07:18.800
s only on one roll, but
it' s very important because if there

104
00:07:18.800 --> 00:07:24.240
' s one thing that defines Homa
Eastar it' s its ability to improve

105
00:07:24.319 --> 00:07:27.759
every month because every month a new
version comes out with bug fixes and important

106
00:07:27.759 --> 00:07:30.839
changes. That is why it is
very important to be on the parrot of

107
00:07:30.879 --> 00:07:34.360
all changes that occur. Enough with
the latest versions. They' ve added

108
00:07:34.399 --> 00:07:38.839
repairs that' s a section where
they inform you of things that will stop

109
00:07:39.160 --> 00:07:41.279
working or that just don' t
work anymore, but don' t trust

110
00:07:41.279 --> 00:07:44.360
them. It' s best to
go to the launch notes, and I

111
00:07:44.399 --> 00:07:45.759
' m telling you, sometimes they' re a pain in the ass.

112
00:07:46.079 --> 00:07:49.199
But it' s indispensable. My
advice is to update each month to the

113
00:07:49.279 --> 00:07:55.360
new version of Homas urges. I' m saying this because less important versions,

114
00:07:55.639 --> 00:08:01.560
minor versions come out in between,
and maybe it' s not worth

115
00:08:01.560 --> 00:08:03.439
updating at the time, but,
of course, looking at the release notes.

116
00:08:03.600 --> 00:08:07.560
But with each version of the month
I recommend that you look at the

117
00:08:07.879 --> 00:08:13.240
notes and update them and as we
couldn' t talk about backups, backups

118
00:08:13.360 --> 00:08:16.279
and backups. If there' s
one thing in this life that' s

119
00:08:16.439 --> 00:08:20.839
safe is that we' re all
going to die memento mori and this includes

120
00:08:22.000 --> 00:08:22.720
your SD card, your hard drive
or your Pendrive. That' s why

121
00:08:22.800 --> 00:08:28.040
it' s important that you keep
a backup of Stan homas and the entire

122
00:08:28.040 --> 00:08:31.399
adomotic system. If you use locker
com poss, also make copies of the

123
00:08:31.399 --> 00:08:35.200
configuration files, apart from all Homassissistant
and all the other tools. One thing

124
00:08:35.279 --> 00:08:39.240
the database is also interesting, although
it is not the most important thing in

125
00:08:39.279 --> 00:08:43.240
my view. I' m saying
that because the historical or default storage of

126
00:08:43.399 --> 00:08:46.600
Homa Eastan is only ten days of
that. Just be clear how to do

127
00:08:46.639 --> 00:08:52.840
backups and also how to restore a
backup. And finally, even if you

128
00:08:52.000 --> 00:08:56.720
already have a backup system, with
proof that the copies are doing well to

129
00:08:56.799 --> 00:09:01.320
see this we' ve all done. I' m talking about installing integrations

130
00:09:01.360 --> 00:09:05.200
to see how they work. It' s normal to try new things.

131
00:09:05.200 --> 00:09:09.679
We all like to poop, but
if you have integrations that you don'

132
00:09:09.720 --> 00:09:11.919
t use remove them, nothing really
happens to have them. It' s

133
00:09:11.960 --> 00:09:15.440
not going to stop Jomastic and more
and they' re officers. However,

134
00:09:15.799 --> 00:09:20.480
when restarting integration, you may be
looking for a device or service, and

135
00:09:20.519 --> 00:09:24.039
if you do not find it,
try to do so until the waiting time

136
00:09:24.039 --> 00:09:26.720
runs out. Let' s go
the typical time out to avoid this and

137
00:09:26.799 --> 00:09:31.360
that your homasis so go faster eliminates
all those that you don' t use

138
00:09:31.480 --> 00:09:35.240
or that don' t work properly. If God created the automations within the

139
00:09:35.320 --> 00:09:39.720
Eastan Homas it is for a reason
to use them, because they are the

140
00:09:39.799 --> 00:09:43.440
pachamama of home automation. However,
there are many ways to do things.

141
00:09:43.960 --> 00:09:46.720
I' m saying that because sooner
or later, you' ll find an

142
00:09:46.799 --> 00:09:52.200
automation, with a lot of triggers
of conditions and one action after another action,

143
00:09:52.000 --> 00:09:54.679
turning into automation. Mrs Barbuda.
In these cases, when you think

144
00:09:54.759 --> 00:10:00.000
that an automation has overcome you because
of its complexity, I recommend that you

145
00:10:00.039 --> 00:10:05.039
step back and think about how you
could do the same in a simpler way.

146
00:10:05.159 --> 00:10:09.399
And this implies that, in certain
cases, a large automation can be

147
00:10:09.440 --> 00:10:13.399
divided into two much simpler automations and, above all, for your mental health,

148
00:10:15.000 --> 00:10:18.559
keep things simple. So you'
ll be much happier and eat partridge.

149
00:10:20.480 --> 00:10:24.600
And we come to the last recommendation
and the one that can give you

150
00:10:24.679 --> 00:10:26.279
the most headaches. Or, at
least I' ve been given the policy

151
00:10:26.399 --> 00:10:33.200
or convention of names. The only
rule with regard to how to name devices,

152
00:10:33.720 --> 00:10:37.159
entities and automations and other components within
Homard exist is that there is no

153
00:10:37.240 --> 00:10:43.080
rule that each can manage as well. And so it happens that you find

154
00:10:43.159 --> 00:10:46.279
domotic systems where the lights are called
light one, light two, and so

155
00:10:46.360 --> 00:10:48.360
until light three hundred and fifty-
one. Then to see who is the

156
00:10:48.440 --> 00:10:54.120
handsome one who knows which light of
the house corresponds to the light seventeen And

157
00:10:54.159 --> 00:10:58.320
what is the best name policy for
Jomasista, because it depends. I have

158
00:10:58.399 --> 00:11:01.720
my own and speak of it long
and stretched into the course of doopotics.

159
00:11:01.679 --> 00:11:05.879
My students know what it is and
they also have their own. What the

160
00:11:05.960 --> 00:11:09.679
IWATE may Fen should be clear about
is that, as you don' t

161
00:11:09.759 --> 00:11:15.000
apply a name policy from the start, sooner or later, it will be

162
00:11:15.080 --> 00:11:18.480
your turn to rename all the components
with the resulting mess of balls that causes

163
00:11:18.480 --> 00:11:22.000
all this. That' s it. Today' s chapter you know that,

164
00:11:22.559 --> 00:11:26.039
speaking in Silver and being a little
soed, I sweat it if you

165
00:11:26.159 --> 00:11:31.120
give five stars or none to this
podcast, because if you really want to

166
00:11:31.240 --> 00:11:35.039
continue learning about Domótti, Carduino and
married in general, the best thing is

167
00:11:35.080 --> 00:11:37.960
that you sign up for the easy
schedule list, com can also do nothing.

168
00:11:39.279 --> 00:11:41.799
It' s another option. Anyway, I don' t know if

169
00:11:41.840 --> 00:11:45.879
next week we' ll listen because
I' m going to be on vacation,

170
00:11:46.320 --> 00:11:48.879
hooked up with the kids, with
the house and as a beautiful wife,

171
00:11:50.399 --> 00:12:03.720
but don' t miss the appointment
in the next chapter, whenever,

172
00:11:54.399 --> 00:12:03.720
and remember happy set