this post was submitted on 13 Apr 2025
49 points (96.2% liked)

Selfhosted

45897 readers
358 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I currently do a lot of my monitoring via MQTT for my solar system etc. I currently use MQTT Alert and set up my alerts to ring my phone at top volume until silenced. But I have missed more than one alert because I don't think the background agent is always active and it doesn't necessarily start when I reboot the phone. While the application does "monitor" the MQTT connection, it only makes a short sound if it drops, with no followup until you notice that there was a notification and go back into it to figure out why the connection is down.

Does anyone have foolproof way of getting things like security alerts that will always trigger on the phone, without having to check the phone 10 times a day to be sure the application is on and the connection is active?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 3 days ago (1 children)

Mine is a Pixel running GrapheneOS, and it doesn't seem to be on your list. My issue is that I'm not using Google Play Services, so I don't get the benefits that it provides, one of which is managing notifications. So Signal has to manage notifications itself, which means it basically needs to always be running instead of the more typical Android model of being woken up when there's a notification.

Or maybe it's what you linked. Either way, I'd check that and see if it's an easy fix.

[–] [email protected] 2 points 2 days ago

For signal, you can look into a fork called Molly. I have Molly setup, along with molly-sockets, which allows for notifications via unified push