The scope defines which devices and which data a dashboard will work with. It can be based on device templates, specific organizations (including sub-orgs), or tags. It’s the core mechanic for targeting dashboards to different audiences—your internal teams or your customers.
A virtual pin is a logical channel used to exchange data between your hardware and Blynk. Reusing consistent V-pin assignments across products (e.g., always using V21 for battery) enables dashboard widgets to aggregate data across different device models.
A platform-level widget displays aggregate metrics like the number of online devices, average temperature, or fleet-wide signal strength. These are useful for fleet overviews and executive dashboards.
A dashboard can be set as the default homepage for any user in your organization or sub-orgs. This ensures they always land on the most relevant view immediately after login.
There’s no hard limit mentioned, but Blynk dashboards are optimized to handle large fleets (hundreds or thousands) when scoped correctly. Use sub-org filtering and aggregation wisely to ensure performance.
Dashboards only apply control commands to currently online devices. But if you use the Sync All API, offline devices will apply the latest dashboard value when they come back online.
Yes. You can build a single dashboard and automatically share it with all sub-organizations. Each customer will only see data from their own devices — no duplication or manual setup needed.
It lets you build one widget that works across all your product types. For example, if battery level is always on V21, you can show fleet-wide battery metrics without configuring each template separately.
Yes, but the data types must be consistent. For example, you can’t aggregate a string and a number on the same virtual pin. Blynk will ignore incompatible data silently — so define your datastreams carefully.
Not by default. Unless you give them specific permissions, customers can view only. Admins can edit dashboards and control access per org.
It’s near real-time, with data updating frequently. For most monitoring use cases, latency is negligible. Events and sensor values refresh on their own without manual reload.
Use widgets like Charts and set the aggregation type (average, min, max). You can define default time windows (e.g., last 7 days) and allow users to change them.
Yes. You can filter by organization, template, or specific device directly inside the dashboard—even after it’s been shared. It’s useful for drilling down without switching views or creating new dashboards.
If it matches the dashboard’s scope (template + org + tag), it’s automatically included. No manual update needed.
🌐 Geospatial support for location-based dashboards
📈 Expanded fleet analytics (e.g. activations, performance benchmarks)
Get a hands-on look at what’s possible — and start building your own dashboards today.