search

caronc / apprise

Apprise - Push Notifications that work with just about every platform!
https://hub.docker.com/r/caronc/apprise
BSD 2-Clause "Simplified" License
10.91k stars 384 forks source link

Support for LunaSea #1070

Closed posixx closed 3 months ago

posixx commented 4 months ago

:loudspeaker: What is the name of the service?

LunaSea support for receiving notifications

:link: Provide some details about the service that can help with it's development.

https://docs.lunasea.app/lunasea/notifications/custom-notifications

:bulb: Anything else?

littlegraycells commented 4 months ago

Came here looking for LunaSea as well.

Piggybacking on this, it would be great to see a more generic webhook notification support.

caronc commented 4 months ago

LunaSea support started, but a bit confused on

  1. how the (FireBase) DeviceID and UserIDs are acquired for use/reference.
  2. I'm also not quite sure if I understand why the ID's need to be in both the Payload and URL (is this intended) as documented here? image
  3. what are the message body and title length restrictions?
  4. Are there any throttle limits at all?
  5. Is it safe to assume both the Cloud based solution (on https://lunasea.app) and a locally hosted one use just basic auth to authenticate with. I can see that a local solution doesn't have a login, so notifications through it can also be sent directly?
posixx commented 4 months ago
  1. The deviceid and/or userid are acquired using the LunaSea application on your device, under settings —> notifications. In order to copy a userid url you need to have a LunaSea cloud login.
  2. I don’t think the deviceid needs to be in the body, only the base url will do
  3. I don’t know..
  4. Again, no idea
  5. Both don’t need authentication as far as I can tell; if you have the required base url you can send notifications
caronc commented 3 months ago

I'm done, if you could please click the link and follow the examples, you could verify if it works okay for me.

caronc commented 3 months ago

I was able to test this out; closing out ticket as complete :rocket: