Hopefully this is the final installation step of my matryoshka virtual bean counter, ie Grocy running on Home Assistant (HA) running on a virtual machine running on my PC. Home Assistant is explicitly designed to be interoperable with and extensible to as wide a range of devices, protocols and programs as possible and uses integrations to link in specific home automation devices and services. However for third-party programs that deliver more extensive functionalities the term Add-on is used and Grocy is an example of such an Add-on. So our first step is to navigate to the Add-ons screen ( Settings > Add-ons ). If you are using a clean install there will be nothing on this page. From here we follow the link to the Add-on Store (bottom right-hand corner above). Don't try to use the search bar ( Search add-ons ) at this point as it won't work, it only looks at your installed Add-ons. Once you are in the Add-on Store using the Search bar will return the link for ...
Now I have a virtual Raspberry Pi set up this should be a discussion on how to get Home Assistant (HA) installed on it. Correct? Well, no. Once I'd got the virtual Raspberry Pi up and running, and forearmed with my (limited) knowledge of how VirtualBox works, I went looking for a distro of Home Assistant that would run on the Raspberry Pi Desktop OS . Only this time I made sure I read the whole list and r ight at the bottom I found what I was looking for - Install Home Assistant on Other Systems . However, instead of needing a prepared Raspberry Pi this protocol will install everything in a single process. It turned out, as I read another manual, that Home Assistant is actually an OS in and of itself. The Open Home Foundation , the developer of HA, uses another piece of open-source software, Buildroot , to craft a bespoke version of Linux it calls the Home Assistant Operating System (HAOS; previously known as HassOS). Although the process of setting up the HA virtual machine (V...