Thank you for this video! So many HA videos just don't bother to explain conceptually what is going on. Making a pure conceptual video removes the distraction of any particular task and allows for a better understanding, facilitating self help and trouble shooting. Well done!
Hello nice video, thanks. One quick question, I use devices into automation triggers and actions, I noticde triggers and actions thru devices is faster than state and service. Any comments? Pros, cons using device in automations? Thank you
Never noticed any significant difference in my end, which device did you use? If it a cloud integration the consistency or latency variation would be higher
I wish I'd seen this diagram when I started out. The only thing I would add would be addons. It took me a while to understand the difference between integrations and addons
What about a way to "document" your home assistant instance i a "report" that starts with installation choices/settings through where all devices are deployed and where all those files exist on the system? (IP addresses, URLs, ports...) That report could be pushed to your personal github repo or tagged somehow onto a backup. The goal would be to hand the report to the someone purchasing your house (for a $10,000 addon price of course) or a child/spouse after you pass. With the report you should be able to install a new HA server, restore a backup and be up & runing on the same network of devices if needed.
Geo I think this is a really good start, for those who seek a more complete picture of how HomeAssistant works need to better understand the Core Architecture and how it consists of the Timer, State Machine, Event Bus and Service Registry and how these interact with Components. The HomeAssistant Developer Docs can help with this understanding although I appreciate that some (many) folk will just want a basic overview.
Great point, that seems to be more of a backend architecture, which is really useful if you plan to contribute towards HA, as a user you will not finding your self interacting with back end much :)
Thanks for considering the newbies! I started using Home Assistant 2 years ago. It was a real uphill struggle. Unfortunately I feel your explanation starts a little too far into the workings of HA. For example, I bought a Raspberry Pi and, lacking any further info, expected to be linking up a monitor & keyboard and accessing HA directly. Why not? that's what I have been doing with computers for years. I struggled to realise that access was only via a web page and the full implications of this. I have to say that, although I appreciate its purpose now, if I had started out by seeing your diagram I would have been put off for good. I hope this is helpful and you are encouraged to do a video on start up concepts.
Appreciate your point of view! My best content for beginners is my free home assistant course! However getting a picture of how complex something is helps!
@@SmartHomeMakers in the same vein, a video about "choosing the right tool for the job" would be a great beginner's guide. Choosing the best use of blueprints, helpers, scripts, packages, templates, etc. in certain contexts is sometimes less than obvious. Personally I tend to design systems with simplicity and the maintainer in mind amd the goal of removing points of failure. With home assistant, it can be daunting at first to choose mechanisms to make stuff happen because it's so flexible, but it's never a good idea to solve problems inconsistently with highly complex systems. That's the biggest challenge with widespread adoption because so many vendors have products that don't have the same approach. I'd love it if all my devices were built on esphome devices because I can enforce systemwide patterns that make it so you don't have to maintain your home like it's a job or require a lot of debugging.
Thank you for this video! So many HA videos just don't bother to explain conceptually what is going on. Making a pure conceptual video removes the distraction of any particular task and allows for a better understanding, facilitating self help and trouble shooting. Well done!
Thanks Matt! Appreciate your comment and kind words
Hello nice video, thanks. One quick question, I use devices into automation triggers and actions, I noticde triggers and actions thru devices is faster than state and service. Any comments? Pros, cons using device in automations? Thank you
Never noticed any significant difference in my end, which device did you use? If it a cloud integration the consistency or latency variation would be higher
Excellent information thank you. Is it possible to get a copy of your chart diagram - very useful 😊
Could you email me and I can reply back!
I wish I'd seen this diagram when I started out. The only thing I would add would be addons. It took me a while to understand the difference between integrations and addons
+1 and HACS
Good shout!
What about a way to "document" your home assistant instance i a "report" that starts with installation choices/settings through where all devices are deployed and where all those files exist on the system? (IP addresses, URLs, ports...)
That report could be pushed to your personal github repo or tagged somehow onto a backup. The goal would be to hand the report to the someone purchasing your house (for a $10,000 addon price of course) or a child/spouse after you pass.
With the report you should be able to install a new HA server, restore a backup and be up & runing on the same network of devices if needed.
Great idea! However we use electricity and plumbing but we don’t know how to maintain it, most people would contact a professional
Not sure how to reply .I cannot use noreply obviously.
there is my email: gio@leonardosmarthomemakers.com
Where do templates fit into your diagram?
more of a language or way to manipulate values of states and attributes to create new entities
What about helpers? Are they part of the helper integration and helper device?
Helpers are just entities that don’t link to a device or integration (external device)
Geo I think this is a really good start, for those who seek a more complete picture of how HomeAssistant works need to better understand the Core Architecture and how it consists of the Timer, State Machine, Event Bus and Service Registry and how these interact with Components. The HomeAssistant Developer Docs can help with this understanding although I appreciate that some (many) folk will just want a basic overview.
Great point, that seems to be more of a backend architecture, which is really useful if you plan to contribute towards HA, as a user you will not finding your self interacting with back end much :)
@@SmartHomeMakers Can you use a smart led bulb in a 3 way lamp? Thank you
Thanks for considering the newbies! I started using Home Assistant 2 years ago. It was a real uphill struggle. Unfortunately I feel your explanation starts a little too far into the workings of HA. For example, I bought a Raspberry Pi and, lacking any further info, expected to be linking up a monitor & keyboard and accessing HA directly. Why not? that's what I have been doing with computers for years. I struggled to realise that access was only via a web page and the full implications of this. I have to say that, although I appreciate its purpose now, if I had started out by seeing your diagram I would have been put off for good. I hope this is helpful and you are encouraged to do a video on start up concepts.
Appreciate your point of view! My best content for beginners is my free home assistant course! However getting a picture of how complex something is helps!
Thank you
Your welcome :) :)
Great overview
Thanks Karl!
@@SmartHomeMakers in the same vein, a video about "choosing the right tool for the job" would be a great beginner's guide. Choosing the best use of blueprints, helpers, scripts, packages, templates, etc. in certain contexts is sometimes less than obvious.
Personally I tend to design systems with simplicity and the maintainer in mind amd the goal of removing points of failure. With home assistant, it can be daunting at first to choose mechanisms to make stuff happen because it's so flexible, but it's never a good idea to solve problems inconsistently with highly complex systems. That's the biggest challenge with widespread adoption because so many vendors have products that don't have the same approach. I'd love it if all my devices were built on esphome devices because I can enforce systemwide patterns that make it so you don't have to maintain your home like it's a job or require a lot of debugging.