120 may determine that the translations and rotations satisfy a similarity threshold, e.g., match or substantially match, and, in response, verify that a position is accurate. In another example, the position verifier 120 may determine that the translations and rotations do not satisfy the similarity threshold and, in response, determine that a position is inaccurate. Where the position verifier 120 determines that the position is inaccurate, the drone 102 may determine that the loop closure has failed and attempt to perform another loop closure at a later point in time, using another reference position, or both.

In some implementations, the similarity threshold can be any appropriate type of similarity threshold. For instance, the position verifier 120 can determine whether a differences between translations and rotations satisfy, e.g., be less than or equal to, a threshold. The position verifier 12 can determine whether rotation matrices that represent the rotations satisfy a rotation similarity threshold, e.g., have at least a predetermined amount of similarity, and translation vectors that represent the translations satisfy a translation similarity threshold, e.g., have at least a predetermined cosine similarity, or both.

Additionally or alternatively to using images to verify loop closure made with LIDAR, the drone 102 can use VIO to verify a loop closure made with LIDAR. The drone 102 may select a reference position based on the sample LIDAR profile, then estimate a linear and angular velocity of the drone 102 from a location of a prior loop closure to the selected reference position, determine a linear and angular velocity of the drone 102 determined from VIO over a same time period, and determine whether the linear and angular velocities satisfy a VIO similarity threshold, e.g., match or substantially match. For example, the drone 102 may determine whether the linear or angular velocities based on the VIO and based on the LIDAR profile are more than 10% off from one another and, if so, determine the loop closure is inaccurate. In another example, the drone 102 may determine whether the linear or angular velocities based on the VIO and based on the LIDAR profile are more than 10% off from one another and, if not, determine the loop closure is accurate.

In some examples, the drone 102 can use VIO data from a previous loop closure position to a current position to verify LIDAR loop closure. For instance, although VIO might drift over time, VIO data can be sufficiently accurate over shorter distances, e.g., enough to determine whether to reject an inaccurate loop closure. The drone 102 can determine a past position, e.g., including a previous loop closure. The drone 102 can add motion estimated by VIO since the past position to the past position to determine an estimated new position. The drone 102 can compare the estimated new position to the selected reference position. If differences between the estimated new position and the selected reference position satisfy one or more difference thresholds, the drone 102 can determine that the loop closure is accurate. If the differences between the estimated new position and the selected reference position do not satisfy the one or more difference thresholds, the drone 102 can determine that the loop closure is inaccurate.

In some implementations, the drone 102 can include more or fewer components. For instance, a single component can perform the operations described with reference to the reference position selector 112 and the LIDAR profile-based position engine 116. In some examples, a single component can perform the operations described with reference to the LIDAR profile-based position engine 116, and the image-based position engine 118.

The drone 102 can include several different functional components, including the reference position selector 112, the LIDAR profile-based position engine 116, the image-based position engine 118, and the position verifier 120. The reference position selector 112, the LIDAR profile-based position engine 116, the image-based position engine 118, the position verifier 120, or a combination of these, can include one or more data processing apparatuses, can be implemented in code, or a combination of both. For instance, each of the reference position selector 112, the LIDAR profile-based position engine 116, the image-based position engine 118, and the position verifier 120 can include one or more data processors and instructions, e.g., code, that cause the one or more data processors to perform the operations discussed herein.

The various functional components of the drone 102 can be installed on one or more computers as separate functional components or as different modules of a same functional component. For example, the reference position selector 112, the LIDAR profile-based position engine 116, the image-based position engine 118, the position verifier 120, or a combination of these, can be implemented as computer programs installed on one or more computers in one or more locations that are coupled to each through a network. In cloud-based systems for example, these components can be implemented by individual computing nodes of a distributed computing system.

FIG. 4 is a flow diagram illustrating an example of a process 400 for loop closure using multi-modal sensor data. Briefly, and as will be described in more detail below, the process 400 includes obtaining a sample LIDAR profile generated by a drone (402), selecting a reference position based on the sample LIDAR profile (404), determining a LIDAR profile-based translation and rotation relative to a reference LIDAR profile of the reference position (406), determining an image-based translation and rotation relative to a reference image of the reference position (408), and determining whether the LIDAR profile-based translation and rotation and the image-based translation and rotation satisfy a similarity threshold (410).

The process 400 includes obtaining a sample LIDAR profile generated by a drone (402). For example, the reference position selector 112 may obtain a point cloud assembled by measurements taken by a LIDAR of the drone 102 during a time period, e.g., the last 6 seconds.

