Intel Galileo Gateway

[vyncem]

Issue tracking the Intel Galileo gateway. Galileo will be connected to the mesh network so that it can read all of the sensor data from the wireless devices. The galileo will also be connected to the webserver via a router.

• [ ] Get node.js running (6 hrs)
• [ ] Get wireless working to communicate to mesh network (12 hrs)
• [ ] Design & implement protocol for aggregating the sensor data (9 hrs)
  • [ ] Read values from Wireless Sensors (5 hrs)
  • [ ] Read value from Door contact (3 hrs)
  • [ ] Read consumption from Power Strip (1 hrs)
• [ ] Setup back channel for remote control of power strip (3 hrs)
• [ ] Configure routing and services for communicating back to server over ethernet (12 hrs)

[gregario]

I think it might make sense for the raspi to run a node client and do edge analytics on the camera using open CV. Then we can have the power strip over serial to the Galileo and the sensors over wireless to Galileo. We run both the Galileo and raspi as node clients that spit relevant info to the node server that handles all the web stuff!

Could the pi or gal also act as the server? Or do we plan on having a computer too? On 24 May 2014 13:06, "vyncem" notifications@github.com wrote:

Issue tracking the Intel Galielo gateway that brings in the:

1. Raspberry Pi Cam,
2. Wireless Sensors and
3. Power Strip to the node.js server that hosts their controls and output-displays.

— Reply to this email directly or view it on GitHubhttps://github.com/thebedroomlaboratory/Maker2014/issues/3 .

[vyncem]

We were thinking to host the WebServer on a laptop so as not to load the PI or Galileo.