This is so cool, first MQTT-based sensor I’ve set up. Already had a broker set up with HA, but how can HA automatically discover which topic to listen to, know the vendor name and how to interpret all the data?

Interesting, so I guess those API-calls are just fetching the cached calendar on my HA Yellow. Wonder why it’s so slow, but I guess there’s not much to do about that then. :(

Not exactly. My main use-case here is for my girlfriend and me to see each both of our calendars in one place, and HA had support for it and is a web portal we both have access to. To do automations on them is secondary.

Currently, whenever I look at the calendar control panel it will load for a bit while pulling all the calendars, and sometimes timeout and not show anything. I believe this to be because it’s pulling from Fastmail / iCloud everytime and might be rate limited or just have a poor connection, this wouldn’t be an issue if the calendars were stored on the instance itself because then it would only miss the latest entries.

The idea that maybe I can self-host an app that does it is that if HA can’t do the caching, then maybe this self-hosted app can and it wouldn’t matter that HA fetches it remotely each time since the remote is on the same local network. Having them as separate calendars is still desirable since that gives some additional information.

Is immich in a usable state yet? I was looking for a self-hosted image service a while back, but eventually I just went with pigallery2 mostly due to the extremely simple file storage (just point to a folder and you’re good to go), but I do miss being able to manage images/albums from the website and having a more mobile friendly version. I kind of avoided immich due to the repo saying it’s under very active development (#scary).

the biggest selling point for me is that I’ll have a mounted folder or two, a shell script for creating the container, and then if I want to move the service to a new computer I just move these files/folders and run the script. it’s awesome. the initial setup is also a lot easier because all dependencies and stuff are bundled with the app.

in short, it’s basically the exe-file of the server world

runs everything as root (not many well built images with proper useranagement it seems)

that’s true I guess, but for the most part shit’s stuck inside the container anyway so how much does it really matter?

you cannot really know which stuff is in the images: you must trust who built it

you kinda can, reading a Dockerfile is pretty much like reading a very basic shell script for the most part. regardless, I do trust most creators of images I use. most of the images I have running are either created by the people who made the app, or official docker images. if I trust them enough to run their apps, why wouldn’t I trust their images?

lots of mess in the system (mounts, fake networks, rules…)

that’s sort of the point, isn’t it? stuff is isolated