view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Can you share the Home Assistant automation / setup that you have for Uptime Kuma notifications? As I'm in the same boat as you. I just got a webhook setup but I'm getting flooded with notifications, especially after services update.
My hope is I just want to be notified when a particular service is down for say 5 minutes but all I care about is knowing the node name. I don't necessarily care to get notified if the service comes back up.
I did it all in Node Red so unfortunately I can't share the automation, but I can point you at this HACS integration https://github.com/meichthys/uptime_kuma
Set that up and all your nodes will be visible in HA then it's just a case of "if node X is off for X minutes" - "notify"
This is what the 'retries' setting in each monitor is for. It will only be considered down if its failed its heartbeat check <retries> number of times in a row.