The process 400 includes selecting a reference position based on the sample LIDAR profile (404). For example, the reference position selector 112 may obtain reference LIDAR profiles for a predetermined number of points, e.g., eight points, use an ICP algorithm to identify the reference LIDAR profile that best matches the sample LIDAR profile, and select the reference position that corresponds to the identified reference LIDAR profile. The reference LIDAR profile that best matches can include the reference LIDAR profile that has a highest similarity index when compared with at least a portion of the sample LIDAR profile. In some implementations, the reference position selector 112 generates multiple similarity indexes. For example, the reference position selector 112 can generate one or more values, e.g., numerical, vectors, matrices, among others, indicating a similarity between a sample LIDAR profile and one or more reference LIDAR profiles.

The process 400 includes determining a LIDAR profile-based translation and rotation relative to a reference LIDAR profile of the reference position (406). For example, the LIDAR profile-based position engine 116 may determine translation and rotation from the reference LIDAR profile of the selected reference position to the sample LIDAR profile.

The process 400 includes determining an image-based translation and rotation relative to a reference image of the reference position (408). For example, the image-based position engine 118 may receive the reference image and the sample image, and determine the translation and the rotation from the reference image to the sample image. The drone 102 can receive the sample image substantially concurrently with receipt of the LIDAR measurements used to obtain the sample LIDAR profile.

The process 400 includes determining whether the LIDAR profile-based translation and rotation and the image-based translation and rotation satisfy a similarity threshold (410). For example, the position verifier 120 may determine whether a distance between the translations and a distance between the rotations satisfy the similarity threshold. In some examples, the position verifier 120 can determine whether the translations and the rotations match.

The order of steps in the process 400 described above is illustrative only, and loop closure using the multi-modal sensor data can be performed in different orders. For example, the drone can determine the image-based translation and rotation prior to or substantially concurrently with the determination of the LIDAR profile-based translation, the selection of the reference position, obtaining the sample LIDAR profile, or a combination of these.

FIG. 5 is a diagram illustrating an example of a property monitoring system 500. In some cases, the property monitoring system 500 may include components of the system 100 of FIG. 1. For example, the drone 102 may be one of the robotic devices 590.

The network 505 is configured to enable exchange of electronic communications between devices connected to the network 505. For example, the network 505 may be configured to enable exchange of electronic communications between the control unit 510, the one or more user devices 540 and 550, the monitoring server 560, and the central alarm station server 570. The network 505 may include, for example, one or more of the Internet, Wide Area Networks (WANs), Local Area Networks (LANs), analog or digital wired and wireless telephone networks (e.g., a public switched telephone network (PSTN), Integrated Services Digital Network (ISDN), a cellular network, and Digital Subscriber Line (DSL)), radio, television, cable, satellite, or any other delivery or tunneling mechanism for carrying data. The network 505 may include multiple networks or subnetworks, each of which may include, for example, a wired or wireless data pathway. The network 505 may include a circuit-switched network, a packet-switched data network, or any other network able to carry electronic communications (e.g., data or voice communications). For example, the network 505 may include networks based on the Internet protocol (IP), asynchronous transfer mode (ATM), the PSTN, packet-switched networks based on IP, X.25, or Frame Relay, or other comparable technologies and may support voice using, for example, VoIP, or other comparable protocols used for voice communications. The network 505 may include one or more networks that include wireless data channels and wireless voice channels. The network 505 may be a wireless network, a broadband network, or a combination of networks including a wireless network and a broadband network.

The control unit 510 includes a controller 512 and a network module 514. The controller 512 is configured to control a control unit monitoring system (e.g., a control unit system) that includes the control unit 510. In some examples, the controller 512 may include a processor or other control circuitry configured to execute instructions of a program that controls operation of a control unit system. In these examples, the controller 512 may be configured to receive input from sensors, flow meters, or other devices included in the control unit system and control operations of devices included in the household (e.g., speakers, lights, doors, etc.). For example, the controller 512 may be configured to control operation of the network module 514 included in the control unit 510.

The network module 514 is a communication device configured to exchange communications over the network 505. The network module 514 may be a wireless communication module configured to exchange wireless communications over the network 505. For example, the network module 514 may be a wireless communication device configured to exchange communications over a wireless data channel and a wireless voice channel. In this example, the network module 514 may transmit alarm data over a wireless data channel and establish a two-way voice communication session over a wireless voice channel. The wireless communication device may include one or more of a LTE module, a GSM module, a radio modem, cellular transmission module, or any type of module configured to exchange communications in one of the following formats: LTE, GSM or GPRS, CDMA, EDGE or EGPRS, EV-DO or EVDO, UMTS, or IP.

The network module 514 also may be a wired communication module configured to exchange communications over the network 505 using a wired connection. For instance, the network module 514 may be a modem, a network interface card, or another type of network interface device. The network module 514 may be an Ethernet network card configured to enable the control unit 510 to communicate over a local area network and/or the Internet. The network module 514 also may be a voice band modem configured to enable the alarm panel to communicate over the telephone lines of Plain Old Telephone Systems (POTS).

