diff --git a/INSTALL b/INSTALL new file mode 100644 index 00000000..cb590664 --- /dev/null +++ b/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/Makefile b/Makefile new file mode 100644 index 00000000..e91893ab --- /dev/null +++ b/Makefile @@ -0,0 +1,46 @@ +# +# Makefile for OpenzWave Mac OS X applications +# Greg Satz + +# GNU make only + +# requires libudev-dev + +.SUFFIXES: .d .cpp .o .a +.PHONY: default clean install + + +top_srcdir := $(abspath $(dir $(lastword $(MAKEFILE_LIST)))) +top_builddir ?= $(CURDIR) +export top_builddir +PREFIX ?= /usr/local +export PREFIX + +all: + $(MAKE) -C $(top_srcdir)/cpp/build/ -$(MAKEFLAGS) + $(MAKE) -C $(top_srcdir)/cpp/examples/MinOZW/ -$(MAKEFLAGS) + +install: + $(MAKE) -C $(top_srcdir)/cpp/build/ -$(MAKEFLAGS) $(MAKECMDGOALS) + $(MAKE) -C $(top_srcdir)/cpp/examples/MinOZW/ -$(MAKEFLAGS) $(MAKECMDGOALS) + +clean: + $(MAKE) -C $(top_srcdir)/cpp/build/ -$(MAKEFLAGS) $(MAKECMDGOALS) + $(MAKE) -C $(top_srcdir)/cpp/examples/MinOZW/ -$(MAKEFLAGS) $(MAKECMDGOALS) + +cpp/src/vers.cpp: + $(MAKE) -C $(top_srcdir)/cpp/build/ -$(MAKEFLAGS) cpp/src/vers.cpp + +check: + +include $(top_srcdir)/cpp/build/support.mk + +dist-update: + @echo "Updating List of Distribition Files" + @$(SVN) --xml -v st > .distfiles + @$(top_srcdir)/makedist + +DIST_FORMATS ?= gzip + +include $(top_srcdir)/distfiles.mk +include $(top_srcdir)/dist.mk \ No newline at end of file diff --git a/config/BeNext/AlarmSound.xml b/config/BeNext/AlarmSound.xml new file mode 100644 index 00000000..ca8e1a19 --- /dev/null +++ b/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/config/aeon_labs/doorwindow.xml b/config/aeon_labs/doorwindow.xml index 871c468d..57427625 100644 --- a/config/aeon_labs/doorwindow.xml +++ b/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/config/eurotronic/eur_stellaz.xml b/config/eurotronic/eur_stellaz.xml new file mode 100644 index 00000000..d92126c8 --- /dev/null +++ b/config/eurotronic/eur_stellaz.xml @@ -0,0 +1,26 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/fibaro/fgfs101.xml b/config/fibaro/fgfs101.xml new file mode 100644 index 00000000..4afe8da0 --- /dev/null +++ b/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/config/fibaro/fgrm222.xml b/config/fibaro/fgrm222.xml new file mode 100644 index 00000000..2a47827a --- /dev/null +++ b/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/config/fibaro/fgss101.xml b/config/fibaro/fgss101.xml new file mode 100644 index 00000000..026d046c --- /dev/null +++ b/config/fibaro/fgss101.xml @@ -0,0 +1,144 @@ + + + + + + + + + The time between when the smoke disappears and the Fibaro Smoke Sensor stops sending the alarm signal. + 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) + + + + + + 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%. + + + + 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. + + + + 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) + Possible parameter settings:1 - 1000 (0.01C - 10.00C) + + + + 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 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.01C] (-100C - 100C). + + + + 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: 10 (1s) + + + + 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/config/fibaro/fgwpe.xml b/config/fibaro/fgwpe.xml index fe88fdfb..97e8b587 100644 --- a/config/fibaro/fgwpe.xml +++ b/config/fibaro/fgwpe.xml @@ -1,6 +1,12 @@ + + + + + + @@ -63,7 +69,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. @@ -100,7 +106,7 @@ - + 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. @@ -115,11 +121,11 @@ - + 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 +162,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). @@ -215,7 +221,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/config/manufacturer_specific.xml b/config/manufacturer_specific.xml index 138ca1d7..e4ab4efc 100644 --- a/config/manufacturer_specific.xml +++ b/config/manufacturer_specific.xml @@ -60,6 +60,7 @@ + @@ -118,6 +119,9 @@ + + + @@ -152,10 +156,12 @@ + + @@ -170,8 +176,10 @@ - - + + + + @@ -205,6 +213,7 @@ + @@ -312,6 +321,9 @@ + + + @@ -319,6 +331,7 @@ + @@ -332,6 +345,7 @@ + @@ -407,6 +421,7 @@ + @@ -419,9 +434,12 @@ + + + - + diff --git a/config/options.xml b/config/options.xml index ff9dc6b0..d088771e 100644 --- a/config/options.xml +++ b/config/options.xml @@ -4,6 +4,6 @@