@marcelode1 Sure, here's how I set up the Blynk dashboard...
Desired Temperature gauge: Pin V1, range 50 - 80 (I'm in the US, so using Farenheit), Push update frequency
Actual Temperature gauge: Pin V0, range 50 - 80, 2 second update frequency
Set Temperature slider: Pin V3, range 50 - 80, send-on-release set to OFF
Unnamed labeled value display: Pin V10, default range of 0-1023, default label of /pin/ , update frequency 500ms
Settings button: Pin V4, PUSH mode, blank on and off labels
Modify button: Pin V5, PUSH mode, blank on and off labels
On LED: pin V7
Home LED pin v29
For aesthetic reasons, many of the widget labels have been either blanked out, by entering blank spaces in the label name field, or center justified, by adding leading blank spaces before typing the name.
Linking the temperature slider to the desired temperature gauge is not done in the app. It's done in the code. It's this section:
//Match temp gauge to slider in Blynk app
TempDes = param.asInt();
The BLYNK_WRITE function receives the new desired temperature value from the slider (on pin V3). We transfer that value to the variable TempDes, so that we can continue to use it in our code. Then, we immediately send that value back to the Desired Temperature gauge (on pin V1), with the Blynk.virtualWrite command.