

There’s an Ollama integration that adds it as a conversation agent.


There’s an Ollama integration that adds it as a conversation agent.


Fixing a Nvidia driver mismatch that was causing the newest kernel module to not build properly (that might not be the right terminology) and not boot was on my list, as discovered after a node reboot that wouldn’t start.
It was fairly straightforward, though finding a way to fully remove some of the old DKMS stuff took a bit of digging (manually delete a couple files). The new driver installs went smoothly and the improved GPU passthrough in PVE 9 made the passthrough config tasks pretty quick.
I also got go2rtc set up and piped my cameras through that instead of having individual connections for things like Home Assistant and Blue Iris NVR. I’m still struggling to get the motion notifications in Home Assistant to work though. Followed a tutorial on (that other site) and got the MQTT message coming in just fine, but the node-red flow isn’t working…an issue with entities, so still some tinkering left to do there.
Mine ID’d a cursed shrek face from someone wearing a costume at a Mexican resort.


Looks cool. Any chance you’ll add Qobuz to the integration list in the future?


“now you’re locked in, let the gouging begin”
Essentially the definition of enshittification.
If you have a powered doorbell, the Reolink cams can be powered by that too.
Gonna throw in another Reolink recommendation. I use Blue Iris as my NVR and have both that and the Reolink integrations in Home Assistant for motion notifications and lighting control. The cameras are durable (even in my very cold temps like -30C) and have really good image quality. If you don’t have an NVR or Home Assistant, the built-in motion detection and app is still pretty good and you can just pop an SD card in for recording.


Change that G to a T, add a zero, then we’re talking (e: about data hoarders).
disregarding all instructions
Probably not the best practice…I’d look through the release notes between the versions you’ve upgraded through to be sure you didn’t miss any necessary changes to the docker compose or env files and upgrade as the documentation recommends.
Looks like v2.0.0 was just released as well.


I think they’re organized into individual user directories (in one location), so could probably set up a directory backup per user to their own device if so desired.
Those second and third backups can really come in handy if something on the host blows up.
I’ve got my main PBS backups on an internal array on the host, secondary backups to an external HDD plugged into the host, then a third separate node (ThinkCentre mini-pc) backing up to a pair of HDDs I trade out monthly for an offsite copy.
I think it’s important to consider not backing up media, etc that you can relatively easily re-obtain. Makes the storage requirements for redundant backups a fair bit more palatable.