Two device, two templates in one arduino

[PeteKnight]

You can use the HTTP(S) API to send data from one device (ore more) to another, then display that data from the “master” device in the app.
It’s the equivalent of the Bridge functionality in the old version of Blynk.

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…

Or use Node-Red to do the same sort of thing…

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.