Replies: 4 comments 4 replies
-
Why not using the AsyncWebSocketClient from AsyncWebsocketServer? |
Beta Was this translation helpful? Give feedback.
-
Some Ideas and information (in german): I mean, we need 3 URLs and not only one. |
Beta Was this translation helpful? Give feedback.
-
I decided to go with the arduino-esp32/HTTPClient. It seems to be a common way to do HTTP requests, It supports http and https, but there is no support for async mode. I actually tried the esp_http_client first and would have preferred it because it seems quite major, but there were too many problems with it: async mode is supported for HTTPS only, there were conflicts with the HTTP_ enum with AsyncWebServer that could only be fixed by doing a lot of changes in the AsyncWebServer library and there were crashes during reading the HTTP response. The HTTP_ enum conflict is not only esp_http_client's fault. Since there will be no async requests, I'l implement a default timeout of 1 second, that can be customized. I think this should do it and safe the ESP32 from reboots when the Powermeter is not reachable. For Json parsing by path, I'll try out https://github.com/mobizt/FirebaseJson . |
Beta Was this translation helpful? Give feedback.
-
PR is open now #153 |
Beta Was this translation helpful? Give feedback.
-
Some people said that they would like to have support for HTTP + Json Powermeter reading, because they can't use MQTT.
Examples:
I just started implementing this, but I need 2 things for this:
Wanted: HTTP request client library
Possible candiates:
Does anyone know something good?
Wanted: An ESP32 Json library with JsonPath support
Any other inputs/ideas are also welcome!
Current Webview design:
Beta Was this translation helpful? Give feedback.
All reactions