From d12c378b4ff22296e5b2d7ba8cd391fe31771fab Mon Sep 17 00:00:00 2001 From: Ziver Koc Date: Sat, 23 Nov 2019 00:36:57 +0100 Subject: [PATCH] Added config files for Zwave and added better logging --- .gitignore | 5 +- plugins/hal-zwave/config/2gig/ct100.xml | 7 + plugins/hal-zwave/config/2gig/ct30.xml | 7 + .../hal-zwave/config/BeNext/1poleswitch.xml | 35 + .../hal-zwave/config/BeNext/2poleswitch.xml | 35 + .../hal-zwave/config/BeNext/AlarmSound.xml | 62 ++ .../hal-zwave/config/BeNext/BuiltinDimmer.xml | 77 ++ .../hal-zwave/config/BeNext/DoorSensor.xml | 44 + .../hal-zwave/config/BeNext/EnergySwitch.xml | 31 + plugins/hal-zwave/config/BeNext/Molite.xml | 33 + .../hal-zwave/config/BeNext/PluginDimmer.xml | 66 ++ plugins/hal-zwave/config/BeNext/TagReader.xml | 40 + plugins/hal-zwave/config/act/lfm20.xml | 4 + plugins/hal-zwave/config/act/zdm230.xml | 93 ++ plugins/hal-zwave/config/act/zdw103.xml | 69 ++ plugins/hal-zwave/config/act/zdw232.xml | 112 ++ plugins/hal-zwave/config/act/zir010.xml | 63 ++ plugins/hal-zwave/config/act/zrp110.xml | 7 + plugins/hal-zwave/config/act/zrw103.xml | 36 + plugins/hal-zwave/config/aeon_labs/alms.xml | 109 ++ .../hal-zwave/config/aeon_labs/doorwindow.xml | 47 + plugins/hal-zwave/config/aeon_labs/hem.xml | 187 ++++ plugins/hal-zwave/config/aeon_labs/hemg2.xml | 177 ++++ plugins/hal-zwave/config/aeon_labs/keyfob.xml | 59 ++ .../hal-zwave/config/aeon_labs/minimote.xml | 32 + .../config/aeon_labs/recessed_doorsensor.xml | 56 + plugins/hal-zwave/config/aeon_labs/ses.xml | 151 +++ plugins/hal-zwave/config/danfoss/living.xml | 5 + plugins/hal-zwave/config/danfoss/z.xml | 7 + plugins/hal-zwave/config/device_classes.xml | 103 ++ plugins/hal-zwave/config/device_classes.xsd | 44 + .../hal-zwave/config/device_configuration.xsd | 252 +++++ plugins/hal-zwave/config/duwi/ZWES1000.xml | 8 + .../config/eurotronic/eur_stellaz.xml | 26 + plugins/hal-zwave/config/everspring/an145.xml | 12 + plugins/hal-zwave/config/everspring/an158.xml | 35 + plugins/hal-zwave/config/everspring/se812.xml | 13 + plugins/hal-zwave/config/everspring/sf812.xml | 12 + plugins/hal-zwave/config/everspring/sm103.xml | 35 + plugins/hal-zwave/config/everspring/sp103.xml | 39 + plugins/hal-zwave/config/everspring/sp814.xml | 48 + plugins/hal-zwave/config/everspring/st814.xml | 56 + plugins/hal-zwave/config/everspring/st815.xml | 48 + plugins/hal-zwave/config/everspring/tse03.xml | 12 + .../hal-zwave/config/everspringct/hsm02.xml | 91 ++ plugins/hal-zwave/config/fibaro/fgbs001.xml | 115 +++ plugins/hal-zwave/config/fibaro/fgd211.xml | 104 ++ plugins/hal-zwave/config/fibaro/fgfs101.xml | 120 +++ plugins/hal-zwave/config/fibaro/fgk001.xml | 96 ++ plugins/hal-zwave/config/fibaro/fgms.xml | 358 +++++++ plugins/hal-zwave/config/fibaro/fgr221.xml | 77 ++ .../hal-zwave/config/fibaro/fgrgbwm441.xml | 103 ++ plugins/hal-zwave/config/fibaro/fgrm222.xml | 82 ++ plugins/hal-zwave/config/fibaro/fgs211.xml | 104 ++ plugins/hal-zwave/config/fibaro/fgs221.xml | 150 +++ plugins/hal-zwave/config/fibaro/fgss101.xml | 167 +++ plugins/hal-zwave/config/fibaro/fgwpe.xml | 246 +++++ .../hal-zwave/config/frostdale/fdn2nxx.xml | 5 + plugins/hal-zwave/config/ge/dimmer.xml | 40 + plugins/hal-zwave/config/ge/dimmer_module.xml | 35 + plugins/hal-zwave/config/ge/relay.xml | 17 + .../hal-zwave/config/greenwave/powernode1.xml | 30 + .../hal-zwave/config/greenwave/powernode6.xml | 31 + plugins/hal-zwave/config/homeseer/hsm100.xml | 108 ++ .../hal-zwave/config/homeseer/ztroller.xml | 6 + .../config/honeywell/th8320zw1000.xml | 5 + plugins/hal-zwave/config/horstmann/hrt4zw.xml | 48 + .../hal-zwave/config/intermatic/ca8900.xml | 7 + plugins/hal-zwave/config/leviton/rzi10.xml | 5 + plugins/hal-zwave/config/leviton/vrcpg.xml | 5 + plugins/hal-zwave/config/leviton/vrf01.xml | 5 + plugins/hal-zwave/config/leviton/vri06.xml | 5 + plugins/hal-zwave/config/leviton/vri10.xml | 5 + .../config/manufacturer_specific.xml | 483 +++++++++ .../config/manufacturer_specific.xsd | 34 + plugins/hal-zwave/config/northq/nq92021.xml | 54 + plugins/hal-zwave/config/options.xml | 10 + plugins/hal-zwave/config/options.xsd | 22 + plugins/hal-zwave/config/philio/psm02.xml | 121 +++ plugins/hal-zwave/config/rcs/em52-zw.xml | 6 + plugins/hal-zwave/config/rcs/pm12-zw.xml | 7 + plugins/hal-zwave/config/rcs/therm0005.xml | 22 + plugins/hal-zwave/config/rcs/therm0007.xml | 39 + plugins/hal-zwave/config/rcs/therm0009.xml | 6 + plugins/hal-zwave/config/remotec/zurc.xml | 27 + plugins/hal-zwave/config/remotec/zxt-120.xml | 5 + .../hal-zwave/config/schlagelink/itemp.xml | 31 + .../config/trane/TZEMT400AB32MAA.xml | 955 ++++++++++++++++++ .../config/trane/TZEMT400BB32MAA.xml | 955 ++++++++++++++++++ plugins/hal-zwave/config/vision/zs5101eu.xml | 8 + plugins/hal-zwave/config/vitrum/vitrumBS.xml | 5 + .../hal-zwave/config/waynedalton/WDTC-20.xml | 8 + plugins/hal-zwave/config/wenzhou/tz66d.xml | 34 + plugins/hal-zwave/config/wenzhou/tz88.xml | 13 + .../hal-zwave/config/zwave.me/ZME_06433.xml | 95 ++ .../hal-zwave/config/zwave.me/ZME_06436.xml | 97 ++ .../hal-zwave/config/zwave.me/ZME_WCD2.xml | 136 +++ plugins/hal-zwave/config/zwave.me/kfob.xml | 118 +++ plugins/hal-zwave/config/zwcfg.xsd | 249 +++++ plugins/hal-zwave/config/zwscene.xsd | 28 + .../hal/plugin/zwave/HalZWaveController.java | 66 +- .../plugin/zwave/HalZWaveControllerTest.java | 5 +- 102 files changed, 8169 insertions(+), 39 deletions(-) create mode 100644 plugins/hal-zwave/config/2gig/ct100.xml create mode 100644 plugins/hal-zwave/config/2gig/ct30.xml create mode 100644 plugins/hal-zwave/config/BeNext/1poleswitch.xml create mode 100644 plugins/hal-zwave/config/BeNext/2poleswitch.xml create mode 100644 plugins/hal-zwave/config/BeNext/AlarmSound.xml create mode 100644 plugins/hal-zwave/config/BeNext/BuiltinDimmer.xml create mode 100644 plugins/hal-zwave/config/BeNext/DoorSensor.xml create mode 100644 plugins/hal-zwave/config/BeNext/EnergySwitch.xml create mode 100644 plugins/hal-zwave/config/BeNext/Molite.xml create mode 100644 plugins/hal-zwave/config/BeNext/PluginDimmer.xml create mode 100644 plugins/hal-zwave/config/BeNext/TagReader.xml create mode 100644 plugins/hal-zwave/config/act/lfm20.xml create mode 100644 plugins/hal-zwave/config/act/zdm230.xml create mode 100644 plugins/hal-zwave/config/act/zdw103.xml create mode 100644 plugins/hal-zwave/config/act/zdw232.xml create mode 100644 plugins/hal-zwave/config/act/zir010.xml create mode 100644 plugins/hal-zwave/config/act/zrp110.xml create mode 100644 plugins/hal-zwave/config/act/zrw103.xml create mode 100644 plugins/hal-zwave/config/aeon_labs/alms.xml create mode 100644 plugins/hal-zwave/config/aeon_labs/doorwindow.xml create mode 100644 plugins/hal-zwave/config/aeon_labs/hem.xml create mode 100644 plugins/hal-zwave/config/aeon_labs/hemg2.xml create mode 100644 plugins/hal-zwave/config/aeon_labs/keyfob.xml create mode 100644 plugins/hal-zwave/config/aeon_labs/minimote.xml create mode 100644 plugins/hal-zwave/config/aeon_labs/recessed_doorsensor.xml create mode 100644 plugins/hal-zwave/config/aeon_labs/ses.xml create mode 100644 plugins/hal-zwave/config/danfoss/living.xml create mode 100644 plugins/hal-zwave/config/danfoss/z.xml create mode 100644 plugins/hal-zwave/config/device_classes.xml create mode 100644 plugins/hal-zwave/config/device_classes.xsd create mode 100644 plugins/hal-zwave/config/device_configuration.xsd create mode 100644 plugins/hal-zwave/config/duwi/ZWES1000.xml create mode 100644 plugins/hal-zwave/config/eurotronic/eur_stellaz.xml create mode 100644 plugins/hal-zwave/config/everspring/an145.xml create mode 100644 plugins/hal-zwave/config/everspring/an158.xml create mode 100644 plugins/hal-zwave/config/everspring/se812.xml create mode 100644 plugins/hal-zwave/config/everspring/sf812.xml create mode 100644 plugins/hal-zwave/config/everspring/sm103.xml create mode 100644 plugins/hal-zwave/config/everspring/sp103.xml create mode 100644 plugins/hal-zwave/config/everspring/sp814.xml create mode 100644 plugins/hal-zwave/config/everspring/st814.xml create mode 100644 plugins/hal-zwave/config/everspring/st815.xml create mode 100644 plugins/hal-zwave/config/everspring/tse03.xml create mode 100644 plugins/hal-zwave/config/everspringct/hsm02.xml create mode 100644 plugins/hal-zwave/config/fibaro/fgbs001.xml create mode 100644 plugins/hal-zwave/config/fibaro/fgd211.xml create mode 100644 plugins/hal-zwave/config/fibaro/fgfs101.xml create mode 100644 plugins/hal-zwave/config/fibaro/fgk001.xml create mode 100644 plugins/hal-zwave/config/fibaro/fgms.xml create mode 100644 plugins/hal-zwave/config/fibaro/fgr221.xml create mode 100644 plugins/hal-zwave/config/fibaro/fgrgbwm441.xml create mode 100644 plugins/hal-zwave/config/fibaro/fgrm222.xml create mode 100644 plugins/hal-zwave/config/fibaro/fgs211.xml create mode 100644 plugins/hal-zwave/config/fibaro/fgs221.xml create mode 100644 plugins/hal-zwave/config/fibaro/fgss101.xml create mode 100644 plugins/hal-zwave/config/fibaro/fgwpe.xml create mode 100644 plugins/hal-zwave/config/frostdale/fdn2nxx.xml create mode 100644 plugins/hal-zwave/config/ge/dimmer.xml create mode 100644 plugins/hal-zwave/config/ge/dimmer_module.xml create mode 100644 plugins/hal-zwave/config/ge/relay.xml create mode 100644 plugins/hal-zwave/config/greenwave/powernode1.xml create mode 100644 plugins/hal-zwave/config/greenwave/powernode6.xml create mode 100644 plugins/hal-zwave/config/homeseer/hsm100.xml create mode 100644 plugins/hal-zwave/config/homeseer/ztroller.xml create mode 100644 plugins/hal-zwave/config/honeywell/th8320zw1000.xml create mode 100644 plugins/hal-zwave/config/horstmann/hrt4zw.xml create mode 100644 plugins/hal-zwave/config/intermatic/ca8900.xml create mode 100644 plugins/hal-zwave/config/leviton/rzi10.xml create mode 100644 plugins/hal-zwave/config/leviton/vrcpg.xml create mode 100644 plugins/hal-zwave/config/leviton/vrf01.xml create mode 100644 plugins/hal-zwave/config/leviton/vri06.xml create mode 100644 plugins/hal-zwave/config/leviton/vri10.xml create mode 100644 plugins/hal-zwave/config/manufacturer_specific.xml create mode 100644 plugins/hal-zwave/config/manufacturer_specific.xsd create mode 100644 plugins/hal-zwave/config/northq/nq92021.xml create mode 100644 plugins/hal-zwave/config/options.xml create mode 100644 plugins/hal-zwave/config/options.xsd create mode 100644 plugins/hal-zwave/config/philio/psm02.xml create mode 100644 plugins/hal-zwave/config/rcs/em52-zw.xml create mode 100644 plugins/hal-zwave/config/rcs/pm12-zw.xml create mode 100644 plugins/hal-zwave/config/rcs/therm0005.xml create mode 100644 plugins/hal-zwave/config/rcs/therm0007.xml create mode 100644 plugins/hal-zwave/config/rcs/therm0009.xml create mode 100644 plugins/hal-zwave/config/remotec/zurc.xml create mode 100644 plugins/hal-zwave/config/remotec/zxt-120.xml create mode 100644 plugins/hal-zwave/config/schlagelink/itemp.xml create mode 100644 plugins/hal-zwave/config/trane/TZEMT400AB32MAA.xml create mode 100644 plugins/hal-zwave/config/trane/TZEMT400BB32MAA.xml create mode 100644 plugins/hal-zwave/config/vision/zs5101eu.xml create mode 100644 plugins/hal-zwave/config/vitrum/vitrumBS.xml create mode 100644 plugins/hal-zwave/config/waynedalton/WDTC-20.xml create mode 100644 plugins/hal-zwave/config/wenzhou/tz66d.xml create mode 100644 plugins/hal-zwave/config/wenzhou/tz88.xml create mode 100644 plugins/hal-zwave/config/zwave.me/ZME_06433.xml create mode 100644 plugins/hal-zwave/config/zwave.me/ZME_06436.xml create mode 100644 plugins/hal-zwave/config/zwave.me/ZME_WCD2.xml create mode 100644 plugins/hal-zwave/config/zwave.me/kfob.xml create mode 100644 plugins/hal-zwave/config/zwcfg.xsd create mode 100644 plugins/hal-zwave/config/zwscene.xsd diff --git a/.gitignore b/.gitignore index eb204076..6ea56641 100755 --- a/.gitignore +++ b/.gitignore @@ -2,4 +2,7 @@ /hal.conf /hal.db* build -/lib/zutil-* \ No newline at end of file +/lib/zutil-* +/OZW_Log.txt +/zwscene.xml +/zwcfg*.xml diff --git a/plugins/hal-zwave/config/2gig/ct100.xml b/plugins/hal-zwave/config/2gig/ct100.xml new file mode 100644 index 00000000..e5aa2ba8 --- /dev/null +++ b/plugins/hal-zwave/config/2gig/ct100.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/plugins/hal-zwave/config/2gig/ct30.xml b/plugins/hal-zwave/config/2gig/ct30.xml new file mode 100644 index 00000000..e5aa2ba8 --- /dev/null +++ b/plugins/hal-zwave/config/2gig/ct30.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/plugins/hal-zwave/config/BeNext/1poleswitch.xml b/plugins/hal-zwave/config/BeNext/1poleswitch.xml new file mode 100644 index 00000000..7ecc03c7 --- /dev/null +++ b/plugins/hal-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/plugins/hal-zwave/config/BeNext/2poleswitch.xml b/plugins/hal-zwave/config/BeNext/2poleswitch.xml new file mode 100644 index 00000000..f3e31a72 --- /dev/null +++ b/plugins/hal-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/plugins/hal-zwave/config/BeNext/AlarmSound.xml b/plugins/hal-zwave/config/BeNext/AlarmSound.xml new file mode 100644 index 00000000..ca8e1a19 --- /dev/null +++ b/plugins/hal-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/plugins/hal-zwave/config/BeNext/BuiltinDimmer.xml b/plugins/hal-zwave/config/BeNext/BuiltinDimmer.xml new file mode 100644 index 00000000..791daee2 --- /dev/null +++ b/plugins/hal-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/plugins/hal-zwave/config/BeNext/DoorSensor.xml b/plugins/hal-zwave/config/BeNext/DoorSensor.xml new file mode 100644 index 00000000..c0a5b75e --- /dev/null +++ b/plugins/hal-zwave/config/BeNext/DoorSensor.xml @@ -0,0 +1,44 @@ + + + + + + + + Set all configuration values to default values (factory settings). + + + + Configure what the external contact sends when triggered. + + + + + + Is not used but can still be set and requested. + + + + Is not used but can still be set and requested. + + + + To configure the operating mode. + + + + + + A signed integer to determine the offset of the temperature. + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/BeNext/EnergySwitch.xml b/plugins/hal-zwave/config/BeNext/EnergySwitch.xml new file mode 100644 index 00000000..62d2f583 --- /dev/null +++ b/plugins/hal-zwave/config/BeNext/EnergySwitch.xml @@ -0,0 +1,31 @@ + + + + + + + Set all configuration values to default values (factory settings). + + + The state in what the switch is when power is supplied. + + + + + When the relay is switched it can't be switched again until the configured time has passed. + + + Show the led state compared to the relay state. + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/BeNext/Molite.xml b/plugins/hal-zwave/config/BeNext/Molite.xml new file mode 100644 index 00000000..5bf075bf --- /dev/null +++ b/plugins/hal-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/plugins/hal-zwave/config/BeNext/PluginDimmer.xml b/plugins/hal-zwave/config/BeNext/PluginDimmer.xml new file mode 100644 index 00000000..081bf8d9 --- /dev/null +++ b/plugins/hal-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/plugins/hal-zwave/config/BeNext/TagReader.xml b/plugins/hal-zwave/config/BeNext/TagReader.xml new file mode 100644 index 00000000..70eea409 --- /dev/null +++ b/plugins/hal-zwave/config/BeNext/TagReader.xml @@ -0,0 +1,40 @@ + + + + + + + + Set all configuration values to default values (factory settings). + + + + To configure the time the beep is automatically turned off in seconds. + + + + + + To configure the timeout to wait for a WAKEUP_NO_MORE_INFORMATION before the error beep is automatically sound. The error beeps are fixed 8 beeps shortly after each other. + + + + To configure the number of beeps per second. Every beep is fixed about 10ms. + + + + To configure the operating mode. If any mode other then 3, that value will be reported after a get but will be handled in SW as mode 1. + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/act/lfm20.xml b/plugins/hal-zwave/config/act/lfm20.xml new file mode 100644 index 00000000..71548775 --- /dev/null +++ b/plugins/hal-zwave/config/act/lfm20.xml @@ -0,0 +1,4 @@ + + + + diff --git a/plugins/hal-zwave/config/act/zdm230.xml b/plugins/hal-zwave/config/act/zdm230.xml new file mode 100644 index 00000000..bc6009e5 --- /dev/null +++ b/plugins/hal-zwave/config/act/zdm230.xml @@ -0,0 +1,93 @@ + + + + + + Dimmers controlled by this switch will start dimming from their current level. + + + + + Disable transmitting commands to Z-Wave devices that are in Group 4 without disassociating those devices from the group. + + + + + In night-light mode the LED on the switch will turn ON when the switch is turned OFF. + + + + + Change the top of the switch to OFF and the bottom of the switch to ON. Note: If you invert the switches and also install the product upside down, remember the load will now be controlled by the right, not the left switch. + + + + + This dimmer will start dimming from its current level. + + + + + When you press and hold the bottom of the ZDM230 switch once, the Z-Wave devices that are associated into Group 1 are sent the Dim command. If this parameter is set to "Yes" the devices in Group 1 will not go to the same level as the ZDM230. + + + + + Indicates how many levels the dimmer will change for each dimming step. + + + This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change. + + + Indicates how many levels the dimmer will change for each dimming step. + + + This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change. + + + Indicates how many levels the dimmer will change for each dimming step. + + + This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change. + + + Units in Group 4 only track when the dimmer is being turned ON and OFF and not while dimming. + + + + + The ZDM230 can operate shade control devices via its group 2. + + + + + The ZDM230 can operate shade control devices via its group 3. + + + + + The ZDM230 will flicker its LED when it is transmitting to any of its 4 groups. This flickering can be set to not flicker at all, to flicker the entire time it is transmitting, or to flicker for only 1 second when it begins transmitting. + + + + + + Poll Group 2 Interval + + + Poll Group 2 + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/act/zdw103.xml b/plugins/hal-zwave/config/act/zdw103.xml new file mode 100644 index 00000000..f9f5cf72 --- /dev/null +++ b/plugins/hal-zwave/config/act/zdw103.xml @@ -0,0 +1,69 @@ + + + + + + Dimmers controlled by this switch will start dimming from their current level. + + + + + In night-light mode the LED on the switch will turn ON when the switch is turned OFF. + + + + + Change the top of the switch to OFF and the bottom of the switch to ON. + + + + + This dimmer will start dimming from its current level. + + + + + Indicates how many levels the dimmer will change for each dimming step. + + + This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change. + + + Indicates how many levels the dimmer will change for each dimming step. + + + This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change. + + + Indicates how many levels the dimmer will change for each dimming step. + + + This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change. + + + The ZDW103 can operate shade control devices via its group 2. + + + + + The ZDW103 can operate shade control devices via its group 3. + + + + + The ZDW103 will flicker its LED when it is transmitting to any of its 4 groups. This flickering can be set to not flicker at all, to flicker the entire time it is transmitting, or to flicker for only 1 second when it begins transmitting. + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/act/zdw232.xml b/plugins/hal-zwave/config/act/zdw232.xml new file mode 100644 index 00000000..bdaa1a0c --- /dev/null +++ b/plugins/hal-zwave/config/act/zdw232.xml @@ -0,0 +1,112 @@ + + + + + + +The ZDW232 can send Dim commands to Z-Wave enabled dimmers. The Dim command has a start level embedded +in it. A dimmer receiving this command will start dimming from that start level. However, the command also has a +bit that indicates whether the dimmer should ignore the start level. If the bit is set to 1, the dimmer will ignore the +start level and instead start dimming from its current level. If this bit is set to 0, the dimmer will not ignore the start +level. + + + + + + You may wish to disable transmitting commands to Z-Wave devices that are in Group 4 without "un-associating" +those devices from the group. Setting parameter 2 to the value of 1 will stop the ZDW232 from transmitting to devices +that are "associated" into Group 4. +It is possible that you may only want the units in Group 4 to track when the dimmer is being turned ON and OFF +and not when dimming. + + + + + In night-light mode the LED on the switch will turn ON when the switch is turned OFF. + + + + + To change the top of the switch to OFF and the bottom of the switch to ON, set parameter 4 to 1. + + + + + The ZDW232 can be set to ignore the start level that is part of the dim command, regardless of whether the command +is telling the dimmer to ignore the start level or not ignore the start level embedded in the command (see Parameter +1). Setting parameter 5 to a value of 1 (factory default) will cause the ZDW232 to ignore the start level and to dim +or brighten from its current level. Setting the value to 0 will cause the ZDW232 to dim or brighten from the level in +the command. + + + + + When you press and hold the bottom of the ZDW232 switch once, the Z-Wave devices that areassociated into Group +1 are sent the Dim command. If parameter 6 is set to 0, after you release the switch, the ZDW232 will command +devices in that group to go to the same level of the ZDW232. If parameter 6 is set to a value of 1 (factory default) +the devices in Group 1 will not go to the same level of the ZDW232. + + + + + Indicates how many levels the dimmer will change for each dimming step. + + + This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change. + + + Indicates how many levels the dimmer will change for each dimming step. + + + This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change. + + + Indicates how many levels the dimmer will change for each dimming step. + + + This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change. + + + After the ZDW232 is commanded to stop dimming, it will then command the Z-Wave devices in Group 4 to the +ZDW232's new level. To prevent the ZDW232 from commanding the Z-Wave devices in Group 4 during this particular +occurrence, set Parameter 13 to the value of 1. + + + + + The ZDW232 can operate shade control devices via its group 2 if this configuration parameter is set to 1. + + + + + The ZDW232 can operate shade control devices via its group 3 if this configuration parameter is set to 1. + + + + + The ZDW232 will flicker its LED when it is transmitting to any of its 4 groups. This flickering can be set to not flicker at all, to flicker the entire time it is transmitting, or to flicker for only 1 second when it begins transmitting. + + + + + + Poll Group 2 Interval + + + Poll Group 2 + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/act/zir010.xml b/plugins/hal-zwave/config/act/zir010.xml new file mode 100644 index 00000000..793c5218 --- /dev/null +++ b/plugins/hal-zwave/config/act/zir010.xml @@ -0,0 +1,63 @@ + + + + + + + The ZIR010 can be configured to operate in 1 of 3 modes. + Those modes are: + Lighting Mode (factory default) + Alarm Mode + Sensor Mode + To change the mode of operation: + For Lighting Mode: Send a value of 0 to Configuration Parameter #17. + For Alarm Mode: Send a value of 1 to Configuration Parameter #17. + For Sensor Mode: Send a value of 2 to Configuration Parameter # 17. + Information reproduced from: http://www.pepper1.net/zwavedb/uploads/resources/bdf086a9388325a2fb8b8aa298e24e512faec65d.pdf + + + + + + + + The configuration parameter that can be used to adjust the amount of delay before the OFF or IDLE command is transmitted is Configuration Parameter # 18. + This parameter can be configured with the value of 0 through 255. + Where 0 means no delay and 255 means 255 minutes of delay. + Default appears to be 1 min. + Information reproduced from: http://www.pepper1.net/zwavedb/uploads/resources/bdf086a9388325a2fb8b8aa298e24e512faec65d.pdf + + + + + The ZIR010 can be disabled from sending commands unsolicited without removing associated devices by + setting Configuration Parameter # 19 to 0 (when asked for number of bytes, select 1). + Setting it back to 1 will re-enable the ZIR010. + Information reproduced from: http://www.pepper1.net/zwavedb/uploads/resources/bdf086a9388325a2fb8b8aa298e24e512faec65d.pdf + + + + + + + The time the ZIR010 stays awake can be adjusted from 15 seconds to 45 seconds by sending a value of 15 + to 45 to the ZIR010 using Configuration Parameter # 22 (when asked for the number of bytes, select 1). + This awake time period starts over every time the ZIR010 receives a command or request. + Defaults to 30 seconds. + Information reproduced from: http://www.pepper1.net/zwavedb/uploads/resources/bdf086a9388325a2fb8b8aa298e24e512faec65d.pdf + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/act/zrp110.xml b/plugins/hal-zwave/config/act/zrp110.xml new file mode 100644 index 00000000..d03a09ff --- /dev/null +++ b/plugins/hal-zwave/config/act/zrp110.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/plugins/hal-zwave/config/act/zrw103.xml b/plugins/hal-zwave/config/act/zrw103.xml new file mode 100644 index 00000000..1802bea4 --- /dev/null +++ b/plugins/hal-zwave/config/act/zrw103.xml @@ -0,0 +1,36 @@ + + + + + + Dimmers controlled by this switch will start dimming from their current level. + + + + + In night-light mode the LED on the switch will turn ON when the switch is turned OFF. + + + + + Change the top of the switch to OFF and the bottom of the switch to ON. + + + + + The ZRW103 will flicker its LED when it is transmitting to any of its 4 groups. This flickering can be set to not flicker at all, to flicker the entire time it is transmitting, or to flicker for only 1 second when it begins transmitting. + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/aeon_labs/alms.xml b/plugins/hal-zwave/config/aeon_labs/alms.xml new file mode 100644 index 00000000..53e3f4c5 --- /dev/null +++ b/plugins/hal-zwave/config/aeon_labs/alms.xml @@ -0,0 +1,109 @@ + + + + + + + Stay awake for 10 minutes after batteries are inserted + 0 -> No + 1 -> Yes + + + + + + + How long should the device associated to multi sensor keep + state On before sending it Off command (if the value is bigger + than 255, the value would be rounded to next integer in minutes) + + + + + Enable Motion Sensor + 0 -> Disabled + 1 -> Enabled + + + + + + + Which commands to send when PIR motion sensor triggered + 1 (default) -> Basic Set + 2 -> Binary Sensor Report + + + + + Reset to default parameters number 101-103. Any value other then 0 will initiate this reset. + + + + + Which reports need to send automatically in timing intervals for group 1 + Bitsets: + 0 -> Battery report + 5 -> Temperature + 6 -> Humidity + 7 -> Luminosity + + + + + Which reports need to send automatically in timing intervals for group 2 + Bitsets: + 0 -> Battery report + 5 -> Temperature + 6 -> Humidity + 7 -> Luminosity + + + + + Which reports need to send automatically in timing intervals for group 3 + Bitsets: + 0 -> Battery report + 5 -> Temperature + 6 -> Humidity + 7 -> Luminosity + + + + + Reset to default parameters number 111-113. Any value other then 0 will initiate this reset. + + + + + The interval of sending report group 1. + 1 seconds - 2678400 seconds + + + + + The interval of sending report group 2. + 1 seconds - 2678400 seconds + + + + + The interval of sending report group 3. + 1 seconds - 2678400 seconds + + + + + Reset to factory defaults. + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/aeon_labs/doorwindow.xml b/plugins/hal-zwave/config/aeon_labs/doorwindow.xml new file mode 100644 index 00000000..57427625 --- /dev/null +++ b/plugins/hal-zwave/config/aeon_labs/doorwindow.xml @@ -0,0 +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/plugins/hal-zwave/config/aeon_labs/hem.xml b/plugins/hal-zwave/config/aeon_labs/hem.xml new file mode 100644 index 00000000..befcca64 --- /dev/null +++ b/plugins/hal-zwave/config/aeon_labs/hem.xml @@ -0,0 +1,187 @@ + + + + + + + Voltage to calculate wattage from amperage. US=120. EU,ANZ=240. + + + + + 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). + + + + + Accumulate energy when Battery Powered. + + + + + This byte denotes whether the product is using batteries (value = 0) or using USB power (value = 1). + + + + + 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. + + + + + Re-calibrate (will destroy factory calibration). CONTACT AEON LABS before using. + + + + + Device tag. + + + + + Reset to the default configuration. + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/aeon_labs/hemg2.xml b/plugins/hal-zwave/config/aeon_labs/hemg2.xml new file mode 100644 index 00000000..aa755057 --- /dev/null +++ b/plugins/hal-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/plugins/hal-zwave/config/aeon_labs/keyfob.xml b/plugins/hal-zwave/config/aeon_labs/keyfob.xml new file mode 100644 index 00000000..2498c55b --- /dev/null +++ b/plugins/hal-zwave/config/aeon_labs/keyfob.xml @@ -0,0 +1,59 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/aeon_labs/minimote.xml b/plugins/hal-zwave/config/aeon_labs/minimote.xml new file mode 100644 index 00000000..db5dcc6e --- /dev/null +++ b/plugins/hal-zwave/config/aeon_labs/minimote.xml @@ -0,0 +1,32 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/aeon_labs/recessed_doorsensor.xml b/plugins/hal-zwave/config/aeon_labs/recessed_doorsensor.xml new file mode 100644 index 00000000..8bd8414d --- /dev/null +++ b/plugins/hal-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/plugins/hal-zwave/config/aeon_labs/ses.xml b/plugins/hal-zwave/config/aeon_labs/ses.xml new file mode 100644 index 00000000..cd48eb0c --- /dev/null +++ b/plugins/hal-zwave/config/aeon_labs/ses.xml @@ -0,0 +1,151 @@ + + + + + + + Defines the contents of Multilevel Sensor Report after Multilevel Sensor Get received. + + + + + + + This is actually a double byte value. The LSB defines the total time the device needs to blink in seconds. The MSB defines the on/off interval of the blink in tenths of seconds. + + + + + Enables automatic notifications to associated devices whenever there is a state change. + + + + + + + + Enable/disable Wattage threshold and percent. + + + + + The minimum change in wattage for a report to be sent. + + + + + Minimum change in percent of wattage to send a report. + + + + + Set report types for groups 1, 2 and 3 to default. Reverts to 0 + after set. + + + + + Defines the type of report sent for reporting group 1. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts. + Value 1 (msb) Reserved + Value 2 Reserved + Value 3 Reserved + Value 4 (lsb) bits 7-4 reserved + bit 3 MRC(KWH) + bit 2 MRC(watt) + bit 1 MSRC + bit 0 reserved + + The MRC(KWH) flag signals that Report Group 1 send(1) or don't send(0) + Meter Report Command(KWh) automatically. + + The MRC(Watt) flag signals that Report Group 1 send(1) or don't send(0) + Meter Report Command(wattage) automatically. + + The MSRC flag signals that Report Group 1 send(1) or don't send(0) + Multilevel Sensor Report Command(wattage) automatically. + + + + + Defines the type of report sent for reporting group 2. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts. + Value 1 (msb) Reserved + Value 2 Reserved + Value 3 Reserved + Value 4 (lsb) bits 7-4 reserved + bit 3 MRC(KWH) + bit 2 MRC(watt) + bit 1 MSRC + bit 0 reserved + + The MRC(KWH) flag signals that Report Group 1 send(1) or don't send(0) + Meter Report Command(KWh) automatically. + + The MRC(Watt) flag signals that Report Group 1 send(1) or don't send(0) + Meter Report Command(wattage) automatically. + + The MSRC flag signals that Report Group 1 send(1) or don't send(0) + Multilevel Sensor Report Command(wattage) automatically. + + + + + Defines the type of report sent for reporting group 3. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts. + Value 1 (msb) Reserved + Value 2 Reserved + Value 3 Reserved + Value 4 (lsb) bits 7-4 reserved + bit 3 MRC(KWH) + bit 2 MRC(watt) + bit 1 MSRC + bit 0 reserved + + The MRC(KWH) flag signals that Report Group 1 send(1) or don't send(0) + Meter Report Command(KWh) automatically. + + The MRC(Watt) flag signals that Report Group 1 send(1) or don't send(0) + Meter Report Command(wattage) automatically. + + The MSRC flag signals that Report Group 1 send(1) or don't send(0) + Multilevel Sensor Report Command(wattage) automatically. + + + + + Set time interval for sending reports for groups 1, 2 and 3 to default. + + + + + Defines the time interval when the defined report for group 1 is sent. + + + + + Defines the time interval when the defined report for group 2 is sent. + + + + + Defines the time interval when the defined report for group 3 is sent. + + + + + Device tag. + + + + + Reset to the default configuration. + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/danfoss/living.xml b/plugins/hal-zwave/config/danfoss/living.xml new file mode 100644 index 00000000..daf3fc37 --- /dev/null +++ b/plugins/hal-zwave/config/danfoss/living.xml @@ -0,0 +1,5 @@ + + + + + diff --git a/plugins/hal-zwave/config/danfoss/z.xml b/plugins/hal-zwave/config/danfoss/z.xml new file mode 100644 index 00000000..7d672174 --- /dev/null +++ b/plugins/hal-zwave/config/danfoss/z.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/plugins/hal-zwave/config/device_classes.xml b/plugins/hal-zwave/config/device_classes.xml new file mode 100644 index 00000000..518456c9 --- /dev/null +++ b/plugins/hal-zwave/config/device_classes.xml @@ -0,0 +1,103 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/device_classes.xsd b/plugins/hal-zwave/config/device_classes.xsd new file mode 100644 index 00000000..060cd23c --- /dev/null +++ b/plugins/hal-zwave/config/device_classes.xsd @@ -0,0 +1,44 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/device_configuration.xsd b/plugins/hal-zwave/config/device_configuration.xsd new file mode 100644 index 00000000..2f7e2178 --- /dev/null +++ b/plugins/hal-zwave/config/device_configuration.xsd @@ -0,0 +1,252 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/duwi/ZWES1000.xml b/plugins/hal-zwave/config/duwi/ZWES1000.xml new file mode 100644 index 00000000..9d77fd27 --- /dev/null +++ b/plugins/hal-zwave/config/duwi/ZWES1000.xml @@ -0,0 +1,8 @@ + + + + + + + + diff --git a/plugins/hal-zwave/config/eurotronic/eur_stellaz.xml b/plugins/hal-zwave/config/eurotronic/eur_stellaz.xml new file mode 100644 index 00000000..69036917 --- /dev/null +++ b/plugins/hal-zwave/config/eurotronic/eur_stellaz.xml @@ -0,0 +1,26 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/everspring/an145.xml b/plugins/hal-zwave/config/everspring/an145.xml new file mode 100644 index 00000000..f9891c86 --- /dev/null +++ b/plugins/hal-zwave/config/everspring/an145.xml @@ -0,0 +1,12 @@ + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/everspring/an158.xml b/plugins/hal-zwave/config/everspring/an158.xml new file mode 100644 index 00000000..66a11be0 --- /dev/null +++ b/plugins/hal-zwave/config/everspring/an158.xml @@ -0,0 +1,35 @@ + + + + + + + + + This is the time the switching status needs to remain +unchanged after a change to cause the device to send out a status +message. 0 is Disabled. + + + + + Enable or Disable Send Basic Command to Group 2 when the local +button press changes the switching state. + + + + + The device will report its meter value within the interval +set. Set to 0 will disable the autoreporting function. + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/everspring/se812.xml b/plugins/hal-zwave/config/everspring/se812.xml new file mode 100644 index 00000000..8a7cf5e6 --- /dev/null +++ b/plugins/hal-zwave/config/everspring/se812.xml @@ -0,0 +1,13 @@ + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/everspring/sf812.xml b/plugins/hal-zwave/config/everspring/sf812.xml new file mode 100644 index 00000000..2735fd4d --- /dev/null +++ b/plugins/hal-zwave/config/everspring/sf812.xml @@ -0,0 +1,12 @@ + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/everspring/sm103.xml b/plugins/hal-zwave/config/everspring/sm103.xml new file mode 100644 index 00000000..57b932cf --- /dev/null +++ b/plugins/hal-zwave/config/everspring/sm103.xml @@ -0,0 +1,35 @@ + + + + + + + Defines the level in the event sent when the sensor is triggered. Default is 99 (full brightness for a Z-Wave dimmer). 100-127 will set device on to the last value it was when turned off. + + + + + On Time sets the number of seconds the sensor stays alerted before the off event is sent. + + + + + Enable/Disable power saving mode. 0 enables. + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/everspring/sp103.xml b/plugins/hal-zwave/config/everspring/sp103.xml new file mode 100644 index 00000000..ef2b7641 --- /dev/null +++ b/plugins/hal-zwave/config/everspring/sp103.xml @@ -0,0 +1,39 @@ + + + + + + + + Phase Level of ON Command + The Configuration parameter that can be used to adjust the phase level of ON command is transmitted is Configuration Parameter # 1. + This parameter can be configured with the value of 0 through 127. + Value 0: Set Device OFF(0x00) + Value 1-99: Set Device On (1-99) + Value 100-127: Set Device On to the last phase (0xFF) + Note: 0xFF means the device will be on to the last phase before the device was turned off. + Information reproduced from: http://www.techstyleuk.co.uk/index_files/sp103_manual.pdf + + + + + Enabling/Disabling Power Saving Function (for testing) + When no movement has been detected for 10 seconds, the SP103 will enter the power saving mode. + It can be disabled or enabled power saving function by setting Configuration Parameter # 3. + This parameter can be configured with the value of 0 through 127, where 0 means power saving being enabled and others mean power saving being disabled. + PS : As long as the batteries have been refitted, the Detector will enable the power saving function automatically. + Information reproduced from: http://www.techstyleuk.co.uk/index_files/sp103_manual.pdf + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/everspring/sp814.xml b/plugins/hal-zwave/config/everspring/sp814.xml new file mode 100644 index 00000000..1f95404c --- /dev/null +++ b/plugins/hal-zwave/config/everspring/sp814.xml @@ -0,0 +1,48 @@ + + + + + + + When Basic Set Command is sent where contains a value, the receiver will take it for consideration; for instance, if a lamp module is received the Basic Set Command of which value is decisive as to how bright of dim level of lamp modeule shall be. + + + + + The Detecting function can be Disabled of Enabled. + + + + + 1 Means lowest sensitivity and 10 means highest. + + + + + Adjust the interval of being re-triggered afer the detector has been triggered in seconds. + + + + + Sets minimum Lux Level of ambient illumination neccesary for Motion Detector to trigger. + + + + + The duration determines how long before the module sends an Off after being triggered. + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/everspring/st814.xml b/plugins/hal-zwave/config/everspring/st814.xml new file mode 100644 index 00000000..73b43bf1 --- /dev/null +++ b/plugins/hal-zwave/config/everspring/st814.xml @@ -0,0 +1,56 @@ + + + + + + + Defines the level in the Basic Set event sent to group 2 when the sensor is triggered. Default is 99 (full brightness for a Z-Wave dimmer). 0 disables. + + + + + Temperature level to trigger when a ON command is sent out. 99 will clear the value. + + + + + Temperature level to trigger when an OFF command is sent out. 99 will clear the value. + + + + + Humidity level to trigger when a ON command is sent out. 99 will clear the value. + + + + + Humidity level to trigger when a OFF command is sent out. 99 will clear the value. + + + + + Sets the auto report time interval. 0 disables. + + + + + Sets the auto report temperature trigger interval. 0 disables. + + + + + Sets the auto report humidity trigger interval. 0 disables. + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/everspring/st815.xml b/plugins/hal-zwave/config/everspring/st815.xml new file mode 100644 index 00000000..743b471e --- /dev/null +++ b/plugins/hal-zwave/config/everspring/st815.xml @@ -0,0 +1,48 @@ + + + + + + + Defines the level in the Basic Set event sent to group 2 when the sensor is triggered. Default is 99 (full brightness for a Z-Wave dimmer). 0 disables. + + + + + Lux level to trigger when a ON command is sent out. 0 will clear the value. + + + + + Lux level to trigger when an OFF command is sent out. 0 will clear the value. + + + + + Set Lux timer trigger to send an OFF command. 0 will clear the value. + + + + + Sets the auto report time interval. 0 disables. + + + + + Sets the auto report Lux interval. 0 disabled. + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/everspring/tse03.xml b/plugins/hal-zwave/config/everspring/tse03.xml new file mode 100644 index 00000000..630230b6 --- /dev/null +++ b/plugins/hal-zwave/config/everspring/tse03.xml @@ -0,0 +1,12 @@ + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/everspringct/hsm02.xml b/plugins/hal-zwave/config/everspringct/hsm02.xml new file mode 100644 index 00000000..00cdf9c7 --- /dev/null +++ b/plugins/hal-zwave/config/everspringct/hsm02.xml @@ -0,0 +1,91 @@ + + + + + + + When Basic Set Command is sent where contains a value, the receiver will + take it for consideration; for instance, if a lamp module is received the Basic + Set command of which value is decisive as to how bright of dim level of lamp + module shall be. + + + + + The Configuration parameter that can be used to adjust the amount of delay + before the OFF command is transmitted as Configuration Parameter #2. + This parameter can be configured with the value of 0 through 127, where 0 + means send OFF command immediately and 127 means 127 seconds of + delay + + + + + + + + + Magnets to be opened/closed + + + + + + + + + + + Once the power has been applied, Alarm Report Command will be sent to + Nodes in Grouping 1 to confirm the power applied status for HSM02. + + + + + When HSM02 automatically wakes up, it will check the battery usage. When + low battery is detected, Alarm Report Command will be sent to Nodes in + Grouping 1, afterward, LED will light up for 1 sec to remind user when HSM02 is + triggered due to open or close incidents. + + + + + Grouping 1, afterward, LED will light up for 1 sec to remind user when HSM02 is + triggered due to open or close incidents. + + + + + + + + + The users can also enquire the battery status of the unit by sending + BATTERY_GET command via Z-Wave Controller. Once the unit receives the + command, it will return BATTERY_REPORT command. The unit will send + Battery_Level = 255 (0xFF) command to the Z-Wave Controller to inform that + the unit is in low battery status. + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/fibaro/fgbs001.xml b/plugins/hal-zwave/config/fibaro/fgbs001.xml new file mode 100644 index 00000000..bc3a7d53 --- /dev/null +++ b/plugins/hal-zwave/config/fibaro/fgbs001.xml @@ -0,0 +1,115 @@ + + + + + + + + Input I alarm cancellation delay. Additional delay after an alarm from input IN1 has ceased. The parameter allows you to specify additional time, after which the input no. 1 alarm is cancelled once its violation has ceased. + + + + Input II alarm cancellation delay. Additional delay after an alarm from input IN1 has ceased. The parameter allows you to specify additional time, after which the input no. 1 alarm is cancelled once its violation has ceased. + + + + Type of input no. 1, what the input 1 will report if no contact is made + + + + + + + + Type of input no. 2, what the input 2 will report if no contact is made + + + + + + + + Type of transmitted control frame for association group 1, activated via input IN1. The parameter allows to specify the type of alarm frame or to force transmission of control commands (BASIC_SET) + + + + + + + + + + + Type of transmitted control frame for association group 2, activated via input IN1. 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%. + + + + 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. 2. 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. + + + + Interval between forcing to send report concerning the temperature conditions. The forced report is sent immediately after the next reading of temperature from the sensor, irrespective of the settings of parameter no. 12. Value 0 = Deactivates the function. Note: Frequent sending of temperature condition reports is reasonable when the sensor is located somewhere where can occure rapid changes of ambient temperature. In other cases it is recommended to leave the parameter set to the default value. + + + + 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:0 – 255 [0oC to 16oC] [0 oF – 28.8oF] +In order to set the appropriate value of the parameter, the following formula should be used: +x = delta T x 16 - for Celsius +x = delta T x 80 / 9 - for Fahrenheit +x – parameter value +delta T – maximum acceptable temperature gradient in Celsius or Fahrenheit +If the value is set to 0, then information about the temperature will be sent every time, immediately once the readings have been taken from the sensor. + + + + 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. + + + + + + + + Enable/Disable scene functionality. 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. + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/fibaro/fgd211.xml b/plugins/hal-zwave/config/fibaro/fgd211.xml new file mode 100644 index 00000000..f34d2df8 --- /dev/null +++ b/plugins/hal-zwave/config/fibaro/fgd211.xml @@ -0,0 +1,104 @@ + + + + + + + Activate/Deactive ALL ON/OFF + + + + + + + Activate/Deactivate association sending for group 1 - Note: Parameter 15 must set to 1 to work properly. + + + + + + Key no.2 is not represented by any physical device except of devices on association list. + This functionality prevents of lack of reaction on pressing key no.2 through polling devices + from association list one by one and checking their actual statuses. + + + + + + Options for changing parameter 1-99 + + + Options for changing parameter 1-255 (10ms - 2,5s) + + + + Options for changing parameter 1-255 (10ms - 2,5s) - 0: this value disables the smooth change in light intensity. NOTE: value 0 is required for inductive and capacitive devices unsuitable for dimming (e.g. fluorescent lamps, motors, etc...) + + + Options for changing parameter 1-99 + + + Options for changing parameter 2-99 + + + Options for changing parameter 1-98 + + + Binary inputs type configuration + + + + + Double-click set lighting at 100% + + + + + Saving state before power faillure + + + + + The function of 3-way switch provides the option to double key no. 1. The dimmer may control two bi-stable push-buttons or an infinite number of mono-stable push-buttons. (default value 0) + + + + + The dimmer communicate the level to the associated devices. (default value 0) + + + + + This function allow user to change [On-Off] bi-stable keys (parameter no. 14) (default value 0) + + + + + This function will enable decreasing the minimum level of the Dimmer by extending the control impulse.[100 - 170] + By changing the minimem level, the user may completely dim LED bulbs. + Not all LED bulbs available on the market have the dimmming option. + WARNING: Wrong setting of the function may cause incorrect operation of the Dimmer. + + + Alarm of any type (general alarm, water flooding alarm, smoke alarm: CO, CO2, temperature alarm) défault value 3-alarm flashing + + + + + + + Amount of time the device keeps on flashing after receipt of Alarm Frame (1s-65535s) + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/fibaro/fgfs101.xml b/plugins/hal-zwave/config/fibaro/fgfs101.xml new file mode 100644 index 00000000..4afe8da0 --- /dev/null +++ b/plugins/hal-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/plugins/hal-zwave/config/fibaro/fgk001.xml b/plugins/hal-zwave/config/fibaro/fgk001.xml new file mode 100644 index 00000000..2e346f2d --- /dev/null +++ b/plugins/hal-zwave/config/fibaro/fgk001.xml @@ -0,0 +1,96 @@ + + + + + + + + Input I alarm cancellation delay. Additional delay after an alarm from input IN1 has ceased. The parameter allows you to specify additional time, after which the input no. 1 alarm is cancelled once its violation has ceased. + + + + Status change signalled by LED + Default setting: 1 + Available parameter settings: + 0 - LED turned Off, + 1 - LED turned Onhas ceased. + + + + + Type of input no. 1, what the input 1 will report if no contact is made + + + + + + + + Type of transmitted control frame for association group 1, activated via input IN1. 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. + + + + Interval between forcing to send report concerning the temperature conditions. The forced report is sent immediately after the next reading of temperature from the sensor, irrespective of the settings of parameter no. 12. Value 0 = Deactivates the function. Note: Frequent sending of temperature condition reports is reasonable when the sensor is located somewhere where can occure rapid changes of ambient temperature. In other cases it is recommended to leave the parameter set to the default value. + + + + 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:0 - 255 [0oC to 16oC] [0 oF - 28.8oF] + In order to set the appropriate value of the parameter, the following formula should be used: + x = delta T x 16 - for Celsius + x = delta T x 80 / 9 - for Fahrenheit + x - parameter value + delta T - maximum acceptable temperature gradient in Celsius or Fahrenheit + If the value is set to 0, then information about the temperature will be sent every time, immediately once the readings have been taken from the sensor. + + + + 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. + + + + + + + + Enable/Disable scene functionality. 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. + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/fibaro/fgms.xml b/plugins/hal-zwave/config/fibaro/fgms.xml new file mode 100644 index 00000000..a95da152 --- /dev/null +++ b/plugins/hal-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/plugins/hal-zwave/config/fibaro/fgr221.xml b/plugins/hal-zwave/config/fibaro/fgr221.xml new file mode 100644 index 00000000..3c451384 --- /dev/null +++ b/plugins/hal-zwave/config/fibaro/fgr221.xml @@ -0,0 +1,77 @@ + + + + + + + + + + + + + + + + + + + + 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. + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/fibaro/fgrgbwm441.xml b/plugins/hal-zwave/config/fibaro/fgrgbwm441.xml new file mode 100644 index 00000000..83e597b4 --- /dev/null +++ b/plugins/hal-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/plugins/hal-zwave/config/fibaro/fgrm222.xml b/plugins/hal-zwave/config/fibaro/fgrm222.xml new file mode 100644 index 00000000..2a47827a --- /dev/null +++ b/plugins/hal-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/plugins/hal-zwave/config/fibaro/fgs211.xml b/plugins/hal-zwave/config/fibaro/fgs211.xml new file mode 100644 index 00000000..09b92156 --- /dev/null +++ b/plugins/hal-zwave/config/fibaro/fgs211.xml @@ -0,0 +1,104 @@ + + + + + + + Activate/Deactive ALL ON/OFF + + + + + + + + Activate/Deactivate Automatic turning off relay after set time + + + + + + + + Automatic turning off relay 1 after set time, in 10ms increments (default: 200ms) + + + + Activate/Deactivate association sending for group 1 - Also see param #15 + + + + + + + In case of bi-stable switches, define their behaviour (toggle or follow) + + + + + + Binary inputs type configuration + + + + + + Enable/Disable opoeration of dimmer or roller shutter devices associated to group 1. + Available only when using mono-stable inputs (buttons) - Hold button 1 or double-tap for operation + + + + + + Saving state before power faillure + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Amount of time (ms) the device keeps on flashing after receipt of Alarm Frame + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/fibaro/fgs221.xml b/plugins/hal-zwave/config/fibaro/fgs221.xml new file mode 100644 index 00000000..ccdc5672 --- /dev/null +++ b/plugins/hal-zwave/config/fibaro/fgs221.xml @@ -0,0 +1,150 @@ + + + + + + + Activate/Deactive ALL ON/OFF + + + + + + + + Activate/Deactivate Automatic turning off relay after set time + + + + + + + + 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) + + + + Activate/Deactivate association sending for group 1 - Also see param #16 + + + + + + + Key no.2 is not represented by any physical device except of devices on association list. + This functionality prevents of lack of reaction on pressing key no.2 through polling devices + from association list one by one and checking their actual statuses. + + + + + + + In case of bi-stable switches, define their behaviour (toggle or follow) + + + + + + Binary inputs type configuration + + + + + + Enable/Disable opoeration of dimmer or roller shutter devices associated to group 1. + Available only when using mono-stable inputs (buttons) - Hold button 1 or double-tap for operation + + + + + + Saving state before power faillure + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Amount of time (ms) the device keeps on flashing after receipt of Alarm Frame + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/fibaro/fgss101.xml b/plugins/hal-zwave/config/fibaro/fgss101.xml new file mode 100644 index 00000000..f34070f7 --- /dev/null +++ b/plugins/hal-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/plugins/hal-zwave/config/fibaro/fgwpe.xml b/plugins/hal-zwave/config/fibaro/fgwpe.xml new file mode 100644 index 00000000..0bbad057 --- /dev/null +++ b/plugins/hal-zwave/config/fibaro/fgwpe.xml @@ -0,0 +1,246 @@ + + + + + + + + + + + + + + + + + Once activated, Wall Plug will keep a connected device constantly + ON, will stop reacting to alarm frames and B-button push. + "Always on" function turns the Plug into a power and energy meter. + Also, connected device will not be turned off upon receiving an alarm + frame from another Z-Wave device (parameter 35 will be ignored). + In "Always on" mode, connected device may be turned off only after + user defined power has been exceeded (parameter 70). In such a + case, connected device can be turned on again by pushing the + B-button or sending a control frame. By default, overload protection + is inactive. Default setting: 1 + + + + + + + Define how will the Plug react after the power supply is back on. Default setting: 1 + + + + + + + Type of transmitted control frame for association group 1, activated via input IN1. The parameter allows to specify the type of alarm frame or to force transmission of control commands (BASIC_SET) + + + + + + + + + + + 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. + 2 - turn off connected device. LED ring signals an alarm through + defined time period (parameter 39) or untill the alarm is cancelled. + 3 - cyclically change device state, each 1second. In alarm mode Wall + Plug does not report status change, power changes, ignores alarm + frames. After the defined time period has passed (parameter 39) or + after the alarm cancellation, connected device is set to the previous + state. + Parameter: 1[byte] + NOTE: + If "always on" function is active (parameter 1), this parameter's + settings are ignored. + + + + + + + + + + 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. + + + + Parameter defines by how much power load must change, in + percents, to be reported to the main controller, with the highest + priority in the Z-Wave network. By default, Fibaro Wall Plug + immediately sends power report if the power load changes by 80%. + Default setting: 80 (%) + + + + + Parameter defines by how much power load must change, in + percents, to be reported to the main controller. By default, Fibaro + Wall Plug sends power report if the power load changes by 15%. + By default such changes in power load may be reported up to 5 times + per 30 seconds. Wall Plug sends 5 reports during time period + specified in paramater 43. Default setting: 15 (%) + + + + This parameter defines how frequently standard power reports + (parameter 42) will be sent. By default Wall Plug sends up to 5 + reports each 30 seconds, provided the power load changes by 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 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. + Default setting: 3 600 (s), Available settings: 1 - 65534 (s) + Value of 65535 - no periodic reports. Reports will be sent only in + case of power load / energy consumption changes (parameters 40, 42, 43,45) or in case of polling. + + + + 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. + + + + + Parameter deifines the way 2nd association group devices are controlled, depending on the current power load. + Default setting: 6 Available settings: + 0 - function inactive, + 1 - turn the associated devices on, once the power drops below + DOWN value (parameter 50), + 2 - turn the associated devices off, once the power drops below + DOWN value (parameter 50), + 3 - turn the associated devices on, once the power rises above UP + value (parameter 51), + 4 - turn the associated devices off, once the power rises above UP + value (parameter 51), + 5 - 1 and 4 combined. Turn the associated devices on, once the + power drops below DOWN value (parameter 50). Turn the + associated devices off, once the power rises above UP value + (parameter 51). + 6 - 2 and 3 combined. Turn the associated devices off, once the + power drops below DOWN value (parameter 50). Turn the + associated devices on, once the power rises above UP value + (parameter 51). + + + + + + + + + + + + + + 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). + + + + 0 - LED ring illumination colour changes in predefined steps, depending on power consumption changes, + 1 - LED ring illumination colour changes continuously, using full spectrum of available colorus, depending on power consumption changes. + 2 - White illumination, + 3 - Red illumination, + 4 - Green illumination, + 5 - Blue illumination, + 6 - Yellow illumination, + 7 - Cyan illumination, + 8 - Magenta illumination, + 9 - illumination turned off completely + + + + + + + + + + + + + + + + + + + + Default setting: 1 + 0 - No change in colour. LED ring illumination colour determined by parameters 61 or 62 settings, + 1 - LED ring flashes red / blue / white (default), + 2 - White illumination, + 3 - Red illumination, + 4 - Green illumination, + 5 - Blue illumination, + 6 - Yellow illumination, + 7 - Cyan illumination, + 8 - Magenta illumination, + 9 - illumination turned off completely. + + + + + + + + + + + + + + + + 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. + Default setting: 65 535 (6 553,5W) + Available settings: 10 - 65 535 (1W - 6 553,5W). + Value higher than 32 000 (3 200W) turns the overload safety switch + off, i.e. this functionality is turned off by default. + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/frostdale/fdn2nxx.xml b/plugins/hal-zwave/config/frostdale/fdn2nxx.xml new file mode 100644 index 00000000..da565ab6 --- /dev/null +++ b/plugins/hal-zwave/config/frostdale/fdn2nxx.xml @@ -0,0 +1,5 @@ + + + + + diff --git a/plugins/hal-zwave/config/ge/dimmer.xml b/plugins/hal-zwave/config/ge/dimmer.xml new file mode 100644 index 00000000..2dd655bf --- /dev/null +++ b/plugins/hal-zwave/config/ge/dimmer.xml @@ -0,0 +1,40 @@ + + + + + + In night-light mode the LED on the switch will turn ON when the switch is turned OFF. + + + + + Change the top of the switch to OFF and the bottom of the switch to ON. Note: If you invert the switches and also install the product upside down, remember the load will now be controlled by the right, not the left switch. + + + + + This dimmer will start dimming from its current level. + + + + + Indicates how many levels the dimmer will change for each dimming step. + + + This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change. + + + Indicates how many levels the dimmer will change for each dimming step. + + + This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change. + + + Indicates how many levels the dimmer will change for each dimming step. + + + This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change. + + + + diff --git a/plugins/hal-zwave/config/ge/dimmer_module.xml b/plugins/hal-zwave/config/ge/dimmer_module.xml new file mode 100644 index 00000000..937a5056 --- /dev/null +++ b/plugins/hal-zwave/config/ge/dimmer_module.xml @@ -0,0 +1,35 @@ + + + + + + Turn on the module when the attached load is connected + + + + + This dimmer will start dimming from its current level. + + + + + Indicates how many levels the dimmer will change for each dimming step. + + + This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change. + + + Indicates how many levels the dimmer will change for each dimming step. + + + This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change. + + + Indicates how many levels the dimmer will change for each dimming step. + + + This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change. + + + + diff --git a/plugins/hal-zwave/config/ge/relay.xml b/plugins/hal-zwave/config/ge/relay.xml new file mode 100644 index 00000000..207df8b8 --- /dev/null +++ b/plugins/hal-zwave/config/ge/relay.xml @@ -0,0 +1,17 @@ + + + + + + In night-light mode the LED on the switch will turn ON when the switch is turned OFF. + + + + + Change the top of the switch to OFF and the bottom of the switch to ON. Note: If you invert the switches and also install the product upside down, remember the load will now be controlled by the right, not the left switch. + + + + + + diff --git a/plugins/hal-zwave/config/greenwave/powernode1.xml b/plugins/hal-zwave/config/greenwave/powernode1.xml new file mode 100644 index 00000000..9327dc6a --- /dev/null +++ b/plugins/hal-zwave/config/greenwave/powernode1.xml @@ -0,0 +1,30 @@ + + + + + + + After how many minutes the GreenWave device should start flashing if the controller didn't communicate with this device + + + + The room color (Corner wheel color) on the GreenWave device + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/greenwave/powernode6.xml b/plugins/hal-zwave/config/greenwave/powernode6.xml new file mode 100644 index 00000000..6a979db6 --- /dev/null +++ b/plugins/hal-zwave/config/greenwave/powernode6.xml @@ -0,0 +1,31 @@ + + + + + + + After how many minutes the GreenWave device should start flashing if the controller didn't communicate with this device + + + + The room color (Corner wheel color) on the GreenWave device + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/homeseer/hsm100.xml b/plugins/hal-zwave/config/homeseer/hsm100.xml new file mode 100644 index 00000000..dc4bcdcd --- /dev/null +++ b/plugins/hal-zwave/config/homeseer/hsm100.xml @@ -0,0 +1,108 @@ + + + + + + + Parameter #0 is undocumented: let us know if you know what it does! + Attributes (type, units, min and max) are wild guesses, except default value. + + + + + Sensitivity sets the amount of motion required for the device to + detect motion. A higher value makes it more sensitive and a + lower value makes it less sensitive. Note that values above 200 + are not recommended when the device is battery operated. + Recommended values: + 10 = Pet Immune. + 100 = Medium sensitivity for hallways. + 200(default) = Highly sensitive for rooms where people are sitting still. + + + + + On Time sets the number of minutes that the lights stay on when + motion has not been detected. + A value of 0 On Time is a special mode where the lights are + constantly sent a command to turn them on whenever motion is + detected. The device will NOT turn the lights off in this mode. + Note that this mode will significantly shorten battery life. + Recommended values: + 5 min for hallways. + 20 min for an office environment. + 60 min for a library or other room where someone may be sitting + still for a long time. + This may be inaccurate, but default for Homeseer HSM100 may actually be 3 minutes, instead of 20? + + + + + LED ON/OFF turns the LED on or off. A slight improvement in + battery life is obtained by turning the LED off. Setting LED + ON/OFF to zero will turn the LED off and 255 turns it on. + Default is On (255). + + + + + + + Light Threshold is the percentage of light in the room above + which the lights will not be turned on. Light Threshold is often + used in room with a lot of natural daylight. Setting Light + Threshold to a value of 50% will cause the device to not turn the + lights on when the natural light in the room is already at the 50% + value. This feature only prevents the lights from coming on when + motion is first detected and the light level in the room is already + above Light Threshold. It will not turn the lights off when the + amount of natural light in the room increases. It will + automatically turn on the lights in a room that has motion in it + and that the amount of natural light has dropped below Light + Threshold. + A value of 100% turns off this feature (default). + Recommended values: + Usually a value between 40% and 60% will prevent the lights + from coming on in a reasonably well light room and will turn + them on as it is getting dark. Some experimentation is required + with each room to determine the proper setting. + + + + + Setting Stay Awake to a non-zero value will cause the device to + always be awake. NOTE: this mode should NOT be used when + the device is battery powered! Batteries will only last a few days + in this mode. + Stay Awake is NOT set to the factory default (0) when the device + is Excluded (reset) from the Z-Wave network. + Setting Stay Awake to a non-zero value will cause the Z-Wave + Listening Bit to be set. The device will become a routing node in + the Z-Wave Mesh-Network when the Listening Bit is set. + To properly have the device included in the routing tables, set + Stay Awake to a non-zero value, then reset the device (Exclude + from the network), then add it back to the network. The new + routing information will be used now that the listening bit is set. + Defaults to 0. + + + + + On Value is the value sent by the Z-Wave BASIC_SET + command when motion is detected. + A value of 0 will turn the lights off (not recommended). + A value between 1 and 100 will set the dim level to between 1% + and 100%. + A value of 255 will turn the light on (default). + NB! According to the manual, the value should not be set between 101-254 (inclusive). + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/homeseer/ztroller.xml b/plugins/hal-zwave/config/homeseer/ztroller.xml new file mode 100644 index 00000000..5524ffcd --- /dev/null +++ b/plugins/hal-zwave/config/homeseer/ztroller.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/plugins/hal-zwave/config/honeywell/th8320zw1000.xml b/plugins/hal-zwave/config/honeywell/th8320zw1000.xml new file mode 100644 index 00000000..13d23c95 --- /dev/null +++ b/plugins/hal-zwave/config/honeywell/th8320zw1000.xml @@ -0,0 +1,5 @@ + + + + + diff --git a/plugins/hal-zwave/config/horstmann/hrt4zw.xml b/plugins/hal-zwave/config/horstmann/hrt4zw.xml new file mode 100644 index 00000000..7295165e --- /dev/null +++ b/plugins/hal-zwave/config/horstmann/hrt4zw.xml @@ -0,0 +1,48 @@ + + + + + + + + + + + + + + + + + + + 0-127 = Disabled. + 128-255 = Enabled. + + + + + 0-127 = Celsius. + 128-255 = Fahrenheit. + + + + + Delta T in steps of 0.1 degree. + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/intermatic/ca8900.xml b/plugins/hal-zwave/config/intermatic/ca8900.xml new file mode 100644 index 00000000..e5aa2ba8 --- /dev/null +++ b/plugins/hal-zwave/config/intermatic/ca8900.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/plugins/hal-zwave/config/leviton/rzi10.xml b/plugins/hal-zwave/config/leviton/rzi10.xml new file mode 100644 index 00000000..65223f0a --- /dev/null +++ b/plugins/hal-zwave/config/leviton/rzi10.xml @@ -0,0 +1,5 @@ + + + + + diff --git a/plugins/hal-zwave/config/leviton/vrcpg.xml b/plugins/hal-zwave/config/leviton/vrcpg.xml new file mode 100644 index 00000000..65223f0a --- /dev/null +++ b/plugins/hal-zwave/config/leviton/vrcpg.xml @@ -0,0 +1,5 @@ + + + + + diff --git a/plugins/hal-zwave/config/leviton/vrf01.xml b/plugins/hal-zwave/config/leviton/vrf01.xml new file mode 100644 index 00000000..65223f0a --- /dev/null +++ b/plugins/hal-zwave/config/leviton/vrf01.xml @@ -0,0 +1,5 @@ + + + + + diff --git a/plugins/hal-zwave/config/leviton/vri06.xml b/plugins/hal-zwave/config/leviton/vri06.xml new file mode 100644 index 00000000..65223f0a --- /dev/null +++ b/plugins/hal-zwave/config/leviton/vri06.xml @@ -0,0 +1,5 @@ + + + + + diff --git a/plugins/hal-zwave/config/leviton/vri10.xml b/plugins/hal-zwave/config/leviton/vri10.xml new file mode 100644 index 00000000..65223f0a --- /dev/null +++ b/plugins/hal-zwave/config/leviton/vri10.xml @@ -0,0 +1,5 @@ + + + + + diff --git a/plugins/hal-zwave/config/manufacturer_specific.xml b/plugins/hal-zwave/config/manufacturer_specific.xml new file mode 100644 index 00000000..2df5f5a5 --- /dev/null +++ b/plugins/hal-zwave/config/manufacturer_specific.xml @@ -0,0 +1,483 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/manufacturer_specific.xsd b/plugins/hal-zwave/config/manufacturer_specific.xsd new file mode 100644 index 00000000..f63524e7 --- /dev/null +++ b/plugins/hal-zwave/config/manufacturer_specific.xsd @@ -0,0 +1,34 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/northq/nq92021.xml b/plugins/hal-zwave/config/northq/nq92021.xml new file mode 100644 index 00000000..3c61f62a --- /dev/null +++ b/plugins/hal-zwave/config/northq/nq92021.xml @@ -0,0 +1,54 @@ + + + + + + + How many pulses are counted per 10 kWh. + + + + Defines the type of sensor. + + + + + + Additional time for feedback measurement.Should always be 0. + + + + Adjusts transmit signal so received signal will in average be equal to this values. Auto calibration might select another value than this. + + + + Wake device up this many times per second. This value also controls number of measurements per second on mechanical meters. + + + + Do not use. Set this value using WAKE_UP_INTERVAL_SET instead. + + + + Current pulse count in device (pulse count / pulse factor = kWh). + + + + How many 'ticks' before going back to sleep in normal wakeup mode. + + + + Set this to enter real-time mode from remote. Contains seconds * poll frequency before going back to sleep. If you press the button once this value will be set. + + + + + + + + + diff --git a/plugins/hal-zwave/config/options.xml b/plugins/hal-zwave/config/options.xml new file mode 100644 index 00000000..84a0786d --- /dev/null +++ b/plugins/hal-zwave/config/options.xml @@ -0,0 +1,10 @@ + + + + diff --git a/plugins/hal-zwave/config/options.xsd b/plugins/hal-zwave/config/options.xsd new file mode 100644 index 00000000..a11dabc1 --- /dev/null +++ b/plugins/hal-zwave/config/options.xsd @@ -0,0 +1,22 @@ + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/philio/psm02.xml b/plugins/hal-zwave/config/philio/psm02.xml new file mode 100644 index 00000000..672438c6 --- /dev/null +++ b/plugins/hal-zwave/config/philio/psm02.xml @@ -0,0 +1,121 @@ + + + + + + + + + Setting the BASIC command value to turn on the light. The 0xFF (255) means turn on the light. + For dimmer equipment 1 to 100 means the light strength. + + + + + + PIR sensitivity settings. + 0 means disable the PIR motion. + 1 means the lowest sensitivity. + 99 means the highest sensitivity. + High sensitivity means can detect long distance, but if there is more noise signal in the environment, it will re-trigger too frequently. + + + + + + Setting the illummination threshold to turn on the light. When the event triggered and the environment illumination lower then + the threshold, the device will turn on the light. + 0 means turn off illumination detected function and never turn on the light. + 1 means darkest. + 99 means brightest. + 100 means turn off illumination detected function. And always turn on the light. + * Notice * in none test mode, only the value in 1 to 99 will enable the illumination detected function and update the illumination value. + + + + + + Bit 0: 1 means security mode; 0 means home automation mode. + Bit 1: 1 means enable test mode; 0 means disable test mode + * Notice * Bit 0 and bit 1 will effect when the DIP Switch setting to program mode. If bit1 is enabled, the bit0 is useless. + Bit 2: Reserved, always 1. + Bit 3: Setting the temperature scale; 0: Fahrenheit, 1:Celsius + Bit 4: Disable illumination report after event triggered. + Bit 5: Disable temperature report after event triggered + + + + + + Multi-Sensor Function switch. Using bit to control. + Bit 0: Reserved, always 1. + Bit 1: Disable PIR integrate Illumination. + Bit 2: Reserved, always 1. + Bit 3: Reserved. + Bit 4: Reserved. + Bit 5: Reserved. + Bit 6: Enable temperature monitoring. When this bit enabled, the temperature changed 3 degree Fahrenheit, it will report. + And also the temperature over 140 degree Fahrenheit, it will report every 64 seconds. + + + + + + In the security mode, after the PIR report motion detected, setting the re-detect time. 8 seconds per tick, and minimum time is 24 seconds, default tick is 3 (24 seconds). + Setting the suitable value to prevent received the trigger signal too frequency. Also can save the battery energy. + * Notice * If this value bigger than the configuration setting NO. 9. There is a period after the light turned off and the PIR not detecting. + + + + + + After turn on the light, setting the delay time to turn off the light when the PIR motion is not detected. + 8 seconds per tick, and minimum time is 32 seconds, default tick is 4 (32 seconds). + + + + + + The interval time for auto report the battery level. + 30 minutes per tick and minimum time is 30 minutes, default tick is 12 (6 hours) + + + + + + The interval time for auto report the illumination. + 30 minutes per tick and minimum time is 30 minutes, default tick is 12 (6 hours) + + + + + + The interval time for auto report the temperature. + 30 minutes per tick and minimum time is 30 minutes, default tick is 12 (6 hours) + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/plugins/hal-zwave/config/rcs/em52-zw.xml b/plugins/hal-zwave/config/rcs/em52-zw.xml new file mode 100644 index 00000000..9c113338 --- /dev/null +++ b/plugins/hal-zwave/config/rcs/em52-zw.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/plugins/hal-zwave/config/rcs/pm12-zw.xml b/plugins/hal-zwave/config/rcs/pm12-zw.xml new file mode 100644 index 00000000..dc186b33 --- /dev/null +++ b/plugins/hal-zwave/config/rcs/pm12-zw.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/plugins/hal-zwave/config/rcs/therm0005.xml b/plugins/hal-zwave/config/rcs/therm0005.xml new file mode 100644 index 00000000..18919dee --- /dev/null +++ b/plugins/hal-zwave/config/rcs/therm0005.xml @@ -0,0 +1,22 @@ + + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/rcs/therm0007.xml b/plugins/hal-zwave/config/rcs/therm0007.xml new file mode 100644 index 00000000..fbc87073 --- /dev/null +++ b/plugins/hal-zwave/config/rcs/therm0007.xml @@ -0,0 +1,39 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/rcs/therm0009.xml b/plugins/hal-zwave/config/rcs/therm0009.xml new file mode 100644 index 00000000..50e17841 --- /dev/null +++ b/plugins/hal-zwave/config/rcs/therm0009.xml @@ -0,0 +1,6 @@ + + + + + + diff --git a/plugins/hal-zwave/config/remotec/zurc.xml b/plugins/hal-zwave/config/remotec/zurc.xml new file mode 100644 index 00000000..9759a248 --- /dev/null +++ b/plugins/hal-zwave/config/remotec/zurc.xml @@ -0,0 +1,27 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/remotec/zxt-120.xml b/plugins/hal-zwave/config/remotec/zxt-120.xml new file mode 100644 index 00000000..04e2b931 --- /dev/null +++ b/plugins/hal-zwave/config/remotec/zxt-120.xml @@ -0,0 +1,5 @@ + + + + + diff --git a/plugins/hal-zwave/config/schlagelink/itemp.xml b/plugins/hal-zwave/config/schlagelink/itemp.xml new file mode 100644 index 00000000..a6748ecf --- /dev/null +++ b/plugins/hal-zwave/config/schlagelink/itemp.xml @@ -0,0 +1,31 @@ + + + + + + + + Attention: This will delete all your configuration, but the device will remain in the network. Handle with care. + + + + + + Configure what the external contact sends when trigger + + + + + + Definesif the sensor is in normal –wakeup- mode or always on. This function shall be used only for testing since it draining the battery very fast. + + + + + + Offset to the temperature. This parameter can be used to calibrate the temperature sensor function if needed. Note. As factory default the temperature sensor function is calibrated. 0 = 0K (default), not 0 = Temperature Offset in K + + + + + diff --git a/plugins/hal-zwave/config/trane/TZEMT400AB32MAA.xml b/plugins/hal-zwave/config/trane/TZEMT400AB32MAA.xml new file mode 100644 index 00000000..97f84e2a --- /dev/null +++ b/plugins/hal-zwave/config/trane/TZEMT400AB32MAA.xml @@ -0,0 +1,955 @@ + + + + + + + + + + 0 = Gas/Elec, 1 = HeatPump + + + + + 0 = Gas, 1 = Elec + + + + + 0 = w/Cool, 1 = w/Heat + + + + + 0 = C, 1 = F + + + + + + + + + 0 = Unlocked, 1 = Locked + + + + + Sets the minimum off time before another heating/cooling cycle can begin to provide compressor short cycle protection. The thermostat screen will display WAIT when minimum off time is being enforced. + + + + + Sets the minimum run time before a heating/cooling cycle can turn off to prevent rapid cycling. Thermostat screen will display "Cool ON" or "Heat ON" while the minimum run time is being enforced. + + + + + Sets the delta from setpoint that stage 1 heating starts. + + + + + Sets the delta from setpoint that stage 1 heating stops. Stage 1 turns off at setpoint minus (-) Delta Stage 1. + + + + + Sets the delta from setpoint that stage 2 heating starts. + + + + + Sets the delta from setpoint that stage 2 heating stops. Stage 1 turns off at setpoint minus (-) Delta Stage 2. + + + + + Sets the delta from setpoint that stage 3 heating starts. + + + + + Sets the delta from setpoint that stage 3 heating stops. Stage 1 turns off at setpoint minus (-) Delta Stage 3. + + + + + Sets the delta from setpoint that stage 1 cooling starts. + + + + + Sets the delta from setpoint that stage 1 cooling stops. Stage 1 turns off at setpoint minus (-) Delta Stage 1. + + + + + Sets the delta from setpoint that stage 2 cooling starts. + + + + + Sets the delta from setpoint that stage 2 cooling stops. Stage 1 turns off at setpoint minus (-) Delta Stage 2. + + + + + + + + + + + + + Sets the minimum separation between the heating and cooling setpoints. Attempts to lower the cooling below the heating setpoint by this amount will PUSH the heating setpoint down to maintain this separation. Same for setting the heating setpoint above the cooling setpoint, it will PUSH the cooling setpoint up to maintain this separation. Settings in F. + + + + + 0 = No Setback, 1 = Setback, 2 if ESM + + + + + + + + + + + + + + + + + Energy Saving Mode (ESM) Setpoints are the setpoints used when the Energy Saving Mode schedule is selected in the Schedule Mode screen (or via Z-Wave control). Setting in F. + + + + + Energy Saving Mode (ESM) Setpoints are the setpoints used when the Energy Saving Mode schedule is selected in the Schedule Mode screen (or via Z-Wave control). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The fan cycler function cycles the HVAC system fan for an ON period followed by an OFF period continuously. Used to provide minimum air ventilation requirements. When the Fan ON time is set to a value greater than 0, an additional Cycler Fan mode is present when pressing the FAN button on the thermostat. + + + + + The fan cycler function cycles the HVAC system fan for an ON period followed by an OFF period continuously. Used to provide minimum air ventilation requirements. When the Fan ON time is set to a value greater than 0, an additional Cycler Fan mode is present when pressing the FAN button on the thermostat. + + + + + 0 = no 2nd stage heat, 1 = 2nd stage heat. + + + + + 0 = no aux heat, 1 = aux heat enabled. + + + + + 0 = no 2nd stage cool, 1 = 2nd stage cool + + + + + + + + + + + + + + + + + + + + + Set to 1 if running schedule (RUN is displayed on the thermostat screen). + + + + + + + + + Default: + HOLD 80F / 26C + RUN 84F / xxC + ESM + + + + + + + + + Heating 1 Setpoint (does this vary with ESM, etc. or is this for the "Hold" setting? + Default: + HOLD 55F / 13C + RUN 60F / xxC + ESM 64F / xxC (unless parameter xx has been changed) + + + + + Backlight Timeout is the time (in seconds) from the last + button press to the backlight going out. The time-out + can be set between 0 and 120 + seconds. When set to 0, the backlight will remain + always on. + Default: 30 + + + + + Sets the maximum heating setpoint value. Will not ramp + or accept setpoints higher than this maximum. + Minimum: 55F / xxC + Maximum: 90F / xxC + Default: 90F / 32C + + + + + Sets the minimum cooling setpoint value. Will not ramp + or accept setpoints lower than this minimum. + Minimum: 60F / xxC + Maximum: 99F / xxC + Default: 60F / 15C + + + + + + + + + This is the time before any screen reverts to the Minimized + Screen (temperature display only), after you stop pushing + buttons. Minimized Screen feature is disabled by setting this + time to 0. + Default: 0 + + + + + + + + + The internal temperature sensor can be calibrated to report + values different from its actual reading. The offset can + range from -7 degrees to +7 degrees. + Default: 0 + + + + + + + + + + + + + + + + + + + + + The Screen Contrast sets the contrast level of the LCD display. + The contrast can be set between 0 and 20. If the display + is too light, use a higher number. If dark lines appear on + the screen, use a lower number. + Default: 10 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 0x2c after reset + 0xf4 after reset + + + + + 0x2c after reset + 0xf4 after reset + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 0xb8 after reset + 0xe4 after reset + + + + + 0xb8 after reset + 0xe4 after reset + + + + + When enabled (set to 1), the local thermostat's scheduler + function is enabled. + Default: 0 + + + + + + + + + + + + + + + + + + + + + 0xff after reset + + + + + + + + + + + + + 0xff after reset + + + + + + + + + + + + + 0xff after reset + + + + + + + + + + + + + 0xff after reset + + + + + + + + + + + + + 0xff after reset + + + + + + + + + + + + + 0xff after reset + + + + + + + + + + + + + 0xff after reset + + + + + + + + + + + + + Recovery enable? + Default: 1 + 0x00 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This value holds information about the first schedule + setpoints for Sundays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x06004643 06:00AM 70F / 67F + 0x06001519 06:00AM 21C / 25C + + + + + This value holds information about the second schedule + setpoints for Sundays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x08003e55 08:00AM 62F / 85F + 0x0800101d 08:00AM 16C / 29C + + + + + This value holds information about the third schedule + setpoints for Sundays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x1200464e 06:00PM 70F / 78F + 0x12001519 06:00PM 21C / 25C + + + + + This value holds information about the fourth schedule + setpoints for Sundays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x16003e52 10:00PM 62F / 82F + 0x1600101b 10:00PM 16C / 27C + + + + + This value holds information about the first schedule + setpoints for Mondays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x06004643 06:00AM 70F / 67F + 0x06001519 06:00AM 21C / 25C + + + + + This value holds information about the second schedule + setpoints for Mondays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x08003e55 08:00AM 62F / 85F + 0x0800101d 08:00AM 16C / 29C + + + + + This value holds information about the third schedule + setpoints for Mondays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x1200464e 06:00PM 70F / 78F + 0x12001519 06:00PM 21C / 25C + + + + + This value holds information about the fourth schedule + setpoints for Mondays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x16003e52 10:00PM 62F / 82F + 0x1600101b 10:00PM 16C / 27C + + + + + This value holds information about the first schedule + setpoints for Tuesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x06004643 06:00AM 70F / 67F + 0x06001519 06:00AM 21C / 25C + + + + + This value holds information about the second schedule + setpoints for Tuesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x08003e55 08:00AM 62F / 85F + 0x0800101d 08:00AM 16C / 29C + + + + + This value holds information about the third schedule + setpoints for Tuesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x1200464e 06:00PM 70F / 78F + 0x12001519 06:00PM 21C / 25C + + + + + This value holds information about the fourth schedule + setpoints for Tuesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x16003e52 10:00PM 62F / 82F + 0x1600101b 10:00PM 16C / 27C + + + + + This value holds information about the first schedule + setpoints for Wednesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x06004643 06:00AM 70F / 67F + 0x06001519 06:00AM 21C / 25C + + + + + This value holds information about the second schedule setpoints for Wednesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x08003e55 08:00AM 62F / 85F + 0x0800101d 08:00AM 16C / 29C + + + + + This value holds information about the third schedule setpoints for Wednesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x1200464e 06:00PM 70F / 78F + 0x12001519 06:00PM 21C / 25C + + + + + This value holds information about the fourth schedule setpoints for Wednesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x16003e52 10:00PM 62F / 82F + 0x1600101b 10:00PM 16C / 27C + + + + + This value holds information about the first schedule setpoints for Thursdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x06004643 06:00AM 70F / 67F + 0x06001519 06:00AM 21C / 25C + + + + + This value holds information about the second schedule setpoints for Thursdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x08003e55 08:00AM 62F / 85F + 0x0800101d 08:00AM 16C / 29C + + + + + This value holds information about the third schedule setpoints for Thursdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x1200464e 06:00PM 70F / 78F + 0x12001519 06:00PM 21C / 25C + + + + + This value holds information about the fourth schedule setpoints for Thursdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x16003e52 10:00PM 62F / 82F + 0x1600101b 10:00PM 16C / 27C + + + + + This value holds information about the first schedule setpoints for Fridays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x06004643 06:00AM 70F / 67F + 0x06001519 06:00AM 21C / 25C + + + + + This value holds information about the second schedule setpoints for Fridays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x08003e55 08:00AM 62F / 85F + 0x0800101d 08:00AM 16C / 29C + + + + + This value holds information about the third schedule setpoints for Fridays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x1200464e 06:00PM 70F / 78F + 0x12001519 06:00PM 21C / 25C + + + + + This value holds information about the fourth schedule setpoints for Fridays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x16003e52 10:00PM 62F / 82F + 0x1600101b 10:00PM 16C / 27C + + + + + This value holds information about the first schedule setpoints for Saturdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x06004643 06:00AM 70F / 67F + 0x06001519 06:00AM 21C / 25C + + + + + This value holds information about the second schedule setpoints for Saturdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x08003e55 08:00AM 62F / 85F + 0x0800101d 08:00AM 16C / 29C + + + + + This value holds information about the third schedule setpoints for Saturdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x1200464e 06:00PM 70F / 78F + 0x12001519 06:00PM 21C / 25C + + + + + This value holds information about the fourth schedule setpoints for Saturdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x16003e52 10:00PM 62F / 82F + 0x1600101b 10:00PM 16C / 27C + + + + + + + + + + diff --git a/plugins/hal-zwave/config/trane/TZEMT400BB32MAA.xml b/plugins/hal-zwave/config/trane/TZEMT400BB32MAA.xml new file mode 100644 index 00000000..f8903f38 --- /dev/null +++ b/plugins/hal-zwave/config/trane/TZEMT400BB32MAA.xml @@ -0,0 +1,955 @@ + + + + + + + + + + 0 = Gas/Elec, 1 = HeatPump + + + + + 0 = Gas, 1 = Elec + + + + + 0 = w/Cool, 1 = w/Heat + + + + + 0 = C, 1 = F + + + + + + + + + 0 = Unlocked, 1 = Locked + + + + + Sets the minimum off time before another heating/cooling cycle can begin to provide compressor short cycle protection. The thermostat screen will display WAIT when minimum off time is being enforced. + + + + + Sets the minimum run time before a heating/cooling cycle can turn off to prevent rapid cycling. Thermostat screen will display "Cool ON" or "Heat ON" while the minimum run time is being enforced. + + + + + Sets the delta from setpoint that stage 1 heating starts. + + + + + Sets the delta from setpoint that stage 1 heating stops. Stage 1 turns off at setpoint minus (-) Delta Stage 1. + + + + + Sets the delta from setpoint that stage 2 heating starts. + + + + + Sets the delta from setpoint that stage 2 heating stops. Stage 1 turns off at setpoint minus (-) Delta Stage 2. + + + + + Sets the delta from setpoint that stage 3 heating starts. + + + + + Sets the delta from setpoint that stage 3 heating stops. Stage 1 turns off at setpoint minus (-) Delta Stage 3. + + + + + Sets the delta from setpoint that stage 1 cooling starts. + + + + + Sets the delta from setpoint that stage 1 cooling stops. Stage 1 turns off at setpoint minus (-) Delta Stage 1. + + + + + Sets the delta from setpoint that stage 2 cooling starts. + + + + + Sets the delta from setpoint that stage 2 cooling stops. Stage 1 turns off at setpoint minus (-) Delta Stage 2. + + + + + + + + + + + + + Sets the minimum separation between the heating and cooling setpoints. Attempts to lower the cooling below the heating setpoint by this amount will PUSH the heating setpoint down to maintain this separation. Same for setting the heating setpoint above the cooling setpoint, it will PUSH the cooling setpoint up to maintain this separation. Settings in F. + + + + + 0 = No Setback, 1 = Setback, 2 if ESM + + + + + + + + + + + + + + + + + Energy Saving Mode (ESM) Setpoints are the setpoints used when the Energy Saving Mode schedule is selected in the Schedule Mode screen (or via Z-Wave control). Setting in F. + + + + + Energy Saving Mode (ESM) Setpoints are the setpoints used when the Energy Saving Mode schedule is selected in the Schedule Mode screen (or via Z-Wave control). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The fan cycler function cycles the HVAC system fan for an ON period followed by an OFF period continuously. Used to provide minimum air ventilation requirements. When the Fan ON time is set to a value greater than 0, an additional Cycler Fan mode is present when pressing the FAN button on the thermostat. + + + + + The fan cycler function cycles the HVAC system fan for an ON period followed by an OFF period continuously. Used to provide minimum air ventilation requirements. When the Fan ON time is set to a value greater than 0, an additional Cycler Fan mode is present when pressing the FAN button on the thermostat. + + + + + 0 = no 2nd stage heat, 1 = 2nd stage heat. + + + + + 0 = no aux heat, 1 = aux heat enabled. + + + + + 0 = no 2nd stage cool, 1 = 2nd stage cool + + + + + + + + + + + + + + + + + + + + + Set to 1 if running schedule (RUN is displayed on the thermostat screen). + + + + + + + + + Default: + HOLD 80F / 26C + RUN 84F / xxC + ESM + + + + + + + + + Heating 1 Setpoint (does this vary with ESM, etc. or is this for the "Hold" setting? + Default: + HOLD 55F / 13C + RUN 60F / xxC + ESM 64F / xxC (unless parameter xx has been changed) + + + + + Backlight Timeout is the time (in seconds) from the last + button press to the backlight going out. The time-out + can be set between 0 and 120 + seconds. When set to 0, the backlight will remain + always on. + Default: 30 + + + + + Sets the maximum heating setpoint value. Will not ramp + or accept setpoints higher than this maximum. + Minimum: 55F / xxC + Maximum: 90F / xxC + Default: 90F / 32C + + + + + Sets the minimum cooling setpoint value. Will not ramp + or accept setpoints lower than this minimum. + Minimum: 60F / xxC + Maximum: 99F / xxC + Default: 60F / 15C + + + + + + + + + This is the time before any screen reverts to the Minimized + Screen (temperature display only), after you stop pushing + buttons. Minimized Screen feature is disabled by setting this + time to 0. + Default: 0 + + + + + + + + + The internal temperature sensor can be calibrated to report + values different from its actual reading. The offset can + range from -7 degrees to +7 degrees. + Default: 0 + + + + + + + + + + + + + + + + + + + + + The Screen Contrast sets the contrast level of the LCD display. + The contrast can be set between 0 and 20. If the display + is too light, use a higher number. If dark lines appear on + the screen, use a lower number. + Default: 10 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 0x2c after reset + 0xf4 after reset + + + + + 0x2c after reset + 0xf4 after reset + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 0xb8 after reset + 0xe4 after reset + + + + + 0xb8 after reset + 0xe4 after reset + + + + + When enabled (set to 1), the local thermostat's scheduler + function is enabled. + Default: 0 + + + + + + + + + + + + + + + + + + + + + 0xff after reset + + + + + + + + + + + + + 0xff after reset + + + + + + + + + + + + + 0xff after reset + + + + + + + + + + + + + 0xff after reset + + + + + + + + + + + + + 0xff after reset + + + + + + + + + + + + + 0xff after reset + + + + + + + + + + + + + 0xff after reset + + + + + + + + + + + + + Recovery enable? + Default: 1 + 0x00 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This value holds information about the first schedule + setpoints for Sundays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x06004643 06:00AM 70F / 67F + 0x06001519 06:00AM 21C / 25C + + + + + This value holds information about the second schedule + setpoints for Sundays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x08003e55 08:00AM 62F / 85F + 0x0800101d 08:00AM 16C / 29C + + + + + This value holds information about the third schedule + setpoints for Sundays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x1200464e 06:00PM 70F / 78F + 0x12001519 06:00PM 21C / 25C + + + + + This value holds information about the fourth schedule + setpoints for Sundays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x16003e52 10:00PM 62F / 82F + 0x1600101b 10:00PM 16C / 27C + + + + + This value holds information about the first schedule + setpoints for Mondays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x06004643 06:00AM 70F / 67F + 0x06001519 06:00AM 21C / 25C + + + + + This value holds information about the second schedule + setpoints for Mondays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x08003e55 08:00AM 62F / 85F + 0x0800101d 08:00AM 16C / 29C + + + + + This value holds information about the third schedule + setpoints for Mondays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x1200464e 06:00PM 70F / 78F + 0x12001519 06:00PM 21C / 25C + + + + + This value holds information about the fourth schedule + setpoints for Mondays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x16003e52 10:00PM 62F / 82F + 0x1600101b 10:00PM 16C / 27C + + + + + This value holds information about the first schedule + setpoints for Tuesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x06004643 06:00AM 70F / 67F + 0x06001519 06:00AM 21C / 25C + + + + + This value holds information about the second schedule + setpoints for Tuesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x08003e55 08:00AM 62F / 85F + 0x0800101d 08:00AM 16C / 29C + + + + + This value holds information about the third schedule + setpoints for Tuesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x1200464e 06:00PM 70F / 78F + 0x12001519 06:00PM 21C / 25C + + + + + This value holds information about the fourth schedule + setpoints for Tuesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x16003e52 10:00PM 62F / 82F + 0x1600101b 10:00PM 16C / 27C + + + + + This value holds information about the first schedule + setpoints for Wednesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x06004643 06:00AM 70F / 67F + 0x06001519 06:00AM 21C / 25C + + + + + This value holds information about the second schedule setpoints for Wednesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x08003e55 08:00AM 62F / 85F + 0x0800101d 08:00AM 16C / 29C + + + + + This value holds information about the third schedule setpoints for Wednesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x1200464e 06:00PM 70F / 78F + 0x12001519 06:00PM 21C / 25C + + + + + This value holds information about the fourth schedule setpoints for Wednesdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x16003e52 10:00PM 62F / 82F + 0x1600101b 10:00PM 16C / 27C + + + + + This value holds information about the first schedule setpoints for Thursdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x06004643 06:00AM 70F / 67F + 0x06001519 06:00AM 21C / 25C + + + + + This value holds information about the second schedule setpoints for Thursdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x08003e55 08:00AM 62F / 85F + 0x0800101d 08:00AM 16C / 29C + + + + + This value holds information about the third schedule setpoints for Thursdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x1200464e 06:00PM 70F / 78F + 0x12001519 06:00PM 21C / 25C + + + + + This value holds information about the fourth schedule setpoints for Thursdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x16003e52 10:00PM 62F / 82F + 0x1600101b 10:00PM 16C / 27C + + + + + This value holds information about the first schedule setpoints for Fridays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x06004643 06:00AM 70F / 67F + 0x06001519 06:00AM 21C / 25C + + + + + This value holds information about the second schedule setpoints for Fridays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x08003e55 08:00AM 62F / 85F + 0x0800101d 08:00AM 16C / 29C + + + + + This value holds information about the third schedule setpoints for Fridays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x1200464e 06:00PM 70F / 78F + 0x12001519 06:00PM 21C / 25C + + + + + This value holds information about the fourth schedule setpoints for Fridays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x16003e52 10:00PM 62F / 82F + 0x1600101b 10:00PM 16C / 27C + + + + + This value holds information about the first schedule setpoints for Saturdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x06004643 06:00AM 70F / 67F + 0x06001519 06:00AM 21C / 25C + + + + + This value holds information about the second schedule setpoints for Saturdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x08003e55 08:00AM 62F / 85F + 0x0800101d 08:00AM 16C / 29C + + + + + This value holds information about the third schedule setpoints for Saturdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x1200464e 06:00PM 70F / 78F + 0x12001519 06:00PM 21C / 25C + + + + + This value holds information about the fourth schedule setpoints for Saturdays. + + Byte 1: Hour (0-23) + Byte 2: Minute (0-59) + Byte 3: Heat Setpoint (degrees) + Byte 4: Cool Setpoint (degrees) + + Default: 0x16003e52 10:00PM 62F / 82F + 0x1600101b 10:00PM 16C / 27C + + + + + + + + + + diff --git a/plugins/hal-zwave/config/vision/zs5101eu.xml b/plugins/hal-zwave/config/vision/zs5101eu.xml new file mode 100644 index 00000000..16963468 --- /dev/null +++ b/plugins/hal-zwave/config/vision/zs5101eu.xml @@ -0,0 +1,8 @@ + + + + + + + + \ No newline at end of file diff --git a/plugins/hal-zwave/config/vitrum/vitrumBS.xml b/plugins/hal-zwave/config/vitrum/vitrumBS.xml new file mode 100644 index 00000000..49ffbf2d --- /dev/null +++ b/plugins/hal-zwave/config/vitrum/vitrumBS.xml @@ -0,0 +1,5 @@ + + + + + \ No newline at end of file diff --git a/plugins/hal-zwave/config/waynedalton/WDTC-20.xml b/plugins/hal-zwave/config/waynedalton/WDTC-20.xml new file mode 100644 index 00000000..720d1050 --- /dev/null +++ b/plugins/hal-zwave/config/waynedalton/WDTC-20.xml @@ -0,0 +1,8 @@ + + + + + + + + diff --git a/plugins/hal-zwave/config/wenzhou/tz66d.xml b/plugins/hal-zwave/config/wenzhou/tz66d.xml new file mode 100644 index 00000000..e74d1661 --- /dev/null +++ b/plugins/hal-zwave/config/wenzhou/tz66d.xml @@ -0,0 +1,34 @@ + + + + + + + If the bit is set to 1, the dimmer will ignore the start level and instead start dimming from its current level. If this bit is set to 0, the dimmer will not ignore the start level. + + + Setting this parameter to the value of 1 will stop theTZ66D from transmitting to devices that are associated into Group 4. + + + The LED on the TZ66D will by default, turn ON when the load attached is turned OFF. To make the LED turn ON when the load attached is turned ON instead, set parameter to a value of 1. + + + To change the top of the switch to OFF and the bottom of the switch ON , set parameter 4 to 1. + + + The TZ66D can operate shade control devices via its Group 2 if this configuration parameter is set to 1. + + + The TZ66D can operate shade control devices via its Group 3 if this configuration parameter is set to 1. + + + The TZ66-D will flicker its LED when it is transmitting to any of its 4 groups. This flickering can be set to not flicker at all (set to 0), to flicker the entire time it is transmitting (set to 1), or to flicker for only 1 second when it begins transmitting (set to 2). By default, the TZ66D is set to flicker for only 1 second. + + + The TZ66D can operate shade control devices via its Group 3 if this configuration parameter is set to 1. + + + If value is 0, the TZ66D will not poll Group 2. If value is 1, the TZ66D will poll Group 2 at the interval set in Configuration Parameter 20. + + + diff --git a/plugins/hal-zwave/config/wenzhou/tz88.xml b/plugins/hal-zwave/config/wenzhou/tz88.xml new file mode 100644 index 00000000..bfa42548 --- /dev/null +++ b/plugins/hal-zwave/config/wenzhou/tz88.xml @@ -0,0 +1,13 @@ + + + + + + + If the setting is configured for 1 hour (value=720), the TZ88 will report its instant power consumption every 1 hour. + + + If the setting is configured for 1 hour (value=6), the TZ88 will report its accumulated power consumption (kWh) every 1 hour. + + + diff --git a/plugins/hal-zwave/config/zwave.me/ZME_06433.xml b/plugins/hal-zwave/config/zwave.me/ZME_06433.xml new file mode 100644 index 00000000..9f09945f --- /dev/null +++ b/plugins/hal-zwave/config/zwave.me/ZME_06433.xml @@ -0,0 +1,95 @@ + + + + + + + + + + + + + + + + If not zero, automatically switch off/close blind after a user defined time + + + If not zero, automatically switch off/close blind after a user defined time + + + + + + Defines if the dimmer shall ignore start level in StartLevelChange command despite it is specified or not. + + + + + Time to dim on button presses and Set command (if it has no duration specified). If not 0, dimming will be done smoothly to preserve bulb life. + + + Time to dim on button holds and StartLevel Change command (if it has no duration specified). + + + Defines if the dimmer shall set maximum light level on On command. By default on On command dimmer restores last level. This parameter allows to configure to set maximum level on second On command (if already On) or to always switch on to maximum level. + + + + + + Time to dim on double click Off button for Baby- Dim function. This function works only if the load is operated by single press and hold button action. If enabled, the device will wait for a click timeout to see if the second click would be pressed. This will introduce a small delay for single click commands, unprotected. + + + Target level on which to stop while executing Baby Dimming. Can be 0 to completely switch off the light. + + + Typical time used to differentiate click, hold, double and triple clicks. + + + + + + + If disabled, the local operations by buttons will not switch the load, but only send commands to On/Off association group. In this mode buttons are not linked with the switch anymore. They can be used separately: buttons to control remote device, switch will operate by RF commands only. + + + + + + Defines which command should be sent on button single press or hold. Basic commands are sent to Association group. Switch All commands are sent broadcast. + + + + + + Defines which command should be sent on button double press or press-hold. Basic commands are sent to Association group. Switch All commands are sent broadcast. If not disabled, the device will wait for a click timeout to see if the second click would be pressed. This will introduce a small delay for single click commands. + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/zwave.me/ZME_06436.xml b/plugins/hal-zwave/config/zwave.me/ZME_06436.xml new file mode 100644 index 00000000..4df58fd4 --- /dev/null +++ b/plugins/hal-zwave/config/zwave.me/ZME_06436.xml @@ -0,0 +1,97 @@ + + + + + + + + + + + + + + + + If not zero, automatically switch off/close blind after a user defined time + + + If not zero, automatically switch off/close blind after a user defined time + + + + + + Time to go from opened to closed state. Used to estimate the current level. Note that in Permanent motion mode the reported value would a be Closed or Opened, while all Basic and Multilevel Set values (1-99, 255) would Open except 0 value that would Close. + + + Time to go from closed to open state. This value may differ from Full close time for some blinds due to gravity. Used to estimate the current level. Note that in Permanent motion mode the reported value would a be Closed or Opened, while all Basic and Multilevel Set values (1-99, 255) would Open except 0 value that would Close. + + + Id of the device which commands would be interpreted not as Open/Close, but as block/unblock. Usefull with door opening detector: if the door is open, block the blind not to break shades while they move. + + + Defines which command from blocking device to interpret as closed door and hence, unprotected. + + + + + Defines behaviour on open press while closing and vice versa. To allow Stop behavior when switched by remote, use Stop by Basic + + + + + + Allow exchanging open and close relays if blind control is wired to the motor incorrectly + + + + + Typical time used to differentiate click, hold, double and triple clicks. + + + + + + + If disabled, the local operations by buttons will not switch the load, but only send commands to On/Off association group. In this mode buttons are not linked with the switch anymore. They can be used separately: buttons to control remote device, switch will operate by RF commands only. + + + + + + Defines which command should be sent on button single press or hold. Basic commands are sent to Association group. Switch All commands are sent broadcast. + + + + + + Defines which command should be sent on button double press or press-hold. Basic commands are sent to Association group. Switch All commands are sent broadcast. If not disabled, the device will wait for a click timeout to see if the second click would be pressed. This will introduce a small delay for single click commands. + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/zwave.me/ZME_WCD2.xml b/plugins/hal-zwave/config/zwave.me/ZME_WCD2.xml new file mode 100644 index 00000000..88b58ab1 --- /dev/null +++ b/plugins/hal-zwave/config/zwave.me/ZME_WCD2.xml @@ -0,0 +1,136 @@ + + + + + + + + + Button 1 and 3 pair mode (Parameter Number 1, + Parameter Size 1) In separate mode button 1 works + with group 1, button 3 with groups 3. Click is On, Hold + is dimming Up, Double click is Off, Click-Hold is + dimming Down. In pair button 1/3 are Up/Down + correspondingly. Click is On/Off, Hold is dimming + Up/Down. Single clicks works with group 1, double click with group + 3. + + + + + + Button 2 and 4 pair mode (Parameter Number 2, + Parameter Size 1) In separate mode button 2 works + with group 2, button 4 with groups 4. Click is On, Hold + is dimming Up, Double click is Off, Click-Hold is + dimming Down. In pair button 2/4 are Up/Down + correspondingly. Click is On/Off, Hold is dimming + Up/Down. Single clicks works with group 2, double click with group 4. + + + + + + + Action on group 1 (Parameter Number 11, + Parameter Size 1) In Switch On/Off only mode On + command is sent on Dim Up, Off on Dim Down. In Scenes mode the + scene ID sent is (10 * group + ActionID), where + ActionID is: 1 = On, 2 = Off, 3 = Dim Up Start, 4 = + Dim Down Start, 5 = Dim Up Stop, 6 = Dim Down Stop + + + + + + + + + + Action on group 2 (Parameter Number 12, + Parameter Size 1) In Switch On/Off only mode On + command is sent on Dim Up, Off on Dim Down. In Scenes mode the + scene ID sent is (10 * group + ActionID), where + ActionID is: 1 = On, 2 = Off, 3 = Dim Up Start, 4 = + Dim Down Start, 5 = Dim Up Stop, 6 = Dim Down Stop + + + + + + + + + + Action on group 3 (Parameter Number 13, + Parameter Size 1) In Switch On/Off only mode On + command is sent on Dim Up, Off on Dim Down. In Scenes mode the + scene ID sent is (10 * group + ActionID), where + ActionID is: 1 = On, 2 = Off, 3 = Dim Up Start, 4 = + Dim Down Start, 5 = Dim Up Stop, 6 = Dim Down Stop + + + + + + + + + + Action on group 4 (Parameter Number 14, + Parameter Size 1) In Switch On/Off only mode On + command is sent on Dim Up, Off on Dim Down. In Scenes mode the + scene ID sent is (10 * group + ActionID), where + ActionID is: 1 = On, 2 = Off, 3 = Dim Up Start, 4 = + Dim Down Start, 5 = Dim Up Stop, 6 = Dim Down Stop + + + + + + + + + + Typical time used to differenciate click, hold and double clicks + + + + + + + + + + + + This allows to save battery + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/zwave.me/kfob.xml b/plugins/hal-zwave/config/zwave.me/kfob.xml new file mode 100644 index 00000000..909e44c7 --- /dev/null +++ b/plugins/hal-zwave/config/zwave.me/kfob.xml @@ -0,0 +1,118 @@ + + + + + + + 0 Separate buttons + 1 Buttons are grouped (one is on, one if off), no double click supported (default) + 2 Buttons are grouped (one is on, one if off), double click supported + + + + + 0 Separate buttons + 1 Buttons are grouped (one is on, one if off), no double click supported (default) + 2 Buttons are grouped (one is on, one if off), double click supported + + + + + 0 Disabled + 1 Control Dimmer, Motor Control and Switches using Basic+Multilevel Switch Commands (default) + 2 Control Switches only, click and hold sends only Basic Commands + 3 Switch All On/Off + 4 Send Scene Activation + 5 Control preconfigured Scenes + 6 Control devices in proximity + + + + + 0 Disabled + 1 Control Dimmer, Motor Control and Switches using Basic+Multilevel Switch Commands (default) + 2 Control Switches only, click and hold sends only Basic Commands + 3 Switch All On/Off + 4 Send Scene Activation + 5 Control preconfigured Scenes + 6 Control devices in proximity + + + + + 0 Disabled + 1 Control Dimmer, Motor Control and Switches using Basic+Multilevel Switch Commands (default) + 2 Control Switches only, click and hold sends only Basic Commands + 3 Switch All On/Off + 4 Send Scene Activation + 5 Control preconfigured Scenes + 6 Control devices in proximity + + + + + 0 Disabled + 1 Control Dimmer, Motor Control and Switches using Basic+Multilevel Switch Commands (default) + 2 Control Switches only, click and hold sends only Basic Commands + 3 Switch All On/Off + 4 Send Scene Activation + 5 Control preconfigured Scenes + 6 Control devices in proximity + + + + + Typical time used to differentiate click, hold, double and click-holds. + 1 100 in 10 ms units (default is 50, that is equivalent to 500 ms) + + + + + 1 Switch All Off only (default) + 2 Switch All On only + 255 Switch All On and Off + + + + + Invert meaning of On/Dim up and Off/Dim down in pairs of buttons. This applies only to pairs in grouped mode. + Buttons 1 and 2 will become Off/Dim down, buttons 3 and 4 On/Dim up. + 0 No (default) + 1 Yes + + + + + To save batteries LED confirmation can be disabled. + 0 No confirmations + 1 Confirm button press + 2 Confirm button press and delivery (default) + + + + + 0 No (default) + 1 To same node as wakeup notification + 2 Broadcast + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/zwcfg.xsd b/plugins/hal-zwave/config/zwcfg.xsd new file mode 100644 index 00000000..ed9d20f8 --- /dev/null +++ b/plugins/hal-zwave/config/zwcfg.xsd @@ -0,0 +1,249 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/config/zwscene.xsd b/plugins/hal-zwave/config/zwscene.xsd new file mode 100644 index 00000000..c2395a5c --- /dev/null +++ b/plugins/hal-zwave/config/zwscene.xsd @@ -0,0 +1,28 @@ + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/plugins/hal-zwave/src/se/hal/plugin/zwave/HalZWaveController.java b/plugins/hal-zwave/src/se/hal/plugin/zwave/HalZWaveController.java index c868b533..38109f26 100644 --- a/plugins/hal-zwave/src/se/hal/plugin/zwave/HalZWaveController.java +++ b/plugins/hal-zwave/src/se/hal/plugin/zwave/HalZWaveController.java @@ -13,7 +13,10 @@ import java.util.concurrent.atomic.AtomicReference; import java.util.logging.Logger; /** - * @author zagumennikov + * + *

