\nA modular system where I could gather data from indoor and outdoor temperatures to local power consumption.<\/p>\n
![\"CasaMonit](\"https:\/\/jaerder.videmogroup.org\/blog\/wp-content\/uploads\/2016\/02\/architecture.png\")
The system is meant to be designed in such manner that the server side\u00a0is fully abstracted from the sensor module side, more sensors modules may be implemented on different hardware platforms. There can be as many sensor modules as required, connected on a single Ethernet network.<\/p>\n
<\/p>\n
Sensor Module Hardware (Prototype)<\/h2>\n![\"Prototype](\"https:\/\/jaerder.videmogroup.org\/blog\/wp-content\/uploads\/2016\/02\/prototype_hw_sensormodule.jpg\")
Prototype Hardware Sensor Module<\/figcaption><\/figure>\n<\/p>\n
An Arduino is being\u00a0used as base, in order to allow for the construction of a fast prototype. Data is sent to the server via TCP\/IP, by a HTTP GET request.
\nThe Ethernet shield used is based on the MIcrochip’s ENC 28J60\u00a0Ethernet controller. \u00a0The\u00a0UIPEthernet<\/a> library was used, as it is a drop-in replacement for the standard Arduino Ethernet library, with support for DHCP, and DNS, \u00a0which is a huge plus, in order to integrate the sensor modules into my home network.
\nThe current prototype is connected to a 1-wire temperature sensor (a\u00a0DS18B20).<\/p>\nServer Side<\/h2>\nHardware<\/h3>\n
The server should be able to run in any hardware capable of running a lamp stack<\/a>.<\/p>\nSensor Module to data base interface<\/h3>\n
In order to exchange information between the sensor modules and the server over tcp\/ip one of the following approaches were considered:<\/p>\n
\n- Write an application running on the server that is capable of accepting and managing several simultaneous connections from several sensor modules. Its a more lengthy and harder approach.<\/li>\n
- Use an already established method that can already do that is described above, but without having to write a native application from scratch.<\/li>\n<\/ul>\n
The method for implementing a communication method that satisfied the above criteria was to use a php script. It solves the concurrency issue, as well as its far more simple to implement.<\/p>\n
Data Base Design<\/h3>\n![\"Initial](\"https:\/\/jaerder.videmogroup.org\/blog\/wp-content\/uploads\/2016\/02\/EER-Diagram.png\")
Initial EER Diagram Proposal.<\/figcaption><\/figure>\nThe initial diagram described above does not take into account that one sensor module may have more than one sensor attached (some of my requirements changed mid development).
\nThe monitoring system must also have a catalog of the sensor modules and sensor types.<\/p>\n
Front end and back end<\/h3>\n
As of 25th of February, I’m still undecided about the implementation, but both the back end and front end will be probably built with bootstrap<\/a> and php.<\/p>\nCurrent status<\/h2>\n
As of today, the sensor module is already capable of sending data via Ethernet via HTTP GET method described\u00a0above, into a lamp stack installed on the development machine.<\/p>\n![\"Prototype](\"https:\/\/jaerder.videmogroup.org\/blog\/wp-content\/uploads\/2016\/02\/proto_table.png\")
Prototype table. The system is already capable of recording sensor data into a database table.<\/figcaption><\/figure>\n <\/p>\n
To be continued…..<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
The quest for a Home Monitoring System : Part 1 General Architecture For a long , long time I wanted to have a system to monitor, and perform data collection, on my home. A modular system where I could gather data from indoor and outdoor temperatures to local power consumption. The system is meant to … <\/p>\n
<\/p>\n
An Arduino is being\u00a0used as base, in order to allow for the construction of a fast prototype. Data is sent to the server via TCP\/IP, by a HTTP GET request. The server should be able to run in any hardware capable of running a lamp stack<\/a>.<\/p>\n In order to exchange information between the sensor modules and the server over tcp\/ip one of the following approaches were considered:<\/p>\n The method for implementing a communication method that satisfied the above criteria was to use a php script. It solves the concurrency issue, as well as its far more simple to implement.<\/p>\n The initial diagram described above does not take into account that one sensor module may have more than one sensor attached (some of my requirements changed mid development). As of 25th of February, I’m still undecided about the implementation, but both the back end and front end will be probably built with bootstrap<\/a> and php.<\/p>\n As of today, the sensor module is already capable of sending data via Ethernet via HTTP GET method described\u00a0above, into a lamp stack installed on the development machine.<\/p>\n <\/p>\n To be continued…..<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" The quest for a Home Monitoring System : Part 1 General Architecture For a long , long time I wanted to have a system to monitor, and perform data collection, on my home. A modular system where I could gather data from indoor and outdoor temperatures to local power consumption. The system is meant to … <\/p>\n
\nThe Ethernet shield used is based on the MIcrochip’s ENC 28J60\u00a0Ethernet controller. \u00a0The\u00a0UIPEthernet<\/a> library was used, as it is a drop-in replacement for the standard Arduino Ethernet library, with support for DHCP, and DNS, \u00a0which is a huge plus, in order to integrate the sensor modules into my home network.
\nThe current prototype is connected to a 1-wire temperature sensor (a\u00a0DS18B20).<\/p>\nServer Side<\/h2>\n
Hardware<\/h3>\n
Sensor Module to data base interface<\/h3>\n
\n
Data Base Design<\/h3>\n
\nThe monitoring system must also have a catalog of the sensor modules and sensor types.<\/p>\nFront end and back end<\/h3>\n
Current status<\/h2>\n