The control unit system that includes the control unit 510 includes one or more sensors 520. For example, the monitoring system may include multiple sensors 520. The sensors 520 may include a lock sensor, a contact sensor, a motion sensor, or any other type of sensor included in a control unit system. The sensors 520 also may include an environmental sensor, such as a temperature sensor, a water sensor, a rain sensor, a wind sensor, a light sensor, a smoke detector, a carbon monoxide detector, an air quality sensor, etc. The sensors 520 further may include a health monitoring sensor, such as a prescription bottle sensor that monitors taking of prescriptions, a blood pressure sensor, a blood sugar sensor, a bed mat configured to sense presence of liquid (e.g., bodily fluids) on the bed mat, etc. In some examples, the health monitoring sensor can be a wearable sensor that attaches to a user in the home. The health monitoring sensor can collect various health data, including pulse, heart rate, respiration rate, sugar or glucose level, bodily temperature, or motion data.

The sensors 520 can also include a radio-frequency identification (RFID) sensor that identifies a particular article that includes a pre-assigned RFID tag.

The system 500 also includes one or more thermal cameras 530 that communicate with the control unit 510. The thermal camera 530 may be an IR camera or other type of thermal sensing device configured to capture thermal images of a scene. For instance, the thermal camera 530 may be configured to capture thermal images of an area within a building or home monitored by the control unit 510. The thermal camera 530 may be configured to capture single, static thermal images of the area and also video thermal images of the area in which multiple thermal images of the area are captured at a relatively high frequency (e.g., thirty images per second). The thermal camera 530 may be controlled based on commands received from the control unit 510. In some implementations, the thermal camera 530 can be an IR camera that captures thermal images by sensing radiated power in one or more IR spectral bands, including NIR, SWIR, MWIR, and/or LWIR spectral bands.

The thermal camera 530 may be triggered by several different types of techniques. For instance, a Passive Infra-Red (PIR) motion sensor may be built into the thermal camera 530 and used to trigger the thermal camera 530 to capture one or more thermal images when motion is detected. The thermal camera 530 also may include a microwave motion sensor built into the camera and used to trigger the thermal camera 530 to capture one or more thermal images when motion is detected. The thermal camera 530 may have a “normally open” or “normally closed” digital input that can trigger capture of one or more thermal images when external sensors (e.g., the sensors 520, PIR, door/window, etc.) detect motion or other events. In some implementations, the thermal camera 530 receives a command to capture an image when external devices detect motion or another potential alarm event. The thermal camera 530 may receive the command from the controller 512 or directly from one of the sensors 520.

In some examples, the thermal camera 530 triggers integrated or external illuminators (e.g., Infra-Red or other lights controlled by the property automation controls 522, etc.) to improve image quality. An integrated or separate light sensor may be used to determine if illumination is desired and may result in increased image quality.

The thermal camera 530 may be programmed with any combination of time/day schedules, monitoring system status (e.g., “armed stay,” “armed away,” “unarmed”), or other variables to determine whether images should be captured or not when triggers occur. The thermal camera 530 may enter a low-power mode when not capturing images. In this case, the thermal camera 530 may wake periodically to check for inbound messages from the controller 512. The thermal camera 530 may be powered by internal, replaceable batteries if located remotely from the control unit 510. The thermal camera 530 may employ a small solar cell to recharge the battery when light is available. Alternatively, the thermal camera 530 may be powered by the controller's 512 power supply if the thermal camera 530 is co-located with the controller 512.

In some implementations, the thermal camera 530 communicates directly with the monitoring server 560 over the Internet. In these implementations, thermal image data captured by the thermal camera 530 does not pass through the control unit 510 and the thermal camera 530 receives commands related to operation from the monitoring server 560.

In some implementations, the system 500 includes one or more visible light cameras, which can operate similarly to the thermal camera 530, but detect light energy in the visible wavelength spectral bands. The one or more visible light cameras can perform various operations and functions within the property monitoring system 500. For example, the visible light cameras can capture images of one or more areas of the property, which the cameras, the control unit, and/or another computer system of the monitoring system 500 can process and analyze.

