Abstract: A method of monitoring or controlling electronic devices and monitoring enclosures in which the electronic devices are installed includes receiving data related to one or more electronic devices registered with a device management system and associated with a user account; and generating a user interface for monitoring or controlling the conditions from a computing device. The user interface may include an image of a first enclosure that is associated with the user account; images of first one or more electronic devices in the one or more electronic devices that are installed in the first enclosure; and current conditions displayed on each of the images of the first one or more electronic devices reflecting aspects of the first enclosure that are controlled or monitored by the first one or more electronic devices.

Abstract: A method of monitoring or controlling electronic devices and monitoring enclosures in which the electronic devices are installed includes receiving data related to one or more electronic devices registered with a device management system and associated with a user account; and generating a user interface for monitoring or controlling the conditions from a computing device. The user interface may include an image of a first enclosure that is associated with the user account; images of first one or more electronic devices in the one or more electronic devices that are installed in the first enclosure; and current conditions displayed on each of the images of the first one or more electronic devices reflecting aspects of the first enclosure that are controlled or monitored by the first one or more electronic devices.

Abstract: A device management system facilitates an automatic pairing of an electronic device with a management account. The device management system receives a public network address associated with a computer device on a private network accessing the management account. The system retrieves the metadata including a public network address associated with a registration of the electronic device with the device management system. The public network address registered with the metadata is provided by a router on the private network and therefore should match the public network address used by computer devices on the private network. The management account is paired with the electronic device if the electronic device has the same public network address as the computer device accessing the management account. Pairing the management account to the electronic device allows the management account to communicate with the electronic device over the public network through the device management system.

Abstract: A thermostat may include one or more temperature sensors, a processor configured to operate in a sleep mode and a wake mode, and a Wi-Fi chip that wirelessly communicates with a thermostat management server. The Wi-Fi chip may be configured to receive data packets from the thermostat management server while the processor operates in the sleep mode, and determine a priority level of the received data packets. The priority level may include a standard priority level and a keep-alive priority level. The Wi-Fi chip may also be configured to filter the received data packets based on the determined priority level of each packet such that the keep-alive priority level packets are discarded, and forward the standard priority level packets to the processor.

Abstract: A device management system facilitates an automatic pairing of an electronic device with a management account. The device management system receives a public network address associated with a computer device on a private network accessing the management account. The system retrieves the metadata including a public network address associated with a registration of the electronic device with the device management system. The public network address registered with the metadata is provided by a router on the private network and therefore should match the public network address used by computer devices on the private network. The management account is paired with the electronic device if the electronic device has the same public network address as the computer device accessing the management account. Pairing the management account to the electronic device allows the management account to communicate with the electronic device over the public network through the device management system.

Abstract: A thermostat management system facilitates an automatic pairing of a thermostat with a thermostat communication account. The thermostat management system receives a public network address associated with a computer device on a private network accessing the thermostat management account. The system retrieves the thermostat metadata including a public network address associated with a registration of the thermostat with the thermostat management system. The public network address registered with the thermostat metadata is provided by a router on the private network and therefore should match the public network address used by computer devices on the private network. The thermostat management account is paired with the thermostat if the thermostat has the same public network address as the computer device accessing the thermostat management account.

Abstract: A thermostat may include one or more temperature sensors, a processor configured to operate in a sleep mode and a wake mode, and a Wi-Fi chip that wirelessly communicates with a thermostat management server. The Wi-Fi chip may be configured to receive data packets from the thermostat management server while the processor operates in the sleep mode, and determine a priority level of the received data packets. The priority level may include a standard priority level and a keep-alive priority level. The Wi-Fi chip may also be configured to filter the received data packets based on the determined priority level of each packet such that the keep-alive priority level packets are discarded, and forward the standard priority level packets to the processor.

Abstract: Aspects of the present invention provide energy conserving communications for networked thermostats powered, in part, by batteries. A thermostat communication server stores a thermostat battery-level to determine what data should be sent to the thermostat. The thermostat communication server classifies types of data to be transmitted to the thermostat according to a data priority ranging from a low-priority to a high-priority data type. If the battery-level associated with the battery on the thermostat is at a low battery-level, the thermostat communication server may only transmit data classified under a high-priority data type. This conserves the power used by the thermostat, allows the battery on the thermostat time to recharge and perform other functions. If the battery-level of the thermostat is at a high level, the thermostat communication server may transmit a range of data to the thermostat classified from a low-priority type to a high-priority data type.

Abstract: A thermostat management system facilitates an automatic pairing of a thermostat with a thermostat communication account. The thermostat management system receives a public network address associated with a computer device on a private network accessing the thermostat management account. The system retrieves the thermostat metadata including a public network address associated with a registration of the thermostat with the thermostat management system. The public network address registered with the thermostat metadata is provided by a router on the private network and therefore should match the public network address used by computer devices on the private network. The thermostat management account is paired with the thermostat if the thermostat has the same public network address as the computer device accessing the thermostat management account.

