thomas-dot-g / connected_house Goto Github PK

add the get return that return the hex file if there is one.
The Hex file is chosen (or not) with getting the id of the bridge and checking if all arduinos are good to be updated or not.

Add another get for the bridge update

Commenting and cleaning up the libraries (of the bridge and the probes) to update the probes and the bridge.

The Example should be updated for the motion we are using.

Edit the Version model so the variable type is not a String anymore but a Type model.

• Modify the code of the web server so that it can send code
• Make sure that the code that is send is well receive

• Do a test that will last at least 3 months
• Do regulary checks
• Use at least 3 arduino (2 probes + one bridge)

• write code that will send an update from the bridge to the probes
• make sure that the update is well received and done

Change name = primary key to name&&user= primary key

In mychannels, if the description is too long, there is a graphical bug.

do a model update and add stringfield description to channel so the user can describe his/her channels

The values given to the javascript to make the electrical graph is certainly wrong, it should be checked to give the right ones
(5 values are given including a timestamp, a value, and some max/min, but not sure in what order nor the exactitude of this)

Add the functional and commented code for the communication between modules

change prob name for ID so it's less confusing for @augustindv

Creating the read me to explain the goal of the project

Add the panels the user sees when connected, regrouping all of its data

being able to create channels and associate them to users.

Using cookie or local storage (see for the forecast js for local storage)

Index in vew should use check_auth

When the forms are not just {{ forms }} but declied as {{ forms.name }}, {{ forms.email }}...
we need to put the error forms. something at the beginning.

Change the remaining javascript files (dashboard for example) from angular to classique/jquery javascript

• Create code on the web app to send the update to the bridge (maybe slightly modify the code for the sent update to the bridge)
• Send the update to the bridge and make sure it is well recieved and done

Pb in forecast when refreashing a city:
the javascript replace multiply the instances (replace .class with a list of
so when called again, it changes all the .class with the same code

If I already have a probe named "test" and I create a new one also named "test", it updates the first one instead of sending back an error.

• make sure that everything is pretty and ergonomic
• make sure that the backend works without bugs

• Add the data in it (that the moteinos will send)
• Add the versions (and current one) of each probes and bridge

Add NETWORKID, GATEWAY, NODEID, TYPE, VERSION for each probes and gateway

• Add the receiver code in a separate file
• Add the receiver code in a separate file

Send an email if someone lose its password

In ajax methods in javascript there is still some localhost call (that works locally but won't work in production)

Not only would it be useful for doing tests, it would also be useful for the end-user who want to create his own server.

When adding a new sensor/bridge, it would be better to see the sensors and bridges on the same page and to stay on this page.

It would be great to be able to delete/modify existing channels in "My channels".

Add the codes for the Bridge Moteino and the temperature and electricity Moteino

Sent a new program to a moteino only using some char

Add files to moteino wireless programming

the user can select his favorite channel to show in the dashboard
the channel is added to the current session

• see what was already done and how it can be improved
• create maybe a modal to identify the probes

Update the documentation of the whole project.
Start by creating the file with stuff already done