pale orchid
Hello folks! I am willing to fund the development of support for NTFY or another UnifiedPush mechanism for the minimal Android Companion app (or both versions of the app, I really don't mind either way about this specific point).
The spec in a single line: have the app do the same things it can do today when it gets a push notification (via persistent notification socket or via FCM) but accept the message via NTFY (exactly like Element / ElementX do it).
How it should be implemented (extend the notify_app integration or use the notify_ntfy integration) is up to the implementer. Ultimately the point of this feature request is that notifications are routed via a UnifiedPush server (to which the companion app asks the NTFY app to subscribe on its behalf), the message is then delivered to NTFY's open socket, and finally NTFY relays the message to the companion app.
A discussion on this issue can be found here: https://github.com/home-assistant/android/issues/3206 it was closed as "not planned"
I would like to know who would like to do this work and how much they are willing to charge to get this done. I honestly can't have the minimal Android app consuming one third of my battery when the phone isn't doing anything.
Stretch goal: I have noticed that when I open the app, a websocket connection is open that sends entity updates to my phone constantly, and this continues for about five minutes after I've locked my phone, obviously draining battery massively as it keeps the phone (specifically its networking) awake. If this could be fixed (lock phone -> stop this stream of data), I would pay extra.
Evidently all the work I'm asking to pay for would be open sourced for everyone to use.
Serious takers only. Thank you!
