-- MySQL dump 10.13  Distrib 5.5.49, for debian-linux-gnu (x86_64)
--
-- Host: 0.0.0.0    Database: iotlab
-- ------------------------------------------------------
-- Server version	5.5.49-0ubuntu0.14.04.1

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;

--
-- Table structure for table `Charts`
--

DROP TABLE IF EXISTS `Charts`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `Charts` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `nombre` varchar(50) DEFAULT NULL,
  `tipo` varchar(5) DEFAULT NULL,
  `formato` varchar(20) DEFAULT NULL,
  `botones` tinyint(1) DEFAULT '0',
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=11 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Dumping data for table `Charts`
--

LOCK TABLES `Charts` WRITE;
/*!40000 ALTER TABLE `Charts` DISABLE KEYS */;
INSERT INTO `Charts` VALUES (1,'Co2','2','line',1),(2,'Humidity','5','line',1),(3,'Temperature','8','line',1),(4,'Power Consumption','7','line',0),(5,'energy cost','10','bar',0),(6,'Co2 Lab','2','gauge',0),(7,'Hum Lab','5','numeric',0),(8,'Temp Lab','8','numeric',0),(9,'Power Consumption Lab','7','numeric',0);
/*!40000 ALTER TABLE `Charts` ENABLE KEYS */;
UNLOCK TABLES;

--
-- Table structure for table `Menus`
--

DROP TABLE IF EXISTS `Menus`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `Menus` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `nombre` varchar(50) DEFAULT NULL,
  `url` varchar(100) DEFAULT NULL,
  `espadre` tinyint(1) DEFAULT NULL,
  `padre` int(3) DEFAULT NULL,
  `orden` int(3) DEFAULT NULL,
  `edit` tinyint(1) DEFAULT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `id` (`id`),
  UNIQUE KEY `Menus_id_unique` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=17 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Dumping data for table `Menus`
--

LOCK TABLES `Menus` WRITE;
/*!40000 ALTER TABLE `Menus` DISABLE KEYS */;
INSERT INTO `Menus` VALUES (1,'Home','/',0,0,1,0),(2,'Use cases','/use-cases',1,0,2,0),(3,'Lab monitoring','/use-cases/lab-monitoring',0,2,1,1),(4,'Smart Grids','#',0,2,2,1),(5,'Description','/use-cases/smart-grids/info',0,2,3,1),(6,'Data','/use-cases/smart-grids',0,2,4,1),(7,'Air Quality','#',0,2,5,1),(8,'Description','/use-cases/air-quality/info',0,2,6,1),(9,'Data','/use-cases/air-quality',0,2,7,1),(10,'Contact','/contact',0,0,4,0),(15,'Photo Gallery','/photo-gallery',0,0,3,1);
/*!40000 ALTER TABLE `Menus` ENABLE KEYS */;
UNLOCK TABLES;

--
-- Table structure for table `PageCharts`
--

DROP TABLE IF EXISTS `PageCharts`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `PageCharts` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `idPage` int(11) DEFAULT NULL,
  `idChart` int(11) DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=12 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Dumping data for table `PageCharts`
--

LOCK TABLES `PageCharts` WRITE;
/*!40000 ALTER TABLE `PageCharts` DISABLE KEYS */;
INSERT INTO `PageCharts` VALUES (1,3,1),(2,3,3),(4,2,3),(5,3,2),(6,2,4),(7,2,5),(8,8,6),(9,8,7),(10,8,8),(11,8,9);
/*!40000 ALTER TABLE `PageCharts` ENABLE KEYS */;
UNLOCK TABLES;

--
-- Table structure for table `PageTypes`
--

DROP TABLE IF EXISTS `PageTypes`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `PageTypes` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `nombre` varchar(50) DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Dumping data for table `PageTypes`
--

LOCK TABLES `PageTypes` WRITE;
/*!40000 ALTER TABLE `PageTypes` DISABLE KEYS */;
INSERT INTO `PageTypes` VALUES (1,'contenido'),(2,'dashboard');
/*!40000 ALTER TABLE `PageTypes` ENABLE KEYS */;
UNLOCK TABLES;

