We need to add documentation for getting the server up and running and connecting devices.

@anaclair or @juliagra you may want to contribute what you can to getting up and running (covering meteor installation, cloning the git repo, etc.

Documentation is a never ending effort, so we'll limit the scope of this issue to getting started documentation

Should be available as an option from the detail view for now.

Claiming and registering IoT devices is a difficult problem, so the first version is to allow us to begin to address user interface and other issues: devices register themselves with common garden and users claim a device by typing in the UUID.

Need to add things like basic validations, etc. Also, #13.

Devices need metadata. Perhaps we should transfer this metadata when the device registers? I.e. it registers with some basic information about itself.

It's mentioned at the bottom of the readme but it should be its own file in the repo.

In the device list and detail view, introduce some UI to indicated that the device is online.

Flash message are good for UX, they are shown to give updates and confirmation to the user.

Currently, it doesn't.

http://matteodem.github.io/meteor-easy-search/

https://atmospherejs.com/raix/push

TODO: make it so users can add their user IDs to the device config to claim a device under their username when it registers with a CommonGarden-IoT instance.

https://themeteorchef.com/recipes/writing-an-api/

We should be able to get the current state of an actuator for instance.

As a user I would like to be able to rename a device.

A page for the user to manager there account such as notifications and changing email / password.

This is sort of important, as otherwise it would just be an IoT interface. This works, but it needs to be documented and examples need to be linked to.

https://themeteorchef.com/blog/securing-meteor-applications/

When looking at the device detail view there should be name, current value and a list of datapoints if a sensor, buttons for actions if an actuator.

Along with login and registration, the reset password flow is another basic part of the app we need.

The internet of things is more than just connected devices. It can also be things like plants for example! As such, images are a useful dataset.

https://themeteorchef.com/snippets/adding-drag-and-drop-sorting-to-lists/

This is very basic account functionality. It should go on the user account page.

Currently we are using the default meteor accounts-ui package. While this was great for getting started, the mobile styles need work. In short, let's build a nicer login/registration system that we can expand if needed.

Relevant blog posts:
http://blog.benmcmahen.com/post/41741539120/building-a-customized-accounts-ui-for-meteor
http://www.sitepoint.com/creating-custom-login-registration-form-with-meteor/

The login and forgot password screens could use some extra styling so that things are spaced nicely.

The logo is out of place for some reason when not logged in.

Also, the validation messages are a little to weird... we should replace them with something more normal.

Should be able to change password or email here.

If there are no devices listed there should be an empty state with a call to get started by adding devices.

https://themeteorchef.com/snippets/loading-patterns/

I'm really digging what the meteor chef is cooking. 🍰

This will generate a new grow file template. For example:

{
    "thing": {
        "type": "grow-file",
        "name": "Saffron Plant",
        "latin-name": "Crocus sativus",
        "description": "The Saffron plant likes well drained soils and full sun.",
        "model": {
            "events": {
                "crons-updated": null,
                "harvest": {
                    "description": "To harvest the Saffron spice, remove the 3 stamens.",
                    "imageURL": "https://example.com/example.jpg"
                },
            },
            "properties": {
                "min-temp": {
                    "value": 40,
                    "unit": "f"
                },
                "max-temp": {
                    "value": 110,
                    "unit": "f"
                },
                "time-to-grow": {
                    "value": 50,
                    "unit": "f"
                },
                "ideal-light": "Full Sun",
                "crons": {
                    "lightsOn": "00 09 * * *",
                    "lightsOff": "00 19 * * *",
                    "waterPlants": {
                        "cron": "00 11,17 * * *",
                        "duration": 20000
                    }
                }
            },
            "actions": [
                {
                    "name": "update-grow-file",
                    "valid": {
                        "crons": {
                            "lightsOn": "Cron",
                            "lightsOff": "Cron",
                            "waterPlants": {
                                "cron": "Cron",
                                "duration": "Integer"
                            }
                        }
                    }
                }
            ]
        }
    }
}

The sidebar show contain a basic menu.

This has already been started, but there is work left to do and it needs to be tested.

Show a live updating chart. Eventually it would be really cool if we could see data over months or the last 30 minutes... visualizing information coming from devices is a never ending issue, so for the scope of this ticket, a simple live updating chart will do nicely.

This info shouldn't be shown by default to keep the interface clean for non-technical users. However, this info can be helpful when debugging.

Currently on mobile sized screens the layout is super funky.

So, I do want to build a grow app but at this stage we're basically building more general IoT oriented technology that will handle:

• Registering and claiming device
• Receiving and sending messages to devices.
• Adding basic permissions for devices (i.e. is this an open device that anyone can read, or owned and controlled only by a specific user, etc.)
• Providing a basic UI

As such, I think it makes sense to rename the repository Meteor-IoT or something with a more general IoT focus.

Stylus, while a cool project, is a lot less popular than SASS, and do to multiple people being confused where the style-sheets were... we should swap Stylus out for SASS. IMHO, not much is gained by using Stylus over SASS, except confusing people.

A device sends an event message to the server and the user is notified.

http://www.dhtmlx.com/blog/use-dhtmlxscheduler-meteorjs-based-apps/

https://github.com/aldeed/meteor-scheduled-tasks/

http://richsilv.github.io/meteor/scheduling-events-in-the-future-with-meteor/

For example, a plant or a room.

https://themeteorchef.com/recipes/exporting-data-from-your-meteor-application/

There are still some material design classes hanging around in the templates. We're using bootstrap.

Devices should display there state both in list and detail view.

If a user is not logged in the should be redirected to the login/signup page.