From OpenHome
(→Node manufacturer benefits) |
(→Node manufacturer benefits) |
||
| Line 35: | Line 35: | ||
* providing a protocol-independent framework from which to build the communications hardware most | * providing a protocol-independent framework from which to build the communications hardware most | ||
suited to each manufacturer | suited to each manufacturer | ||
| + | * point 2 | ||
| + | * point 3 | ||
Revision as of 11:28, 29 February 2012
Contents |
Introduction
This document provides a technical overview of the ohWidget home automation system and details about the physical architecture it uses. It introduces the concepts, terminology and interactions of each component of an ohWidget system.
This document does not provide low-level technical information such as hardware specifications of the Nodes nor code examples from the ohWidget API.
ohWidget
ohWidget makes use of three distinct components: Widgets, Control Points and Nodes. This document uses these three terms heavily throughout and are defined simply as follows:
Widget
Any device in an end-user's home that can be remotely controlled. Widgets can range in complexity from simple single-service lights to multi-service audio/visual devices.
Control Point
A device used by the end-user to access the services provided by each Widget.
Node
The device used to aggregate devices and services published by Widgets, for quick and easy access by Control Points.
Together these three classes of device can be used in any number to create an ohWidget home automation system.
Node manufacturer benefits
ohWidget supports Node manufacturers by:
- providing a protocol-independent framework from which to build the communications hardware most
suited to each manufacturer
- point 2
- point 3