--
-- Table structure for table `Pages`
--

DROP TABLE IF EXISTS `Pages`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `Pages` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `titulo` varchar(50) DEFAULT NULL,
  `url` varchar(100) DEFAULT NULL,
  `contenido` text,
  `tipo` int(2) DEFAULT NULL,
  `plantilla` varchar(100) DEFAULT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `id` (`id`),
  UNIQUE KEY `Pages_id_unique` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=15 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Dumping data for table `Pages`
--

LOCK TABLES `Pages` WRITE;
/*!40000 ALTER TABLE `Pages` DISABLE KEYS */;
INSERT INTO `Pages` VALUES (1,'Contact','/contact','<p><img alt=\"\" src=\"https://iotlab-local-iubeda.c9users.io/static/images/iotworldR.png\" /></p>\r\n\r\n<p>mail: iotworld@cttc.es<br />\r\nIoTWORLD website:<a href=\"http://iotworld.cttc.es/\" target=\"_blank\">http://iotworld.cttc.es</a><br />\r\nCommunication Technologies Division (CTD)<br />\r\nCentre Tecnologic de Telecomunicacions de Catalunya (CTTC) -<a href=\"http://www.cttc.es/\" target=\"_blank\">www.cttc.es</a></p>\r\n',1,'contentPage'),(2,'Smart Grids','/use-cases/smart-grids','',2,'usecase/smartgrid'),(3,'Air Quality Dashboard','/use-cases/air-quality','',2,'usecase/templateChartBtns'),(5,'Smart Grids','/use-cases/smart-grids/info','<p>The smart grid is envisioned as the evolution of the current energy grid, which faces important challenges, such as blackouts caused by peaks of energy demand that exceed the energy grid capacity. A proposed approach to alleviate this problem is to incentivize the consumers to reschedule their energy consumption to different time intervals with lower expected power demand. These incentives are based on dynamic pricing tariffs that consider a variable energy price.</p>\r\n\r\n<p>Heating, Ventilation and Air Conditioning (HVAC) modules are considered as the most energy demanding appliances in buildings. The significant energy consumption of the HVAC systems, along with their direct influence on the user&rsquo;s well-being, highlights the necessity for effective HVAC management algorithms that reduce the power consumption in buildings, taking into account the end-user&rsquo;s comfort.</p>\r\n\r\n<p>&nbsp;</p>\r\n\r\n<p><img src=\"https://iotlab-local-iubeda.c9users.io/static/images/Smart_Grid_Use_Case.png\" /></p>\r\n\r\n<p>Fig 1. Proposed HVAC energy management system with comfort constraints in the context of IoT</p>\r\n\r\n<p>To this end, a system relying on energy scheduling methods was designed, see Fig. 1. These techniques assume a specific smart pricing tariff and various time periods. For each of these time intervals, the scheduler determines the operational power (ON or OFF) of the HVACs modules both to minimize the energy consumption cost and to respect the users&rsquo; comfort constraints. These decisions are sent to actuators through an Ethernet connection. The actuators consist on programmable sockets where the HVACs are connected. To assess the comfort, the temperature is measured at several building positions by different sensor nodes that form a wireless sensor network (WSN), thus providing a more accurate measure of comfort compared to traditional methods. Thanks to the Internet of Things (IoT) paradigm, the user may interact remotely with the HVAC control system. In particular, a web server application was developed, which permits the user to decide remotely the temperature of comfort. Moreover, by means of this web application the real-time temperature and energy consumption information is sent through Internet and displayed at the end user&rsquo;s device. The energy scheduler, the web server application and a database, that stores the data measurements, form part of the Gateway subsystem. This is exemplified in more detail in Fig. 2, where a block diagram of the overall system is displayed.</p>\r\n\r\n<p><img src=\"https://iotlab-local-iubeda.c9users.io/static/images/Smart_Grid_Blocks.png\" /></p>\r\n\r\n<p>Fig. 2. Detail of the Gateway subsystem as well as its interaction with the rest of blocks</p>\r\n\r\n<p>Fig 3. shows in more detail the inputs (Smart pricing tariff, temperatures measurements and the user constraints) and the outputs (the decision to switch on or off a load) of the energy schedulers proposed.</p>\r\n\r\n<p><img src=\"https://iotlab-local-iubeda.c9users.io/static/images/Smart_Grids_Energy_scheduler.png\" /></p>\r\n\r\n<p>Fig3. Energy schedulers inputs/outputs</p>\r\n',1,'contentPage'),(6,'Air Quality','/use-cases/air-quality/info','<p>Air quality monitoring in smart buildings is of paramount importance for both people well-being and for the energy efficient management of HVAC (Heating Ventilation and Air Conditioning) systems. Regarding people&rsquo;s well-being, Carbon dioxide (CO2) levels are regarded as a standard for air quality. In fact, according to the Standard of The American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE), CO2&nbsp;concentrations above 1000 ppm provoke severe effects on people&rsquo;s well-being such as discomfort, feel dizzy or feel headache. In this regard, next table (introduced by Max von Pettenkofer) establishes the relation between CO2&nbsp;concentration levels and the indoor air quality.</p>\r\n\r\n<p><img alt=\"\" src=\"https://iotlab-local-iubeda.c9users.io/static/images/Table1_air_quality.png\" /></p>\r\n\r\n<p>The air quality is monitored in two different buildings by means of CO2&nbsp;sensors as CO2concentration level is the standard parameter to assess the air quality. Moreover, temperature and humidity sensors are deployed, as these are parameters directly related to the people&rsquo;s well-being. More specifically, the IoTWORLD implementation for this setup is described next.</p>\r\n\r\n<p><img alt=\"\" src=\"https://iotlab-local-iubeda.c9users.io/static/images/Air_Quality_Use_Case.png\" /></p>\r\n\r\n<p>In CTTC&rsquo;s building B6, the air quality of one room is monitored by means of one CO2&nbsp;sensor and two humidity and temperature sensors. The CO2&nbsp;sensor is connected to a WSN node whereas each pair of humidity and temperature sensors is connected to a WSN node. The CO2Engine K30 sensor by SenseAir was considered to obtain the desired CO2&nbsp;measurements. Regarding the WSN node, the Zolertia Z1 mote is used.</p>\r\n\r\n<p>The connection between the CO2&nbsp;Engine K30 sensor and the Zolertia Z1 WSN node is done through I2C (Inter-Integrated Circuit) communication protocol, see next figure<em>:</em></p>\r\n\r\n<p><img alt=\"\" src=\"https://iotlab-local-iubeda.c9users.io/static/images/Z1_co2_air_quality.png\" /></p>\r\n\r\n<p>Regarding the temperature and humidity sensors, the SHT11 sensors by Sensirion have been selected. The WSN nodes gather the measurements, provided by the sensors, and send them periodically to a WSN node sink by means of a one hop wireless channel. On its turn, the WSN sink is connected via USB to the control centre. It is worth mention that the WSN nodes support Contiki OS, an open-source operating system for the Internet of Things (IoT). Contiki permits to manage easily the communication between the peripherals, i.e. the sensors, and the WSN nodes and also between WSN nodes.</p>\r\n\r\n<p>The control centre, consists of several sub blocks and has several functionalities which will be described next, by means of the next figure, which contains a detailed description of the control centre.</p>\r\n\r\n<p><img alt=\"\" src=\"https://iotlab-local-iubeda.c9users.io/static/images/Control_center_air_quality.png\" /></p>\r\n\r\n<p>First, the WSN sink receives the measurements sent by the WSN sources. These data are sent to the server, which stores the measurements in a database. The server is written in JavaScript and the communication with the database is done by means of SQL queries. Moreover, the server manages the communication through internet with remote users. This permits the users to visualize remotely the air quality. To this end, in the user side we use a web application. More specifically, we rely on&nbsp;<em>Sencha Touch</em>, which is a high-performance HTML5 mobile application framework, which enables developers to build powerful applications for various operating systems, including iOS and Android. Thereby, by means of this web application, the user can see plots of the CO2&nbsp;measurements. More specifically, real time plots and statistics of the last minutes and hours are displayed.</p>\r\n\r\n<p>As it is shown above, the air quality is measured in another CTTC building called &ldquo;CTTC building B4&rdquo;. The experimental setup in this building is as follows and it is detailed in the next figure.</p>\r\n\r\n<p><img alt=\"\" src=\"https://iotlab-local-iubeda.c9users.io/static/images/Building_B4_air_quality.png\" /></p>\r\n\r\n<p>The air quality is measured by means of CO2&nbsp;sensors in two different places of the building. The first one is located in the ground floor of the building, and its identifier is &ldquo;9&rdquo;, whereas the other sensor is located in the first floor and its identifier is &ldquo;15&rdquo;. As it can be observed, a multihop WSN is considered between the CO2&nbsp;sensors and the gateway (GW). The GW consists of two components. The first one is a WSN sink, which receives the CO2&nbsp;measurements forwarded by the multihop WSN. The WSN sink node is connected via USB to a Raspberry Pi 2, whose aim is to take the measurements of the WSN sink and to send them via SQL queries to the Cloud database. It is worth to mention that the software that permits to perform the SQL queries is based on Python language.</p>\r\n\r\n<p>Last but not least it is important to specify how the multihop WSN relays the CO2measurements from the source nodes to the sink node. The protocol implemented for this purpose is called Routing Protocol for Low power and Lossy Networks (RPL). The main objective of RPL protocol is to address the routing problem in sensor networks, i.e. setting up and maintaining reliable paths as well as promptly detecting link failures without wasting energy and communication resources.</p>\r\n',1,'contentPage'),(7,'IoTWORLD','/','<p>IoTWORLD is a unique end-to-end experimental platform for the Internet of Things. It is focused on Wireless Communications systems and data analytics. It has been entirely developed by the Communication Technologies Division of CTTC.</p>\r\n\r\n<p>&nbsp;</p>\r\n\r\n<div style=\"position:relative;padding-bottom:56.25%;padding-top:30px;height:0;overflow:hidden;\"><iframe allowfullscreen=\"\" frameborder=\"0\" height=\"360\" src=\"//www.youtube.com/embed/2K4PD36kqxs?rel=0\" style=\"position: absolute;top: 0;left: 0;width: 100%;height: 100%;\" width=\"640\"></iframe></div>\r\n\r\n<p>&nbsp;</p>\r\n\r\n<p>The heterogeneity of IoTWORLD is realized in a variety of available sensors, actuators, wireless technologies, Internet connectivity, and use cases already available. IoTWORLD relies on a 4-layer architecture.</p>\r\n\r\n<p>&nbsp;</p>\r\n\r\n<p><img alt=\"\" src=\"https://iotlab-local-iubeda.c9users.io/static/images/IoTWORLD_block_diagram.jpg\" /></p>\r\n\r\n<p>The bottom layer consists of heterogeneous low power sensing devices and actuators which permit to interact with the real world. Sensors include temperature, humidity, light, ultrasonic, accelerometers, CO2 level, power consumption meters, and a variety of eHealth sensors, among others. Various actuators are available in IoTWORLD: smart DC plugs, lights, and moving robots, among others.</p>\r\n\r\n<p>The second layer of IoTWORLD consists of a set of gateways which permit to gather the data sent by the sensing devices via heterogeneous wireless technologies. This can be done either in a single hop or via multihop routes. Moreover, the gateways can also store and analyze the data measurements, and communicate with data centers on the edge via software defined networking. Thereby, data analytics on the edge are enabled.</p>\r\n\r\n<p>Various wireless communication technologies are available in IoTWORLD to connect the sensors and actuators with the gateways. This includes Low Power Wide Area Networks, like LoRa and SigFox technologies, operating in SubGigahertz bands, as well as Zigbee and Low Power Wi-Fi.</p>\r\n\r\n<p>The gateways of IoTWORLD are implemented in Raspberry Pi 2 platforms. These are, essentially, small and low-cost computers which facilitate the flexibility and scalability of IoTWORLD. One of the functions of these gateways is to provide sensors and actuators with Internet connectivity to reach the cloud. This connectivity is provided in IoTWORLD via Ethernet, Wi-Fi, 3G and LTE, or operator-like Low Power Wide Area Networks. Another important function of the gateways is to provide distributed data analytics capabilities of the gathered measurements. Moreover, they can be connected to data centers in the cloud through software defined networking.</p>\r\n\r\n<p>The third layer lies on the cloud. Distributed data storage and applications running on the cloud are available in IoTWORLD.</p>\r\n\r\n<p>The top layer of IoTWORLD consists of the user layer. Users can interact with IoTWORLD through applications running in their computing devices, such as tablets, smartphones, or personal computers.</p>\r\n\r\n<p>The overall architecture is independent of the number of simultaneous running networks and connected nodes. Therefore, it is extremely flexible and scalable, as it is desired for a platform devoted to experiment with the Internet of Things.</p>\r\n',1,'contentPage'),(8,'Lab monitoring','/use-cases/lab-monitoring','',2,'usecase/general'),(12,'Photo Gallery','/photo-gallery','<p><img alt=\"\" src=\"https://iotlab-local-iubeda.c9users.io/static/images/IMG_3241.JPG\" /></p>\r\n\r\n<p>Stand CTTC</p>\r\n\r\n<p>&nbsp;</p>\r\n\r\n<p><img alt=\"\" src=\"https://iotlab-local-iubeda.c9users.io/static/images/DSC_0578.JPG\" /></p>\r\n\r\n<p>CTTC conference room</p>\r\n\r\n<p>&nbsp;</p>\r\n\r\n<p><img alt=\"\" src=\"https://iotlab-local-iubeda.c9users.io/static/images/DSC_0576.JPG\" /></p>\r\n\r\n<p>Motes</p>\r\n',1,'contentPage');
/*!40000 ALTER TABLE `Pages` ENABLE KEYS */;
UNLOCK TABLES;

