Hi.
I wasn’t aware of that issue.
Thanks for your suggestion.
Regards,
Sara

I used your example and first it worked really well.
After integrating the code in my software I got some trouble with crashes of the system.
By analysing the problem I found that some memory, that is used by the secure communication routines will not be released… In my case, this led to crashes because of heap/stack collision.

Some web investigation led me to a solution: If one adds a “client.stop();” statement after the “https.end;”, most of the allocated memory will be released. Some additional bytes will be available after a minute or so, looks like a timeout.

So this might be an improvement for your example!

Best regards and thanks for your wonderful website!
Manfred

Hi.
You can use MQTT for example, to send data to your ESP32, or HTTP requests.
Regardsm
Sara

I have an ESP32 with a display I sit in my counter, and I’d like it to RECEIVE notifications from my desktop home automation system, or maybe my phone.

ESP as a RECEIVER, not a transmitter.

Thanks, Mark.

I’ve tried this sketch which works well “alone”.
I have integrated the code in another one already in place with http requests but it doesn’t work.
After many different approaches, it looks like it is not possible to manage both HTTP and HTTPS in the same sketch with the ESP8266.
Regards,
Romain

Hi.
This certificate is valid until 2038. But, Pushover might change their certificate whenever they want.
There might be a way to know when the certificate has changed, but I don’t know how to do that at the moment.
Regards,
Sara

The cert change was a problem for me, too. How often does it happen? Is there a way to get a notification that is going to happen? PS: you still have the old cert in the explanation section.

Hi.
Yes, you’re right.
Thanks for letting us know.
Yes, the problem is with the certificate.
We updated the code with the new certificate.
The code should work now.

Regards,
Sara

Hi.
I think you can use the same API key for all devices.
Regards,
Sara