Pushover https post request

[DavidAntonin]

Hi, I have read all the information regarding https so I know that it is not currently possible to implement it on esp8266. Unfortunately the Pushover service only accepts POST to https://api.pushover.net/1/messages.json. One library for ESP8266 solves this on the client with setInsecure(). Would it not be possible to implement this as well?
Thank you

[khoih-prog]

Thanks for your interest in the library.

As you know, this library is designed for HTTP request only, and HTTPS is not implemented now.

However, I'm currently working on and already successful in making a twin library (AsyncHTTPSRequest_Generic) to deal with HTTPS only, but just working OK so far with ESP32. It'll take some time to fully test and publish it. Making it supporting to ESP8266, STM32 and many other boards, if easily possible and time-permitted, is in my plan.

You certainly can use normal secure sync WebClient for those services using only HTTPS, and setInsecure() can be easily used, but it's just a kludge and not advisable (unless it's absolutely necessary without any better choice) as real certificate checking is bypassed.

Anyway. I'm closing the issue now because HTTPS won't be supported by this library.

[DavidAntonin]

Thank you for a fast reply.  I am happy to see you are working on https version. Please let me know when it is ready for esp8266. I have my own board with esp8266 so it is not possigle to switch it for esp32 Thank you for your hard work and support. regards David ---------- Původní e-mail ---------- Od: Khoi Hoang ***@***.***> Komu: khoih-prog/AsyncHTTPRequest_Generic ***@***.*** github.com> Datum: 21. 10. 2021 0:20:43 Předmět: Re: [khoih-prog/AsyncHTTPRequest_Generic] Pushover https post request (Issue #21) " Thanks for your interest in the library. As you know, this library is designed for HTTP request only, and HTTPS is not implemented now. However, I'm currently working on and already successful in making a twin library (AsyncHTTPSRequest_Generic) to deal with HTTPS only, but just working OK so far with ESP32. It'll take some time to fully test and publish it. Making it supporting to ESP8266, STM32 and many other boards, if easily possible and time-permitted, is in my plan. You certainly can use normal secure sync WebClient for those services using only HTTPS, and setInsecure() can be easily used, but it's just a kludge and not advisable (unless it's absolutely necessary without any better choice) as real certificate checking is bypassed. Anyway. I'm closing the issue now because HTTPS won't be supported by this library. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub (#21 (comment)) , or unsubscribe (https://github.com/notifications/unsubscribe-auth/ALM5VK4JO74UAPJUUGHDTB3UH46DJANCNFSM5GK7BJYA) . Triage notifications on the go with GitHub Mobile for iOS (https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675) or Android (https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub) . "

[khoih-prog]

FYI

The first library in the AsyncSSL series has been published

1. AsyncTCP_SSL to support only ESP32

The next one

2. AsyncHTTPSRequest_Generic will be released tomorow, just supporting only ESP32.

[khoih-prog]

AsyncHTTPSRequest_Generic has just been released, just supporting only ESP32.

You'd better try and switch to ESP32 if can't wait for ESP8266 support (currently without time-frame yet)

[DavidAntonin]

Thank you for your work on the libraries. Is it possible to use both AsyncHTTPRequest_Generic and AsyncHTTPSRequest_Generic on ESP32? Alternatively, how to resolve this situation: I created a home security system on ESP32 + CC1101 that receives signals from 433MHz sensors. When a signal arrives, it saves the record via HTTP GET + PHP to a SQL database, on the home NAS. When the alarm is activated, and the signal is e.g. "door open" a message is sent to the mobile phone via HTTPS POST + Pushover. The problem is that when sending to SQL, other activities are blocked - it takes about 1s - 1,5s. This is not fast enough to detect a signal that arrives during this time - e.g. a door being opened and quickly closed. The following actions should take place: 1 - opening the door 2 - save the "door open" record to SQL 3 - sending a Pushover message "door open" 4 - closing the door 5 - saving the "door closed" record to SQL The problem is that 4 and 5 come before 2 and 3 are completed Thank you for your help

…

---------- Původní e-mail ---------- Od: Khoi Hoang ***@***.***> Komu: khoih-prog/AsyncHTTPRequest_Generic ***@***.*** github.com> Datum: 22. 10. 2021 6:21:32 Předmět: Re: [khoih-prog/AsyncHTTPRequest_Generic] Pushover https post request (Issue #21) " FYI The first library in the AsyncSSL series has been published 1. AsyncTCP_SSL(https://github.com/khoih-prog/AsyncTCP_SSL) to support only ESP32 The next one 1. AsyncHTTPSRequest_Generic (https://github.com/khoih-prog/AsyncHTTPSRequest_Generic) will be released tomorow, just supporting only ESP32. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub (#21 (comment)) , or unsubscribe (https://github.com/notifications/unsubscribe-auth/ALM5VK6MDVQOEMZ27DB4AZTUIDRD7ANCNFSM5GK7BJYA) . Triage notifications on the go with GitHub Mobile for iOS (https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675) or Android (https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub) . "

[khoih-prog]

Sorry I don't have time to help you solve your special use-case issue.

Just some quick idea that you wrongly design your mission-critical system, by failing to use powerful ESP32 multitasking RTOS and/or Timer Interrupt.

If you don't know how to start, check

1. Async_ESP32_MultiTask example, which is written to use prioritized multi-tasks for blocking Blynk
2. ESP32_New_TimerInterrupt library

Libraries are written for many boards / platforms, for general use-case to demonstrate how to use basic libraries' features. So don't expect to use directly to any use-case without having good design, depending on the board / platform.

If you still have more issues, please post and ask for help on Arduino / ESP32 Forum.

[DavidAntonin]

Thank you for a fast reply. So only few qustions to libraries:

• It is possible to use AsyncHTTPRequest_Generic and AsyncHTTPSRequest_Generic together on ESP32?
• It is possible to send second http request while the first still did not get response? If I understand it correctly, this is not possible, because the new request can not be sent until readyState == 4 (complete with response received)
  Thank you

[khoih-prog]

It is possible to use AsyncHTTPRequest_Generic and AsyncHTTPSRequest_Generic together on ESP32?

I haven't tested but guessed that there will be some conflicts. Why not using the better HTTPS only?

Possibly in the future, I'll add feature into AsyncHTTPSRequest_Generic to permit you to do both HTTP and HTTPS.

It is possible to send second http request while the first still did not get response?

I don't see why not as this is Async, not Sync. You don't need to wait for any response, but just receive and process the responses when they comes.

Certainly it depends on how you write your code, which can destroy the Async features of the library.

[DavidAntonin]

I tried a simple modification of your basic example for ESP. I added monitoring of readyState to see how long sending a receiving took. Request can be sent when readyState is readyStateUnsent (0) or readyStateDone (4). In my testing i get only values 0,1,4 - 4 is on receiving the response. So I investigate I can only send another request when I receive a response.

#if !( defined(ESP8266) ||  defined(ESP32) )
#error This code is intended to run on the ESP8266 or ESP32 platform! Please check your Tools->Board setting.
#endif

// Level from 0-4
#define ASYNC_HTTP_DEBUG_PORT     Serial
#define _ASYNC_HTTP_LOGLEVEL_     1

// 300s = 5 minutes to not flooding
#define HTTP_REQUEST_INTERVAL     60  //300

// 10s
#define HEARTBEAT_INTERVAL        10

int status;     // the Wifi radio's status

const char* ssid        = "***";
const char* password    = "***";
int lastReadySt = 99;

#if (ESP8266)
#include <ESP8266WiFi.h>
#elif (ESP32)
#include <WiFi.h>
#endif

#define ASYNC_HTTP_REQUEST_GENERIC_VERSION_MIN_TARGET      "AsyncHTTPRequest_Generic v1.5.0"
#define ASYNC_HTTP_REQUEST_GENERIC_VERSION_MIN             1005000

#include <AsyncHTTPRequest_Generic.h>             // https://github.com/khoih-prog/AsyncHTTPRequest_Generic

// To be included only in main(), .ino with setup() to avoid `Multiple Definitions` Linker Error
#include <AsyncHTTPRequest_Impl_Generic.h>        // https://github.com/khoih-prog/AsyncHTTPRequest_Generic

#include <Ticker.h>

AsyncHTTPRequest request;
Ticker ticker;
Ticker ticker1;

void heartBeatPrint(void)
{
  static int num = 1;

  if (WiFi.status() == WL_CONNECTED)
    Serial.print(F("H"));        // H means connected to WiFi
  else
    Serial.print(F("F"));        // F means not connected to WiFi

  if (num == 80)
  {
    Serial.println();
    num = 1;
  }
  else if (num++ % 10 == 0)
  {
    Serial.print(F(" "));
  }
}

void sendRequest()
{
  static bool requestOpenResult;

  if (request.readyState() == readyStateUnsent || request.readyState() == readyStateDone)
  {
    //requestOpenResult = request.open("GET", "http://worldtimeapi.org/api/timezone/Europe/London.txt");
    requestOpenResult = request.open("GET", "http://copnb.cz/test/time.php");

    if (requestOpenResult)
    {
      // Only send() if open() returns true, or crash
      request.send();
      Serial.printf("%i - request sent\n", millis());
    }
    else
    {
      Serial.println("Can't send bad request");
    }
  }
  else
  {
    Serial.println("Can't send request");
  }
}

void requestCB(void* optParm, AsyncHTTPRequest* request, int readyState)
{
  (void) optParm;

  if (readyState == readyStateDone)
  {
    Serial.printf("%i - response received\n", millis());
    Serial.println("\n**************************************");
    Serial.println(request->responseText());
    Serial.println("**************************************");

    request->setDebug(false);
  }
}

void setup()
{
  // put your setup code here, to run once:
  Serial.begin(115200);
  while (!Serial);

  Serial.println("\nStarting AsyncHTTPRequest_ESP using " + String(ARDUINO_BOARD));
  Serial.println(ASYNC_HTTP_REQUEST_GENERIC_VERSION);

  WiFi.mode(WIFI_STA);

  WiFi.begin(ssid, password);

  Serial.println("Connecting to WiFi SSID: " + String(ssid));

  while (WiFi.status() != WL_CONNECTED)
  {
    delay(500);
    Serial.print(".");
  }

  Serial.print(F("AsyncHTTPRequest @ IP : "));
  Serial.println(WiFi.localIP());

  request.setDebug(false);

  request.onReadyStateChange(requestCB);
  ticker.attach(HTTP_REQUEST_INTERVAL, sendRequest);

  ticker1.attach(HEARTBEAT_INTERVAL, heartBeatPrint);

  // Send first request now
  sendRequest();
}

void loop()
{
  if  (lastReadySt != request.readyState())
  {
    Serial.printf("%i - readyState = %i \n", millis(), request.readyState());
    lastReadySt = request.readyState();
  }

}

[khoih-prog]

Hi @DavidAntonin

Sorry for forgetting the issue for some time

As you can see in the example

void sendRequest()
{
  static bool requestOpenResult;

  if (request.readyState() == readyStateUnsent || request.readyState() == readyStateDone)
  {
     ...
  }
  else
  {
    Serial.println("Can't send request");
  }
}

The request can only be sent if (request.readyState() == readyStateUnsent or request.readyState() == readyStateDone. So the result you got is quite expected.

The example is just example, to show how you can basically use some library's functions. You have to adapt for using in your complex use-case.

Try to drop

 if (request.readyState() == readyStateUnsent || request.readyState() == readyStateDone)

and see if it's OK