meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
sustcodecamp2016:group4:start [2016/03/10 14:07]
shaghayegh.royaee_student.lut.fi
sustcodecamp2016:group4:start [2016/03/11 15:19] (current)
omater
Line 113: Line 113:
 We made the choice of retrieving from the html page rather than from a telnet session and the perl api of the fhem server simply because we were not really familiar with the entire API behind the FHEM server and the WEBFHEM was the tool that we understood most. We made the choice of retrieving from the html page rather than from a telnet session and the perl api of the fhem server simply because we were not really familiar with the entire API behind the FHEM server and the WEBFHEM was the tool that we understood most.
 \\ \\
-Here is the code to set the temperature ​to a certain value from our application:​+Here is the example method (which sets the desired ​temperature ​on thermostat) that shows the idea in which our application ​sets and retrieves information:
 \\ \\
 <​code>​ <​code>​
Line 133: Line 133:
  }  }
 </​code>​ </​code>​
 +\\
 +Among many classes used by our application we use three, that reflect real devices. Those classes implement the following methods:
 +<​code>​
 +Thermostat
 +|_getDesiredTemperature()
 +|_setTemperature(double Temperature)
 +|_setScheduleTime(String dayTime, String time)
 +|_getMeasuredTemperatures()
 +|_getCurrentTemperature()
 +MovementDetector
 +|_checkIfThereWasMovement()
 +WindowDetector
 +|_checkIfWindowIsOpened()
 +</​code>​
 +\\
 +Class implementing our GUI creates new thread for movement detector and also for window detector. It checks the value returned by methods from suitable classes every given period of time.
 +
 +
 ====Limitations and Future Possibilities==== ====Limitations and Future Possibilities====
 With the amount of time we had to work with the tools that were given, we decided to stick with the integrated schedule system of the fht80b thermostat. With the amount of time we had to work with the tools that were given, we decided to stick with the integrated schedule system of the fht80b thermostat.
Line 142: Line 160:
 This could be done using the GPS system from the user's smartphone for example. This could be done using the GPS system from the user's smartphone for example.
 \\  \\ 
 +Our system could also propose some changes of the schedule, based on the registered behaviors of the user, that differ from current schedule (for example lack of movement in apartment during the period, in which it should be heated). ​
  
 ====Protocol to present==== ====Protocol to present====
Line 166: Line 185:
 ====Documentation==== ====Documentation====
   * Unordered List ItemProject Presentation:​ {{:​sustcodecamp2016:​group4:​group3_presentation.pdf|}}   * Unordered List ItemProject Presentation:​ {{:​sustcodecamp2016:​group4:​group3_presentation.pdf|}}
-  * Unordered List ItemProject Poster:  +  * Unordered List ItemProject Poster: ​{{:​sustcodecamp2016:​group4:​poster.pdf|}} 
-  * Unordered List ItemProject Report:+  * Unordered List ItemProject Report: ​{{:​sustcodecamp2016:​group4:​lut_codecamp_theinternationals.pdf|}}
  
 ====Refrences==== ====Refrences====