Want to know about device bridging is it still useable in new blynk

[engdanial]

BLYNK_CONNECTED() {
bridge1.setAuthToken(“YBzhRaqqZzZzBgx-VmzFRtnJv2LiOaCH”); // Place the AuthToken of the second hardware here
}

[PeteKnight]

No, Bridge isn’t available in Blynk IoT, but you can use Automations to send data from one device to another (although there are some restrictions/drawbacks to this approach) or you can use the HTTP(S) API to simulate Bridge, provided you are using an appropriate type of device.

There are some examples of how to do this:

For the 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…

For the 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…

Pete.