2.1.1 is out today with three dashboard items:
- A sample data source, so every widget has something real-looking to show before devices are connected.
- Board settings.
- Board packages that carry every card of a board.
Where to read up: the sample source is on Data sources and parameters, the board settings on Create and organise boards, and exporting and importing a board on Board templates and board files.
The automation and notification items in 2.1.1 have their own post.
The sample source is perfect timing for me. My sensors for my final year project arrive in two weeks and I have to demo the board before that. Anything to watch out for if I leave sample cards on it?
Only that it is meant for testing. The sample sources show up when you turn on Also list the sample data and the developer sources in a card’s Data tab, and the docs say to leave that off for production boards. When your sensors arrive, open each card’s Data tab and bind it to the device instead. Good luck with the demo.
We build boards in a test organisation and then hand them over to the customer’s organisation. Is the board package the way to move them now?
Yes. In the board menu, Export gives you a .board.json for that board, or Export with linked a .boards.json that also carries the boards it opens, so the links keep working. In the other organisation, Import in the dashboards list, read the dry run (nothing is written yet), then Import.
What the file leaves out: the organisation, people, sharing, revision history and the definition of your own widgets. Those widgets move with the widget library’s own export.
Did exactly this for a client last week. The dry run listed two cards as Skipped, both process diagram cards, because the client org didn’t have the SCADA module on yet. Turned it on, deleted the first import, imported again and all 14 cards came across. Read the dry run, it tells you exactly which card and why.
Thanks for writing it up. The Commands line under What this package points at in the same dry run is worth a look too: it marks each command as Can be used, Not found here, Not permitted for you or Takes different params here.
- You must be logged in to reply to this topic.
Join the conversation
Sign in to ask and answer, like helpful posts and mark the reply that solved your problem. Every contribution earns points and levels.