--
-- Table structure for table `SensorDetails`
--

DROP TABLE IF EXISTS `SensorDetails`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `SensorDetails` (
  `tipo` int(11) NOT NULL DEFAULT '0',
  `nombre` varchar(255) DEFAULT NULL,
  `unidad` varchar(255) DEFAULT NULL,
  `evento` varchar(255) DEFAULT NULL,
  PRIMARY KEY (`tipo`),
  UNIQUE KEY `tipo` (`tipo`),
  UNIQUE KEY `SensorDetails_tipo_unique` (`tipo`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Dumping data for table `SensorDetails`
--

LOCK TABLES `SensorDetails` WRITE;
/*!40000 ALTER TABLE `SensorDetails` DISABLE KEYS */;
INSERT INTO `SensorDetails` VALUES (2,'CO2','ppm','co2'),(5,'Humidity','%','hum'),(7,'Power Consumption','W','halleff'),(8,'Temperature','ºC','temp'),(10,'Energy cost','€','cost'),(11,'Unknown','Unknown','unk');
/*!40000 ALTER TABLE `SensorDetails` ENABLE KEYS */;
UNLOCK TABLES;

--
-- Table structure for table `SensorLocations`
--

DROP TABLE IF EXISTS `SensorLocations`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `SensorLocations` (
  `address` int(11) NOT NULL DEFAULT '0',
  `nombre` varchar(255) DEFAULT NULL,
  PRIMARY KEY (`address`),
  UNIQUE KEY `address` (`address`),
  UNIQUE KEY `SensorLocations_address_unique` (`address`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Dumping data for table `SensorLocations`
--

LOCK TABLES `SensorLocations` WRITE;
/*!40000 ALTER TABLE `SensorLocations` DISABLE KEYS */;
INSERT INTO `SensorLocations` VALUES (1,'Lab Temp1'),(2,'Lab Hum1'),(3,'Lab Temp2'),(4,'Lab Hum2'),(5,'Load_1 Lab'),(6,'Load_2 Lab'),(7,'Load_3 Lab'),(8,'CO2_Lab'),(9,'CO2_Audit'),(11,'outside Temp'),(12,'outside Hum'),(15,'CO2_Floor1'),(16,'CO2_Corridor'),(80,'Load 1'),(81,'Load 2'),(82,'Load 3'),(83,'Energy Cost 1'),(84,'Energy Cost 2');
/*!40000 ALTER TABLE `SensorLocations` ENABLE KEYS */;
UNLOCK TABLES;

--
-- Table structure for table `Sensors`
--

DROP TABLE IF EXISTS `Sensors`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `Sensors` (
  `identifier` varchar(255) NOT NULL DEFAULT '',
  `name` varchar(255) DEFAULT NULL,
  `type` int(11) DEFAULT NULL,
  `address` int(11) DEFAULT NULL,
  `lastseq` int(11) DEFAULT NULL,
  `createdAt` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `updatedAt` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `active` tinyint(1) DEFAULT '0',
  PRIMARY KEY (`identifier`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Dumping data for table `Sensors`
--

LOCK TABLES `Sensors` WRITE;
/*!40000 ALTER TABLE `Sensors` DISABLE KEYS */;
INSERT INTO `Sensors` VALUES ('1+8','Sensor of type 8',8,1,1,'2014-09-01 12:16:03','2016-03-07 06:14:17',1),('11+8','Sensor of type 8',8,11,1,'2015-11-16 11:36:54','2016-03-04 02:00:37',0),('12+5','Sensor of type 5',5,12,1,'2015-11-16 11:36:54','2016-03-04 02:00:37',0),('15+2','Sensor of type 2',2,15,1,'2015-09-07 13:12:47','2015-09-23 01:25:08',1),('16+2','Sensor of type 2',2,16,NULL,'0000-00-00 00:00:00','0000-00-00 00:00:00',0),('2+5','Sensor of type 5',5,2,1,'2014-09-01 12:16:03','2016-03-07 06:14:17',1),('3+8','Sensor of type 8',8,3,1,'2014-09-01 12:15:38','2016-03-07 06:14:17',1),('4+5','Sensor of type 5',5,4,1,'2014-09-01 12:15:38','2016-03-07 06:14:17',1),('5+7','Sensor of type 7',7,5,1,'2014-09-01 12:15:57','2016-03-14 14:58:50',1),('6+7','Sensor of type 7',7,6,1,'2014-09-01 12:15:50','2016-03-14 14:58:51',0),('7+7','Sensor of type 7',7,7,1,'2014-09-01 12:15:54','2016-03-14 14:58:52',0),('8+2','Sensor of type 2',2,8,1,'2014-09-01 11:58:40','2016-03-14 14:58:51',1),('80+11','Sensor of type 11',11,80,1,'0000-00-00 00:00:00','0000-00-00 00:00:00',0),('81+11','Sensor of type 11',11,81,1,'0000-00-00 00:00:00','0000-00-00 00:00:00',0),('82+11','Sensor of type 11',11,82,1,'0000-00-00 00:00:00','0000-00-00 00:00:00',0),('83+10','Sensor of type 10',10,83,1,'0000-00-00 00:00:00','0000-00-00 00:00:00',1),('9+2','Sensor of type 2',2,9,1,'0000-00-00 00:00:00','2015-09-23 01:25:08',0);
/*!40000 ALTER TABLE `Sensors` ENABLE KEYS */;
UNLOCK TABLES;

--
-- Table structure for table `Users`
--

DROP TABLE IF EXISTS `Users`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `Users` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `nombre` varchar(50) DEFAULT NULL,
  `pass` varchar(200) DEFAULT NULL,
  `tipo` int(2) DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Dumping data for table `Users`
--

LOCK TABLES `Users` WRITE;
/*!40000 ALTER TABLE `Users` DISABLE KEYS */;
INSERT INTO `Users` VALUES (1,'admin','21232f297a57a5a743894a0e4a801fc3',1);
/*!40000 ALTER TABLE `Users` ENABLE KEYS */;
UNLOCK TABLES;
/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;

/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;

-- Dump completed on 2016-06-29 19:52:43
