I’ve got a Fairphone 3 with /e/OS corresponding to Android 13 installed (/e/OS 3.2-t-20251022539004-official -FP3). Foss Warn, an alternative to Nina and KatWarn that does not need Google services, did work flawlessly in its old version using a pull mechanism. Some time ago with version 1.0.0 it switched to push. It took me some time to fiddle out how to set everything up. And at first it seemed to work out. I had an abo and initiating a testing message did result in a notification. However, it does not work! Messages are not shown automatically. Only if I open up Foss Warn, it fetches warnings after some time of “consideration”. Also after a while the current abo becomes disabled and I have to activate it again. This is not how push should work. Today a testing alarm of sirenes took place and no notification came.
I noticed, that there are 2 ntfys installed and operating, one from /e/OS, that can not be accessed via the Apps menu and shows up only in settings and battery, that seemingly does not allow for choosing a server, and the one I installed via FDroid and have set to use ntfy.adminforge.de according to the installation instructions of Foss Warn.
Both ntfy instances are active at the same time and use up battery power, so I think they may be in conflict with each other. Accidentally I once came across a setting to allow access from third parties to ntfy, which I activated. Unfortunately this setting does not show up, when using ntfy or push as a keywords in the search function of settings. So I have got no idea how to find it again. May this setting be the problem?
just switch off the built-in ntfy-clone in device settings → system → unified Push
yes, pretty awkward that built-in ntfy-clone does not show up when ntfy is searched in device settings.
This behaviour is also reported as a FOSS Warn issue (and I observed it too):
Maybe you will add your observations there.
Since a few days there is a new version 1.0.1 of FOSS Warn available (on F-Droid). It has got some improvements concerning setting up the Unified Push service and also a self test. The latter may give you some more information.
For this device, as I try to test Foss Warn (including as @obacht suggestion install io.heckel.ntfy v-1.18.0) still fails UP Example, org.unifiedpush.example.
In your self test screenshot there is only one “UnifiedPush Distributor” available.
It seems the installation io.heckel.ntfy is not running. This has to be examined first. The default server used by io.heckel.ntfy is not working reliable. Change the server used by ntfy as described in the wiki.
If ntfy is running then UP Example should work!
Then select io.heckel.ntfy in FOSS Warn. The self test then should display it as “Selected Distributor”.
Additionally you have to disable UnifiedPush in the settings of /e/OS: Settings→System→UnifiedPush
on my pixel4A 3.3-a15-20251211556413-community-sunfish
it works ootb with foundation.e.ntfy-server
(maybe there have been fixes in the background in the meantime because from what I recall it did not work some in the past with some previous eOS-version - and for me at that time it was just “some other glitch” that I did not bother much whilst trying to set up Mollys UP on my S7…)
self check works OK
Thanks for the feedback @MiSta, unfortunate of me to proceed before UP example passed. However with proper rtfm as soon as UP example passed with io.heckel.ntfy then Foss Warn gave all green and apparently reliable Notifications on device.
Looks good! I have seen in GitLab there were some merge requests concerning ntfy coming now with /e/OS 3.3. Maybe the issues observed, reported, and discussed by us are now actually fixed.
Unfortunately, /e/OS 3.3-official is not yet available for my OnePlus Nord. I will test UnifiedPush and FossWarn with foundation.e.ntfy when I’ve updated to 3.3.
while waiting for the release of /e/OS 3.3 for all devices that are still stuck at 3.2, I saw that breezy weather supports FOSS public alert server in beta phase. Could this be a working alternative? or would it have the same problem?
Today I upgraded my OnePlus Nord (avicii) to the latest /e/OS 3.3-s-official (A12) and was now able to examine the Unified Push issue with FOSS warn further:
It seems there is no more possibility to disable the built-in foundation.e.ntfy in the settings and it is always running: Test messages sent by UP Example app are always received on both distributors.
It seems that disabling it is not required anymore! FOSS Warn works as soon as io.heckel.ntfy is selected in FOSS Warn:
Yes, strange, I didn’t install ntfy separately, it ran with the onboard service…
But now I’m getting a message from foss-warn saying that the subscriptions have expired and re-registration is failing, and I can’t add any locations…
Also: UP seems to be gone from device settings - system, really odd…
Can you check in your 3.3 @MiSta ?
I think that part is not fully implemented on e’s end…
I switched back to ntfy-install for my signal …
Foss warn does not work on my system anymore with neither ntfy (onboard or install)… Who knows what they did in the background…
But it seems there is no need to disable it. On my phone FOSS Warn is working even if both ntfy implementations are running in parallel (but you have to choose io.heckel.ntfy as distributor).