Abstract: A thermostat management system facilitates an automatic pairing of a thermostat with a thermostat communication account. The thermostat management system receives a public network address associated with a computer device on a private network accessing the thermostat management account. The system retrieves the thermostat metadata including a public network address associated with a registration of the thermostat with the thermostat management system. The public network address registered with the thermostat metadata is provided by a router on the private network and therefore should match the public network address used by computer devices on the private network. The thermostat management account is paired with the thermostat if the thermostat has the same public network address as the computer device accessing the thermostat management account.

Abstract: Aspects of the present invention provide energy conserving communications for networked thermostats powered, in part, by batteries. A thermostat communication server stores a thermostat battery-level to determine what data should be sent to the thermostat. The thermostat communication server classifies types of data to be transmitted to the thermostat according to a data priority ranging from a low-priority to a high-priority data type. If the battery-level associated with the battery on the thermostat is at a low battery-level, the thermostat communication server may only transmit data classified under a high-priority data type. This conserves the power used by the thermostat, allows the battery on the thermostat time to recharge and perform other functions. If the battery-level of the thermostat is at a high level, the thermostat communication server may transmit a range of data to the thermostat classified from a low-priority type to a high-priority data type.

Abstract: A method and apparatus for providing information by merging of an arbitrarily shaped data source with an arbitrary display hierarchy, including binding data in a source data file to application or content code. In one embodiment, the data source is an XML data file and the application is a rich Internet application provided by a presentation server. The method includes the steps of providing a structured data file; and merging the structured data file with a source file, the source file including at least one display element definition including an expression that refers to an arbitrary position or range within the data file. In another aspect, the invention is an apparatus. The apparatus includes one or more storage devices, and one or more processors in communication with said one or more storage devices.

Abstract: A server is disclosed that presents content to a client. The server receives a request for particular content. In response to the request, the server accesses data and/or code that describes the particular content. The server compiles that code and/or data to create executable code, and transmits the executable code to the client for execution on the client. In one embodiment, the code describing the particular content is a mark-up language description. In various implementations, the executable code includes a user interface that provides access to the requested content.

Abstract: The present invention provides software developers with the capability to create applications that can access information online and offline without having to program such capabilities into their applications. An application can gather information from various remote data sources via a network or other communication means, and still have access to all or a portion of that information when the computing device running the application is no longer connected to the network. In one embodiment, a client manages information access, caching and synchronization for the application. When connected, information accessed is stored in a local data store on (or near) the computing device. When disconnected, requests are run against the local data store instead of the remote data source. When reconnected, information is synchronized between the local data store and the remote data source.

Abstract: A method for decreasing a computer application's start-up time. In one aspect, the method comprises: creating a serialized representation of application objects in a runtime environment; building an object code file using the serialized representation; and providing the application to a new runtime environment. In another embodiment the method may include the steps of: compiling an application provided in a source language; initializing the application in a runtime environment; and creating a serialized representation of the application.

Abstract: The present invention provides software developers with the capability to create applications that can access information online and offline without having to program such capabilities into their applications. An application can gather information from various remote data sources via a network or other communication means, and still have access to all or a portion of that information when the computing device running the application is no longer connected to the network. In one embodiment, a client manages information access, caching and synchronization for the application. When connected, information accessed is stored in a local data store on (or near) the computing device. When disconnected, requests are run against the local data store instead of the remote data source. When reconnected, information is synchronized between the local data store and the remote data source.

Abstract: Code for a program is received by a compiler (or other entity). The code includes an expression for a variable and a marker that specifies when the expressions should be evaluated during execution of the program. Example markers can indicate that an expression should be evaluated immediately, once or always. Additional functionality is provided to the code in order to evaluate the expression at the specified time during execution of the program. If the expression is to be evaluated always, then the expression will likely be dependent on a item that can change. Functionality is provided that evaluates the expression when the item changes so that the variable can be updated.

Abstract: The present invention provides software developers with the capability to create applications that can access information online and offline without having to program such capabilities into their applications. An application can gather information from various remote data sources via a network or other communication means, and still have access to all or a portion of that information when the computing device running the application is no longer connected to the network. In one embodiment, a client manages information access, caching and synchronization for the application. When connected, information accessed is stored in a local data store on (or near) the computing device. When disconnected, requests are run against the local data store instead of the remote data source. When reconnected, information is synchronized between the local data store and the remote data source.

Abstract: A server is disclosed that presents content to a client. The server receives a request for particular content. In response to the request, the server accesses data and/or code that describes the particular content. The server compiles that code and/or data to create executable code, and transmits the executable code to the client for execution on the client. In one embodiment, the code describing the particular content is a mark-up language description. In various implementations, the executable code includes a user interface that provides access to the requested content.

Abstract: The present invention provides software developers with the capability to create applications that can access information online and offline without having to program such capabilities into their applications. An application can gather information from various remote data sources via a network or other communication means, and still have access to all or a portion of that information when the computing device running the application is no longer connected to the network. In one embodiment, a client manages information access, caching and synchronization for the application. When connected, information accessed is stored in a local data store on (or near) the computing device. When disconnected, requests are run against the local data store instead of the remote data source. When reconnected, information is synchronized between the local data store and the remote data source.