For the past week or so I’ve been bumbling my way though migrating projects to the new blynk platform. Things have actually gone pretty smoothly moving single device projects over to 2.0. However, I’ve been hung up on how to display datastreams from several devices on a single screen. In the old blynk I was able to select the source for a widget and pick from a list of devices. Is it correct that this functionality does not exist anymore? Are there any workarounds in 2.0 (bridge etc…)?
In my case I have a heating system project with 4 physically remote devices, each with a number of temperature sensors. It was really helpful to see all of the datastreams in one place to trouble shoot the system.
It’s very possible I’m missing something obvious to others. If that’s the case I’d love to be pointed in the right direction.
@Blynk_Coeur was saying recently that if you add multiple devices with the same template then you can add controls to the same screen on the app.
I’ve not tried it, but I guess that you’d add datastreams to the app that are grouped together and which represent data from the different devices.
Not sure if this is an “officially approved” approach though!
Thanks @Blynk_Coeur and @PeteKnight for the quick responses! The Blynk API is new ground to me, so I’ll have to do some learning. But basically one template, one Auth token, different devices, different virtual pins, and tie it together with blynk API?
@Blynk_Coeur , your idea on using timestamps to detect offline devices was most helpful to me. Thanks.
Situation: I have multiple SONOFF switches operating as a single Blynk Device (so that I can see them all at once). And I have an ESP32 as a separate Blynk Device that Schedules the SONOFFs. I wanted the ESP32 Scheduler to know when any of the SONOFFs went offline.
I did have to create my own Blynk 1.0 Time Input widget replacement using available Blynk IoT widgets, would love to see that helpful Time Input widget return in Blynk IoT.
Solution: each SONOFF does a timer-driven HTTP update to a single Datastream on the ESP32 Scheduler, updating the ESP32 Scheduler Datastream with an ID unique to each SONOFF. Using the unique ID, the Scheduler tracks the time BLYNK_WRITE gets triggered by each SONOFF’s HTTP update. Then a Timer-driven routine on the ESP32 Scheduler checks to see which SONOFFs have checked in recently.