The system 500 also includes one or more property automation controls 522 that communicate with the control unit to perform monitoring. The property automation controls 522 are connected to one or more devices connected to the system 500 and enable automation of actions at the property. For instance, the property automation controls 522 may be connected to one or more lighting systems and may be configured to control operation of the one or more lighting systems. Also, the property automation controls 522 may be connected to one or more electronic locks at the property and may be configured to control operation of the one or more electronic locks (e.g., control Z-Wave locks using wireless communications in the Z-Wave protocol). Further, the property automation controls 522 may be connected to one or more appliances at the property and may be configured to control operation of the one or more appliances. The property automation controls 522 may include multiple modules that are each specific to the type of device being controlled in an automated manner. The property automation controls 522 may control the one or more devices based on commands received from the control unit 510. For instance, the property automation controls 522 may interrupt power delivery to a particular outlet of the property or induce movement of a smart window shade of the property.

The system 500 also includes thermostat 534 to perform dynamic environmental control at the property. The thermostat 534 is configured to monitor temperature and/or energy consumption of an HVAC system associated with the thermostat 534, and is further configured to provide control of environmental (e.g., temperature) settings. In some implementations, the thermostat 534 can additionally or alternatively receive data relating to activity at the property and/or environmental data at the home, e.g., at various locations indoors and outdoors at the property. The thermostat 534 can directly measure energy consumption of the HVAC system associated with the thermostat, or can estimate energy consumption of the HVAC system associated with the thermostat 534, for example, based on detected usage of one or more components of the HVAC system associated with the thermostat 534. The thermostat 534 can communicate temperature and/or energy monitoring information to or from the control unit 510 and can control the environmental (e.g., temperature) settings based on commands received from the control unit 510.

In some implementations, the thermostat 534 is a dynamically programmable thermostat and can be integrated with the control unit 510. For example, the dynamically programmable thermostat 534 can include the control unit 510, e.g., as an internal component to the dynamically programmable thermostat 534. In addition, the control unit 510 can be a gateway device that communicates with the dynamically programmable thermostat 534. In some implementations, the thermostat 534 is controlled via one or more property automation controls 522.

In some implementations, a module 537 is connected to one or more components of an HVAC system associated with the property, and is configured to control operation of the one or more components of the HVAC system. In some implementations, the module 537 is also configured to monitor energy consumption of the HVAC system components, for example, by directly measuring the energy consumption of the HVAC system components or by estimating the energy usage of the one or more HVAC system components based on detecting usage of components of the HVAC system. The module 537 can communicate energy monitoring information and the state of the HVAC system components to the thermostat 534 and can control the one or more components of the HVAC system based on commands received from the thermostat 534.

In some examples, the system 500 further includes one or more robotic devices 590. The robotic devices 590 may be any type of robot that are capable of moving and taking actions that assist in home monitoring. For example, the robotic devices 590 may include drones that are capable of moving throughout a property based on automated control technology and/or user input control provided by a user. In this example, the drones may be able to fly, roll, walk, or otherwise move about the property. The drones may include helicopter type devices (e.g., quad copters), rolling helicopter type devices (e.g., roller copter devices that can fly and/or roll along the ground, walls, or ceiling) and land vehicle type devices (e.g., automated cars that drive around a property). In some cases, the robotic devices 590 may be robotic devices 590 that are intended for other purposes and merely associated with the system 500 for use in appropriate circumstances. For instance, a robotic vacuum cleaner device may be associated with the monitoring system 500 as one of the robotic devices 590 and may be controlled to take action responsive to monitoring system events.

In some examples, the robotic devices 590 automatically navigate within a property. In these examples, the robotic devices 590 include sensors and control processors that guide movement of the robotic devices 590 within the property. For instance, the robotic devices 590 may navigate within the property using one or more cameras, one or more proximity sensors, one or more gyroscopes, one or more accelerometers, one or more magnetometers, a global positioning system (GPS) unit, an altimeter, one or more sonar or laser sensors, and/or any other types of sensors that aid in navigation about a space. The robotic devices 590 may include control processors that process output from the various sensors and control the robotic devices 590 to move along a path that reaches the desired destination and avoids obstacles. In this regard, the control processors detect walls or other obstacles in the property and guide movement of the robotic devices 590 in a manner that avoids the walls and other obstacles.

In addition, the robotic devices 590 may store data that describes attributes of the property. For instance, the robotic devices 590 may store a floorplan of a building on the property and/or a three-dimensional model of the property that enables the robotic devices 590 to navigate the property. During initial configuration, the robotic devices 590 may receive the data describing attributes of the property, determine a frame of reference to the data (e.g., a property or reference location in the property), and navigate the property based on the frame of reference and the data describing attributes of the property. Further, initial configuration of the robotic devices 590 also may include learning of one or more navigation patterns in which a user provides input to control the robotic devices 590 to perform a specific navigation action (e.g., fly to an upstairs bedroom and spin around while capturing video and then return to a home charging base). In this regard, the robotic devices 590 may learn and store the navigation patterns such that the robotic devices 590 may automatically repeat the specific navigation actions upon a later request.

