As shown in some of my earlier posts, I run a fair number of services at home, and I like to measure things. Two of the things I measure are the electricity meters in the basement: one for the house and one for the heating. Both are modern meters with an optical (infrared) interface, and for years a small script has been reading them and pushing the numbers into MQTT, from where the rest of my homelab picks them up for dashboards and the occasional automation.

Running services in Docker is easy. Running them securely, observably, and without punching unnecessary holes into your host? That’s where things get interesting.

IKEA’s Tradfri series offers a very affordable entry into smart lighting, with a range of ZigBee-controlled RGB and RGBW bulbs. While they work well for color effects, there’s one glaring shortcoming: the RGB lights struggle to reproduce accurate white color temperatures. Warm whites can appear too pink or yellow, and cooler whites can lean slightly green or blue.

AI Agents are often limited to triggers by humans. This is a big limitation. I wanted my AI Agents to be able to schedule work for their future selves. Not Cron. Not a waiting loop. A proper “Hey, wake me up in 20 minutes and remind me what I was thinking” kind of timer. So I built a small workflow that acts as a self-activating timer. Any AI Agent can call it, hand over an interval and a prompt, and then, after the timer expires, the agent is pinged again with precisely the context it left behind. It turns out to be both incredibly simple and incredibly useful.

I’ve always been passionate about home automation and automating my life. When I discovered n8n’s powerful workflow automation capabilities, I was slightly disappointed that there was no built-in option to control Kodi. But that is what open-source is for, so let’s create it! That’s how n8n-nodes-kodi was born – a comprehensive plugin that brings the full power of Kodi’s JSON-RPC API to n8n workflows. Note: Most of the plugin, as well as this article have been written by AI.

I have been having some issues with setting up rspamd in combination with Dovecot >2.4. It seemed there was no complete documentation and the configuration options have changed quite a bit in Dovecot 2.4. So I pieced this together myself and provide it as a short tutorial here. Of course, there is lots of possible implementations of this, I use a smarthost setup with Fetchmail. Since no spam filter is perfect out-of-the-box, I also wanted to have learning of spam/ham supported.