Difference between revisions of "Everspring SP103"
From LinuxMCE
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Category: Hardware]] | ||
{{versioninfo|810Status=According to category, Works without caveats|810UpdatedDate=11th May 2010|810UpdatedBy=[[User:Wierdbeard65|Wierdbeard65]]|}} | {{versioninfo|810Status=According to category, Works without caveats|810UpdatedDate=11th May 2010|810UpdatedBy=[[User:Wierdbeard65|Wierdbeard65]]|}} | ||
[[Category: RF Control]] | [[Category: RF Control]] | ||
| Line 20: | Line 21: | ||
= Setup = | = Setup = | ||
== In a nutshell == | == In a nutshell == | ||
| − | : 1 | + | : Step 1: Addition/Inclusion of motion sensor to ZWave network |
| − | : 2 | + | : Step 2: Association of motion sensor via LinuxMCE WebUI |
== Addition/Inclusion == | == Addition/Inclusion == | ||
| Line 29: | Line 30: | ||
: 4. Complete inclusion process by inserting batteries in motion sensor | : 4. Complete inclusion process by inserting batteries in motion sensor | ||
: 5. Plug ZWave controller back to LinuxMCE Core | : 5. Plug ZWave controller back to LinuxMCE Core | ||
| + | |||
| + | == Association == | ||
| + | : 1. Collect data from your ZWave controler needed for association | ||
| + | :: 1.1. Advanced -> Configuration -> Devices | ||
| + | :: 1.2. In left windows scroll down to ZWave and click on '''ZWave Controller''' | ||
| + | :: 1.3. Read Port/Channel Number, in my case "1" | ||
| + | : 2. Associate Motion sensor | ||
| + | :: 2.1. Wizard -> Devices -> Interfaces | ||
| + | :: 2.2. Click '''Advanced''' button for ZWave device with Device Template #: 1754 | ||
| + | :: 2.3. Click '''Send command to device''' | ||
| + | :: 2.4. Select '''Set Association" from drop down menu | ||
= Command Classes = | = Command Classes = | ||
Latest revision as of 16:34, 28 September 2010
| Version | Status | Date Updated | Updated By |
|---|---|---|---|
| 710 | Unknown | N/A | N/A |
| 810 | According to category, Works without caveats | 11th May 2010 | Wierdbeard65 |
| 1004 | Unknown | N/A | N/A |
| 1204 | Unknown | N/A | N/A |
| 1404 | Unknown | N/A | N/A |
| Usage Information | |||
Contents
Status
Tested (and working) with the latest svn Z-Wave driver (will be included in 0810).
The Everspring SP103 is a basic PIR supporting on/off. One of the disadvantages is the energy consumpton "Eats batteries like there is no tomorrow"
About
The Everspring SP103 is a battery powered Z-Wave PIR sensor. It uses a frequency of 868MHz. There is also a US version.
Manuf ID1: 0x0 ID2: 0x60, Prod Typ1: 0x2 Typ2: 0x2, Prod ID1: 0x0 ID2: 0x1
Setup
In a nutshell
- Step 1: Addition/Inclusion of motion sensor to ZWave network
- Step 2: Association of motion sensor via LinuxMCE WebUI
Addition/Inclusion
- 1. Remove batteries from motion sensor
- 2. Unplug USB ZWave controller from Core
- 3. Put ZWave controller into inclusion mode
- 4. Complete inclusion process by inserting batteries in motion sensor
- 5. Plug ZWave controller back to LinuxMCE Core
Association
- 1. Collect data from your ZWave controler needed for association
- 1.1. Advanced -> Configuration -> Devices
- 1.2. In left windows scroll down to ZWave and click on ZWave Controller
- 1.3. Read Port/Channel Number, in my case "1"
- 2. Associate Motion sensor
- 2.1. Wizard -> Devices -> Interfaces
- 2.2. Click Advanced button for ZWave device with Device Template #: 1754
- 2.3. Click Send command to device
- 2.4. Select Set Association" from drop down menu
Command Classes
- BASIC_TYPE_ROUTING_SLAVE
- GENERIC_TYPE_SENSOR_BINARY
Supports
- COMMAND_CLASS_SENSOR_BINARY
- COMMAND_CLASS_WAKE_UP
- COMMAND_CLASS_ASSOCIATION
- COMMAND_CLASS_CONFIGURATION
- COMMAND_CLASS_BATTERY
- COMMAND_CLASS_MANUFACTURER_SPECIFIC
- COMMAND_CLASS_VERSION
Controls
- COMMAND_CLASS_BASIC