Reference: http://www.openzwave.com/dev/namespaceOpenZWave.html + * + * @author Ziver Koc */ public class HalZWaveController implements HalSensorController, HalEventController, HalAutoScannableController, NotificationWatcher{ private static final Logger logger = LogUtil.getLogger(); @@ -80,60 +83,47 @@ public class HalZWaveController implements HalSensorController, HalEventControll switch (notification.getType()) { case DRIVER_READY: homeId = notification.getHomeId(); - logger.info("Driver ready (Home ID: " + homeId + ")"); + logger.info("Driver ready (Home ID: " + homeId + ")."); break; case DRIVER_FAILED: - logger.info("Driver failed"); + logger.info("Driver failed."); break; case DRIVER_RESET: - logger.info("Driver reset"); + logger.info("Driver reset."); break; case AWAKE_NODES_QUERIED: - logger.info("Awake nodes queried"); + logger.info("Controller is done initializing, All awake nodes queried."); + manager.writeConfig(homeId); break; case ALL_NODES_QUERIED_SOME_DEAD: - logger.info("Some Nodes are dead"); - case ALL_NODES_QUERIED: - logger.info("All nodes queried"); + logger.info("Controller is done initializing, All nodes queried but some are dead."); + manager.writeConfig(homeId); + break; + case ALL_NODES_QUERIED: + logger.info("Controller is done initializing, All nodes queried."); manager.writeConfig(homeId); - logger.info(" Controller is done initializing"); break; case POLLING_ENABLED: - System.out.println("Polling enabled"); + logger.fine("[NodeID: " + notification.getNodeId() + "] Polling enabled."); break; case POLLING_DISABLED: - System.out.println("Polling disabled"); + logger.fine("[NodeID: " + notification.getNodeId() + "] Polling disabled."); break; case NODE_NEW: - System.out.println(String.format("Node new\n" + - "\tnode id: %d", - notification.getNodeId() - )); + logger.fine("[NodeID: " + notification.getNodeId() + "] New node detected."); break; case NODE_ADDED: - System.out.println(String.format("Node added\n" + - "\tnode id: %d", - notification.getNodeId() - )); + logger.fine("[NodeID: " + notification.getNodeId() + "] Node registered to controller."); break; case NODE_REMOVED: - System.out.println(String.format("Node removed\n" + - "\tnode id: %d", - notification.getNodeId() - )); + logger.fine("[NodeID: " + notification.getNodeId() + "] Node unregistered from controller."); break; case ESSENTIAL_NODE_QUERIES_COMPLETE: - System.out.println(String.format("Node essential queries complete\n" + - "\tnode id: %d", - notification.getNodeId() - )); + logger.finest("[NodeID: " + notification.getNodeId() + "] Essential node queries complete."); break; case NODE_QUERIES_COMPLETE: - System.out.println(String.format("Node queries complete\n" + - "\tnode id: %d", - notification.getNodeId() - )); + logger.finest("[NodeID: " + notification.getNodeId() + "] Node queries complete."); break; case NODE_EVENT: System.out.println(String.format("Node event\n" + @@ -144,10 +134,10 @@ public class HalZWaveController implements HalSensorController, HalEventControll )); break; case NODE_NAMING: - System.out.println(String.format("Node naming\n" + - "\tnode id: %d", - notification.getNodeId() - )); + logger.fine("[NodeID: " + notification.getNodeId() + "] Node identified as: " + + manager.getNodeManufacturerName(notification.getHomeId(), notification.getNodeId()) + ", " + + manager.getNodeProductName(notification.getHomeId(), notification.getNodeId()) + ); break; case NODE_PROTOCOL_INFO: System.out.println(String.format("Node protocol info\n" + @@ -257,10 +247,12 @@ public class HalZWaveController implements HalSensorController, HalEventControll )); break; case NOTIFICATION: - System.out.println("Notification"); + logger.fine("[NodeID: " + notification.getNodeId() + "] Received notification, will query dynamic state of node."); + //if (!manager.requestNodeDynamic(notification.getHomeId(), notification.getNodeId())) + // logger.fine("[NodeID: " + notification.getNodeId() + "] Requesting dynamic state failed."); break; default: - System.out.println(notification.getType().name()); + logger.warning("Unknown notification type: " + notification.getType().name()); break; } } diff --git a/plugins/hal-zwave/test/se/hal/plugin/zwave/HalZWaveControllerTest.java b/plugins/hal-zwave/test/se/hal/plugin/zwave/HalZWaveControllerTest.java index bf0ee157..6570e863 100644 --- a/plugins/hal-zwave/test/se/hal/plugin/zwave/HalZWaveControllerTest.java +++ b/plugins/hal-zwave/test/se/hal/plugin/zwave/HalZWaveControllerTest.java @@ -10,6 +10,7 @@ import zutil.log.LogUtil; import java.io.IOException; import java.util.List; import java.util.concurrent.atomic.AtomicReference; +import java.util.logging.Level; import java.util.logging.Logger; /** @@ -19,10 +20,12 @@ public class HalZWaveControllerTest { public static void main(String[] args) throws IOException { LogUtil.setGlobalFormatter(new CompactLogFormatter()); + LogUtil.setGlobalLevel(Level.ALL); + HalZWaveController controller = new HalZWaveController(); controller.initialize( "/dev/serial/by-id/usb-0658_0200-if00", - "./"); + "./plugins/hal-zwave/config"); System.out.println("Press ENTER to exit application."); System.in.read();