Having a central place to view or search through server logs is awesome. I’ve used Graylog in the past, but I’ve always felt it was a bit cumbersome to set up and use — and it felt overkill for my need.

Instead I gave Grafana Loki and Promtail a try 👇

Controlling my Komfovent balanced ventilation system through Home Assistant — opens up a world of possibilities.

Here are three automations I use to make the system a bit smarter 🙂

Mona needed more places to plant her flowers, so I built her some planter boxes — using impregnated wood and lining the inside with landscape fabric.

The Unifi UAP-AC-M access point in my garage stopped working a few weeks ago. Or, the device didn’t stop working, it still showed up in the Unifi controller and I could ping it. But it stopped providing Wi-Fi connectivity — my phone connected, but got no network access…

I remembered experiencing this before — the VLANs for user and guest Wi-Fi wasn’t allowed through the D-Link switch. I had simply not configured them, but why was it failing now?

Trying to log into the switch — I found that it no longer got an IP from the DHCP server. By all accounts; it looked like the switch had been reset.

Last year — I wrote about plans for my home network, or home network v2, as I called it. Let’s take a look at what I have done, what remains, and what has changed since then.

After my Wi-Fi mapping adventure — I found a few spots with low Wi-Fi signal. Both kids’ rooms on the 2nd floor only had mediocre signal, at -67 and -68 dBm 2.4 GHz, and the side garden had -71 dBm — which is terrible!

I also discovered that Mona’s side of the bed had much worse Wi-Fi signal than my side. This was because I had a clear line of sight to the UAP-AC-IW in the den, but the signal to Mona’s side had to go through a wall and her wardrobe…

Simply not acceptable, something had to be done!

Hello again reader; I’ve been AFK for a few months — got fed up with computers and did other things 🙂

I’ve had many routers over the years — Linksys WRT54GL, Linux and iptables, ASUS RT-N66U, Ubiquiti USG, OPNsense, Ubiquiti EdgeRouter, and MikroTik CCR1009. At least those are the ones I can remember.

But I’ve been fascinated by VyOS ever since I first heard about it, even more so after using the EdgeRouter CLI. As both VyOS and EdgeOS are forks of Vyatta.

Fascinated and intimidated is probably more accurate — the lack of a GUI doesn’t give you a lot of help… But at the same time, it’s a great learning experience — you have to know and understand what you are doing 🙂

So I set out to replace my internet facing router — with a virtualized VyOS instance 🙂

We got balanced ventilation installed last year, and have been very happy with the system 🙂 But we quickly found that we needed to expand it into two more rooms — the 1st floor bathroom, used as the laundry room, and the play room, which will be a bedroom at some point.

Time to fix that 🙂

I set up a super simple status page for the homelab — using a small bash script, NetBox, AWS S3 and CloudFront.

But ended up using a hosted service instead — HetrixTools.

I’ve already written about my PDU suddenly dying — and in that post I explained that I was going to do some changes to the homelab power layout. It’s time to do those changes 🙂

It’s time for another ZFS pool expansion. When I last expanded; I doubled the capacity of my 2nd vdev — going from 16 TB to 32 TB raw capacity. This time I’m doubling again — replacing the last limiting drive, and fully utilizing the all the 8 TB drives 😃

I’ve been planning to enable scheduled S.M.A.R.T. scans ever since I built my file server, but it was just one of those things that I never got around to do.

Well — when one of the 8 TB drives suddenly started reporting S.M.A.R.T. errors, the scheduled scans got back on the agenda. So let’s do that now 👇

I have a local mail server with Postfix and Dovecot — I use it as a local SMTP smart host, and “notification center”.

While gathering information for this post; I discovered that my file server have been sending me emails, warning me of S.M.A.R.T. errors on a disk in the ZFS pool. Every day — since September!

So I’ve included a section on how to avoid missing important server emails.

Since we first moved into this house — I’ve wanted to ceiling mount a Wi-Fi access point on the 2nd floor. But getting a network cable to the attic was challenging, so instead I opted for a Unifi UAP-AC-IW in the upstairs living room.

It’s time to do it right, but I’m not running just one. My earlier Wi-Fi mapping revealed poor 5 GHz coverage in the kid’s rooms, so I’m running two CAT6 cables — for two ceiling mounted Wi-Fi access points.

To have the option of running more CAT6 to rooms on the 2nd floor later — I’m including a 10 Gbit fiber as well 😎

And as my previous runs — no visible cables.

My homelab PDU suddenly died! It’s dead, D-E-D, dead! There are few things worse than a server rack suddenly going completely silent…

The PDU has had an error since the power outage last summer — F11 means Power fail on auxiliary 1. Which is an odd error for a PDU with only one input. And; it wasn’t possible to clear or reset it it 😕

In my new home office — I never got around to set up an organized system for my tools. I’ve had some in tool cases, others in boxes — with lids. Not a good system…

I’ve found that if something is out of arm’s reach, I’m far less likely to put it back when I’m done with it. So I’ve accumulated tools; on the bench, and on the floor.

But — with my new tool trolley; I’m hoping to solve all these issues 😎

Comments. I’ve written about them before, two times — but here we go again.

Long story short; I’ve spent some time thinking about adding comments, and think it might be time to give it another try. Why now? As my traffic numbers have gone up, so has the emails from readers. I don’t get a lot — by any measure, but I do get some with very good insight about the post.

I’d like to share that knowledge, but reworking it into the article is not always so easy. With a comment section; they could be put on display 🙂

I’m using a Raspberry Pi to communicate with the power equipment in my homelab rack; the UPS, ATS and PDU. For the UPS, I’m using NUT (Network UPS Tools), and for the ATS and PDU; my own PowerWalker Python library.

In this post I’ll be going through how I’ve set up the NUT server to communicate with my PowerWalker VI 1500 RT HID UPS, and NUT clients running on all other physical machines in the rack.

In 2021 I wrote 69 blog posts, which is an all time record for me. In 2022 — I’m going to try and keep it going 🙂