Using Home Assistant for centralised home control

Using Home Assistant for centralised home control

I run Home Assistant on a Raspberry Pi as my central controller. I want local control, not another cloud app I need to babysit, and I want a touchscreen that shows the doorbell camera, heat pump status and ventilation readouts. The setup below is the version I would use again.

Getting started with smart home integration

Overview of smart home integration

Smart home integration means getting different devices to talk to one controller. That controller becomes the place for status, control and automation. Here I use it for sensors, cameras, HVAC gear such as a heat pump, a ventilation unit, lighting and the doorbell camera feed.

Importance of centralised control

A single controller cuts down on guesswork. One dashboard can show the doorbell camera, the heat pump and the ventilation unit. It also lets automations cross radios and vendors, which is where these systems usually start misbehaving. Local automation avoids cloud lag and keeps more of the home off someone else’s server.

Setting up Home Assistant

I’d use Home Assistant on a Raspberry Pi 4 with 4GB or 8GB. Run Home Assistant OS on a fast SD card or, better, an SSD on a USB 3 adapter. The usual setup is:

1. Download the Home Assistant image and flash it to the storage media.
2. Boot the Pi and finish the initial web setup at http://homeassistant.local:8123 or via the Pi’s IP address.
3. Add the integrations you need: MQTT broker, ONVIF or RTSP for cameras, and Z-Wave or Zigbee via USB stick if you use those radios.
4. Install the Lovelace dashboard and add a camera card for the doorbell feed on the touchscreen.

Check it on the touchscreen before you call it done. Open the Lovelace view and tap the camera card. The feed should appear without much delay. If it freezes, switch the camera to RTSP in its settings.

Choosing the right hardware

Pick hardware that supports local protocols. My list is simple:

• Raspberry Pi 4, 4GB or 8GB, with SSD boot if the budget stretches to it.
• USB Zigbee stick, such as ConBee II or Sonoff Zigbee 3.0.
• USB Z-Wave stick if you have Z-Wave devices.
• Ethernet to the Pi for stability, not Wi-Fi, if you can manage it.
• A 7 to 10 inch HDMI touchscreen for a hallway display.
• A doorbell camera with RTSP or ONVIF support.

For a heat pump and ventilation unit, check the manuals for Modbus, LAN API or dry contacts. Some HVAC and ventilation units expose Modbus RTU or Modbus TCP, or a simple open and close input for mode control. If there is no network port, you may need a gateway or relay interface.

Compatibility with smart devices

Casambi lighting uses Bluetooth mesh. That means you need a Casambi gateway or a bridge that talks to Home Assistant. Sonoff and Tuya devices often work if you can flash local firmware such as Tasmota, or if the device already supports local MQTT or a LAN API. If a device is cloud-only and cannot be made local, I’d treat it as the weak link and replace it if possible.

Before buying, check for RTSP, ONVIF, MQTT, Modbus or a documented LAN API.

Advanced smart home automation techniques

Integrating multiple devices

My aim was one touchscreen that shows the doorbell camera and controls HVAC and lighting. Running low-voltage data cables back to one place makes life easier. For radios that do not share a stack, use bridges: Zigbee-to-MQTT or Bluetooth-to-MQTT bridges let otherwise incompatible kit speak the same language.

Example setup:

• Cameras via RTSP into Home Assistant.
• Casambi via a Bluetooth gateway that exposes MQTT topics for brightness and scene control.
• Heat pump via Modbus TCP or a manufacturer API integration.
• Ventilation unit via Modbus or a relay input controlled from a GPIO expansion board or a dedicated interface.

Custom automation scenarios

Write automations in YAML or use the visual editor. A few I use:

1. Ventilation pause for open windows

   • Trigger: window contact opens.
   • Condition: ventilation in auto mode.
   • Action: switch ventilation to low or pause.
   • Check: confirm the ventilation unit status entity changes and a timestamp appears in the log.

2. Doorbell to touchscreen

   • Trigger: doorbell pressed.
   • Action: show the camera full-screen on the touchscreen and play a chime.
   • Action 2: if it is night, turn on the porch light at 30% for 2 minutes.

3. Heat pump seasonal setback

   • Trigger: outside temperature sensor and time of day.
   • Action: set the heat pump target temperature through its integration.

To build a simple automation in Home Assistant:

1. Create the entities for the device you want to control, then check they appear in Developer Tools.
2. Build the trigger and test it by firing the trigger in Developer Tools.
3. Add conditions and test the automation with the Developer Tools simulate function.
4. Turn on logging for the automation and watch the state changes in the logbook.

Use History and Logbook to confirm the automation fired and the device states changed the way you expected.

Troubleshooting common issues

The usual failures are cloud-only devices, radio range and flaky integrations.

• Cloud-only devices: replace them or use a local bridge.
• Bluetooth range for Casambi: Bluetooth mesh needs nodes in range, so a centrally placed gateway helps.
• Camera lag: use wired ethernet where possible. If you are on Wi-Fi, set the camera to 2.4 GHz or put a dedicated AP nearby.
• MQTT drops: run Mosquitto on the same Pi or on a local NAS to cut down on network hops.

When something breaks, I check logs first, then entity state, then network connectivity. That order gets me to the fault faster than poking around at random.

Security with smart home tech

Local control reduces exposure. The practical steps are straightforward:

• Keep Home Assistant on a VLAN or separate network from guest Wi-Fi.
• Use strong passwords and long random tokens for integrations that need them.
• Block cloud access for devices that work locally.
• Run automatic backups of the Home Assistant config and copy them offsite.

Future-proofing the setup

Leave spare ports and power at the central point. Keep room for future sensors and a spare USB port for another radio stick. Use MQTT, Modbus and RTSP where you can. Buy devices that expose a local API or a documented protocol.

The short version: use local control first, wire the central point for the devices that matter, and keep automations simple enough to test properly. A Raspberry Pi with Home Assistant, a touchscreen and a few protocol bridges handles the heat pump, ventilation unit and doorbell camera in one place.