I updated to /e/OS 3.3 and also realized that the UnifiedPush Setting in System is gone. After some experiments with foundation.e.ntfy, wich broke the whole setup, I removed the external ntfy and Foss Warn and reinstalled both. For some time push registration between Foss Warn and ntfy did not work. Suddenly it did. However, situation is as before. Although Foss Warn is allowed to give notifications it does not, but remains passive. Only when opening it up, it receives or retrieves messages and shows them (such as the warnings for frost and slickness the last time). May it be possible that still some setting in system is missing? UnifiedPush cannot be deactivated in System anymore and if I inactivate the system ntfy, it will soon be active again. Perhaps it is required for /e/Os notifications such as updates?
There is a bugticket for the missing nfty settings: Unified Push Settings missing (#9101) · Issues · e / Backlog · GitLab
I cannot comment on nfty because /e/OS 3.3 is not available for my phone (OnePlus 6; build failed because of missing storage space, next release for it will be 3.4).
If I understand correctly, nfty is now enabled by default on /e/OS so that the /e/OS users may be informed about maintenance etc., see the release notes v3.3-a15 · e / os / 🚀 Releases · GitLab
Notifications
- Notifications regarding /e/OS and Murena Workspace features and maintenance will now reach you directly on your device
(Personally, I think that this is a good idea - users can be informed about known problems with the current release even if not part of the forum. Still, some may prefer to deactivate the notifications so that the settings should be restored.)
Thanks for digging out the gitlab-issue!
I commented there
I tend to agree to the first part but definitely to the latter…
And as long as the built-in UP does not reliably work for messages from other apps (that requirement or usecase is foreseeable) the situation makes users twiggle around and end up with an extra install of ntfy in order to receive messages they rely on with the unused built-in thing still running in the background…
For testing purpose I just switched back to the built-in ntfy/UP (and deinstalled ntfy)
As of now notifications work again for Molly as well as for UP-example.
(3.3-a15-20251211556413-community-sunfish)
I´ll keep that config for now.
Subscribing to locations in FOSS Warn and selftest therein works again as well.
The hidden configuration menu of the build in ntfy of /e/OS will become accessible via Activity Manager app (cf. F-Droid).
In the Activity Manager app:
- open ntfy (foundation.e.ntfy)
- Main Activity (io.heckel.ntfy.ui.MainActivity)
- three vertical dots at the right top
- “Einstellungen” (may be “options” in English)
- “Allgemein” (may be “general” in English)
- Standard-Server: I changed it to: https://ntfy.adminforge.de/
Will notifications about updates etc. from e/OS still be available after changing the standard server?
Yes that should be the case, least of eOS-update per device as the device actively checks if an ota-update is available, it’s pull, not push.
I followed your advice and changed the standard server via Activity Manager. Doing so, I noticed a hint at the top of Activity Manager’s screen, saying I should switch to WebSockets Connection. On my system (German), it’s:
“Der Umstieg auf WebSockets ist die empfohlene Verbindungsweise zu Deinem Server und benötigt möglicherweise weniger Akkuleistung…”
(“Switching to WebSockets is the recommended way to connect to your server and may require less battery power…”**)
Now I’m wondering, if I should switch to WebSockets or not, because I don’t know how to switch back in case I should have to. I suppose, Murena has it’s reasons to use this default setting.
Any advice?
I have tested some notification using the acivity manager app and foundation.e.ntfy to use my ntfy server. I was unable to get a notification but this is more a problem of the config on my side.
Anyway, using the activity manager > foundation.e.ntfy > MainActivity > three dot menu top right > settings > connection protocol > i switched to websockets for testing and back to JSON-over-HTTP-Stream.
I have not received any murena push notifications. I believe there were none?!
Use some more places in FOSS Warn, perhaps also such ones you don’t even know, also with a bigger perimeter, so that you catch up more warnings, just for testing.
I have the setting like you and it works. I get ordinary “treacherous icy conditions” warnings every day, for instance in some cities in Germany.
Same here.
FOSS Warn and Pachli (Mastodon) notifications are working fine with the integrated ntfy. It’s just Molly’s Signal notifications, they often come delayed or not at all, unless I open the app. So I suppose, it’s an issue of the MollySocket-Server.
Even FCM is integrated into the FOSS app in the FOSS F-Droid repo. There is a gitlab issue for it. No idea what happend but the last (I mean current) Molly version seems messed up
Thanks for the info!
I hope there will be an update soon.