Avoiding shared button states across users in Blueprint [Tip #55 Carolina from Support]

Hey y’all! Carolina from support here!
Yesterday a client reached out with an interesting question that I thought might be useful for others too!
He was using a push button in a Blueprint dashboard (temperature logger use case) and noticed that when one user pressed the button, all other users on the same Blueprint could see the button as activated even though the logging had only started for the user who pressed it.

Why does this happen?

The button widget reflects the state of a variable linked to a specific device. If multiple users are looking at the same device and the same variable, any change to that variable will be reflected across all their dashboards simultaneously.

Here we go with the tip…Create a separate device for each user and attribute the button variable to each user’s individual device. This way, the button state is isolated per user and only the person who pressed it will see it as active, and only they will receive the associated variables on their device.

This is a great pattern to keep in mind when building multi-user dashboards where individual state tracking matters!

Hope this helps! Let me know if you have any questions!

Happy weekend,