Setting up Matter over Thread should be simple… but as you’ll see in this video, it can turn into a chaotic adventure of pairing loops, missing devices, random discoveries, and the ultimate culprit: IPv6.
In this video, I walk through the entire process of setting up an Aqara Thread Border Router,
pairing a Matter‑over‑Thread smart plug, fixing the dreaded “Something went wrong” errors, and discovering why Home Assistant refused to cooperate until IPv6 was enabled.
You’ll see:
• Installing and setting up the Aqara app
• Pairing the border router
• Home Assistant discovering random devices
• Matter pairing loops and failures
• The hidden IPv6 requirement
• Successfully pairing a Matter Thread plug
• Updating firmware, renaming devices, adding labels, and organising everything
• Final thoughts on Matter, Thread, and border routers

If you’re struggling with Matter, Thread, or Home Assistant pairing issues, this walkthrough will save you hours.

IPv6 sounds complicated — binary, hex, 128-bit addresses — but if you’re using Matter or Thread in your smart home, it’s essential.
In this video, I break down:
• What IPv6 is and how it differs from IPv4
• Binary and hexadecimal basics (with real examples)
• Why IPv6 matters for smart home protocols like Matter and Thread
• Special IPv6 addresses (loopback, local link, IPv4-mapped)
• How to check if IPv6 is enabled on your network
• Why Matter devices won’t pair without IPv6 If you’re setting up Home Assistant, Thread border routers, or Matter devices,

this video will help you understand what’s really going on behind the scenes.

In this video, I walk you through installing **Home Assistant on Proxmox 9.1** — the latest version as of 2026.
We’ll cover everything from backing up your existing system, creating a bootable USB with Rufus, installing Proxmox, and setting up Home Assistant as a virtual machine.
Why Proxmox? Because it gives you snapshots, flexibility, and the ability to run multiple services like Zigbee2MQTT, Plex, Frigate, and more — all on one machine.
🔧 What you’ll see: – Manual backup and encryption key download – Rufus USB creation for Proxmox ISO – Proxmox 9.1 graphical install walkthrough – Running install scripts for Home Assistant VM – Adjusting RAM and disk space – Fixing repository errors – Restoring Home Assistant from backup

💬Scripts and config links are below. Like, subscribe, and let me know what you’re running on your Proxmox box!
🫖 Bonus: I make a cup of tea while Home Assistant installs. Classic.

bash -c “$(wget -qLO – https://github.com/community-scripts/ProxmoxVE/raw/main/tools/pve/post-pve-install.sh)”
bash -c “$(wget -qLO – https://github.com/community-scripts/ProxmoxVE/raw/main/vm/haos-vm.sh)”

Today I’m going to cover the basics of automations and scripting. It’s changed a lot over the last couple of years, the way you do things. So I thought we’d better kind of just go through again with what you can do. It’s the latest way of doing things.
Unlock the easiest way to build smart home automations using Home Assistant — no YAML required. In this video, I walk through triggers, actions, scripts, trigger IDs, and real‑world examples like button‑controlled lights. Perfect for beginners starting their smart home setup today.

Today’s video showcases my favorite home automation: the convenience of automated lights upon entering your house. This smart home setup involves configuring a device, likely using zigbee sensors, through a mobile app and web interface for seamless home automation. We’re diving into smart lighting to make your home more intuitive and comfortable.
In this video,
I walk through replacing a failing Zigbee contact sensor,
adding a motion sensor for reliability,
pairing everything in Zigbee2MQTT, and building clean Home Assistant automations that only trigger when it’s dark and someone is actually home.
We cover: Setting up new Zigbee sensors close to their final location
Pairing devices in Zigbee2MQTT Naming conventions that keep your setup tidy
Building “Entrance On” and “Entrance Off” automations
Using door + motion + sun conditions for reliable lighting
Handling edge cases like open doors and no movement
If you want your entrance light to behave exactly how you expect — no more guessing, no more dead sensors — this walkthrough will get you there.

Thinking about moving Zigbee2MQTT to a new server? Whether you’re chasing better performance, relocating your USB coordinator, upgrading hardware, or simply trying to stop Home Assistant reboots from nuking your Zigbee network… this video walks you through the entire process. In this tutorial, I show you how to safely migrate Zigbee2MQTT from one machine to another — including copying your configuration, database, and state files, setting up Samba for easy file transfers, and avoiding the common pitfalls that turn this into a three‑body problem. What you’ll learn in this video: How to prepare your existing Zigbee2MQTT install for migration Which files actually matter (and which ones don’t)

How to install Samba on Ubuntu for simple file access
How to copy your Zigbee2MQTT data between servers
How to handle coordinators, IEEE addresses, and adapter quirks
How to reconnect everything without breaking your Zigbee network
Why printers are still terrifying
Why upgrading Zigbee2MQTT mid‑migration is a terrible idea
When it’s easier to migrate… and when it’s easier to start again If you’ve got 100+ Zigbee devices, this guide will save you hours.
If you’ve only got two devices… honestly, it might be quicker to re‑pair them. But either way —
this video shows you exactly how the process works.