Documentation and Configuration of my Home Assistant powered Smart Home installation.
Raspberry Pi 4 B 8GB | Dual Fan Aluminium Heatsink Case for Raspberry Pi 4 | Sandisk Extreme microSDXC 128GB | Raspberry Pi 4 USB-C 5.1V 15.3W PSU |
---|---|---|---|
![]() |
![]() |
![]() |
![]() |
This hardware isn’t anything amazing, but for my current needs it is more than satisfactory, and should be future proof enough to see me well into the next few years of automation.
Obviously I am running the latest version of Home Assistant (ver 2021.3.4 at time of writing) on the hardware listed above. For my current needs this is more than enough to run my instance of Home Assistant.
On top of this vanilla install of Home Assistant I am also running a few other applications, as listed below:
Currently I am only using Node-RED to run a script to integrate my Smart Robot Vacuum (Roborock S6 MaxV), as there is no native integration with Home Assistant for newer models of the Roborock vacuums. This was achieved (after many headaches) by using a ‘token extractor’ developed by Piotr Machowski (https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor). This token then can then be inputted into the Xiaomi Roborock connectivity nodes (https://flows.nodered.org/node/node-red-contrib-miio-roborock) in order for me to issue simple commands to my vacuum cleaner from inside of Home Assistant.
In order to circumvent the nightmare that is proprietary Zigbee hubs, and still capitalise on the many benefits of Zigbee, I am currently running Zigbee2MQTT in tandem with Mosquitto to handle the MQTT side of things. In order to ‘talk’ to my Zigbee devices I am using a CC2531 purchased from eBay (https://www.ebay.com.au/itm/224344010798?chn=ps&mkevt=1&mkcid=28). This allows me to ‘sniff’ Zigbee data and convert each ‘sensor’ to a topic in MQTT which means I can then detect posts to these topics based upon a change in state of the sensor and detect this as an update in Home Assistant, or run this process in reverse, and publish a message to one of the sensor’s topics in order to facilitate a state change.
As I mentioned earlier, Mosquitto is used to handle all of MQTT back and forth from the Zigbee devices. Nothing special here, just a basic installation of Mosquitto that is subscribed to the topics that my sensors are posting to.
This is a fairly new addition to the arsenal, and I am beginning to use Grafana map and view data over time, in an easy to read format. Currently I am tracking power usage from a few devices, and graphing this to track consumption. Once again, nothing revolutionary
I’m running Nabu Casa for 2 main reasons: 1) To be able to access Home Assistant via the Android App, 2) in order to cast Home Assistant to the 2 Google Home Hub’s that I use as in home interfaces.
Considering I create, and maintain networks for a day job, you’d think my home network would be something a bit more interesting, however this setup has filled my needs (in its various iterations) for several years now. Below is a map of my network, and its function.
Currently my Internet is powered by the Huawei B818 modem, to connect to 4G, however this is in bridge mode due to having incredibly limited functionality out of the box.
My TP-Link Archer C2 is used to handle all of the actual networking, as like previously stated this is not a strong suit of the B818. I am running 2 separate Wifi channels, one on 2.4Ghz, and the other on 5Ghz. Obviously I prioritise the 5Ghz signal for devices that are close enough (and equipped) to receive it, however the 2.4Ghz is there for those older devices, and devices that are just that little bit too far from my router to pick up the 5Ghz signal. The Archer also handles IP allocation, and all of my sensors and smart devices are assigned a Static IP outside of the DHCP reservation to remove any possibility for things to get confused with their IP addresses (this happens all too frequently if the IP addresses are assigned dynamically).
I am looking at upgrading this network in the near future and replacing it with some Unifi gear from Ubiquiti. Below is a more detailed look at my proposed network map (if I can ever justify the $$$)
In Australia, for the longest time, there was only 1 choice when it came to Voice Control; Google. When Amazon first released their products they were not available in Australia, and up until very recently although available they weren’t supported. This meant that as an early adopter of this technology I was only left with one option. At the time I had just moved myself and my partner across to Google Pixel’s from our iPhones, and i felt that the Google Home was the natural next step.
Currently in my home I have:
This is somewhat overkill, but I seem to be a lamp, that everyone Google Home’s gravitate towards like moths, when the original owner gets over the novelty of “Hey Google! What sound does a cow make?”
Light Control - LED Strips, Wall Switches and Bulbs
Climate Control - Control our 2 Airconditioners
Media Control - Turn on/off Media Devices, play Media
Although currently I dont really use any TTS (except for a talking clock script created in Node-RED by my father), it is something that I have toyed with the idea of for a while now. Half of me thinks it would be great to get TTS notifications about certain events, while the other half thinks about how quickly it would get turned off after the novelty wears off.
I originally began using Home Assistant because I had too many sensors, all with proprietary apps to track, and while it all made sense to me, my partner could not make head nor toe of it and thus would not use the system correctly.
I have a Xiami Aqara Door sensor, to detect when the front door is opened/closed and this in tandem with my phone’s GPS then triggers Automations such as vacuuming the house, or turning on the lights.
Philips Hue has always been the ‘gold standard’ in terms of Home Automation in my eyes, however having to buy a hub was big barrier to entry. This was removed with the advent of Zigbee2MQTT, and by god i’m glad it was. I currently have 2 Philips combination Lux/Temp/Motion sensors positioned near both of my air conditioners in order to detect the difference in outside/inside temp, and turn on climate control until they are at equilibrum. The Lux sensors are also a good way to turn lights on/off without having to rely on Sunset/Sunrise times.
For my lighting, once again it comes down to what was cheap/available at the time of purchase.
These were the first lights I ever bought, and they have always been some of my favourites. With a bit of work you can even put them into a local mode that doesn’t require requests to leave your local network (very handy when the internet goes down). I currently have 3 Yeelight RGB Bulbs, and I use them in my lounge room as they have a good white gamut, as well as bright vivid colours that are great for Multimedia.
These are a recent addition, and I only have 1 as I received it as part of a bundle deal. It works very well, and also has the added bonus that it acts as a Zigbee extender
These bulbs were purchased for 2 reasons: Affordability, and ability to extend my Zigbee network. They serve their purpose and I dont really have any complaints, except for the fact that they aren’t tuneable, and are warm white (not a fan in tropical QLD).
This is the section for all the devices I couldn’t fit anywhere else.
As the owner of a Japanese Spitz in a sub-tropical climate, I’m no stranger to dog-hair (or floof as my partner likes to call it). After countless hours of watching reviews, comparing features and price the Roborock S6 MaxV seemed to come out on top, and also seemed to have a pretty easy workaround for controlling it via Home Assistant. I had this vaccum for a little over 9 months, and I must say it has been one of the best things I have ever purchased. vacuuming, mopping, sweeping it does it all!