In some examples, the robotic devices 590 may include data capture and recording devices. In these examples, the robotic devices 590 may include one or more cameras, one or more motion sensors, one or more microphones, one or more biometric data collection tools, one or more temperature sensors, one or more humidity sensors, one or more air flow sensors, and/or any other types of sensors that may be useful in capturing monitoring data related to the property and users at the property. The one or more biometric data collection tools may be configured to collect biometric samples of a person in the property with or without contact of the person. For instance, the biometric data collection tools may include a fingerprint scanner, a hair sample collection tool, a skin cell collection tool, and/or any other tool that allows the robotic devices 590 to take and store a biometric sample that can be used to identify the person (e.g., a biometric sample with DNA that can be used for DNA testing).

In some implementations, one or more of the thermal cameras 530 may be mounted on one or more of the robotic devices 590.

In some implementations, the robotic devices 590 may include output devices. In these implementations, the robotic devices 590 may include one or more displays, one or more speakers, and/or any type of output devices that allow the robotic devices 590 to communicate information to a nearby user.

The robotic devices 590 also may include a communication module that enables the robotic devices 590 to communicate with the control unit 510, each other, and/or other devices. The communication module may be a wireless communication module that allows the robotic devices 590 to communicate wirelessly. For instance, the communication module may be a Wi-Fi module that enables the robotic devices 590 to communicate over a local wireless network at the property. The communication module further may be a 900 MHz wireless communication module that enables the robotic devices 590 to communicate directly with the control unit 510. Other types of short-range wireless communication protocols, such as Bluetooth, Bluetooth LE, Z-wave, Zigbee, etc., may be used to allow the robotic devices 590 to communicate with other devices in the property. In some implementations, the robotic devices 590 may communicate with each other or with other devices of the system 500 through the network 505.

The robotic devices 590 further may include processor and storage capabilities. The robotic devices 590 may include any suitable processing devices that enable the robotic devices 590 to operate applications and perform the actions described throughout this disclosure. In addition, the robotic devices 590 may include solid state electronic storage that enables the robotic devices 590 to store applications, configuration data, collected sensor data, and/or any other type of information available to the robotic devices 590.

The robotic devices 590 can be associated with one or more charging stations. The charging stations may be located at predefined home base or reference locations at the property. The robotic devices 590 may be configured to navigate to the charging stations after completion of tasks needed to be performed for the monitoring system 500. For instance, after completion of a monitoring operation or upon instruction by the control unit 510, the robotic devices 590 may be configured to automatically fly to and land on one of the charging stations. In this regard, the robotic devices 590 may automatically maintain a fully charged battery in a state in which the robotic devices 590 are ready for use by the monitoring system 500.

The charging stations may be contact-based charging stations and/or wireless charging stations. For contact-based charging stations, the robotic devices 590 may have readily accessible points of contact that the robotic devices 590 are capable of positioning and mating with a corresponding contact on the charging station. For instance, a helicopter type robotic device 590 may have an electronic contact on a portion of its landing gear that rests on and mates with an electronic pad of a charging station when the helicopter type robotic device 590 lands on the charging station. The electronic contact on the robotic device 590 may include a cover that opens to expose the electronic contact when the robotic device 590 is charging and closes to cover and insulate the electronic contact when the robotic device is in operation.

For wireless charging stations, the robotic devices 590 may charge through a wireless exchange of power. In these cases, the robotic devices 590 need only locate themselves closely enough to the wireless charging stations for the wireless exchange of power to occur. In this regard, the positioning needed to land at a predefined home base or reference location in the property may be less precise than with a contact based charging station. Based on the robotic devices 590 landing at a wireless charging station, the wireless charging station outputs a wireless signal that the robotic devices 590 receive and convert to a power signal that charges a battery maintained on the robotic devices 590.

In some implementations, each of the robotic devices 590 has a corresponding and assigned charging station such that the number of robotic devices 590 equals the number of charging stations. In these implementations, the robotic devices 590 always navigate to the specific charging station assigned to that robotic device. For instance, a first robotic device 590 may always use a first charging station and a second robotic device 590 may always use a second charging station.

In some examples, the robotic devices 590 may share charging stations. For instance, the robotic devices 590 may use one or more community charging stations that are capable of charging multiple robotic devices 590. The community charging station may be configured to charge multiple robotic devices 590 in parallel. The community charging station may be configured to charge multiple robotic devices 590 in serial such that the multiple robotic devices 590 take turns charging and, when fully charged, return to a predefined home base or reference location in the property that is not associated with a charger. The number of community charging stations may be less than the number of robotic devices 590.

