Feature request: Full AlertR control about alertr-push-android HOT 1 OPEN

This is something I have in the back of my mind for a long time. The problem is that I want to build it in a way that no one needs to change settings on the their home network like allowing a port to a webserver from the outside or something like this. If this is something you are searching for, this already is an (undocumented) part in the AlertR repository which also has a "beta" client in the Google Playstore. This app connects to a webserver via HTTPS which and logs in via basic authentication. However, this code exists for years and will not be pursued further since I see it as a dead end (but it works, I still use it).

Back to how to tackle the problem of not having to change any network setting. I have two ideas to work on this issue:

First idea (and the simple one):
Next to the central push notification system, also provide a way to store AlertR information there. Then a new "AlertR Manager Client" could publish the data AlertR gathers there and the App could gather it. In order to be privacy preserving, this would need end-to-end encryption. Meaning, the new "AlertR Manager Client" would encrypt the data with a secret configured and the AlertR App would decrypt the data on the mobile device with the same secret. This would also allow the App to provide widgets that show for example sensor states on your mobile device display directly instead of starting the App to see the information.

Second idea (complicated one):
Next to the central push notification system, also provide a proxy service here. Meaning a new "AlertR Manager Client" would always connect to the central system, your AlertR App would also connect to the central system, and then both would establish an end-to-end encrypted tunnel. Meaning the central system is some kind of proxy which only provides a means to build a connection back to your local AlertR system. Since this tunnel would be end-to-end encrypted, it is privacy preserving and even the centralized system could not see the data exchanged.

Both ideas a more involved. I looked into the second idea and how one could create an end-to-end encrypted tunnel. However, if one wants to use build-in functions to create a TLS tunnel there seems to be a bug on Android which makes this more difficult. But could be this is already fixed, since I looked it up a few years ago.

from alertr-push-android.