diff --git a/README.md b/README.md index ea74449..4e8c789 100644 --- a/README.md +++ b/README.md @@ -3,11 +3,16 @@ node-openzwave This is a node.js add-on which wraps the [Open Z-Wave](https://code.google.com/p/open-zwave/) library to provide access to a -Z-Wave network from JavaScript. +Z-Wave network from [Node.JS](https://nodejs.org) (server-side JavaScript.) It is currently able to scan a Z-Wave network, report on connected devices, monitor the network for changes, and has rudimentary write support. +## NOTE: +this is essentially [a fork from jperkin's work](https://github.com/jperkin/node-openzwave) +so all the credit is due to him, not me, I (ekarak) only added support for +multi-instance ZWave devices (eg the Fibaro FGS-221). + ## Install The module currently builds only on OS X and Linux. On Linux you will need to @@ -71,9 +76,15 @@ zwave.switchOff(nodeid); /* * Set arbitrary values. */ -zwave.setValue(nodeid, commandclass, index, value); +zwave.setValue(nodeid, commandclass, index, instance, value); +``` +This is useful for multi-instance devices, such as the Fibaro FGS-221 eg: +```js +zwave.setValue(8, 37, 0, 1, true); // turn on 1st output relay +zwave.setValue(8, 37, 0, 2, true); // turn on 2nd output relay ``` + Writing to device metadata (stored on the device itself): ```js diff --git a/deps/open-zwave/INSTALL b/deps/open-zwave/INSTALL new file mode 100644 index 0000000..cb59066 --- /dev/null +++ b/deps/open-zwave/INSTALL @@ -0,0 +1,82 @@ +Minimal Install Guide for OpenZWave! + +For Unix's (including Mac, bsd's etc) +================= +execute Make in the Top Level Directory +make + +Libraries to link to (Static and Dynamic) will be in top level directory as +well (but you can change that as detailed below with LIBDIR) + +To Install: +make install + +Some Options you can set: +"BUILD=(release|debug)" - Build a Release or Debug Version of the Library +(Release is default) + +"PREFIX=(path)" - Prefix to install the shared library into - Defaults to +/usr/local + +"LIBDIR=/tmp" - Path to place the libraries into after complication. A poor +mans "make install" for simple Applications. + +To use the options, specify them on the commandline when executing make eg: +"BUILD=debug PREFIX=/opt/local make" + +What Gets installed: +When make install is called the following happens: + +* Documentation: + if you have DoxyGen, API documentation is installed into + (PREFIX)/share/doc/openzwave-(version)/ + +* Shared Libary (libopenzwave.so.*): + The Shared Library is installed into either (prefix)/lib64 (on 64 + bit platforms) or (prefix)/lib/ on 32 bit platforms) + +* Header Files: + Installed into (prefix)/include/openzwave/ + +* pkg-config file: + Installed into (prefix)/lib(64)/pkgconfig/libopenzwave.pc + +* Config files and Device Databases (manufacturer_specific.xml et al) + Installed into (prefix)/etc/openzwave/ + +* MinOZW example program: + Installed into (prefix)/bin/ directory + +The Static Version of the library is never installed, but will be created in +cpp/lib directory after a successfull make. + +Windows Versions +================ + +Visual Studio Solution Files and Mingw32 Makefiles are present in +cpp/build/windows/. Select the correct Visual Studio or Mingw32 directory +depending on the versions you have. + +(Note, if building DLL's on Windows (currently a option in the vs2010 +solution) - You have to ensure you application is compiled with exactly the +same compiler options and versions as OpenZWave - Otherwise strange things +might happen) + +For the .NET dll, the solution files exist in the dotnet/build/ directory + +Sample Programs +=============== + +For all platforms, there is a simple example program that will print out +events as they happen on your ZWave network. This sample is called MinOZW +and you can find the source in the cpp/examples directory. By default, these +examples are built during the Make Install Stage. If you want compile them +separately, you can use the "make examples" target. + +For the .NET wrapper, there is a OZWForm application in +dotnet/examples/OZWForm/. Please read the README file in that directory for +further instructions + + + + diff --git a/deps/open-zwave/config/BeNext/1poleswitch.xml b/deps/open-zwave/config/BeNext/1poleswitch.xml new file mode 100644 index 0000000..7ecc03c --- /dev/null +++ b/deps/open-zwave/config/BeNext/1poleswitch.xml @@ -0,0 +1,35 @@ + + + + + + + + Set all configuration values to default values (factory settings). + + + + The mode in which a different Z-Wave message is sent. + + + + The time that a user has to activate the double button pressed scene, if time is passed then the single pressed button scene is notified. (value * 10 ms) + + + + A signed integer to determine the offset of the temperature. + + + + + + + + + + + + + + + diff --git a/deps/open-zwave/config/BeNext/2poleswitch.xml b/deps/open-zwave/config/BeNext/2poleswitch.xml new file mode 100644 index 0000000..f3e31a7 --- /dev/null +++ b/deps/open-zwave/config/BeNext/2poleswitch.xml @@ -0,0 +1,35 @@ + + + + + + + + Set all configuration values to default values (factory settings). + + + + The mode in which a different Z-Wave message is sent. + + + + The time that a user has to activate the double button pressed scene, if time is passed then the single pressed button scene is notified. (value * 10 ms) + + + + A signed integer to determine the offset of the temperature. + + + + + + + + + + + + + + + diff --git a/deps/open-zwave/config/BeNext/AlarmSound.xml b/deps/open-zwave/config/BeNext/AlarmSound.xml new file mode 100644 index 0000000..ca8e1a1 --- /dev/null +++ b/deps/open-zwave/config/BeNext/AlarmSound.xml @@ -0,0 +1,62 @@ + + + + + + + + + Set all configuration values to default values (factory settings) + + + Enables an internal routine that periodically checks the Z-Wave device in assocication group 2 + + + Configure the time that the AlarmSound sends a new frame when previous frame was send successful + + + Configure the time that the AlarmSound sends a few frame when previous frame was send not successful + + + A (signed) offset to calibrate the onboard temperature sensor + + + A (signed) offset to calibrate the onboard temperature sensor + + + The index of the sound mode when a switch binary/basic set frame is received + + + The index of the sound mode when the AlarmSound will start when it is unplugged + + + The index of the sound mode when the AlarmSound will play when it is unable to reach the device in association group 2 + + + Params 10 until 27 are the values to configure the sound and light thtat are played when index 1 is selected + + + Params 28 until 45 are the values to configure the sound and light thtat are played when index 2 is selected + + + Params 46 until 63 are the values to configure the sound and light thtat are played when index 3 is selected + + + Params 64 until 81 are the values to configure the sound and light thtat are played when index 4 is selected + + + Params 82 until 99 are the values to configure the sound and light thtat are played when index 5 is selected + + + Params 100 until 117 are the values to configure the sound and light thtat are played when index 6 is selected + + + + + + + + + + + diff --git a/deps/open-zwave/config/BeNext/BuiltinDimmer.xml b/deps/open-zwave/config/BeNext/BuiltinDimmer.xml new file mode 100644 index 0000000..791daee --- /dev/null +++ b/deps/open-zwave/config/BeNext/BuiltinDimmer.xml @@ -0,0 +1,77 @@ + + + + + + + + Set all configuration values to default values (factory settings). + + + + The way how the button reacts when press/released + + + + + + + The way the Built-in Dimmer reacts when light is turned on/off with button + + + + + + This parameter is used to enable the dimming option of the product. When disabled the dimming and fading routine are disabled. + + + + + + The maximum powerload in watts when light is turned on, when measured higher then this value the Inline Dimmer is automatically turned off. + + + + The speed of dimming when activated (manual and RF). Dim speed is 1% per value (* 10 ms) + + + + The speed of fading up when activated (manual and RF). Fade speed is 1% per value (* 10 ms) + + + + The time window to repress button to start dimming. Toggle time is value (* 10ms) + + + + A percentage that an energy value must be different compared to a previous sent value before an unsolicited meter report is sent. Minimum value = 10% Maximum value = 100% + + + + A watt value that an energy value must be different compared to a previous sent value before an unsolicited meter report is sent. Minimum value = 5 watt Maximum value = 255 watt + + + + A time value that has to be passed compared to a previous sent value before a unsolicited meter report is sent. Minimum value = 10 seconds Maximum value = 255 seconds + + + + What to do with lamp status when power applied. If 0x00: Always switch light off when power applied. If > 0x00: Switch lamp on/off depending on last known lampstatus before power was disconnected. + + + + The speed of fading up when activated (manual and RF). Fade speed is 1% per value (* 10 ms) + + + + + + + + + + + + + + diff --git a/deps/open-zwave/config/BeNext/DoorSensor.xml b/deps/open-zwave/config/BeNext/DoorSensor.xml index f29b13a..c0a5b75 100644 --- a/deps/open-zwave/config/BeNext/DoorSensor.xml +++ b/deps/open-zwave/config/BeNext/DoorSensor.xml @@ -27,6 +27,10 @@ + + + A signed integer to determine the offset of the temperature. + diff --git a/deps/open-zwave/config/BeNext/Molite.xml b/deps/open-zwave/config/BeNext/Molite.xml new file mode 100644 index 0000000..5bf075b --- /dev/null +++ b/deps/open-zwave/config/BeNext/Molite.xml @@ -0,0 +1,33 @@ + + + + + + + Set all configuration values to default values (factory settings). + + + The time used in mode 2 to turn the sensor off. This Time will start running as soon as detection is seen. + + + The switch off time will start running as soon as mode timeout is done. Motion sensor is turned on and when movement is detected again the mode timeout (cfg param 1) will start running all over again. When switch off time is done a basic off message is sent to the associated node. + + + Sensitivity value between 0 and 127 (values above 127 will be reported as the set value but will be handled in SW as 127). + + + The mode that is entered after detection. If mode is 0 or higher then 3, that value will be reported after a get but will be handled in SW as mode 2. + + + + + + + + + + + + + + diff --git a/deps/open-zwave/config/BeNext/PluginDimmer.xml b/deps/open-zwave/config/BeNext/PluginDimmer.xml new file mode 100644 index 0000000..081bf8d --- /dev/null +++ b/deps/open-zwave/config/BeNext/PluginDimmer.xml @@ -0,0 +1,66 @@ + + + + + + + + Set all configuration values to default values (factory settings). + + + + The way the Built-in Dimmer reacts when light is turned on/off with button + + + + + + This parameter is used to enable the dimming option of the product. When disabled the dimming and fading routine are disabled. + + + + + + The maximum powerload in watts when light is turned on, when measured higher then this value the Inline Dimmer is automatically turned off. + + + + The speed of dimming when activated (manual and RF). Dim speed is 1% per value (* 10 ms) + + + + The speed of fading up when activated (manual and RF). Fade speed is 1% per value (* 10 ms) + + + + A percentage that an energy value must be different compared to a previous sent value before an unsolicited meter report is sent. Minimum value = 10% Maximum value = 100% + + + + A watt value that an energy value must be different compared to a previous sent value before an unsolicited meter report is sent. Minimum value = 5 watt Maximum value = 255 watt + + + + A time value that has to be passed compared to a previous sent value before a unsolicited meter report is sent. Minimum value = 10 seconds Maximum value = 255 seconds + + + + What to do with lamp status when power applied. If 0x00: Always switch light off when power applied. If > 0x00: Switch lamp on/off depending on last known lampstatus before power was disconnected. + + + + The speed of fading up when activated (manual and RF). Fade speed is 1% per value (* 10 ms) + + + + + + + + + + + + + + diff --git a/deps/open-zwave/config/aeon_labs/doorwindow.xml b/deps/open-zwave/config/aeon_labs/doorwindow.xml index 871c468..5742762 100644 --- a/deps/open-zwave/config/aeon_labs/doorwindow.xml +++ b/deps/open-zwave/config/aeon_labs/doorwindow.xml @@ -1,13 +1,47 @@ - - - - - - - - - + + + + 0, Open: FF, Close: 00; 1, Open: 00, Close: FF + Default setting: 0 + + + + 0: Disable; 1: Enable + Default setting: 0 + + + + 0, Open: FF, Close: 00; 1, Open: 00, Close: FF; + Default setting: 0 + + + + Which reports need to send automatically in timing intervals for group 1 + Bitsets: + 0 -> Battery report + 4 -> Sensor Binary + 8 -> Basic Set + Default setting: 0x00000100 (Basic Set) + + + + Device Tag + + + Reset to factory defaults. + + + + + + + + + + + + diff --git a/deps/open-zwave/config/aeon_labs/hemg2.xml b/deps/open-zwave/config/aeon_labs/hemg2.xml new file mode 100644 index 0000000..aa75505 --- /dev/null +++ b/deps/open-zwave/config/aeon_labs/hemg2.xml @@ -0,0 +1,177 @@ + + + + + + + If the reverse clamping pliers, negative power is detected. + + + + + + + Automatic report only when power is changed. + + + + + + + Threshold change in wattage to induce a automatic report (whole HEM). + + + + + Threshold change in wattage to induce a automatic report (Clamp 1). + + + + + Threshold change in wattage to induce a automatic report (Clamp 2). + + + + + Threshold change in wattage to induce a automatic report (Clamp 3). + + + + + Percentage change in wattage to induce a automatic report (whole HEM). + + + + + Percentage change in wattage to induce a automatic report (Clamp 1). + + + + + Percentage change in wattage to induce a automatic report (Clamp 2). + + + + + Percentage change in wattage to induce a automatic report (Clamp 3). + + + + + Reset to default parameters number 101-103. Any value other then 0 will initiate this reset. + + + + + Which reports need to send in group1. Format is as follows: + Byte 1 (msb): Reserved + Byte 2: Reserved + Byte 3: Bit 7: reserved + Bit 6: reserved + Bit 5: Auto Send Meter Report (for kWh) at the group time interval (Clamp 3) + Bit 4: Auto Send Meter Report (for kWh) at the group time interval (Clamp 2) + Bit 3: Auto Send Meter Report (for kWh) at the group time interval (Clamp 1) + Bit 2: Auto Send Meter Report (for watts) at the group time interval (Clamp 3) + Bit 1: Auto Send Meter Report (for watts) at the group time interval (Clamp 2) + Bit 0: Auto Send Meter Report (for watts) at the group time interval (Clamp 1) + Byte 4 (lsb): Bit 7: reserved + Bit 6: reserved + Bit 5: reserved + Bit 4: reserved + Bit 3: Auto Send Meter Report (for kWh) at the group time interval (whole HEM) + Bit 2: Auto Send Meter Report (for watts) at the group time interval (whole HEM) + Bit 1: Auto Send Multilevel Sensor Report (for watts) at the group time interval (whole HEM) + Bit 0: Auto Send Battery Report at the group time interval (whole HEM) + + + + + Which reports need to send in group2. Format is as follows: + Byte 1 (msb): Reserved + Byte 2: Reserved + Byte 3: Bit 7: reserved + Bit 6: reserved + Bit 5: Auto Send Meter Report (for kWh) at the group time interval (Clamp 3) + Bit 4: Auto Send Meter Report (for kWh) at the group time interval (Clamp 2) + Bit 3: Auto Send Meter Report (for kWh) at the group time interval (Clamp 1) + Bit 2: Auto Send Meter Report (for watts) at the group time interval (Clamp 3) + Bit 1: Auto Send Meter Report (for watts) at the group time interval (Clamp 2) + Bit 0: Auto Send Meter Report (for watts) at the group time interval (Clamp 1) + Byte 4 (lsb): Bit 7: reserved + Bit 6: reserved + Bit 5: reserved + Bit 4: reserved + Bit 3: Auto Send Meter Report (for kWh) at the group time interval (whole HEM) + Bit 2: Auto Send Meter Report (for watts) at the group time interval (whole HEM) + Bit 1: Auto Send Multilevel Sensor Report (for watts) at the group time interval (whole HEM) + Bit 0: Auto Send Battery Report at the group time interval (whole HEM) + + + + + Which reports need to send in group3. Format is as follows: + Byte 1 (msb): Reserved + Byte 2: Reserved + Byte 3: Bit 7: reserved + Bit 6: reserved + Bit 5: Auto Send Meter Report (for kWh) at the group time interval (Clamp 3) + Bit 4: Auto Send Meter Report (for kWh) at the group time interval (Clamp 2) + Bit 3: Auto Send Meter Report (for kWh) at the group time interval (Clamp 1) + Bit 2: Auto Send Meter Report (for watts) at the group time interval (Clamp 3) + Bit 1: Auto Send Meter Report (for watts) at the group time interval (Clamp 2) + Bit 0: Auto Send Meter Report (for watts) at the group time interval (Clamp 1) + Byte 4 (lsb): Bit 7: reserved + Bit 6: reserved + Bit 5: reserved + Bit 4: reserved + Bit 3: Auto Send Meter Report (for kWh) at the group time interval (whole HEM) + Bit 2: Auto Send Meter Report (for watts) at the group time interval (whole HEM) + Bit 1: Auto Send Multilevel Sensor Report (for watts) at the group time interval (whole HEM) + Bit 0: Auto Send Battery Report at the group time interval (whole HEM) + + + + + Reset to default parameters number 111-113. Any value other then 0 will initiate this reset. + + + + + The interval of sending report group 1. + + + + + The interval of sending report group 2. + + + + + The interval of sending report group 3. + + + + + + + + + Device tag. + + + + + Reset to the default configuration. + + + + + + + + + + + + + diff --git a/deps/open-zwave/config/aeon_labs/recessed_doorsensor.xml b/deps/open-zwave/config/aeon_labs/recessed_doorsensor.xml new file mode 100644 index 0000000..8bd8414 --- /dev/null +++ b/deps/open-zwave/config/aeon_labs/recessed_doorsensor.xml @@ -0,0 +1,56 @@ + + + + + + + 0, Open: FF, Close: 00; 1, Open: 00, Close: FF; + Default setting: 0 + + + + 0, Open: FF, Close: 00; 1, Open: 00, Close: FF; + Default setting: 0 + + + + 0, Disable, 1, Enable; + Default setting: 0 + + + + This parameter is available when the low battery checking + function is activated or the device was waked up by other + actions (i.e. the z-wave button trigger, magnet switch + trigger and the Wake Up Interval Set timeout trigger). + The Recessed Door Sensor will check the battery power + when it was wake up as other ways. For example: the + z-wave button trigger, magnet switch trigger and the + Wake Up Interval Set timeout trigger. + Default setting: 86640 + + + + Bitsets: + 4 -> Sensor Binary + 8 -> Basic Set + Default setting: 0x00000100 (Basic Set) + + + + Device Tag + + + Reset to factory defaults. + + + + + + + + + + + + diff --git a/deps/open-zwave/config/device_configuration.xsd b/deps/open-zwave/config/device_configuration.xsd index 14e3249..2f7e217 100644 --- a/deps/open-zwave/config/device_configuration.xsd +++ b/deps/open-zwave/config/device_configuration.xsd @@ -51,6 +51,7 @@ + @@ -101,6 +102,7 @@ + @@ -227,6 +229,14 @@ + + + + + + + + diff --git a/deps/open-zwave/config/eurotronic/eur_stellaz.xml b/deps/open-zwave/config/eurotronic/eur_stellaz.xml new file mode 100644 index 0000000..6903691 --- /dev/null +++ b/deps/open-zwave/config/eurotronic/eur_stellaz.xml @@ -0,0 +1,26 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/deps/open-zwave/config/everspring/sp103.xml b/deps/open-zwave/config/everspring/sp103.xml index d9c5b26..79a0d5e 100644 --- a/deps/open-zwave/config/everspring/sp103.xml +++ b/deps/open-zwave/config/everspring/sp103.xml @@ -26,6 +26,7 @@ + diff --git a/deps/open-zwave/config/fibaro/fgbs001.xml b/deps/open-zwave/config/fibaro/fgbs001.xml index f5c0681..bc3a7d5 100644 --- a/deps/open-zwave/config/fibaro/fgbs001.xml +++ b/deps/open-zwave/config/fibaro/fgbs001.xml @@ -101,6 +101,7 @@ If the value is set to 0, then information about the temperature will be sent ev + diff --git a/deps/open-zwave/config/fibaro/fgd211.xml b/deps/open-zwave/config/fibaro/fgd211.xml index b412220..f34d2df 100644 --- a/deps/open-zwave/config/fibaro/fgd211.xml +++ b/deps/open-zwave/config/fibaro/fgd211.xml @@ -87,17 +87,17 @@ - - Amount of time (ms) the device keeps on flashing after receipt of Alarm Frame [1-65535][ms] + + Amount of time the device keeps on flashing after receipt of Alarm Frame (1s-65535s) - - - + + + diff --git a/deps/open-zwave/config/fibaro/fgfs101.xml b/deps/open-zwave/config/fibaro/fgfs101.xml new file mode 100644 index 0000000..4afe8da --- /dev/null +++ b/deps/open-zwave/config/fibaro/fgfs101.xml @@ -0,0 +1,120 @@ + + + + + + + + Flood alarm cancellation delay. Additional delay after a flood alarm has ceased. The parameter allows you to specify additional time, after which the flood alarm is cancelled once its violation has ceased. + + + + Acoustic and visual signals in case of flooding. + + + + + + + + Type of alarm frame for association group 1, activated by flood sensor. The parameter allows to specify the type of alarm frame or to force transmission of control commands (BASIC_SET) + + + + + + Value of the parameter specifying the forced level of dimming / opening sun blinds when comes "switch on" / "open" command to devices from association group no. 1. +In the case of alarm frames the alarm priority is specified. Possible parameter settings: (1 – 99) and 255. Value of 255 makes it possible to activate the device when using the Dimmer module it means activating the device and setting it to the previous stored condition, e.g. when Dimmer is set to 30%, then deactivated, and then reactivated using command 255, it will automatically be set to the previous condition, i.e. 30%. + + + + Deactivating transmission of the frame cancelling the alarm or the control frame deactivating the device (Basic). It allows for disabling the deactivation function or the alarm cancellation function for devices associated with the appropriate input of the Fibaro Sensor. NOTE: Information concerning alarm violation or activation commands for devices from association groups are always sent. + + + + + + Interval between successive readings of temperature from all sensors connected to the device in seconds. Note: taking temperature readings from the sensor does not result in sending a temperature condition report to the central hub. + + + + Insensitiveness to temperature changes. This is the maximum acceptable difference between the last reported temperature and the current temperature taken from the sensor. If the temperatures differ by the set value or more, then a report with the current temperature value is sent to the device assigned to association group no. 3. Intervals between taking readings from sensors are specified by parameter no. 10. +Possible parameter settings:1 – 1000 [each 0.01oC] [0.01oC – 10.00oC]. + + + + Transmitting the alarm or control frame in "broadcast" mode (i.e. to all devices within range), information sent in this mode is not repeated by the mesh network. NOTE: If the broadcast mode of information transmission is activated for a given channel, then transmission of information in singlecast mode to devices assigned to the association group of this channel is deactivated. + + + + + + + + The parameter stores a temperature value, below which LED indicator blinks with a colour determined by Parameter 61 settings. By default the LED indicator blinks blue. +Possible parameter settings:-10000 – 10000 [each 0.01oC] [-100oC – 100oC]. + + + + The parameter stores a temperature value, above which LED indicator blinks with a colour determined by Parameter 62 settings. By default the LED indicator blinks red. +Possible parameter settings:-10000 – 10000 [each 0.01oC] [-100oC – 100oC]. + + + + The parameter stores RGB colour value. + + + + The parameter stores RGB colour value. + + + + Parameter determines LED indicator's operation. Set to 0 turns the indicator off, saving battery life. + + + + + + + Parameter stores a temperature value to be added to or deducted from the current temperature measured by the internal temperature sensor in order to compensate the difference between air temperature and the temperature at floor level. +Possible parameter settings:-10000 – 10000 [each 0.01oC] [-100oC – 100oC]. + + + + The device is able to turn on alarms resulting from sensors vibrations, e.g. when the sensor is moved, or the TMP button is released. Group 2 association alarms are not cancelled. + + + + + + + + Parameter determines a time period after which alarm will become 'quiet' - still active but the device will go into battery saving mode. Visual or acoustic alarm will be reactivated after time period specified in Parameter 76. When alarm status ceases, alarm will be turned off immediately. +Value of 0 means visual and acoustic alarms are active indefinitely. In battery power mode the device will never go to sleep which may shorten battery life significantly. + + + + Parameter determines a time period after which an alarm frame will be retransmitted. +Value of 0 cancels an alarm frame retransmission. + + + + Allows for turning off the internal flood sensor. Tamper and internal temperature sensors will remain active. + + + + + + + + + + + + + + + + + + diff --git a/deps/open-zwave/config/fibaro/fgms.xml b/deps/open-zwave/config/fibaro/fgms.xml new file mode 100644 index 0000000..a95da15 --- /dev/null +++ b/deps/open-zwave/config/fibaro/fgms.xml @@ -0,0 +1,358 @@ + + + + + + + + + At each wake up the Fibaro Motion Sensor communicates with the + main controller, updates parameter settings and the software if + necessary. The Motion Sensor will wake up at a defined time interval + and will ALWAYS try to communicate with the main controller + Wake Up Interval set to 0 cancels the WAKE UP command frame, + i.e. the device will have to be woke up manually, through the B + button, sending NODE INFO command frame. + Available settings: 0-65535 (0-65535 seconds). + Default setting: 7200 (7200 seconds). + NOTE + It's not recommended to set the value of Wake Up + interval below 10 seconds. Short wake up interval + may shorten the battery life and delay the reports or + even make them impossible. + + + + + The lower the value, the more sensitive the PIR sensor. + Available settings: 8 - 255 + Default setting: 10 + + + + + Period of time through which the PIR sensor is "blind" (insensitive) to + motion. After this time period the PIR sensor will be again able to + detect motion. The longer the insensitivity period, the longer the + battery life. If the sensor is required to detect motion quickly, the time + period may be shortened. The time of insensitivity should be shorter + that the time period set in parameter 6. + Available settings: 0 - 15 + Formula to calculate the time: time [s] = 0.5 x (value + 1) + Default setting: 15 (8 seconds) + + + + + Sets the number of moves required for the PIR sensor to report + motion. The lower the value, the less sensitive the PIR sensor. It's + not recommended to modify this parameter settings. + Available settings: 0 - 3 + Formula to calculate the number of pulses: pulses = (value + 1) + Default setting: 1 (2 pulses) + + + + + + + + + Period of time during which the number of moves set in parameter 3 + must be detected in order for the PIR sensor to report motion. The + higher the value, the more sensitive the PIR sensor. It's not + recommended to modify this parameter setting. + Available settings: 0 - 3 + Formula to calculate the time: time [s] = 4 x (value + 1) + Default setting: 2 (12 seconds) + + + + + + + + + Motion alarm will be cancelled in the main controller and the + associated devices after the period of time set in this parameter. Any + motion detected during the cancellation delay time countdown will + result in the countdown being restarted. In case of small values, + below 10 seconds, the value of parameter 2 must be modified (PIR + sensor's "Blind Time"). + Available settings: 1 - 65535 + Default setting: 30 (30 seconds) + + + + + The parameter determines the part of day in which the PIR sensor + will be active. This parameter influences only the motion reports and + associations. Tamper, light intensity and temperature measurements + will be still active, regardless of this parameter settings. + Default setting: 0 (always active) + + + + + + + + The parameter defines the difference between night and day, in + terms of light intensity, used in parameter 8. + Available settings: 1 - 65535 + Default setting: 200 (200 lux) + + + + + The parameter determines the command frames sent in 1-st + association group, assigned to PIR sensor. + Values of BASIC ON and BASIC OFF command frames may be + modified by dedicated parameters. + Default setting: 0 (ON and OFF) + + + + + + + + The value of 255 allows to turn ON a device. In case of the Dimmer, + the value of 255 means turning ON at the last memorized state, e.g. + the Dimmer turned ON at 30% and turned OFF using the value of + 255, and then turned OFF, will be turned ON at 30%, i.e. the last + memorized state. + Available settings: 0 - 255 + Default setting: 255 + + + + + The command frame sent at the moment of motion alarm + cancellation, after the cancellation delay time, specified in parameter + 6, has passed. + The value of 0 allows to turn a device OFF while the value of 255 + allows to turn ON a device. In case of the Dimmer, the value of 255 + means turning ON at the last memorized state, e.g. the Dimmer + turned ON at 30% and turned OFF using the value of 255, and then + turned OFF, will be turned ON at 30%, i.e. the last memorized state. + Available settings: 0 - 255 + Default setting: 0 + + + + + The parameter determines the changes in forces acting on the Fibaro + Motion Sensor resulting in tamper alarm being reported - g-force + acceleration. + Available settings: 0 - 122 (0.08 - 2g; multiply by 0.016g; 0 = tamper inactive) + Default setting: 15 (0.224g) + + + + + Time period after which a tamper alarm will be cancelled. Another + tampering detected during the countdown to cancellation will not + extend the delay. + Available settings: 1 - 65535 + Default setting: 30 (seconds) + + + + + The parameter determines the behaviour of tamper and how it + reports. + Tamper: Tamper alarm is reported in Sensor Alarm command class. + Cancellation: Cancellation is reported in Sensor Alarm command class after the time period set in parameter 22 (Tamper Alarm Cancellation Delay). + Orientation: Sensor's orientation in space is reported in Fibaro Command Class after the time period set in parameter 22. + Vibration: The maximum level of vibrations recorded in the time period set + in parameter 22 is reported. Reports stop being sent when the + vibrations cease. The reports are sent in Sensor Alarm command + class. Value displayed in the "value" field (0 - 100) depends on the + vibrations force. Reports to the association groups are sent using + Sensor Alarm command class. + Default setting: 0 (Tamper) + + + + + + + + + + The parameter determines whether the tamper alarm frame will or + will not be sent in broadcast mode. Alarm frames sent in broadcast + mode may be received by all of the devices within communication + range (if they accept such frames). + Default setting: 0 + + + + + + + The parameter determines the change in light intensity level + resulting in illumination report being sent to the main controller. + Available settings: 0 - 65535 (1 - 65535 lux; 0 = reports are not + sent) + Default setting: 200 (200 lux) + + + + + Time interval between consecutive illumination reports. The reports + are sent even if there are no changes in the light intensity. + Available settings: 0 - 65535 (1 - 65535 seconds; 0 = reports are + not sent) + Default setting: 0 (no reports) + NOTE + Frequent reports will shorten the battery life. + Parameter value under 5 may result in blocking the + temperature reports. + + + + + The parameter determines the change in level of temperature + resulting in temperature report being sent to the main controller. + Available settings: 0 - 255 (0.1 - 25.5C; 0 = reports are not sent) + Default setting: 10 (1C) + + + + + The parameter determines how often the temperature will be + measured. The shorter the time, the more frequently the temperature + will be measured, but the battery life will shorten. + Available settings: 0 - 65535 (1 - 65535 seconds; 0 = temperature + will not be measured) + Default setting: 900 (900 seconds) + NOTE + Frequent reports will shorten the battery life. + Parameter value under 5 may result in blocking the + illumination reports. + + + + + The parameter determines how often the temperature reports will be + sent to the main controller. + Available settings: 0 - 65535 (1 - 65535 seconds; 0 = reports are not + sent) + Default setting: 0 + + + + + The value to be added to the actual temperature, measured by the + sensor (temperature compensation). + Available settings: 0 - 100 (0 to 100C) or 64536 - 65535 (-100 to -0.10C) + Default setting: 0 + + + + + The parameter determines the way in which LED behaves + after motion has been detected. + Values 1 and from 3 to 9 = single long blink at the moment of reporting + motion. No other motion will be indicated until alarm is cancelled. + Values from 10 to 18 = single long blink at the moment of reporting + motion and one short blink each time the motion is detected again. + Values from 19 to 26 = single long blink at the moment of reporting + motion and two short blinks each time the motion is detected again. + Default setting: 10 (flashlight) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The parameter determines the brightness of LED when indicating + motion. + Available settings: 0 - 100 (1 - 100%; 0 = brightness determined by + the ambient lighting - see parameters 82 and 83) + Default setting: 50 + + + + + The parameter is relevant only when the parameter 81 is set to 0. + Available settings: 0 to parameter 83 value + Default setting: 100 (100 lux) + + + + + The parameter is relevant only when the parameter 81 is set to 0. + Available settings: parameter 82 value to 65535 + Default setting: 1000 (1000 lux) + NOTE + The value of the parameter 83 must be higher than + the value of the parameter 82. + + + + + This parameter is relevant only when parameter 80 has been + properly configured. + Available settings: 0 to parameter 87 value (degrees Celsius) + Default setting: 18 (18C) + + + + + This parameter is relevant only when parameter 80 has been + properly configured. + Available settings: parameter 86 value to 255 (degrees Celsius) + Default setting: 28 (28C) + + + + + Indicating mode resembles a police car (white, red and blue). + Default setting: 1 (on) + + + + + + + + + + + + + + + + + + + diff --git a/deps/open-zwave/config/fibaro/fgrgbwm441.xml b/deps/open-zwave/config/fibaro/fgrgbwm441.xml new file mode 100644 index 0000000..83e597b --- /dev/null +++ b/deps/open-zwave/config/fibaro/fgrgbwm441.xml @@ -0,0 +1,103 @@ + + + + + + + Activate/Deactive ALL ON/OFF + + + + + + + Choose which command classes are sent to associated devices. + + + + + + + + Choose the behaviour of transitions between different levels. + + + + + Size of the step for each change in level during the transition. + + + Time between each step in a transition between levels. Setting this to zero means an instantaneous change. + + + 0 - immediate change; 1->63: 20ms->126ms (value*20ms); 65->127: 1s->63s (value-64)*1s; 129->191: 10s->630s (value-128)*10s; 193->255: 1min->63min (value-192)*1min. Default setting: 67 (3s) + + + Maximum brightness level for the dimmer + + + Minimum brightness level for the dimmer + + + This is too complex to describe here, since this value is built up from 4-bits for each of the 4 channels. Refer to the table in the product manual. Default value is 4369 (1111 in hex). + + + Saving state before power faillure + + + + + Alarm of any type (general alarm, water flooding alarm, smoke alarm: CO, CO2, temperature alarm). Default setting 0 (Inactive) + + + + + + + Program number selected from the 10 available. + + + In ALARM PROGRAM mode (see parameter 30), this defines the time in seconds the program lasts (1s->65534s) + + + Specify which command class is used to report output status changes + + + + + + Parameter defines a value by which input voltage must change in order to be reported to the main controller. New value is calculated based on last reported value: Default setting: 5 (0.5V). Range: 1->100 - (0.1V->10V). + + + Sent if last reported value differs from the current value. Reports will also be sent in case of polling. Default setting: 30 (30s). Range: 1->65534 (1s->65534s) - interval between reports. Zero means reports are only sent in the case of polling, or at turning OFF the device + + + Interval between energy consumption reports (in kWh). New reported energy consumption value is calculated based on last reported value. 1->254 (0.01kWh->2.54kWh). Zero means changes in consumed energy will not be reported, except in case of polling. + + + Set whether to remember the previous RGB mix after the brightness has fallen to zero (black) + + + + + First predefined program to use when device is set to work in RGB/RGBW mode (parameter 14) + + + Behaviour when an input is triple-clicked + + + + + + + + + + + + + + + + + diff --git a/deps/open-zwave/config/fibaro/fgrm222.xml b/deps/open-zwave/config/fibaro/fgrm222.xml new file mode 100644 index 0000000..2a47827 --- /dev/null +++ b/deps/open-zwave/config/fibaro/fgrm222.xml @@ -0,0 +1,82 @@ + + + + + + + + + + + + + + + + + + + + Binary inputs type configuration + + + + + + + Options for changing parameter 1-99, default 16 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Only valid for the 1.9 version of FGR221. The device offers the possibility of sending commands compatible with Command class scene activation. Information is sent to devices assigned to association group no. 3. Controllers such as Home Center 2 are able to interpret such commands and based on these commands they activate scenes, to which specific scene IDs have been assigned. The user may expand the functionality of the button connected to inputs S1 and S2 by distinguishing the actions of keys connected to those inputs. For example: double click would activate the scene goodnight and triple click would activate the scene morning. + + + + + + Start a Calibration Cycle on the device + + + + + + + + + + + + + + + diff --git a/deps/open-zwave/config/fibaro/fgs221.xml b/deps/open-zwave/config/fibaro/fgs221.xml index ada6d7a..ccdc567 100644 --- a/deps/open-zwave/config/fibaro/fgs221.xml +++ b/deps/open-zwave/config/fibaro/fgs221.xml @@ -19,11 +19,11 @@ - + Automatic turning off relay 1 after set time, in 10ms increments (default: 200ms) - + Automatic turning off relay 2 after set time, in 10ms increments (default: 200ms) diff --git a/deps/open-zwave/config/fibaro/fgss101.xml b/deps/open-zwave/config/fibaro/fgss101.xml new file mode 100644 index 0000000..f34070f --- /dev/null +++ b/deps/open-zwave/config/fibaro/fgss101.xml @@ -0,0 +1,167 @@ + + + + + + + + + The time between when the smoke disappears and the Fibaro Smoke Sensor stops sending the alarm signal. + Available settings: 0 – 17280, 65535 (5s multiplier) [5s-24h] + 0: no delay, immediate cancellation, + 65535: alarm cancellation inactive - Smoke Sensor will keep indicating smoke alarm after the smoke will have disappeared. The smoke alarm can be only ceased manually, by entering 2nd menu level (see section XIII). + Default setting: 0 + + + + + Allows for deactivating the LED indicator and the acoustic alarm, in case of detecting an alarm of any type. + This doesn’t affect the communication with the Z-Wave network controller, i.e. the sensor will keep sending alarms, reports and all information to the associated devices. + Modifying this parameter settings helps extending the battery life. + + + + + + + + + Type of alarm frame for association group 1, activated by smoke sensor. + The parameter allows to specify the type of alarm frame or to force transmission of control commands (BASIC_SET) + + + + + + + The value of 255 allows for turning on a device. In case of Dimmer, the value of 255 means turning on the device with the last memorized state. E.g. + Dimmer set to 30% and then turned off, and next turned on using the 255 command, will turn on with the last remembered status, i.e. 30%. + In case of alarm frames, alarm priority is defined. + Available settings: (1 - 99) or 255 + Default setting: 255 + + + + + Time interval between consecutive temperature reports. + The parameter is relevant for the battery powering mode only. Longer time interval means less frequent communication and thus a longer battery life. + Report is sent when new temperatue value is different from the one previously reported. Temperature reports can be also sent as a result of polling. + Available settings: 1 – 17280, 0 (multiply by 5 seconds) [5s-24h] + 0 – reports inactive + Default setting: 0 (Reports inactive) + + + + + The temperature report will only be sent if there is a difference in temperature value from the previous value reported, defined in this parameter (hysteresis). + Temparature reports can be also sent as a result of polling. + Available settings: 0 – 100 (in 0,1C steps) + 0 – temperature change reporting inactive + Default setting: 20 (2C) + + + + + Transmitting the alarm or control frame in "broadcast" mode (i.e. to all devices within range), information sent in this mode is not repeated by the mesh network. + NOTE: If the broadcast mode of information transmission is activated for a given channel, then transmission of information in singlecast mode to devices assigned to the association group of this channel is deactivated. + + + + + + + + + Parameter stores a temperature value to be added to or deducted from the current temperature measured by internal temperature sensor in order to compensate the difference between air temperature and temperature measured at the ceiling level. + Available settings: -1000 -/+ 1000 (in 0,1C steps) + Default setting: 0 (0C) + + + + + Time period between the consecutive Z-Wave network range tests. + In battery powering mode, Z-Wave network range test is carried out at the wake up interval. The value of 0 turns off the Z-Wave range test, regardless of the powering mode chosen. + Available settings: 0 – 144 (10min multiplier) [10min-24h] + 0 – Z-Wave network range test inactive + Default setting: 1 (10min) + + + + + Temperature value, measured by the built-in temperature sensor, above which the temperature alarm is sent. + Available settings: 0,2 - 100 + 0 – temperature alarm inactive + 2 - 100 – (2 - 100C) + Default setting: 54 (54C) + + + + + There are 3 levels of sensitivity to smoke presence. Level 1 means the highest sensitivity. + + + + + + + This parameter allows for specifying the moment in which the Black Box starts recording data. After the specified smoke and temperature values will be exceeded, the Fibaro Smoke Sensor’s Black Box will record them. + + + + + + + Time interval in which malfuntion alarm, if detected, is repeated using visual and acoustic alarms. + Available settings: 1 - 255 (100 ms multiplier) [100ms-25,5s] + Default setting: 10 (1s) + + + + + Time interval in which temperature alarm, if detected, is repeated using visual and acoustic alarms. + Available settings: 1 - 255 (100 ms multiplier) [100ms-25,5s] + Default setting: 5 (500ms) + + + + + Time interval in which lack of the Z-Wave network alarm, if detected, is repeated using visual and acoustic alarms. + Available settings: 1 - 17280 (5s multiplier) [5s-24h] + Default setting: 360 (30min) + + + + + Time interval in which low battery alarm, if detected, is repeated using visual and acoustic alarms. + Available settings: 1 - 17280 (5s multiplier) [5s-24h] + Default setting: 360 (30min) + + + + + This parameter allows for specifying the moment in which the Black Box starts recording data. After the specified smoke and temperature values will be exceeded, the Fibaro Smoke Sensor’s Black Box will record them. + + + + + + default setting: tamper alarm active, with cancellation option available + + + + + + + + + + + + + + + + + + + diff --git a/deps/open-zwave/config/fibaro/fgwpe.xml b/deps/open-zwave/config/fibaro/fgwpe.xml index fe88fdf..0bbad05 100644 --- a/deps/open-zwave/config/fibaro/fgwpe.xml +++ b/deps/open-zwave/config/fibaro/fgwpe.xml @@ -1,6 +1,15 @@ + + + + + + + + + @@ -39,8 +48,7 @@ - Parameter defines how the Wall Plug will respond to alarms (device's - status change) Default setting: 0 + Parameter defines how the Wall Plug will respond to alarms (device's status change) Default setting: 0 0 - no reaction, 1 - turn on connected device. LED ring signals an alarm through defined time period (parameter 39) or untill the alarm is cancelled. @@ -63,7 +71,7 @@ - + Wall Plug's alarm mode duration. If a device sending an alarm frame through the Z-Wave network sets alarm duration as well, this parameter's settings are ignored. @@ -92,15 +100,15 @@ Default seting: 30 (s) - + New, reported energy value is calculated based on last reported value. Default setting: 10 (0,1 kWh). Available settings: 1 - 254 (0,01kWh - 2,54kWh). - Value of 25 - changes in consumed energy will not be reported. + Value of 255 - changes in consumed energy will not be reported. Reports will be sent only in case of polling. - + Parameter defines time period between reports sent when changes in power load have not been recorded. By default, if power load changes have not been recorded, reports are sent every hour. @@ -111,15 +119,15 @@ This parameter determines whether energy metering should include the amount of energy consumed by the Wall Plug itself. Results are being added to energy consumed by controlled device. Default setting: 0 - - + + - + Lower power threshold, used in parameter 52. Default setting: 300 (30 W) Available settings: 0 - 25 000 (0,0W - 2 500W) DOWN value cannot be higher than a value specified in parameter 51. - + Upper power threshold, used in parameter 52. Default setting: 500 (50 W) Available settings: 1 - 25 000 (0,1W - 2 500W) UP value cannot be lower than a value specified in parameter 50. @@ -156,7 +164,7 @@ - + Function is active only when parameter 61 is set to 0 or 1.Default setting: 25 000 (2 500W) Available settings: 1 000 - 32 000 (100W - 3200W). @@ -174,7 +182,7 @@ - + @@ -215,7 +223,7 @@ - + This function allows for turning off the controlled device in case of exceeding the defined power. Controlled device will be turned off even if "always on" function is active (parameter 1). Controlled device can be turned back on via B-button or sending a control frame. By default this function is inactive. diff --git a/deps/open-zwave/config/manufacturer_specific.xml b/deps/open-zwave/config/manufacturer_specific.xml index cf26973..2df5f5a 100644 --- a/deps/open-zwave/config/manufacturer_specific.xml +++ b/deps/open-zwave/config/manufacturer_specific.xml @@ -40,13 +40,21 @@ + + + + + + + + @@ -59,10 +67,18 @@ + + + + + + + + @@ -96,14 +112,12 @@ + - - - @@ -118,6 +132,9 @@ + + + @@ -128,6 +145,7 @@ + @@ -138,6 +156,8 @@ + + @@ -149,13 +169,17 @@ + + + + @@ -163,13 +187,20 @@ - - - - - - + + + + + + + + + + + + + @@ -185,7 +216,9 @@ + + @@ -204,6 +237,7 @@ + @@ -273,6 +307,9 @@ + + + @@ -311,6 +348,10 @@ + + + + @@ -318,6 +359,7 @@ + @@ -331,6 +373,7 @@ + @@ -388,15 +431,15 @@ - - - - - - - - - + + + + + + + + + @@ -406,6 +449,9 @@ + + + @@ -418,12 +464,17 @@ + + + - + + + diff --git a/deps/open-zwave/config/options.xml b/deps/open-zwave/config/options.xml index ff9dc6b..84a0786 100644 --- a/deps/open-zwave/config/options.xml +++ b/deps/open-zwave/config/options.xml @@ -4,6 +4,7 @@