Different equipment on the same screen

[PeteKnight]

@Flavio_Lemos

Do you have any link where I can laern about it?

ESP32

Webhook widget

Okay, I’ve been doing some testing this afternoon. I’ve been using an ESP32 and the HTTPClient.h library. I’ve not tested with an ESP8266 and the ESP8266HTTPClient.h library, but I wouldn’t expect the results to be much different. I’ve managed to use the HTTPS API call with both the BlynkSimpleEsp32.h and BlynkSimpleEsp32_SSL.h libraries, however, the response times from the HTTPS API call are much longer than when using the HTTP API call. I guess this is what was causing @Blynk_Coeur’s -5 err…

ESP8266

Webhook widget

[EDIT 14th January 2022] Version 3.0.0 of the ESP8266 Core now requires that the http.begin command now includes the WiFi Client name as well as the server path. In the original sketch the start of the api_bridge function looked like this… void api_bridge(String token, int virtual_pin, float value_to_send) { HTTPClient http; String server_path = server_name + "update?token=" + token + "&pin=v" + String(virtual_pin) + "&value=" + float(value_to_send); // Your Domain name with URL path…

You could also use Node-Red…

My home automation projects built with MQTT and Node Red

Update January 2022 Okay, it’s been almost 3 years since my last post in this topic, and things have changed quite a bit – so it’s time for an update…. New Blynk IoT Obviously, the main thing that’s changed since my last update is the launch of the new Blynk IoT system (AKA Blynk 2.0). This required some changes to the Node-Red contrib for Blynk, so a new contrib called node-red-contrib-blynk-iot has been launched. The current version of this contrib is 0.2.0 and the following warning… [image…

Pete.