Also, the charging stations may not be assigned to specific robotic devices 590 and may be capable of charging any of the robotic devices 590. In this regard, the robotic devices 590 may use any suitable, unoccupied charging station when not in use. For instance, when one of the robotic devices 590 has completed an operation or is in need of battery charge, the control unit 510 references a stored table of the occupancy status of each charging station and instructs the robotic device 590 to navigate to the nearest charging station that is unoccupied.

The system 500 further includes one or more integrated security devices 580. The one or more integrated security devices may include any type of device used to provide alerts based on received sensor data. For instance, the one or more control units 510 may provide one or more alerts to the one or more integrated security input/output devices 580. Additionally, the one or more control units 510 may receive one or more sensor data from the sensors 520 and determine whether to provide an alert to the one or more integrated security input/output devices 580.

The sensors 520, the property automation controls 522, the thermal camera 530, the thermostat 534, and the integrated security devices 580 may communicate with the controller 512 over communication links 524, 526, 528, 532, and 584. The communication links 524, 526, 528, 532, and 584 may be a wired or wireless data pathway configured to transmit signals from the sensors 520, the property automation controls 522, the thermal camera 530, the thermostat 534, and the integrated security devices 580 to the controller 512. The sensors 520, the property automation controls 522, the thermal camera 530, the thermostat 534, and the integrated security devices 580 may continuously transmit sensed values to the controller 512, periodically transmit sensed values to the controller 512, or transmit sensed values to the controller 512 in response to a change in a sensed value.

The communication links 524, 526, 528, 532, and 584 may include a local network. The sensors 520, the property automation controls 522, the thermal camera 530, the thermostat 534, and the integrated security devices 580, and the controller 512 may exchange data and commands over the local network. The local network may include 802.11 “Wi-Fi” wireless Ethernet (e.g., using low-power Wi-Fi chipsets), Z-Wave, Zigbee, Bluetooth, “Homeplug” or other “Powerline” networks that operate over AC wiring, and a Category 5 (CAT5) or Category 6 (CAT6) wired Ethernet network. The local network may be a mesh network constructed based on the devices connected to the mesh network.

The monitoring server 560 is one or more electronic devices configured to provide monitoring services by exchanging electronic communications with the control unit 510, the one or more user devices 540 and 550, and the central alarm station server 570 over the network 505. For example, the monitoring server 560 may be configured to monitor events (e.g., alarm events) generated by the control unit 510. In this example, the monitoring server 560 may exchange electronic communications with the network module 514 included in the control unit 510 to receive information regarding events (e.g., alerts) detected by the control unit 510. The monitoring server 560 also may receive information regarding events (e.g., alerts) from the one or more user devices 540 and 550.

In some examples, the monitoring server 560 may route alert data received from the network module 514 or the one or more user devices 540 and 550 to the central alarm station server 570. For example, the monitoring server 560 may transmit the alert data to the central alarm station server 570 over the network 505.

The monitoring server 560 may store sensor data, thermal image data, and other monitoring system data received from the monitoring system and perform analysis of the sensor data, thermal image data, and other monitoring system data received from the monitoring system. Based on the analysis, the monitoring server 560 may communicate with and control aspects of the control unit 510 or the one or more user devices 540 and 550.

The monitoring server 560 may provide various monitoring services to the system 500. For example, the monitoring server 560 may analyze the sensor, thermal image, and other data to determine an activity pattern of a resident of the property monitored by the system 500. In some implementations, the monitoring server 560 may analyze the data for alarm conditions or may determine and perform actions at the property by issuing commands to one or more of the automation controls 522, possibly through the control unit 510.

The central alarm station server 570 is an electronic device configured to provide alarm monitoring service by exchanging communications with the control unit 510, the one or more mobile devices 540 and 550, and the monitoring server 560 over the network 505. For example, the central alarm station server 570 may be configured to monitor alerting events generated by the control unit 510. In this example, the central alarm station server 570 may exchange communications with the network module 514 included in the control unit 510 to receive information regarding alerting events detected by the control unit 510. The central alarm station server 570 also may receive information regarding alerting events from the one or more mobile devices 540 and 550 and/or the monitoring server 560.

The central alarm station server 570 is connected to multiple terminals 572 and 574. The terminals 572 and 574 may be used by operators to process alerting events. For example, the central alarm station server 570 may route alerting data to the terminals 572 and 574 to enable an operator to process the alerting data. The terminals 572 and 574 may include general-purpose computers (e.g., desktop personal computers, workstations, or laptop computers) that are configured to receive alerting data from a server in the central alarm station server 570 and render a display of information based on the alerting data. For instance, the controller 512 may control the network module 514 to transmit, to the central alarm station server 570, alerting data indicating that a sensor 520 detected motion from a motion sensor via the sensors 520. The central alarm station server 570 may receive the alerting data and route the alerting data to the terminal 572 for processing by an operator associated with the terminal 572. The terminal 572 may render a display to the operator that includes information associated with the alerting event (e.g., the lock sensor data, the motion sensor data, the contact sensor data, etc.) and the operator may handle the alerting event based on the displayed information.

