Tootfinder

Just to be clear: :homeassistant: #HomeAssistant does not have a UI to delete timespans of (bogus/calibration) data? Unless you sift through the various tables in the sqlite db and manually delete the offending rows, those data will forever taint all of your statistics and graphs? 🤔

RE: #homeassistant

Genug Starkstrom-Leitungen für die PV-Anlage verlegt – Zeit für den feinen Lötkolben und das Elektronik-Lab! 🔌🛠️
Als erstes Projekt steht jetzt die saubere Integration der Anlage in #HomeAssistant an. Datenströme visualisieren, Automationen bauen und endlich die volle Kontrolle über die eigene Energie haben.
Lötkolben ist heiß, Oszilloskop läuft – jetzt wird gebastelt! ⚡️…

Update on the #homeassistant restore - everything worked almost perfectly. Three gotchas I found so far:
- The “restoring” page would just keep displaying, since after the restore, the service no longer responded to homeassistant.local. Luckily I saw my soundbar turn on, which is always a good indicator that HA rebooted.
- The backup seemingly did not contain the sound files I had uploaded, so my improvised temporary doorbell is borked until I upload a new sound file.
- The most interesting one: The zigbee devices did not reconnect initially, except for a single one, and the reason was interesting - I learned something new about Zigbee today.
Apparently Zigbee has a frame counter, and the devices will remember the last frame counter they observed, and refuse messages with a lower count afterwards. The backup contained stale frame counters, since the machine died several hours after the last backup, hence, all devices were refusing messages from the coordinator. The solution was to power-cycle all mains-powered devices. The battery-powered devices came back automatically after that, except for two buttons which I had to re-pair manually. Credits to Claude for figuring this out based on the logs.
Other than that, quite happy with the “restore from backup” on Home Assistant for now. Now I only need to reconfigure my two wall tablets to point to the new local home assistant URL, as the RPi has a different hostname on my network now, and the wall tablets used the local alias of the old machine for the connection, as I did not want to route them via the internet ingress through Nabu Casa. But that’s not the fault of the backup, that’s just me configuring my stuff weird.

What can I say? Not much yet, I need to digest that I just acquired freaking DFG funding. You got to love German bureaucracy. Sometimes. A bit.
As one likes to say: Die Gutachten zu diesem Antrag fallen in allen wesentlichen Hinsichten positiv aus.
Scream Emoji.

Die Wut über unser vollständig autozentriertes Verkehrssystem und seine Befürworter:innen kommt ja nicht nur daher, dass Autofahrende ständig Fehler machen, sondern auch daher, dass für die eigenen, genauso unvermeidlichen Fehler Schmerzen drohen. So wie bei diesem jungen Mann in Uelzen.
https://www.presseportal.d…

Well, since my #homelab server randomly died yesterday, I guess it’s time to find out how well the #homeassistant backup/restore system *actually* works in practice. Setting up a temporary HomeAssistant instance on an old Pi4 to make sure the house works again while waiting on the response by #Geekom on my warranty claim for the dead machine.

Minor post on using groups instead of devices in #HomeAssistant automations.
https://unixorn.github.io/post/hass/2026-10-17-use-groups-instead-of-devices/

Okay, it turns out that the media was missing from the backup because I had not actually *turned on* backups for the media, so... Yeah, kind of my fault. #homeassistant

Also thinking about what to do in the medium- to long term. Continue with Proxmox? Switch to a bare-metal OS install, since I was mostly using a single VM Docker for everything anyway, and get a HomeAssistant Green for my HA to keep it on separate hardware from the home server? Get two or three cheaper individual machines, connect them into a k8s cluster, host applications on that? Everything has its advantages and drawbacks. #selfhosting