Let' s see if I can give advice on homas urge. It' s not because I' m the smartest guy in the place. On the contrary, I' m rather lazy and very clumsy, but if I can do it by now, it' s for two reasons. The first is because I have checked in my own aupmotic system what is the easiest, easiest and most useful way to automate a house, specifically mine. I' m saying this because I have two kids, a business to attend to, and that' s complicated my life right now, because the truth isn' t
with me. And second and most importantly, I still know first hand what doesn' t work and what shouldn' t touch with a stick. This is why in this chapter I am not going to give three hundred and fifty - one advices on Homa urge, because they are only seven plus one, like dwarfs and white snows. And look out for the plus one because it ' s maybe the biggest headache you can get with Hume. Welcome to a new chapter on technology for all. The podcast where I speak of ardui and
a home automation programming and everything related to the maker movement. My name is the same as in the other chapters you call it Luis del Valle and you can find me in programming easy com The first advice I' m going to give is to think about hardware. Without a doubt, a rasverry Pie is the simplest and most economical way to enter the world of home automation and homa. If you have one at home, don' t hesitate, take it
out of the drawer and use it. Yes, if you' ve started on this Eastan Homa thing from now on, you' ll probably start adding more and more devices. At first it won' t be many, but since this gets you hooked you' re going to want to automate even your kids to get the trash out. Come on, in two Christmases, they ' ve got the house full of pots. In this sense, you have
to consider two things, the server and the data network. With respect to the server, incorporating more and more devices into your home automation network means that Eastan Homas will have more devices, entities, script automations and more components. If your server has limitations. As for performance, how can you get to have a Rasberry Pine, your home automation system will start going slow or directly to not working well. Doesn' t mean you' re not gonna take
advantage of the Pine rasverry. It' s not that. What I' m saying is that over time you have to be aware that sooner or later you' ll have to switch machines and buy a more powerful machine. It ' s a matter of time. I' m telling you for now. If you' ve got a rasverry foot still with her, but keep this in mind. On the other hand, we have the WITHID data network that
have limitations and are given by the router we are using. In theory, a household rutter can manage up to two hundred and fifty- four connected devices simultaneously. This is due to the limit of addresses and pes. For example, in my case, the range is one, one of two, one, six, eight, eighteen zero to two hundred and fifty- five. Not all can be used, as the rutter reserves some for internal use. The hipe range is almost every rooter can be different, depending on the type
of rutter and the model and how it is configured. In my case, that' s the case, and in addition, reserve the zero and the one. This gives me two hundred and fifty- two and p available and, in theory, I could connect all these devices. I say in theory because, as we will see later, it doesn' t just depend on the IPS to know all this information. In your specific case, you have to look within the rutter configuration, which is usually provided by the Internet operator,
which you have hired. If you don' t know how to do it, I recommend you get in touch with it. However, if you can as far as possible, I try to use your own rooter. This will prevent when you change the operator, something very common, as your IP range changes and everything that involves reconfiguring the rutter or the adopted system. Also regarding addresses and PS there is another possibility and it is doing the same, but at the software level creating your own DNSS server. In that sense,
there are applications such as p HALL or d NS. The more we get into all this in other chapters. Although, as we have seen, the limitation with respect to IPS addressing allows us to connect many devices, the reality is that the vast majority of rutters have technical limitations. As for hardware, you can know what they are if you look at the technical features sheet of your Rutter model and not just take into account the automated devices connected to Homasis
Other devices like phone, stable, smart speakers or TVs. Or smart TVs also intervene in network saturation. Therefore, the limitations come in terms of the number of addresses and pes that we have available that provides the rutter and the Rutter itself, i e the hardware. This makes the Wi- Fi network a great bottleneck. The solution, therefore, involves using other data networks such as ZEWAP zipb or bluetooth. I will talk about this in other chapters as
well. I' ll talk about these technologies. My advice is that at first you pull what you have and gradually add other network technologies. In other words, don' t go into the typical analysis paralysis syndrome to see if the WIFY network is going to give me enough devices, because if you want to start with Eastan Homas, the first thing you have to do is get into a nation and you have to pull with the WITHI network you have. In relation to the previous point, it is essential to use fixed ip on
all elements of your home automation system. I' m talking about the server and any device that connects to your home automation system. To see unless there is a prolonged power outage, something serious happens on the net doesn' t have to happen at all. However, you can avoid many headaches and it can be done easily through the rutter settings, although you can also do it at the software level, for example, with tasmota or mirror allow you to
put a fixed IP on the nodes. And last but not least, try to have an ester sheet with all the IPS of the devices and their names, and also their location within the house. Another tip custom components. I mean, when I talk about custom components, I mean devices made by ourselves. We are very handy and we love to do things and connect them to homas instam. This is a double- edged weapon if you don' t
use Jomasista' s official integrations. I mean complements like Jacks. Many people publish their own integrations and share them on the Internet, even if they are in official forums, they are still integrations made by third parties, and most importantly, they are not official. The biggest problem you can find is that when you upgrade to a new version, two, three or four new versions
come out each month. The custom component or integration may stop working. As I have to assume, this will make devices that depend on this custom component or this integration also stop working. So, experiments with sodas whenever you can use official integrations And if it doesn' t exist, there' s another solution, and it' s using standard protocols like MQTT and using its official
integration. Let' s talk about the release notes. I know it' s only on one roll, but it' s very important because if there ' s one thing that defines Homa Eastar it' s its ability to improve every month because every month a new version comes out with bug fixes and important changes. That is why it is very important to be on the parrot of
all changes that occur. Enough with the latest versions. They' ve added repairs that' s a section where they inform you of things that will stop working or that just don' t work anymore, but don' t trust them. It' s best to go to the launch notes, and I ' m telling you, sometimes they' re a pain in the ass. But it' s indispensable. My advice is to update each month to the
new version of Homas urges. I' m saying this because less important versions, minor versions come out in between, and maybe it' s not worth updating at the time, but, of course, looking at the release notes. But with each version of the month I recommend that you look at the notes and update them and as we couldn' t talk about backups, backups and backups. If there' s one thing in this life that' s safe is that we' re all going to die memento mori and this includes
your SD card, your hard drive or your Pendrive. That' s why it' s important that you keep a backup of Stan homas and the entire adomotic system. If you use locker com poss, also make copies of the configuration files, apart from all Homassissistant and all the other tools. One thing the database is also interesting, although it is not the most important thing in my view. I' m saying that because the historical or default storage of Homa Eastan is only ten days of that. Just be clear how to do
backups and also how to restore a backup. And finally, even if you already have a backup system, with proof that the copies are doing well to see this we' ve all done. I' m talking about installing integrations to see how they work. It' s normal to try new things. We all like to poop, but if you have integrations that you don' t use remove them, nothing really happens to have them. It' s
not going to stop Jomastic and more and they' re officers. However, when restarting integration, you may be looking for a device or service, and if you do not find it, try to do so until the waiting time runs out. Let' s go the typical time out to avoid this and that your homasis so go faster eliminates all those that you don' t use or that don' t work properly. If God created the automations within the Eastan Homas it is for a reason to use them, because they are the
pachamama of home automation. However, there are many ways to do things. I' m saying that because sooner or later, you' ll find an automation, with a lot of triggers of conditions and one action after another action, turning into automation. Mrs Barbuda. In these cases, when you think that an automation has overcome you because of its complexity, I recommend that you step back and think about how you could do the same in a simpler way.
And this implies that, in certain cases, a large automation can be divided into two much simpler automations and, above all, for your mental health, keep things simple. So you' ll be much happier and eat partridge. And we come to the last recommendation and the one that can give you the most headaches. Or, at least I' ve been given the policy
or convention of names. The only rule with regard to how to name devices, entities and automations and other components within Homard exist is that there is no rule that each can manage as well. And so it happens that you find domotic systems where the lights are called light one, light two, and so until light three hundred and fifty- one. Then to see who is the handsome one who knows which light of the house corresponds to the light seventeen And
what is the best name policy for Jomasista, because it depends. I have my own and speak of it long and stretched into the course of doopotics. My students know what it is and they also have their own. What the IWATE may Fen should be clear about is that, as you don' t apply a name policy from the start, sooner or later, it will be your turn to rename all the components with the resulting mess of balls that causes
all this. That' s it. Today' s chapter you know that, speaking in Silver and being a little soed, I sweat it if you give five stars or none to this podcast, because if you really want to continue learning about Domótti, Carduino and married in general, the best thing is that you sign up for the easy schedule list, com can also do nothing.
It' s another option. Anyway, I don' t know if next week we' ll listen because I' m going to be on vacation, hooked up with the kids, with the house and as a beautiful wife, but don' t miss the appointment in the next chapter, whenever, and remember happy set