In some implementations, the terminals 572 and 574 may be mobile devices or devices designed for a specific function. Although FIG. 5 illustrates two terminals for brevity, actual implementations may include more (and, perhaps, many more) terminals.

The one or more authorized user devices 540 and 550 are devices that host and display user interfaces. For instance, the user device 540 is a mobile device that hosts or runs one or more native applications (e.g., the smart home application 542). The user device 540 may be a cellular phone or a non-cellular locally networked device with a display. The user device 540 may include a cell phone, a smart phone, a tablet PC, a personal digital assistant (“PDA”), or any other portable device configured to communicate over a network and display information. For example, implementations may also include Blackberry-type devices (e.g., as provided by Research in Motion), electronic organizers, iPhone-type devices (e.g., as provided by Apple), iPod devices (e.g., as provided by Apple) or other portable music players, other communication devices, and handheld or portable electronic devices for gaming, communications, and/or data organization. The user device 540 may perform functions unrelated to the monitoring system, such as placing personal telephone calls, playing music, playing video, displaying pictures, browsing the Internet, maintaining an electronic calendar, etc.

The user device 540 includes a smart home application 542. The smart home application 542 refers to a software/firmware program running on the corresponding mobile device that enables the user interface and features described throughout. The user device 540 may load or install the smart home application 542 based on data received over a network or data received from local media. The smart home application 542 runs on mobile devices platforms, such as iPhone, iPod touch, Blackberry, Google Android, Windows Mobile, etc. The smart home application 542 enables the user device 540 to receive and process image and sensor data from the monitoring system.

The user device 550 may be a general-purpose computer (e.g., a desktop personal computer, a workstation, or a laptop computer) that is configured to communicate with the monitoring server 560 and/or the control unit 510 over the network 505. The user device 550 may be configured to display a smart home user interface 552 that is generated by the user device 550 or generated by the monitoring server 560. For example, the user device 550 may be configured to display a user interface (e.g., a web page) provided by the monitoring server 560 that enables a user to perceive images captured by the thermal camera 530 and/or reports related to the monitoring system. Although FIG. 5 illustrates two user devices for brevity, actual implementations may include more (and, perhaps, many more) or fewer user devices.

The smart home application 542 and the smart home user interface 552 can allow a user to interface with the property monitoring system 500, for example, allowing the user to view monitoring system settings, adjust monitoring system parameters, customize monitoring system rules, and receive and view monitoring system messages.

In some implementations, the one or more user devices 540 and 550 communicate with and receive monitoring system data from the control unit 510 using the communication link 538. For instance, the one or more user devices 540 and 550 may communicate with the control unit 510 using various local wireless protocols such as Wi-Fi, Bluetooth, Z-wave, Zigbee, HomePlug (ethernet over power line), or wired protocols such as Ethernet and USB, to connect the one or more user devices 540 and 550 to local security and automation equipment. The one or more user devices 540 and 550 may connect locally to the monitoring system and its sensors and other devices. The local connection may improve the speed of status and control communications because communicating through the network 505 with a remote server (e.g., the monitoring server 560) may be significantly slower.

Although the one or more user devices 540 and 550 are shown as communicating with the control unit 510, the one or more user devices 540 and 550 may communicate directly with the sensors 520 and other devices controlled by the control unit 510. In some implementations, the one or more user devices 540 and 550 replace the control unit 510 and perform the functions of the control unit 510 for local monitoring and long range/offsite communication.

In other implementations, the one or more user devices 540 and 550 receive monitoring system data captured by the control unit 510 through the network 505. The one or more user devices 540, 550 may receive the data from the control unit 510 through the network 505 or the monitoring server 560 may relay data received from the control unit 510 to the one or more user devices 540 and 550 through the network 505. In this regard, the monitoring server 560 may facilitate communication between the one or more user devices 540 and 550 and the monitoring system 500.

In some implementations, the one or more user devices 540 and 550 may be configured to switch whether the one or more user devices 540 and 550 communicate with the control unit 510 directly (e.g., through link 538) or through the monitoring server 560 (e.g., through network 505) based on a location of the one or more user devices 540 and 550. For instance, when the one or more user devices 540 and 550 are located close to the control unit 510 and in range to communicate directly with the control unit 510, the one or more user devices 540 and 550 use direct communication. When the one or more user devices 540 and 550 are located far from the control unit 510 and not in range to communicate directly with the control unit 510, the one or more user devices 540 and 550 use communication through the monitoring server 560.

