User interface in a premises network
摘要
說明書
As an example, the time intervals of an embodiment allow users to ‘zoom’ in and out of timeframes to see different timescale. The embodiment minimizes server calls and provides a ‘snappy’ interface on the client (each screen displays within two (2) seconds, even if all data is not yet present). The following timespans of information are presented as examples, but the embodiment is not so limited: system (alarm events) include, but are not limited to, 6 hours, 1 day, 3 days, 1 week (e.g., loaded and cached at idle time except 6-hour period which is updated as needed; screen should pop up with latest information, and once latest 6 hour time period is updated it then refreshes); camera data timespans include, but are not limited to, 6 hours, 1 day, 3 days, 1 week (e.g., last 6 hours of actual clips should be pre-loaded) (data indicating clips, pictures should be loaded and cached like system events); thermostat data timespans include, but are not limited to, 6 hours, 1 day, 3 days, 1 week, and thermostat data plot points are pre-loaded.
A “CAMERAS” screen allows the user to view live and archived pictures and video from all cameras on a network. The user can view live video from different cameras in a multi-camera system by tapping the left/right arrows in the bar at the top of the video feed. The user can also flick left/right to navigate between cameras. A page indicator shows the currently visible camera.
