Page 1 of 1

Espeasy message with Pushover

Posted: 23 Jun 2021, 11:04
by NetEye
Hi there,
I used the following working rule line with pusbullet:

SendToHTTP,maker.ifttt.com,80,/trigger/textxxxxxxx/with/key/xxxxxxxxxxx

Pushbullet is no longer supported on iOS so I choosed for Pushover now.
After some time with my friend google I made a still not working rule line:

SendToHTTP api.pushover.net,443,/1/messages.json?token=XXXXXX?user=XXXX?device=iphone?title=test?message=Test

Can anyone help me to make it work?
(Perhaps a , instead of a space before api.pushover.net ??)

Thanks for your time

Re: Espeasy message with Pushover

Posted: 23 Jun 2021, 11:15
by TD-er
Have you checked "SendToHTTP wait for ack" on Tools -> Advanced?

Re: Espeasy message with Pushover

Posted: 23 Jun 2021, 11:29
by Ath
I don't think that API will accept a connection on port 443 without ESPEasy providing a proper ssl connection setup... (ESPEasy doesn't support ssl atm.)

Re: Espeasy message with Pushover

Posted: 23 Jun 2021, 12:07
by NetEye
SendtoHTTP works fine.
I have used the first rule with Pushbullet for several years.
Instead of Pushbullet I have to use Pushhover (or another platform which you like better).

Re: Espeasy message with Pushover

Posted: 23 Jun 2021, 12:09
by TD-er
But you try to send to port 443, which is normally the SSL port for HTTP.
SSL is not supported by ESPEasy.

Re: Espeasy message with Pushover

Posted: 23 Jun 2021, 12:13
by NetEye
Ok marked, thanks,
Do you think 80 is the solution?

Re: Espeasy message with Pushover

Posted: 23 Jun 2021, 12:15
by TD-er
If supported by that service, then yep that would for sure make a difference.

Also look at the checkbox I mentioned.

Re: Espeasy message with Pushover

Posted: 23 Jun 2021, 12:21
by NetEye
I will try it tomorrow.
Is there also a maximum length for the user key and the API token to use in the rule ofvthe Espeasy?
I remember I had to change something for using longer lenght.
Pushover uses much longer length as Pushbullet

Re: Espeasy message with Pushover

Posted: 23 Jun 2021, 12:32
by TD-er
What length do you need in the URL?

Re: Espeasy message with Pushover

Posted: 23 Jun 2021, 12:50
by Ath
Length of credentials won't be an issue when used in an url. In controller settings there is an option to use an extended size settings, but that doesn't apply here.
AFAICS, Pushover won't accept connections on port 80 (or might redirect those to 443/https), so that won't work either.
You can use a home automation system to send the notification there, but you might need to script that in some way, depending on the home automation system used (most are linux or windows hosted, so will/can support ssl connections, while still accepting http connections from an ESPEasy unit on the local network).

Re: Espeasy message with Pushover

Posted: 23 Jun 2021, 14:30
by NetEye
Both, the user key and API token are 30 characters.
Both are used in the rule of Espeasy for Pushover.
Pushbullet does only need a API token.
If what Ath said about not working with 80 its all useless.
What platform can I use instead of Pushbullet.
Yes Ath I can use forinstance Domoticz to send messages but I would like to use Espeasy.
Thanks for all your time

Re: Espeasy message with Pushover

Posted: 23 Jun 2021, 18:38
by NetEye
the user key and API token are 30 characters.