Although the one or more user devices 540 and 550 are shown as being connected to the network 505, in some implementations, the one or more user devices 540 and 550 are not connected to the network 505. In these implementations, the one or more user devices 540 and 550 communicate directly with one or more of the monitoring system components and no network (e.g., Internet) connection or reliance on remote servers is needed.

In some implementations, the one or more user devices 540 and 550 are used in conjunction with only local sensors and/or local devices in a house. In these implementations, the system 500 includes the one or more user devices 540 and 550, the sensors 520, the property automation controls 522, the thermal camera 530, and the robotic devices 590. The one or more user devices 540 and 550 receive data directly from the sensors 520, the property automation controls 522, the thermal camera 530, and the robotic devices 590 (i.e., the monitoring system components) and sends data directly to the monitoring system components. The one or more user devices 540, 550 provide the appropriate interfaces/processing to provide visual surveillance and reporting.

In other implementations, the system 500 further includes network 505 and the sensors 520, the property automation controls 522, the thermal camera 530, the thermostat 534, and the robotic devices 59 are configured to communicate sensor and image data to the one or more user devices 540 and 550 over network 505 (e.g., the Internet, cellular network, etc.). In yet another implementation, the sensors 520, the property automation controls 522, the thermal camera 530, the thermostat 534, and the robotic devices 590 (or a component, such as a bridge/router) are intelligent enough to change the communication pathway from a direct local pathway when the one or more user devices 540 and 550 are in close physical proximity to the sensors 520, the property automation controls 522, the thermal camera 530, the thermostat 534, and the robotic devices 590 to a pathway over network 505 when the one or more user devices 540 and 550 are farther from the sensors 520, the property automation controls 522, the thermal camera 530, the thermostat 534, and the robotic devices 590. In some examples, the system leverages GPS information from the one or more user devices 540 and 550 to determine whether the one or more user devices 540 and 550 are close enough to the monitoring system components to use the direct local pathway or whether the one or more user devices 540 and 550 are far enough from the monitoring system components that the pathway over network 505 is required. In other examples, the system leverages status communications (e.g., pinging) between the one or more user devices 540 and 550 and the sensors 520, the property automation controls 522, the thermal camera 530, the thermostat 534, and the robotic devices 590 to determine whether communication using the direct local pathway is possible. If communication using the direct local pathway is possible, the one or more user devices 540 and 550 communicate with the sensors 520, the property automation controls 522, the thermal camera 530, the thermostat 534, and the robotic devices 590 using the direct local pathway. If communication using the direct local pathway is not possible, the one or more user devices 540 and 550 communicate with the monitoring system components using the pathway over network 505.

In some implementations, the system 500 provides end users with access to thermal images captured by the thermal camera 530 to aid in decision making. The system 500 may transmit the thermal images captured by the thermal camera 530 over a wireless WAN network to the user devices 540 and 550. Because transmission over a wireless WAN network may be relatively expensive, the system 500 can use several techniques to reduce costs while providing access to significant levels of useful visual information (e.g., compressing data, down-sampling data, sending data only over inexpensive LAN connections, or other techniques).

In some implementations, a state of the monitoring system and other events sensed by the monitoring system may be used to enable/disable video/image recording devices (e.g., the thermal camera 530 or other cameras of the system 500). In these implementations, the thermal camera 530 may be set to capture thermal images on a periodic basis when the alarm system is armed in an “armed away” state, but set not to capture images when the alarm system is armed in an “armed stay” or “unarmed” state. In addition, the thermal camera 530 may be triggered to begin capturing thermal images when the alarm system detects an event, such as an alarm event, a door-opening event for a door that leads to an area within a field of view of the thermal camera 530, or motion in the area within the field of view of the thermal camera 530. In other implementations, the thermal camera 530 may capture images continuously, but the captured images may be stored or transmitted over a network when needed.

The described systems, methods, and techniques may be implemented in digital electronic circuitry, computer hardware, firmware, software, or in combinations of these elements. Apparatus implementing these techniques may include appropriate input and output devices, a computer processor, and a computer program product tangibly embodied in a machine-readable storage device for execution by a programmable processor. A process implementing these techniques may be performed by a programmable processor executing a program of instructions to perform desired functions by operating on input data and generating appropriate output. The techniques may be implemented in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device. Each computer program may be implemented in a high-level procedural or object-oriented programming language, or in assembly or machine language if desired; and in any case, the language may be a compiled or interpreted language. Suitable processors include, by way of example, both general and special purpose microprocessors. Generally, a processor will receive instructions and data from a read-only memory and/or a random-access memory. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and Compact Disc Read-Only Memory (CD-ROM). Any of the foregoing may be supplemented by, or incorporated in, specially designed ASICs (application-specific integrated circuits).