CMPE PolyProtoPi. A multiprotocol home automation system that is configurable and accessible from the cloud. Weekly Progress Report 2

Transcription

1 CMPE PolyProtoPi A multiprotocol home automation system that is configurable and accessible from the cloud. Weekly Progress Report 2 Andrew Scarani, Benji Arnold, Jeremy Williams

2 Updated Milestone Chart Task Name Test different boards Design between HA device and cloud server Choose final hardware Fix issues with Zwave binding Implement UI using demo sitemap Write script to parse and change Openhab.cfg Design MVC controllers for handling websocket with HA device Implement Google authentication on website/server Create Sitemap representing final capabilities Implement serverdevice Design and implement database on server Implement controller recognition Baseline Estimated Team Member(s) Updated Fri 1/31/14 Jeremy[25%] Fri 1/31/14 Mon 2/3/14 Andrew,Jeremy[75%] Fri 2/7/14 Comments We are now using the Beagleboard xm to host the openhab software. Communication method and syntax is mostly defined. Final Hardware is ordered. We may 2/11/14 Benji,Andrew,Jeremy 2/11/14 add components if time and budget allow When physically changing the state of a device (eg. Turning on a lamp), the Wed 2/12/14 Benji Wed 2/12/14 UI is not updated. The source of this error has been identified. A solution is still being developed Wed 2/19/14 Andrew Mon 2/17/14 2/11/14 Jeremy Wed 2/19/14. Thu 2/13/14 Andrew 2/25/14 Wed 2/12/14 Andrew Thu 2/27/14 Fri 2/21/14 Andrew Mon 3/3/14 Mon 2/24/14 Andrew,Jeremy Fri 3/7/14 Mon 3/3/14 Andrew Thu 3/13/14 Fri 2/21/14 Jeremy Mon 3/17/14 Control UI currently shows basic sitemap in a swipe-interaction flow. Some brief work was done to demo Comet Sockets using the Play Framework. Tests were successful. Currently waiting on more information about what the HA system will be sending. Very basic aspects of the login page have been created (routes, handlers, etc.) Methods were researched for storing data. MongoDB looks like the top choice right now.

3 Test Basic UI elements with final Wed 3/12/14 Andrew Wed 3/19/14 sitemap Implement ZigBee Wed 3/19/14 bindings Wed 3/19/14 Investigate zigbee protocol 2/18/14 Benji 2/18/14 Write binding 3/4/14 Benji 3/4/14 Unit testing Wed 3/19/14 Benji Wed 3/19/14 Determine how new devices are Thu 3/6/14 Jeremy recognized by each Fri 3/21/14 protocol Implement setup process for adding Wed 3/12/14 Andrew users and systems Mon 3/24/14 to database Implement device 3/11/14 Jeremy backup Mon 3/24/14 Implement X10 bindings Wed 3/26/14 Wed 3/26/14 Investigate X10 Mon 2/24/14 Benji protocol Mon 2/24/14 Develop X10 binding Wed 3/12/14 Benji Wed 3/12/14 Unit testing Wed 3/26/14 Benji Wed 3/26/14 Implement adding Wed 3/12/14 Andrew devices via the UI Thu 3/27/14 Unit testing of board software 3/18/14 Jeremy Fri 3/28/14 Implement system Wed 3/12/14 Andrew log viewer Mon 3/31/14 Unit testing of server software Wed 3/19/14 Andrew Mon 4/7/14 Unit testing complete Wed 3/26/14 Andrew,Benji,Jeremy Mon 4/7/14 Integration testing of Thu 4/3/14 Andrew,Jeremy[50%] 4/15/14 between server and system Integration testing between bindings, Thu 4/3/14 Benji,Jeremy[50%] 4/15/14 devices, and openhab config Final testing 4/8/14 Andrew,Benji,Jeremy Fri 4/18/14

4 Project Complete 4/8/14 Fri 4/18/14 Current Milestones Task Name Design between HA device and cloud server Choose final hardware Fix issues with Zwave binding Baseline Estimated Mon 2/3/14 2/11/14 Wed 2/12/14 Team Member(s) Updated Andrew,Jeremy[75%] Fri 2/7/14 Comments Communication method and syntax is mostly defined. Benji,Andrew,Jeremy 2/11/14 Final Hardware is ordered. We may add components if time and budget allow Benji Wed Issue has been identified 2/12/14 Next Milestones Task Name Implement UI using demo sitemap Write script to parse and change Openhab.cfg Investigate zigbee protocol Baseline Estimated Wed 2/19/14 2/11/14 2/18/14 Team Member(s) Andrew Jeremy Benji Updated Mon 2/17/14 Wed 2/19/14 2/18/14 Comments Control UI currently shows basic sitemap in a swipe-interaction flow. Status Development of the interface between the device and the server was mostly finished this week. The basic method of and the syntax of the messages was established. An overall framework for the scripts on the device was also finalized. Next, functions to parse, modify, and write the openhab config files will be created. The basics of the control UI were developed to show a swipe-interface as had previously been developed using the Google App Engine. This task was a bit more problematic than expected due to poor documentation on deserialization of JSON using Play Framework s Scala templates. After establishing the websocket connection between the server and the home automation system, the UI will

5 be able to be updated via a comet socket connection with the server. Some testing was performed to ensure that the comet socket connection would work properly. More development will also need to take place in refining the CSS (styling) of the page. Besides working on the UI, the base of the login page (the routes and handlers) were configured and database types were researched. The Play Framework has a Mongo DB module that seems to be perfect for storing user and home automation system information. The issue with the Zwave binding exists when the state of an end device, such as a lamp, is physically changed. When this happens the state in the UI is not updated and displayed correctly. This is a recognized issue in the openhab community and has to do with an incorrect configuration of the Zwave module. A solution is soon to be developed.

6 Gantt Chart