Home monitoring with Zabbix: the complete starter guide

By day I lead site reliability engineers in a global cybersecurity company. By night I use my spare time to turn my home into a Zabbix monitoring lab, and I have been doing it since 2017. This guide collects the pieces that actually work, so you do not have to start from an empty dashboard.

Zabbix is free and open source and scales from a single Raspberry Pi to an enterprise estate. The whole trick of home monitoring is that you already own the things you want to watch: temperature sensors, power plugs, a router, a car, a fridge. This guide shows how to bring them in and get value on day one.

What can you actually monitor at home with Zabbix?

Anyone not following the blog expects servers. In practice the fun is elsewhere:

• IoT devices: smart lights, motion sensors, door sensors, thermometers and energy meters through a hub such as Cozify.
• Home infrastructure: your router, Wi-Fi signal strength, network traffic, backups and Raspberry Pi health.
• Energy: the electricity price, grid power consumption and tripped fuses.
• People and pets: when the baby wakes up, whether the kids' devices are on, whether the dogs came home, and how often someone forgets their facial cream.
• Vehicles: in my case the Toyota bZ4X electric car, from battery to charging cost.

A doorstep-sensor box that tracks facial cream usage (part 4) is a great example of the mindset: monitoring does not have to be serious, but the method is the same one you would use in production.

What hardware do you need?

Not much. My whole lab has run for years on a Raspberry Pi 4 that happily also serves the blog and other jobs. Zabbix 7.0 runs noticeably lighter than 6.4 there, mostly thanks to the threaded collectors (part 58). I reflected on the full experience after nine months (part 33). For sensors I rely on the Cozify home-automation hub we have owned since 2017: one hub, dozens of device categories, and my own side that loves the data it exposes (part 1).

Step 1 - Get Zabbix running

Start with a single Zabbix server on your Pi and keep the rest boring. When Zabbix 7.0 came out I moved the main instance over (part 58) and the upgrade was painless, data, dashboards and triggers intact. When the infrastructure itself needed a refresh, I rebuilt it properly (part 102). For testing a proxy-and-server split, a Zabbix 7.0 proxy on a rented FreeBSD VM does the trick (part 76).

Step 2 - Pull in your sensors and devices

Most home devices do not speak the Zabbix agent protocol. My three favourite bridges are:

• Cozify API via Python: an unofficial read-only Python library reads all sensor values; cron writes text files every five minutes; Zabbix polls a handful of master items and uses dependent items for the 40+ data points (part 1).
• zabbix_sender: for anything that produces a value anywhere, for example the currently playing song pushed at an API (part 93).
• HTTP agent items: when the source already has an API or a web page you can scrape, from Nord Pool energy prices to product prices (part 56).

Once the data is in, you can compare reality to your assumptions: I proved a freezer incident and watched the general chaos unfold in what I call (the Zabbixverse) all with ordinary items and triggers.

Step 3 - Add dashboards you will actually look at

Zabbix collects and alerts; Grafana makes it beautiful. My living-room Mission Control dashboards are cast to the TV and show battery levels, light status, firmware versions and more (part 2). A few dashboard panel ideas later (part 72) the setup matured, and Zabbix 7.0's own widgets got a big quality bump (part 145). If you want text on a dashboard, AI-generated alert summaries work there too (part 66).

Step 4 - Set alerting, not noise

Alerts are the part your family will notice, so make them matter. Email is the reliable default (part 132). When a trigger matters, escalate: my facial-cream slot alerts if the box stays unopened too long (part 4 and its SLA, measured). For the truly sleepy moments, watching when the baby cries is what parents dream of (part 29 and later part 134).

The 7 things to beware when you monitor your home

Nothing is as smooth as it looks. Over a year of home IoT I collected the painful lessons in part 46: the status a hub reports is not always true, low-battery messages lie, Bluetooth and 2.4 GHz Wi-Fi interfere, helper components (hello, Home Assistant in Docker) silently stop, APIs change, and your monitoring itself needs monitoring. Read it once and you will save weekends.

Keeping the lab alive

A monitoring lab must survive its own hobbies:

• Backups: I dump the Zabbix database with BackupPC and monitor the backups with Zabbix (part 25 and part 75).
• HA: a spare laptop acts as a secondary Zabbix node, built ahead of feared power blackouts (part 27).
• Disk: SD cards fail, with and without warning (part 55 and part 141).
• Peace of mind: a maintenance calendar keeps windows visible (part 90) and security basics are in part 48.

Where to go next in this guide series

• Network monitoring: router health, Wi-Fi, NetFlow, DNS and global availability.
• Electric-car monitoring: a real Toyota bZ4X on Zabbix.
• Home energy monitoring: electricity prices, grid power and tripped fuses.
• AI + Zabbix: local LLMs that explain your alerts.

Frequently asked questions

Is Zabbix really free for home use?

Yes. Zabbix is open source and licenced for free use at any scale, including at home. You only pay if you buy vendor support, which a home lab does not need.

Do I need expensive hardware for home monitoring?

No. A Raspberry Pi 4 has run my whole home Zabbix, Grafana and a lot of other services for years. Zabbix 7.0 made it even lighter thanks to the threaded collectors.

How do I get IoT devices to talk to Zabbix?

The easiest path is a hub: Cozify exposes an API that an unofficial read-only Python library can query. Scripts run on cron, write text files, and Zabbix parses them with master and dependent items. For anything with its own API, an HTTP agent item works directly.

Can Zabbix and Grafana work together at home?

They are a classic pair. Zabbix does the data collection and alerting, Grafana the dashboards. There is an official Grafana Zabbix datasource, and Grafana remained happy even after I moved my server to Zabbix 7.0 and 7.2.

How do I alert my family without being annoying?

Keep triggers few and actionable, and escalate instead of repeating. Email notifications cover the reliable base; for habits, a single 'forgotten for too long' alert is enough. The 7 things to beware list in part 46 is the best reality check for home alerting.

Does the What's up, home? blog cover all of this?

Everything in this guide comes from the 170+ posts on whatsuphome.fi, from marrying Zabbix and Cozify to tracking a cruise ship. If a page here links a post, that post has the full details, screenshots and scripts.

First published as part of the home monitoring guide series on whatsuphome.fi. The detailed, screenshot-laden versions of every step live in the blog posts linked above.