Creating and using custom dashboard of thing and property

[arist0v]

As a user i would like to be able to create custom dashboard of thing and also select wich thing property is part of the dashboard. i would also want to be able to choose wich thind and property is highlited so i could have an easy way to ajust the room temperature in exemple

[benfrancis]

I like the idea of custom dashboards, and I think this is something we should eventually add to the gateway's own web interface too.

I think this issue needs breaking down into more detailed user stories to explain what you can do with dashboards. So far I have filed:

• 43

• 46

• 44

• 45

What should you be able to add to dashboards? I've listed some ideas below.

• Add/remove thing - Create a custom list of things to view their status
• Add/remove property - Shows the current value of a property of a thing
• Add/remove action - Provides a button to trigger an action of a thing
• Add/remove event log - Provides a log of instances of an event of a thing
• Add/remove property log - Provides a graph showing the change in a property over time
• Add/remove rule switch - Provides a way to quickly toggle a rule on and off

I'm also wondering if we should start with just a single dashboard with a "Dashboard" entry in the main menu and see how people use it, before adding the capability for multiple dashboards which could get quite complicated.

[arist0v]

i think we should start with a basic dashboard that will include all the things in a first way, then add custom dashboard later since it is for me one of the main reason i would like to build an app. Managing multiple dashboard won'T be so complicated if we keep in mind that all dashboard is an object, that have multiple thing related to him, so we create a dashboard and jsut link thing to the dashboard.

my idea of what we add to a Dashboard is the following:

• you choose the thing you want on that dashboard(no matter from wich source it is)
• you choose wich property of a thing you want to be used in that dashboard
• you choose wich property you want to have a hilighted for the thing (so i want that the main property is the heating setpoint so i could set the heatpoint from the dashboard screen

My view is really to control a room or a "system" from a single, simple dashboard

[benfrancis]

i think we should start with a basic dashboard that will include all the things in a first way, then add custom dashboard later since it is for me one of the main reason i would like to build an app

That sounds good to me. I'd suggest that an initial dashboard which includes everything is simply called "Things" like the web app, then we create a separate "Dashboard" which is customisable.

• you choose the thing you want on that dashboard(no matter from wich source it is)

• you choose wich property of a thing you want to be used in that dashboard

• you choose wich property you want to have a hilighted for the thing (so i want that the main property is the heating setpoint so i could set the heatpoint from the dashboard screen

Sounds good.

My view is really to control a room or a "system" from a single, simple dashboard

We need to think carefully about how this overlaps with the new "groups" feature in 1.1, and the floorplan feature, and make sure we don't make things too complex. Starting with a single customisable dashboard might help with that.

[arist0v]

That sounds good to me. I'd suggest that an initial dashboard which includes everything is simply called "Things" like the web app,

starting with a Things page is a good idea. But we just should keep in mind when creating the base that at some point we will have multiple source so we need to be sure to include all of them in a Things Screen. Could you provide me a Mockup for this screen, maybe splitting it by source and/or other section for a more readable way since it could got a lot of thing in the page.

then we create a separate "Dashboard" which is customisable.

I Suggest that at this point we create a Dashboards page that allow to create custom Dasbhoard in it, so the Dashboards page will be a list all the user created Dashboard.

Before going that way, we will still need to define the way to go on discussion #27