What is used to replace the Blynk bridge

[PeteKnight]

@Grant

Node-RED

Blynk 2.0 - Adding multiple devices to one template

Okay, here’s a sketch hacked together from segments of my regular (much larger) MQTT sketch. What it does… The sketch allows the onboard LED of a NodeMCU (pin GPIO2, active LOW) to be turned on/off by an MQTT message on the Test_Device/LED_Command topic. The NodeMCU sends-back a confirmation of the LED status on the Test_Device/LED_Status topic. In addition, the NodeMCU publishes it’s RSSI signal strength, Free RAM and Uptime on the Test_Device/RSSI, Test_Device/Free_RAM and Test_Device/Upt…

@Grant

blynk API

ESP32 example…

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…

NodeMCU example…

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…

Pete.