Unifiedpush with NextPush

[timechips]

Is there an existing request for this?

• I have searched the existing issues

Feature description

The unifiedpush worked with NextPush on the seperate app, but since the apps merged I cannot seem to figure out how to set it up. The only option molly gives me is to scan the QR code for molly socket.

[phoropter]

UnifiedPush requires mollysocket. That was always the case. What most likely happened before is that your app reverted to websocket for notifications.

If you cannot/ don't want to host your own mollysocket, then there are services that host it publicly, like https://molly.adminforge.de/

[timechips]

UnifiedPush requires mollysocket. That was always the case. What most likely happened before is that your app reverted to websocket for notifications.

If you cannot/ don't want to host your own mollysocket, then there are services that host it publicly, like https://molly.adminforge.de/

Reinstalled the depricated molly unifiedpush app just to check. I logged in and connected to NextPush. I'm pretty sure it is using unified push from my Nextcloud server. Correct me if I'm wrong.

[phoropter]

You can see in the 1st & 2nd screenshots that it's giving you warnings about no mollysocket server. I'm pretty sure the app will swap to websocket after enough time without a mollysocket connection and you won't get timely notifications until it does so.

[timechips]

I had this config for over half a year. Worked flawlessly, only time it did not was when my server was down, at that time NextPush notified me so (I did not get notifications when the server was down). All the notifications were on time (almost always under 5sec, and never over 30). No exessive battery usage. Never seen "WebSocket Service" notification. All the people using NextPush also had molly-socket configured, I did not. Was this just websocket? And if it was, why did I not get notifications when my server was down?

[p1gp1g]

The previous UX could be confusing and let some user think they were using UP while Molly was using the websocket (which we improved a bit). For instance, on your screenshot you can see the warning next to "UnifiedPush" and "MollySocket server not found" for the status.

We made the QR code mandatory for many reasons, one of them is to ensure the user has a mollysocket server running. Sorry for the confusion