From 43d9795e076cda9a1c2905c894ef5391385bc801 Mon Sep 17 00:00:00 2001 From: "CloudBees DEV@Cloud" Date: Sun, 8 Jul 2018 16:50:52 +0200 Subject: [PATCH] Updated external content (Jenkins build 13) --- _addons_bindings/astro/readme.md | 2 +- _addons_bindings/cardio2e1/readme.md | 136 +++ _addons_bindings/comfoair1/readme.md | 9 + _addons_bindings/digitalstrom/readme.md | 7 + _addons_bindings/fritzboxtr0641/readme.md | 2 +- _addons_bindings/fronius/readme.md | 2 - _addons_bindings/gardena/readme.md | 29 +- _addons_bindings/kodi/readme.md | 3 + _addons_bindings/meteostick/readme.md | 96 +- _addons_bindings/mihome/readme.md | 22 +- _addons_bindings/milight1/readme.md | 2 +- _addons_bindings/mpd1/readme.md | 4 +- _addons_bindings/robonect/readme.md | 7 +- _addons_bindings/solaredge/readme.md | 135 +++ _addons_bindings/squeezebox/readme.md | 11 +- _addons_bindings/systeminfo1/readme.md | 12 +- _addons_bindings/zigbee/readme.md | 38 +- _addons_bindings/zwave/doc/act/zir010_0_0.md | 7 +- .../zwave/doc/aeon/dsa03202_0_0.md | 7 +- _addons_bindings/zwave/doc/aeon/dsa38_0_0.md | 7 +- _addons_bindings/zwave/doc/aeon/dsb29_0_0.md | 7 +- _addons_bindings/zwave/doc/aeon/dsb45_0_0.md | 6 +- _addons_bindings/zwave/doc/aeon/dsb54_0_0.md | 7 +- _addons_bindings/zwave/doc/aeon/dsc25_0_0.md | 7 +- _addons_bindings/zwave/doc/aeon/dsc26_0_0.md | 148 ++- _addons_bindings/zwave/doc/aeon/zw074_0_0.md | 7 +- _addons_bindings/zwave/doc/aeon/zw088_1_0.md | 7 +- _addons_bindings/zwave/doc/aeon/zw089_0_0.md | 6 +- _addons_bindings/zwave/doc/aeon/zw090_0_0.md | 4 - _addons_bindings/zwave/doc/aeon/zw096_0_0.md | 4 - _addons_bindings/zwave/doc/aeon/zw097_0_0.md | 7 +- _addons_bindings/zwave/doc/aeon/zw100_1_10.md | 8 - _addons_bindings/zwave/doc/aeon/zw100_1_8.md | 8 - _addons_bindings/zwave/doc/aeon/zw112_0_0.md | 10 +- _addons_bindings/zwave/doc/aeon/zw116_0_0.md | 25 +- _addons_bindings/zwave/doc/aeon/zw117_0_0.md | 7 +- _addons_bindings/zwave/doc/aeon/zw120_0_0.md | 6 +- _addons_bindings/zwave/doc/aeon/zw122_0_0.md | 7 +- _addons_bindings/zwave/doc/aeon/zw129_0_0.md | 7 +- _addons_bindings/zwave/doc/aeon/zw130_0_0.md | 6 +- _addons_bindings/zwave/doc/aeon/zw132_0_0.md | 31 +- .../zwave/doc/august/asl03_0_0.md | 4 - .../zwave/doc/benext/doorsensor_0_0.md | 7 +- .../zwave/doc/benext/energyswitch_0_0.md | 7 +- .../zwave/doc/benext/molite_0_0.md | 7 +- .../zwave/doc/benext/tagreader_0_0.md | 7 +- .../zwave/doc/bonig/pope005206_0_0.md | 7 +- _addons_bindings/zwave/doc/brk/zcombo_0_0.md | 7 +- _addons_bindings/zwave/doc/brk/zsmoke_0_0.md | 7 +- .../zwave/doc/chromagic/hsm02_0_0.md | 7 +- .../zwave/doc/chromagic/sm103_0_0.md | 7 +- _addons_bindings/zwave/doc/cloud/a803n_0_0.md | 7 +- .../zwave/doc/cooper/rf9500_0_0.md | 7 +- .../zwave/doc/coqon/psmz0001_0_0.md | 7 +- .../zwave/doc/danfoss/010101_0_0.md | 6 +- .../zwave/doc/danfoss/014g0160_0_0.md | 6 +- .../zwave/doc/danfoss/dthermz5_0_0.md | 7 +- .../zwave/doc/danfoss/dthermz6_0_0.md | 7 +- .../zwave/doc/danfoss/lc13_0_0.md | 6 +- .../zwave/doc/danfoss/lcz251_0_0.md | 35 +- .../zwave/doc/danfoss/mt02650_0_0.md | 6 +- .../zwave/doc/defaro/dad101_0_0.md | 4 - .../zwave/doc/defaro/das102_0_0.md | 4 - .../zwave/doc/defaro/dsi101_0_0.md | 6 +- .../zwave/doc/devolo/09813_0_0.md | 7 +- .../zwave/doc/devolo/mt02646_0_0.md | 11 +- .../zwave/doc/devolo/mt02647_0_0.md | 7 +- .../zwave/doc/devolo/mt02648_0_0.md | 8 +- .../zwave/doc/devolo/mt2652_0_0.md | 7 +- .../zwave/doc/devolo/mt2653_0_0.md | 7 +- .../zwave/doc/devolo/mt2755_0_0.md | 6 +- .../zwave/doc/devolo/mt2756_0_0.md | 11 +- .../zwave/doc/devolo/pst021b_0_0.md | 7 +- .../zwave/doc/dlink/dchz110_0_0.md | 7 +- .../zwave/doc/dlink/dchz120_0_0.md | 7 +- .../zwave/doc/dlink/dchz310_0_0.md | 6 +- .../zwave/doc/eco/dwzwave2_0_0.md | 7 +- .../zwave/doc/eco/ecolinkpirv25_0_0.md | 7 +- .../zwave/doc/eco/flfzwave5r1_0_0.md | 7 +- _addons_bindings/zwave/doc/eco/pir1_0_0.md | 6 +- .../zwave/doc/eco/tiltzwave25eco_0_0.md | 6 +- .../zwave/doc/eco/tiltzwave2_0_0.md | 7 +- _addons_bindings/zwave/doc/elexa/dmms1_0_0.md | 6 +- _addons_bindings/zwave/doc/elexa/dmmz1_0_0.md | 7 +- _addons_bindings/zwave/doc/elexa/dmwd1_0_0.md | 7 +- _addons_bindings/zwave/doc/elexa/dmws1_0_0.md | 7 +- .../zwave/doc/enerwave/zw20r_0_0.md | 4 - .../zwave/doc/enerwave/zw500dm_0_0.md | 60 +- .../zwave/doc/enerwave/zwnbds_0_0.md | 6 +- .../zwave/doc/enerwave/zwnbpc_0_0.md | 7 +- .../zwave/doc/enerwave/zwnbpc_5_10.md | 7 +- .../zwave/doc/erone/hmdw001_0_0.md | 7 +- .../zwave/doc/eurotronic/cometz_0_0.md | 7 +- .../zwave/doc/eurotronic/spirit_0_0.md | 4 + .../zwave/doc/eurotronic/stellaz_0_0.md | 7 +- .../zwave/doc/everspring/hsm02_0_0.md | 7 +- .../zwave/doc/everspring/hsp02_0_0.md | 7 +- .../zwave/doc/everspring/sf812_0_0.md | 7 +- .../zwave/doc/everspring/sm103_0_0.md | 7 +- .../zwave/doc/everspring/sp103_0_0.md | 7 +- .../zwave/doc/everspring/sp814_0_0.md | 12 +- .../zwave/doc/everspring/sp816_0_0.md | 6 +- .../zwave/doc/everspring/st812_0_0.md | 7 +- .../zwave/doc/everspring/st814_0_0.md | 7 +- .../zwave/doc/everspring/st815_0_0.md | 7 +- .../zwave/doc/evolve/lpm15_0_0.md | 35 +- _addons_bindings/zwave/doc/fakro/arf_0_0.md | 13 +- .../zwave/doc/fibaro/fgcd001_0_0.md | 7 +- .../zwave/doc/fibaro/fgd211_0_0.md | 68 +- .../zwave/doc/fibaro/fgdw002_0_0.md | 55 +- .../zwave/doc/fibaro/fgfs101_23_23.md | 7 +- .../zwave/doc/fibaro/fgfs101_3_2.md | 6 +- .../zwave/doc/fibaro/fggc001_0_0.md | 98 +- .../zwave/doc/fibaro/fgk101_0_0.md | 6 +- .../zwave/doc/fibaro/fgk101_2_5.md | 6 +- .../zwave/doc/fibaro/fgk101_3_2.md | 7 +- .../zwave/doc/fibaro/fgkf601_0_0.md | 7 +- .../zwave/doc/fibaro/fgms001_0_0.md | 69 +- .../zwave/doc/fibaro/fgms001_3_2.md | 7 +- .../zwave/doc/fibaro/fgpb101_0_0.md | 51 +- .../zwave/doc/fibaro/fgr222_24_24.md | 4 - .../zwave/doc/fibaro/fgrm222_0_0.md | 74 +- .../zwave/doc/fibaro/fgs212_0_0.md | 40 +- .../zwave/doc/fibaro/fgsd002_0_0.md | 40 +- .../zwave/doc/fibaro/fgss001_0_0.md | 7 +- .../zwave/doc/fibaro/fgt001_0_0.md | 4 - .../zwave/doc/fireangle/zst630_0_0.md | 7 +- .../zwave/doc/forest/shuttlesl_0_0.md | 4 - .../zwave/doc/fortrezz/wv01_0_0.md | 4 +- .../zwave/doc/fortrezz/wwa02_0_0.md | 7 +- _addons_bindings/zwave/doc/ge/14318_0_0.md | 7 +- _addons_bindings/zwave/doc/ge/ge14299_0_0.md | 139 +++ _addons_bindings/zwave/doc/ge/ge14321_0_0.md | 1 + .../zwave/doc/ge/ge28167zw3104_0_0.md | 7 +- .../zwave/doc/ge/motiondimmerswitch_0_0.md | 194 ++++ .../zwave/doc/ge/smartdoorsensor_0_0.md | 29 +- _addons_bindings/zwave/doc/ge/zw4002_0_0.md | 4 - _addons_bindings/zwave/doc/ge/zw6302_0_0.md | 7 +- .../zwave/doc/goodway/78008_0_0.md | 4 - _addons_bindings/zwave/doc/graber/csz1_0_0.md | 4 - _addons_bindings/zwave/doc/hank/dws01_0_0.md | 7 +- .../zwave/doc/hank/hkzwfld01_0_0.md | 6 +- .../zwave/doc/hank/hkzwms01_0_0.md | 7 +- _addons_bindings/zwave/doc/hank/scn01_0_0.md | 6 +- _addons_bindings/zwave/doc/hank/scn04_0_0.md | 6 +- _addons_bindings/zwave/doc/hank/swes01_0_0.md | 7 +- .../zwave/doc/heiman/hs1caz_0_0.md | 7 +- .../zwave/doc/heiman/hs1dsz_0_0.md | 6 +- .../zwave/doc/heiman/hs1htz_0_0.md | 7 +- .../zwave/doc/heiman/hs1msz_0_0.md | 6 +- .../zwave/doc/heiman/hs1sa_0_0.md | 6 +- .../zwave/doc/heiman/m4172_0_0.md | 7 +- .../zwave/doc/hogar/htp4s1fb_2_2.md | 7 +- .../zwave/doc/hogar/htp850xx_0_0.md | 4 - .../zwave/doc/homeseer/ezmotionexpress_0_0.md | 7 +- .../zwave/doc/homeseer/ezmultipli_0_0.md | 24 +- .../zwave/doc/homeseer/hsds100_0_0.md | 7 +- .../zwave/doc/homeseer/hsls100_0_0.md | 6 +- .../zwave/doc/homeseer/hsms100_0_0.md | 6 +- .../zwave/doc/honeywell/39358_0_0.md | 143 +++ .../zwave/doc/horstmann/hrt4zw_0_0.md | 7 +- .../zwave/doc/horstmann/scsc17_0_0.md | 7 +- .../zwave/doc/horstmann/ses302_0_0.md | 7 +- .../zwave/doc/horstmann/ses303_0_0.md | 7 +- .../zwave/doc/horstmann/srt323_0_0.md | 7 +- .../zwave/doc/horstmann/ssr302_0_0.md | 7 +- .../zwave/doc/horstmann/swm301_0_0.md | 6 +- .../zwave/doc/idlock/idl101_0_0.md | 4 - .../doc/ingersollecolink/dwzwave1_0_0.md | 7 +- .../zwave/doc/ingersollecolink/rs200_0_0.md | 7 +- .../zwave/doc/innovus/smoothremote_0_0.md | 7 +- .../zwave/doc/inovelli/nzw31_0_0.md | 191 ---- .../zwave/doc/intermatic/ca600_0_0.md | 35 +- .../zwave/doc/intermatic/ha20_0_0.md | 12 +- .../zwave/doc/isurpass/smokedetector_0_0.md | 7 +- .../zwave/doc/kaipule/doorwindowsensor_0_0.md | 6 +- .../zwave/doc/kaipule/es61_0_0.md | 6 +- .../zwave/doc/kaipule/im20_0_0.md | 6 +- .../zwave/doc/kaipule/ix32_6_0.md | 7 +- .../zwave/doc/leviton/vrpd3_0_0.md | 5 + .../zwave/doc/linear/gb00z_0_0.md | 7 +- .../zwave/doc/linear/pd300z2_0_0.md | 22 +- .../zwave/doc/linear/wa00z1_0_0.md | 7 +- .../zwave/doc/linear/wadwaz1_0_0.md | 6 +- .../zwave/doc/linear/wapirz_0_0.md | 27 +- .../zwave/doc/linear/wd500z_0_0.md | 29 +- .../zwave/doc/linear/wo15z_0_0.md | 28 +- .../zwave/doc/linear/ws15z_0_0.md | 13 +- .../zwave/doc/logic/scenecontroller_0_0.md | 955 ++++++++++++++++++ .../zwave/doc/mcohome/mh9co2wd_0_0.md | 7 +- .../zwave/doc/mcohome/mhs311_0_0.md | 4 - .../zwave/doc/mcohome/mhs511il_0_0.md | 7 +- .../zwave/doc/mcohome/mhs512il_0_0.md | 7 +- .../zwave/doc/mcohome/mhs521_0_0.md | 7 +- .../zwave/doc/merten/506219_0_0.md | 7 +- .../zwave/doc/merten/507900_0_0.md | 4 - .../zwave/doc/merten/5082xx_0_0.md | 7 +- .../zwave/doc/merten/50x5xx_0_0.md | 22 +- .../zwave/doc/monoprice/10795_0_0.md | 7 +- .../zwave/doc/nexia/db100z_0_0.md | 7 +- .../zwave/doc/nodon/crc3100_0_0.md | 7 +- .../zwave/doc/nodon/cws3101_0_0.md | 7 +- .../zwave/doc/nodon/softremote_0_0.md | 7 +- .../zwave/doc/northq/nq9021_0_0.md | 7 +- .../zwave/doc/northq/nq9121_3_0.md | 6 +- _addons_bindings/zwave/doc/oomi/ft098_0_0.md | 6 +- _addons_bindings/zwave/doc/oomi/ft130_0_0.md | 342 +++++++ .../zwave/doc/philio/pab01_0_0.md | 7 +- .../zwave/doc/philio/pan061b_1_8.md | 317 ------ .../zwave/doc/philio/pan081a_0_0.md | 4 - .../zwave/doc/philio/pat02a_0_0.md | 17 +- .../zwave/doc/philio/pat02b_0_0.md | 7 +- .../zwave/doc/philio/pat02c_0_0.md | 7 +- .../zwave/doc/philio/psm02_0_0.md | 7 +- .../zwave/doc/philio/psp05_0_0.md | 7 +- .../zwave/doc/philio/psr04_0_0.md | 6 +- .../zwave/doc/philio/pst02a_0_0.md | 7 +- .../zwave/doc/philio/pst02b_0_0.md | 7 +- .../zwave/doc/philio/pst02c_0_0.md | 6 +- _addons_bindings/zwave/doc/popp/004407_1_0.md | 6 +- _addons_bindings/zwave/doc/popp/005206_0_0.md | 7 +- _addons_bindings/zwave/doc/popp/009204_0_0.md | 7 +- _addons_bindings/zwave/doc/popp/009303_0_0.md | 6 +- _addons_bindings/zwave/doc/popp/009501_1_2.md | 7 +- .../zwave/doc/popp/pope700052_0_0.md | 7 +- .../zwave/doc/popp/pope700168_0_0.md | 50 +- .../zwave/doc/qubino/smartplug_0_0.md | 4 - .../zwave/doc/qubino/zmnhba_0_0.md | 31 +- .../zwave/doc/qubino/zmnhda_0_0.md | 34 +- _addons_bindings/zwave/doc/reitz/05443_0_0.md | 6 +- .../zwave/doc/reitz/zwesj300_0_0.md | 7 +- .../zwave/doc/remotec/zrc100_0_0.md | 6 +- .../zwave/doc/remotec/zrc90_0_0.md | 7 +- _addons_bindings/zwave/doc/rtc/ct200_0_0.md | 6 - .../zwave/doc/samsungsds/hmdm100_0_0.md | 4 - .../zwave/doc/schlage/be369_0_0.md | 4 - .../zwave/doc/schlage/be468_0_0.md | 4 - .../zwave/doc/schlage/be469_0_0.md | 4 - .../zwave/doc/sensative/1101011_0_0.md | 6 +- .../zwave/doc/sensative/1102011_0_0.md | 6 +- .../zwave/doc/shenzhen/doorsensorin_0_0.md | 7 +- .../doc/shenzhen/doorwindowsensor_0_0.md | 6 +- .../zwave/doc/shenzhen/floodsensor_0_0.md | 6 +- .../zwave/doc/shenzhen/motionsensor_0_0.md | 6 +- .../zwave/doc/shenzhen/motionsensorin_0_0.md | 7 +- .../zwave/doc/shenzhen/nasab01z_0_0.md | 4 - .../zwave/doc/shenzhen/nasds01z_0_0.md | 7 +- .../zwave/doc/shenzhen/sirenalarm_0_0.md | 197 ---- .../doc/shenzhen/sosremotecontrol_0_0.md | 7 +- .../zwave/doc/sigma/m4179e_0_0.md | 7 +- _addons_bindings/zwave/doc/sigma/zwck8_0_0.md | 6 +- .../zwave/doc/sunricher/zv9001k8dim_0_0.md | 60 +- .../zwave/doc/telldus/tzdw100_0_0.md | 7 +- .../zwave/doc/telldus/tzwp102_0_0.md | 132 +++ .../zwave/doc/thermofloor/tf016_0_0.md | 7 + .../zwave/doc/thermofloor/ztrm2_2_6.md | 49 +- _addons_bindings/zwave/doc/things.md | 56 +- _addons_bindings/zwave/doc/tkb/gr308_0_0.md | 7 +- _addons_bindings/zwave/doc/tkb/tsm02_0_0.md | 7 +- _addons_bindings/zwave/doc/tkb/tz55d_0_0.md | 116 ++- _addons_bindings/zwave/doc/tkb/tz75_0_0.md | 32 +- _addons_bindings/zwave/doc/tkb/tz77_0_0.md | 7 +- _addons_bindings/zwave/doc/uei/45601_0_0.md | 7 +- .../zwave/doc/ufairy/tp807zg_0_0.md | 7 +- .../zwave/doc/ufairy/zse02_0_0.md | 7 +- .../zwave/doc/vda/euboiler_0_0.md | 7 +- .../zwave/doc/vemmio/mt100_0_0.md | 6 +- .../zwave/doc/vision/zd2102_0_0.md | 7 +- .../zwave/doc/vision/zd2102plus_0_0.md | 7 +- .../zwave/doc/vision/zd2105_0_0.md | 6 +- .../zwave/doc/vision/zd2201_0_0.md | 7 +- .../zwave/doc/vision/zf5201eu_0_0.md | 6 +- .../zwave/doc/vision/zg8101_0_0.md | 7 +- .../zwave/doc/vision/zl7101_0_0.md | 7 +- .../zwave/doc/vision/zm1602_0_0.md | 12 +- .../zwave/doc/vision/zp3102_0_0.md | 7 +- .../zwave/doc/vision/zp3102_8_0.md | 6 +- .../zwave/doc/vision/zp3103_0_0.md | 7 +- .../zwave/doc/vision/zs5101_0_0.md | 6 +- .../zwave/doc/vision/zs6101_0_0.md | 7 +- .../zwave/doc/vision/zs6301_0_0.md | 7 +- .../zwave/doc/vision/zse40_0_0.md | 6 +- .../zwave/doc/willis/nzw30t_0_0.md | 4 - .../zwave/doc/willis/zen21_0_0.md | 4 - .../zwave/doc/willis/zw691_0_0.md | 7 +- .../dhswinblwdhs_0_0.md} | 150 +-- .../zwave/doc/wintop/itemp_0_0.md | 7 +- .../zwave/doc/wintop/multisensor_0_0.md | 7 +- .../zwave/doc/wintop/wtrfid_0_0.md | 7 +- .../zwave/doc/zipato/hmhs1ca_0_0.md | 7 +- .../zwave/doc/zipato/hmhs1wlz_0_0.md | 6 +- .../zwave/doc/zipato/hs1sa_0_0.md | 7 +- .../zwave/doc/zipato/nenaspd01z_0_0.md | 7 +- .../zwave/doc/zipato/zd2102plus_0_0.md | 7 +- .../zwave/doc/zipato/zp3102_0_0.md | 6 +- _addons_bindings/zwave/doc/zooz/zen23_0_0.md | 7 +- _addons_bindings/zwave/doc/zooz/zse08_0_0.md | 6 +- _addons_bindings/zwave/doc/zooz/zse09_0_0.md | 7 +- _addons_bindings/zwave/doc/zooz/zse30_0_0.md | 6 +- _addons_bindings/zwave/doc/zooz/zse40_0_0.md | 60 +- .../zwave/doc/zwaveme/fgr316_0_0.md | 294 ++++++ .../zwave/doc/zwaveme/kfob_0_0.md | 7 +- .../zwave/doc/zwaveme/wallcs_0_0.md | 7 +- .../zwave/doc/zwaveme/wcd2_0_0.md | 7 +- .../zwave/doc/zwaveme/zme06443_0_0.md | 7 +- .../zwave/doc/zwaveme/zmekfobs_0_0.md | 7 +- .../zwave/doc/zwaveme/zmerc2_0_0.md | 7 +- .../zwave/doc/zwaveme/zweather_0_0.md | 7 +- .../zwave/doc/zwaveproducts/ws100_0_0.md | 7 +- _addons_bindings/zwave/doc/zyxel/st812_0_0.md | 7 +- _addons_persistences/rrd4j/readme.md | 66 +- _addons_transformations/exec/readme.md | 15 + _addons_transformations/javascript/readme.md | 15 + _addons_transformations/jsonpath/readme.md | 15 + _addons_transformations/map/readme.md | 15 + _addons_transformations/regex/readme.md | 15 + _addons_transformations/scale/readme.md | 119 ++- _addons_transformations/xpath/readme.md | 15 + _addons_transformations/xslt/readme.md | 15 + concepts/units-of-measurement.md | 114 +++ 320 files changed, 5464 insertions(+), 1706 deletions(-) create mode 100644 _addons_bindings/cardio2e1/readme.md create mode 100644 _addons_bindings/solaredge/readme.md create mode 100644 _addons_bindings/zwave/doc/ge/ge14299_0_0.md create mode 100644 _addons_bindings/zwave/doc/ge/motiondimmerswitch_0_0.md create mode 100644 _addons_bindings/zwave/doc/honeywell/39358_0_0.md delete mode 100644 _addons_bindings/zwave/doc/inovelli/nzw31_0_0.md create mode 100644 _addons_bindings/zwave/doc/logic/scenecontroller_0_0.md create mode 100644 _addons_bindings/zwave/doc/oomi/ft130_0_0.md delete mode 100644 _addons_bindings/zwave/doc/philio/pan061b_1_8.md delete mode 100644 _addons_bindings/zwave/doc/shenzhen/sirenalarm_0_0.md create mode 100644 _addons_bindings/zwave/doc/telldus/tzwp102_0_0.md rename _addons_bindings/zwave/doc/{digitalhome/dhswinblw_0_0.md => wintop/dhswinblwdhs_0_0.md} (61%) create mode 100644 _addons_bindings/zwave/doc/zwaveme/fgr316_0_0.md diff --git a/_addons_bindings/astro/readme.md b/_addons_bindings/astro/readme.md index 22e3e4ad5f..d803f50b6c 100644 --- a/_addons_bindings/astro/readme.md +++ b/_addons_bindings/astro/readme.md @@ -48,7 +48,7 @@ Optionally, a refresh `interval` (in seconds) can be defined to also calculate p * `duration` (Number) * **group** `position` * **channel** - * `azimuth, elevation` (Number) + * `azimuth, elevation, shadeLength` (Number) * **group** `radiation` * **channel** * `direct, diffuse, total` (Number) diff --git a/_addons_bindings/cardio2e1/readme.md b/_addons_bindings/cardio2e1/readme.md new file mode 100644 index 0000000000..2eb4d952dd --- /dev/null +++ b/_addons_bindings/cardio2e1/readme.md @@ -0,0 +1,136 @@ +--- +id: cardio2e +label: Cardio2e +title: Cardio2e - Bindings +type: binding +description: "The openHAB Cardio2e binding allows connecting to Secant Cardio IIé home automation system installations. Dimming or switching lights on and off, switching devices on and off, activating roller shutters, executing scenarios, managing HVACs or activating system security are only some examples." +source: https://github.com/openhab/openhab1-addons/blob/master/bundles/binding/org.openhab.binding.cardio2e/README.md +since: 1x +install: manual +--- + + + +{% include base.html %} + +# Cardio2e Binding +The openHAB Cardio2e binding allows connecting to Secant Cardio IIé home automation system installations. Dimming or switching lights on and off, switching devices on and off, activating roller shutters, executing scenarios, managing HVACs or activating system security are only some examples. + +To access your Cardio system you need an RS-232 interface (e.g. a Prolific PL-2303 based USB to RS-232 converter interface) and a DB-9 to RJ-11 cable suitable for either Cardio PC or Cardio ACC port. You can use this [schema](https://github.com/openhab/openhab1-addons/files/999699/PcCardio_Cable.pdf&sa=D&ust=1528711214015000) to build your Cardio PC port cable. + +> Note: You can also use the Cardio accessory port (ACC) instead of PC port, so you must crimp the RJ-11 in reverse order, exchange RD and TD signals from the DB-9 connector with respect to the previous PC schematic (pins 2 and 3) and do not connect pin 7. + +## Binding Configuration +This binding can be configured in the file `configurations/openhab.cfg` (openHAB 1) or `conf/services/cardio2e.cfg` (openHAB 2). + +| Property | Default | Required | Description | +|----------|---------|:--------:|-------------| +| port | | Yes | Serial RS-232 port. Examples: '/dev/ttyUSB0' for Linux, 'COM1' for Windows. | +| programcode | 00000 |No | Installer program code for login. | +| securitycode | | No | Security code for arm / disarm alarm. | +| zones | false | No | Alarm zones state detection. Enables alarm zones state detection (by default 'false' for minimum use of resources). | +| zoneUnchangedMinRefreshDelay | 600000 | No | Minimum delay in milliseconds for zone detection refresh when no state changes succeed (by default '600000' milliseconds = 10 minutes). | +| datetimeMaxOffset | 15 | No | Date and time maximum offset allowed (in minutes) for progressive (step by step, minute by minute) date and time state update. Special values: '0' will remove offset limit, '-1' will disable progressive update and will remove offset limit, '-2' will do unconditional update without any filter even if current date and time of Cardio IIé matches the update. | +| firstUpdateWillSetDatetime | false | No | Always will set Cardio IIé clock on first date and time update from last binding start, even if allowedDatetimeUpdateHour was set. | +| allowedDatetimeUpdateHour | -1 | No | Allows date and time updates on specified hour only (for example, a safe hour when no events will be triggered by Cardio's schedules). Valid values are from '0' to '23' ('-1' disables hour restriction).| +| testmode | false | No | Enables fake port console test mode, for developer debug purposes only. Warning: Real communication with Cardio IIé will not work if enabled! | +| minDelayBetweenReceivingAndSending | 200 | No | Minimum delay in milliseconds between receiving and sending, for expert tuning only. By default '200' milliseconds (tested safe value).| +| minDelayBetweenSendings | 300 | No | Minimum delay in milliseconds between sendings, for expert tuning only. By default '300' milliseconds (tested safe value). | +| filterUnnecessaryCommand | false | No | Avoid sending commands when the last value of the object reported by Cardio IIé is the same value as the command value. | +| filterUnnecessaryReverseModeUpdate | true | No | Avoid sending updates (reverse mode) when the last value of the object reported by Cardio IIé is the same value as the update value.| +| smartSendingEnabledObjectTypes | | No | Comma separated list of smart sending enabled object types. Smart sending enabled means that no contradictory commands will be stored in the sending buffer for that object type, so that if a command directed to a specific object exists in sending buffer and a new command is received for the same object, the command stored will be replaced by the new one. Valid values are 'LIGHTING', 'RELAY', 'HVAC_CONTROL', 'DATE_AND_TIME', 'SCENARIO', 'SECURITY', 'ZONES_BYPASS' and 'CURTAIN'. | + +### Example +``` +cardio2e:port=/dev/ttyUSB0 +cardio2e:programcode=00000 +cardio2e:securitycode=12345 +cardio2e:zones=true +cardio2e:filterUnnecessaryCommand=true +cardio2e:smartSendingEnabledObjectTypes=LIGHTING,RELAY,HVAC_CONTROL,DATE_AND_TIME,SCENARIO,SECURITY,ZONES_BYPASS,CURTAIN +``` + +## Items Configuration +### Description +In order to bind an item to a Cardio IIé system you need to provide configuration settings. The easiest way to do so is to add binding information in your items file. The syntax for the Cardio2e binding configuration string is explained here: +* **LIGHTING**: +`c2e="LIGHTING,object_number"` +where 'object_number' is a number between 1 and 160 that represent the light number you want to control. You can bind both 'Switch' and 'Dimmer' items types. +*Reverse mode*: Can be enabled by adding '!' symbol before 'LIGHTING' (example: `c2e="!LIGHTING,20"`), so the Cardio object will be considered as a control, not an actuator. You can bind in reverse mode an unused lighting Cardio control in order to send commands to openHAB item, and to receive item updates (you can enable a unused Cardio lighting control by assigning it a fake X10 address). +*Dimmer correction*: Can be enabled by adding '%' symbol before 'object_number' (example: `c2e="LIGHTING,%1"`), in order to consider Cardio lighting 1% values as 0% (powered off). This correction is necessary when Cardio is programmed to turn on a light by presence, since when power on time expires, Cardio sends a 1% value to the DM1 instead of 0% power off value (in fact, in practice, any value less than 10% in a DM1 will turn off the light). +*Autoupdate*: Cardio always reports the status of its 'LIGHTING' objects after executing a command, so we recommend that you add 'autoupdate=false' in the item settings to make sure that the item's value always matches Cardio's value (example: `Dimmer My_Light {c2e="LIGHTING,2",autoupdate=false}`). Not applicable when "reverse mode" is used. +* **RELAY**: +*Option #1*: `c2e="RELAY,object_number"` +where 'object_number' is a number between 1 and 40 that represents the relay number you want to control. You can only bind 'Switch' items type. +*Option #2*: `c2e="RELAY,shutter_up_object_number,shutter_down_object_number"` +where 'shutter_up_object_number' and 'shutter_down_object_number' are numbers between 1 and 40 that represents the relay numbers of a pair of timed relays used to move shutter up and down. You can only bind 'Rollershutter' items type. +*Reverse mode*: Can be enabled by adding '!' symbol before 'RELAY' (example: `c2e="!RELAY,4"`), so the Cardio object will be considered as a control, not an actuator. You can bind in reverse mode an unused relay Cardio control in order to send commands to openHAB item, and to receive item updates. +*Autoupdate*: Cardio always reports the status of its 'RELAY' objects after executing a command, so we recommend that you add 'autoupdate=false' in the item settings to make sure that the item's value always matches Cardio's value (example: `RollerShutter My_Shutter {c2e="RELAY,5,6",autoupdate=false}`). Not applicable when "reverse mode" is used. +* **HVAC_TEMPERATURE**: +`c2e="HVAC_TEMPERATURE,hvac_zone"` +can be bound to a 'Number' item type, where 'hvac_zone' is a value between 1 and 5 that represents the Cardio IIé HVAC zone number you want to receive temperature value states from (the unit of measurement, ºC or ºF, will be the same that was set in Cardio system config). +Example: `Number My_Temperature {c2e="HVAC_TEMPERATURE,1"}`). +* **HVAC_CONTROL**: +*One parameter options*: `c2e="HVAC_CONTROL,hvac_zone"` +where 'hvac_zone' is a value between 1 and 5 that represents the Cardio IIé HVAC zone number you want to control. You can bind to a 'Switch' item in order to simply switch on / off Cardio IIé HVAC zone (example: `Switch My_HVAC_Switch {c2e="HVAC_CONTROL,1"}`). You also can bind to a 'Number' item in order to control HVAC zone with KNX standard internetworking DPT 20.105 HVAC control values (auto=0, heating=1, cooling= 3, off=6), and no KNX compliant values for Cardio IIé additional submodes (normal=254, economy=255). +*Two parameters options*: `c2e="HVAC_CONTROL,hvac_zone,function"` +where 'hvac_zone' is a value between 1 and 5 that also represents the Cardio IIé HVAC zone number, and 'function' is the HVAC function you want to control: 'FAN' for fan control, 'AUTO', 'COOLING' and 'HEATING' for HVAC mode switch, and 'ECONOMY' and 'NORMAL' for additional submodes. You can bind to a 'Switch' item in order to switch on / off Cardio IIé HVAC functions, or you can bind to a 'Number' item in order to adjust cooling and heating setpoints (Cardio IIé has two different setpoints, one for cooling and one for heating, and the unit of measurement, ºC or ºF, will be the same that was set in Cardio system config). +*Autoupdate*: Cardio always reports the status of its 'HVAC_CONTROL' objects after executing a command, so we recommend that you add 'autoupdate=false' in the item settings to make sure that the item's value always matches Cardio's value. +*Examples*: + ``` + Switch My_HVAC_Switch {c2e="HVAC_CONTROL,1",autoupdate=false} + Number My_HVAC_KNX_Mode {c2e="HVAC_CONTROL,1"[,optional_KNX_binding_config],autoupdate=false} + Switch My_HVAC_Fan "Fan" {c2e="HVAC_CONTROL,1,FAN",autoupdate=false} + Switch My_HVAC_Auto "Auto mode" {c2e="HVAC_CONTROL,1,AUTO",autoupdate=false} + Switch My_HVAC_Heating "Heating mode" {c2e="HVAC_CONTROL,1,HEATING",autoupdate=false} + Switch My_HVAC_Cooling "Cooling mode" {c2e="HVAC_CONTROL,1,COOLING",autoupdate=false} + Switch My_HVAC_Eco "Economy submode" {c2e="HVAC_CONTROL,1,ECONOMY",autoupdate=false} + Switch My_HVAC_Normal "Normal submode" {c2e="HVAC_CONTROL,1,NORMAL",autoupdate=false} + Number My_HVAC_Cooling_Setpoint "Cooling setpoint [%.1f °C]" {c2e="HVAC_CONTROL,1,COOLING",autoupdate=false} + Number My_HVAC_Heating_Setpoint "Heating setpoint [%.1f °C]" {c2e="HVAC_CONTROL,1,HEATING",autoupdate=false} + ``` +* **ZONES**: +`c2e="ZONES,zone_number,zone_type"` +can be bound to a 'Contact' or 'Switch' item type, where 'zone_number' is a value between 1 and 16 that represents the Cardio IIé alarm zone number you want to monitor, and 'zone_type' is a value that specifies zone type defined in Cardio system config: 'OPEN' for NO (normally open), 'CLOSED' for NC (normally closed) and 'NORMAL' for EOL (end of line resistor). WARNING: Alarm zones state detection is disabled by default for minimum use of resources. In order to monitor alarm zones you must set parameter 'zones=true' in binding configuration. +*Invert value*: Can be enabled by adding '!' symbol before 'ZONES', so the reported status of the Cardio alarm zone will be inverted. +Examples: + ``` + Contact My_Contact {c2e="ZONES,1,NORMAL"} + Switch My_Contact {c2e="ZONES,1,CLOSED"} + Contact My_Contact {c2e="!ZONES,2,OPEN"} + Switch My_Contact {c2e="!ZONES,2,NORMAL"} + ``` +* **ZONES_BYPASS**: +`c2e="ZONES_BYPASS,zone_number"` +can be bound to a 'Switch' item type, where 'zone_number' is a value between 1 and 16 that represents the Cardio IIé alarm zone number you want to bypass (example: `Switch My_Zone_Bypass {c2e="ZONES_BYPASS,1"}`). +*Invert value*: Can be enabled by adding '!' symbol before 'ZONES_BYPASS', so the operating mode of the Cardio IIé alarm zone bypass will be inverted, so that the item will indicate whether the zone will be armed for Cardio IIé security system or not (example: `Switch My_Zone_Armed {c2e="!ZONES_BYPASS,1"}`). +*Note about autoupdate*: Cardio WILL NOT report the status of its 'ZONES_BYPASS' objects after executing a command, but it will do it after arming security system. So we recommend that you DO NOT add 'autoupdate=false' in the item settings. +* **DATE_AND_TIME**: +`c2e="DATE_AND_TIME"` +can be bound to a 'DateTime' item type. When a date and time value command is received Cardio's clock will be unconditionally set to item date and time value. However, upon receiving an update, the clock will be updated based on the criteria defined in the binding configuration (see 'datetimeMaxOffset', 'firstUpdateWillSetDatetime' and 'allowedDatetimeUpdateHour' config parameters). +Because Cardio's clock usually lags behind, you can use NTP binding in order to keep the clock on time, for example, sending updates every 15 minutes. + Time sync example with OH1 NTP binding: `DateTime My_date_and_time {ntp="Europe/Madrid:es_ES", c2e="DATE_AND_TIME")` + Time sync example with OH2 NTP binding: `DateTime My_date_and_time {channel="ntp:ntp:cardiosync:dateTime", c2e="DATE_AND_TIME")` +* **SCENARIO**: +`c2e="SCENARIO"` +can be bound to 'Number' items type. When a number value command between 0 and 41 is received, the corresponding Cardio scene number between 1 and 42 will be activated (command value + 1). +Note that numbers between 0 and 41 are used to provide direct compatibility with the scene numbers range used in protocols such as KNX, where the first scene is encoded with the number 0. +* **SECURITY**: +`c2e="SECURITY"` +can be bound to 'Switch' and 'Number' items type. +Using a 'Switch' item we can arm / disarm Cardio security system by ON / OFF commands as well as receive state updates (securitycode must be previously set in config file). +*Autoupdate*: Cardio always reports the status of its 'SECURITY' objects after executing a command, so we recommend that you add 'autoupdate=false' in the item settings to make sure that the item's value always matches Cardio's value (example: `Switch Security_Arm {c2e="SECURITY",autoupdate=false}`). +*Error code*: If security system could not be armed, we can show the reason as numeric error code value update received in a linked 'Number' item (example: `Number Security_Error {c2e="SECURITY", autoupdate=false}`). Likewise, we can configure an entry in the sitemap that translates those values by its corresponding description. +*Sitemap example*: + ``` + Text item=Security_Error label="ERROR # [%d]" visibility=[Security_Error>0] labelcolor=[Security_Error>0="red"] valuecolor=[Security_Error>0="red"] + Text item=Security_Error label="(security code is not valid)" icon="none" visibility=[Security_Error==4] labelcolor=[Security_Error>0="red"] + Text item=Security_Error label="(there are open zones)" icon="none" visibility=[Security_Error==16] labelcolor=[Security_Error>0="red"] + Text item=Security_Error label="(there is a power problem)" icon="none" visibility=[Security_Error==17] labelcolor=[Security_Error>0="red"] + Text item=Security_Error label="(unknown reason)" icon="none" visibility=[Security_Error==18] labelcolor=[Security_Error>0="red"] + ``` +* **CURTAIN**: +`c2e="CURTAIN,object_number"` +where 'object_number' is a number between 1 and 80 that represent the shutter number you want to control. You can bind both 'RollerShutter' and 'Dimmer' items types (no STOP or MOVE commands are supported, and 100% value means shutter down). Note that 'CURTAIN' objects are only available in lastest Cardio IIé firmware versions. +*Reverse mode*: Can be enabled by adding '!' symbol before 'CURTAIN'' (example: `c2e="!CURTAIN,13"`), so the Cardio object will be considered as a control, not an actuator. You can bind in reverse mode an unused curtain Cardio control in order to send commands to openHAB item, and to receive item updates. +*Autoupdate*: Cardio always reports the status of its 'CURTAIN' objects after executing a command, so we recommend that you add 'autoupdate=false' in the item settings to make sure that the item's value always matches Cardio's value (example: `Dimmer My_Curtain {c2e="CURTAIN,3",autoupdate=false}`). Not applicable when "reverse mode" is used. diff --git a/_addons_bindings/comfoair1/readme.md b/_addons_bindings/comfoair1/readme.md index d142edda43..c06d7c2b3e 100644 --- a/_addons_bindings/comfoair1/readme.md +++ b/_addons_bindings/comfoair1/readme.md @@ -55,9 +55,18 @@ where `` is replaced with the ComfoAir command from the list bel | incomming_fan | Read | | | outgoing_fan | Read | | | filter_running | Read | | +| filter_error | Read | | | filter_error_intern | Read | | | filter_error_extern | Read | | +| filter_reset | Write | filterhours will be reset to 0 | | error_message | Read | | +| ewt_temperatur | Read | | +| ewt_temperatur_low | Read | | +| ewt_temperatur_high | Read | | +| ewt_speed | Read | | +| ewt_mode | Read | | +| bypass_mode | Read | | +| error_reset | Write | error messages will be reset | ## Limitations diff --git a/_addons_bindings/digitalstrom/readme.md b/_addons_bindings/digitalstrom/readme.md index b168188a76..bd27dc10eb 100644 --- a/_addons_bindings/digitalstrom/readme.md +++ b/_addons_bindings/digitalstrom/readme.md @@ -389,6 +389,13 @@ The digitalSTROM-Server **Notes: ** +*Generally:* + +* The digitalSTROM-Server only informs the binding about scene-commands. So if you set the output value of devices e.g. through the dSS-App, the binding will not be informed about the changes and you have to send a "refresh-command" to update the channel. +* If you press a physical switch at your digitalSTROM-installation and the called scene-value is not red out yet, it can take a bit time to read it out and change the state of the channel. +It the scene-value is red out, the state will change immediately. +See also *General-Informations/digitalSTROM-Scenes*. + *Channels with accepted command type increase and decrease:* * digitalSTROM will only evaluate increase and decrease commands, if a scene was called before which turn the device on. diff --git a/_addons_bindings/fritzboxtr0641/readme.md b/_addons_bindings/fritzboxtr0641/readme.md index ced375efc3..dc9470b56f 100644 --- a/_addons_bindings/fritzboxtr0641/readme.md +++ b/_addons_bindings/fritzboxtr0641/readme.md @@ -148,7 +148,7 @@ NULL=unknown Now, as item configuration use (the addon "Map Transformation" must be installed): ``` -Contact cFboxMacOnline "Presence (Wifi) [MAP(presence.map):%s]" {fritzboxtr064="maconline:11-22-33-44-55-66 } +Contact cFboxMacOnline "Presence (Wifi) [MAP(presence.map):%s]" {fritzboxtr064="maconline:11-22-33-44-55-66"} ``` ### Rules diff --git a/_addons_bindings/fronius/readme.md b/_addons_bindings/fronius/readme.md index 3d796f92b2..39604c7654 100644 --- a/_addons_bindings/fronius/readme.md +++ b/_addons_bindings/fronius/readme.md @@ -81,8 +81,6 @@ Number UAC { channel="fronius:powerinverter:mybridge:myinverter:inverterdatachan Number UDC { channel="fronius:powerinverter:mybridge:myinverter:inverterdatachanneludc" } Number Grid_Power { channel="fronius:powerinverter:mybridge:myinverter:powerflowchannelpgrid" } Number Load_Power { channel="fronius:powerinverter:mybridge:myinverter:powerflowchannelpload" } -Number Load_Power { channel="fronius:powerinverter:mybridge:myinverter:powerflowchannelpload" } -Number Load_Power { channel="fronius:powerinverter:mybridge:myinverter:powerflowchannelpload" } Number Battery_Power { channel="fronius:powerinverter:mybridge:myinverter:powerflowchannelpakku" } ``` diff --git a/_addons_bindings/gardena/readme.md b/_addons_bindings/gardena/readme.md index 5529868bf2..8612c2d424 100644 --- a/_addons_bindings/gardena/readme.md +++ b/_addons_bindings/gardena/readme.md @@ -22,14 +22,15 @@ This binding allows you to integrate, view and control Gardena Smart Home device Devices connected to Gardena Smart Home, currently: -| Thing type | Name | -|--------------------------|-----------------------| -| bridge | smart Home Gateway | -| mower | smart Sileno(+) Mower | -| watering_computer | smart Water Control | -| sensor | smart Sensor | -| electronic_pressure_pump | smart Pressure Pump | -| power | smart Power Plug | +| Thing type | Name | +|--------------------------|--------------------------| +| bridge | smart Home Gateway | +| mower | smart Sileno(+) Mower | +| watering_computer | smart Water Control | +| sensor | smart Sensor | +| electronic_pressure_pump | smart Pressure Pump | +| power | smart Power Plug | +| ic24 | smart Irrigation Control | The schedules are not yet integrated! @@ -118,11 +119,14 @@ sendCommand(ITEM_NAME, RefreshType.REFRESH) ```shell // smart Water Control -Switch Watering_Valve "Valve" { channel="gardena:watering_computer:home:myvalve:outlet#valve_open"} -Number Watering_Duration "Duration [%d min]" { channel="gardena:watering_computer:home:wasserhahn:outlet#button_manual_override_time"} +Switch Watering_Valve "Valve" { channel="gardena:watering_computer:home:myValve:outlet#valve_open" } +Number Watering_Duration "Duration [%d min]" { channel="gardena:watering_computer:home:myValve:outlet#button_manual_override_time" } // smart Power Plug -String Power_Timer "Power Timer [%s]" { channel="gardena:power:home:myPowerplug:power#power_timer"} +String Power_Timer "Power Timer [%s]" { channel="gardena:power:home:myPowerplug:power#power_timer" } + +// smart Irrigation Control +Number Watering_Timer_1 "Watering Timer 1 [%d min] { channel="gardena:ic24:home:myIrrigationController:watering#watering_timer_1" } ``` ```shell @@ -132,6 +136,9 @@ Watering_Duration.sendCommand(ON) Power_Timer.sendCommand("on") Power_Timer.sendCommand("off") Power_Timer.sendCommand("180") // on for 180 seconds + +Watering_Timer_1.sendCommand(0) // turn off watering +Watering_Timer_1.sendCommand(30) // turn on for 30 minutes ``` ### Debugging and Tracing diff --git a/_addons_bindings/kodi/readme.md b/_addons_bindings/kodi/readme.md index cd5448d4de..d113579712 100644 --- a/_addons_bindings/kodi/readme.md +++ b/_addons_bindings/kodi/readme.md @@ -99,6 +99,7 @@ The Kodi thing supports the following channels: | inputaction | String | Sends a predefined action to Kodi to control the UI and/or perform other tasks. Valid commands are: `left`, `right`, `up`, `down`, `pageup`, `pagedown`, `select`, `highlight`, `parentdir`, `parentfolder`, `back`, `menu`, `previousmenu`, `info`, `pause`, `stop`, `skipnext`, `skipprevious`, `fullscreen`, `aspectratio`, `stepforward`, `stepback`, `bigstepforward`, `bigstepback`, `chapterorbigstepforward`, `chapterorbigstepback`, `osd`, `showsubtitles`, `nextsubtitle`, `cyclesubtitle`, `playerdebug`, `codecinfo`, `playerprocessinfo`, `nextpicture`, `previouspicture`, `zoomout`, `zoomin`, `playlist`, `queue`, `zoomnormal`, `zoomlevel1`, `zoomlevel2`, `zoomlevel3`, `zoomlevel4`, `zoomlevel5`, `zoomlevel6`, `zoomlevel7`, `zoomlevel8`, `zoomlevel9`, `nextcalibration`, `resetcalibration`, `analogmove`, `analogmovex`, `analogmovey`, `rotate`, `rotateccw`, `close`, `subtitledelayminus`, `subtitledelay`, `subtitledelayplus`, `audiodelayminus`, `audiodelay`, `audiodelayplus`, `subtitleshiftup`, `subtitleshiftdown`, `subtitlealign`, `audionextlanguage`, `verticalshiftup`, `verticalshiftdown`, `nextresolution`, `audiotoggledigital`, `number0`, `number1`, `number2`, `number3`, `number4`, `number5`, `number6`, `number7`, `number8`, `number9`, `smallstepback`, `fastforward`, `rewind`, `play`, `playpause`, `switchplayer`, `delete`, `copy`, `move`, `screenshot`, `rename`, `togglewatched`, `scanitem`, `reloadkeymaps`, `volumeup`, `volumedown`, `mute`, `backspace`, `scrollup`, `scrolldown`, `analogfastforward`, `analogrewind`, `moveitemup`, `moveitemdown`, `contextmenu`, `shift`, `symbols`, `cursorleft`, `cursorright`, `showtime`, `analogseekforward`, `analogseekback`, `showpreset`, `nextpreset`, `previouspreset`, `lockpreset`, `randompreset`, `increasevisrating`, `decreasevisrating`, `showvideomenu`, `enter`, `increaserating`, `decreaserating`, `setrating`, `togglefullscreen`, `nextscene`, `previousscene`, `nextletter`, `prevletter`, `jumpsms2`, `jumpsms3`, `jumpsms4`, `jumpsms5`, `jumpsms6`, `jumpsms7`, `jumpsms8`, `jumpsms9`, `filter`, `filterclear`, `filtersms2`, `filtersms3`, `filtersms4`, `filtersms5`, `filtersms6`, `filtersms7`, `filtersms8`, `filtersms9`, `firstpage`, `lastpage`, `guiprofile`, `red`, `green`, `yellow`, `blue`, `increasepar`, `decreasepar`, `volampup`, `volampdown`, `volumeamplification`, `createbookmark`, `createepisodebookmark`, `settingsreset`, `settingslevelchange`, `stereomode`, `nextstereomode`, `previousstereomode`, `togglestereomode`, `stereomodetomono`, `channelup`, `channeldown`, `previouschannelgroup`, `nextchannelgroup`, `playpvr`, `playpvrtv`, `playpvrradio`, `record`, `togglecommskip`, `showtimerrule`, `leftclick`, `rightclick`, `middleclick`, `doubleclick`, `longclick`, `wheelup`, `wheeldown`, `mousedrag`, `mousemove`, `tap`, `longpress`, `pangesture`, `zoomgesture`, `rotategesture`, `swipeleft`, `swiperight`, `swipeup`, `swipedown`, `error`, `noop`. | | systemcommand | String | This channel allows to send system commands to `shutdown`, `suspend`, `hibernate` or `reboot` Kodi | | mediatype | String | The media type of the current file. Valid return values are: `unknown`, `channel`, `episode`, `movie`, `musicvideo`, `picture`, `radio`, `song`, `video` | +| genreList | String | A comma-separated list of genres of the current file | | thumbnail | Image | The URL to the thumbnail of the current file | | fanart | Image | The URL to the fanart of the current file | | playnotification | String | Plays the notification sound by a given URI | @@ -160,6 +161,7 @@ String myKodi_input "Input" { channel="kodi: String myKodi_inputtext "Inputtext" { channel="kodi:kodi:myKodi:inputtext" } String myKodi_systemcommand "Systemcommand" { channel="kodi:kodi:myKodi:systemcommand" } String myKodi_mediatype "Mediatype [%s]" { channel="kodi:kodi:myKodi:mediatype" } +String myKodi_genrelist "Genres [%s]" { channel="kodi:kodi:myKodi:genreList" } Image myKodi_thumbnail { channel="kodi:kodi:myKodi:thumbnail" } Image myKodi_fanart { channel="kodi:kodi:myKodi:fanart" } Number:Time myKodi_currenttime "Current Time [%d %unit%]" { channel="kodi:kodi:myKodi:currenttime" } @@ -191,6 +193,7 @@ sitemap demo label="myKodi" Selection item=myKodi_input mappings=[Up='Up', Down='Down', Left='Left', Right='Right', Select='Select', Back='Back', Home='Home', ContextMenu='ContextMenu', Info='Info'] Selection item=myKodi_systemcommand mappings=[Shutdown='Herunterfahren', Suspend='Bereitschaft', Reboot='Neustart'] Text item=myKodi_mediatype + Text item=myKodi_genrelist Image item=myKodi_thumbnail Image item=myKodi_fanart Text item=myKodi_currenttime diff --git a/_addons_bindings/meteostick/readme.md b/_addons_bindings/meteostick/readme.md index 376e8de520..094b1e9a9d 100644 --- a/_addons_bindings/meteostick/readme.md +++ b/_addons_bindings/meteostick/readme.md @@ -48,8 +48,8 @@ Set mode to one of the following depending on your device and region: | Mode | Device | Region | Frequency | |-------|--------------|------------------|-----------| | 0 | Davis | North America | 915 Mhz | -| 1 | Davis | Australia | 915 Mhz | -| 2 | Davis | Europe | 868 Mhz | +| 1 | Davis | Europe | 868 Mhz | +| 2 | Davis | Australia | 915 Mhz | | 3 | Fine Offset | North America | 915 Mhz | | 4 | Fine Offset | Europe | 868 Mhz | | 5 | Davis | New Zealand | 931.5 Mhz | @@ -77,15 +77,17 @@ Set mode to one of the following depending on your device and region: | outdoor-temperature | Number:Temperature | Outside temperature | | humidity | Number | Humidity | | wind-direction | Number:Angle | Wind direction | +| wind-direction-last2min-average | Number:Angle | Wind direction average over last 2 minutes | | wind-speed | Number:Speed | Wind speed | -| rain-raw | Number | Raw rain counter from the tipping bucket sensor | +| wind-speed-last2min-average | Number:Speed | Wind speed average over last 2 minutes | +| wind-speed-last2min-maximum | Number:Speed | Wind speed maximum over last 2 minutes | +| rain-raw | Number | Raw rain counter from the tipping spoon sensor | | rain-currenthour | Number:Length | The rainfall in the last 60 minutes | | rain-lasthour | Number:Length | The rainfall in the previous hour | | solar-power | Number | Solar power from the sensor station | | signal-strength | Number | Received signal strength | | low-battery | Switch | Low battery warning | - #### Rainfall There are three channels associated with rainfall. @@ -94,9 +96,93 @@ The rainfall in the previous hour is the rainfall for each hour of the day and i ## Full Example -Things can be defined in the .things file as follows +This example uploads weather data to for your personal weather station at Weather Underground every two minutes. + +Steps: + +1. Install the [MeteoStick](http://www.smartbedded.com/wiki/index.php/Meteostick) binding for use with your [Davis Vantage Vue Integrated Sensor Suite (ISS)](https://www.davisnet.com/solution/vantage-vue/). +1. [Register](https://www.wunderground.com/personal-weather-station/signup.asp) your personal weather station with Weather Underground and make note of the station ID and password issued. +1. Add the following files to your openHAB configuration: + +### things/meteostick.things + +Things can be defined in the .things file as follows: ``` meteostick:meteostick_bridge:receiver [ port="/dev/tty.usbserial-AI02XA60", mode=1 ] meteostick:meteostick_davis_iss:iss (meteostick:meteostick_bridge:receiver) [ channel=1, spoon=0.2 ] ``` + +Note the configuration options for `port`, `mode`, `channel` and `spoon` above and adjust as needed for your specific hardware. + +### items/meteostick.items + +``` +Number:Pressure MeteoStickPressure "Meteostick Pressure [%.1f hPa]"{ channel="meteostick:meteostick_bridge:receiver:pressure" } +Number:Temperature DavisVantageVueOutdoorTemperature "ISS Outdoor Temp [%.1f °C]" { channel="meteostick:meteostick_davis_iss:iss:outdoor-temperature" } +Number DavisVantageVueHumidity "ISS Humidity [%.0f %%]" { channel="meteostick:meteostick_davis_iss:iss:humidity" } +Number:Angle DavisVantageVueWindDirection "ISS Wind Direction [%.0f °]" { channel="meteostick:meteostick_davis_iss:iss:wind-direction" } +Number:Angle DavisVantageVueWindDirectionAverage "ISS Average Wind Direction [%.0f °]" { channel="meteostick:meteostick_davis_iss:iss:wind-direction-last2min-average" } +Number:Speed DavisVantageVueWindSpeed "ISS Wind Speed [%.1f m/s]" { channel="meteostick:meteostick_davis_iss:iss:wind-speed" } +Number:Speed DavisVantageVueWindSpeedAverage "ISS Average Wind Speed [%.1f m/s]" { channel="meteostick:meteostick_davis_iss:iss:wind-speed-last2min-average" } +Number:Speed DavisVantageVueWindSpeedMaximum "ISS Maximum Wind Speed [%.1f m/s]" { channel="meteostick:meteostick_davis_iss:iss:wind-speed-last2min-maximum" } +Number:Length DavisVantageVueRainCurrentHour "ISS Rain Current Hour [%.1f mm]" { channel="meteostick:meteostick_davis_iss:iss:rain-currenthour" } +``` + +### rules/meteostick.rules + +Replace `YOUR_ID` and `your_password` below with the values from the the Weather Underground registration process. + +``` +import java.net.URLEncoder +import java.text.SimpleDateFormat +import java.util.Date +import java.util.Map +import java.util.TimeZone + +/* Uploads weather station data using this format: + + http://wiki.wunderground.com/index.php/PWS_-_Upload_Protocol + */ + +rule PWS +when + Item DavisVantageVueWindDirectionAverage received update +then + val id = 'YOUR_ID' + val pw = 'your_password' + val sdf = new SimpleDateFormat('yyyy-MM-dd HH:mm:ss') + sdf.setTimeZone(TimeZone.getTimeZone('UTC')) + val Map params = newLinkedHashMap( + 'action' -> 'updateraw', + 'ID' -> id, + 'PASSWORD' -> pw, + 'dateutc' -> sdf.format(new Date()), + 'winddir' -> DavisVantageVueWindDirection.getStateAs(QuantityType).toUnit('°').intValue, + 'windspeedmph' -> DavisVantageVueWindSpeed.getStateAs(QuantityType).toUnit('mph').doubleValue, + 'windgustmph' -> DavisVantageVueWindSpeedMaximum.getStateAs(QuantityType).toUnit('mph').doubleValue, + 'windgustdir' -> DavisVantageVueWindDirectionAverage.getStateAs(QuantityType).toUnit('°').intValue, + 'windspdmph_avg2m' -> DavisVantageVueWindSpeedAverage.getStateAs(QuantityType).toUnit('mph').doubleValue, + 'winddir_avg2m' -> DavisVantageVueWindDirectionAverage.getStateAs(QuantityType).toUnit('°').intValue, + 'humidity' -> DavisVantageVueHumidity.state, + 'tempf' -> DavisVantageVueOutdoorTemperature.getStateAs(QuantityType).toUnit('°F').doubleValue, + 'rainin' -> DavisVantageVueRainCurrentHour.getStateAs(QuantityType).toUnit('in').doubleValue, + 'baromin' -> MeteoStickPressure.getStateAs(QuantityType).toUnit('inHg').doubleValue, + 'softwaretype' -> 'openHAB 2.3') + + var url = 'https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?' + var first = true + for (key : params.keySet()) { + if (!first) { + url += '&' + } + url += key + '=' + URLEncoder::encode(params.get(key).toString, 'UTF-8') + first = false + } + + logDebug('PWS', 'url is {}', url) + sendHttpGetRequest(url) +end +``` + +openHAB will now report your weather station data to Weather Underground every two minutes. diff --git a/_addons_bindings/mihome/readme.md b/_addons_bindings/mihome/readme.md index 958dc51b2e..6246530411 100644 --- a/_addons_bindings/mihome/readme.md +++ b/_addons_bindings/mihome/readme.md @@ -22,7 +22,7 @@ from the [Google Play](https://play.google.com/store/apps/details?id=com.xiaomi. ## Supported devices -* Xiaomi Smart Gateway v2 (with radio support) +* Xiaomi Smart Gateway v2 (with radio support) or v3 * Xiaomi Smart Temperature and Humidity Sensor (round one) * Xiaomi Smart Door/Window Sensor (round one) * Xiaomi Wireless Switch (round one) @@ -47,20 +47,18 @@ from the [Google Play](https://play.google.com/store/apps/details?id=com.xiaomi. ## Setup * Install the binding -* Setup Gateway to be discoverable - - 1. Add Gateway 2 or 3 to your WiFi Network - 2. Install MiHome app from [Google Play](https://play.google.com/store/apps/details?id=com.xiaomi.smarthome) or [AppStore](https://itunes.apple.com/app/mi-home-xiaomi-for-your-smarthome/id957323480) (your phone may need to be changed to English language first) - 3. Set your region to Mainland China under Settings -> Locale (seems to be required) - 4. Update gateway to the latest firmware (note that update window may pop up sequentially) - 5. Enable developer mode: +* Is your gateway already configured to connect to your WiFi? If not: + 1. Install MiHome app from [Google Play](https://play.google.com/store/apps/details?id=com.xiaomi.smarthome) or [AppStore](https://itunes.apple.com/app/mi-home-xiaomi-for-your-smarthome/id957323480) (your phone may need to be changed to English language first) + 2. In the app create a Mi Home account and make sure to set your region to Mainland (China) under Settings -> Locale + 3. If asked, update your gateway to the latest firmware (note that update window may pop up sequentially) +* Enable developer mode of your gateway: 1. Select your Gateway in the MiHome app 2. Go to the "..." menu on the top right corner and click "About" - 3. Tap the version number "Version : 2.XX" at the bottom of the screen repeatedly until you enable developer mode - 4. You should now have 2 extra options listed: `local area network communication protocol` and `gateway information` - 5. Choose `local area network communication protocol` - 6. Tap the toggle switch to enable LAN functions. Note down the developer key (something like: 91bg8zfkf9vd6uw7) + 3. Tap the version number "Plug-in version : 2.XX.X" at the bottom of the screen repeatedly until you enable developer mode + 4. You should now have 2 extra options listed: `wireless communication protocol` and `hub info` + 5. Choose `wireless communication protocol` + 6. Tap the toggle switch to enable WiFi functions. Note down the developer key (aka password), something like: 91bg8zfkf9vd6uw7 7. Make sure you hit the OK button (to the right of the cancel button) to save your changes * In openHAB you should now be able to discover the Xiaomi Gateway diff --git a/_addons_bindings/milight1/readme.md b/_addons_bindings/milight1/readme.md index 1ac1710f43..b27ffdfe4b 100644 --- a/_addons_bindings/milight1/readme.md +++ b/_addons_bindings/milight1/readme.md @@ -83,7 +83,7 @@ The following command is valid for RGBW bulbs only : * `` is valid for RGBW bulbs only and has to be used with `commandType=brightness`. -This optional setting can be used if your RGBW bulbs are not dimming in 27 steps as this is the default [(See the API)](http://www.limitlessled.com/dev/). +This optional setting can be used if your RGBW bulbs are not dimming in 27 steps as this is the default [(See an archive of the API)](https://github.com/Fantasmos/LimitlessLED-DevAPI). ## Limitations diff --git a/_addons_bindings/mpd1/readme.md b/_addons_bindings/mpd1/readme.md index a9022017fc..37a3a4287a 100644 --- a/_addons_bindings/mpd1/readme.md +++ b/_addons_bindings/mpd1/readme.md @@ -17,7 +17,7 @@ install: manual [Music Player Daemon (MPD)](http://www.musicpd.org/) is a flexible, powerful, server-side application for playing music. Through plugins and libraries it can play a variety of sound files while being controlled by its network protocol. -By help of the openHAB MPD binding, you can e.g. start/stop playing music in specific rooms / on various channels and change volume. +With the openHAB MPD binding you can start/stop playing music in specific rooms / on various channels, change volume, and even see which track is playing. ## Binding Configuration @@ -33,7 +33,7 @@ where `` is a unique name that you give for the player, such as `livi ## Item Configuration -The syntax for the Exec binding configuration string is explained here: +The syntax for the MPD binding configuration string is explained here: ``` mpd="::[,::][,...]" diff --git a/_addons_bindings/robonect/readme.md b/_addons_bindings/robonect/readme.md index 86e16b101e..874c5eeb5f 100644 --- a/_addons_bindings/robonect/readme.md +++ b/_addons_bindings/robonect/readme.md @@ -64,7 +64,7 @@ Thing robonect:mower:automower "Mower" @ "Garden" [ host="192.168.2.1", pollInte | `battery` | Number | Retrieves the current battery status in percent | | `status-duration` | Number | Retrieves the duration of the current status (see `status`) of the mower | | `mowing-hours` | Number | Retrieves the number of hours of mowing operation | -| `mode` | String | Retrieves or sets the mode of the mower. Possible values retrieval values are
  • HOME
  • AUTO
  • MAN
In addition he channel allows to set following values for triggering special actions
  • EOD : triggers the "end of day" mode. The mower will switch in to the HOME mode and stay int this mode for the rest of the day
  • JOB : The mower will start a job according to the job parameters defined with the channels `job-remote-start`, `job-after-mode`, `job-start` and `job-end`
| +| `mode` | String | Retrieves or sets the mode of the mower. Possible values retrieval values are
  • HOME
  • AUTO
  • MANUAL
  • EOD : triggers the "end of day" mode. The mower will switch in to the HOME mode and stay int this mode for the rest of the day. After midnight it will switch back to the mode which was set previously.
| | `status` | Number | Retrieves the current mower status which can be
  • 0 : DETECTING_STATUS
  • 1 : PARKING
  • 2 : MOWING
  • 3 : SEARCH_CHARGING_STATION
  • 4 : CHARGING
  • 5 : SEARCHING
  • 6 : UNKNOWN_6
  • 7 : ERROR_STATUS
  • 16 : OFF
  • 17 : SLEEPING
  • 98 : OFFLINE (Binding cannot connect to mower)
  • 99 : UNKNOWN
| | `start` | Switch | Starts the mower. ON is started (analog to pressing the start button on mower) or OFF (analog to the stop button on mower). | | `job` | Switch | Starts a job. The channels can be configured with the three parameters `remoteStart`, `afterMode` and `duration`. `remoteStart` defines the mowing start point with the corresponding options `REMOTE_1`, `REMOTE_2` and `DEFAULT`. `afterMode` is the mode the mower will be set after the job is done. Allowed values are `AUTO`, `HOME` or `EOD`. `duration` is the job duration in minutes. Please note, if the mower is charging it will wait to start the job until it is fully charged, but the jobs duration is already started.| @@ -106,10 +106,7 @@ Switch mowerStarted "Mower started" { String mowerTimerStatus "Mower timer status" {channel="robonect:mower:automower:timer-status"} DateTime mowerNextTimer "Next timer [%1$td/%1$tm %1$tH:%1$tM]" {channel="robonect:mower:automower:timer-next"} Number mowerWlanSignal "WLAN signal [%d dB ]" {channel="robonect:mower:automower:wlan-signal"} -String mowerJobAfterMode "Mode after job execution" {channel="robonect:mower:automower:job-after-mode"} -String mowerJobRemoteStart "Remote start on job execution" {channel="robonect:mower:automower:job-remote-start"} -String mowerJobStart "Job start time" {channel="robonect:mower:automower:job-start"} -String mowerJobEnd "Job end time" {channel="robonect:mower:automower:job-end"} +Switch mowerOneHourJob "Start mowing for one hour from now" {channel="robonect:mower:automower:job",remoteStart=REMOTE_1,afterMode=AUTO,duration=60} Number mowerErrorCode "Error code" {channel="robonect:mower:automower:error-code"} String mowerErrorMessage "Error message" {channel="robonect:mower:automower:error-message"} DateTime mowerErrorDate "Error date [%1$td/%1$tm %1$tH:%1$tM]" {channel="robonect:mower:automower:error-date"} diff --git a/_addons_bindings/solaredge/readme.md b/_addons_bindings/solaredge/readme.md new file mode 100644 index 0000000000..2da7dc5f82 --- /dev/null +++ b/_addons_bindings/solaredge/readme.md @@ -0,0 +1,135 @@ +--- +id: solaredge +label: SolarEdge +title: SolarEdge - Bindings +type: binding +description: "The SolarEdge binding is used to get live data from from SolarEdge inverters via the central web api. This binding should in general be compatible with all inverter models that upload data to the solaredge portal." +since: 2x +install: auto +--- + + + +{% include base.html %} + +# SolarEdge Binding + +The SolarEdge binding is used to get live data from from SolarEdge inverters via the central web api. This binding should in general be compatible with all inverter models that upload data to the solaredge portal. +Only read access is supported. + +## Supported Things + +This binding provides only one thing type: "generic" which is the inverter itself. As the name suggests it is generic which means it applies to all available inverters. Create one inverter thing per physical inverter installation available in your home(s). Additional stuff like batteries is automatically supported. + +## Discovery + +Auto-Discovery is not supported, as access requires authentication. + +## Thing Configuration + +The following configuration parameters are available for this thing: + +- **tokenOrApiKey** (required) +Either the official API Key for using the public API or when using the inofficial private API: a token which can be retrieved from browser's cookie store when logged into the solaredge website. It is called 'SPRING_SECURITY_REMEMBER_ME_COOKIE' + +- **solarId** (required) +Id of your inverter at SolarEdge (can be found in the URL after successful login: https://monitoring.solaredge.com/solaredge-web/p/site/**<>**/#/dashboard) + +- **usePrivateApi** (optional) +can be set to true to use the private API. Private API has no limit regarding query frequency but is less stable. Private API will only gather live data if a meter is available. The official public API ha a limit of 300 queries per day but should be much more reliable/stable. (default = false) + +- **meterInstalled** (optional) +can be set to true for setups that contain a SolarEdge modbus meter (see here: https://www.solaredge.com/products/pv-monitoring/accessories/css-wattnode-modbus-meter ). A meter allows more detailed live data retrieval. (default = false) + +- **liveDataPollingInterval** (optional) +interval (minutes) in which live data values are retrieved from Solaredge. Setting less than 10 minutes is only allowed when using private API. (default = 10). + +- **"aggregateDataPollingInterval"** (optional) +interval (minutes) in which aggregate data values are retrieved from Solaredge. Setting less than 60 is only allowed when using private API. (default = 60). + +## Channels + +Available channels depend on the specific setup e.g. if a meter and/or a battery is present. Following models/channels are currently available +All numeric channels use the UoM feature (see https://www.eclipse.org/smarthome/blog/2018/02/22/units-of-measurement.html for details). This means you can easily change the desired unit e.g. MWh instead of kWh just in your item definition. + +| Channel Type ID | Item Type | Description | Remark | +|-----------------------------------------------|----------------------|--------------------------------------------------|-------------------------------------------------| +| live#production | Number:Power | Current PV production | general available | +| live#pv_status | String | Current PV status | only available when 'meterInstalled' is set | +| live#consumption | Number:Power | Current power consumption | only available when 'meterInstalled' is set | +| live#load_status | String | Current load status | only available when 'meterInstalled' is set | +| live#battery_charge | Number:Power | Current charge flow | requires battery | +| live#battery_discharge | Number:Power | Current discharge flow | requires battery | +| live#battery_charge_discharge | Number:Power | Current charge/discharge flow (+/-) | requires battery | +| live#battery_level | Number:Dimensionless | Current charge level | requires battery | +| live#battery_status | String | Current battery status | requires battery | +| live#battery_critical | String | true or false | requires battery | +| live#import | Number:Power | Current import from grid | only available when 'meterInstalled' is set | +| live#export | Number:Power | Current export to grid | only available when 'meterInstalled' is set | +| live#grid_status | String | Current grid status | only available when 'meterInstalled' is set | +| aggregate_day#production | Number:Energy | Day Aggregate PV production | general available | +| aggregate_day#consumption | Number:Energy | Day Aggregate power consumption | requires solaredge modbus meter attached | +| aggregate_day#selfConsumptionForConsumption | Number:Energy | Day Aggregate self consumption (incl battery) | requires solaredge modbus meter attached | +| aggregate_day#selfConsumptionCoverage | Number:Dimensionless | Day Coverage of consumption by self production | requires solaredge modbus meter attached | +| aggregate_day#batterySelfConsumption | Number:Energy | Day Aggregate self consumption from battery | requires battery and private API activated | +| aggregate_day#import | Number:Energy | Day Aggregate import from grid | requires solaredge modbus meter attached | +| aggregate_day#export | Number:Energy | Day Aggregate export to grid | requires solaredge modbus meter attached | +| aggregate_week#production | Number:Energy | Week Aggregate PV production | general available | +| aggregate_week#consumption | Number:Energy | Week Aggregate power consumption | requires solaredge modbus meter attached | +| aggregate_week#selfConsumptionForConsumption | Number:Energy | Week Aggregate self consumption (incl battery) | requires solaredge modbus meter attached | +| aggregate_week#selfConsumptionCoverage | Number:Dimensionless | Week Coverage of consumption by self production | requires solaredge modbus meter attached | +| aggregate_week#batterySelfConsumption | Number:Energy | Week Aggregate self consumption from battery | requires battery and private API activated | +| aggregate_week#import | Number:Energy | Week Aggregate import from grid | requires solaredge modbus meter attached | +| aggregate_week#export | Number:Energy | Week Aggregate export to grid | requires solaredge modbus meter attached | +| aggregate_month#production | Number:Energy | Month Aggregate PV production | general available | +| aggregate_month#consumption | Number:Energy | Month Aggregate power consumption | requires solaredge modbus meter attached | +| aggregate_month#selfConsumptionForConsumption | Number:Energy | Month Aggregate self consumption (incl battery) | requires solaredge modbus meter attached | +| aggregate_month#selfConsumptionCoverage | Number:Dimensionless | Month Coverage of consumption by self production | requires solaredge modbus meter attached | +| aggregate_month#batterySelfConsumption | Number:Energy | Month Aggregate self consumption from battery | requires battery and private API activated | +| aggregate_month#import | Number:Energy | Month Aggregate import from grid | requires solaredge modbus meter attached | +| aggregate_month#export | Number:Energy | Month Aggregate export to grid | requires solaredge modbus meter attached | +| aggregate_year#production | Number:Energy | Year Aggregate PV production | general available | +| aggregate_year#consumption | Number:Energy | Year Aggregate power consumption | requires solaredge modbus meter attached | +| aggregate_year#selfConsumptionForConsumption | Number:Energy | Year Aggregate self consumption (incl battery) | requires solaredge modbus meter attached | +| aggregate_year#selfConsumptionCoverage | Number:Dimensionless | Year Coverage of consumption by self production | requires solaredge modbus meter attached | +| aggregate_year#batterySelfConsumption | Number:Energy | Year Aggregate self consumption from battery | requires battery and private API activated | +| aggregate_year#import | Number:Energy | Year Aggregate import from grid | requires solaredge modbus meter attached | +| aggregate_year#export | Number:Energy | Year Aggregate export to grid | requires solaredge modbus meter attached | + + +## Full Example + +### Thing + +- minimum configuration + +``` +solaredge:generic:se2200 [ tokenOrApiKey="...", solarId="..."] +``` + +- with pollingIntervals + +``` +solaredge:generic:se2200[ tokenOrApiKey="...", solarId="...", liveDataPollingInterval=..., aggregateDataPollingInterval=... ] +``` + +- maximum version + +``` +solaredge:generic:se2200 [ tokenOrApiKey="secret", solarId="4711", meterInstalled=true, usePrivateApi=true, liveDataPollingInterval=15, aggregateDataPollingInterval=60 ] +``` + +- multiple inverters + +``` +solaredge:generic:home1 [ tokenOrApiKey="...", solarId="..."] +solaredge:generic:home2 [ tokenOrApiKey="...", solarId="..."] +``` + +### Items + +``` +Number:Power SE2200_Live_Production "PV Produktion [%.2f %unit%]" {channel="solaredge:generic:se2200:live#production"} +Number:Dimensionless SE2200_Live_Level "Batterieladung" {channel="solaredge:generic:se2200:live#battery_level"} +Number:Energy SE2200_Day_Production "PV Produktion [%.2f kWh]" {channel="solaredge:generic:se2200:aggregate_day#production"} +``` diff --git a/_addons_bindings/squeezebox/readme.md b/_addons_bindings/squeezebox/readme.md index a69f210dd1..af89916fa8 100644 --- a/_addons_bindings/squeezebox/readme.md +++ b/_addons_bindings/squeezebox/readme.md @@ -106,6 +106,7 @@ All devices support some of the following channels: | sync | String | Add another player to your device for synchronized playback (other player mac address) | | playListIndex | Number | Playlist Index | | currentPlayingTime | Number | Current Playing Time | +| duration | Number | Duration of currently playing track (in seconds) | | currentPlaylistShuffle | Number | Current playlist shuffle mode (0 No Shuffle, 1 Shuffle Songs, 2 Shuffle Albums) | | currentPlaylistRepeat | Number | Current playlist repeat Mode (0 No Repeat, 1 Repeat Song, 2 Repeat Playlist) | | title | String | Title of the current song | @@ -157,7 +158,11 @@ Selecting a favorite from the list will play it. #### For Sitemap -- Currently, the Selection widget in Basic UI doesn’t use the state options. +- To use state options on the playFavorite channel, simply omit the *mappings* from the Selection widget. + +``` +Selection item=YourPlayer_PlayFavorite label="Play Favorite" +``` ## Notifications @@ -178,7 +183,7 @@ when Item GarageDoorOpenNotification received command ON then // Play the notification on the default sink at a specified volume level - say("The garage door is open!", "voicerss:enUS", 35) + say("The garage door is open!", "voicerss:enUS", new PercentType(35)) // Play the notification on a specific sink say("The garage door is open!", "voicerss:enUS", "squeezebox:squeezeboxplayer:5919BEA2-764B-4590-BC70-D74DCC15491B:20cfbf221510") end @@ -194,7 +199,7 @@ then // Play the sound on the default sink playSound("doorbell.mp3") // Play the sound on a specific sink at a specified volume level - playSound("squeezebox:squeezeboxplayer:5919BEA2-764B-4590-BC70-D74DCC15491B:20cfbf221510", "doorbell.mp3", 45) + playSound("squeezebox:squeezeboxplayer:5919BEA2-764B-4590-BC70-D74DCC15491B:20cfbf221510", "doorbell.mp3", new PercentType(45)) end ``` diff --git a/_addons_bindings/systeminfo1/readme.md b/_addons_bindings/systeminfo1/readme.md index 37c7465f55..f5860f7624 100644 --- a/_addons_bindings/systeminfo1/readme.md +++ b/_addons_bindings/systeminfo1/readme.md @@ -309,8 +309,16 @@ Number System_Temperature_GPU "Temperature GPU [%.1f °C]" (System Add to `rrd4j.persist` file: -``` -System_Temperature_Chart* : strategy = everyChange, everyMinute, restoreOnStartup +```java +Strategies { + // for rrd charts, we need a cron strategy + everyMinute : "0 * * * * ?" +} + +Items { + // persist items on every change and every minute + System_Temperature_Chart* : strategy = everyChange, everyMinute, restoreOnStartup +} ``` Add to `sitemaps/default.sitemap` file: diff --git a/_addons_bindings/zigbee/readme.md b/_addons_bindings/zigbee/readme.md index defcc5b291..7ea016485c 100644 --- a/_addons_bindings/zigbee/readme.md +++ b/_addons_bindings/zigbee/readme.md @@ -23,19 +23,19 @@ The ZigBee binding supports an interface to a wireless ZigBee home automation ne A ZigBee Coordinator is the network controller, and is therefore the heart of the ZigBee network. It also acts as the trust centre to control security access to the network. -Coordinators need to be installed manually and the serial port must be set. +Coordinators need to be installed manually and the serial port and baud rate must be set. These are set to match the configuration that the dongle is in. Should you wish to use a different baud rate than the default speed of the device, you must change the configuration of the dongle using some other, and then configure the binding to match your change. If in doubt, you should leave the settings at their default values which should work in most cases. -#### Examples for coordinators +The following coordinators are known to be supported. | Name and Link | Coordinator | Comment | |----------------------------|-------------|-------------------------------| -|[Texas Instruments CC2531EMK](http://www.ti.com/tool/cc2531emk)|[TI2531](#ti2531-coordinator)|Needs extra hardware and correct firmware (might be hard to find) for flashing.
There are also cheap copies of the CC2531 Stick available on eBay, Aliexpress, etc. like [this](https://de.aliexpress.com/item/Drahtlose-Zigbee-CC2531-Sniffer-software-protokoll-analyse-Bareboard-Paket-Protokoll-Analyzer-Modul-Usb-schnittstelle-Dongle-Erfassen/32852226435.html) and a module to flash the firmware like [this](https://de.aliexpress.com/item/SmartRF04EB-CC1110-CC2530-ZigBee-Module-USB-Downloader-Emulator-MCU-M100/32673666126.html)
Also CC2530, CC2538 or CC2650 might work with the correct firmware but are not suggested| -|[Bitron Video ZigBee USB Funkstick](http://www.bitronvideo.eu/index.php/produkte/smart-home-produkte/zb-funkstick/)|[Ember](#ember-ezsp-ncp-coordinator)|-| -|[Cortet EM358 USB Stick](https://www.cortet.com/iot-hardware/cortet-usb-sticks/em358-usb-stick)|[Ember](#ember-ezsp-ncp-coordinator)|-| -|[Nortek Security & Control HUSBZB-1](https://nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/)|[Ember](#ember-ezsp-ncp-coordinator)|Stick contains both Z-Wave and Zigbee| -|[Telegesis ETRX357USB zigbee® USB Stick](https://www.silabs.com/products/wireless/mesh-networking/telegesis-modules-gateways/etrx3-zigbee-usb-sticks)|[Telegesis](#telegesis-etrx3)|-| +|[Texas Instruments CC2531EMK](http://www.ti.com/tool/cc2531emk)|[TI2531](#ti2531-coordinator)|Needs extra hardware and correct firmware (might be hard to find) for flashing.
There are also cheap copies of the CC2531 Stick available on eBay, Aliexpress, etc. like [this](https://de.aliexpress.com/item/Drahtlose-Zigbee-CC2531-Sniffer-software-protokoll-analyse-Bareboard-Paket-Protokoll-Analyzer-Modul-Usb-schnittstelle-Dongle-Erfassen/32852226435.html) and a module to flash the firmware like [this](https://de.aliexpress.com/item/SmartRF04EB-CC1110-CC2530-ZigBee-Module-USB-Downloader-Emulator-MCU-M100/32673666126.html)
Also CC2530, CC2538 or CC2650 may work with the correct firmware but are not suggested| +|[Bitron Video ZigBee USB Funkstick](http://www.bitronvideo.eu/index.php/produkte/smart-home-produkte/zb-funkstick/)|[Ember](#ember-ezsp-ncp-coordinator)| | +|[Cortet EM358 USB Stick](https://www.cortet.com/iot-hardware/cortet-usb-sticks/em358-usb-stick)|[Ember](#ember-ezsp-ncp-coordinator)| Use baud rate 57600 and software flow control. | +|[Nortek Security & Control HUSBZB-1](https://nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/)|[Ember](#ember-ezsp-ncp-coordinator)|Stick contains both Z-Wave and ZigBee. Use baud rate 57600 and software flow control. | +|[Telegesis ETRX357USB ZigBee® USB Stick](https://www.silabs.com/products/wireless/mesh-networking/telegesis-modules-gateways/etrx3-zigbee-usb-sticks)|[Telegesis](#telegesis-etrx3)| | |[QIVICON ZigBee-Funkstick](https://www.qivicon.com/de/produkte/produktinformationen/zigbee-funkstick/)|[Telegesis](#telegesis-etrx3)|Only working on Linux devices| -|[Digi XStick](https://www.digi.com/products/xbee-rf-solutions/boxed-rf-modems-adapters/xstick)|[XBee](#xbee-xu-z11-coordinator)|-| +|[Digi XStick](https://www.digi.com/products/xbee-rf-solutions/boxed-rf-modems-adapters/xstick)|[XBee](#xbee-xu-z11-coordinator)| | #### TI2531 Coordinator @@ -61,6 +61,8 @@ The firmware can be flashed with `./cc-tool -e -w CC2531ZNP-Pro-Secure_Standard. The Ember EZSP NCP (Network Co-Processor) supports the Silabs EM358 or MightyGecko dongles with the standard NCP firmware. The thing type is ```coordinator_ember```. +Note that there are generally two versions of the Ember NCP firmware in use. One operates at a baud rate of 115200 with RTS/CTS flow control (i.e. hardware flow control), the other operates at a baud rate of 57600, and XON/XOFF flow control (i.e. software flow control). If you are programming your own stick (e.g. the CEL stick) then it should be advisable to use the hardware flow control version - many commercial sticks seem to use the lower speed and software flow control (e.g. Bitron and Nortek HUSBZB-1). + #### Telegesis ETRX3 The thing type is ```coordinator_telegesis```. @@ -101,7 +103,7 @@ Once the binding is installed, and an adapter is added, it automatically reads a The binding will store the list of devices that have joined the network locally between restarts to allow them to be found again later. A ZigBee coordinator does not store a list of known devices, so rediscovery of devices following a restart may not be seemless if the dongle is moved to another system. -When a ZigBee device restarts (eg a bulb is powered on), it will send an announcement to advise the coordinator that it is on the network and this will allow the binding to rediscover devices that have become lost. Battery devices often have a button that may also perform this function. +When a ZigBee device restarts (e.g. a bulb is powered on), it will send an announcement to advise the coordinator that it is on the network and this will allow the binding to rediscover devices that have become lost. Battery devices often have a button that may also perform this function. ## Leave @@ -123,18 +125,26 @@ The following channels are supported -: | Channel UID | ZigBee Cluster | Type |Description | |-------------|----------------|----------|-----------------------------| -| switch_dimmer | ```LEVEL_CONTROL``` (0x0008) | Dimmer | | -| switch_onoff | ```ON_OFF``` (0x0006) | Switch | +| battery-level | ```POWER_CONFIGURATION``` (0x0001) | Number | | +| battery_voltage | ```POWER_CONFIGURATION``` (0x0001) | Number | | | color_color | ```COLOR_CONTROL``` (0x0300) | Color | | | color_temperature | ```COLOR_CONTROL``` (0x0300) | Dimmer | | | electrical_activepower | ```ELECTRICAL_MEASUREMENT``` (0x0B04) | Number | | +| electrical_rmscurrent | ```ELECTRICAL_MEASUREMENT``` (0x0B04) | Number | | +| electrical_rmsvoltage | ```ELECTRICAL_MEASUREMENT``` (0x0B04) | Number | | +| ias_codetector | ```IAS_ZONE``` (0x0500) | Switch | | | ias_contactportal1 | ```IAS_ZONE``` (0x0500) | Switch | | +| ias_fire | ```IAS_ZONE``` (0x0500) | Switch | | | ias_motionintrusion | ```IAS_ZONE``` (0x0500) | Switch | | | ias_motionpresence | ```IAS_ZONE``` (0x0500) | Switch | | | ias_standard_system | ```IAS_ZONE``` (0x0500) | Switch | | | measurement_illuminance | ```ILLUMINANCE_MEASUREMENT``` (0x0400) | Number | | -| measurement_temperature | ```TEMPERATURE_MEASUREMENT``` (0x0402) | Number | | -| sensor_occupancy | ```OCCUPANCY_SENSING``` (0x0406) | Switch | | +| measurement_pressure | ```PRESSURE_MEASUREMENT``` (0x0403) | Number | | +| measurement_relativehumidity | ```RELATIVE_HUMIDITY_MEASUREMENT``` (0x0405) | Number | | +| measurement_temperature | ```TEMPERATURE_MEASUREMENT``` (0x0402) | Number:Temperature | | +| sensor_occupancy | ```OCCUPANCY_SENSING``` (0x0406) | Switch | | +| switch_dimmer | ```LEVEL_CONTROL``` (0x0008) | Dimmer | | +| switch_onoff | ```ON_OFF``` (0x0006) | Switch | ### Updates @@ -153,4 +163,4 @@ log:set debug com.zsmartsystems.zigbee This will log data into the standard openhab.log file. -Note that logs can only show what is happening at a high level - it can't show all data exchanges between the device and the coordinator - just what the coordinator sends to the binding. For this reason it can be difficult to debug issues where devices are not joining the network. +Note that logs can only show what is happening at a high level - it can't show all data exchanges between the device and the coordinator - just what the coordinator sends to the binding. For this reason it can be difficult to debug issues where devices are not joining the network, or other low level issues need resolving. In such cases a network sniffer log is required, which requires additional hardware and software. diff --git a/_addons_bindings/zwave/doc/act/zir010_0_0.md b/_addons_bindings/zwave/doc/act/zir010_0_0.md index 38c76dc24b..0cc1e8f11f 100644 --- a/_addons_bindings/zwave/doc/act/zir010_0_0.md +++ b/_addons_bindings/zwave/doc/act/zir010_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *ZIR010*, manufactured by *ACT - Advanced Contr The ZIR010 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZIR010 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZIR010 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/189) to improve the documentation. +### Wakeup Information +The ZIR010 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZIR010 -: diff --git a/_addons_bindings/zwave/doc/aeon/dsa03202_0_0.md b/_addons_bindings/zwave/doc/aeon/dsa03202_0_0.md index f482de7f84..f54b6bf9ab 100644 --- a/_addons_bindings/zwave/doc/aeon/dsa03202_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/dsa03202_0_0.md @@ -8,12 +8,15 @@ title: DSA03202 - ZWave # DSA03202 Minimote 4 button remote control This describes the Z-Wave device *DSA03202*, manufactured by *[AEON Labs](http://aeotec.com/)* with the thing type UID of ```aeon_dsa03202_00_000```. -The DSA03202 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DSA03202 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/74) to improve the documentation. +### Wakeup Information +The DSA03202 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DSA03202 -: diff --git a/_addons_bindings/zwave/doc/aeon/dsa38_0_0.md b/_addons_bindings/zwave/doc/aeon/dsa38_0_0.md index 501d485bf4..2a84f64f9a 100644 --- a/_addons_bindings/zwave/doc/aeon/dsa38_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/dsa38_0_0.md @@ -11,12 +11,15 @@ This describes the Z-Wave device *DSA38*, manufactured by *[AEON Labs](http://ae ![DSA38 product image](https://www.cd-jackson.com/zwave_device_uploads/88/88_default.jpg) -The DSA38 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DSA38 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/88) to improve the documentation. +### Wakeup Information +The DSA38 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DSA38 -: diff --git a/_addons_bindings/zwave/doc/aeon/dsb29_0_0.md b/_addons_bindings/zwave/doc/aeon/dsb29_0_0.md index 4968bd0513..4911f2bea2 100644 --- a/_addons_bindings/zwave/doc/aeon/dsb29_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/dsb29_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *DSB29*, manufactured by *[AEON Labs](http://ae The DSB29 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DSB29 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DSB29 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/70) to improve the documentation. +### Wakeup Information +The DSB29 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DSB29 -: diff --git a/_addons_bindings/zwave/doc/aeon/dsb45_0_0.md b/_addons_bindings/zwave/doc/aeon/dsb45_0_0.md index 39b4278ec0..3c074eb30a 100644 --- a/_addons_bindings/zwave/doc/aeon/dsb45_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/dsb45_0_0.md @@ -13,12 +13,16 @@ This describes the Z-Wave device *DSB45*, manufactured by *[AEON Labs](http://ae The DSB45 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DSB45 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DSB45 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview ### Wakeup Information +The DSB45 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + To wake up the sensor, _don't_ push the wake up button, as it does nothing. Instead, tap the zwave button once. Use wake up button to put back to sleep immediately. Press WakeUp button or hold z-wave button diff --git a/_addons_bindings/zwave/doc/aeon/dsb54_0_0.md b/_addons_bindings/zwave/doc/aeon/dsb54_0_0.md index 37420c424f..8c76499ecd 100644 --- a/_addons_bindings/zwave/doc/aeon/dsb54_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/dsb54_0_0.md @@ -12,12 +12,15 @@ The device is in the category of *Door*, defining Door sensors. The DSB54 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DSB54 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DSB54 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/68) to improve the documentation. +### Wakeup Information +The DSB54 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DSB54 -: diff --git a/_addons_bindings/zwave/doc/aeon/dsc25_0_0.md b/_addons_bindings/zwave/doc/aeon/dsc25_0_0.md index 68718b18a2..8d66123b0e 100644 --- a/_addons_bindings/zwave/doc/aeon/dsc25_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/dsc25_0_0.md @@ -8,12 +8,15 @@ title: DSC25 - ZWave # DSC25 Smart Energy Illuminator G2 This describes the Z-Wave device *DSC25*, manufactured by *[AEON Labs](http://aeotec.com/)* with the thing type UID of ```aeon_dsc25_00_000```. -The DSC25 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DSC25 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/276) to improve the documentation. +### Wakeup Information +The DSC25 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DSC25 -: diff --git a/_addons_bindings/zwave/doc/aeon/dsc26_0_0.md b/_addons_bindings/zwave/doc/aeon/dsc26_0_0.md index 5a25a87991..e1f97c608d 100644 --- a/_addons_bindings/zwave/doc/aeon/dsc26_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/dsc26_0_0.md @@ -10,11 +10,26 @@ This describes the Z-Wave device *DSC26*, manufactured by *[AEON Labs](http://ae The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. +![DSC26 product image](https://www.cd-jackson.com/zwave_device_uploads/82/82_default.jpg) + + The DSC26 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/82) to improve the documentation. +Relay based unit designed to be included inside a junction box to switch a load. Supports external switch. + +### Inclusion Information + +Push case button. + +External switch (if attached) can be toggled 10X quickly to include/exclude. + +### Exclusion Information + +Push case button. + +External switch (if attached) can be toggled 10X quickly to include/exclude. ## Channels @@ -34,58 +49,77 @@ The ```switch_binary``` channel supports the ```Switch``` item and is in the ``` ## Device Configuration -The following table provides a summary of the 13 configuration parameters available in the DSC26. +The following table provides a summary of the 15 configuration parameters available in the DSC26. Detailed information on each parameter can be found in the sections below. | Param | Name | Description | |-------|-------|-------------| -| 2 | Make Micro Switch 2nd Edition Blink | This is a double byte value. The LSB defines the total time the device need to blink. The value if set in seconds. The MSB defines the on/off interval of the blinking. The unit is 0.1 s. | -| 80 | Notification on Status Change | Parameter to Enable to send notification to associated devices (Group 1) when the state of Micro Switch's load changed | -| 101 | Which reports need to send automatically in timing intervals for group 1 | The value is a combination number made up of the sum of the values for the individual parameters. The parameters have the values: KWH=8, Wattage=4, Current=2, Voltage=1. | -| 102 | Which reports need to send automatically in timing intervals for group 2 | The value is a combination number made up of the sum of the values for the individual parameters. The parameters have the values: KWH=8, Wattage=4, Current=2, Voltage=1. | -| 103 | Which reports need to send automatically in timing intervals for group 3 | The value is a combination number made up of the sum of the values for the individual parameters. The parameters have the values: KWH=8, Wattage=4, Current=2, Voltage=1. | -| 111 | Interval to send out reports of group 1 | | -| 112 | Interval to send out reports of group 2 | | -| 113 | Interval to send out reports of group 3 | | -| 120 | Turn External Button Mode | Parameter to set External button type | +| 2 | LED blink repeat | Number of times LED should blink | +| 2 | LED duty time | length of time LED will blink on/off per cycle | +| 80 | Notification on Status Change | Notification on Status Change | +| 101 | Group 1 report values to send | Group 1 report values to send | +| 102 | Group 2 report variables to send | Group 2 report variables to send | +| 103 | Group 3 report variables to send | Group 3 report variables to send | +| 111 | Interval to send out reports to group 1 | Interval to send out reports to group 1 | +| 112 | Interval to send out reports to group 2 | Interval to send out reports to group 2 | +| 113 | Interval to send out reports to group 3 | Interval to send out reports to group 3 | +| 120 | External Button Type | | | 200 | Partner ID | | +| 250 | CHECK AND DELETE ME formerly parameter 2 | CHECK AND DELETE ME formerly parameter 2 | | 252 | Enable/disable Lock Configuration | | | 254 | Device Tag | | | 255 | Reset configuration set up to default setting | | | | Switch All Mode | Set the mode for the switch when receiving SWITCH ALL commands | -### Parameter 2: Make Micro Switch 2nd Edition Blink +### Parameter 2: LED blink repeat -This is a double byte value. The LSB defines the total time the device need to blink. The value if set in seconds. The MSB defines the on/off interval of the blinking. The unit is 0.1 s. +Number of times LED should blink +Number of ON-OFF cycles the LED should complete once set. +Values in the range 0 to 255 may be set. + +The manufacturer defined default value is ```0```. + +This parameter has the configuration ID ```config_2_2_000000FF``` and is of type ```INTEGER```. -Values in the range 0 to 65535 may be set. + +### Parameter 2: LED duty time + +length of time LED will blink on/off per cycle +LED will turn on and off for this many tenths of a second once set. +Values in the range 0 to 255 may be set. The manufacturer defined default value is ```0```. -This parameter has the configuration ID ```config_2_2``` and is of type ```INTEGER```. +This parameter has the configuration ID ```config_2_2_0000FF00``` and is of type ```INTEGER```. ### Parameter 80: Notification on Status Change -Parameter to Enable to send notification to associated devices (Group 1) when the state of Micro Switch's load changed - +Notification on Status Change +Send notification to associated devices in Group 1 when device state changed locally. The following option values may be configured -: | Value | Description | |--------|-------------| -| 0 | Deactivate | +| 0 | Do nothing | | 1 | Hail CC Sent | | 2 | Basic CC Report Sent | -The manufacturer defined default value is ```0``` (Deactivate). +The manufacturer defined default value is ```0``` (Do nothing). This parameter has the configuration ID ```config_80_1``` and is of type ```INTEGER```. -### Parameter 101: Which reports need to send automatically in timing intervals for group 1 +### Parameter 101: Group 1 report values to send -The value is a combination number made up of the sum of the values for the individual parameters. The parameters have the values: KWH=8, Wattage=4, Current=2, Voltage=1. +Group 1 report values to send +Value is the sum of the individual parameters: + +KWH=8 +Wattage=4 +Current=2 +Voltage=1 Values in the range 0 to 65535 may be set. The manufacturer defined default value is ```4```. @@ -93,10 +127,16 @@ The manufacturer defined default value is ```4```. This parameter has the configuration ID ```config_101_4``` and is of type ```INTEGER```. -### Parameter 102: Which reports need to send automatically in timing intervals for group 2 +### Parameter 102: Group 2 report variables to send -The value is a combination number made up of the sum of the values for the individual parameters. The parameters have the values: KWH=8, Wattage=4, Current=2, Voltage=1. +Group 2 report variables to send +Value is the sum of the individual parameters: + +KWH=8 +Wattage=4 +Current=2 +Voltage=1 Values in the range 0 to 65535 may be set. The manufacturer defined default value is ```8```. @@ -104,10 +144,16 @@ The manufacturer defined default value is ```8```. This parameter has the configuration ID ```config_102_4``` and is of type ```INTEGER```. -### Parameter 103: Which reports need to send automatically in timing intervals for group 3 +### Parameter 103: Group 3 report variables to send -The value is a combination number made up of the sum of the values for the individual parameters. The parameters have the values: KWH=8, Wattage=4, Current=2, Voltage=1. +Group 3 report variables to send +Value is the sum of the individual parameters: + +KWH=8 +Wattage=4 +Current=2 +Voltage=1 Values in the range 0 to 65535 may be set. The manufacturer defined default value is ```0```. @@ -115,9 +161,9 @@ The manufacturer defined default value is ```0```. This parameter has the configuration ID ```config_103_4``` and is of type ```INTEGER```. -### Parameter 111: Interval to send out reports of group 1 - +### Parameter 111: Interval to send out reports to group 1 +Interval to send out reports to group 1 Values in the range 1 to 2678400 may be set. @@ -126,9 +172,9 @@ The manufacturer defined default value is ```3```. This parameter has the configuration ID ```config_111_4``` and is of type ```INTEGER```. -### Parameter 112: Interval to send out reports of group 2 - +### Parameter 112: Interval to send out reports to group 2 +Interval to send out reports to group 2 Values in the range 1 to 2678400 may be set. @@ -137,9 +183,9 @@ The manufacturer defined default value is ```600```. This parameter has the configuration ID ```config_112_4``` and is of type ```INTEGER```. -### Parameter 113: Interval to send out reports of group 3 - +### Parameter 113: Interval to send out reports to group 3 +Interval to send out reports to group 3 Values in the range 1 to 2678400 may be set. @@ -148,17 +194,17 @@ The manufacturer defined default value is ```600```. This parameter has the configuration ID ```config_113_4``` and is of type ```INTEGER```. -### Parameter 120: Turn External Button Mode +### Parameter 120: External Button Type + -Parameter to set External button type The following option values may be configured -: | Value | Description | |--------|-------------| -| 0 | Momentary Button Mode | -| 1 | 2 State Switch Mode | -| 2 | 3 Way Switch Mode | +| 0 | Momentary Button | +| 1 | 2 State Switch | +| 2 | 3 Way Switch | The manufacturer defined default value is ```255```. @@ -174,13 +220,34 @@ The following option values may be configured -: | Value | Description | |--------|-------------| | 0 | Aeon Labs Standard Product | -| 1 | AT&T | +| 1 | ATandT | The manufacturer defined default value is ```0``` (Aeon Labs Standard Product). This parameter has the configuration ID ```config_200_1``` and is of type ```INTEGER```. +### Parameter 250: CHECK AND DELETE ME formerly parameter 2 + +CHECK AND DELETE ME formerly parameter 2 +This is a double byte value. The LSB defines the total time the device need to blink. The value if set in seconds. The MSB defines the on/off interval of the blinking. The unit is 0.1 s. + +CHECK ME! + +CHECK ME! + +CHECK ME! + +CHECK ME! + +(did I do this right for parameter 2?) +Values in the range 0 to 65535 may be set. + +The manufacturer defined default value is ```0```. + +This parameter has the configuration ID ```config_250_2``` and is of type ```INTEGER```. + + ### Parameter 252: Enable/disable Lock Configuration @@ -189,10 +256,10 @@ The following option values may be configured -: | Value | Description | |--------|-------------| -| 0 | Disable | -| 1 | Enable | +| 0 | Configuration unlocked | +| 1 | Configuration locked | -The manufacturer defined default value is ```0``` (Disable). +The manufacturer defined default value is ```0``` (Configuration unlocked). This parameter has the configuration ID ```config_252_1``` and is of type ```INTEGER```. @@ -273,6 +340,7 @@ This group supports 5 nodes. ### Documentation Links * [Micro Switch G2 manual](https://www.cd-jackson.com/zwave_device_uploads/82/10-Micro-Switch-G2.pdf) +* [User manual](https://www.cd-jackson.com/zwave_device_uploads/82/aeon-labs-dsc26-MicroSwitch.pdf) --- diff --git a/_addons_bindings/zwave/doc/aeon/zw074_0_0.md b/_addons_bindings/zwave/doc/aeon/zw074_0_0.md index 447acdc2ce..88b47927db 100644 --- a/_addons_bindings/zwave/doc/aeon/zw074_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/zw074_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *ZW074*, manufactured by *[AEON Labs](http://ae The ZW074 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZW074 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZW074 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/72) to improve the documentation. +### Wakeup Information +The ZW074 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZW074 -: diff --git a/_addons_bindings/zwave/doc/aeon/zw088_1_0.md b/_addons_bindings/zwave/doc/aeon/zw088_1_0.md index 1579aa3468..22365f1c93 100644 --- a/_addons_bindings/zwave/doc/aeon/zw088_1_0.md +++ b/_addons_bindings/zwave/doc/aeon/zw088_1_0.md @@ -9,7 +9,7 @@ title: ZW088 - ZWave This describes the Z-Wave device *ZW088*, manufactured by *[AEON Labs](http://aeotec.com/)* with the thing type UID of ```aeon_zw088_01_000```. This version of the device is limited to firmware versions above 1.0 -The ZW088 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZW088 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -19,6 +19,11 @@ Key Fob Gen5 is a fully functional Z-wave remote controller, which can include, Short press the “Include” button on the Key Fob, it will go into inclusion state and its blue LED will blink slowly to wait including other slave Z-Wave devices. +### Wakeup Information + +The ZW088 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZW088 -: diff --git a/_addons_bindings/zwave/doc/aeon/zw089_0_0.md b/_addons_bindings/zwave/doc/aeon/zw089_0_0.md index ff262ab82c..97d5541c4c 100644 --- a/_addons_bindings/zwave/doc/aeon/zw089_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/zw089_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Door*, defining Door sensors. The ZW089 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZW089 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZW089 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -37,6 +37,10 @@ Aeon Labs Recessed Door Sensor Gen5 is a door detector that can detect the state ### Wakeup Information +The ZW089 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Press and hold the Z‐wave Button for 6 seconds. It will sleep after you released the z‐wave button for 10 seconds, or sleep right away when received the Wake Up No More Information and then the led will turn off. ## Channels diff --git a/_addons_bindings/zwave/doc/aeon/zw090_0_0.md b/_addons_bindings/zwave/doc/aeon/zw090_0_0.md index e22eaa32e9..aa62013d0b 100644 --- a/_addons_bindings/zwave/doc/aeon/zw090_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/zw090_0_0.md @@ -36,10 +36,6 @@ the network.) 3\. The orange LED will then return to blinking fast, indicating readiness for further device exclusions. Repeat step 1 for each device as you wish to exclude -### Wakeup Information - -N/A - ## Channels The following table summarises the channels available for the ZW090 -: diff --git a/_addons_bindings/zwave/doc/aeon/zw096_0_0.md b/_addons_bindings/zwave/doc/aeon/zw096_0_0.md index 09fa71dcbf..53544bab95 100644 --- a/_addons_bindings/zwave/doc/aeon/zw096_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/zw096_0_0.md @@ -55,10 +55,6 @@ Remove Smart Switch from a z-wave network: 3. Press the Action button. 4. If the remove is successful, Smart Switch LED will blink slowly. If Smart Switch LED still be solid, please repeat the process from step 2. -### Wakeup Information - -mains device - ## Channels The following table summarises the channels available for the ZW096 -: diff --git a/_addons_bindings/zwave/doc/aeon/zw097_0_0.md b/_addons_bindings/zwave/doc/aeon/zw097_0_0.md index dad1e8f093..19c9b9b0ab 100644 --- a/_addons_bindings/zwave/doc/aeon/zw097_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/zw097_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *ZW097*, manufactured by *[AEON Labs](http://ae The ZW097 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZW097 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZW097 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/267) to improve the documentation. +### Wakeup Information +The ZW097 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZW097 -: diff --git a/_addons_bindings/zwave/doc/aeon/zw100_1_10.md b/_addons_bindings/zwave/doc/aeon/zw100_1_10.md index 158a743720..b6658e7840 100644 --- a/_addons_bindings/zwave/doc/aeon/zw100_1_10.md +++ b/_addons_bindings/zwave/doc/aeon/zw100_1_10.md @@ -71,14 +71,6 @@ press the Action Button. 4\. If the exclusion is success, MultiSensor’s LED will blink slowly when you short press the Action Button. If MultiSensor’s LED still keeps on status, in which you need to repeat the process from step 2. -### Wakeup Information - -Press and hold for 3 seconds -============================ - -Enable/disable wake up for 10 minutes. -(When it is enabled, the orange Led will fast blink) - ## Channels The following table summarises the channels available for the ZW100 -: diff --git a/_addons_bindings/zwave/doc/aeon/zw100_1_8.md b/_addons_bindings/zwave/doc/aeon/zw100_1_8.md index 0f45c3a9ab..514df22029 100644 --- a/_addons_bindings/zwave/doc/aeon/zw100_1_8.md +++ b/_addons_bindings/zwave/doc/aeon/zw100_1_8.md @@ -71,14 +71,6 @@ press the Action Button. 4\. If the exclusion is success, MultiSensor’s LED will blink slowly when you short press the Action Button. If MultiSensor’s LED still keeps on status, in which you need to repeat the process from step 2. -### Wakeup Information - -Press and hold for 3 seconds -============================ - -Enable/disable wake up for 10 minutes. -(When it is enabled, the orange Led will fast blink) - ## Channels The following table summarises the channels available for the ZW100 -: diff --git a/_addons_bindings/zwave/doc/aeon/zw112_0_0.md b/_addons_bindings/zwave/doc/aeon/zw112_0_0.md index 484d55c911..d9872fb3a8 100644 --- a/_addons_bindings/zwave/doc/aeon/zw112_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/zw112_0_0.md @@ -8,17 +8,19 @@ title: ZW112 - ZWave # ZW112 Door/Window Sensor 6 This describes the Z-Wave device *ZW112*, manufactured by *[AEON Labs](http://aeotec.com/)* with the thing type UID of ```aeon_zw112_00_000```. +The device is in the category of *Door*, defining Door sensors. + ![ZW112 product image](https://www.cd-jackson.com/zwave_device_uploads/274/274_default.jpg) The ZW112 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZW112 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZW112 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview Aeon Labs Door/ Window Sensor 6 is a smart Z-Wave sensor that can detect the status of door/window's open/close in real time. -It’s a security Z-Wave device that supports security encryption. Also it supports the “Over the Air Firmware Updating” that allows you wirelessly update its firmware if needs. +It’s a security Z-Wave device that supports security encryption. Also it supports the “Over the Air Firmware Updating” that allows you wirelessly update its firmware if needs. It can be included and operated in any Z-Wave network with other Z-Wave certified devices from manufacturers and/or other applications. ### Inclusion Information @@ -31,6 +33,10 @@ Turn the primary controller into exclusion mode, short press the product’s Act ### Wakeup Information +The ZW112 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Press the Action Button once, which will trigger sending out the Wake up notification command, press and hold the Action Button for 3 seconds, which will toggle on/off the Sensor be waked up for 10 minutes. ## Channels diff --git a/_addons_bindings/zwave/doc/aeon/zw116_0_0.md b/_addons_bindings/zwave/doc/aeon/zw116_0_0.md index 0a21937032..ba641e1451 100644 --- a/_addons_bindings/zwave/doc/aeon/zw116_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/zw116_0_0.md @@ -8,6 +8,8 @@ title: ZW116 - ZWave # ZW116 Aeotec Nano Switch This describes the Z-Wave device *ZW116*, manufactured by *[AEON Labs](http://aeotec.com/)* with the thing type UID of ```aeon_zw116_00_000```. +The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. + ![ZW116 product image](https://www.cd-jackson.com/zwave_device_uploads/591/591_default.jpg) @@ -15,10 +17,25 @@ The ZW116 supports routing. This allows the device to communicate using other ro ## Overview -Aeotec Nano Switch is a Z-Wave Smart Switch specifically used to enable Z-Wave command and control (on/off) of any wall switches. It can report immediate wattage consumption or kWh energy usage over a period of time. In the event of power failure, non-volatile memory retains all programmed information relating to the unit’s operating status. +Aeotec Nano Switch is a Z-Wave Smart Switch specifically used to enable Z-Wave command and control (on/off) of any wall switches. It can report immediate wattage consumption or kWh energy usage over a period of time. In the event of power failure, non-volatile memory retains all programmed information relating to the unit’s operating status. + It can connect to 2 external manual switches to control the load ON/OFF independently. Its surface has a pin socket, which can be used for connecting to the touch panel, so you can also use the touch panel to control the Dual Nano Switch. The Nano Switch is also a security Z-Wave device and supports Over The Air (OTA) feature for the products firmware upgrade. +### Inclusion Information + +**Including Nano Switch as a non-secure device** + +If you want your Nano Switch as a non-secure device in your Z-Wave network, press the Action Button once on Nano Switch when you pair it to your gateway. If inclusion is successful, the green LED will be on for 2 seconds, and then return to a solid indication. If inclusion is unsuccessful, the red LED will be on for 2 seconds and then return to a colourful gradient. + +**Including Nano Switch as a secure device** + +In order to take full advantage of the Nano Switch, you will want your Nano Switch as a security device that uses encrypted messages to communicate in your Z-wave network. A security enabled controller/ gateway (or Z-Wave Plus controller) is required. + +1. Set your Z-Wave Plus controller into pairing mode. +2. Press the Action Button 2 times within 1 second on the Nano Switch, the blue LED (secure indication) will blink to indicate the Nano Switch is entering into secure pairing mode. +3. If the Nano Switch has been successfully added to your Z-Wave network, its RGB LED will be solid. If the pairing was unsuccessful, the red LED will be on for 2 seconds and then remain a colourful gradient, repeat the instructions above from step 1. + ## Channels The following table summarises the channels available for the ZW116 -: @@ -569,7 +586,7 @@ Association groups allow the device to send unsolicited reports to the controlle The ZW116 supports 3 association groups. -### Group 1: Z-Wave Plus Lifeline +### Group 1: Lifeline This group supports 5 nodes. @@ -611,6 +628,10 @@ This group supports 5 nodes. | COMMAND_CLASS_ASSOCIATION_V2| | | COMMAND_CLASS_VERSION_V2| | +### Documentation Links + +* [User Manual](https://www.cd-jackson.com/zwave_device_uploads/591/Nano-Switch-with-Energy-Metering-Manual.pdf) + --- Did you spot an error in the above definition or want to improve the content? diff --git a/_addons_bindings/zwave/doc/aeon/zw117_0_0.md b/_addons_bindings/zwave/doc/aeon/zw117_0_0.md index d73729ff5d..52305faba3 100644 --- a/_addons_bindings/zwave/doc/aeon/zw117_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/zw117_0_0.md @@ -8,11 +8,16 @@ title: ZW117 - ZWave # ZW117 Range Extender 6 This describes the Z-Wave device *ZW117*, manufactured by *[AEON Labs](http://aeotec.com/)* with the thing type UID of ```aeon_zw117_00_000```. +The device is in the category of *Power Outlet*, defining Small devices to be plugged into a power socket in a wall which stick there. + +![ZW117 product image](https://www.cd-jackson.com/zwave_device_uploads/527/527_default.jpg) + + The ZW117 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/527) to improve the documentation. +Aeotec Range Extender is a Z-Wave mesh network repeater which can extend the range of communication between Z-Wave products and assist other devices to reach each other in your Z-Wave network. The Range Extender can also communicate securely via AES 128 wireless Z-Wave commands and supports Over-The-Air (OTA) firmware upgrades. ## Channels diff --git a/_addons_bindings/zwave/doc/aeon/zw120_0_0.md b/_addons_bindings/zwave/doc/aeon/zw120_0_0.md index 298b3ce0c8..8f281753a6 100644 --- a/_addons_bindings/zwave/doc/aeon/zw120_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/zw120_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet The ZW120 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZW120 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZW120 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -31,6 +31,10 @@ To exclude your sensor from the z-wave network, turn the primary controller into ### Wakeup Information +The ZW120 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Remove your Sensor unit from its Back Mounting Plate, press the Action Button on the back of the Sensor unit and then release the Action Button. This will trigger and send a wake up notification command to your controller/gateway. ## Channels diff --git a/_addons_bindings/zwave/doc/aeon/zw122_0_0.md b/_addons_bindings/zwave/doc/aeon/zw122_0_0.md index 8c6289dc25..ae4c8397da 100644 --- a/_addons_bindings/zwave/doc/aeon/zw122_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/zw122_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Sensor*, defining Device used to measure somet The ZW122 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZW122 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZW122 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/721) to improve the documentation. +### Wakeup Information +The ZW122 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZW122 -: diff --git a/_addons_bindings/zwave/doc/aeon/zw129_0_0.md b/_addons_bindings/zwave/doc/aeon/zw129_0_0.md index f0db557126..b6c24f3969 100644 --- a/_addons_bindings/zwave/doc/aeon/zw129_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/zw129_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Wall Switch*, defining Any device attached to The ZW129 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZW129 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZW129 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/390) to improve the documentation. +### Wakeup Information +The ZW129 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZW129 -: diff --git a/_addons_bindings/zwave/doc/aeon/zw130_0_0.md b/_addons_bindings/zwave/doc/aeon/zw130_0_0.md index f72325f61d..92ebdf6c31 100644 --- a/_addons_bindings/zwave/doc/aeon/zw130_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/zw130_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Wall Switch*, defining Any device attached to The ZW130 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZW130 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZW130 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -43,6 +43,10 @@ If your WallMote Quad is successfully removed from the Z-Wave network, the LED w ### Wakeup Information +The ZW130 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + In order to send your WallMote Quad new configuration commands from your Z-Wave controller or gateway, it will need to be woken up. Remove your WallMote Quad unit from its Back Mounting Plate, press and hold the Action Button for 3 seconds(the buzzer chirp once and the orange LED will be ON) on the back of the WallMote Quad unit and then release it. This will trigger and send a wake up notification command to your controller/gateway, then your WallMote Quad will wake up for 10 minutes and the orange LED will fast blink while it is awake (if the WallMote Quad does not receive the Wake Up No More Info from the primary Controller). diff --git a/_addons_bindings/zwave/doc/aeon/zw132_0_0.md b/_addons_bindings/zwave/doc/aeon/zw132_0_0.md index f867782755..c5a8004f0a 100644 --- a/_addons_bindings/zwave/doc/aeon/zw132_0_0.md +++ b/_addons_bindings/zwave/doc/aeon/zw132_0_0.md @@ -10,11 +10,36 @@ This describes the Z-Wave device *ZW132*, manufactured by *[AEON Labs](http://ae The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. +![ZW132 product image](https://www.cd-jackson.com/zwave_device_uploads/724/724_default.jpg) + + The ZW132 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/724) to improve the documentation. +Aeotec Dual Nano Switch is a low-cost Z-Wave Switch specifically used to enable Z-Wave command and control (on/off) of any wall switches. It can report immediate wattage consumption or kWh energy usage over a period of time. In the event of power failure, non-volatile memory retains all programmed information relating to the unit’s operating status. + +It can connect to 2 external manual switches to control the load ON/OFF independently. Its surface has a pin socket, which can be used for connecting to the touch panel, so you can also use the touch panel to control the Dual Nano Switch. + +The Dual Nano Switch is also a security Z-Wave device and supports Over The Air (OTA) feature for the products firmware upgrade. + +**Reset your Dual Nano Switch.** + +If at some stage, your primary controller is missing or inoperable, you may wish to reset all of your Dual Nano Switch’s settings to their factory defaults. To do this, press and hold the Action Button for 20 seconds and then release it. Your Dual Nano Switch will now be reset to its original settings, and the green LED will be solid for 2 seconds and then remain the colourful gradient status as a confirmation. + +### Inclusion Information + +**Including Dual Nano Switch as a non-secure device:** + +If you want your Dual Nano Switch as a non-secure device in your Z-Wave network, press the Action Button once on Dual Nano Switch when you pair it to your gateway. If inclusion is successful, the green LED will be on for 2 seconds, and then return to a solid indication. If inclusion is unsuccessful, the red LED will be on for 2 seconds and then return to a colourful gradient. + +**Including Dual Nano Switch as a secure device:** + +In order to take full advantage of the Dual Nano Switch, you will want your Dual Nano Switch as a security device that uses encrypted messages to communicate in your Z-wave network. A security enabled controller/gateway (or Z-Wave Plus controller) is required. + +1. Set your Z-Wave Plus controller into pairing mode. +2. Press the Action Button 2 times within 1 second on the Dual Nano Switch, the blue LED (secure indication) will blink to indicate the Dual Nano Switch is entering into secure pairing mode. +3. If the Dual Nano Switch has been successfully added to your Z-Wave network, its RGB LED will be solid. If the pairing was unsuccessful, the red LED will be on for 2 seconds and then remain a colourful gradient, repeat the instructions above from step 1. ## Channels @@ -662,6 +687,10 @@ This group supports 5 nodes. | COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | | COMMAND_CLASS_SECURITY_V0| | +### Documentation Links + +* [User Manual](https://www.cd-jackson.com/zwave_device_uploads/724/Dual-Nano-Switch-manual.pdf) + --- Did you spot an error in the above definition or want to improve the content? diff --git a/_addons_bindings/zwave/doc/august/asl03_0_0.md b/_addons_bindings/zwave/doc/august/asl03_0_0.md index 4f04460983..9f2591f538 100644 --- a/_addons_bindings/zwave/doc/august/asl03_0_0.md +++ b/_addons_bindings/zwave/doc/august/asl03_0_0.md @@ -29,10 +29,6 @@ In order to include the August Smart Lock on to a Z-Wave network the user will h In order to exclude the August Smart Lock from a Z-Wave network the user will have to do the following: 1. Open the August app 2. Go to the Lock Settings screen 3. Select Z-Wave Settings 4. Select Remove Z-Wave Device 5. Put the controller into exclusion mode and select My Hub is in Exlusion Mode on the August app -### Wakeup Information - -Any operation (manual, RF, etc.) will wake up the lock. - ## Channels The following table summarises the channels available for the ASL-03 -: diff --git a/_addons_bindings/zwave/doc/benext/doorsensor_0_0.md b/_addons_bindings/zwave/doc/benext/doorsensor_0_0.md index 06997b5c00..61d934a1dd 100644 --- a/_addons_bindings/zwave/doc/benext/doorsensor_0_0.md +++ b/_addons_bindings/zwave/doc/benext/doorsensor_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *doorSensor*, manufactured by *[BeNext](http:// The doorSensor supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The doorSensor does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The doorSensor does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/223) to improve the documentation. +### Wakeup Information +The doorSensor does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the doorSensor -: diff --git a/_addons_bindings/zwave/doc/benext/energyswitch_0_0.md b/_addons_bindings/zwave/doc/benext/energyswitch_0_0.md index f2e7c9ebf5..359d97c129 100644 --- a/_addons_bindings/zwave/doc/benext/energyswitch_0_0.md +++ b/_addons_bindings/zwave/doc/benext/energyswitch_0_0.md @@ -11,12 +11,15 @@ This describes the Z-Wave device *Energy Switch +*, manufactured by *[BeNext](ht ![Energy Switch + product image](https://www.cd-jackson.com/zwave_device_uploads/445/445_default.png) -The Energy Switch + does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Energy Switch + does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/445) to improve the documentation. +### Wakeup Information +The Energy Switch + does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the Energy Switch + -: diff --git a/_addons_bindings/zwave/doc/benext/molite_0_0.md b/_addons_bindings/zwave/doc/benext/molite_0_0.md index d22539795b..1542da839c 100644 --- a/_addons_bindings/zwave/doc/benext/molite_0_0.md +++ b/_addons_bindings/zwave/doc/benext/molite_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *Molite*, manufactured by *[BeNext](http://www. The Molite supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The Molite does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Molite does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/374) to improve the documentation. +### Wakeup Information +The Molite does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the Molite -: diff --git a/_addons_bindings/zwave/doc/benext/tagreader_0_0.md b/_addons_bindings/zwave/doc/benext/tagreader_0_0.md index ce0e0e18f2..e66652240e 100644 --- a/_addons_bindings/zwave/doc/benext/tagreader_0_0.md +++ b/_addons_bindings/zwave/doc/benext/tagreader_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *Tag Reader*, manufactured by *[BeNext](http:// The Tag Reader supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The Tag Reader does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Tag Reader does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/444) to improve the documentation. +### Wakeup Information +The Tag Reader does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the Tag Reader -: diff --git a/_addons_bindings/zwave/doc/bonig/pope005206_0_0.md b/_addons_bindings/zwave/doc/bonig/pope005206_0_0.md index c671180fc6..c8c8467673 100644 --- a/_addons_bindings/zwave/doc/bonig/pope005206_0_0.md +++ b/_addons_bindings/zwave/doc/bonig/pope005206_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *POPE005206*, manufactured by *Bönig und Kalle The POPE005206 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The POPE005206 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The POPE005206 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/234) to improve the documentation. +### Wakeup Information +The POPE005206 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the POPE005206 -: diff --git a/_addons_bindings/zwave/doc/brk/zcombo_0_0.md b/_addons_bindings/zwave/doc/brk/zcombo_0_0.md index 0e557bd310..4fb00552de 100644 --- a/_addons_bindings/zwave/doc/brk/zcombo_0_0.md +++ b/_addons_bindings/zwave/doc/brk/zcombo_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *ZCOMBO*, manufactured by *BRK Brands, Inc.* wi The ZCOMBO supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZCOMBO does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZCOMBO does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/238) to improve the documentation. +### Wakeup Information +The ZCOMBO does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZCOMBO -: diff --git a/_addons_bindings/zwave/doc/brk/zsmoke_0_0.md b/_addons_bindings/zwave/doc/brk/zsmoke_0_0.md index 259e63a169..26e893baed 100644 --- a/_addons_bindings/zwave/doc/brk/zsmoke_0_0.md +++ b/_addons_bindings/zwave/doc/brk/zsmoke_0_0.md @@ -12,12 +12,15 @@ The device is in the category of *Smoke Detector*, defining Smoke detectors. The ZSMOKE supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZSMOKE does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZSMOKE does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/239) to improve the documentation. +### Wakeup Information +The ZSMOKE does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZSMOKE -: diff --git a/_addons_bindings/zwave/doc/chromagic/hsm02_0_0.md b/_addons_bindings/zwave/doc/chromagic/hsm02_0_0.md index 7b97125b0b..4ea06c462d 100644 --- a/_addons_bindings/zwave/doc/chromagic/hsm02_0_0.md +++ b/_addons_bindings/zwave/doc/chromagic/hsm02_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *HSM02*, manufactured by *[Chromagic Technologi The HSM02 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HSM02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HSM02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/342) to improve the documentation. +### Wakeup Information +The HSM02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the HSM02 -: diff --git a/_addons_bindings/zwave/doc/chromagic/sm103_0_0.md b/_addons_bindings/zwave/doc/chromagic/sm103_0_0.md index 9aa4ea1e39..7ccccd478b 100644 --- a/_addons_bindings/zwave/doc/chromagic/sm103_0_0.md +++ b/_addons_bindings/zwave/doc/chromagic/sm103_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *SM103*, manufactured by *[Chromagic Technologi The SM103 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The SM103 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SM103 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/428) to improve the documentation. +### Wakeup Information +The SM103 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the SM103 -: diff --git a/_addons_bindings/zwave/doc/cloud/a803n_0_0.md b/_addons_bindings/zwave/doc/cloud/a803n_0_0.md index 851f504a50..7db0c5e0e6 100644 --- a/_addons_bindings/zwave/doc/cloud/a803n_0_0.md +++ b/_addons_bindings/zwave/doc/cloud/a803n_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *A803N*, manufactured by *Cloud Media* with the The A803N supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The A803N does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The A803N does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/521) to improve the documentation. +### Wakeup Information +The A803N does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the A803N -: diff --git a/_addons_bindings/zwave/doc/cooper/rf9500_0_0.md b/_addons_bindings/zwave/doc/cooper/rf9500_0_0.md index 85868bad3f..499c4761f5 100644 --- a/_addons_bindings/zwave/doc/cooper/rf9500_0_0.md +++ b/_addons_bindings/zwave/doc/cooper/rf9500_0_0.md @@ -12,12 +12,15 @@ The device is in the category of *Wall Switch*, defining Any device attached to The RF9500 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The RF9500 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The RF9500 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/14) to improve the documentation. +### Wakeup Information +The RF9500 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the RF9500 -: diff --git a/_addons_bindings/zwave/doc/coqon/psmz0001_0_0.md b/_addons_bindings/zwave/doc/coqon/psmz0001_0_0.md index 7aaaf004aa..9a4773cbca 100644 --- a/_addons_bindings/zwave/doc/coqon/psmz0001_0_0.md +++ b/_addons_bindings/zwave/doc/coqon/psmz0001_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *PSMZ0001*, manufactured by *Coqon* with the th The device is in the category of *Power Outlet*, defining Small devices to be plugged into a power socket in a wall which stick there. -The PSMZ0001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The PSMZ0001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/427) to improve the documentation. +### Wakeup Information +The PSMZ0001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the PSMZ0001 -: diff --git a/_addons_bindings/zwave/doc/danfoss/010101_0_0.md b/_addons_bindings/zwave/doc/danfoss/010101_0_0.md index bf27e77600..ecf4b6283b 100644 --- a/_addons_bindings/zwave/doc/danfoss/010101_0_0.md +++ b/_addons_bindings/zwave/doc/danfoss/010101_0_0.md @@ -13,7 +13,7 @@ This describes the Z-Wave device *010101*, manufactured by *Danfoss* with the th The 010101 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The 010101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The 010101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -23,6 +23,10 @@ Short push middle button ### Wakeup Information +The 010101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Short push middle button ## Channels diff --git a/_addons_bindings/zwave/doc/danfoss/014g0160_0_0.md b/_addons_bindings/zwave/doc/danfoss/014g0160_0_0.md index 4d4a195463..1806c67acd 100644 --- a/_addons_bindings/zwave/doc/danfoss/014g0160_0_0.md +++ b/_addons_bindings/zwave/doc/danfoss/014g0160_0_0.md @@ -13,7 +13,7 @@ This describes the Z-Wave device *014G0160*, manufactured by *Danfoss* with the The 014G0160 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The 014G0160 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The 014G0160 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -27,6 +27,10 @@ Push one time LED Button ### Wakeup Information +The 014G0160 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Any button (LED, Temp+ or Temp-) ## Channels diff --git a/_addons_bindings/zwave/doc/danfoss/dthermz5_0_0.md b/_addons_bindings/zwave/doc/danfoss/dthermz5_0_0.md index 56e464aa42..18c166020a 100644 --- a/_addons_bindings/zwave/doc/danfoss/dthermz5_0_0.md +++ b/_addons_bindings/zwave/doc/danfoss/dthermz5_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *DTHERMZ5*, manufactured by *Danfoss* with the The DTHERMZ5 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DTHERMZ5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DTHERMZ5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/501) to improve the documentation. +### Wakeup Information +The DTHERMZ5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DTHERMZ5 -: diff --git a/_addons_bindings/zwave/doc/danfoss/dthermz6_0_0.md b/_addons_bindings/zwave/doc/danfoss/dthermz6_0_0.md index 4b1b56d758..d18112d9cc 100644 --- a/_addons_bindings/zwave/doc/danfoss/dthermz6_0_0.md +++ b/_addons_bindings/zwave/doc/danfoss/dthermz6_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *DTHERMZ6*, manufactured by *Danfoss* with the The DTHERMZ6 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DTHERMZ6 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DTHERMZ6 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/502) to improve the documentation. +### Wakeup Information +The DTHERMZ6 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DTHERMZ6 -: diff --git a/_addons_bindings/zwave/doc/danfoss/lc13_0_0.md b/_addons_bindings/zwave/doc/danfoss/lc13_0_0.md index 4f0353f5ec..76b0ca0359 100644 --- a/_addons_bindings/zwave/doc/danfoss/lc13_0_0.md +++ b/_addons_bindings/zwave/doc/danfoss/lc13_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *HVAC*, defining Air condition devices, Fans. The LC-13 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The LC-13 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The LC-13 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -44,6 +44,10 @@ Short push middle button ### Wakeup Information +The LC-13 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Short push middle button ## Channels diff --git a/_addons_bindings/zwave/doc/danfoss/lcz251_0_0.md b/_addons_bindings/zwave/doc/danfoss/lcz251_0_0.md index 1e6cae5757..779000fdf2 100644 --- a/_addons_bindings/zwave/doc/danfoss/lcz251_0_0.md +++ b/_addons_bindings/zwave/doc/danfoss/lcz251_0_0.md @@ -8,13 +8,40 @@ title: LCZ251 - ZWave # LCZ251 Living Connect Z Thermostat 2.51 This describes the Z-Wave device *LCZ251*, manufactured by *Danfoss* with the thing type UID of ```danfoss_lcz251_00_000```. +The device is in the category of *Radiator Control*, defining Controls on radiators used to heat up rooms. + +![LCZ251 product image](https://www.cd-jackson.com/zwave_device_uploads/163/163_default.jpg) + + The LCZ251 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The LCZ251 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The LCZ251 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/163) to improve the documentation. +Danfoss Living connect® Z is an electronic radiator thermostat, intended for using with water based room radiators. + +### Inclusion Information + +• Ensure living connect® Z is factory reset . +• Activate “Inclusion” on the Z-Wave controller. +• Quickly press and release middle button on living connect® Z. +• Observe both controller and living connect® Z for status of the process. + +### Exclusion Information + +• Ensure living connect® Z is factory reset . +• Activate “Inclusion” on the Z-Wave controller. +• Quickly press and release middle button on living connect® Z. +• Observe both controller and living connect® Z for status of the process. + +### Wakeup Information + +The LCZ251 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + +• Quickly press and release middle button on living connect® Z. ## Channels @@ -71,6 +98,10 @@ This group supports 1 nodes. | COMMAND_CLASS_VERSION_V1| | | COMMAND_CLASS_MULTI_CMD_V1| | +### Documentation Links + +* [Danfoss Manual](https://www.cd-jackson.com/zwave_device_uploads/163/Danfoss-living-connect-OEM-VQIDA15T-013R9563.pdf) + --- Did you spot an error in the above definition or want to improve the content? diff --git a/_addons_bindings/zwave/doc/danfoss/mt02650_0_0.md b/_addons_bindings/zwave/doc/danfoss/mt02650_0_0.md index 1e8c4abc03..f76b7ccc75 100644 --- a/_addons_bindings/zwave/doc/danfoss/mt02650_0_0.md +++ b/_addons_bindings/zwave/doc/danfoss/mt02650_0_0.md @@ -10,7 +10,7 @@ This describes the Z-Wave device *MT02650*, manufactured by *Danfoss* with the t The MT02650 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The MT02650 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The MT02650 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -22,6 +22,10 @@ Short push middle button ### Wakeup Information +The MT02650 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Short push middle button ## Channels diff --git a/_addons_bindings/zwave/doc/defaro/dad101_0_0.md b/_addons_bindings/zwave/doc/defaro/dad101_0_0.md index 931425402c..bf8b4217f8 100644 --- a/_addons_bindings/zwave/doc/defaro/dad101_0_0.md +++ b/_addons_bindings/zwave/doc/defaro/dad101_0_0.md @@ -28,10 +28,6 @@ The DAD-101 supports routing. This allows the device to communicate using other 1. Put controller in exclusion mode. 2. Fast press add/remove button three times. -### Wakeup Information - -Always listening - ## Channels The following table summarises the channels available for the DAD-101 -: diff --git a/_addons_bindings/zwave/doc/defaro/das102_0_0.md b/_addons_bindings/zwave/doc/defaro/das102_0_0.md index 9cc9c51855..fc962bc53b 100644 --- a/_addons_bindings/zwave/doc/defaro/das102_0_0.md +++ b/_addons_bindings/zwave/doc/defaro/das102_0_0.md @@ -31,10 +31,6 @@ https://defaro.ru/index.php/support/instructions/70-das-102 2. Fast press add/remove button three times. 3. Please note that all parameters except for parameters 15 & 16 will reset to their default state -### Wakeup Information - -Always woken. - ## Channels The following table summarises the channels available for the DAS-102 -: diff --git a/_addons_bindings/zwave/doc/defaro/dsi101_0_0.md b/_addons_bindings/zwave/doc/defaro/dsi101_0_0.md index 611b1e42c5..135b2abf44 100644 --- a/_addons_bindings/zwave/doc/defaro/dsi101_0_0.md +++ b/_addons_bindings/zwave/doc/defaro/dsi101_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Wall Switch*, defining Any device attached to The DSI-101 binary switch supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DSI-101 binary switch does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DSI-101 binary switch does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -35,6 +35,10 @@ https://defaro.ru/index.php/support/instructions/208-dsi-101 ### Wakeup Information +The DSI-101 binary switch does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Press button on the device once. ## Channels diff --git a/_addons_bindings/zwave/doc/devolo/09813_0_0.md b/_addons_bindings/zwave/doc/devolo/09813_0_0.md index b14b00153f..7430e4bdbb 100644 --- a/_addons_bindings/zwave/doc/devolo/09813_0_0.md +++ b/_addons_bindings/zwave/doc/devolo/09813_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Smoke Detector*, defining Smoke detectors. The 09813 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The 09813 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The 09813 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/615) to improve the documentation. +### Wakeup Information +The 09813 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the 09813 -: diff --git a/_addons_bindings/zwave/doc/devolo/mt02646_0_0.md b/_addons_bindings/zwave/doc/devolo/mt02646_0_0.md index 7604a453b0..683289868d 100644 --- a/_addons_bindings/zwave/doc/devolo/mt02646_0_0.md +++ b/_addons_bindings/zwave/doc/devolo/mt02646_0_0.md @@ -17,7 +17,16 @@ The MT02646 supports routing. This allows the device to communicate using other ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1) to improve the documentation. +The Home Control Smart Metering Plug can be plugged into any wall outlet in the home. It enhances every +connected device with useful functions, such as time-controlled enabling and disabling or power monitoring + +### Inclusion Information + +Push the front button three times rapidly within 2 seconds. + +### Exclusion Information + +Push the front button three times rapidly within 2 seconds. ## Channels diff --git a/_addons_bindings/zwave/doc/devolo/mt02647_0_0.md b/_addons_bindings/zwave/doc/devolo/mt02647_0_0.md index ef221f6135..d157778c4f 100644 --- a/_addons_bindings/zwave/doc/devolo/mt02647_0_0.md +++ b/_addons_bindings/zwave/doc/devolo/mt02647_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *MT02647*, manufactured by *Devolo* with the th The MT02647 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The MT02647 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The MT02647 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/290) to improve the documentation. +### Wakeup Information +The MT02647 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the MT02647 -: diff --git a/_addons_bindings/zwave/doc/devolo/mt02648_0_0.md b/_addons_bindings/zwave/doc/devolo/mt02648_0_0.md index 1fa5411af5..55737affca 100644 --- a/_addons_bindings/zwave/doc/devolo/mt02648_0_0.md +++ b/_addons_bindings/zwave/doc/devolo/mt02648_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Door*, defining Door sensors. The MT02648 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The MT02648 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The MT02648 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -40,6 +40,10 @@ The MT02648 does not permanently listen for messages sent from the controller - ### Wakeup Information +The MT02648 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + to wake-up the device immediately, please remove the front cover, and press the tamper key once. The device will wake-up 10 seconds ## Channels @@ -253,7 +257,7 @@ The following option values may be configured, in addition to values in the rang | Value | Description | |--------|-------------| -| 20 | Preset: PIR Super Sensitivity and Binary Report = Bits: 00010100 = 20 | +| 20 | PIR Super Sensitivity and Binary Report | The manufacturer defined default value is ```4```. diff --git a/_addons_bindings/zwave/doc/devolo/mt2652_0_0.md b/_addons_bindings/zwave/doc/devolo/mt2652_0_0.md index 23fb2e409f..d898f24be4 100644 --- a/_addons_bindings/zwave/doc/devolo/mt2652_0_0.md +++ b/_addons_bindings/zwave/doc/devolo/mt2652_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Wall Switch*, defining Any device attached to The MT2652 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The MT2652 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The MT2652 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/3) to improve the documentation. +### Wakeup Information +The MT2652 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the MT2652 -: diff --git a/_addons_bindings/zwave/doc/devolo/mt2653_0_0.md b/_addons_bindings/zwave/doc/devolo/mt2653_0_0.md index 9b8c9835a5..043ca58896 100644 --- a/_addons_bindings/zwave/doc/devolo/mt2653_0_0.md +++ b/_addons_bindings/zwave/doc/devolo/mt2653_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *MT2653*, manufactured by *Devolo* with the thi The MT2653 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The MT2653 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The MT2653 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/341) to improve the documentation. +### Wakeup Information +The MT2653 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the MT2653 -: diff --git a/_addons_bindings/zwave/doc/devolo/mt2755_0_0.md b/_addons_bindings/zwave/doc/devolo/mt2755_0_0.md index be66d671f8..17fad011b9 100644 --- a/_addons_bindings/zwave/doc/devolo/mt2755_0_0.md +++ b/_addons_bindings/zwave/doc/devolo/mt2755_0_0.md @@ -13,7 +13,7 @@ This describes the Z-Wave device *MT02755*, manufactured by *Devolo* with the th The MT02755 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The MT02755 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The MT02755 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -46,6 +46,10 @@ Notice: Use this procedure only in the event that the primary controller is lost ### Wakeup Information +The MT02755 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Press the tamper button on the back side ## Channels diff --git a/_addons_bindings/zwave/doc/devolo/mt2756_0_0.md b/_addons_bindings/zwave/doc/devolo/mt2756_0_0.md index 97851829a8..f79124c64a 100644 --- a/_addons_bindings/zwave/doc/devolo/mt2756_0_0.md +++ b/_addons_bindings/zwave/doc/devolo/mt2756_0_0.md @@ -8,17 +8,24 @@ title: MT2756 - ZWave # MT2756 MT2756 Flood Sensor This describes the Z-Wave device *MT2756*, manufactured by *Devolo* with the thing type UID of ```devolo_mt2756_00_000```. +The device is in the category of *Sensor*, defining Device used to measure something. + ![MT2756 product image](https://www.cd-jackson.com/zwave_device_uploads/489/489_default.jpg) The MT2756 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The MT2756 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The MT2756 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/489) to improve the documentation. +The Home Control Water Sensor is a water sensor and warns you about flooding or leaking water. As soon as water touches the open metal contacts, the device triggers an alarm. The Home Control Water Sensor is ideal for use in locations such as under a sink, under the supply valve of a washing machine or on an aquarium. It is equipped with an integrated LED and a release button. + +### Wakeup Information + +The MT2756 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the MT2756 -: diff --git a/_addons_bindings/zwave/doc/devolo/pst021b_0_0.md b/_addons_bindings/zwave/doc/devolo/pst021b_0_0.md index ee4e8a8356..ff81112510 100644 --- a/_addons_bindings/zwave/doc/devolo/pst021b_0_0.md +++ b/_addons_bindings/zwave/doc/devolo/pst021b_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *PST02-1B*, manufactured by *Devolo* with the t The PST02-1B supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The PST02-1B does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The PST02-1B does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/534) to improve the documentation. +### Wakeup Information +The PST02-1B does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the PST02-1B -: diff --git a/_addons_bindings/zwave/doc/dlink/dchz110_0_0.md b/_addons_bindings/zwave/doc/dlink/dchz110_0_0.md index a675f85278..f10c73d3f2 100644 --- a/_addons_bindings/zwave/doc/dlink/dchz110_0_0.md +++ b/_addons_bindings/zwave/doc/dlink/dchz110_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *DCH-Z110*, manufactured by *[D-Link](http://ww The DCH-Z110 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DCH-Z110 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DCH-Z110 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/252) to improve the documentation. +### Wakeup Information +The DCH-Z110 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DCH-Z110 -: diff --git a/_addons_bindings/zwave/doc/dlink/dchz120_0_0.md b/_addons_bindings/zwave/doc/dlink/dchz120_0_0.md index 1881942d5d..8a7268de64 100644 --- a/_addons_bindings/zwave/doc/dlink/dchz120_0_0.md +++ b/_addons_bindings/zwave/doc/dlink/dchz120_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *DCH-Z120*, manufactured by *[D-Link](http://ww The DCH-Z120 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DCH-Z120 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DCH-Z120 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/308) to improve the documentation. +### Wakeup Information +The DCH-Z120 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DCH-Z120 -: diff --git a/_addons_bindings/zwave/doc/dlink/dchz310_0_0.md b/_addons_bindings/zwave/doc/dlink/dchz310_0_0.md index c6b4c382a2..22f7a1f176 100644 --- a/_addons_bindings/zwave/doc/dlink/dchz310_0_0.md +++ b/_addons_bindings/zwave/doc/dlink/dchz310_0_0.md @@ -12,7 +12,7 @@ The device is in the category of *Smoke Detector*, defining Smoke detectors. The DCH-Z310 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DCH-Z310 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DCH-Z310 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -28,6 +28,10 @@ Put your hub/controller in Exclusion mode. Press the button on the front of the ### Wakeup Information +The DCH-Z310 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + After the device is added to the network, it will wake-up once per day in default. When it wake-up it will broadcast the "Wake Up Notification" message to the network, and wake-up for 10 seconds to receive the setting commands. The wake-up interval minimum setting is 30 minutes, and maximum setting is 120 hours. And the interval step is 30 minutes. If the user wants to wake-up the device immediately, please press the button once. The device will wake-up 10 seconds. ## Channels diff --git a/_addons_bindings/zwave/doc/eco/dwzwave2_0_0.md b/_addons_bindings/zwave/doc/eco/dwzwave2_0_0.md index 437ec11602..16a41089a9 100644 --- a/_addons_bindings/zwave/doc/eco/dwzwave2_0_0.md +++ b/_addons_bindings/zwave/doc/eco/dwzwave2_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *DWZWAVE2*, manufactured by *Ecolink* with the The DWZWAVE2 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DWZWAVE2 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DWZWAVE2 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/138) to improve the documentation. +### Wakeup Information +The DWZWAVE2 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DWZWAVE2 -: diff --git a/_addons_bindings/zwave/doc/eco/ecolinkpirv25_0_0.md b/_addons_bindings/zwave/doc/eco/ecolinkpirv25_0_0.md index b52ae6dcae..e0a0b12e04 100644 --- a/_addons_bindings/zwave/doc/eco/ecolinkpirv25_0_0.md +++ b/_addons_bindings/zwave/doc/eco/ecolinkpirv25_0_0.md @@ -10,7 +10,7 @@ This describes the Z-Wave device *Ecolink PIR v2.5*, manufactured by *Ecolink* w The Ecolink PIR v2.5 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The Ecolink PIR v2.5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Ecolink PIR v2.5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -32,6 +32,11 @@ Initial device inclusion is started by removing the pull tab from the back of th The manual indicates network-wide inclusion is supported, but also indicates that the device should be within 15 feet of the controller during the inclusion process. +### Wakeup Information + +The Ecolink PIR v2.5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the Ecolink PIR v2.5 -: diff --git a/_addons_bindings/zwave/doc/eco/flfzwave5r1_0_0.md b/_addons_bindings/zwave/doc/eco/flfzwave5r1_0_0.md index 5d69eb74fe..d08e90e41e 100644 --- a/_addons_bindings/zwave/doc/eco/flfzwave5r1_0_0.md +++ b/_addons_bindings/zwave/doc/eco/flfzwave5r1_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *FLF-ZWAVE5 R1*, manufactured by *Ecolink* with The FLF-ZWAVE5 R1 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FLF-ZWAVE5 R1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FLF-ZWAVE5 R1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/744) to improve the documentation. +### Wakeup Information +The FLF-ZWAVE5 R1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the FLF-ZWAVE5 R1 -: diff --git a/_addons_bindings/zwave/doc/eco/pir1_0_0.md b/_addons_bindings/zwave/doc/eco/pir1_0_0.md index 971e962704..12673a4a20 100644 --- a/_addons_bindings/zwave/doc/eco/pir1_0_0.md +++ b/_addons_bindings/zwave/doc/eco/pir1_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Motion Detector*, defining Motion sensors/dete The PIR supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The PIR does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The PIR does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -33,6 +33,10 @@ nodes in group two (turning devices off). See Configuration Command Class. ### Wakeup Information +The PIR does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + By default, a sensor is configured to send Wake Up Notification frames every three hours. A controller may change the duration between Wake Up Notification frames to be between one hour and one week in increments of two hundred seconds with the Wake Up Interval Set diff --git a/_addons_bindings/zwave/doc/eco/tiltzwave25eco_0_0.md b/_addons_bindings/zwave/doc/eco/tiltzwave25eco_0_0.md index 863c5d5305..5fd3c90135 100644 --- a/_addons_bindings/zwave/doc/eco/tiltzwave25eco_0_0.md +++ b/_addons_bindings/zwave/doc/eco/tiltzwave25eco_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Garage Door*, defining Garage Door. The TILT-ZWAVE2.5-ECO supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The TILT-ZWAVE2.5-ECO does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The TILT-ZWAVE2.5-ECO does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -35,6 +35,10 @@ Exclusion mode on the sensor is activated on the sensor by the exact same proced ### Wakeup Information +The TILT-ZWAVE2.5-ECO does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + To save power, this sensor sleeps most of the time and is therefore not awake to receive messages from a gateway for testing. Removing the top case from the sensor will put in device into a tampered mode in which the sensor will stay awake and able to receive messages. Most of the time an end user would not do this, but if the sensor needs to be configured after inclusion, an end user can follow the instructions below for sending Wake-Up notifications. The sensor will wake up every so often and when the case is closed, it will send a Wake-Up Notification to allow the life line master node controller that the sensor is now available for any queued messages that the controller may have for the sensor. **The time between Wake-Up Notifications can be configured with the Wake-Up Notification command class to be between 1 hour and 1 week with interval steps of 200 seconds.** diff --git a/_addons_bindings/zwave/doc/eco/tiltzwave2_0_0.md b/_addons_bindings/zwave/doc/eco/tiltzwave2_0_0.md index 2e14ff1954..75ef6dc68f 100644 --- a/_addons_bindings/zwave/doc/eco/tiltzwave2_0_0.md +++ b/_addons_bindings/zwave/doc/eco/tiltzwave2_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *TILTZWAVE2*, manufactured by *Ecolink* with th The TILTZWAVE2 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The TILTZWAVE2 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The TILTZWAVE2 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/139) to improve the documentation. +### Wakeup Information +The TILTZWAVE2 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the TILTZWAVE2 -: diff --git a/_addons_bindings/zwave/doc/elexa/dmms1_0_0.md b/_addons_bindings/zwave/doc/elexa/dmms1_0_0.md index e7f3a4b240..eb9f3e6414 100644 --- a/_addons_bindings/zwave/doc/elexa/dmms1_0_0.md +++ b/_addons_bindings/zwave/doc/elexa/dmms1_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Motion Detector*, defining Motion sensors/dete The DMMS1 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DMMS1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DMMS1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -45,6 +45,10 @@ Factory Reset: ### Wakeup Information +The DMMS1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + 1. Remove the cover of the Motion Detector by twisting apart and make sure the Motion Detector is powered 2. Press the Connect Button quickly three times in a row diff --git a/_addons_bindings/zwave/doc/elexa/dmmz1_0_0.md b/_addons_bindings/zwave/doc/elexa/dmmz1_0_0.md index ec24cd2181..7265537028 100644 --- a/_addons_bindings/zwave/doc/elexa/dmmz1_0_0.md +++ b/_addons_bindings/zwave/doc/elexa/dmmz1_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *DMMZ1*, manufactured by *Elexa Consumer Produc The DMMZ1 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DMMZ1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DMMZ1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/684) to improve the documentation. +### Wakeup Information +The DMMZ1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DMMZ1 -: diff --git a/_addons_bindings/zwave/doc/elexa/dmwd1_0_0.md b/_addons_bindings/zwave/doc/elexa/dmwd1_0_0.md index 27175ce6f7..cc743a2fe0 100644 --- a/_addons_bindings/zwave/doc/elexa/dmwd1_0_0.md +++ b/_addons_bindings/zwave/doc/elexa/dmwd1_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Sensor*, defining Device used to measure somet The DMWD1 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DMWD1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DMWD1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/608) to improve the documentation. +### Wakeup Information +The DMWD1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DMWD1 -: diff --git a/_addons_bindings/zwave/doc/elexa/dmws1_0_0.md b/_addons_bindings/zwave/doc/elexa/dmws1_0_0.md index f82b4c6ae6..6d826a0d6d 100644 --- a/_addons_bindings/zwave/doc/elexa/dmws1_0_0.md +++ b/_addons_bindings/zwave/doc/elexa/dmws1_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *DMWS1*, manufactured by *Elexa Consumer Produc The DMWS1 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DMWS1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DMWS1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/651) to improve the documentation. +### Wakeup Information +The DMWS1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DMWS1 -: diff --git a/_addons_bindings/zwave/doc/enerwave/zw20r_0_0.md b/_addons_bindings/zwave/doc/enerwave/zw20r_0_0.md index b6946121b7..6cb2a6601c 100644 --- a/_addons_bindings/zwave/doc/enerwave/zw20r_0_0.md +++ b/_addons_bindings/zwave/doc/enerwave/zw20r_0_0.md @@ -27,10 +27,6 @@ When the controller is in exclusion mode, press the program button of ZW20R, and then the controller will remove it from the current Z-Wave network, and the LED will blink on the receptacle. -### Wakeup Information - -mains device - ## Channels The following table summarises the channels available for the ZW20R -: diff --git a/_addons_bindings/zwave/doc/enerwave/zw500dm_0_0.md b/_addons_bindings/zwave/doc/enerwave/zw500dm_0_0.md index 2248e210eb..0d1019469a 100644 --- a/_addons_bindings/zwave/doc/enerwave/zw500dm_0_0.md +++ b/_addons_bindings/zwave/doc/enerwave/zw500dm_0_0.md @@ -10,11 +10,35 @@ This describes the Z-Wave device *ZW500DM*, manufactured by *Wenzhou MTLC Electr The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. +![ZW500DM product image](https://www.cd-jackson.com/zwave_device_uploads/382/382_default.jpg) + + The ZW500DM supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/382) to improve the documentation. +The ZW500DM Dimmer Switch is a perfect wireless manual and remote on/off/ dim brightness control replacement of regular switch, controlling incandescent, dimmable LED and CFL. This ZW500DM dimmer switch is fully compatible with other Z-Wave devices, provides programmable function creating a perfect ambiance such as scenes, association, schedule event, etc. Also it can be added to most Z-Wave compliant controllers. + +Sliding Air-Gap switch to totally disconnect power while replacing light bulbs and preventing from leakage current from the fixture(s). This ZW500DM dimmer works with ZW3K 3-Way Auxiliary Switch that reduces energy consumption, enhancing the value of technology of your home, condominiums and apartment. + +Features -: + +- Perfect Replacement for regular wall ON/OFF & Dim switch, 120VAC +- Wireless Z-Wave technology creates a mesh network for command and control interoperability with other Z-Wave compliant controller and devices +- Manual and Remote ON/OFF& Dim control of any permanently installed incandescent, dimmable LED and CFL lamp fixture +- Preset light level option allows the dimmer will turn on to the light level that it was adjusted to the previous time when the light was on +- Can be used for single pole or 3- Way (Multi-location) with ZW3K Auxiliary Switch (sold separately) +- Measures energy usage of the wired load + +The ZW500DM Smart Meter Dimmer Switch enables you to measure the energy usage of your appliance. When added to a Z-Wave network, the ZW500DM reports real time data to your gateway or controller. It can also display actual consumption (in W) and the accumulated power used (in kWh) in the user interface of the gateway/remote. Please use the gateway installation manual for specific instructions on measuring the power. + +### Inclusion Information + +When the primary controller is in the adding mode, flicks the paddle 3 times in the 1.5 second. The primary controller will verify the adding, assign a node ID number for the module. + +### Exclusion Information + +When the primary controller is in the removing mode, flicks the paddle 3 times in the 1.5 second. The primary controller will verify the removing, remove the module from the current Z-Wave network, and the LED will blink when the module is on power. ## Channels @@ -22,10 +46,18 @@ The following table summarises the channels available for the ZW500DM -: | Channel | Channel Id | Category | Item Type | |---------|------------|----------|-----------| +| Dimmer | switch_dimmer | DimmableLight | Dimmer | | Sensor (power) | sensor_power | Energy | Number | | Electric meter (kWh) | meter_kwh | Energy | Number | | Electric meter (watts) | meter_watts | Energy | Number | +### Dimmer + +The brightness channel allows to control the brightness of a light. + It is also possible to switch the light on and off. + +The ```switch_dimmer``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. + ### Sensor (power) Indicates the energy consumption (kWh). @@ -53,15 +85,15 @@ Detailed information on each parameter can be found in the sections below. | Param | Name | Description | |-------|-------|-------------| -| 1 | | Synchronization of load power and LED indicator | -| 8 | | Instant Energy Autosend Interval (send METER\_REPORT) | -| 9 | | Instant Energy Autosend interval (send SENSOR\_MULTILEVEL\_REPORT) | -| 10 | | Accumulated Energy Autosend Interval report (send METER\_REPORT) | -| 11 | | Enable automatic notifications to associated device | -| 12 | | Minimum change in wattage report | +| 1 | LED is on when load is on | Synchronization of load power and LED indicator | +| 8 | Instant Energy Autosend Interval | Instant Energy Autosend Interval (send METER\_REPORT) | +| 9 | Instant Power Autosend Interval | Instant Power Autosend interval (send SENSOR\_MULTILEVEL\_REPORT) | +| 10 | Accumulated Energy Autosend Interval | Accumulated Energy Autosend Interval report (send METER\_REPORT) | +| 11 | Enable automatic notifications | Enable automatic notifications to associated device | +| 12 | Minimum change in wattage triggering report | Minimum change in wattage report | | | Switch All Mode | Set the mode for the switch when receiving SWITCH ALL commands | -### Parameter 1: +### Parameter 1: LED is on when load is on Synchronization of load power and LED indicator @@ -77,7 +109,7 @@ The manufacturer defined default value is ```0``` (Power on, LED off). This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```. -### Parameter 8: +### Parameter 8: Instant Energy Autosend Interval Instant Energy Autosend Interval (send METER\_REPORT) @@ -88,9 +120,9 @@ The manufacturer defined default value is ```0```. This parameter has the configuration ID ```config_8_1``` and is of type ```INTEGER```. -### Parameter 9: +### Parameter 9: Instant Power Autosend Interval -Instant Energy Autosend interval (send SENSOR\_MULTILEVEL\_REPORT) +Instant Power Autosend interval (send SENSOR\_MULTILEVEL\_REPORT) Values in the range 0 to 255 may be set. @@ -99,7 +131,7 @@ The manufacturer defined default value is ```0```. This parameter has the configuration ID ```config_9_1``` and is of type ```INTEGER```. -### Parameter 10: +### Parameter 10: Accumulated Energy Autosend Interval Accumulated Energy Autosend Interval report (send METER\_REPORT) @@ -110,7 +142,7 @@ The manufacturer defined default value is ```0```. This parameter has the configuration ID ```config_10_1``` and is of type ```INTEGER```. -### Parameter 11: +### Parameter 11: Enable automatic notifications Enable automatic notifications to associated device Device will send a notification whenever the is a wattage change @@ -128,7 +160,7 @@ The manufacturer defined default value is ```1``` (Send (METER_REPORT) only). This parameter has the configuration ID ```config_11_1``` and is of type ```INTEGER```. -### Parameter 12: +### Parameter 12: Minimum change in wattage triggering report Minimum change in wattage report 0-255: 0.0-25.5W diff --git a/_addons_bindings/zwave/doc/enerwave/zwnbds_0_0.md b/_addons_bindings/zwave/doc/enerwave/zwnbds_0_0.md index e4a0020da8..80cff0432c 100644 --- a/_addons_bindings/zwave/doc/enerwave/zwnbds_0_0.md +++ b/_addons_bindings/zwave/doc/enerwave/zwnbds_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet The ZWN-BDS supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZWN-BDS does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZWN-BDS does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -44,6 +44,10 @@ _At the back of the door/window sensor, there is a program button which is used ### Wakeup Information +The ZWN-BDS does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + To complete Z-Wave association, please refer to your controller's manual. Each controller has its own association method. **If your controller needs the sensor to wake up, press and hold the program button for 2 seconds, release the button when the status LED turns off, and the ZWN-BDS will wake up manually.** ## Channels diff --git a/_addons_bindings/zwave/doc/enerwave/zwnbpc_0_0.md b/_addons_bindings/zwave/doc/enerwave/zwnbpc_0_0.md index 3ef215746d..96ed8a6b85 100644 --- a/_addons_bindings/zwave/doc/enerwave/zwnbpc_0_0.md +++ b/_addons_bindings/zwave/doc/enerwave/zwnbpc_0_0.md @@ -16,12 +16,15 @@ The device is in the category of *Motion Detector*, defining Motion sensors/dete The ZWN-BPC supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZWN-BPC does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZWN-BPC does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/186) to improve the documentation. +### Wakeup Information +The ZWN-BPC does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZWN-BPC -: diff --git a/_addons_bindings/zwave/doc/enerwave/zwnbpc_5_10.md b/_addons_bindings/zwave/doc/enerwave/zwnbpc_5_10.md index 1db4756965..55c7d6cf66 100644 --- a/_addons_bindings/zwave/doc/enerwave/zwnbpc_5_10.md +++ b/_addons_bindings/zwave/doc/enerwave/zwnbpc_5_10.md @@ -16,12 +16,15 @@ The device is in the category of *Motion Detector*, defining Motion sensors/dete The ZWN-BPC-PLUS supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZWN-BPC-PLUS does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZWN-BPC-PLUS does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/795) to improve the documentation. +### Wakeup Information +The ZWN-BPC-PLUS does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZWN-BPC-PLUS -: diff --git a/_addons_bindings/zwave/doc/erone/hmdw001_0_0.md b/_addons_bindings/zwave/doc/erone/hmdw001_0_0.md index df92b659a2..f39594f080 100644 --- a/_addons_bindings/zwave/doc/erone/hmdw001_0_0.md +++ b/_addons_bindings/zwave/doc/erone/hmdw001_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *HM-DW001*, manufactured by *Erone* with the th The HM-DW001 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HM-DW001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HM-DW001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/694) to improve the documentation. +### Wakeup Information +The HM-DW001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the HM-DW001 -: diff --git a/_addons_bindings/zwave/doc/eurotronic/cometz_0_0.md b/_addons_bindings/zwave/doc/eurotronic/cometz_0_0.md index 11cd80962f..0d707a2da2 100644 --- a/_addons_bindings/zwave/doc/eurotronic/cometz_0_0.md +++ b/_addons_bindings/zwave/doc/eurotronic/cometz_0_0.md @@ -12,12 +12,15 @@ The device is in the category of *Radiator Control*, defining Controls on radiat The CometZ supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The CometZ does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The CometZ does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/372) to improve the documentation. +### Wakeup Information +The CometZ does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the CometZ -: diff --git a/_addons_bindings/zwave/doc/eurotronic/spirit_0_0.md b/_addons_bindings/zwave/doc/eurotronic/spirit_0_0.md index c19ac64225..9ceaad2594 100644 --- a/_addons_bindings/zwave/doc/eurotronic/spirit_0_0.md +++ b/_addons_bindings/zwave/doc/eurotronic/spirit_0_0.md @@ -17,6 +17,10 @@ The Spirit supports routing. This allows the device to communicate using other r ## Overview +Spirit Z-Wave Plus is a Z-Wave radio standard compatible energy-saving radiator thermostat. + +FLiRS (Frequently Listening Receiver Slave): Spirit Z-Wave uses FLiRS to provide short latency and short responding times. + ### Inclusion Information Start Inclusion mode of your primary Z-Wave Controller. Press the Boost-Button. Spirit Z-Wave Plus will show the assigned NodeID. diff --git a/_addons_bindings/zwave/doc/eurotronic/stellaz_0_0.md b/_addons_bindings/zwave/doc/eurotronic/stellaz_0_0.md index 0f283ebd80..4391c2a795 100644 --- a/_addons_bindings/zwave/doc/eurotronic/stellaz_0_0.md +++ b/_addons_bindings/zwave/doc/eurotronic/stellaz_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Radiator Control*, defining Controls on radiat The StellaZ supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The StellaZ does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The StellaZ does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/183) to improve the documentation. +### Wakeup Information +The StellaZ does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the StellaZ -: diff --git a/_addons_bindings/zwave/doc/everspring/hsm02_0_0.md b/_addons_bindings/zwave/doc/everspring/hsm02_0_0.md index bacae7d3b6..39afc85c67 100644 --- a/_addons_bindings/zwave/doc/everspring/hsm02_0_0.md +++ b/_addons_bindings/zwave/doc/everspring/hsm02_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *HSM02*, manufactured by *Everspring* with the The HSM02 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HSM02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HSM02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/34) to improve the documentation. +### Wakeup Information +The HSM02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the HSM02 -: diff --git a/_addons_bindings/zwave/doc/everspring/hsp02_0_0.md b/_addons_bindings/zwave/doc/everspring/hsp02_0_0.md index 23caab4813..67dea291e3 100644 --- a/_addons_bindings/zwave/doc/everspring/hsp02_0_0.md +++ b/_addons_bindings/zwave/doc/everspring/hsp02_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Motion Detector*, defining Motion sensors/dete The HSP02 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HSP02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HSP02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/22) to improve the documentation. +### Wakeup Information +The HSP02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the HSP02 -: diff --git a/_addons_bindings/zwave/doc/everspring/sf812_0_0.md b/_addons_bindings/zwave/doc/everspring/sf812_0_0.md index 0b9352040d..1a24de4fab 100644 --- a/_addons_bindings/zwave/doc/everspring/sf812_0_0.md +++ b/_addons_bindings/zwave/doc/everspring/sf812_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Smoke Detector*, defining Smoke detectors. The SF812 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The SF812 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SF812 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -41,6 +41,11 @@ Pressing link key three times within 1.5 second will enter inclusion mode. The D Pressing link key three times within 1.5 second will enter exclusion mode. The Detector will stay “awake” for 10 minutes to allow time for setting and device status enquiring. +### Wakeup Information + +The SF812 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the SF812 -: diff --git a/_addons_bindings/zwave/doc/everspring/sm103_0_0.md b/_addons_bindings/zwave/doc/everspring/sm103_0_0.md index 839e06907e..4a55ceeed1 100644 --- a/_addons_bindings/zwave/doc/everspring/sm103_0_0.md +++ b/_addons_bindings/zwave/doc/everspring/sm103_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Door*, defining Door sensors. The SM103 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The SM103 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SM103 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/35) to improve the documentation. +### Wakeup Information +The SM103 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the SM103 -: diff --git a/_addons_bindings/zwave/doc/everspring/sp103_0_0.md b/_addons_bindings/zwave/doc/everspring/sp103_0_0.md index 62e22066c2..182c96b06e 100644 --- a/_addons_bindings/zwave/doc/everspring/sp103_0_0.md +++ b/_addons_bindings/zwave/doc/everspring/sp103_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *SP103*, manufactured by *Everspring* with the The SP103 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The SP103 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SP103 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/29) to improve the documentation. +### Wakeup Information +The SP103 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the SP103 -: diff --git a/_addons_bindings/zwave/doc/everspring/sp814_0_0.md b/_addons_bindings/zwave/doc/everspring/sp814_0_0.md index 745e436baf..ad2251ebd1 100644 --- a/_addons_bindings/zwave/doc/everspring/sp814_0_0.md +++ b/_addons_bindings/zwave/doc/everspring/sp814_0_0.md @@ -8,14 +8,22 @@ title: SP814 - ZWave # SP814 Motion Detector This describes the Z-Wave device *SP814*, manufactured by *Everspring* with the thing type UID of ```everspring_sp814_00_000```. +The device is in the category of *Motion Detector*, defining Motion sensors/detectors. + +![SP814 product image](https://www.cd-jackson.com/zwave_device_uploads/30/30_default.jpg) + + The SP814 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The SP814 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SP814 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/30) to improve the documentation. +### Wakeup Information + +The SP814 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the SP814 -: diff --git a/_addons_bindings/zwave/doc/everspring/sp816_0_0.md b/_addons_bindings/zwave/doc/everspring/sp816_0_0.md index 6bceaf0bd9..75d22737ab 100644 --- a/_addons_bindings/zwave/doc/everspring/sp816_0_0.md +++ b/_addons_bindings/zwave/doc/everspring/sp816_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Motion Detector*, defining Motion sensors/dete The SP816 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The SP816 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SP816 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -31,6 +31,10 @@ The detector supports Auto Inclusion feature where it will automatically enter I ### Wakeup Information +The SP816 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + For waking up please triple click the tamper switch ## Channels diff --git a/_addons_bindings/zwave/doc/everspring/st812_0_0.md b/_addons_bindings/zwave/doc/everspring/st812_0_0.md index f1ce0f4aed..740cadbda9 100644 --- a/_addons_bindings/zwave/doc/everspring/st812_0_0.md +++ b/_addons_bindings/zwave/doc/everspring/st812_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *ST812*, manufactured by *Everspring* with the The ST812 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ST812 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ST812 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/37) to improve the documentation. +### Wakeup Information +The ST812 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ST812 -: diff --git a/_addons_bindings/zwave/doc/everspring/st814_0_0.md b/_addons_bindings/zwave/doc/everspring/st814_0_0.md index 0c5c4287ef..02cd07db6c 100644 --- a/_addons_bindings/zwave/doc/everspring/st814_0_0.md +++ b/_addons_bindings/zwave/doc/everspring/st814_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *ST814*, manufactured by *Everspring* with the The ST814 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ST814 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ST814 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/31) to improve the documentation. +### Wakeup Information +The ST814 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ST814 -: diff --git a/_addons_bindings/zwave/doc/everspring/st815_0_0.md b/_addons_bindings/zwave/doc/everspring/st815_0_0.md index f1f544e3a3..3bb5bb6ec9 100644 --- a/_addons_bindings/zwave/doc/everspring/st815_0_0.md +++ b/_addons_bindings/zwave/doc/everspring/st815_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *ST815*, manufactured by *Everspring* with the The ST815 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ST815 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ST815 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/32) to improve the documentation. +### Wakeup Information +The ST815 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ST815 -: diff --git a/_addons_bindings/zwave/doc/evolve/lpm15_0_0.md b/_addons_bindings/zwave/doc/evolve/lpm15_0_0.md index 21ad854226..566300c337 100644 --- a/_addons_bindings/zwave/doc/evolve/lpm15_0_0.md +++ b/_addons_bindings/zwave/doc/evolve/lpm15_0_0.md @@ -8,6 +8,8 @@ title: LPM-15 - ZWave # LPM-15 Appliance module This describes the Z-Wave device *LPM-15*, manufactured by *Evolve* with the thing type UID of ```evolve_lpm15_00_000```. +The device is in the category of *Power Outlet*, defining Small devices to be plugged into a power socket in a wall which stick there. + ![LPM-15 product image](https://www.cd-jackson.com/zwave_device_uploads/580/580_default.jpg) @@ -15,7 +17,34 @@ The LPM-15 supports routing. This allows the device to communicate using other r ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/580) to improve the documentation. +The Evolve Plug-in Appliance Module is a component of the Evolve lighting control system and is fully scene capable. The Appliance Module is plugged into any standard grounded AC wall outlet, and the appliance or other device is then plugged into the module. Once connected, the appliance/device can be easily turned ON or OFF remotely via the Z-Wave network. + +This device is compatible with Z-Wave security systems and can handle a maximum of the following loads: + +- Incandescent – 600W, 120 VAC +- Resistive – 15 amps (1800 watts), 120 VAC +- Motor – ½ H.P., 120 VAC + +This Plug-in Appliance Module is designed to work with other Evolve enabled devices. Evolve nodes of other types can be included in the network and will also act as repeaters to increase the range of the network. + +As part of a Z-Wave network, the LPM-15 will also act as a wireless repeater to ensure that commands intended for another device in the network are received. This is useful when the device would otherwise be out of the radio range of the wireless controller. + +### Inclusion Information + +1. Start a search for new z-wave binding items via the add things interface +2. Press the button on the front of the unit to include + +Note: will work with inclusion set to network-wide. + +Factory reset procedure: + +1. Unplug device and wait 15 seconds +2. Plug device in and immediately press the front button twice (the two presses must occur within 20 seconds of plugging in the unit. + +### Exclusion Information + +1. Place controller in exclude mode +2. Press button on front of device ## Channels @@ -69,6 +98,10 @@ The device does not support associations. | COMMAND_CLASS_PROTECTION_V1| | | COMMAND_CLASS_VERSION_V1| | +### Documentation Links + +* [Evlovle LPM-15 Product Overview](https://www.cd-jackson.com/zwave_device_uploads/580/LPM-15.pdf) + --- Did you spot an error in the above definition or want to improve the content? diff --git a/_addons_bindings/zwave/doc/fakro/arf_0_0.md b/_addons_bindings/zwave/doc/fakro/arf_0_0.md index 50263624a7..ab8f6e6559 100644 --- a/_addons_bindings/zwave/doc/fakro/arf_0_0.md +++ b/_addons_bindings/zwave/doc/fakro/arf_0_0.md @@ -36,7 +36,7 @@ The following table summarises the channels available for the ARF -: | Channel | Channel Id | Category | Item Type | |---------|------------|----------|-----------| | Switch | switch_binary | Switch | Switch | -| Dimmer | switch_dimmer | DimmableLight | Dimmer | +| Blinds control | blinds_control | Blinds | Rollershutter | | Alarm (power) | alarm_power | Door | Switch | ### Switch @@ -45,12 +45,11 @@ Switch the power on and off. The ```switch_binary``` channel supports the ```Switch``` item and is in the ```Switch``` category. -### Dimmer +### Blinds control -The brightness channel allows to control the brightness of a light. - It is also possible to switch the light on and off. +Provides start / stop control of blinds. -The ```switch_dimmer``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. +The ```blinds_control``` channel supports the ```Rollershutter``` item and is in the ```Blinds``` category. ### Alarm (power) @@ -87,7 +86,7 @@ The device does not support associations. | COMMAND_CLASS_NO_OPERATION_V1| | | COMMAND_CLASS_BASIC_V1| | | COMMAND_CLASS_SWITCH_BINARY_V1| | -| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| | +| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| Linked to BASIC| | COMMAND_CLASS_SWITCH_ALL_V1| | | COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | | COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| | @@ -102,7 +101,7 @@ The device does not support associations. ### Documentation Links -* [fakro arf manual EN](https://www.cd-jackson.com/zwave_device_uploads/848/ARF-ARP-Z-WAVE-EN.pdf) +* [User Manual (EN)](https://www.cd-jackson.com/zwave_device_uploads/848/ARF-ARP-Z-WAVE-EN.pdf) --- diff --git a/_addons_bindings/zwave/doc/fibaro/fgcd001_0_0.md b/_addons_bindings/zwave/doc/fibaro/fgcd001_0_0.md index 7b18505694..709c2fc4b8 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgcd001_0_0.md +++ b/_addons_bindings/zwave/doc/fibaro/fgcd001_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *FGCD001*, manufactured by *[Fibargroup](http:/ The FGCD001 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FGCD001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FGCD001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/711) to improve the documentation. +### Wakeup Information +The FGCD001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the FGCD001 -: diff --git a/_addons_bindings/zwave/doc/fibaro/fgd211_0_0.md b/_addons_bindings/zwave/doc/fibaro/fgd211_0_0.md index 9bc7dca39e..8b0dd866ac 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgd211_0_0.md +++ b/_addons_bindings/zwave/doc/fibaro/fgd211_0_0.md @@ -18,7 +18,23 @@ The FGD211 supports routing. This allows the device to communicate using other r ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/117) to improve the documentation. +Remotely controlled Dimmer designed to operate with or without neutral lead. It may be used as a switch in systems without neutral lead. + +As a Dimmer it operates under the following loads: + +- conventional incandescent +- Halogen 230V +- low voltage halogen 12V (with electronic transformers) +- dimmable LED +- when used with FGB001 it may operate with any dimmable load up to 500W + +### Inclusion Information + +The Dimmer enters the mode of inclusion after a quick pressing three times the push-button connected to S1 terminal or push-button B located inside the housing. For bi-stable switch perform 3 position changes. + +### Exclusion Information + +The Dimmer enters the mode of exclusion after a quick pressing three times the push-button connected to S1 terminal or push-button B located inside the housing. For bi-stable switch perform 3 position changes ## Channels @@ -46,20 +62,20 @@ Detailed information on each parameter can be found in the sections below. |-------|-------|-------------| | 1 | Enable/Disable ALL ON/OFF | Activate/Deactive ALL ON/OFF | | 6 | Separation of association sending (key 1) | Activate/Deactivate association sending for group 1 - Also see param #16 | -| 7 | Control key #2 behaviour | Key no.2 is not represented by any physical device - only devices in the 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 | +| 7 | Control key #2 behaviour | Key no. 2 is not represented by any physical device | | 8 | Dimming step at automatic control | | | 9 | Time of MANUALLY moving between the extreme dimming values | Options for changing parameter 1-255 (10ms - 2,5s) | -| 10 | Time of AUTOMATIC moving between the extreme dimming values | 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...) | +| 10 | Time of AUTOMATIC moving between extreme dimming values | Time of autom. moving the dimmer between min/max | | 11 | Dimming step at manual control | Options for changing parameter 1-99 | | 12 | Maximum dimmer level control | Options for changing parameter 2-99 | | 13 | Minimum dimmer level control | Options for changing parameter 1-98 | | 14 | Inputs Button/Switch configuration | Binary inputs type configuration | | 15 | Parm 15 | Double-click set lighting at 100% | | 16 | Saving state before power failure | Saving state before power failure | -| 17 | 3-way switch | 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) | +| 17 | 3-way switch | Function of 3-way switch | | 18 | Synchronizing light level for associated devices | The dimmer communicate the level to the associated devices. (default value 0) | -| 19 | Change [On-Off] bi-stable keys | This function allow user to change \[On-Off\] bi-stable keys (parameter no. 14) (default value 0) | -| 20 | Parm 20 | 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 dimmm | +| 19 | Change [On-Off] bi-stable keys | Allow user to change \[On-Off\] bi-stable keys | +| 20 | Control impulse length | Change of control impulse length. | | 30 | Relay 1: Response to General Alarm | | | 39 | ALARM FLASHING alarm time | Amount of time (ms) the device keeps on flashing after receipt of Alarm Frame | | | Switch All Mode | Set the mode for the switch when receiving SWITCH ALL commands | @@ -91,8 +107,8 @@ The following option values may be configured -: | Value | Description | |--------|-------------| | 0 | Map status to all devices in group 1 | -| 1 | Map OFF status to all devices in group 1, Double click on key 1 will s | -| 2 | Map OFF status to all devices in group 1, Double click on key 1 will s | +| 1 | Map OFF status to all devices in group 1 | +| 2 | Map OFF status to all devices in group 1, 100% brightness | The manufacturer defined default value is ```0``` (Map status to all devices in group 1). @@ -101,8 +117,8 @@ This parameter has the configuration ID ```config_6_1``` and is of type ```INTEG ### Parameter 7: Control key #2 behaviour -Key no.2 is not represented by any physical device - only devices in the 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 - +Key no. 2 is not represented by any physical device +Info: Key no. 2 is not represented by any physical device expect 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 states The following option values may be configured -: | Value | Description | @@ -137,10 +153,10 @@ The manufacturer defined default value is ```5```. This parameter has the configuration ID ```config_9_1``` and is of type ```INTEGER```. -### Parameter 10: Time of AUTOMATIC moving between the extreme dimming values +### Parameter 10: Time of AUTOMATIC moving between extreme dimming values +Time of autom. moving the dimmer between min/max 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...) - Values in the range 0 to 255 may be set. The manufacturer defined default value is ```1```. @@ -221,18 +237,18 @@ The following option values may be configured -: | Value | Description | |--------|-------------| -| 0 | State NOT saved at power failure, all outputs are set to OFF upon powe | -| 1 | State saved at power failure, all outputs are set to previous state up | +| 0 | State NOT saved at power failure | +| 1 | State saved at power failure | -The manufacturer defined default value is ```1``` (State saved at power failure, all outputs are set to previous state up). +The manufacturer defined default value is ```1``` (State saved at power failure). This parameter has the configuration ID ```config_16_1``` and is of type ```INTEGER```. ### Parameter 17: 3-way switch +Function of 3-way switch 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 following option values may be configured -: | Value | Description | @@ -263,24 +279,26 @@ This parameter has the configuration ID ```config_18_1``` and is of type ```INTE ### Parameter 19: Change [On-Off] bi-stable keys +Allow user to change \[On-Off\] bi-stable keys This function allow user to change \[On-Off\] bi-stable keys (parameter no. 14) (default value 0) - The following option values may be configured -: | Value | Description | |--------|-------------| | 0 | Device changes status on key status change | -| 1 | Device status depends on key status; ON when the key is ON, OFF when t | +| 1 | Device status depends on key status | The manufacturer defined default value is ```0``` (Device changes status on key status change). This parameter has the configuration ID ```config_19_1``` and is of type ```INTEGER```. -### Parameter 20: Parm 20 +### Parameter 20: Control impulse length -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 dimmm +Change of control impulse length. +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 dimming capabilty. Values in the range 100 to 170 may be set. The manufacturer defined default value is ```110```. @@ -297,11 +315,11 @@ The following option values may be configured -: | Value | Description | |--------|-------------| | 0 | DEACTIVATION - no response to alarm frames | -| 1 | ALARM RELAY ON - relay will turn ON upon receipt of alarm frame | -| 2 | ALARM RELAY OFF - relay will turn OFF upon receipt of alarm frame | -| 3 | ALARM FLASHING - relay will turn ON and OFF periodically (see param.39 | +| 1 | Alarm relay ON | +| 2 | Alarm relay OFF | +| 3 | ALARM FLASHING | -The manufacturer defined default value is ```3``` (ALARM FLASHING - relay will turn ON and OFF periodically (see param.39). +The manufacturer defined default value is ```3``` (ALARM FLASHING). This parameter has the configuration ID ```config_30_1``` and is of type ```INTEGER```. @@ -373,7 +391,7 @@ This group supports 1 nodes. ### Documentation Links -* [English User Manual (v1.4-v1.8)](https://www.cd-jackson.com/zwave_device_uploads/117/Fibaro---FGD211-Dimmer-en-1-4-1-8.pdf) +* [FGD211 EN 1.4-1.8](https://www.cd-jackson.com/zwave_device_uploads/117/FGD-211-EN-A-v1-4-1-8.pdf) --- diff --git a/_addons_bindings/zwave/doc/fibaro/fgdw002_0_0.md b/_addons_bindings/zwave/doc/fibaro/fgdw002_0_0.md index 391398dd97..6f10d880ce 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgdw002_0_0.md +++ b/_addons_bindings/zwave/doc/fibaro/fgdw002_0_0.md @@ -10,33 +10,62 @@ This describes the Z-Wave device *FGDW002*, manufactured by *[Fibargroup](http:/ The device is in the category of *Sensor*, defining Device used to measure something. -![FGDW002 product image](https://www.cd-jackson.com/zwave_device_uploads/604/604_default.png) +![FGDW002 product image](https://www.cd-jackson.com/zwave_device_uploads/604/604_default.jpg) The FGDW002 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FGDW002 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FGDW002 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview +FIBARO Door/Window Sensor 2 is a wireless, battery powered Hall effect contact sensor, compatible with the Z-Wave Plus standard. Changing the device’s status will automatically send signal to the Z-Wave controller and associated devices. + +Sensor can be used to trigger scenes and wherever there is a need for information about opening or closing of doors, windows, garage doors, etc. Opening is detected by separating the sensor’s body and the magnet. + +In addition the FIBARO Door/Window Sensor 2 is equipped with a built-in temperature sensor. + +**Main features of FIBARO Door/Window Sensor 2** + +- Compatible with any Z-Wave or Z-Wave+ Controller, +- Supports protected mode (Z-Wave network Security Mode) with AES-128 encryption +- Door/window opening detected through separation of Sensor’s body and a magnet +- Built-in temperature sensor +- Detects tampering, when detached or opened +- Easily mounted on doors, windows, garage gates and roller blinds +- Battery powered +- Visual LED indicator signalling status of the device +- 7 color variations. + +### Inclusion Information + +1. Place the Door/Window Sensor 2 within the direct range of your Z-Wave controller. +2. Set the main controller in (Security/non-Security Mode) add mode (see the controller’s manual). +3. Quickly, three times press one of the TMP buttons (while the other button is pressed). +4. Wait for the adding process to end. +5. Successful adding will be confirmed by the Z-Wave controller’s message. + +### Exclusion Information + +1. Place the Door/Window Sensor 2 within the direct range of your Z-Wave controller. +2. Set the main controller into remove mode (see the controller’s manual). +3. Quickly, three times press one of the TMP buttons (while the other button is pressed). +4. Wait for the removing process to end. +5. Successful removing will be confirmed by the Z-Wave controller’s message. + ### Wakeup Information -Available settings: 0 or 3600-64800 (in seconds (1-18h), 3600s (1h) -step) -Default setting: 21600 (6h) +The FGDW002 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. - -The Door/Window Sensor will wake up after each defined time interval and always try to connect with the main controller. After a successful communication attempt, the sensor will update configuration parameters, associations and settings and will go into standby mode. +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. - -After failed communication attempt (e.g. lack of Z-Wave range) the device will go into standby mode and retry to establish connection with the main controller after the next time interval. +Available settings: 0 or 3600-64800 (in seconds (1-18h), 3600s (1h) step). Default setting: 21600 seconds (6h) - -Setting wake up interval to 0 disables sending Wake Up Notification frame automatically. +The Door/Window Sensor will wake up after each defined time interval and always try to connect with the main controller. After a successful communication attempt, the sensor will update configuration parameters, associations and settings and will go into standby mode. -Wake up may be still performed manually by a clicking one of the TMP buttons (while the other button is pressed). +After failed communication attempt (e.g. lack of Z-Wave range) the device will go into standby mode and retry to establish connection with the main controller after the next time interval. -Longer time interval means less frequent communication and thus a longer battery life. +Setting wake up interval to 0 disables sending Wake Up Notification frame automatically. Wake up may be still performed manually by a clicking one of the TMP buttons (while the other button is pressed). ## Channels diff --git a/_addons_bindings/zwave/doc/fibaro/fgfs101_23_23.md b/_addons_bindings/zwave/doc/fibaro/fgfs101_23_23.md index 0bde1cea9a..e04e8320e6 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgfs101_23_23.md +++ b/_addons_bindings/zwave/doc/fibaro/fgfs101_23_23.md @@ -16,12 +16,15 @@ The device is in the category of *Sensor*, defining Device used to measure somet The FGFS101 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FGFS101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FGFS101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/408) to improve the documentation. +### Wakeup Information +The FGFS101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the FGFS101 -: diff --git a/_addons_bindings/zwave/doc/fibaro/fgfs101_3_2.md b/_addons_bindings/zwave/doc/fibaro/fgfs101_3_2.md index 2d2dc6a57f..13bd02468d 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgfs101_3_2.md +++ b/_addons_bindings/zwave/doc/fibaro/fgfs101_3_2.md @@ -16,7 +16,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet The FGFS101 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FGFS101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FGFS101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -50,6 +50,10 @@ inundation of water. ### Wakeup Information +The FGFS101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Single click TMP button ## Channels diff --git a/_addons_bindings/zwave/doc/fibaro/fggc001_0_0.md b/_addons_bindings/zwave/doc/fibaro/fggc001_0_0.md index 8070686f57..182cd38e04 100644 --- a/_addons_bindings/zwave/doc/fibaro/fggc001_0_0.md +++ b/_addons_bindings/zwave/doc/fibaro/fggc001_0_0.md @@ -8,16 +8,48 @@ title: FGGC001 - ZWave # FGGC001 Fibaro Swipe Scene Controller This describes the Z-Wave device *FGGC001*, manufactured by *[Fibargroup](http://www.fibaro.com/)* with the thing type UID of ```fibaro_fggc001_00_000```. +The device is in the category of *Remote Control*, defining Any portable or hand-held device that controls the status of something, e.g. remote control, keyfob etc.. + ![FGGC001 product image](https://www.cd-jackson.com/zwave_device_uploads/349/349_default.jpg) The FGGC001 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FGGC001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FGGC001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/349) to improve the documentation. +FIBARO Swipe is a revolutionary battery gesture control pad that allows you to control devices in your Z-Wave network without actually touching anything. Swipe up, down, left, right, make a circular gesture and use sequences to get full and intuitive control of your home. + +### Inclusion Information + +1\. Place the Swipe within the direct range of your Z-Wave controller. +2\. Set the main controller in (security/non-security) add mode (see the controller’s manual). +3\. Move and hold your hand close to the center of the pad. +4\. If the device is battery powered, high pitched beep will signal exiting the Standby Mode. +5\. Loud sound sequence will confrm entering the menu, keep holding your hand. +6\. After hearing two short beeps (green indicator colour), withdraw the hand and perform swiping up gesture to confrm selection (two beeps will confrm validity). +7\. Wait for the adding process to end. +8\. Successful adding will be confrmed by the Z-Wave controller’s message and 3 short beeps (green visual indicator colour). + +### Exclusion Information + +1\. Place the Swipe within the direct range of your Z-Wave controller. +2\. Set the main controller in remove mode (see the controller’s manual). +3\. Move and hold your hand close to the center of the pad. +4\. If the device is battery powered, high pitched beep will signal exiting the Standby Mode. +5\. Loud sound sequence will confrm entering the menu, keep holding your hand. +6\. After hearing two short beeps (green indicator colour), withdraw the hand and perform swiping up gesture to confrm selection (two beeps will confrm validity). +7\. Wait for the removing process to end. +8\. Successful removing will be confrmed by the Z-Wave controller’s message and sequence of 2 short beeps, pause, 1 short beep (red visual indicator colour). + +### Wakeup Information + +The FGGC001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + +Use 1st menu position to wake up the device or click the button on the back of the device once. ## Channels @@ -49,26 +81,26 @@ Detailed information on each parameter can be found in the sections below. | Param | Name | Description | |-------|-------|-------------| -| 1 | Device Orientation | Parameter determines orientation of the Swipe in relation to its default position. | +| 1 | Device Orientation | Orientation in relation to default position. | | 2 | Buzzer - acoustic signal settings | Acoustic signalling of gestures detection. | | 3 | LED diode - visual indicator settings | Visual indication of gestures detection | | 4 | Buzzer - signalling result of gesture recognition | Acoustic signalling of gesture recognition result (using the built-in buzzer). | -| 5 | Powering mode - interval of updating the current mode | This parameter determines how often the device checks if the USB power supply is connected and updates powering mode if needed. | +| 5 | Powering mode - interval of updating the current mode | Check if the USB pwr supply is connected, update pwr mode | | 6 | Power saving mode (battery mode) | This parameter determines operation of gesture detection when battery powered. | -| 7 | Hold gesture to enter the menu | This parameter allows to choose if the menu can be entered using the Hold gesture. | +| 7 | Hold gesture to enter the menu | Choose if the menu can be entered using the Hold gesture. | | 10 | Scenes sent to the controller | Defines which actions result in sending scenes to 1st “Lifeline” group. | -| 11 | Associations in Z-Wave network security mode | Parameter defines how commands are sent in specified association groups: as secure or non-secure. Parameter is active only in Z-Wave network security mode. It does not apply to 1st “Lifeline” association group. | -| 12 | Control mode of 2nd - 5th "Flick UP/DOWN/LEFT/RIGHT” association groups and scenes | Parameter allows to choose control mode for 2nd-5th groups and scenes. | -| 13 | Rate of smooth level control | Parameter allows to choose how long the hand has to be held near the center of the pad after "AirWheel" gesture for the associated devices to reach their maximum/minimum level. | -| 20 | SWITCH ON control frame value for FLICK UP gesture | This parameter allows to set value sent in SWITCH ON command frame to the association group. | -| 21 | SWITCH OFF control frame value for FLICK UP gesture | This parameter allows to set value sent in SWITCH OFF command frame to the association group. | -| 22 | SWITCH ON control frame value for FLICK DOWN gesture | This parameter allows to set value sent in SWITCH ON command frame to the association group. | -| 23 | SWITCH OFF control frame value for FLICK DOWN gesture | This parameter allows to set value sent in SWITCH OFF command frame to the association group. | -| 24 | SWITCH ON control frame value for FLICK LEFT gesture | This parameter allows to set value sent in SWITCH ON command frame to the association group. | -| 25 | SWITCH OFF control frame value for FLICK LEFT gesture | This parameter allows to set value sent in SWITCH OFF command frame to the association group. | -| 26 | SWITCH ON control frame value for FLICK RIGHT gesture | This parameter allows to set value sent in SWITCH ON command frame to the association group. | -| 27 | SWITCH OFF control frame value for FLICK RIGHT gesture | This parameter allows to set value sent in SWITCH OFF command frame to the association group. | -| 30 | Sequence learning mode | Parameter activated by the main Z-Wave controller. Change its value to launch sequence learning procedure for the desired slot. | +| 11 | Associations in Z-Wave network security mode | Define sent command for specified association groups. | +| 12 | Control mode of 2nd-5th "Flick UP/DOWN/LEFT/RIGHT” | Choose control mode for 2nd-5th groups and scenes. | +| 13 | Rate of smooth level control | Choose gesture time for "AirWheel" to reach max/min level. | +| 20 | SWITCH ON control frame value for FLICK UP gesture | Value sent in SWITCH ON command | +| 21 | SWITCH OFF control frame value for FLICK UP gesture | Value sent in SWITCH OFF command frame. | +| 22 | SWITCH ON control frame value for FLICK DOWN gesture | Value sent in SWITCH ON command frame. | +| 23 | SWITCH OFF control frame value for FLICK DOWN gesture | Value sent in SWITCH OFF command frame. | +| 24 | SWITCH ON control frame value for FLICK LEFT gesture | Value sent in SWITCH ON command frame. | +| 25 | SWITCH OFF control frame value for FLICK LEFT gesture | Value sent in SWITCH OFF command frame. | +| 26 | SWITCH ON control frame value for FLICK RIGHT gesture | Value sent in SWITCH ON command frame. | +| 27 | SWITCH OFF control frame value for FLICK RIGHT gesture | Value sent in SWITCH OFF command frame. | +| 30 | Sequence learning mode | Launch sequence learning procedure | | 31 | 1st gestures sequence (SLOT 1) | Value containing sequence of gestures. | | 32 | 2nd gestures sequence (SLOT 2) | Value containing sequence of gestures. | | 33 | 3rd gestures sequence (SLOT 3) | Value containing sequence of gestures. | @@ -80,8 +112,8 @@ Detailed information on each parameter can be found in the sections below. ### Parameter 1: Device Orientation +Orientation in relation to default position. Parameter determines orientation of the Swipe in relation to its default position. - The following option values may be configured -: | Value | Description | @@ -147,8 +179,8 @@ This parameter has the configuration ID ```config_4_1``` and is of type ```INTEG ### Parameter 5: Powering mode - interval of updating the current mode +Check if the USB pwr supply is connected, update pwr mode This parameter determines how often the device checks if the USB power supply is connected and updates powering mode if needed. - The following option values may be configured, in addition to values in the range 0 to 1080 -: | Value | Description | @@ -182,7 +214,9 @@ This parameter has the configuration ID ```config_6_1``` and is of type ```INTEG ### Parameter 7: Hold gesture to enter the menu +Choose if the menu can be entered using the Hold gesture. This parameter allows to choose if the menu can be entered using the Hold gesture. + After disabling the Hold gesture in parameter 7, menu can be entered by using the B-button only!This is an advanced parameter and will therefore not show in the user interface without entering advanced mode. The following option values may be configured -: @@ -220,7 +254,9 @@ This is a read only parameter. ### Parameter 11: Associations in Z-Wave network security mode +Define sent command for specified association groups. Parameter defines how commands are sent in specified association groups: as secure or non-secure. Parameter is active only in Z-Wave network security mode. It does not apply to 1st “Lifeline” association group. + Parameter 11 values may be combined, e.g. 1+2=3 means that 2nd & 3rd group are sent as secure. The following option values may be configured, in addition to values in the range 1 to 31 -: @@ -237,9 +273,11 @@ The manufacturer defined default value is ```31```. This parameter has the configuration ID ```config_11_1``` and is of type ```INTEGER```. -### Parameter 12: Control mode of 2nd - 5th "Flick UP/DOWN/LEFT/RIGHT” association groups and scenes +### Parameter 12: Control mode of 2nd-5th "Flick UP/DOWN/LEFT/RIGHT” +Choose control mode for 2nd-5th groups and scenes. Parameter allows to choose control mode for 2nd-5th groups and scenes. + By default, Toggle Mode is active, meaning that a single flick turns ON the group and the same flick turns it OFF, doubled flicks are inactive. After disabling Toggle Mode a single flick will turn the device ON and the same flick doubled will turn it OFF. @@ -263,7 +301,9 @@ This parameter has the configuration ID ```config_12_1``` and is of type ```INTE ### Parameter 13: Rate of smooth level control +Choose gesture time for "AirWheel" to reach max/min level. Parameter allows to choose how long the hand has to be held near the center of the pad after "AirWheel" gesture for the associated devices to reach their maximum/minimum level. + Available settings: 0-10 - duration in seconds @@ -278,7 +318,9 @@ This parameter has the configuration ID ```config_13_2``` and is of type ```INTE ### Parameter 20: SWITCH ON control frame value for FLICK UP gesture +Value sent in SWITCH ON command This parameter allows to set value sent in SWITCH ON command frame to the association group. + Commands sent to association group for turn ON/OFF can be adjusted in parameters 20-27. 0 - turning off associated devices @@ -295,7 +337,9 @@ This parameter has the configuration ID ```config_20_2``` and is of type ```INTE ### Parameter 21: SWITCH OFF control frame value for FLICK UP gesture +Value sent in SWITCH OFF command frame. This parameter allows to set value sent in SWITCH OFF command frame to the association group. + Commands sent to association group for turn ON/OFF can be adjusted in parameters 20-27. 0 - turning off associated devices @@ -312,7 +356,9 @@ This parameter has the configuration ID ```config_21_2``` and is of type ```INTE ### Parameter 22: SWITCH ON control frame value for FLICK DOWN gesture +Value sent in SWITCH ON command frame. This parameter allows to set value sent in SWITCH ON command frame to the association group. + Commands sent to association group for turn ON/OFF can be adjusted in parameters 20-27. 0 - turning off associated devices @@ -329,7 +375,9 @@ This parameter has the configuration ID ```config_22_2``` and is of type ```INTE ### Parameter 23: SWITCH OFF control frame value for FLICK DOWN gesture +Value sent in SWITCH OFF command frame. This parameter allows to set value sent in SWITCH OFF command frame to the association group. + Commands sent to association group for turn ON/OFF can be adjusted in parameters 20-27. 0 - turning off associated devices @@ -346,7 +394,9 @@ This parameter has the configuration ID ```config_23_2``` and is of type ```INTE ### Parameter 24: SWITCH ON control frame value for FLICK LEFT gesture +Value sent in SWITCH ON command frame. This parameter allows to set value sent in SWITCH ON command frame to the association group. + Commands sent to association group for turn ON/OFF can be adjusted in parameters 20-27. 0 - turning off associated devices @@ -363,7 +413,9 @@ This parameter has the configuration ID ```config_24_2``` and is of type ```INTE ### Parameter 25: SWITCH OFF control frame value for FLICK LEFT gesture +Value sent in SWITCH OFF command frame. This parameter allows to set value sent in SWITCH OFF command frame to the association group. + Commands sent to association group for turn ON/OFF can be adjusted in parameters 20-27. 0 - turning off associated devices @@ -380,7 +432,9 @@ This parameter has the configuration ID ```config_25_2``` and is of type ```INTE ### Parameter 26: SWITCH ON control frame value for FLICK RIGHT gesture +Value sent in SWITCH ON command frame. This parameter allows to set value sent in SWITCH ON command frame to the association group. + Commands sent to association group for turn ON/OFF can be adjusted in parameters 20-27. 0 - turning off associated devices @@ -397,7 +451,9 @@ This parameter has the configuration ID ```config_26_2``` and is of type ```INTE ### Parameter 27: SWITCH OFF control frame value for FLICK RIGHT gesture +Value sent in SWITCH OFF command frame. This parameter allows to set value sent in SWITCH OFF command frame to the association group. + Commands sent to association group for turn ON/OFF can be adjusted in parameters 20-27. 0 - turning off associated devices @@ -414,7 +470,9 @@ This parameter has the configuration ID ```config_27_2``` and is of type ```INTE ### Parameter 30: Sequence learning mode +Launch sequence learning procedure Parameter activated by the main Z-Wave controller. Change its value to launch sequence learning procedure for the desired slot. + 0 - learning mode disabled 1-6 - launch sequence learning for selected slot diff --git a/_addons_bindings/zwave/doc/fibaro/fgk101_0_0.md b/_addons_bindings/zwave/doc/fibaro/fgk101_0_0.md index b96eea7247..f22730e140 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgk101_0_0.md +++ b/_addons_bindings/zwave/doc/fibaro/fgk101_0_0.md @@ -16,7 +16,7 @@ The device is in the category of *Door*, defining Door sensors. The FGK101 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FGK101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FGK101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -60,6 +60,10 @@ The Fibaro Door / Window Sensor is a wireless, battery powered, Z-Wave compatibl ### Wakeup Information +The FGK101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + The default wake-up interval will drain the battery in a few weeks to months. It's advised to set a minimum wake-up interval of 3 hours to 24 hours after the device is configured correctly and a node.xml file has been created for the device. ## Channels diff --git a/_addons_bindings/zwave/doc/fibaro/fgk101_2_5.md b/_addons_bindings/zwave/doc/fibaro/fgk101_2_5.md index 40c2273006..b0d7586565 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgk101_2_5.md +++ b/_addons_bindings/zwave/doc/fibaro/fgk101_2_5.md @@ -16,7 +16,7 @@ The device is in the category of *Door*, defining Door sensors. The FGK101 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FGK101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FGK101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -50,6 +50,10 @@ Adding/removing will be confirmed by LED blinking. Fast blinking means that the ### Wakeup Information +The FGK101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + **Waking up the Door/Window Sensor:** FIBARO Door/Window Sensor needs to be woken up to receive information about the new configuration from the controller, like parameters and associations. diff --git a/_addons_bindings/zwave/doc/fibaro/fgk101_3_2.md b/_addons_bindings/zwave/doc/fibaro/fgk101_3_2.md index f48894c8b9..6e936afa5b 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgk101_3_2.md +++ b/_addons_bindings/zwave/doc/fibaro/fgk101_3_2.md @@ -16,12 +16,15 @@ The device is in the category of *Door*, defining Door sensors. The FGK101 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FGK101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FGK101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/381) to improve the documentation. +### Wakeup Information +The FGK101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the FGK101 -: diff --git a/_addons_bindings/zwave/doc/fibaro/fgkf601_0_0.md b/_addons_bindings/zwave/doc/fibaro/fgkf601_0_0.md index 45d018f2c9..a761e79390 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgkf601_0_0.md +++ b/_addons_bindings/zwave/doc/fibaro/fgkf601_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *FGKF601*, manufactured by *[Fibargroup](http:/ The FGKF601 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FGKF601 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FGKF601 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/542) to improve the documentation. +### Wakeup Information +The FGKF601 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the FGKF601 -: diff --git a/_addons_bindings/zwave/doc/fibaro/fgms001_0_0.md b/_addons_bindings/zwave/doc/fibaro/fgms001_0_0.md index 3743b9c4be..afb78315e8 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgms001_0_0.md +++ b/_addons_bindings/zwave/doc/fibaro/fgms001_0_0.md @@ -16,11 +16,46 @@ The device is in the category of *Motion Detector*, defining Motion sensors/dete The FGMS001 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FGMS001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FGMS001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/115) to improve the documentation. +The Fibaro Motion Sensor is a universal Z-Wave multi-sensor. Along with detecting motion the device measures the temperature and light +intensity. + + The sensor has a built-in accelerometer to detect any tampering of the device. The Fibaro Motion Sensor is battery powered device and designed to be installed quckly and easily on any surface. + +### Inclusion Information + +1\) Insert the battery into the Fibaro Motion Sensor. Enclosure lock is +marked with a dot. Make sure the device is located within the direct +range of the main controller. +2\) Set the main controller into the learning mode (see main +controller’s operating manual). +3\) Quickly, triple click the B-button - LED diode will glow blue. +4\) Fibaro Motion Sensor will be detected and included in the Z-Wave +network. +5\) Wait for the main controller to configure the sensor. +6\) If necessary, wake up the Motion Sensor by triple clicking the +B-button. +7\) LED diode will glow blue to confirm the sensor woke up, and then +wait for the main controller to configure the sensor + +### Exclusion Information + +1\) Set the main controller into the exclusion mode (see main +controller’s operating manual). +2\) Quickly, triple click the B-button - LED diode will glow blue. +3\) Fibaro Motion Sensor will be excluded from the Z-Wave +network. + +### Wakeup Information + +The FGMS001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + +Quickly, triple click the B-button - LED diode will glow blue. ## Channels @@ -435,7 +470,7 @@ The following option values may be configured -: | Value | Description | |--------|-------------| | 0 | LED inactive. | -| 1 | LED colour depends on the temperature | +| 1 | LED colour depends on the temperature. | | 2 | Flashlight mode - LED glows in white for 10 seconds. | | 3 | White. | | 4 | Red. | @@ -446,21 +481,21 @@ The following option values may be configured -: | 9 | Magenta. | | 10 | LED colour depends on the temperature | | 11 | Flashlight mode | -| 12 | White. | -| 13 | Red. | -| 14 | Green. | -| 15 | Blue. | -| 16 | Yellow. | -| 17 | Cyan. | -| 18 | Magenta. | +| 12 | White | +| 13 | Red | +| 14 | Green | +| 15 | Blue | +| 16 | Yellow | +| 17 | Cyan | +| 18 | Magenta | | 19 | LED colour depends on the temperature | -| 20 | White. | -| 21 | Red. | -| 22 | Green. | -| 23 | Blue. | -| 24 | Yellow. | -| 25 | Cyan. | -| 26 | Magenta. | +| 20 | White | +| 21 | Red | +| 22 | Green | +| 23 | Blue | +| 24 | Yellow | +| 25 | Cyan | +| 26 | Magenta | The manufacturer defined default value is ```10``` (LED colour depends on the temperature). diff --git a/_addons_bindings/zwave/doc/fibaro/fgms001_3_2.md b/_addons_bindings/zwave/doc/fibaro/fgms001_3_2.md index 182e5b8e85..c9f96cdf52 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgms001_3_2.md +++ b/_addons_bindings/zwave/doc/fibaro/fgms001_3_2.md @@ -16,12 +16,15 @@ The device is in the category of *Motion Detector*, defining Motion sensors/dete The FGMS001 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FGMS001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FGMS001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/328) to improve the documentation. +### Wakeup Information +The FGMS001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the FGMS001 -: diff --git a/_addons_bindings/zwave/doc/fibaro/fgpb101_0_0.md b/_addons_bindings/zwave/doc/fibaro/fgpb101_0_0.md index eb689003a6..c0fa7bc382 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgpb101_0_0.md +++ b/_addons_bindings/zwave/doc/fibaro/fgpb101_0_0.md @@ -8,16 +8,63 @@ title: FGPB101 - ZWave # FGPB101 A real push button (switch) available in several colors. This describes the Z-Wave device *FGPB101*, manufactured by *[Fibargroup](http://www.fibaro.com/)* with the thing type UID of ```fibaro_fgpb101_00_000```. +The device is in the category of *Remote Control*, defining Any portable or hand-held device that controls the status of something, e.g. remote control, keyfob etc.. + ![FGPB101 product image](https://www.cd-jackson.com/zwave_device_uploads/436/436_default.png) The FGPB101 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FGPB101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FGPB101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/436) to improve the documentation. +FIBARO Button is a compact, battery-powered, Z-Wave Plus compatible device. It allows you to control devices through the Z-Wave network and run various scenes defined in FIBARO System. + +Different actions may be triggered with one to five clicks or by holding the button down. In panic mode, each press of the button results in triggering the FIBARO Alarm. + +With its small design and wireless communication, the FIBARO Button can be conveniently mounted on any surface and in any position or location at home, e.g. beside the bed or under the desk. + +Main features of FIBARO Button: + +- Compatible with any Z-Wave or Z-Wave+ Controller +- Supports Z-Wave network Security Mode with AES-128 encryption +- Completely wireless with battery power and Z-Wave communication +- May be installed anywhere in your home +- Extremely easy installation - simply add and put on desired surface +- Many colour variations: black, white, red, green, blue, yellow, orange and brown. + +### Inclusion Information + +Adding (Inclusion) - Z-Wave device learning mode, allowing to add the device to existing Z-Wave network. + +To add the device to the Z-Wave network: + +1. Place the Button within the direct range of your Z-Wave controller. +2. Set the main controller in (Security/non-Security) add mode (see the controller’s manual). +3. Click the Button at least six times. +4. Wait for the adding process to end. +5. Successful adding will be confirmed by the Z-Wave controller’s message. + +### Exclusion Information + +Removing (Exclusion) - Z-Wave device learning mode, allowing to remove the device from existing Z-Wave network. + +To remove the device to the Z-Wave network: + +1. Place the Button within the direct range of your Z-Wave controller. +2. Set the main controller in remove mode (see the controller’s manual). +3. Click the Button at least six times. +4. Wait for the removing process to end. +5. Successful removing will be confirmed by the Z-Wave controller’s message. + +### Wakeup Information + +The FGPB101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + +The Button needs to be woken up to receive information about the new configuration from the controller, like parameters and associations. Click the Button 4 times to wake it up. ## Channels diff --git a/_addons_bindings/zwave/doc/fibaro/fgr222_24_24.md b/_addons_bindings/zwave/doc/fibaro/fgr222_24_24.md index 57ef7a3674..4bfb43a53c 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgr222_24_24.md +++ b/_addons_bindings/zwave/doc/fibaro/fgr222_24_24.md @@ -45,10 +45,6 @@ Manual Z-Wave network inclusion: 2. Set the main controller into the learn mode (see main controllers operating manual). 3. Triple click the B-button or a push button connected to the S1 terminal. -### Wakeup Information - -device has mains power, doesn't sleep. - ## Channels The following table summarises the channels available for the FGR222 -: diff --git a/_addons_bindings/zwave/doc/fibaro/fgrm222_0_0.md b/_addons_bindings/zwave/doc/fibaro/fgrm222_0_0.md index 3cc6c710be..69530fc141 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgrm222_0_0.md +++ b/_addons_bindings/zwave/doc/fibaro/fgrm222_0_0.md @@ -129,38 +129,38 @@ Detailed information on each parameter can be found in the sections below. | Param | Name | Description | |-------|-------|-------------| -| 1 | Local protection | Enables/disables local entry. If activated module stops responding to S1 and S2 push buttons, SCENE ID and association commands will not be sent. Only exception is the B-button. | -| 2 | Radio protection | Enables/disables RF protection. If activated device stops responding to command frames. Configuration and polling still possible. | -| 3 | Reports type | Parameters value shoud be set to 1 if the module operates in Venetian Blind mode. | +| 1 | Local protection | Enables/disables local entry | +| 2 | Radio protection | Enables/disables RF protection | +| 3 | Reports type | Enable Venetian Blind mode | | 10 | Roller Shutter operating modes | | -| 12 | Turning time/ delay time | In Venetian Blind mode (parameter 10 set to 2) the parameter determines time of full turn of the lamellas. In Gate Mode (parameter 10 set to 3 or 4) the parameter defines the delay time after which an open gate starts closing. Type range | -| 13 | Lamellas positioning mode | Parameter influences the lamellas positioning in venetian blind mode (parameter 10 set to 2) | -| 14 | Switch type | parameter settings are relevant for Roller Blind Mode and Venetian Blind Mode (parameter 10 set to 0, 1, 2). | -| 17 | Delay time after S2 | In roller blind mode or venetian blind mode (parameter 10 set to 0, 1, 2) the parameter determines when the Roller Shutter relays are turned off after reaching a limit switch. In Gate Mode (parameter 10 set to 3 or 4) the parameter determines a time perio | +| 12 | Turning time/delay time | Time of full turn of the lamellas. | +| 13 | Lamellas positioning mode | Lamellas positioning in venetian blind mode | +| 14 | Switch type | Parameter settings for Roller and Venetian Blind Mode | +| 17 | Delay time after S2 | Relays turn off time after reaching a limit switch. | | 18 | Motor operation detection | Power threshold to be interpreted as reaching a limit switch. | | 22 | Motor operation time | Time period for the motor to continue operation. | -| 29 | Forced Roller Shutter calibration | Seting the parameter to 1 Roller Shutter enters the calibration mode. Parameter is only only relevant if a Roller Shutter is set to work in positioning mode (parameter 10 set to 1, 2 or 4). | +| 29 | Forced Roller Shutter calibration | Roller Shutter enters the calibration mode. | | 30 | Response to General Alarm | | | 31 | Response to Water Flood Alarm | | | 32 | Response to Smoke, CO, CO2 Alarm | | | 33 | Response to Temperature Alarm | | -| 35 | Managing lamellas in response to alarm | In Venetian Blind Mode (parameter 10 set to 2), the parameter determines how the lamellas will react upon alarm detection. | -| 40 | Power reports | Power level change that will result in new power value report being sent. value is a percentage of the previous report. | +| 35 | Managing lamellas in response to alarm | Lamellas reaction upon alarm detection. | +| 40 | Power reports | Power level change resulting in new power value report | | 42 | Periodic power or energy reports | Time to the next report. Value of 0 means the reports are turned off. | -| 43 | Energy reports | Energy level change which will result in new energy value report being sent. Value of 0 means the reports are turned off. | -| 44 | Self-measurement | Enables/disables to include the power and energy used by itself in reports to main controller. | -| 50 | Scenes/ Associations activation | Parameter determines whether scenes or associations are activated by the switch keys. | +| 43 | Energy reports | Energy level change resulting in new energy value report | +| 44 | Self-measurement | Enables/disables power and energy report used by itself | +| 50 | Scenes/Associations activation | Determine whether scenes or associations are activated | ### Parameter 1: Local protection +Enables/disables local entry Enables/disables local entry. If activated module stops responding to S1 and S2 push buttons, SCENE ID and association commands will not be sent. Only exception is the B-button. - The following option values may be configured -: | Value | Description | |--------|-------------| | 0 | No protection. Roller Shutter responds to push buttons | -| 2 | Local protection active. Roller Shutter does not respond to push butto | +| 2 | Local protection active | The manufacturer defined default value is ```255```. @@ -169,14 +169,14 @@ This parameter has the configuration ID ```config_1_1``` and is of type ```INTEG ### Parameter 2: Radio protection +Enables/disables RF protection Enables/disables RF protection. If activated device stops responding to command frames. Configuration and polling still possible. - The following option values may be configured -: | Value | Description | |--------|-------------| | 0 | No protection. Roller Shutter responds to command frames. | -| 1 | RF Protection active. Roller Shutter does not respond to the Z-Wave co | +| 1 | RF Protection active. | The manufacturer defined default value is ```0``` (No protection. Roller Shutter responds to command frames.). @@ -185,16 +185,16 @@ This parameter has the configuration ID ```config_2_1``` and is of type ```INTEG ### Parameter 3: Reports type +Enable Venetian Blind mode Parameters value shoud be set to 1 if the module operates in Venetian Blind mode. - The following option values may be configured -: | Value | Description | |--------|-------------| -| 0 | Blind position reports sent to the main controller using Z-Wave Comman | -| 1 | Blind position reports sent to the main controller using Fibar Command | +| 0 | Blind position reports sent using Z-Wave Commands | +| 1 | Blind position reports sent using Fibaro Commands. | -The manufacturer defined default value is ```0``` (Blind position reports sent to the main controller using Z-Wave Comman). +The manufacturer defined default value is ```0``` (Blind position reports sent using Z-Wave Commands). This parameter has the configuration ID ```config_3_1``` and is of type ```INTEGER```. @@ -218,10 +218,10 @@ The manufacturer defined default value is ```1``` (Roller Blind Mode, with posit This parameter has the configuration ID ```config_10_1``` and is of type ```INTEGER```. -### Parameter 12: Turning time/ delay time - -In Venetian Blind mode (parameter 10 set to 2) the parameter determines time of full turn of the lamellas. In Gate Mode (parameter 10 set to 3 or 4) the parameter defines the delay time after which an open gate starts closing. Type range +### Parameter 12: Turning time/delay time +Time of full turn of the lamellas. +In Venetian Blind mode (parameter 10 set to 2) the parameter determines time of full turn of the lamellas. In Gate Mode (parameter 10 set to 3 or 4) the parameter defines the delay time after which an open gate starts closing. Values in the range 0 to 65535 may be set. The manufacturer defined default value is ```150```. @@ -231,8 +231,8 @@ This parameter has the configuration ID ```config_12_2``` and is of type ```INTE ### Parameter 13: Lamellas positioning mode +Lamellas positioning in venetian blind mode Parameter influences the lamellas positioning in venetian blind mode (parameter 10 set to 2) - The following option values may be configured -: | Value | Description | @@ -248,8 +248,8 @@ This parameter has the configuration ID ```config_13_1``` and is of type ```INTE ### Parameter 14: Switch type -parameter settings are relevant for Roller Blind Mode and Venetian Blind Mode (parameter 10 set to 0, 1, 2). - +Parameter settings for Roller and Venetian Blind Mode +Parameter settings are relevant for Roller Blind Mode and Venetian Blind Mode (parameter 10 set to 0, 1, 2). The following option values may be configured -: | Value | Description | @@ -265,8 +265,8 @@ This parameter has the configuration ID ```config_14_1``` and is of type ```INTE ### Parameter 17: Delay time after S2 -In roller blind mode or venetian blind mode (parameter 10 set to 0, 1, 2) the parameter determines when the Roller Shutter relays are turned off after reaching a limit switch. In Gate Mode (parameter 10 set to 3 or 4) the parameter determines a time perio - +Relays turn off time after reaching a limit switch. +In roller blind mode or venetian blind mode (parameter 10 set to 0, 1, 2) the parameter determines when the Roller Shutter relays are turned off after reaching a limit switch. In Gate Mode (parameter 10 set to 3 or 4) the parameter determines a time period. Values in the range 0 to 255 may be set. The manufacturer defined default value is ```10```. @@ -298,8 +298,8 @@ This parameter has the configuration ID ```config_22_2``` and is of type ```INTE ### Parameter 29: Forced Roller Shutter calibration +Roller Shutter enters the calibration mode. Seting the parameter to 1 Roller Shutter enters the calibration mode. Parameter is only only relevant if a Roller Shutter is set to work in positioning mode (parameter 10 set to 1, 2 or 4). - The following option values may be configured -: | Value | Description | @@ -382,8 +382,8 @@ This parameter has the configuration ID ```config_33_1``` and is of type ```INTE ### Parameter 35: Managing lamellas in response to alarm +Lamellas reaction upon alarm detection. In Venetian Blind Mode (parameter 10 set to 2), the parameter determines how the lamellas will react upon alarm detection. - The following option values may be configured -: | Value | Description | @@ -398,8 +398,8 @@ This parameter has the configuration ID ```config_35_1``` and is of type ```INTE ### Parameter 40: Power reports -Power level change that will result in new power value report being sent. value is a percentage of the previous report. - +Power level change resulting in new power value report +Power level change that will result in new power value report being sent. Value is a percentage of the previous report. Values in the range 0 to 100 may be set. The manufacturer defined default value is ```10```. @@ -420,8 +420,8 @@ This parameter has the configuration ID ```config_42_2``` and is of type ```INTE ### Parameter 43: Energy reports +Energy level change resulting in new energy value report Energy level change which will result in new energy value report being sent. Value of 0 means the reports are turned off. - Values in the range -126 to 127 may be set. The manufacturer defined default value is ```10```. @@ -431,8 +431,8 @@ This parameter has the configuration ID ```config_43_1``` and is of type ```INTE ### Parameter 44: Self-measurement +Enables/disables power and energy report used by itself Enables/disables to include the power and energy used by itself in reports to main controller. - The following option values may be configured -: | Value | Description | @@ -445,10 +445,10 @@ The manufacturer defined default value is ```0``` (Disabled). This parameter has the configuration ID ```config_44_1``` and is of type ```INTEGER```. -### Parameter 50: Scenes/ Associations activation +### Parameter 50: Scenes/Associations activation +Determine whether scenes or associations are activated Parameter determines whether scenes or associations are activated by the switch keys. - The following option values may be configured -: | Value | Description | diff --git a/_addons_bindings/zwave/doc/fibaro/fgs212_0_0.md b/_addons_bindings/zwave/doc/fibaro/fgs212_0_0.md index 354e5951a7..3da731070d 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgs212_0_0.md +++ b/_addons_bindings/zwave/doc/fibaro/fgs212_0_0.md @@ -17,7 +17,45 @@ The FGS212 supports routing. This allows the device to communicate using other r ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/114) to improve the documentation. +Remotely Controlled Relay Switch of Fibaro System is designed to operate in a wall switch box or in locations where the control of an electric device is needed. + +### Inclusion Information + +Fibaro Switch must be placed within the range of Home Center +controller, as adding mode requires direct communication with the +controller. + +Find key no. 1 which allows to switch circuit 1 on, in accordance +with the diagram +During the installation it is recommended to use a +momentary key connected to S1. + +Add Fibaro Switch to the network by pushing three times key no. 1 +or push-button B located inside the housing of the device. For +toggle switch perform 3 position changes. + +The controller indicates when the device is correctly added to the +network. + +**CAUTION** +Fibaro Switch cancels the "learning" mode after +key no. 1 is pressed once. Therefore, pressing key +no. 1 four times will not add the devices to the +network. The same applies to push-button B. + +### Exclusion Information + +Find key no. 1 which allows to switch circuit 1 on, in accordance +with the diagram +During removing it is recommended to use a +momentary key connected to S1. + +Remove Fibaro Switch from the network by pushing three times key no. 1 +or push-button B located inside the housing of the device. For +toggle switch perform 3 position changes. + +The controller indicates when the device is correctly removed from the +network. ## Channels diff --git a/_addons_bindings/zwave/doc/fibaro/fgsd002_0_0.md b/_addons_bindings/zwave/doc/fibaro/fgsd002_0_0.md index 10e27cea34..d71d16b3ca 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgsd002_0_0.md +++ b/_addons_bindings/zwave/doc/fibaro/fgsd002_0_0.md @@ -15,11 +15,33 @@ The device is in the category of *Smoke Detector*, defining Smoke detectors. The FGSD002 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FGSD002 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FGSD002 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/129) to improve the documentation. +The Fibaro Smoke Sensor is a universal, optical Z-Wave smoke detector. Fire alarm is signaled by sound, visual indicator blinking and by sending Z-Wave alarm and control commands + +### Inclusion Information + +1. Install the battery. Visual indicator will signal the Z-Wave network inclusion status (red - device ready for inclusion, green - device included, remove firstly - see p. II). +2. Make sure the device is located within direct range of the Z-Wave controller. +3. Set the main controller into the learning mode (see main controller’s operating manual). +4. Quickly, triple click the B-button, located on Fibaro Smoke Sensor’s casing. +5. Fibaro Smoke Sensor will be detected and included in the Z-Wave network + +### Exclusion Information + +1. Make sure the sensor is connected to battery. +2. Set the main controller into the learning mode (see main controller’s operating manual) +3. Quickly, triple click the B-button, located on Fibaro Smoke Sensor’s casing. + +### Wakeup Information + +The FGSD002 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + +Click the B-button once. ## Channels @@ -142,7 +164,7 @@ Detailed information on each parameter can be found in the sections below. | 10 | Configuration of control frames in BASIC command class | This parameter defines which frames will be sent ... | | 11 | BASIC ON frame value | BASIC ON frame is sent in case of smoke presence detection ... | | 12 | BASIC OFF frame value | BASIC OFF frame is sent in case of FIRE ALARM cancellation. | -| 13 | Alarm broadcast | A value other than 0 means that alarms are being sent in ... | +| 13 | Alarm broadcast | A value other than 0 means that alarms are being ... | | 20 | Temperature report interval | Time interval between consecutive temperature reports. | | 21 | Temperature report hysteresis | The temperature report will only be sent if there is a difference ... | | 30 | Temperature threshold | Temperature threshold for activating alarms | @@ -212,7 +234,7 @@ The following option values may be configured -: | 2 | Exceeding temperature threshold notification enabled | | 3 | Enclosure opening notification enabled + | | 4 | Lack of Z-Wave range notification | -| 5 | Enclosure opening notification enabled + | +| 5 | Enclosure opening notification enabled and | | 6 | Exceeding temperature threshold notification enabled + | | 7 | Enclosure opening notification enabled + | @@ -236,7 +258,7 @@ The following option values may be configured -: | 4 | Lack of Z-Wave range notification | | 5 | Enclosure opening notification enabled + | | 6 | Exceeding temperature threshold notification enabled + | -| 7 | Enclosure opening notification enabled + | +| 7 | Enclosure opening notification enabled and | The manufacturer defined default value is ```0``` (All notifications disabled). @@ -284,16 +306,16 @@ This parameter has the configuration ID ```config_12_2``` and is of type ```INTE ### Parameter 13: Alarm broadcast -A value other than 0 means that alarms are being sent in ... -broadcast mode, i.e. to all devices within a Fibaro Smoke Sensor’s range +A value other than 0 means that alarms are being ... + ... sent in broadcast mode, i.e. to all devices within a Fibaro Smoke Sensor’s range The following option values may be configured -: | Value | Description | |--------|-------------| | 0 | broadcast inactive | | 1 | FIRE ALARM broadcast (2-nd and 4-th Association Group) ... | -| 2 | FIRE ALARM broadcast (2-nd and 4-th Association Group) ... | -| 3 | FIRE ALARM broadcast (2-nd and 4-th Association Group) ... | +| 2 | FIRE ALARM broadcast (2nd and 4th Association Group) ... | +| 3 | FIRE ALARM broadcast (2nd and 4-th Association Group) ... | The manufacturer defined default value is ```0``` (broadcast inactive). diff --git a/_addons_bindings/zwave/doc/fibaro/fgss001_0_0.md b/_addons_bindings/zwave/doc/fibaro/fgss001_0_0.md index aed9f489d1..af4ea0c748 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgss001_0_0.md +++ b/_addons_bindings/zwave/doc/fibaro/fgss001_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Smoke Detector*, defining Smoke detectors. The FGSS001 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FGSS001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FGSS001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/134) to improve the documentation. +### Wakeup Information +The FGSS001 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the FGSS001 -: diff --git a/_addons_bindings/zwave/doc/fibaro/fgt001_0_0.md b/_addons_bindings/zwave/doc/fibaro/fgt001_0_0.md index 61f9676095..fb50451e21 100644 --- a/_addons_bindings/zwave/doc/fibaro/fgt001_0_0.md +++ b/_addons_bindings/zwave/doc/fibaro/fgt001_0_0.md @@ -62,10 +62,6 @@ To remove the device from the Z-Wave network: 6\. Successful removing will be confirmed by the Z-Wave controller. -### Wakeup Information - -FIBARO Heat Controller is a FLiRS device. The FLiRS device alternates between sleep mode and a partially awake mode in which it is listening beam signal. When device receives this beam, it immediately fully wakes up and then communicates with the controller or other Z-Wave device. - ## Channels The following table summarises the channels available for the FGT-001 -: diff --git a/_addons_bindings/zwave/doc/fireangle/zst630_0_0.md b/_addons_bindings/zwave/doc/fireangle/zst630_0_0.md index 249064005f..3587999821 100644 --- a/_addons_bindings/zwave/doc/fireangle/zst630_0_0.md +++ b/_addons_bindings/zwave/doc/fireangle/zst630_0_0.md @@ -12,12 +12,15 @@ The device is in the category of *Smoke Detector*, defining Smoke detectors. The ZST-630 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZST-630 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZST-630 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/733) to improve the documentation. +### Wakeup Information +The ZST-630 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZST-630 -: diff --git a/_addons_bindings/zwave/doc/forest/shuttlesl_0_0.md b/_addons_bindings/zwave/doc/forest/shuttlesl_0_0.md index 6d6f1686ec..b7d8da07a8 100644 --- a/_addons_bindings/zwave/doc/forest/shuttlesl_0_0.md +++ b/_addons_bindings/zwave/doc/forest/shuttlesl_0_0.md @@ -31,10 +31,6 @@ To exclude, set your main controller into exclude mode. Press configuration butt You can also reset the device, but only use this if your main controller is not operable. For reset, press the config button 25 times and confirm by pressing the button once more for 4 seconds until the led blinks 3 times and goes off. -### Wakeup Information - -Not specified - ## Channels The following table summarises the channels available for the Shuttle S/L -: diff --git a/_addons_bindings/zwave/doc/fortrezz/wv01_0_0.md b/_addons_bindings/zwave/doc/fortrezz/wv01_0_0.md index d6b64fcde0..14d6cdd6df 100644 --- a/_addons_bindings/zwave/doc/fortrezz/wv01_0_0.md +++ b/_addons_bindings/zwave/doc/fortrezz/wv01_0_0.md @@ -17,7 +17,9 @@ The WV-01 supports routing. This allows the device to communicate using other ro ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/368) to improve the documentation. +Fortrezz WV-01 Wireless Z-Wave Water Valve is a patented, wireless water detection and automatic water shut-off system that works as an automatic valve for your home's main water supply line and can easily be installed by a certified professional plumber. + +When used in a Z-Wave home automation network, the smart valve can be used along with Z-Wave water alarm sensors to reduce or eliminate water damage caused by leaky pipes or faulty appliances. It can also be used in conjunction with remotely installed flood sensors to shut off the main water supply in case of water leakage. ## Channels diff --git a/_addons_bindings/zwave/doc/fortrezz/wwa02_0_0.md b/_addons_bindings/zwave/doc/fortrezz/wwa02_0_0.md index 7c660bcdec..ef914965b2 100644 --- a/_addons_bindings/zwave/doc/fortrezz/wwa02_0_0.md +++ b/_addons_bindings/zwave/doc/fortrezz/wwa02_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Sensor*, defining Device used to measure somet The WWA-01 / WWA-02 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The WWA-01 / WWA-02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The WWA-01 / WWA-02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/222) to improve the documentation. +### Wakeup Information +The WWA-01 / WWA-02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the WWA-01 / WWA-02 -: diff --git a/_addons_bindings/zwave/doc/ge/14318_0_0.md b/_addons_bindings/zwave/doc/ge/14318_0_0.md index 2c8a5765a9..21c9dcef12 100644 --- a/_addons_bindings/zwave/doc/ge/14318_0_0.md +++ b/_addons_bindings/zwave/doc/ge/14318_0_0.md @@ -8,12 +8,15 @@ title: Jasco 14318 - ZWave # Jasco 14318 Jasco 3-way Light Switch This describes the Z-Wave device *Jasco 14318*, manufactured by *Jasco Products* with the thing type UID of ```ge_14318_00_000```. -The Jasco 14318 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Jasco 14318 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/717) to improve the documentation. +### Wakeup Information +The Jasco 14318 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the Jasco 14318 -: diff --git a/_addons_bindings/zwave/doc/ge/ge14299_0_0.md b/_addons_bindings/zwave/doc/ge/ge14299_0_0.md new file mode 100644 index 0000000000..3f068ab9b0 --- /dev/null +++ b/_addons_bindings/zwave/doc/ge/ge14299_0_0.md @@ -0,0 +1,139 @@ +--- +layout: documentation +title: GE/Jasco 14299 - ZWave +--- + +{% include base.html %} + +# GE/Jasco 14299 GE/Jasco In-Wall 1000W Incandescent Smart Dimmer +This describes the Z-Wave device *GE/Jasco 14299*, manufactured by *Jasco Products* with the thing type UID of ```ge_ge14299_00_000```. + +The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. + +![GE/Jasco 14299 product image](https://www.cd-jackson.com/zwave_device_uploads/862/862_default.jpg) + + +The GE/Jasco 14299 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. + +## Overview + +**Basic operation** + +The connected light can be turned ON/OFF and adjust dim levels in two ways: + +1. Manually from the front panel of the In-Wall Dimmer. +2. Remotely with a Z-Wave Controller . + +**Manual control** + +The Front Panel Rocker Dimmer allows the user to turn ON/OFF the connected fixture. + +1. To turn the connected fixture ON: press and release the top of the rocker. +2. To turn the connected fixture OFF: press and release the bottom of the rocker. + +**Adjust dim level** + +1. To increase brightness: press and hold the top of the rocker. +2. To decrease brightness: press and hold the bottom of the rocker. + +**Disable / Enable LED** + +1. Press UP three (3) times then quickly press and release DOWN one (1) time. +2. Repeat to disable/enable LED. + +**This device supports Association Command Class (3 Groups)** + +1. Association Group 1 supports Lifeline, Switch Multilevel Report +2. Association Group 2 supports Basic Set and is controlled by pressing the On or Off button with the local load +3. Association Group 3 supports Basic Set and is controlled by double pressing the On or Off button +4. Each Association Group supports 5 total nodes + +### Inclusion Information + +**Adding your device to a Z-Wave network** + +1. Follow the instructions for your Z-Wave certified controller to add a device to the Z-Wave network. +2. Once the controller is ready to add your device, press and release the top or bottom of the wireless smart switch (rocker) to add it in the network. + +Please reference the controller's manual for instructions. + +### Exclusion Information + +**To remove and reset the device** + +1. Follow the instructions for your Z-Wave certified controller to remove a device from the Z-Wave network. +2. Once the controller is ready to remove your device, press and release the top or bottom of the wireless smart dimmer (rocker) to remove it from the network. + +**To return your switch to factory defaults:** + +Quickly press ON (Top) button three (3) times then immediately press the OFF (Bottom) button three (3) times. The LED will flash ON/OFF 5 times when completed successfully. Note: This should only be used in the event your network’s primary controller is missing or otherwise inoperable. + +### Wakeup Information + +The GE/Jasco 14299 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +## Channels + +The following table summarises the channels available for the GE/Jasco 14299 -: + +| Channel | Channel Id | Category | Item Type | +|---------|------------|----------|-----------| +| Dimmer | switch_dimmer | DimmableLight | Dimmer | +| Scene Number | scene_number | | Number | + +### Dimmer + +The brightness channel allows to control the brightness of a light. + It is also possible to switch the light on and off. + +The ```switch_dimmer``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. + +### Scene Number + +Triggers when a scene button is pressed. + +The ```scene_number``` channel supports the ```Number``` item. + + + +## Device Configuration + +The device has no configuration parameters configured. + +## Association Groups + +Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic. + +The device does not support associations. +## Technical Information + +### Endpoints + +#### Endpoint 0 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_SWITCH_MULTILEVEL_V2| | +| COMMAND_CLASS_SWITCH_ALL_V1| | +| COMMAND_CLASS_SCENE_ACTIVATION_V1| | +| COMMAND_CLASS_SCENE_ACTUATOR_CONF_V1| | +| COMMAND_CLASS_CRC_16_ENCAP_V1| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| | +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_CONFIGURATION_V1| | +| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| | +| COMMAND_CLASS_POWERLEVEL_V1| | +| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_VERSION_V2| | + +### Documentation Links + +* [GE Jasco In-Wall 1000W Incandescant Smart Dimmer Manual](https://www.cd-jackson.com/zwave_device_uploads/862/14299-QSG-v2.pdf) + +--- + +Did you spot an error in the above definition or want to improve the content? +You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/862). diff --git a/_addons_bindings/zwave/doc/ge/ge14321_0_0.md b/_addons_bindings/zwave/doc/ge/ge14321_0_0.md index 22b254bc9b..9793faafb0 100644 --- a/_addons_bindings/zwave/doc/ge/ge14321_0_0.md +++ b/_addons_bindings/zwave/doc/ge/ge14321_0_0.md @@ -172,6 +172,7 @@ The device does not support associations. ### Documentation Links * [User Manual](https://www.cd-jackson.com/zwave_device_uploads/583/GE-45613-manual.pdf) +* [GE Jasco In-Wall 1000W Incandescant Smart Dimmer Manual](https://www.cd-jackson.com/zwave_device_uploads/583/14299-QSG-v2.pdf) --- diff --git a/_addons_bindings/zwave/doc/ge/ge28167zw3104_0_0.md b/_addons_bindings/zwave/doc/ge/ge28167zw3104_0_0.md index 8d1fc556cc..7b681178f4 100644 --- a/_addons_bindings/zwave/doc/ge/ge28167zw3104_0_0.md +++ b/_addons_bindings/zwave/doc/ge/ge28167zw3104_0_0.md @@ -8,12 +8,15 @@ title: GE 28167 (ZW3104) - ZWave # GE 28167 (ZW3104) Plug-In Smart Dimmer This describes the Z-Wave device *GE 28167 (ZW3104)*, manufactured by *Jasco Products* with the thing type UID of ```ge_ge28167zw3104_00_000```. -The GE 28167 (ZW3104) does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The GE 28167 (ZW3104) does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/577) to improve the documentation. +### Wakeup Information +The GE 28167 (ZW3104) does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the GE 28167 (ZW3104) -: diff --git a/_addons_bindings/zwave/doc/ge/motiondimmerswitch_0_0.md b/_addons_bindings/zwave/doc/ge/motiondimmerswitch_0_0.md new file mode 100644 index 0000000000..a491113b90 --- /dev/null +++ b/_addons_bindings/zwave/doc/ge/motiondimmerswitch_0_0.md @@ -0,0 +1,194 @@ +--- +layout: documentation +title: Motion Dimmer Switch - ZWave +--- + +{% include base.html %} + +# Motion Dimmer Switch Motion Dimmer Switch +This describes the Z-Wave device *Motion Dimmer Switch*, manufactured by *Jasco Products* with the thing type UID of ```ge_motiondimmerswitch_00_000```. + +The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. + +![Motion Dimmer Switch product image](https://www.cd-jackson.com/zwave_device_uploads/840/840_default.png) + + +The Motion Dimmer Switch supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. + +## Overview + +#### Description + +Set your life in motion with the Z-Wave Plus In-Wall Smart Motion Switch. This energy-efficient sensor works with your home’s gateway to wirelessly trigger scenes and send alerts to your smartphone or tablet whenever motion is has turned lights on or off. + +Three different modes offer the best lighting option for you: occupancy, vacancy and manual. In occupancy mode, the lights will automatically turn on when you enter the room and automatically turn off once you’ve left (customizable between 5 seconds and 30 minutes). + +In vacancy mode, the lights are turned on manually and will turn off automatically after a preset amount of time. In manual mode, the lights will function as a normal light switch and manually turn on and off. Along with conveniently saving you time and energy costs, the smart motion dimmer can replace any existing light switch in your home, and can be used in 3- and 4-way applications. + +You may also coordinate the switch with your household decor with the included white and light almond buttons. Experience the comfort of automation in your life when you come home to the Z-Wave Plus In Wall Smart Motion Switch. + +#### Features + +- Wirelessly trigger scenes and send alerts when motion detection has turned lights on or off +- Remotely monitor with any mobile device (Requires Z-Wave gateway or controller) +- Compatible with all certified Z-Wave devices +- Requires in-wall installation with hard-wired connections - neutral wire required +- Can be used in 3- and 4-way applications +- Works with all dimmable LED, CFL, halogen and incandescent bulbs +- Multiple operation modes: Occupancy - auto ON/auto OFF, Vacancy - manual ON/auto OFF, Manual - manual ON/OFF +- Built-in timer lets you set length of time light stays on after motion ceases - from 5 seconds to 30 minutes +- 3 sensitivity levels - low, medium, high +- Includes white and light almond paddles +- Indoor use only + +#### Technical Specifications + +- Specification Value Max Load 600W Incandescent +- 150W Dimmable Power 120VAC, 60Hz +- Operating Temp. Rge 32-104°F (0-40°C) +- Signal Frequency 908.4/916MHz +- Wireless Range Up to 150 feet + +### Inclusion Information + +Adding your device to a Z-Wave network + +1. Follow the instructions for your Z-Wave certified controller to add the smart dimmer to the Z-Wave network. +2. Once the controller is ready to add your smart dimmer, press and release the top or bottom button on the smart dimmer to include it in the network. + +To return to factory defaults + +Press and release the top button ten times within 5 seconds. The LED will flash 3 times quickly confirming change. + +### Exclusion Information + +To remove and reset the device + +1. Follow the instructions for your Z-Wave certified controller to remove a device from the Z-Wave network. +2. Once the controller is ready to remove your device, press and release the top button on the smart dimmer to remove it from the network. + +To return to factory defaults + +Press and release the top button ten times within 5 seconds. The LED will flash 3 times quickly confirming change. + +## Channels + +The following table summarises the channels available for the Motion Dimmer Switch -: + +| Channel | Channel Id | Category | Item Type | +|---------|------------|----------|-----------| +| Dimmer | switch_dimmer | DimmableLight | Dimmer | +| Scene Number | scene_number | | Number | +| Alarm (burglar) | alarm_burglar | Door | Switch | +| Dimmer 1 | switch_dimmer1 | DimmableLight | Dimmer | +| Alarm (burglar) 2 | alarm_burglar2 | Door | Switch | + +### Dimmer + +The brightness channel allows to control the brightness of a light. + It is also possible to switch the light on and off. + +The ```switch_dimmer``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. + +### Scene Number + +Triggers when a scene button is pressed. + +The ```scene_number``` channel supports the ```Number``` item. + +### Alarm (burglar) + +Indicates if the burglar alarm is triggered. + +The ```alarm_burglar``` channel supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device. + +The following state translation is provided for this channel to the ```Switch``` item type -: + +| Value | Label | +|-------|-----------| +| OFF | Ok | +| ON | Alarm | + +### Dimmer 1 + +The brightness channel allows to control the brightness of a light. + It is also possible to switch the light on and off. + +The ```switch_dimmer1``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. + +### Alarm (burglar) 2 + +Indicates if the burglar alarm is triggered. + +The ```alarm_burglar2``` channel supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device. + +The following state translation is provided for this channel to the ```Switch``` item type -: + +| Value | Label | +|-------|-----------| +| OFF | Ok | +| ON | Alarm | + + + +## Device Configuration + +The device has no configuration parameters configured. + +## Association Groups + +Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic. + +The device does not support associations. +## Technical Information + +### Endpoints + +#### Endpoint 0 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_NO_OPERATION_V1| | +| COMMAND_CLASS_BASIC_V1| | +| COMMAND_CLASS_SWITCH_MULTILEVEL_V2| Linked to BASIC| +| COMMAND_CLASS_SWITCH_ALL_V1| | +| COMMAND_CLASS_SCENE_ACTIVATION_V1| | +| COMMAND_CLASS_SCENE_ACTUATOR_CONF_V1| | +| COMMAND_CLASS_CRC_16_ENCAP_V1| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| | +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_MULTI_CHANNEL_V2| | +| COMMAND_CLASS_CONFIGURATION_V1| | +| COMMAND_CLASS_ALARM_V4| | +| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| | +| COMMAND_CLASS_POWERLEVEL_V1| | +| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_VERSION_V2| | +| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | +#### Endpoint 1 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_SWITCH_MULTILEVEL_V2| Linked to BASIC| +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +#### Endpoint 2 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_ALARM_V4| | + +### Documentation Links + +* [Manual](https://www.cd-jackson.com/zwave_device_uploads/840/GE-Jasco-26933-EnFrSp-v1-3.pdf) + +--- + +Did you spot an error in the above definition or want to improve the content? +You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/840). diff --git a/_addons_bindings/zwave/doc/ge/smartdoorsensor_0_0.md b/_addons_bindings/zwave/doc/ge/smartdoorsensor_0_0.md index a0ceb37b06..88ed3fe87e 100644 --- a/_addons_bindings/zwave/doc/ge/smartdoorsensor_0_0.md +++ b/_addons_bindings/zwave/doc/ge/smartdoorsensor_0_0.md @@ -8,15 +8,30 @@ title: 32563 - ZWave # 32563 Smart Door Sensor This describes the Z-Wave device *32563*, manufactured by *Jasco Products* with the thing type UID of ```ge_smartdoorsensor_00_000```. +The device is in the category of *Sensor*, defining Device used to measure something. + ![32563 product image](https://www.cd-jackson.com/zwave_device_uploads/504/504_default.png) The 32563 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The 32563 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The 32563 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview +#### Description + +Whether you’re coming or going, your home is ready when you are with the Z-Wave Smart Door Sensor. Not only does the Smart Door Sensor efficiently eliminate household tasks as you go about your day, but remote monitoring allows you to feel secure once you’ve left home. By simply opening or closing your door, the sensor uses Z-Wave technology to wirelessly trigger scenes throughout your home. From your mobile device, you’re able to schedule lights to turn on as soon as you walk in and be notified of activity while you’re away. Simple installation uses your door’s existing hinge and pin, making setup a breeze. The sensor is discreetly designed to blend subtly into the frame of the door, adding the convenience of the Smart Door Sensor to your home without distracting from your household decor. Color-matching kits are also available, with options including white, dark brown and a paintable finish. + +#### Features + +- Works on all standard doors using your existing hinge +- Reversible for right and left door openings +- Adjusts to fit door trim +- Compatible with hinge pins up to 5/16" in diameter +- CR2 battery included (battery lasts up to 2 years) +- Color matching kits available + ### Inclusion Information 1. Follow the instructions for your Z-Wave certified controller to include the device to the Z-Wave network. @@ -31,6 +46,10 @@ You may wish to reset all of your Hinge Pin Smart Door Sensor's settings to thei ### Wakeup Information +The 32563 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + 1. Press and hold the Z-wave Button for 6 seconds. It will be wake up and send “Wake Up Notification CC “ to HUB. 2. It will sleep after timeout for 10 seconds, or sleep right away when received the “Wake Up No More Information CC”. @@ -125,17 +144,17 @@ Association groups allow the device to send unsolicited reports to the controlle The 32563 supports 3 association groups. -### Group 1: 1 +### Group 1: Lifeline -Z-Wave Plus Lifeline +Lifeline This group supports 5 nodes. -### Group 2: 2 +### Group 2: Control For Control This group supports 5 nodes. -### Group 3: 3 +### Group 3: Control For Control This group supports 5 nodes. diff --git a/_addons_bindings/zwave/doc/ge/zw4002_0_0.md b/_addons_bindings/zwave/doc/ge/zw4002_0_0.md index 6e9a661667..48e89492c1 100644 --- a/_addons_bindings/zwave/doc/ge/zw4002_0_0.md +++ b/_addons_bindings/zwave/doc/ge/zw4002_0_0.md @@ -50,10 +50,6 @@ Once the controller is ready to include your device, press and release the top o Tap up or down -### Wakeup Information - -Tap up or down - ## Channels The following table summarises the channels available for the ZW4002 -: diff --git a/_addons_bindings/zwave/doc/ge/zw6302_0_0.md b/_addons_bindings/zwave/doc/ge/zw6302_0_0.md index fda9fda7cf..f55d8e0feb 100644 --- a/_addons_bindings/zwave/doc/ge/zw6302_0_0.md +++ b/_addons_bindings/zwave/doc/ge/zw6302_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Motion Detector*, defining Motion sensors/dete The ZW6302 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZW6302 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZW6302 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/447) to improve the documentation. +### Wakeup Information +The ZW6302 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZW6302 -: diff --git a/_addons_bindings/zwave/doc/goodway/78008_0_0.md b/_addons_bindings/zwave/doc/goodway/78008_0_0.md index ef29993ebc..6922ecd2f9 100644 --- a/_addons_bindings/zwave/doc/goodway/78008_0_0.md +++ b/_addons_bindings/zwave/doc/goodway/78008_0_0.md @@ -39,10 +39,6 @@ can include 2 extern sensors 3\. The device is logged off -### Wakeup Information - -The Dorr/Window sensor stays in sleep mode for the majority of time. It can be woken up at specified intervals by setting WAKE\_UP\_INTERVAL\_SET command. - ## Channels The following table summarises the channels available for the 78008 -: diff --git a/_addons_bindings/zwave/doc/graber/csz1_0_0.md b/_addons_bindings/zwave/doc/graber/csz1_0_0.md index 74ef21fcc4..6de7d0732d 100644 --- a/_addons_bindings/zwave/doc/graber/csz1_0_0.md +++ b/_addons_bindings/zwave/doc/graber/csz1_0_0.md @@ -25,10 +25,6 @@ See http://products.z-wavealliance.org/products/1749 1. Put Primary Controller into Exclusion Mode 2. Press and Hold Shade Programming Button for >2 seconds -### Wakeup Information - -The Wakeup command class should be configured by a hub when the remote is joined to a Z-Wave network. A WAKE\_UP\_INTERVAL\_SET command should configure the NodeID at a minimum. The Wakeup interval can be configured to any value from 6 minutes to 25 hours. Recommendation is to leave the interval at the default of 12 hours to maximize battery life. The remote will wake up every WakeUpInterval and send a WakeUp Notification command as well as a battery report to the NodeID assigned with the Interval Set command. The WakeUp Notification will be sent within a few minutes of power being applied to the remote and then once every Wake Up Interval. A Wakeup Interval Capabilities command will inform the hub of the default, minimum, maximum and step size of the Wake Up interval. - ## Channels The following table summarises the channels available for the CSZ1 -: diff --git a/_addons_bindings/zwave/doc/hank/dws01_0_0.md b/_addons_bindings/zwave/doc/hank/dws01_0_0.md index d0f3d6fbf1..22a426b3f1 100644 --- a/_addons_bindings/zwave/doc/hank/dws01_0_0.md +++ b/_addons_bindings/zwave/doc/hank/dws01_0_0.md @@ -11,7 +11,7 @@ This describes the Z-Wave device *DWS01*, manufactured by *[Hank](http://www.han ![DWS01 product image](https://www.cd-jackson.com/zwave_device_uploads/663/663_default.jpg) -The DWS01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DWS01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -19,6 +19,11 @@ Unit is labeled with HKZW-DWS01 But, also sold as "MONOPRICE Door and Window Sensor P/N 24259" +### Wakeup Information + +The DWS01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DWS01 -: diff --git a/_addons_bindings/zwave/doc/hank/hkzwfld01_0_0.md b/_addons_bindings/zwave/doc/hank/hkzwfld01_0_0.md index 7e9d96eaa2..f93289ef72 100644 --- a/_addons_bindings/zwave/doc/hank/hkzwfld01_0_0.md +++ b/_addons_bindings/zwave/doc/hank/hkzwfld01_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet The HKZW_FLD01 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HKZW_FLD01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HKZW_FLD01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -73,6 +73,10 @@ Remove Flood Sensor into Z-Wave Network: ### Wakeup Information +The HKZW_FLD01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Defining a time period by which the flood Sensor sends a wake up notification command frame to communicate with the assigned device, update parameters, update software detecs battery level. Wake up interval set to 0 disables the sending wake up notification command, in such configuration it is needed manually wake the device up by press the Z-button. diff --git a/_addons_bindings/zwave/doc/hank/hkzwms01_0_0.md b/_addons_bindings/zwave/doc/hank/hkzwms01_0_0.md index a3533bcd0f..67ff8d0b03 100644 --- a/_addons_bindings/zwave/doc/hank/hkzwms01_0_0.md +++ b/_addons_bindings/zwave/doc/hank/hkzwms01_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *HKZW_MS01*, manufactured by *[Hank](http://www The HKZW_MS01 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HKZW_MS01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HKZW_MS01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/675) to improve the documentation. +### Wakeup Information +The HKZW_MS01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the HKZW_MS01 -: diff --git a/_addons_bindings/zwave/doc/hank/scn01_0_0.md b/_addons_bindings/zwave/doc/hank/scn01_0_0.md index 8f98565684..1aa7879a6e 100644 --- a/_addons_bindings/zwave/doc/hank/scn01_0_0.md +++ b/_addons_bindings/zwave/doc/hank/scn01_0_0.md @@ -13,12 +13,16 @@ This describes the Z-Wave device *SCN01*, manufactured by *[Hank](http://www.han The SCN01 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The SCN01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SCN01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview ### Wakeup Information +The SCN01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + There are no available settings to set up the wake up time. Pressing and holding the Z-Button for 3 seconds. The led will turn to green, which means Scene Controller has successfully sent the wake up notification out. diff --git a/_addons_bindings/zwave/doc/hank/scn04_0_0.md b/_addons_bindings/zwave/doc/hank/scn04_0_0.md index 0850bf2805..d3e48022b6 100644 --- a/_addons_bindings/zwave/doc/hank/scn04_0_0.md +++ b/_addons_bindings/zwave/doc/hank/scn04_0_0.md @@ -10,7 +10,7 @@ This describes the Z-Wave device *SCN04*, manufactured by *[Hank](http://www.han The SCN04 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The SCN04 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SCN04 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -44,6 +44,10 @@ Included as a **secure** device: ### Wakeup Information +The SCN04 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Press and hold any button for three seconds. ## Channels diff --git a/_addons_bindings/zwave/doc/hank/swes01_0_0.md b/_addons_bindings/zwave/doc/hank/swes01_0_0.md index 298b092a7c..7000a4665a 100644 --- a/_addons_bindings/zwave/doc/hank/swes01_0_0.md +++ b/_addons_bindings/zwave/doc/hank/swes01_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *SW es01*, manufactured by *[Hank](http://www.h The SW es01 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The SW es01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SW es01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/707) to improve the documentation. +### Wakeup Information +The SW es01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the SW es01 -: diff --git a/_addons_bindings/zwave/doc/heiman/hs1caz_0_0.md b/_addons_bindings/zwave/doc/heiman/hs1caz_0_0.md index ef81b8862b..b68d4ca509 100644 --- a/_addons_bindings/zwave/doc/heiman/hs1caz_0_0.md +++ b/_addons_bindings/zwave/doc/heiman/hs1caz_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet The HS1CA-Z supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HS1CA-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HS1CA-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -59,6 +59,11 @@ Set the z-Wave controller to exclusion mode and then quickly triple press button If exclusion process is successful, green LED will blink 6 times and then turn off. +### Wakeup Information + +The HS1CA-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the HS1CA-Z -: diff --git a/_addons_bindings/zwave/doc/heiman/hs1dsz_0_0.md b/_addons_bindings/zwave/doc/heiman/hs1dsz_0_0.md index ddbfceac42..b978587699 100644 --- a/_addons_bindings/zwave/doc/heiman/hs1dsz_0_0.md +++ b/_addons_bindings/zwave/doc/heiman/hs1dsz_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet The HS1DS-Z supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HS1DS-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HS1DS-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -34,6 +34,10 @@ Long press Func\_Button while installing batteries in HS1DS-Z. ### Wakeup Information +The HS1DS-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + - Wake up Notification is transmitted every 24 hours by default. - Wake up Notification is transmitted after Notification Report is Transmitted. diff --git a/_addons_bindings/zwave/doc/heiman/hs1htz_0_0.md b/_addons_bindings/zwave/doc/heiman/hs1htz_0_0.md index bdeb6662b7..f29cb1d481 100644 --- a/_addons_bindings/zwave/doc/heiman/hs1htz_0_0.md +++ b/_addons_bindings/zwave/doc/heiman/hs1htz_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet The HS1HT-Z supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HS1HT-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HS1HT-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -38,6 +38,11 @@ Click \[Remove\] icon in Z-Wave Controller. \- Press the Net\_Button 3 times within 1.5s \- If Exclusion Process is successful, Green LED is Blinking 6 times, then turn off +### Wakeup Information + +The HS1HT-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the HS1HT-Z -: diff --git a/_addons_bindings/zwave/doc/heiman/hs1msz_0_0.md b/_addons_bindings/zwave/doc/heiman/hs1msz_0_0.md index 2e4caf7061..e36f2df265 100644 --- a/_addons_bindings/zwave/doc/heiman/hs1msz_0_0.md +++ b/_addons_bindings/zwave/doc/heiman/hs1msz_0_0.md @@ -12,7 +12,7 @@ The device is in the category of *Motion Detector*, defining Motion sensors/dete The HS1MS-Z supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HS1MS-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HS1MS-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -30,6 +30,10 @@ The smart motion sensor is designed to detect motion indoors. When the smart mot ### Wakeup Information +The HS1MS-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + - Wake up Notification is transmitted every 24 hours by default. - Wake up Notification is transmitted after Notification Report is Transmitted. diff --git a/_addons_bindings/zwave/doc/heiman/hs1sa_0_0.md b/_addons_bindings/zwave/doc/heiman/hs1sa_0_0.md index 1128c3bdc1..d4374a4915 100644 --- a/_addons_bindings/zwave/doc/heiman/hs1sa_0_0.md +++ b/_addons_bindings/zwave/doc/heiman/hs1sa_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Smoke Detector*, defining Smoke detectors. The HS1SA-Z supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HS1SA-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HS1SA-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -33,6 +33,10 @@ The smart smoke sensor detects smoke, and sends an alarm signals to alert of dan ### Wakeup Information +The HS1SA-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + - Wake up Notification is transmitted every 24 hours by default. - Wake up Notification is transmitted after Notification Report is Transmitted. diff --git a/_addons_bindings/zwave/doc/heiman/m4172_0_0.md b/_addons_bindings/zwave/doc/heiman/m4172_0_0.md index 2903ef1c5a..0953597713 100644 --- a/_addons_bindings/zwave/doc/heiman/m4172_0_0.md +++ b/_addons_bindings/zwave/doc/heiman/m4172_0_0.md @@ -12,12 +12,15 @@ The device is in the category of *Sensor*, defining Device used to measure somet The M417-2 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The M417-2 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The M417-2 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/738) to improve the documentation. +### Wakeup Information +The M417-2 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the M417-2 -: diff --git a/_addons_bindings/zwave/doc/hogar/htp4s1fb_2_2.md b/_addons_bindings/zwave/doc/hogar/htp4s1fb_2_2.md index 3a13f0b0bd..072ac104bb 100644 --- a/_addons_bindings/zwave/doc/hogar/htp4s1fb_2_2.md +++ b/_addons_bindings/zwave/doc/hogar/htp4s1fb_2_2.md @@ -14,7 +14,7 @@ This version of the device is limited to firmware versions above 2.2 The HTP-4S1-FB supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HTP-4S1-FB does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HTP-4S1-FB does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -46,6 +46,11 @@ Please visit http://hogarcontrols.com/shop/touch-panels/four-touch-panel-socket 4\. The LED of the button will flash pink (once) indicating that the device is ready to be included. +### Wakeup Information + +The HTP-4S1-FB does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the HTP-4S1-FB -: diff --git a/_addons_bindings/zwave/doc/hogar/htp850xx_0_0.md b/_addons_bindings/zwave/doc/hogar/htp850xx_0_0.md index bc5ddc5047..24cf1b1335 100644 --- a/_addons_bindings/zwave/doc/hogar/htp850xx_0_0.md +++ b/_addons_bindings/zwave/doc/hogar/htp850xx_0_0.md @@ -27,10 +27,6 @@ Touch and hold any key on the panel excess 5 seconds. All indication lights blin Touch and hold any key on the panel excess 10 seconds. All indication lights blinks blue, then release, touch panel start exclusion process -### Wakeup Information - -n/a - ## Channels The following table summarises the channels available for the HTP-8S0-XX -: diff --git a/_addons_bindings/zwave/doc/homeseer/ezmotionexpress_0_0.md b/_addons_bindings/zwave/doc/homeseer/ezmotionexpress_0_0.md index 2a38d906f4..1bb8ebc953 100644 --- a/_addons_bindings/zwave/doc/homeseer/ezmotionexpress_0_0.md +++ b/_addons_bindings/zwave/doc/homeseer/ezmotionexpress_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *EZMotion Express*, manufactured by *Express Co The EZMotion Express supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The EZMotion Express does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The EZMotion Express does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/140) to improve the documentation. +### Wakeup Information +The EZMotion Express does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the EZMotion Express -: diff --git a/_addons_bindings/zwave/doc/homeseer/ezmultipli_0_0.md b/_addons_bindings/zwave/doc/homeseer/ezmultipli_0_0.md index 352056a55a..0b33a6ad62 100644 --- a/_addons_bindings/zwave/doc/homeseer/ezmultipli_0_0.md +++ b/_addons_bindings/zwave/doc/homeseer/ezmultipli_0_0.md @@ -17,7 +17,25 @@ The EZMultiPli supports routing. This allows the device to communicate using oth ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/268) to improve the documentation. +EZMultiPli™ enables fully automated lighting that turns on the lights when you enter a room and turns them off shortly after you leave. Sophisticated lighting, Audio, Video and heating/cooling are enabled with the EZMultiPli™ threesensors-in-one Z-Wave® device. + +EZMultiPli is primarily intended as a motion sensor that will detect motion and send a command to up to 4 associated ZWave devices as well as the system controller. The other ZWave devices can directly control lights in a room or the motion indication can be sent to a computer for complex scene control of lighting, audio, video and heating/cooling. When motion is not detected within a pre-set amount of time, EZMultiPli will send an “off” command to the Z-Wave nodes to turn the lights off. + +In addition to the motion sensor, EZMultiPli also senses the amount of light in the room as well as the current temperature. The color LED light within EZMultiPli is a convenient night light or can be used as an indicator light to let you know if the weather forecast is predicting rain, your garage doors are open or any other indicator supported by your home control application. + +EZMultiPli is wall powered and needs no wires or batteries. Simply plug EZMultiPli into the wall, join the Z-Wave network and you’re ready to go. + +### Inclusion Information + +Before attempting to include (pair) EZMultiPli to a Z-Wave network, be sure the LED is blinking an aqua color. If it is not blinking aqua, follow the exclusion instructions above. + +Follow the procedure of the Z-Wave primary controller to begin the inclusion process. Then press and release the push button on the side of EZMultiPli. Once EZMultiPli has been added to the Z-Wave network, the LED will stop blinking blue and instead will blink white each time it detects motion. EZMultiPli remains in this mode for 5 minutes. Once the 5 minutes has expired, EZMultiPli will enter normal operating mode and the LED will remain off. Pressing the push button will restart the 5 minute motion detector test mode. The primary controller should provide a Z-Wave NodeID which has been assigned to EZMultiPli. The NodeID is a unique identifier and is used by many home control applications to identify this particular EZMultiPli. Write down the NodeID and location for later entry into your home control application. + +### Exclusion Information + +When EZMultiPli is first plugged into the wall outlet, the LED should blink an aqua color. This indicates that it is not currently joined (or paired) to a Z-Wave network. If the LED is blinking white each time motion is detected, then it is already joined to a Z-Wave network. If the LED is blinking white you will need to exclude it from the other Z-Wave network before attempting to join a new one. + +Follow the procedure of the Z-Wave primary controller to begin the exclusion process. Once the primary controller is ready to receive the exclusion command, press and release the push button on the side of EZMultiPli. The primary controller should give an indication that the reset process has completed. EZMultiPlis LED will blink aqua when it is ready to be added to a Z-Wave network. ## Channels @@ -154,12 +172,12 @@ Association groups allow the device to send unsolicited reports to the controlle The EZMultiPli supports 2 association groups. -### Group 1: LIFELINE +### Group 1: Lifeline This group is normally automatically assigned to the Z-Wave system controller when EZMultiPli is added to the ZWave network. This group supports 1 nodes. -### Group 2: BASIC +### Group 2: Basic This group is used to directly turn lights on or off when motion is detected. This group supports 4 nodes. diff --git a/_addons_bindings/zwave/doc/homeseer/hsds100_0_0.md b/_addons_bindings/zwave/doc/homeseer/hsds100_0_0.md index ae5a063143..566b7351f5 100644 --- a/_addons_bindings/zwave/doc/homeseer/hsds100_0_0.md +++ b/_addons_bindings/zwave/doc/homeseer/hsds100_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Door*, defining Door sensors. The HS-DS100+ supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HS-DS100+ does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HS-DS100+ does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -38,6 +38,11 @@ Note: If you want this Door/window sensor to function as a security device using 2\. Triple-click the Z-Wave button inside the sensor body. If successful, the LED will turn off within 1 second. If unsuccessful, the LED with blink for 5 seconds. Should this happen, repeat the exclusion process. +### Wakeup Information + +The HS-DS100+ does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the HS-DS100+ -: diff --git a/_addons_bindings/zwave/doc/homeseer/hsls100_0_0.md b/_addons_bindings/zwave/doc/homeseer/hsls100_0_0.md index 947c6f250a..9c8eaac0ef 100644 --- a/_addons_bindings/zwave/doc/homeseer/hsls100_0_0.md +++ b/_addons_bindings/zwave/doc/homeseer/hsls100_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet The HS-LS100+ supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HS-LS100+ does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HS-LS100+ does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -35,6 +35,10 @@ Exclusion ### Wakeup Information +The HS-LS100+ does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Press and hold the Z button for more that 5 seconds and release ## Channels diff --git a/_addons_bindings/zwave/doc/homeseer/hsms100_0_0.md b/_addons_bindings/zwave/doc/homeseer/hsms100_0_0.md index 7d58b162eb..952b5090ff 100644 --- a/_addons_bindings/zwave/doc/homeseer/hsms100_0_0.md +++ b/_addons_bindings/zwave/doc/homeseer/hsms100_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Motion Detector*, defining Motion sensors/dete The HS-MS100+ supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HS-MS100+ does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HS-MS100+ does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -57,6 +57,10 @@ The features list: ### Wakeup Information +The HS-MS100+ does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Press and hold Z button for more than 5 seconds and release ## Channels diff --git a/_addons_bindings/zwave/doc/honeywell/39358_0_0.md b/_addons_bindings/zwave/doc/honeywell/39358_0_0.md new file mode 100644 index 0000000000..c029a8d1a2 --- /dev/null +++ b/_addons_bindings/zwave/doc/honeywell/39358_0_0.md @@ -0,0 +1,143 @@ +--- +layout: documentation +title: 39358 - ZWave +--- + +{% include base.html %} + +# 39358 Z-Wave In-Wall Smart Fan Control +This describes the Z-Wave device *39358*, manufactured by *Honeywell* with the thing type UID of ```honeywell_39358_00_000```. + +The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. + +![39358 product image](https://www.cd-jackson.com/zwave_device_uploads/861/861_default.jpg) + + +The 39358 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. + +## Overview + +Smart solutions +--------------- + +Stay connected to your home with a Honeywell In-Wall Smart Fan Control Switch. Compatible with all Z‑Wave certified gateways, the smart fan switch gives you wireless control of your ceiling fans from any mobile device, computer or Z-Wave enabled remote. Installation is easy – simply replace a standard in-wall switch with the smart fan switch. Whether you’re at home or away, access the switch to choose among 3 different speed settings, or to turn your fan on and off. The rocker-style switch includes white and light almond switch covers to match any decor and features a blue LED indicator light to locate the switch in a dark room. Your smart home just got smarter with the Honeywell In-Wall Smart Fan Control Switch. + +Model Number: 39358 + +Product Features +---------------- + +- Wirelessly control schedule from anywhere +- 3 speed fan control (High, Medium, Low) +- Rocker-style switch +- White and light almond switch covers +- Add-on compatible (3-way, 4-way, 5-way) + +Product Specifications +---------------------- + +- Brand: Honeywell +- Model Number: 39358 +- Z-Wave Cert Number: ZC10-17125903 + +References +---------- + +- http://www.z-wave.com/shop-z-wave-smart-home-products/smart-fan-control-honeywell-honeywell-z-wave-in-wall-3-speed-fan-control-paddle +- https://byjasco.com/products/honeywell-z-wave-plus-wall-smart-fan-control +- https://www.amazon.com/dp/B07B3Y7YK5/ + +### Inclusion Information + +### CONNECTING YOUR DEVICE TO A Z-WAVE NETWORK + +1. Follow the instructions for your Z-Wave certified controller to add a device to the Z-Wave network. +2. Once the controller is ready to add your device, press and release the top or bottom of the wireless smart fan control (rocker) to add it in the network. + +Now you have complete control to turn your fixture ON/OFF according to groups, scenes, schedules and interactive automations programmed by your controller. If your Z-Wave certified controller features remote access, you can now control your fixture from your mobile devices. + +### Exclusion Information + +### REMOVING AND RESETTING THE DEVICE + +1. Follow the instructions for your Z-Wave certified controller to remove a device from the Z-Wave network. +2. Once the controller is ready to remove your device, press and release the top or bottom of the wireless smart fan control (rocker) to remove it from the network. + +### RETURNING SWITCH TO FACTORY DEFAULTS + +Quickly press ON (Top) button three (3) times then immediately press the OFF (Bottom) button three (3) times. The LED will flash ON/OFF 5 times when completed successfully. + +**Note:** This should only be used in the event your network’s primary controller is missing or otherwise inoperable. + +## Channels + +The following table summarises the channels available for the 39358 -: + +| Channel | Channel Id | Category | Item Type | +|---------|------------|----------|-----------| +| Dimmer | switch_dimmer | DimmableLight | Dimmer | +| Scene Number | scene_number | | Number | + +### Dimmer + +The brightness channel allows to control the brightness of a light. + It is also possible to switch the light on and off. + +The ```switch_dimmer``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. + +### Scene Number + +Triggers when a scene button is pressed. + +The ```scene_number``` channel supports the ```Number``` item. + + + +## Device Configuration + +The device has no configuration parameters configured. + +## Association Groups + +Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic. + +The 39358 supports 1 association group. + +### Group 1: Lifeline + +Lifeline, Multilevel Switch Support +This group supports 5 nodes. + +## Technical Information + +### Endpoints + +#### Endpoint 0 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_NO_OPERATION_V1| | +| COMMAND_CLASS_BASIC_V1| | +| COMMAND_CLASS_SWITCH_MULTILEVEL_V1| | +| COMMAND_CLASS_SWITCH_ALL_V1| | +| COMMAND_CLASS_SCENE_ACTIVATION_V1| | +| COMMAND_CLASS_SCENE_ACTUATOR_CONF_V1| | +| COMMAND_CLASS_CRC_16_ENCAP_V1| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| | +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_CONFIGURATION_V1| | +| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| | +| COMMAND_CLASS_POWERLEVEL_V1| | +| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_VERSION_V2| | + +### Documentation Links + +* [PDF manual](https://www.cd-jackson.com/zwave_device_uploads/861/Quick-start-guide-Honeywell-Z-Wave-In-Wall-3-Speed-Fan-Control--Paddle-.pdf) + +--- + +Did you spot an error in the above definition or want to improve the content? +You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/861). diff --git a/_addons_bindings/zwave/doc/horstmann/hrt4zw_0_0.md b/_addons_bindings/zwave/doc/horstmann/hrt4zw_0_0.md index ace367f95d..08c42baf6d 100644 --- a/_addons_bindings/zwave/doc/horstmann/hrt4zw_0_0.md +++ b/_addons_bindings/zwave/doc/horstmann/hrt4zw_0_0.md @@ -13,12 +13,17 @@ The device is in the category of *HVAC*, defining Air condition devices, Fans. ![HRT4-ZW product image](https://www.cd-jackson.com/zwave_device_uploads/20/20_default.jpg) -The HRT4-ZW does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HRT4-ZW does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview **Note**: This device is also sold as Secure SRT321 +### Wakeup Information + +The HRT4-ZW does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the HRT4-ZW -: diff --git a/_addons_bindings/zwave/doc/horstmann/scsc17_0_0.md b/_addons_bindings/zwave/doc/horstmann/scsc17_0_0.md index d7a06de815..86f732a3f5 100644 --- a/_addons_bindings/zwave/doc/horstmann/scsc17_0_0.md +++ b/_addons_bindings/zwave/doc/horstmann/scsc17_0_0.md @@ -11,12 +11,15 @@ This describes the Z-Wave device *SCSC-17*, manufactured by *Horstmann Controls ![SCSC-17 product image](https://www.cd-jackson.com/zwave_device_uploads/21/21_default.jpg) -The SCSC-17 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SCSC-17 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/21) to improve the documentation. +### Wakeup Information +The SCSC-17 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the SCSC-17 -: diff --git a/_addons_bindings/zwave/doc/horstmann/ses302_0_0.md b/_addons_bindings/zwave/doc/horstmann/ses302_0_0.md index 01c0de427f..e270016c49 100644 --- a/_addons_bindings/zwave/doc/horstmann/ses302_0_0.md +++ b/_addons_bindings/zwave/doc/horstmann/ses302_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Sensor*, defining Device used to measure somet The SES 302 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The SES 302 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SES 302 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/505) to improve the documentation. +### Wakeup Information +The SES 302 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the SES 302 -: diff --git a/_addons_bindings/zwave/doc/horstmann/ses303_0_0.md b/_addons_bindings/zwave/doc/horstmann/ses303_0_0.md index 2de8ca3e2b..b0c04e28ef 100644 --- a/_addons_bindings/zwave/doc/horstmann/ses303_0_0.md +++ b/_addons_bindings/zwave/doc/horstmann/ses303_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Sensor*, defining Device used to measure somet The SES 303 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The SES 303 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SES 303 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/782) to improve the documentation. +### Wakeup Information +The SES 303 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the SES 303 -: diff --git a/_addons_bindings/zwave/doc/horstmann/srt323_0_0.md b/_addons_bindings/zwave/doc/horstmann/srt323_0_0.md index 490815f762..a0dd5c3745 100644 --- a/_addons_bindings/zwave/doc/horstmann/srt323_0_0.md +++ b/_addons_bindings/zwave/doc/horstmann/srt323_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *HVAC*, defining Air condition devices, Fans. The SRT323 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The SRT323 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SRT323 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/466) to improve the documentation. +### Wakeup Information +The SRT323 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the SRT323 -: diff --git a/_addons_bindings/zwave/doc/horstmann/ssr302_0_0.md b/_addons_bindings/zwave/doc/horstmann/ssr302_0_0.md index 37f904a3f2..bab29e5813 100644 --- a/_addons_bindings/zwave/doc/horstmann/ssr302_0_0.md +++ b/_addons_bindings/zwave/doc/horstmann/ssr302_0_0.md @@ -12,12 +12,15 @@ The device is in the category of *HVAC*, defining Air condition devices, Fans. The SSR-302 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The SSR-302 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SSR-302 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/262) to improve the documentation. +### Wakeup Information +The SSR-302 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the SSR-302 -: diff --git a/_addons_bindings/zwave/doc/horstmann/swm301_0_0.md b/_addons_bindings/zwave/doc/horstmann/swm301_0_0.md index ac3f3114b1..bc5313bd08 100644 --- a/_addons_bindings/zwave/doc/horstmann/swm301_0_0.md +++ b/_addons_bindings/zwave/doc/horstmann/swm301_0_0.md @@ -13,7 +13,7 @@ This describes the Z-Wave device *SWM301*, manufactured by *Horstmann Controls L The SWM301 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The SWM301 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SWM301 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -30,6 +30,10 @@ The RF module records the meter reading by backlash-free pick-up on the litre wh ### Wakeup Information +The SWM301 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Hold a small magnet near to reed switch until the LED is turned on. Remove magnet right away when LED turned on. LED will remain on for next 4 seconds and then it will flash once to indicate NIF is sent. SWM301 will wake up for 10 seconds after sending NIF diff --git a/_addons_bindings/zwave/doc/idlock/idl101_0_0.md b/_addons_bindings/zwave/doc/idlock/idl101_0_0.md index 95b295cb52..d5d62c2e0e 100644 --- a/_addons_bindings/zwave/doc/idlock/idl101_0_0.md +++ b/_addons_bindings/zwave/doc/idlock/idl101_0_0.md @@ -35,10 +35,6 @@ http://idlock.no/ 4. Press the key 8 on the outside panel 5. The LED flashes blue when exclusion is done -### Wakeup Information - -This is a frequently listening device (FLIRS) which supports beaming. This means that the lock will check regularly for incoming commands, and respond quickly without the need for any user specification of wakeup intervals or physical wakeup procedures. - ## Channels The following table summarises the channels available for the IDL-101 -: diff --git a/_addons_bindings/zwave/doc/ingersollecolink/dwzwave1_0_0.md b/_addons_bindings/zwave/doc/ingersollecolink/dwzwave1_0_0.md index 5f145625fb..20e32256f9 100644 --- a/_addons_bindings/zwave/doc/ingersollecolink/dwzwave1_0_0.md +++ b/_addons_bindings/zwave/doc/ingersollecolink/dwzwave1_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *DWZWAVE1*, manufactured by *Ingersoll Rand (wa The DWZWAVE1 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DWZWAVE1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DWZWAVE1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/135) to improve the documentation. +### Wakeup Information +The DWZWAVE1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DWZWAVE1 -: diff --git a/_addons_bindings/zwave/doc/ingersollecolink/rs200_0_0.md b/_addons_bindings/zwave/doc/ingersollecolink/rs200_0_0.md index 9380fa8076..14b8370148 100644 --- a/_addons_bindings/zwave/doc/ingersollecolink/rs200_0_0.md +++ b/_addons_bindings/zwave/doc/ingersollecolink/rs200_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *RS200*, manufactured by *Ingersoll Rand (was E The RS200 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The RS200 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The RS200 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/695) to improve the documentation. +### Wakeup Information +The RS200 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the RS200 -: diff --git a/_addons_bindings/zwave/doc/innovus/smoothremote_0_0.md b/_addons_bindings/zwave/doc/innovus/smoothremote_0_0.md index 4257d9fe11..0b3b5d43bc 100644 --- a/_addons_bindings/zwave/doc/innovus/smoothremote_0_0.md +++ b/_addons_bindings/zwave/doc/innovus/smoothremote_0_0.md @@ -8,12 +8,15 @@ title: SmoothRemote - ZWave # SmoothRemote SmoothRemote This describes the Z-Wave device *SmoothRemote*, manufactured by *INNOVUS* with the thing type UID of ```innovus_smoothremote_00_000```. -The SmoothRemote does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SmoothRemote does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/440) to improve the documentation. +### Wakeup Information +The SmoothRemote does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the SmoothRemote -: diff --git a/_addons_bindings/zwave/doc/inovelli/nzw31_0_0.md b/_addons_bindings/zwave/doc/inovelli/nzw31_0_0.md deleted file mode 100644 index c78422ffc7..0000000000 --- a/_addons_bindings/zwave/doc/inovelli/nzw31_0_0.md +++ /dev/null @@ -1,191 +0,0 @@ ---- -layout: documentation -title: NZW31 - ZWave ---- - -{% include base.html %} - -# NZW31 In-wall Dimming Switch -This describes the Z-Wave device *NZW31*, manufactured by *Inovelli* with the thing type UID of ```inovelli_nzw31_00_000```. - -The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. - -![NZW31 product image](https://www.cd-jackson.com/zwave_device_uploads/856/856_default.jpg) - - -The NZW31 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. - -## Overview - -Inovelli's In-Wall Smart Dimmer not only has the ability to control lights from anywhere in the world, but it acts as a Z-Wave signal repeater, which amplifies your Z-Wave signal, growing the capabilities of your network. - -In addition, it has scene control enabled, which allows you to double tap the switch to activate a Z-Wave scene. An example would be a bedtime scene, which turns off all lights, locks the door(s) and sets the temperature to 68 degrees. - -Simplifying lives, one smart home product at a time... that's Inovelli. - -### Inclusion Information - -**Including Steps:** - -- This will vary based on the HUB/Gateway you’re using, but you need to go one (1) step before putting your HUB/Gateway in inclusion process — once you are one (1) step away from physically starting the inclusion/pairing process — **THEN STOP!** -- Walk down to your circuit breaker and flip on the power (you will now have 30 seconds to physically start the inclusion process on your HUB/Gateway) -- While next to the breaker, start the inclusion process and your HUB/Gateway will automatically start looking for devices -- Wait for auto-inclusion to do its thing. Your switch will automatically include/pair to your HUB/Gateway - - If successful, your device will flash twice (**NOTE:** Auto-Inclusion will time out after 30 seconds) - - If the switch does not flash within 30 seconds, please use the alternate method of pairing which is pressing the top (UP) button 6x within 2 seconds -- Confirm that your HUB/Gateway shows the switch - -Congratulations, you now have a remote controlled switch! - -**If you are having issues pairing your device, please ensure your switch is within range of your HUB. 95% of the pairing/including failures stem from this issue. Best practice is to start with Z-Wave products near your HUB and build your network out. The more Z-Wave devices, the more efficient your network.** - -### Exclusion Information - -- Press the Top (UP) Button on your NZW31 six (6) times within 2 seconds - -## Channels - -The following table summarises the channels available for the NZW31 -: - -| Channel | Channel Id | Category | Item Type | -|---------|------------|----------|-----------| -| Dimmer | switch_dimmer | DimmableLight | Dimmer | -| Scene Number | scene_number | | Number | - -### Dimmer - -The brightness channel allows to control the brightness of a light. - It is also possible to switch the light on and off. - -The ```switch_dimmer``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. - -### Scene Number - -Triggers when a scene button is pressed. - -The ```scene_number``` channel supports the ```Number``` item. - - - -## Device Configuration - -The following table provides a summary of the 4 configuration parameters available in the NZW31. -Detailed information on each parameter can be found in the sections below. - -| Param | Name | Description | -|-------|-------|-------------| -| 1 | Dimmer Step Configuration | Dimmer Speed Setting (On/Off) | -| 2 | Dimmer Minimum Configuration | Lowest dim setting before turning off | -| 4 | Switch Orientation | Invert On/Off from Top/Bottom | -| 5 | Countdown Timer | Shutoff Timer | -| | Switch All Mode | Set the mode for the switch when receiving SWITCH ALL commands | - -### Parameter 1: Dimmer Step Configuration - -Dimmer Speed Setting (On/Off) -Control the speed with which the dimmer turns on and off. -Values in the range 1 to 99 may be set. - -The manufacturer defined default value is ```1```. - -This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```. - - -### Parameter 2: Dimmer Minimum Configuration - -Lowest dim setting before turning off -Lowest dim setting before turning off -Values in the range 1 to 99 may be set. - -The manufacturer defined default value is ```1```. - -This parameter has the configuration ID ```config_2_1``` and is of type ```INTEGER```. - - -### Parameter 4: Switch Orientation - -Invert On/Off from Top/Bottom -Invert the switch on/off position. - -00 - Up = On, Down = Off - -01 - Up = Off, Down = On -Values in the range 0 to 1 may be set. - -The manufacturer defined default value is ```0```. - -This parameter has the configuration ID ```config_4_1``` and is of type ```INTEGER```. - - -### Parameter 5: Countdown Timer - -Shutoff Timer -Countdown timer. - -0x00 - x8000 - 0-32768 Seconds -Values in the range 0 to 32768 may be set. - -The manufacturer defined default value is ```0```. - -This parameter has the configuration ID ```config_5_2``` and is of type ```INTEGER```. - -### Switch All Mode - -Set the mode for the switch when receiving SWITCH ALL commands. - -The following option values may be configured -: -| Value | Description | -|--------|-------------| -| 0 | Exclude from All On and All Off groups | -| 1 | Include in All On group | -| 2 | Include in All Off group | -| 255 | Include in All On and All Off groups | - -This parameter has the configuration ID ```switchall_mode``` and is of type ```INTEGER```. - - -## Association Groups - -Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic. - -The NZW31 supports 1 association group. - -### Group 1: Lifeline - - -This group supports 5 nodes. - -## Technical Information - -### Endpoints - -#### Endpoint 0 - -| Command Class | Comment | -|---------------|---------| -| COMMAND_CLASS_NO_OPERATION_V1| | -| COMMAND_CLASS_BASIC_V1| | -| COMMAND_CLASS_APPLICATION_STATUS_V1| | -| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| Linked to BASIC| -| COMMAND_CLASS_SWITCH_ALL_V1| | -| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | -| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| | -| COMMAND_CLASS_CENTRAL_SCENE_V3| | -| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | -| COMMAND_CLASS_CONFIGURATION_V1| | -| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| | -| COMMAND_CLASS_POWERLEVEL_V1| | -| COMMAND_CLASS_PROTECTION_V2| | -| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| | -| COMMAND_CLASS_ASSOCIATION_V2| | -| COMMAND_CLASS_VERSION_V2| | -| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | - -### Documentation Links - -* [NZW31 Manual](https://www.cd-jackson.com/zwave_device_uploads/856/NZW31.pdf) - ---- - -Did you spot an error in the above definition or want to improve the content? -You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/856). diff --git a/_addons_bindings/zwave/doc/intermatic/ca600_0_0.md b/_addons_bindings/zwave/doc/intermatic/ca600_0_0.md index 86765c94a0..6871a722fd 100644 --- a/_addons_bindings/zwave/doc/intermatic/ca600_0_0.md +++ b/_addons_bindings/zwave/doc/intermatic/ca600_0_0.md @@ -8,11 +8,40 @@ title: CA600 - ZWave # CA600 Dimmer Switch This describes the Z-Wave device *CA600*, manufactured by *Intermatic* with the thing type UID of ```intermatic_ca600_00_000```. +The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. + +![CA600 product image](https://www.cd-jackson.com/zwave_device_uploads/656/656_default.jpg) + + The CA600 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/656) to improve the documentation. +CA 600 is a 600 watt wall-mounted dimmer switch. + +### Inclusion Information + +If you’re using a Z-Stick: + +1. Follow installation instructions for the light switch +2. If light switch is ready for pairing the LED will pulse red & blue +3. If your Z-Stick is plugged into a gateway or a computer, unplug it. +4. Take your Z-Stick to your light Switch. +5. Press the Action Button on your Z-Stick. +6. Press press the toggle on your light Switch. +7. If your switch has been successfully linked to your Z-Wave network, its Status LED will no longer blink. If the linking was unsuccessful, the Status LED continues to blink. Repeat the above steps. +8. Press the Action Button on your Z-Stick to take it out of installation mode + +### Exclusion Information + +If you’re using a Z-Stick: + +1. Unplug the Z-Stick from your gateway or computer. +2. Take your Z-Stick to your light switch. +3. Press the Action Button on your Z-Stick. +4. Press the toggle on your light switch. +5. If your light switch has been successfully removed from your network, its Status LED will blink. If the removal was unsuccessful, its Status LED will not blink. +6. Press the Action Button on your Z-Stick to take it out of removal mode. ## Channels @@ -58,6 +87,10 @@ The device does not support associations. | COMMAND_CLASS_VERSION_V1| | | COMMAND_CLASS_MANUFACTURER_PROPRIETARY_V0| | +### Documentation Links + +* [CA600 Dimmer Switch Manual](https://www.cd-jackson.com/zwave_device_uploads/656/CA600-Manual.pdf) + --- Did you spot an error in the above definition or want to improve the content? diff --git a/_addons_bindings/zwave/doc/intermatic/ha20_0_0.md b/_addons_bindings/zwave/doc/intermatic/ha20_0_0.md index 7fbe499779..7f715c353f 100644 --- a/_addons_bindings/zwave/doc/intermatic/ha20_0_0.md +++ b/_addons_bindings/zwave/doc/intermatic/ha20_0_0.md @@ -17,7 +17,17 @@ The HA20 supports routing. This allows the device to communicate using other rou ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/19) to improve the documentation. +600W In-Wall Toggle Style Dimmer + +### Inclusion Information + +1. Put the controller in inclusion mode +2. Flip the toggle switch on the HA-20 + +### Exclusion Information + +1. Put the controller in exclusion mode +2. Flip the toggle switch on the HA-20 ## Channels diff --git a/_addons_bindings/zwave/doc/isurpass/smokedetector_0_0.md b/_addons_bindings/zwave/doc/isurpass/smokedetector_0_0.md index 479d94754a..068f8eb5b7 100644 --- a/_addons_bindings/zwave/doc/isurpass/smokedetector_0_0.md +++ b/_addons_bindings/zwave/doc/isurpass/smokedetector_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *Smoke Detector*, manufactured by *Shenzhen iSu The Smoke Detector supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The Smoke Detector does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Smoke Detector does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/728) to improve the documentation. +### Wakeup Information +The Smoke Detector does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the Smoke Detector -: diff --git a/_addons_bindings/zwave/doc/kaipule/doorwindowsensor_0_0.md b/_addons_bindings/zwave/doc/kaipule/doorwindowsensor_0_0.md index d48c49d4fe..f2804cb305 100644 --- a/_addons_bindings/zwave/doc/kaipule/doorwindowsensor_0_0.md +++ b/_addons_bindings/zwave/doc/kaipule/doorwindowsensor_0_0.md @@ -10,7 +10,7 @@ This describes the Z-Wave device *TP-802ZD*, manufactured by *Kaipule Technology The TP-802ZD supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The TP-802ZD does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The TP-802ZD does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -32,6 +32,10 @@ To exclude the sensor in a networks start by placing the controller in exclusion ### Wakeup Information +The TP-802ZD does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + a) Manual Wake-up Quickly press tamper switch once, the door sensor will automatically send wake-up information, and there will be 10s after wake-up to receive gateway setting information. diff --git a/_addons_bindings/zwave/doc/kaipule/es61_0_0.md b/_addons_bindings/zwave/doc/kaipule/es61_0_0.md index 7d88655f64..c0108c7e76 100644 --- a/_addons_bindings/zwave/doc/kaipule/es61_0_0.md +++ b/_addons_bindings/zwave/doc/kaipule/es61_0_0.md @@ -16,7 +16,7 @@ The device is in the category of *Smoke Detector*, defining Smoke detectors. The ES-61 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ES-61 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ES-61 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -34,6 +34,10 @@ Enter the Exclusion Mode of the gateway, and press the tamper switch 3 times wit ### Wakeup Information +The ES-61 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + a) Manual Wake-up - Quickly press tamper switch once, the Smoke Sensor will automatically send wake-up information, and there will be 10s after wake-up to receive gateway setting information. b) Automatic Wake-up - Default time of automatic wake-up is 24 hours, and there will be 10s after wake-up to receive gateway setting information. The max automatic report time = 24 hours, minimum = 30 min. diff --git a/_addons_bindings/zwave/doc/kaipule/im20_0_0.md b/_addons_bindings/zwave/doc/kaipule/im20_0_0.md index 2a69188f70..6940d07a59 100644 --- a/_addons_bindings/zwave/doc/kaipule/im20_0_0.md +++ b/_addons_bindings/zwave/doc/kaipule/im20_0_0.md @@ -12,7 +12,7 @@ The device is in the category of *Door*, defining Door sensors. The IM-20 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The IM-20 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The IM-20 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -33,6 +33,10 @@ Enter the Exclusion Mode of gateway, and press the tamper switch 3 times within ### Wakeup Information +The IM-20 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + a) Manual Wake-up Quickly press tamper switch once, the door sensor will automatically send wake-up information, and there will be 10s after wake-up to receive gateway setting information. diff --git a/_addons_bindings/zwave/doc/kaipule/ix32_6_0.md b/_addons_bindings/zwave/doc/kaipule/ix32_6_0.md index 2df1a5ddd9..bea4c52661 100644 --- a/_addons_bindings/zwave/doc/kaipule/ix32_6_0.md +++ b/_addons_bindings/zwave/doc/kaipule/ix32_6_0.md @@ -14,12 +14,17 @@ This version of the device is limited to firmware versions above 6.0 The DP-32 / IX-30 / IX-32 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DP-32 / IX-30 / IX-32 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DP-32 / IX-30 / IX-32 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview The hardware board for the IX30 (wall) and IX32 (ceiling) is the same thing and reports the same Type and ID. +### Wakeup Information + +The DP-32 / IX-30 / IX-32 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DP-32 / IX-30 / IX-32 -: diff --git a/_addons_bindings/zwave/doc/leviton/vrpd3_0_0.md b/_addons_bindings/zwave/doc/leviton/vrpd3_0_0.md index 51d10c563e..1045dbe0c7 100644 --- a/_addons_bindings/zwave/doc/leviton/vrpd3_0_0.md +++ b/_addons_bindings/zwave/doc/leviton/vrpd3_0_0.md @@ -8,6 +8,11 @@ title: VRPD3 - ZWave # VRPD3 Scene Capable Plug-in Dimmer This describes the Z-Wave device *VRPD3*, manufactured by *Leviton* with the thing type UID of ```leviton_vrpd3_00_000```. +The device is in the category of *Power Outlet*, defining Small devices to be plugged into a power socket in a wall which stick there. + +![VRPD3 product image](https://www.cd-jackson.com/zwave_device_uploads/199/199_default.jpg) + + The VRPD3 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. ## Overview diff --git a/_addons_bindings/zwave/doc/linear/gb00z_0_0.md b/_addons_bindings/zwave/doc/linear/gb00z_0_0.md index 29a64b5f10..301fb61edf 100644 --- a/_addons_bindings/zwave/doc/linear/gb00z_0_0.md +++ b/_addons_bindings/zwave/doc/linear/gb00z_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *GB00Z*, manufactured by *Linear Corp* with the The GB00Z supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The GB00Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The GB00Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/565) to improve the documentation. +### Wakeup Information +The GB00Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the GB00Z -: diff --git a/_addons_bindings/zwave/doc/linear/pd300z2_0_0.md b/_addons_bindings/zwave/doc/linear/pd300z2_0_0.md index 585a390221..a4b13e7516 100644 --- a/_addons_bindings/zwave/doc/linear/pd300z2_0_0.md +++ b/_addons_bindings/zwave/doc/linear/pd300z2_0_0.md @@ -8,11 +8,27 @@ title: PD300Z-2 - ZWave # PD300Z-2 Plug-in Wall Dimmer This describes the Z-Wave device *PD300Z-2*, manufactured by *Linear Corp* with the thing type UID of ```linear_pd300z2_00_000```. +The device is in the category of *Light Bulb*, defining Devices that illuminate something, such as bulbs, etc.. + +![PD300Z-2 product image](https://www.cd-jackson.com/zwave_device_uploads/7/7_default.jpg) + + The PD300Z-2 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/7) to improve the documentation. +300 Watt, 120 VAC NWI and Scene Capable Plug-In Lamp Module + +### Inclusion Information + +1. Prepare the Controller to include a unit to the network. The PD300Z-2 must be in its permanently installed location. +2. For NWI Inclusion, press the button on the PD300Z-2 once. +3. For classic inclusion, press the button on the PD300Z-2 twice. + +### Exclusion Information + +1. Set the Controller into Removal Mode +2. Remove the switch by press the button twice ## Channels @@ -102,6 +118,10 @@ The device does not support associations. | COMMAND_CLASS_POWERLEVEL_V1| | | COMMAND_CLASS_VERSION_V1| | +### Documentation Links + +* [PD300Z-2 Manual](https://www.cd-jackson.com/zwave_device_uploads/7/PD300Z-2-Install.pdf) + --- Did you spot an error in the above definition or want to improve the content? diff --git a/_addons_bindings/zwave/doc/linear/wa00z1_0_0.md b/_addons_bindings/zwave/doc/linear/wa00z1_0_0.md index 2b99650c57..0a2179f1ec 100644 --- a/_addons_bindings/zwave/doc/linear/wa00z1_0_0.md +++ b/_addons_bindings/zwave/doc/linear/wa00z1_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *WA00Z-1*, manufactured by *Linear Corp* with t The WA00Z-1 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The WA00Z-1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The WA00Z-1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/610) to improve the documentation. +### Wakeup Information +The WA00Z-1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the WA00Z-1 -: diff --git a/_addons_bindings/zwave/doc/linear/wadwaz1_0_0.md b/_addons_bindings/zwave/doc/linear/wadwaz1_0_0.md index 938f8946d1..8727b60e39 100644 --- a/_addons_bindings/zwave/doc/linear/wadwaz1_0_0.md +++ b/_addons_bindings/zwave/doc/linear/wadwaz1_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Door*, defining Door sensors. The WADWAZ-1 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The WADWAZ-1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The WADWAZ-1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -48,6 +48,10 @@ For “Exclusion” from (removing from) a network: ### Wakeup Information +The WADWAZ-1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Open and then closed the cover to wakeup the device. This will also trigger the tamper alarm, which needs to be turned off manually. ## Channels diff --git a/_addons_bindings/zwave/doc/linear/wapirz_0_0.md b/_addons_bindings/zwave/doc/linear/wapirz_0_0.md index cf0bb84953..cd9479532f 100644 --- a/_addons_bindings/zwave/doc/linear/wapirz_0_0.md +++ b/_addons_bindings/zwave/doc/linear/wapirz_0_0.md @@ -15,11 +15,34 @@ The device is in the category of *Motion Detector*, defining Motion sensors/dete The WAPIRZ-1 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The WAPIRZ-1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The WAPIRZ-1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/5) to improve the documentation. +Wireless Passive Infrared (PIR) Motion Detector + +### Inclusion Information + +1. Prepare the Controller to include a unit to the network by adding it to a group (method of adding a node to the network). Refer to controller instructions. +2. If your Controller supports Network Wide Inclusion (NWI) locate the WAPIRZ-1 near the proposed installation location. If not skip to Step 4. +3. With your Controller in Inclusion mode, you should see an indication on your Controller that the “device was included” in the network. It should display binary switch / Linear. The LED will stop blinking. Skip to Step 10. If the LED does not stop blinking, relocate the WAPIRZ-1 to within 100 feet (line of sight) of a Z-Wave device or your hub and repeat Step 3. If the LED continues to blink, your Controller does not support NWI and continue with Step 4. +4. Place the WAPIRZ-1 within 3 feet of the Controller. +5. With your controller in Inclusion mode, depress the Tamper switch for 1 second then release. +6. You should see an indication on your Controller that the “device was included” in the network. It should display binary switch / Linear. The LED will stop blinking. +7. The device will appear in the list of Switches. + +### Exclusion Information + +1. Set up the Z-Wave™ Interface Controller into “exclusion” mode, and following its instruction to delete the WAPIRZ-1 from the controller. +2. Press the Tamper switch of WAPIRZ-1 for 1 second and release to be excluded. The LED light will flash continuously when the sensor is in the Exclusion condition. + +### Wakeup Information + +The WAPIRZ-1 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + +Open the motion detector case to “wake” the unit. ## Channels diff --git a/_addons_bindings/zwave/doc/linear/wd500z_0_0.md b/_addons_bindings/zwave/doc/linear/wd500z_0_0.md index d5d7abb512..3782732cd7 100644 --- a/_addons_bindings/zwave/doc/linear/wd500z_0_0.md +++ b/_addons_bindings/zwave/doc/linear/wd500z_0_0.md @@ -17,7 +17,15 @@ The WD500Z-1 supports routing. This allows the device to communicate using other ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/6) to improve the documentation. +500W, 120 VAC Wall Mounted Dimmer + +### Inclusion Information + +Pushing the top or bottom of the switch, the WD500Z-1 allows the user to include or exclude the module from the Z-Wave network. + +### Exclusion Information + +Pushing the top or bottom of the switch, the WD500Z-1 allows the user to include or exclude the module from the Z-Wave network. ## Channels @@ -43,18 +51,18 @@ Detailed information on each parameter can be found in the sections below. | Param | Name | Description | |-------|-------|-------------| -| 1 | Dim Start Level | A dimmer receiving this command will start dimming from that start level if this bit is set to 0. If the bit is set to 1, the dimmer will ignore the start level and instead start dimming from its current level. | +| 1 | Dim Start Level | Start dimming from that start level or current level | | 3 | LED Indication | The WD500Z-1 will flicker its LED when it is transmitting to any of its groups. | -| 4 | Invert Switch | To change the top of the switch to OFF and the bottom to ON change parameter to 1. | +| 4 | Invert Switch | Reverse switch direction | | 14 | Enable Shade Control Group 2 | The switch can control shade control devices if this parameter is set to 1 | | 15 | Enable Shade Control Group 3 | The switch can control shade control devices if this parameter is set to 1. | -| 19 | LED Transmission Indication | The WD500Z-1 will flicker its LED when it is transmitting to any of its groups. Parameter set to 0 = not flicker Parameter set to 1 = flicker the entire time of transmitting Parameter set to 2 = flicker for only 1 second. | +| 19 | LED Transmission Indication | LED mode while transmitting | | | Switch All Mode | Set the mode for the switch when receiving SWITCH ALL commands | ### Parameter 1: Dim Start Level +Start dimming from that start level or current level A dimmer receiving this command will start dimming from that start level if this bit is set to 0. If the bit is set to 1, the dimmer will ignore the start level and instead start dimming from its current level. - The following option values may be configured -: | Value | Description | @@ -85,8 +93,8 @@ This parameter has the configuration ID ```config_3_1``` and is of type ```INTEG ### Parameter 4: Invert Switch +Reverse switch direction To change the top of the switch to OFF and the bottom to ON change parameter to 1. - The following option values may be configured -: | Value | Description | @@ -97,6 +105,7 @@ The following option values may be configured -: The manufacturer defined default value is ```0``` (Top-ON, Bottom-OFF ). This parameter has the configuration ID ```config_4_1``` and is of type ```INTEGER```. +This is a read only parameter. ### Parameter 14: Enable Shade Control Group 2 @@ -133,8 +142,14 @@ This parameter has the configuration ID ```config_15_1``` and is of type ```INTE ### Parameter 19: LED Transmission Indication -The WD500Z-1 will flicker its LED when it is transmitting to any of its groups. Parameter set to 0 = not flicker Parameter set to 1 = flicker the entire time of transmitting Parameter set to 2 = flicker for only 1 second. +LED mode while transmitting +The WD500Z-1 will flicker its LED when it is transmitting to any of its groups. + +Parameter set to 0 = not flicker + +Parameter set to 1 = flicker the entire time of transmitting +Parameter set to 2 = flicker for only 1 second. The following option values may be configured -: | Value | Description | diff --git a/_addons_bindings/zwave/doc/linear/wo15z_0_0.md b/_addons_bindings/zwave/doc/linear/wo15z_0_0.md index 08bcaa5d29..f68c49dfa0 100644 --- a/_addons_bindings/zwave/doc/linear/wo15z_0_0.md +++ b/_addons_bindings/zwave/doc/linear/wo15z_0_0.md @@ -8,11 +8,29 @@ title: WO15Z - ZWave # WO15Z Single Wall Outlet This describes the Z-Wave device *WO15Z*, manufactured by *Linear Corp* with the thing type UID of ```linear_wo15z_00_000```. +The device is in the category of *Power Outlet*, defining Small devices to be plugged into a power socket in a wall which stick there. + +![WO15Z product image](https://www.cd-jackson.com/zwave_device_uploads/12/12_default.jpg) + + The WO15Z supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/12) to improve the documentation. +120 VAC 15 Amp Duplex Receptacle + +### Inclusion Information + +1. Prepare the Controller to include a unit to the network. The WO15Z-1 must be in its permanently installed location. +2. Press the button on the WO15Z-1 once. +3. You should see an indication on your Controller that the “DEVICE WAS INCLUDED” in the network. + +### Exclusion Information + +1. Set the Controller into Removal Mode and follow its instruction to delete the + WO15Z-1 from the Controller. +2. Remove the switch by pressing the button twice. +3. You should see an indication on your Controller that the “device was removed” from the network. ## Channels @@ -44,13 +62,13 @@ Detailed information on each parameter can be found in the sections below. | Param | Name | Description | |-------|-------|-------------| -| 3 | Night Light | By default, the blue LED on the WO15Z-1 will turn ON when the load attached is turned ON. To make the LED turn OFF when the load attached is turned ON, set Parameter 3 to a value of 1. | +| 3 | Night Light | LED mode for attached load | | | Switch All Mode | Set the mode for the switch when receiving SWITCH ALL commands | ### Parameter 3: Night Light +LED mode for attached load By default, the blue LED on the WO15Z-1 will turn ON when the load attached is turned ON. To make the LED turn OFF when the load attached is turned ON, set Parameter 3 to a value of 1. - The following option values may be configured -: | Value | Description | @@ -102,6 +120,10 @@ The device does not support associations. | COMMAND_CLASS_PROTECTION_V1| | | COMMAND_CLASS_VERSION_V1| | +### Documentation Links + +* [WO15Z-1 Manual](https://www.cd-jackson.com/zwave_device_uploads/12/WO15Z-1-Install-1.pdf) + --- Did you spot an error in the above definition or want to improve the content? diff --git a/_addons_bindings/zwave/doc/linear/ws15z_0_0.md b/_addons_bindings/zwave/doc/linear/ws15z_0_0.md index 8e36ed8b61..ab771a4394 100644 --- a/_addons_bindings/zwave/doc/linear/ws15z_0_0.md +++ b/_addons_bindings/zwave/doc/linear/ws15z_0_0.md @@ -17,7 +17,18 @@ The WS15Z-1 supports routing. This allows the device to communicate using other ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/4) to improve the documentation. +Scene and NWI capable wall mounted switch + +### Inclusion Information + +1. With your Controller in Discovery or Add Mode, tap the switch once for Network Wide Inclusion. Tap twice for Standard Inclusion. +2. You should see an indication on your Controller that the “device was added” to the network and the LED will stop blinking. + +### Exclusion Information + +1. Set the Controller into Removal Mode and follow its instruction to delete the WS15Z-1 from the Controller. +2. Remove the switch by tapping the paddle 2 times. +3. You should see an indication on your Controller that the “device was removed” from the network. ## Channels diff --git a/_addons_bindings/zwave/doc/logic/scenecontroller_0_0.md b/_addons_bindings/zwave/doc/logic/scenecontroller_0_0.md new file mode 100644 index 0000000000..881cec38a0 --- /dev/null +++ b/_addons_bindings/zwave/doc/logic/scenecontroller_0_0.md @@ -0,0 +1,955 @@ +--- +layout: documentation +title: Heatit Z-Scene Controller - ZWave +--- + +{% include base.html %} + +# Heatit Z-Scene Controller Push button 6-gang +This describes the Z-Wave device *Heatit Z-Scene Controller*, manufactured by *[Logic Home Control](http://logichome.dk/)* with the thing type UID of ```logic_scenecontroller_00_000```. + +The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. + +![Heatit Z-Scene Controller product image](https://www.cd-jackson.com/zwave_device_uploads/846/846_default.png) + + +The Heatit Z-Scene Controller does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. + +## Overview + +The Heatit Z-Wave Scene Controller is a Z-Wave module specifically adapted to Gira KNX touch sensors. The Heatit Z-Wave Scene Controller is a device with built-in wireless Z-Wave communication that may be used to control other Z-Wave devices such as dimmers, relay modules, etc. + +The scene controller has a built-in relay that can be used to turn on and off a local load, e.g. a lamp, thus replacing a standard 1-pole switch. + +### Inclusion Information + +Pushing the upper left button 3 times (triple click) will activate Inclusion Mode on the device. It is also possible to activate Inclusion Mode by triple clicking the switch inside the module (through a little hole in the front of the module). + +### Exclusion Information + + The inclusion and exclusion of the device is confirmed by sending out a Node Information Frame. Beside this, it may be necessary for certain network operations to send out a Node Information Frame. Triple clicking the button inside the module through a little hole (normally covered by GIRA module) or the upper left button will issue a Node Information Frame. + +### Wakeup Information + +The Heatit Z-Scene Controller does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +## Channels + +The following table summarises the channels available for the Heatit Z-Scene Controller -: + +| Channel | Channel Id | Category | Item Type | +|---------|------------|----------|-----------| +| Switch | switch_binary | Switch | Switch | +| Dimmer | switch_dimmer | DimmableLight | Dimmer | +| Scene Number | scene_number | | Number | +| Switch 1 | switch_binary1 | Switch | Switch | +| Dimmer 1 | switch_dimmer1 | DimmableLight | Dimmer | +| Switch 2 | switch_binary2 | Switch | Switch | +| Dimmer 2 | switch_dimmer2 | DimmableLight | Dimmer | +| Switch 3 | switch_binary3 | Switch | Switch | +| Dimmer 3 | switch_dimmer3 | DimmableLight | Dimmer | +| Switch 4 | switch_binary4 | Switch | Switch | +| Dimmer 4 | switch_dimmer4 | DimmableLight | Dimmer | +| Switch 5 | switch_binary5 | Switch | Switch | +| Dimmer 5 | switch_dimmer5 | DimmableLight | Dimmer | +| Switch 6 | switch_binary6 | Switch | Switch | +| Dimmer 6 | switch_dimmer6 | DimmableLight | Dimmer | + +### Switch + +Switch the power on and off. + +The ```switch_binary``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### Dimmer + +The brightness channel allows to control the brightness of a light. + It is also possible to switch the light on and off. + +The ```switch_dimmer``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. + +### Scene Number + +Triggers when a scene button is pressed. + +The ```scene_number``` channel supports the ```Number``` item. + +### Switch 1 + +Switch the power on and off. + +The ```switch_binary1``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### Dimmer 1 + +The brightness channel allows to control the brightness of a light. + It is also possible to switch the light on and off. + +The ```switch_dimmer1``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. + +### Switch 2 + +Switch the power on and off. + +The ```switch_binary2``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### Dimmer 2 + +The brightness channel allows to control the brightness of a light. + It is also possible to switch the light on and off. + +The ```switch_dimmer2``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. + +### Switch 3 + +Switch the power on and off. + +The ```switch_binary3``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### Dimmer 3 + +The brightness channel allows to control the brightness of a light. + It is also possible to switch the light on and off. + +The ```switch_dimmer3``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. + +### Switch 4 + +Switch the power on and off. + +The ```switch_binary4``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### Dimmer 4 + +The brightness channel allows to control the brightness of a light. + It is also possible to switch the light on and off. + +The ```switch_dimmer4``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. + +### Switch 5 + +Switch the power on and off. + +The ```switch_binary5``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### Dimmer 5 + +The brightness channel allows to control the brightness of a light. + It is also possible to switch the light on and off. + +The ```switch_dimmer5``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. + +### Switch 6 + +Switch the power on and off. + +The ```switch_binary6``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### Dimmer 6 + +The brightness channel allows to control the brightness of a light. + It is also possible to switch the light on and off. + +The ```switch_dimmer6``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. + + + +## Device Configuration + +The following table provides a summary of the 26 configuration parameters available in the Heatit Z-Scene Controller. +Detailed information on each parameter can be found in the sections below. + +| Param | Name | Description | +|-------|-------|-------------| +| 1 | Upper paddle buttons mode | Configuration of Pair Mode for the upper two buttons (button #1 and #2) | +| 2 | Middle paddle buttons mode | Configuration of Pair Mode for the middle two buttons (button #3 and #4) | +| 3 | Lower paddle buttons mode | Configuration of Pair Mode for the lower two buttons (button #5 and #6) | +| 4 | LED #1 mode. | Configuration of the internal operation of LED #1 | +| 5 | LED #2 mode | Configuration of the internal operation of LED #2 | +| 6 | LED #3 mode | Configuration of the internal operation of LED #3 | +| 7 | LED #4 mode | Configuration of the internal operation of LED #4 | +| 8 | LED #5 mode | Configuration of the internal operation of LED #5 | +| 9 | LED #6 mode | Configuration of the internal operation of LED #6 | +| 10 | Relay mode | This parameter configures the built-in relay | +| 11 | Disable Central Scene notification | Disables or enables the sending of Central Scene notifications | +| 12 | Disable House Cleaning Mode | Disable House Cleaning Mode, double press = 100% light | +| 13 | Multilevel Switch for button #1 | Configuration of the Multilevel Switch | +| 14 | Multilevel Switch for button #2 | Configuration of the Multilevel Switch | +| 15 | Multilevel Switch for button #3 | Configuration of the Multilevel Switch | +| 16 | Multilevel Switch for button #4 | Configuration of the Multilevel Switch | +| 17 | Multilevel Switch for button #5 | Configuration of the Multilevel Switch | +| 18 | Multilevel Switch for button #6 | Configuration of the Multilevel Switch | +| 19 | Association groups for button 1 | Association groups for button 1 | +| 20 | Association groups for button 2 | Association groups for button 2 | +| 21 | Association groups for button 3 | Association groups for button 3 | +| 22 | Association groups for button 4 | Association groups for button 4 | +| 23 | Association groups for button 5 | Association groups for button 5 | +| 24 | Association groups for button 6 | Association groups for button 6 | +| 25 | Backlight control | Configuration of backlight control. | +| 26 | Basic Set for endpoint 0 | Enable or disable that Basic Set commands to the root device | + +### Parameter 1: Upper paddle buttons mode + +Configuration of Pair Mode for the upper two buttons (button #1 and #2) +0 Separate mode (toggle mode). (Default) + +1 In pair mode, left side sends on/up commands, right side sends off/down commands. +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```0```. + +This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```. + + +### Parameter 2: Middle paddle buttons mode + +Configuration of Pair Mode for the middle two buttons (button #3 and #4) +0 Separate mode (toggle mode). (Default) + +1 In pair mode, left side sends on/up commands, right side sends off/down commands. +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```0```. + +This parameter has the configuration ID ```config_2_1``` and is of type ```INTEGER```. + + +### Parameter 3: Lower paddle buttons mode + +Configuration of Pair Mode for the lower two buttons (button #5 and #6) +0 Separate mode (toggle mode). (Default) + +1 In pair mode, left side sends on/up commands, right side sends off/down commands. +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```0```. + +This parameter has the configuration ID ```config_3_1``` and is of type ```INTEGER```. + + +### Parameter 4: LED #1 mode. + +Configuration of the internal operation of LED #1 +0 LED indication is disabled (LED can be controlled by Indicator Command Class Set commands). + +1 LED indicates the status of the corresponding button. (Default) + +2 LED indicates the status of the corresponding button, with inverted indication. + +3 LED indicates the status of corresponding paddle (in pair mode). + +4 LED indicates the status of the corresponding paddle (in pair mode), with inverted indication. + +5 LED indicates the status of the built-in relay. + +6 LED indicates the status of the built-in relay, with inverted indication. + +7 LED show a 5 seconds indication when the corresponding button is pressed. +Values in the range 0 to 7 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_4_1``` and is of type ```INTEGER```. + + +### Parameter 5: LED #2 mode + +Configuration of the internal operation of LED #2 +0 LED indication is disabled (LED can be controlled by Indicator Command Class Set commands). + +1 LED indicates the status of the corresponding button. (Default) + +2 LED indicates the status of the corresponding button, with inverted indication. + +3 LED indicates the status of corresponding paddle (in pair mode). + +4 LED indicates the status of the corresponding paddle (in pair mode), with inverted indication. + +5 LED indicates the status of the built-in relay. + +6 LED indicates the status of the built-in relay, with inverted indication. + +7 LED show a 5 seconds indication when the corresponding button is pressed. +Values in the range 0 to 7 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_5_1``` and is of type ```INTEGER```. + + +### Parameter 6: LED #3 mode + +Configuration of the internal operation of LED #3 +0 LED indication is disabled (LED can be controlled by Indicator Command Class Set commands). + +1 LED indicates the status of the corresponding button. (Default) + +2 LED indicates the status of the corresponding button, with inverted indication. + +3 LED indicates the status of corresponding paddle (in pair mode). + +4 LED indicates the status of the corresponding paddle (in pair mode), with inverted indication. + +5 LED indicates the status of the built-in relay. + +6 LED indicates the status of the built-in relay, with inverted indication. + +7 LED show a 5 seconds indication when the corresponding button is pressed. +Values in the range 0 to 7 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_6_1``` and is of type ```INTEGER```. + + +### Parameter 7: LED #4 mode + +Configuration of the internal operation of LED #4 +0 LED indication is disabled (LED can be controlled by Indicator Command Class Set commands). + +1 LED indicates the status of the corresponding button. (Default) + +2 LED indicates the status of the corresponding button, with inverted indication. + +3 LED indicates the status of corresponding paddle (in pair mode). + +4 LED indicates the status of the corresponding paddle (in pair mode), with inverted indication. + +5 LED indicates the status of the built-in relay. + +6 LED indicates the status of the built-in relay, with inverted indication. + +7 LED show a 5 seconds indication when the corresponding button is pressed. +Values in the range 0 to 7 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_7_1``` and is of type ```INTEGER```. + + +### Parameter 8: LED #5 mode + +Configuration of the internal operation of LED #5 +0 LED indication is disabled (LED can be controlled by Indicator Command Class Set commands). + +1 LED indicates the status of the corresponding button. (Default) + +2 LED indicates the status of the corresponding button, with inverted indication. + +3 LED indicates the status of corresponding paddle (in pair mode). + +4 LED indicates the status of the corresponding paddle (in pair mode), with inverted indication. + +5 LED indicates the status of the built-in relay. + +6 LED indicates the status of the built-in relay, with inverted indication. + +7 LED show a 5 seconds indication when the corresponding button is pressed. +Values in the range 0 to 7 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_8_1``` and is of type ```INTEGER```. + + +### Parameter 9: LED #6 mode + +Configuration of the internal operation of LED #6 +0 LED indication is disabled (LED can be controlled by Indicator Command Class Set commands). + +1 LED indicates the status of the corresponding button. (Default) + +2 LED indicates the status of the corresponding button, with inverted indication. + +3 LED indicates the status of corresponding paddle (in pair mode). + +4 LED indicates the status of the corresponding paddle (in pair mode), with inverted indication. + +5 LED indicates the status of the built-in relay. + +6 LED indicates the status of the built-in relay, with inverted indication. + +7 LED show a 5 seconds indication when the corresponding button is pressed. +Values in the range 0 to 7 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_9_1``` and is of type ```INTEGER```. + + +### Parameter 10: Relay mode + +This parameter configures the built-in relay +0 Relay is disabled. + +1 Relay is controlled by button #1 or by upper paddle when pair mode is active. (Default) + +2 Relay is controlled by button #2 or by upper paddle when pair mode is active. + +3 Relay is controlled by button #3 or by middle paddle when pair mode is active. + +4 Relay is controlled by button #4 or by middle paddle when pair mode is active. + +5 Relay is controlled by button #5 or by lower paddle when pair mode is active. + +6 Relay is controlled by button #6 or by lower paddle when pair mode is active. + +7 Relay is activated for one second and is controlled by button #1 or by upper paddle when pair mode is active. +Values in the range 0 to 7 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_10_1``` and is of type ```INTEGER```. + + +### Parameter 11: Disable Central Scene notification + +Disables or enables the sending of Central Scene notifications +0 Central Scene notifications are enabled. (Default) + +1 Central Scene notifications are disabled. +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```0```. + +This parameter has the configuration ID ```config_11_1``` and is of type ```INTEGER```. + + +### Parameter 12: Disable House Cleaning Mode + +Disable House Cleaning Mode, double press = 100% light +0 House Cleaning Mode is enabled (Default) + +1 House Cleaning Mode is disabled; double-press button scene notifications will be disabled too. +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```0```. + +This parameter has the configuration ID ```config_12_1``` and is of type ```INTEGER```. + + +### Parameter 13: Multilevel Switch for button #1 + +Configuration of the Multilevel Switch +**Byte 1**: Enable / Disable + +0 Disabled – When single pressing the button, nodes associated to group 6 won’t be switched. + +1 Enabled – When single pressing the button, nodes associated to group 6 will be switched between the configured upper and lower switch values. (Default) + +**Byte 2**: Upper switch value + +0 – 99, 255 When single pressing the button for ON, a Multilevel Switch Set with this value will be send to devices in association group 6. (Default = 255) + +**Byte 3**: Lower switch value + +0 - 99 When single pressing the button for OFF, a Multilevel Switch Set with this value will be send to devices in association group 6. (Default = 0) + +**Byte 4**: Not used – must be set to 0. +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_13_4``` and is of type ```INTEGER```. + + +### Parameter 14: Multilevel Switch for button #2 + +Configuration of the Multilevel Switch +**Byte 1**: Enable / Disable + +0 Disabled – When single pressing the button, nodes associated to group 6 won’t be switched. + +1 Enabled – When single pressing the button, nodes associated to group 6 will be switched between the configured upper and lower switch values. (Default) + +**Byte 2**: Upper switch value + +0 – 99, 255 When single pressing the button for ON, a Multilevel Switch Set with this value will be send to devices in association group 6. (Default = 255) + +**Byte 3**: Lower switch value + +0 - 99 When single pressing the button for OFF, a Multilevel Switch Set with this value will be send to devices in association group 6. (Default = 0) + +**Byte 4:** Not used – must be set to 0. +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_14_4``` and is of type ```INTEGER```. + + +### Parameter 15: Multilevel Switch for button #3 + +Configuration of the Multilevel Switch +**Byte 1**: Enable / Disable + +0 Disabled – When single pressing the button, nodes associated to group 6 won’t be switched. + +1 Enabled – When single pressing the button, nodes associated to group 6 will be switched between the configured upper and lower switch values. (Default) + +**Byte 2**: Upper switch value + +0 – 99, 255 When single pressing the button for ON, a Multilevel Switch Set with this value will be send to devices in association group 6. (Default = 255) + +**Byte 3**: Lower switch value + +0 - 99 When single pressing the button for OFF, a Multilevel Switch Set with this value will be send to devices in association group 6. (Default = 0) + +**Byte 4**: Not used – must be set to 0. +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_15_4``` and is of type ```INTEGER```. + + +### Parameter 16: Multilevel Switch for button #4 + +Configuration of the Multilevel Switch +**Byte 1**: Enable / Disable + +0 Disabled – When single pressing the button, nodes associated to group 6 won’t be switched. + +1 Enabled – When single pressing the button, nodes associated to group 6 will be switched between the configured upper and lower switch values. (Default) + +**Byte 2**: Upper switch value + +0 – 99, 255 When single pressing the button for ON, a Multilevel Switch Set with this value will be send to devices in association group 6. (Default = 255) + +**Byte 3**: Lower switch value + +0 - 99 When single pressing the button for OFF, a Multilevel Switch Set with this value will be send to devices in association group 6. (Default = 0) + +**Byte 4**: Not used – must be set to 0. +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_16_4``` and is of type ```INTEGER```. + + +### Parameter 17: Multilevel Switch for button #5 + +Configuration of the Multilevel Switch +**Byte 1**: Enable / Disable + +0 Disabled – When single pressing the button, nodes associated to group 6 won’t be switched. + +1 Enabled – When single pressing the button, nodes associated to group 6 will be switched between the configured upper and lower switch values. (Default) + +**Byte 2**: Upper switch value + +0 – 99, 255 When single pressing the button for ON, a Multilevel Switch Set with this value will be send to devices in association group 6. (Default = 255) + +**Byte 3**: Lower switch value + +0 - 99 When single pressing the button for OFF, a Multilevel Switch Set with this value will be send to devices in association group 6. (Default = 0) + +**Byte 4**: Not used – must be set to 0. +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_17_4``` and is of type ```INTEGER```. + + +### Parameter 18: Multilevel Switch for button #6 + +Configuration of the Multilevel Switch +**Byte 1**: Enable / Disable + +0 Disabled – When single pressing the button, nodes associated to group 6 won’t be switched. + +1 Enabled – When single pressing the button, nodes associated to group 6 will be switched between the configured upper and lower switch values. (Default) + +**Byte 2**: Upper switch value + +0 – 99, 255 When single pressing the button for ON, a Multilevel Switch Set with this value will be send to devices in association group 6. (Default = 255) + +**Byte 3**: Lower switch value + +0 - 99 When single pressing the button for OFF, a Multilevel Switch Set with this value will be send to devices in association group 6. (Default = 0) + +**Byte 4**: Not used – must be set to 0. +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_18_4``` and is of type ```INTEGER```. + + +### Parameter 19: Association groups for button 1 + +Association groups for button 1 +0 When commands are received by device 1, nodes in the association groups will not be switched, button activations will still send switch values. + +1 When commands are received by device 1, nodes in the association groups will be switched. (Default) +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_19_1``` and is of type ```INTEGER```. + + +### Parameter 20: Association groups for button 2 + +Association groups for button 2 +0 When commands are received by device 1, nodes in the association groups will not be switched, button activations will still send switch values. + +1 When commands are received by device 1, nodes in the association groups will be switched. (Default) +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_20_1``` and is of type ```INTEGER```. + + +### Parameter 21: Association groups for button 3 + +Association groups for button 3 +0 When commands are received by device 1, nodes in the association groups will not be switched, button activations will still send switch values. + +1 When commands are received by device 1, nodes in the association groups will be switched. (Default) +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_21_1``` and is of type ```INTEGER```. + + +### Parameter 22: Association groups for button 4 + +Association groups for button 4 +0 When commands are received by device 1, nodes in the association groups will not be switched, button activations will still send switch values. + +1 When commands are received by device 1, nodes in the association groups will be switched. (Default) +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_22_1``` and is of type ```INTEGER```. + + +### Parameter 23: Association groups for button 5 + +Association groups for button 5 +0 When commands are received by device 1, nodes in the association groups will not be switched, button activations will still send switch values. + +1 When commands are received by device 1, nodes in the association groups will be switched. (Default) +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_23_1``` and is of type ```INTEGER```. + + +### Parameter 24: Association groups for button 6 + +Association groups for button 6 +0 When commands are received by device 1, nodes in the association groups will not be switched, button activations will still send switch values. + +1 When commands are received by device 1, nodes in the association groups will be switched. (Default) +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_24_1``` and is of type ```INTEGER```. + + +### Parameter 25: Backlight control + +Configuration of backlight control. +0 Backlight is only controlled by Indicator Command Class – commands send to endpoint 0. + +1 Backlight is turned on for 5 seconds when a button is pressed. (Default) +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_25_1``` and is of type ```INTEGER```. + + +### Parameter 26: Basic Set for endpoint 0 + +Enable or disable that Basic Set commands to the root device +Enable or disable that Basic Set commands to the root device will be able to control the backlight. + +Value Description + +0 Basic Set commands to endpoint 0 is forwarded to endpoint 1 (Default). + +1 Basic Set commands to endpoint 0 controls backlight (on/off). +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```0```. + +This parameter has the configuration ID ```config_26_1``` and is of type ```INTEGER```. + + +## Association Groups + +Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic. + +The Heatit Z-Scene Controller supports 31 association groups. + +### Group 1: Lifeline + + +This group supports 5 nodes. + +### Group 2: Basic Report On/Off button 1 + +Send Basic Report (On/Off) when button #1 is used +This group supports 5 nodes. + +### Group 3: Basic Set On/Off button #1 + +Sends Basic Set (On/Off) when button #1 is used +This group supports 5 nodes. + +### Group 4: Binary Switch Set On/Off button #1 + +Sends Binary Switch Set (On/Off) when button #1 is used +This group supports 5 nodes. + +### Group 5: Binary Toggle Switch Set button #1 + +Send Binary Toggle Switch Set when button #1 is used. +This group supports 5 nodes. + +### Group 6: Multilevel Switch for button #1 + +Sends Multilevel Switch Set / Multilevel Switch Start Level Change / Multilevel Switch Stop Level Change when button #1 is used. +This group supports 5 nodes. + +### Group 7: Basic Report On/Off button 2 + +Send Basic Report (On/Off) when button #2 is used +This group supports 5 nodes. + +### Group 8: Basic Set On/Off button #2 + +Sends Basic Set (On/Off) when button #2 is used +This group supports 5 nodes. + +### Group 9: Binary Switch Set On/Off button #2 + +Sends Binary Switch Set (On/Off) when button #2 is used +This group supports 5 nodes. + +### Group 10: Binary Toggle Switch Set button #2 + +Send Binary Toggle Switch Set when button #2 is used +This group supports 5 nodes. + +### Group 11: Multilevel Switch for button #2 + +Sends Multilevel Switch Set / Multilevel Switch Start Level Change / Multilevel Switch Stop Level Change when button #2 is used. +This group supports 5 nodes. + +### Group 12: Basic Report On/Off button 3 + +Send Basic Report (On/Off) when button #3 is used +This group supports 5 nodes. + +### Group 13: Basic Set On/Off button #3 + +Sends Basic Set (On/Off) when button #3 is used +This group supports 5 nodes. + +### Group 14: Binary Switch Set On/Off button #3 + +Sends Binary Switch Set (On/Off) when button #3 is used +This group supports 5 nodes. + +### Group 15: Binary Toggle Switch Set button #3 + +Send Binary Toggle Switch Set when button #3 is used. +This group supports 5 nodes. + +### Group 16: Multilevel Switch for button #3 + +Sends Multilevel Switch Set / Multilevel Switch Start Level Change / Multilevel Switch Stop Level Change when button #3 is used. +This group supports 5 nodes. + +### Group 17: Basic Report On/Off button 4 + +Send Basic Report (On/Off) when button #4 is used +This group supports 5 nodes. + +### Group 18: Basic Set On/Off button #4 + +Sends Basic Set (On/Off) when button #4 is used +This group supports 5 nodes. + +### Group 19: Binary Switch Set On/Off button #4 + +Sends Binary Switch Set (On/Off) when button #4 is used +This group supports 5 nodes. + +### Group 20: Binary Toggle Switch Set button #4 + +Send Binary Toggle Switch Set when button #4 is used +This group supports 5 nodes. + +### Group 21: Multilevel Switch for button #4 + +Sends Multilevel Switch Set / Multilevel Switch Start Level Change / Multilevel Switch Stop Level Change when button #4 is used. +This group supports 5 nodes. + +### Group 22: Basic Report On/Off button #5 + +Sends Basic Report (On/Off) when button #5 is used +This group supports 5 nodes. + +### Group 23: Basic Set On/Off button #5 + +Sends Basic Set (On/Off) when button #5 is used +This group supports 5 nodes. + +### Group 24: Binary Switch Set On/Off button #5 + +Sends Binary Switch Set (On/Off) when button #5 is used +This group supports 5 nodes. + +### Group 25: Binary Toggle Switch Set button #5 + +Send Binary Toggle Switch Set when button #5 is used +This group supports 5 nodes. + +### Group 26: Multilevel Switch for button #5 + +Sends Multilevel Switch Set / Multilevel Switch Start Level Change / Multilevel Switch Stop Level Change when button #5 is used. +This group supports 5 nodes. + +### Group 27: Basic Report On/Off button 6 + +Send Basic Report (On/Off) when button #6 is used +This group supports 5 nodes. + +### Group 28: Basic Set On/Off button #6 + +Sends Basic Set (On/Off) when button #6 is used +This group supports 5 nodes. + +### Group 29: Binary Switch Set On/Off button #6 + +Sends Binary Switch Set (On/Off) when button #6 is used +This group supports 5 nodes. + +### Group 30: Binary Toggle Switch Set button #6 + +Send Binary Toggle Switch Set when button #6 is used +This group supports 5 nodes. + +### Group 31: Multilevel Switch for button #6 + +Sends Multilevel Switch Set / Multilevel Switch Start Level Change / Multilevel Switch Stop Level Change when button #6 is used. +This group supports 5 nodes. + +## Technical Information + +### Endpoints + +#### Endpoint 0 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_SWITCH_BINARY_V1| | +| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| | +| COMMAND_CLASS_SWITCH_TOGGLE_BINARY_V1| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| | +| COMMAND_CLASS_CENTRAL_SCENE_V2| | +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_MULTI_CHANNEL_V2| | +| COMMAND_CLASS_CONFIGURATION_V1| | +| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| | +| COMMAND_CLASS_POWERLEVEL_V1| | +| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_VERSION_V2| | +| COMMAND_CLASS_INDICATOR_V1| | +| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | +#### Endpoint 1 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_SWITCH_BINARY_V1| | +| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| | +| COMMAND_CLASS_SWITCH_TOGGLE_BINARY_V1| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_INDICATOR_V1| | +| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | +#### Endpoint 2 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_SWITCH_BINARY_V1| | +| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| | +| COMMAND_CLASS_SWITCH_TOGGLE_BINARY_V1| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_INDICATOR_V1| | +| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | +#### Endpoint 3 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_SWITCH_BINARY_V1| | +| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| | +| COMMAND_CLASS_SWITCH_TOGGLE_BINARY_V1| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_INDICATOR_V1| | +| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | +#### Endpoint 4 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_SWITCH_BINARY_V1| | +| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| | +| COMMAND_CLASS_SWITCH_TOGGLE_BINARY_V1| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_INDICATOR_V1| | +| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | +#### Endpoint 5 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_SWITCH_BINARY_V1| | +| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| | +| COMMAND_CLASS_SWITCH_TOGGLE_BINARY_V1| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_INDICATOR_V1| | +| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | +#### Endpoint 6 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_SWITCH_BINARY_V1| | +| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| | +| COMMAND_CLASS_SWITCH_TOGGLE_BINARY_V1| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_INDICATOR_V1| | +| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | + +### Documentation Links + +* [Manual](https://www.cd-jackson.com/zwave_device_uploads/846/manualmultiregzwavescenecontroller.pdf) + +--- + +Did you spot an error in the above definition or want to improve the content? +You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/846). diff --git a/_addons_bindings/zwave/doc/mcohome/mh9co2wd_0_0.md b/_addons_bindings/zwave/doc/mcohome/mh9co2wd_0_0.md index f22d25ea82..ef8b68cbe0 100644 --- a/_addons_bindings/zwave/doc/mcohome/mh9co2wd_0_0.md +++ b/_addons_bindings/zwave/doc/mcohome/mh9co2wd_0_0.md @@ -11,7 +11,7 @@ This describes the Z-Wave device *MH9-CO2-WD*, manufactured by *[McoHome Technol ![MH9-CO2-WD product image](https://www.cd-jackson.com/zwave_device_uploads/455/455_default.png) -The MH9-CO2-WD does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The MH9-CO2-WD does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -64,6 +64,11 @@ If a node ID displays, it means the device is already in a Z-Wave network. To press K2 once can remove it from the network. “- - -” displays and press K1 once can return to normal work. +### Wakeup Information + +The MH9-CO2-WD does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the MH9-CO2-WD -: diff --git a/_addons_bindings/zwave/doc/mcohome/mhs311_0_0.md b/_addons_bindings/zwave/doc/mcohome/mhs311_0_0.md index 1357194d2b..af10399d4c 100644 --- a/_addons_bindings/zwave/doc/mcohome/mhs311_0_0.md +++ b/_addons_bindings/zwave/doc/mcohome/mhs311_0_0.md @@ -27,10 +27,6 @@ Press and hold any key on the panel for 8 seconds. If inclusion is successful, a Press and hold any key on the panel for 8 seconds. If the exclusion is successful, all INDICATION LEDs on the panel will turn orange, and all switches will turn off. The exclusion will delete all association data. -### Wakeup Information - -Same as inclusion - ## Channels The following table summarises the channels available for the MH-S311H -: diff --git a/_addons_bindings/zwave/doc/mcohome/mhs511il_0_0.md b/_addons_bindings/zwave/doc/mcohome/mhs511il_0_0.md index 02d2cc15db..5ea12a5afd 100644 --- a/_addons_bindings/zwave/doc/mcohome/mhs511il_0_0.md +++ b/_addons_bindings/zwave/doc/mcohome/mhs511il_0_0.md @@ -11,12 +11,15 @@ This describes the Z-Wave device *MH-S511-IL*, manufactured by *[McoHome Technol ![MH-S511-IL product image](https://www.cd-jackson.com/zwave_device_uploads/690/690_default.png) -The MH-S511-IL does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The MH-S511-IL does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/690) to improve the documentation. +### Wakeup Information +The MH-S511-IL does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the MH-S511-IL -: diff --git a/_addons_bindings/zwave/doc/mcohome/mhs512il_0_0.md b/_addons_bindings/zwave/doc/mcohome/mhs512il_0_0.md index 58af7a34d1..15882f3111 100644 --- a/_addons_bindings/zwave/doc/mcohome/mhs512il_0_0.md +++ b/_addons_bindings/zwave/doc/mcohome/mhs512il_0_0.md @@ -11,12 +11,15 @@ This describes the Z-Wave device *MH-S512-IL*, manufactured by *[McoHome Technol ![MH-S512-IL product image](https://www.cd-jackson.com/zwave_device_uploads/691/691_default.png) -The MH-S512-IL does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The MH-S512-IL does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/691) to improve the documentation. +### Wakeup Information +The MH-S512-IL does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the MH-S512-IL -: diff --git a/_addons_bindings/zwave/doc/mcohome/mhs521_0_0.md b/_addons_bindings/zwave/doc/mcohome/mhs521_0_0.md index aafe8fb93d..c16bfe10ce 100644 --- a/_addons_bindings/zwave/doc/mcohome/mhs521_0_0.md +++ b/_addons_bindings/zwave/doc/mcohome/mhs521_0_0.md @@ -8,12 +8,15 @@ title: MH-S521 - ZWave # MH-S521 Shutter Panel This describes the Z-Wave device *MH-S521*, manufactured by *[McoHome Technology Co., Ltd](http://www.mcohome.com/)* with the thing type UID of ```mcohome_mhs521_00_000```. -The MH-S521 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The MH-S521 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/722) to improve the documentation. +### Wakeup Information +The MH-S521 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the MH-S521 -: diff --git a/_addons_bindings/zwave/doc/merten/506219_0_0.md b/_addons_bindings/zwave/doc/merten/506219_0_0.md index 8bba363a6b..60049fa7c8 100644 --- a/_addons_bindings/zwave/doc/merten/506219_0_0.md +++ b/_addons_bindings/zwave/doc/merten/506219_0_0.md @@ -10,7 +10,7 @@ This describes the Z-Wave device *506219*, manufactured by *Merten* with the thi The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. -The 506219 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The 506219 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -38,6 +38,11 @@ Triple click on operating surface Wait until the red LED D goes out. Used to ide Triple click on operating surface LED flashes approx. 6 seconds. Used for include/exclude the device by the primary +### Wakeup Information + +The 506219 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the 506219 -: diff --git a/_addons_bindings/zwave/doc/merten/507900_0_0.md b/_addons_bindings/zwave/doc/merten/507900_0_0.md index e9e5937897..3620b890c9 100644 --- a/_addons_bindings/zwave/doc/merten/507900_0_0.md +++ b/_addons_bindings/zwave/doc/merten/507900_0_0.md @@ -29,10 +29,6 @@ Teaching (transmits Node info frame), see CONNECT radio system description Reset to the factory settings; de- lete everything taught -### Wakeup Information - -Triple click on the switch button - ## Channels The following table summarises the channels available for the 507900 -: diff --git a/_addons_bindings/zwave/doc/merten/5082xx_0_0.md b/_addons_bindings/zwave/doc/merten/5082xx_0_0.md index 1a1dc6d50c..7c5e55513f 100644 --- a/_addons_bindings/zwave/doc/merten/5082xx_0_0.md +++ b/_addons_bindings/zwave/doc/merten/5082xx_0_0.md @@ -8,12 +8,15 @@ title: 5082xx - ZWave # 5082xx Battery Powered Wall Controller MOVE This describes the Z-Wave device *5082xx*, manufactured by *Merten* with the thing type UID of ```merten_5082xx_00_000```. -The 5082xx does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The 5082xx does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/59) to improve the documentation. +### Wakeup Information +The 5082xx does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the 5082xx -: diff --git a/_addons_bindings/zwave/doc/merten/50x5xx_0_0.md b/_addons_bindings/zwave/doc/merten/50x5xx_0_0.md index 6de0baa6bb..82b88cbf2f 100644 --- a/_addons_bindings/zwave/doc/merten/50x5xx_0_0.md +++ b/_addons_bindings/zwave/doc/merten/50x5xx_0_0.md @@ -10,23 +10,28 @@ This describes the Z-Wave device *50x5xx*, manufactured by *Merten* with the thi The device is in the category of *Blinds*, defining Roller shutters, window blinds, etc.. +![50x5xx product image](https://www.cd-jackson.com/zwave_device_uploads/57/57_default.jpg) + + The 50x5xx supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. ## Overview +The roller shutter push-button contains a radio receiver for the Merten CONNECT radio system. If you use the blind control inserts 580699 or 580698, you can operate the connected roller shutter drive remotely using a Merten CONNECT radio transmitter. You can also operate the roller shutters using the rocker on the roller shutter push-button. + +You can use the Merten CONNECT radio button, the Merten CONNECT radio remote control or the Merten CONNECT radio central unit as the transmitter. + ### Inclusion Information Program (transmits Node info frame) -Triple click on operating surface. Used for -include/exclude the device by the primary +Triple click on operating surface. Used for include/exclude the device by the primary ### Exclusion Information Reset to the factory settings; exclude -Triple click on operating surface. Used for -include/exclude the device by the primary +Triple click on operating surface. Used for include/exclude the device by the primary ## Channels @@ -34,18 +39,17 @@ The following table summarises the channels available for the 50x5xx -: | Channel | Channel Id | Category | Item Type | |---------|------------|----------|-----------| -| Dimmer | switch_dimmer | DimmableLight | Dimmer | +| Blinds Control | blinds_control | Blinds | Rollershutter | | Sensor (luminance) | sensor_luminance | Temperature | Number | | Dimmer 1 | switch_dimmer1 | DimmableLight | Dimmer | | Sensor (luminance) 1 | sensor_luminance1 | Temperature | Number | | Dimmer 2 | switch_dimmer2 | DimmableLight | Dimmer | -### Dimmer +### Blinds Control -The brightness channel allows to control the brightness of a light. - It is also possible to switch the light on and off. +Provides start / stop control of blinds. -The ```switch_dimmer``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. +The ```blinds_control``` channel supports the ```Rollershutter``` item and is in the ```Blinds``` category. ### Sensor (luminance) diff --git a/_addons_bindings/zwave/doc/monoprice/10795_0_0.md b/_addons_bindings/zwave/doc/monoprice/10795_0_0.md index 75242da608..7309b6ef4d 100644 --- a/_addons_bindings/zwave/doc/monoprice/10795_0_0.md +++ b/_addons_bindings/zwave/doc/monoprice/10795_0_0.md @@ -12,12 +12,15 @@ The device is in the category of *Door*, defining Door sensors. The 10795 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The 10795 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The 10795 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/817) to improve the documentation. +### Wakeup Information +The 10795 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the 10795 -: diff --git a/_addons_bindings/zwave/doc/nexia/db100z_0_0.md b/_addons_bindings/zwave/doc/nexia/db100z_0_0.md index 9319f70eab..7910bdecde 100644 --- a/_addons_bindings/zwave/doc/nexia/db100z_0_0.md +++ b/_addons_bindings/zwave/doc/nexia/db100z_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Door*, defining Door sensors. The DB100Z supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The DB100Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The DB100Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/309) to improve the documentation. +### Wakeup Information +The DB100Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the DB100Z -: diff --git a/_addons_bindings/zwave/doc/nodon/crc3100_0_0.md b/_addons_bindings/zwave/doc/nodon/crc3100_0_0.md index d96ce326cf..36b198a008 100644 --- a/_addons_bindings/zwave/doc/nodon/crc3100_0_0.md +++ b/_addons_bindings/zwave/doc/nodon/crc3100_0_0.md @@ -13,7 +13,7 @@ The device is in the category of *Remote Control*, defining Any portable or hand ![CRC-3100 product image](https://www.cd-jackson.com/zwave_device_uploads/249/249_default.jpg) -The CRC-3100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The CRC-3100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -35,6 +35,11 @@ Push on circle button within 10 seconds. The LED blinks in pink to confirm your choice The LED blinks in green to confirm the procedure +### Wakeup Information + +The CRC-3100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the CRC-3100 -: diff --git a/_addons_bindings/zwave/doc/nodon/cws3101_0_0.md b/_addons_bindings/zwave/doc/nodon/cws3101_0_0.md index c7cb219925..f7e564d240 100644 --- a/_addons_bindings/zwave/doc/nodon/cws3101_0_0.md +++ b/_addons_bindings/zwave/doc/nodon/cws3101_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *CWS-3101*, manufactured by *[ID-RF](http://www The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. -The CWS-3101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The CWS-3101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/294) to improve the documentation. +### Wakeup Information +The CWS-3101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the CWS-3101 -: diff --git a/_addons_bindings/zwave/doc/nodon/softremote_0_0.md b/_addons_bindings/zwave/doc/nodon/softremote_0_0.md index da149fbc1e..31b8fe2ef5 100644 --- a/_addons_bindings/zwave/doc/nodon/softremote_0_0.md +++ b/_addons_bindings/zwave/doc/nodon/softremote_0_0.md @@ -8,12 +8,15 @@ title: Soft Remote - ZWave # Soft Remote Remote Control This describes the Z-Wave device *Soft Remote*, manufactured by *[ID-RF](http://www.nodon.fr/)* with the thing type UID of ```nodon_softremote_00_000```. -The Soft Remote does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Soft Remote does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/250) to improve the documentation. +### Wakeup Information +The Soft Remote does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the Soft Remote -: diff --git a/_addons_bindings/zwave/doc/northq/nq9021_0_0.md b/_addons_bindings/zwave/doc/northq/nq9021_0_0.md index 99fa1e2b2c..6d785e51f3 100644 --- a/_addons_bindings/zwave/doc/northq/nq9021_0_0.md +++ b/_addons_bindings/zwave/doc/northq/nq9021_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *NQ-9021*, manufactured by *NorthQ* with the th The NQ-9021 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The NQ-9021 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The NQ-9021 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/180) to improve the documentation. +### Wakeup Information +The NQ-9021 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the NQ-9021 -: diff --git a/_addons_bindings/zwave/doc/northq/nq9121_3_0.md b/_addons_bindings/zwave/doc/northq/nq9121_3_0.md index 94cab277d7..c3588d4df1 100644 --- a/_addons_bindings/zwave/doc/northq/nq9121_3_0.md +++ b/_addons_bindings/zwave/doc/northq/nq9121_3_0.md @@ -14,7 +14,7 @@ This version of the device is limited to firmware version 3.0 The NQ-9121 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The NQ-9121 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The NQ-9121 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -32,6 +32,10 @@ In order to exclude the Power/Gas Reader from a Z-Wave network, place the contro ### Wakeup Information +The NQ-9121 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + The Power Reader has two functioning modes: \- Real-time mode: the device will be awake and keep the antenna on. It will stay in real-time a predefined number of seconds (900). diff --git a/_addons_bindings/zwave/doc/oomi/ft098_0_0.md b/_addons_bindings/zwave/doc/oomi/ft098_0_0.md index e897d951d2..471aeddb03 100644 --- a/_addons_bindings/zwave/doc/oomi/ft098_0_0.md +++ b/_addons_bindings/zwave/doc/oomi/ft098_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Light Bulb*, defining Devices that illuminate The FT098 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The FT098 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The FT098 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -42,6 +42,10 @@ Your Bulb can be removed from your Z-Wave network at any time. You'll need to us ### Wakeup Information +The FT098 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + To check if LED Bulb is already paired to an existing network, toggle the wall switch off and on 3 times fast (the final ending position of the wall switch must be on). If LED Bulb blinks orange for 3 seconds, it is already paired into a Z-Wave network. ## Channels diff --git a/_addons_bindings/zwave/doc/oomi/ft130_0_0.md b/_addons_bindings/zwave/doc/oomi/ft130_0_0.md new file mode 100644 index 0000000000..87b1a2f607 --- /dev/null +++ b/_addons_bindings/zwave/doc/oomi/ft130_0_0.md @@ -0,0 +1,342 @@ +--- +layout: documentation +title: FT130 - ZWave +--- + +{% include base.html %} + +# FT130 Wall-mount four Button +This describes the Z-Wave device *FT130*, manufactured by *[Fantem](http://www.oomi.com/)* with the thing type UID of ```oomi_ft130_00_000```. + +The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. + +![FT130 product image](https://www.cd-jackson.com/zwave_device_uploads/860/860_default.jpg) + + +The FT130 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. + +The FT130 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. + +## Overview + +Fantem WallMote Quad is an intelligent Z-Wave remote controller that mounted on a wall. It has 4 touch buttons that you can easily control the Z-Wave devices in your home network via touching, long pressing or sliding the button areas. Its surface has a RGB LED to indicate the button actions also accompanied by touch beep and vibration. The WallMote Quad is also a security Z-Wave device and supports Over The Air (OTA) feature for the products firmware upgrade. + +### Inclusion Information + +**Including Fantem** **WallMote Quad as a non-secure device:** + +If you want your WallMote Quad as a non-security device in your Z-wave network, you just need to press the Action Button once on WallMote Quad when you use a controller/gateway to add/include it. The green LED will be on for 2 seconds and then the orange LED will fast blink for 10 minutes (if the WallMote Quad does not receive the Wake Up No More Info command from primary Controller) to indicate the inclusion is successful + +**Including Fantem** **WallMote Quad as a secure device:** + +In order to take full advantage of all functionality the WallMote Quad, you may want your WallMote Quad is a security device that uses secure/encrypted message to communicate in Z-wave network, so a security enabled controller/gateway is needed for the WallMote Quad to be used as a security device. You need to press the WallMote Quad’s Action Button 2 times within 1 second when your security controller/gateway starts the network inclusion. The blue LED will be on for 2 seconds and then the orange LED will fast blink for 10 minutes (if the WallMote Quad does not receive the Wake Up No More Info command from primary Controller) to indicate the inclusion is successful. + +### Exclusion Information + +Your WallMote Quad can be removed from your Z-Wave network at any time. You'll need to use your Z-Wave network's main controller/ gateway. To do this, please refer to the part of their respective manuals that tell you how to remove devices from your network. + +Put your primary controller into device removal mode. + +Unlock your WallMote Quad from the Back Mount plate and take the WallMote Quad unit near to your primary controller. + +Press the Action Button on your WallMote Quad. + +If your WallMote Quad is successfully removed from the Z-Wave network, the LED will become a colourful gradient for a few seconds and then turn off. If the removing was unsuccessful, the red LED will be solid for 2 seconds and then turn off, repeat the above steps. + +### Wakeup Information + +The FT130 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + +In order to send your WallMote Quad new configuration commands from your Z-Wave controller or gateway, it will need to be woken up. + +## Channels + +The following table summarises the channels available for the FT130 -: + +| Channel | Channel Id | Category | Item Type | +|---------|------------|----------|-----------| +| Scene Number | scene_number | | Number | +| Alarm (power) | alarm_power | Door | Switch | +| Battery Level | battery-level | Battery | Number | + +### Scene Number + +Triggers when a scene button is pressed. + +The ```scene_number``` channel supports the ```Number``` item. + +### Alarm (power) + +Indicates if a power alarm is triggered. + +The ```alarm_power``` channel supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device. + +The following state translation is provided for this channel to the ```Switch``` item type -: + +| Value | Label | +|-------|-----------| +| OFF | Ok | +| ON | Alarm | + +### Battery Level + +Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading. + +The ```battery-level``` channel supports the ```Number``` item and is in the ```Battery``` category. + + + +## Device Configuration + +The following table provides a summary of the 6 configuration parameters available in the FT130. +Detailed information on each parameter can be found in the sections below. + +| Param | Name | Description | +|-------|-------|-------------| +| 1 | Touch sound | Enable/disable the touch sound. | +| 2 | Touch vibration | Enable/disable the touch vibration. | +| 3 | Button slide | Enable/disable the function of button slide. | +| 4 | Notification report | Which notification to be sent to the associated devices. | +| 39 | Low battery value | Set the low battery value | +| 255 | Reset the WallMote Quad | Reset the WallMote Quad to factory default. | +| | Wakeup Interval | Sets the interval at which the device will accept commands from the controller | +| | Wakeup Node | Sets the node ID of the device to receive the wakeup notifications | + +### Parameter 1: Touch sound + +Enable/disable the touch sound. + +The following option values may be configured -: + +| Value | Description | +|--------|-------------| +| 0 | Disable | +| 1 | Enable | + +The manufacturer defined default value is ```1``` (Enable). + +This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```. + + +### Parameter 2: Touch vibration + +Enable/disable the touch vibration. + +The following option values may be configured -: + +| Value | Description | +|--------|-------------| +| 0 | Disable | +| 1 | Enable | + +The manufacturer defined default value is ```1``` (Enable). + +This parameter has the configuration ID ```config_2_1``` and is of type ```INTEGER```. + + +### Parameter 3: Button slide + +Enable/disable the function of button slide. + +The following option values may be configured -: + +| Value | Description | +|--------|-------------| +| 0 | Disable | +| 1 | Enable | + +The manufacturer defined default value is ```1``` (Enable). + +This parameter has the configuration ID ```config_3_1``` and is of type ```INTEGER```. + + +### Parameter 4: Notification report + +Which notification to be sent to the associated devices. +To set which notification would be sent to the associated devices 3, slide functionality on the buttons is activated. +The following option values may be configured -: + +| Value | Description | +|--------|-------------| +| 1 | Central scene | +| 3 | Central scene and config | + +The manufacturer defined default value is ```1``` (Central scene). + +This parameter has the configuration ID ```config_4_1``` and is of type ```INTEGER```. + + +### Parameter 39: Low battery value + +Set the low battery value + +Values in the range 0 to 50 may be set. + +The manufacturer defined default value is ```5```. + +This parameter has the configuration ID ```config_39_1``` and is of type ```INTEGER```. + + +### Parameter 255: Reset the WallMote Quad + +Reset the WallMote Quad to factory default. + +The following option values may be configured -: + +| Value | Description | +|--------|-------------| +| 0 | Reset to factory default | +| 1431655765 | Reset and remove | + +The manufacturer defined default value is ```0``` (Reset to factory default). + +This parameter has the configuration ID ```config_255_4``` and is of type ```INTEGER```. + +### Wakeup Interval + +The wakeup interval sets the period at which the device will listen for messages from the controller. This is required for battery devices that sleep most of the time in order to conserve battery life. The device will wake up at this interval and send a message to the controller to tell it that it can accept messages - after a few seconds, it will go back to sleep if there is no further communications. + +This setting is defined in *seconds*. It is advisable not to set this interval too short or it could impact battery life. A period of 1 hour (3600 seconds) is suitable in most instances. + +Note that this setting does not affect the devices ability to send sensor data, or notification events. + +This parameter has the configuration ID ```wakeup_interval``` and is of type ```INTEGER```. + +### Wakeup Node + +When sleeping devices wake up, they send a notification to a listening device. Normally, this device is the network controller, and normally the controller will set this automatically to its own address. +In the event that the network contains multiple controllers, it may be necessary to configure this to a node that is not the main controller. This is an advanced setting and should not be changed without a full understanding of the impact. + +This parameter has the configuration ID ```wakeup_node``` and is of type ```INTEGER```. + + +## Association Groups + +Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic. + +The FT130 supports 9 association groups. + +### Group 1: Lifeline + +Central Scene Notification +This group supports 2 nodes. + +### Group 2: Button 1 basic + +On/off control via button 1 +This group supports 5 nodes. + +### Group 3: Button 1 multilevel + +Dim control via button 1 +This group supports 5 nodes. + +### Group 4: Button 2 basic + +On/off control via button 2 +This group supports 5 nodes. + +### Group 5: Button 2 multilevel + +Dim control via button 2 +This group supports 5 nodes. + +### Group 6: Button 3 basic + +On/off control via button 3 +This group supports 5 nodes. + +### Group 7: Button 3 multilevel + +Dim control via button 3 +This group supports 5 nodes. + +### Group 8: Button 4 basic + +On/off control via button 4 +This group supports 5 nodes. + +### Group 9: Button 4 multilevel + +Dim control via button 4 +This group supports 5 nodes. + +## Technical Information + +### Endpoints + +#### Endpoint 0 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_NO_OPERATION_V1| | +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_SWITCH_MULTILEVEL_V0| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| | +| COMMAND_CLASS_CENTRAL_SCENE_V2| Linked to BASIC| +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_MULTI_CHANNEL_V2| | +| COMMAND_CLASS_CONFIGURATION_V1| | +| COMMAND_CLASS_ALARM_V4| | +| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| | +| COMMAND_CLASS_POWERLEVEL_V1| | +| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| | +| COMMAND_CLASS_BATTERY_V1| | +| COMMAND_CLASS_WAKE_UP_V2| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_VERSION_V2| | +| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | +#### Endpoint 1 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_SWITCH_MULTILEVEL_V0| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_CENTRAL_SCENE_V0| Linked to BASIC| +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | +#### Endpoint 2 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_CENTRAL_SCENE_V0| Linked to BASIC| +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | +#### Endpoint 3 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_CENTRAL_SCENE_V0| Linked to BASIC| +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | +#### Endpoint 4 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_CENTRAL_SCENE_V0| Linked to BASIC| +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | + +### Documentation Links + +* [FT130-C Manual Part1](https://www.cd-jackson.com/zwave_device_uploads/860/FT130-C-Manual-Part1.pdf) +* [FT130-C Manual Part2](https://www.cd-jackson.com/zwave_device_uploads/860/FT130-C-Manual-Part2.pdf) + +--- + +Did you spot an error in the above definition or want to improve the content? +You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/860). diff --git a/_addons_bindings/zwave/doc/philio/pab01_0_0.md b/_addons_bindings/zwave/doc/philio/pab01_0_0.md index cd0bd56375..a752c36caf 100644 --- a/_addons_bindings/zwave/doc/philio/pab01_0_0.md +++ b/_addons_bindings/zwave/doc/philio/pab01_0_0.md @@ -11,12 +11,15 @@ This describes the Z-Wave device *ZIP-PAB01*, manufactured by *[Philio Technolog ![ZIP-PAB01 product image](https://www.cd-jackson.com/zwave_device_uploads/560/560_default.jpg) -The ZIP-PAB01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZIP-PAB01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/560) to improve the documentation. +### Wakeup Information +The ZIP-PAB01 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZIP-PAB01 -: diff --git a/_addons_bindings/zwave/doc/philio/pan061b_1_8.md b/_addons_bindings/zwave/doc/philio/pan061b_1_8.md deleted file mode 100644 index 721f307be0..0000000000 --- a/_addons_bindings/zwave/doc/philio/pan061b_1_8.md +++ /dev/null @@ -1,317 +0,0 @@ ---- -layout: documentation -title: PAN06-1B - ZWave ---- - -{% include base.html %} - -# PAN06-1B In Wall Dual Relay(1 Way) Switch Module 2 x 1.5kW -This describes the Z-Wave device *PAN06-1B*, manufactured by *[Philio Technology Corp](http://www.philio-tech.com/)* with the thing type UID of ```philio_pan061b_01_008```. -This version of the device is limited to firmware versions above 1.8 - -The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. - -![PAN06-1B product image](https://www.cd-jackson.com/zwave_device_uploads/858/858_default.png) - - -The PAN06-1B supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. - -## Overview - -The PAN06 allows controlling two independent loads both wirelessly via Z-Wave and locally utilizing a traditional wall switch. Thanks to its calibration technology the device cannot only be used to switch resistive devices but also works perfectly with many kind of reactive or resistive loads such as fluorescent lights or LEDs. -The device is placed in a wall box right behind the normal switch. The switch is not longer directly -connected to the load but acts as input device for the insert that is controlling the load. This device is -designed for a 3 wire system and needs a neutral wire in the wall box. - -### Inclusion Information - -1\. Have Z-Wave Controller entered inclusion mode. -2\. Pressing Include button of PAN06 three times within 2 seconds will enter inclusion mode - -### Exclusion Information - -1\. Have Z-Wave Controller entered exclusion mode. -2\. Pressing Include button of PAN06 three times within 2 seconds will enter exclusion mode - -## Channels - -The following table summarises the channels available for the PAN06-1B -: - -| Channel | Channel Id | Category | Item Type | -|---------|------------|----------|-----------| -| Switch | switch_binary | Switch | Switch | -| Scene Number | scene_number | | Number | -| Alarm | alarm_general | Door | Switch | -| Battery Level | battery-level | Battery | Number | -| Switch 1 | switch_binary1 | Switch | Switch | -| Switch 2 | switch_binary2 | Switch | Switch | -| Switch 3 | switch_binary3 | Switch | Switch | - -### Switch - -Switch the power on and off. - -The ```switch_binary``` channel supports the ```Switch``` item and is in the ```Switch``` category. - -### Scene Number - -Triggers when a scene button is pressed. - -The ```scene_number``` channel supports the ```Number``` item. - -### Alarm - -Indicates if an alarm is triggered. - -The ```alarm_general``` channel supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device. - -The following state translation is provided for this channel to the ```Switch``` item type -: - -| Value | Label | -|-------|-----------| -| OFF | Ok | -| ON | Alarm | - -### Battery Level - -Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading. - -The ```battery-level``` channel supports the ```Number``` item and is in the ```Battery``` category. - -### Switch 1 - -Switch the power on and off. - -The ```switch_binary1``` channel supports the ```Switch``` item and is in the ```Switch``` category. - -### Switch 2 - -Switch the power on and off. - -The ```switch_binary2``` channel supports the ```Switch``` item and is in the ```Switch``` category. - -### Switch 3 - -Switch the power on and off. - -The ```switch_binary3``` channel supports the ```Switch``` item and is in the ```Switch``` category. - - - -## Device Configuration - -The following table provides a summary of the 6 configuration parameters available in the PAN06-1B. -Detailed information on each parameter can be found in the sections below. - -| Param | Name | Description | -|-------|-------|-------------| -| 1 | Selected endpoint | Send Basic Command Class | -| 2 | Switch mode | Change the external switch mode | -| 3 | Restore Switch State Mode | Switch state after repowering | -| 4 | Auto OFF Timer | | -| 5 | RF OFF command | RF OFF command mode | -| 6 | Existence of endpoint 3 | | -| | Switch All Mode | Set the mode for the switch when receiving SWITCH ALL commands | - -### Parameter 1: Selected endpoint - -Send Basic Command Class -If Controller not using Multi\_Channel command class to access the endpoint of PAN06, you may configure the endpoint value to react the Basic Command Class -The following option values may be configured -: - -| Value | Description | -|--------|-------------| -| 1 | Relay 1 | -| 2 | Relay 2 | -| 3 | Relay 1+2 | - -The manufacturer defined default value is ```3``` (Relay 1+2). - -This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```. - - -### Parameter 2: Switch mode - -Change the external switch mode - -The following option values may be configured -: - -| Value | Description | -|--------|-------------| -| 1 | Edge mode | -| 2 | Pulse mode | -| 3 | Edge-Toggle mode | - -The manufacturer defined default value is ```1``` (Edge mode). - -This parameter has the configuration ID ```config_2_1``` and is of type ```INTEGER```. - - -### Parameter 3: Restore Switch State Mode - -Switch state after repowering -0 : Switch off -1 : Last switch state -2 : Switch on - -Whenever the AC power return from lost, PAN06 will restore the switch state which -could be SWITCH OFF、 LAST SWITCH STATE、 SWITCH ON. The default setting is -LAST SWITCH STATE -The following option values may be configured -: - -| Value | Description | -|--------|-------------| -| 0 | Switch OFF | -| 1 | Last Switch state | -| 2 | Switch ON | - -The manufacturer defined default value is ```1``` (Last Switch state). - -This parameter has the configuration ID ```config_3_1``` and is of type ```INTEGER```. - - -### Parameter 4: Auto OFF Timer - - - -Values in the range 0 to 32767 may be set. - -The manufacturer defined default value is ```0```. - -This parameter has the configuration ID ```config_4_2``` and is of type ```INTEGER```. - - -### Parameter 5: RF OFF command - -RF OFF command mode -Whenever a switch off command, BASIC\_SET 、BINARY\_SWITCH\_SET 、 -SWITCH\_ALL\_OFF, is received, it could be interpreted as 4 variety of commands. -3-5-1 Switch Off：It switches to OFF state. The default setting is Switch Off. -3-5-2 Ignore：The switch off command will be ignored. -3-5-3 Switch Toggle：It switches to the inverse of current state. -3-5-4 Switch On：It switches to ON state. - -0 : Switch off -1 : Ignore -2 : Switch toggle -3 : Switch on -The following option values may be configured -: - -| Value | Description | -|--------|-------------| -| 0 | Switch OFF | -| 1 | Ignore | -| 2 | Switch toggle | -| 3 | Switch on | - -The manufacturer defined default value is ```0``` (Switch OFF). - -This parameter has the configuration ID ```config_5_1``` and is of type ```INTEGER```. - - -### Parameter 6: Existence of endpoint 3 - - - -The following option values may be configured -: - -| Value | Description | -|--------|-------------| -| 1 | Endpoint 3 exists | -| 2 | No endpoint 3 | - -The manufacturer defined default value is ```1``` (Endpoint 3 exists). - -This parameter has the configuration ID ```config_6_1``` and is of type ```INTEGER```. - -### Switch All Mode - -Set the mode for the switch when receiving SWITCH ALL commands. - -The following option values may be configured -: -| Value | Description | -|--------|-------------| -| 0 | Exclude from All On and All Off groups | -| 1 | Include in All On group | -| 2 | Include in All Off group | -| 255 | Include in All On and All Off groups | - -This parameter has the configuration ID ```switchall_mode``` and is of type ```INTEGER```. - - -## Association Groups - -Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic. - -The PAN06-1B supports 3 association groups. - -### Group 1: Relay 1 + 2 - - -This group supports 1 nodes. - -### Group 2: Relay 1 - - -This group supports 1 nodes. - -### Group 3: Relay 2 - - -This group supports 1 nodes. - -## Technical Information - -### Endpoints - -#### Endpoint 0 - -| Command Class | Comment | -|---------------|---------| -| COMMAND_CLASS_NO_OPERATION_V1| | -| COMMAND_CLASS_BASIC_V0| | -| COMMAND_CLASS_SWITCH_BINARY_V1| | -| COMMAND_CLASS_SWITCH_ALL_V1| | -| COMMAND_CLASS_SCENE_ACTIVATION_V1| | -| COMMAND_CLASS_SCENE_ACTUATOR_CONF_V1| | -| COMMAND_CLASS_SENSOR_MULTILEVEL_V0| | -| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | -| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| | -| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | -| COMMAND_CLASS_MULTI_CHANNEL_V2| | -| COMMAND_CLASS_CONFIGURATION_V1| | -| COMMAND_CLASS_ALARM_V1| | -| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| | -| COMMAND_CLASS_POWERLEVEL_V1| | -| COMMAND_CLASS_PROTECTION_V2| | -| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| | -| COMMAND_CLASS_BATTERY_V0| | -| COMMAND_CLASS_ASSOCIATION_V2| | -| COMMAND_CLASS_VERSION_V2| | -#### Endpoint 1 - -| Command Class | Comment | -|---------------|---------| -| COMMAND_CLASS_BASIC_V0| | -| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC| -#### Endpoint 2 - -| Command Class | Comment | -|---------------|---------| -| COMMAND_CLASS_BASIC_V0| | -| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC| -#### Endpoint 3 - -| Command Class | Comment | -|---------------|---------| -| COMMAND_CLASS_BASIC_V0| | -| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC| - -### Documentation Links - -* [PAN06-1B Manual](https://www.cd-jackson.com/zwave_device_uploads/858/C50101008V01-PAN06-1-2-3B-manual-20150831.pdf) - ---- - -Did you spot an error in the above definition or want to improve the content? -You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/858). diff --git a/_addons_bindings/zwave/doc/philio/pan081a_0_0.md b/_addons_bindings/zwave/doc/philio/pan081a_0_0.md index 210fabacb0..7b20185821 100644 --- a/_addons_bindings/zwave/doc/philio/pan081a_0_0.md +++ b/_addons_bindings/zwave/doc/philio/pan081a_0_0.md @@ -51,10 +51,6 @@ controller manufacturer. within 2 seconds will enter exclusion mode. -### Wakeup Information - -Device is not battery operated, hence no wakeup procedure. - ## Channels The following table summarises the channels available for the PAN08-1a -: diff --git a/_addons_bindings/zwave/doc/philio/pat02a_0_0.md b/_addons_bindings/zwave/doc/philio/pat02a_0_0.md index 3b34543d8a..8e62542c14 100644 --- a/_addons_bindings/zwave/doc/philio/pat02a_0_0.md +++ b/_addons_bindings/zwave/doc/philio/pat02a_0_0.md @@ -8,9 +8,14 @@ title: PAT02-A - ZWave # PAT02-A Flood Multisensor (incl. humidty and temperature) This describes the Z-Wave device *PAT02-A*, manufactured by *[Philio Technology Corp](http://www.philio-tech.com/)* with the thing type UID of ```philio_pat02a_00_000```. +The device is in the category of *Sensor*, defining Device used to measure something. + +![PAT02-A product image](https://www.cd-jackson.com/zwave_device_uploads/261/261_default.jpg) + + The PAT02-A supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The PAT02-A does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The PAT02-A does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -43,6 +48,10 @@ Notice: Including a node ID allocated by Z-WaveTM Controller means “Add” or ### Wakeup Information +The PAT02-A does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + After the device adding to the network, it will wake-up once per day in default. When it wake-up it will broadcast the “Wake Up Notification” message to the network, and wake-up 10 seconds for receive the setting commands. The wake-up interval minimum setting is 30 minutes, and maximum setting is 120 hours. And the interval step is 30 minutes. @@ -149,7 +158,7 @@ Setting the BASIC command value. Setting the BASIC command value. When the flood trigger off (0x00), send the BASIC CC to the group 2 -Values in the range 1 to 100 may be set. +Values in the range 0 to 255 may be set. The manufacturer defined default value is ```0```. @@ -162,9 +171,9 @@ Setting the BASIC command value. Setting the BASIC command value. When the flood trigger on(0xFF), send the BASIC CC to the group 2. -Values in the range 1 to 100 may be set. +Values in the range 0 to 255 may be set. -The manufacturer defined default value is ```0```. +The manufacturer defined default value is ```255```. This parameter has the configuration ID ```config_2_1``` and is of type ```INTEGER```. diff --git a/_addons_bindings/zwave/doc/philio/pat02b_0_0.md b/_addons_bindings/zwave/doc/philio/pat02b_0_0.md index 7413cd6408..f606288b21 100644 --- a/_addons_bindings/zwave/doc/philio/pat02b_0_0.md +++ b/_addons_bindings/zwave/doc/philio/pat02b_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *PAT02-B*, manufactured by *[Philio Technology The PAT02-B supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The PAT02-B does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The PAT02-B does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/533) to improve the documentation. +### Wakeup Information +The PAT02-B does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the PAT02-B -: diff --git a/_addons_bindings/zwave/doc/philio/pat02c_0_0.md b/_addons_bindings/zwave/doc/philio/pat02c_0_0.md index 1277a92fd1..e5127c6260 100644 --- a/_addons_bindings/zwave/doc/philio/pat02c_0_0.md +++ b/_addons_bindings/zwave/doc/philio/pat02c_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *PAT02-C*, manufactured by *[Philio Technology The PAT02-C supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The PAT02-C does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The PAT02-C does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/178) to improve the documentation. +### Wakeup Information +The PAT02-C does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the PAT02-C -: diff --git a/_addons_bindings/zwave/doc/philio/psm02_0_0.md b/_addons_bindings/zwave/doc/philio/psm02_0_0.md index 7d71c0b146..bb0b0e3bb6 100644 --- a/_addons_bindings/zwave/doc/philio/psm02_0_0.md +++ b/_addons_bindings/zwave/doc/philio/psm02_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *PSM02*, manufactured by *[Philio Technology Co The PSM02 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The PSM02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The PSM02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/167) to improve the documentation. +### Wakeup Information +The PSM02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the PSM02 -: diff --git a/_addons_bindings/zwave/doc/philio/psp05_0_0.md b/_addons_bindings/zwave/doc/philio/psp05_0_0.md index 449542a714..14f37d462a 100644 --- a/_addons_bindings/zwave/doc/philio/psp05_0_0.md +++ b/_addons_bindings/zwave/doc/philio/psp05_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Sensor*, defining Device used to measure somet The PSP05 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The PSP05 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The PSP05 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/600) to improve the documentation. +### Wakeup Information +The PSP05 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the PSP05 -: diff --git a/_addons_bindings/zwave/doc/philio/psr04_0_0.md b/_addons_bindings/zwave/doc/philio/psr04_0_0.md index d60dd7b994..00e433e29a 100644 --- a/_addons_bindings/zwave/doc/philio/psr04_0_0.md +++ b/_addons_bindings/zwave/doc/philio/psr04_0_0.md @@ -10,12 +10,16 @@ This describes the Z-Wave device *PSR04*, manufactured by *[Philio Technology Co The PSR04 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The PSR04 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The PSR04 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview ### Wakeup Information +The PSR04 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + By default, this device only wakes up every 86400 seconds (24 hours). To manually wake this device up: 1. Hold the device vertically, or against a wall (this will not work if the device is horizontal). diff --git a/_addons_bindings/zwave/doc/philio/pst02a_0_0.md b/_addons_bindings/zwave/doc/philio/pst02a_0_0.md index 9f26c9932c..df4d0f5b11 100644 --- a/_addons_bindings/zwave/doc/philio/pst02a_0_0.md +++ b/_addons_bindings/zwave/doc/philio/pst02a_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *PST02A*, manufactured by *[Philio Technology C The PST02A supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The PST02A does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The PST02A does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/168) to improve the documentation. +### Wakeup Information +The PST02A does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the PST02A -: diff --git a/_addons_bindings/zwave/doc/philio/pst02b_0_0.md b/_addons_bindings/zwave/doc/philio/pst02b_0_0.md index a58a71cc1d..9116602ca9 100644 --- a/_addons_bindings/zwave/doc/philio/pst02b_0_0.md +++ b/_addons_bindings/zwave/doc/philio/pst02b_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Sensor*, defining Device used to measure somet The PST02B supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The PST02B does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The PST02B does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/169) to improve the documentation. +### Wakeup Information +The PST02B does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the PST02B -: diff --git a/_addons_bindings/zwave/doc/philio/pst02c_0_0.md b/_addons_bindings/zwave/doc/philio/pst02c_0_0.md index 4e36ee8648..497ae906d7 100644 --- a/_addons_bindings/zwave/doc/philio/pst02c_0_0.md +++ b/_addons_bindings/zwave/doc/philio/pst02c_0_0.md @@ -10,7 +10,7 @@ This describes the Z-Wave device *PST02C*, manufactured by *[Philio Technology C The PST02C supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The PST02C does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The PST02C does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -41,6 +41,10 @@ In the first time, add the device into the Z-WaveTM network. First, make sure th ### Wakeup Information +The PST02C does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + After the device adding to the network, it will wake-up once per day in default. When it wake-up it will broadcast the “Wake Up Notification” message to the network, and wake-up 10 seconds for receive the setting commands. The wake-up interval minimum setting is 30 minutes, and maximum setting is 120 hours. And the interval step is 30 minutes. diff --git a/_addons_bindings/zwave/doc/popp/004407_1_0.md b/_addons_bindings/zwave/doc/popp/004407_1_0.md index 2f5f031bfc..3a9e267eb3 100644 --- a/_addons_bindings/zwave/doc/popp/004407_1_0.md +++ b/_addons_bindings/zwave/doc/popp/004407_1_0.md @@ -14,7 +14,7 @@ This version of the device is limited to firmware versions above 1.0 The 004407 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The 004407 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The 004407 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -36,6 +36,10 @@ A single click on the Z-Wave button will exclude the device. ### Wakeup Information +The 004407 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Wakeup is done by single push of the Z-Wave button ## Channels diff --git a/_addons_bindings/zwave/doc/popp/005206_0_0.md b/_addons_bindings/zwave/doc/popp/005206_0_0.md index 528f9ce6e7..e5d85d37fe 100644 --- a/_addons_bindings/zwave/doc/popp/005206_0_0.md +++ b/_addons_bindings/zwave/doc/popp/005206_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *005206*, manufactured by *Popp & Co* with the The 005206 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The 005206 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The 005206 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/512) to improve the documentation. +### Wakeup Information +The 005206 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the 005206 -: diff --git a/_addons_bindings/zwave/doc/popp/009204_0_0.md b/_addons_bindings/zwave/doc/popp/009204_0_0.md index 7adef9ba7e..eba02e27c7 100644 --- a/_addons_bindings/zwave/doc/popp/009204_0_0.md +++ b/_addons_bindings/zwave/doc/popp/009204_0_0.md @@ -8,12 +8,15 @@ title: 009204 - ZWave # 009204 KFOB-C Remote-Control This describes the Z-Wave device *009204*, manufactured by *Popp & Co* with the thing type UID of ```popp_009204_00_000```. -The 009204 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The 009204 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/415) to improve the documentation. +### Wakeup Information +The 009204 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the 009204 -: diff --git a/_addons_bindings/zwave/doc/popp/009303_0_0.md b/_addons_bindings/zwave/doc/popp/009303_0_0.md index 1641e189f5..9c6f697810 100644 --- a/_addons_bindings/zwave/doc/popp/009303_0_0.md +++ b/_addons_bindings/zwave/doc/popp/009303_0_0.md @@ -13,7 +13,7 @@ The device is in the category of *Wall Switch*, defining Any device attached to ![009303 product image](https://www.cd-jackson.com/zwave_device_uploads/233/233_default.png) -The 009303 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The 009303 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -27,6 +27,10 @@ see attached file "Popp 009303 Battery Wall Controller Manual" (section Referenc ### Wakeup Information +The 009303 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + see attached file "Popp 009303 Battery Wall Controller Manual" (section Reference Documents) ## Channels diff --git a/_addons_bindings/zwave/doc/popp/009501_1_2.md b/_addons_bindings/zwave/doc/popp/009501_1_2.md index a23038189f..543f988f59 100644 --- a/_addons_bindings/zwave/doc/popp/009501_1_2.md +++ b/_addons_bindings/zwave/doc/popp/009501_1_2.md @@ -9,7 +9,7 @@ title: 009501 - ZWave This describes the Z-Wave device *009501*, manufactured by *Popp & Co* with the thing type UID of ```popp_009501_01_002```. This version of the device is limited to firmware version 1.2 -The 009501 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The 009501 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -24,6 +24,11 @@ For inclusion press the red button on the top of the enclosure 3 times For exclusion press the red button on the top of the enclosure 3 times +### Wakeup Information + +The 009501 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the 009501 -: diff --git a/_addons_bindings/zwave/doc/popp/pope700052_0_0.md b/_addons_bindings/zwave/doc/popp/pope700052_0_0.md index 0b5caea392..d8785c4a0e 100644 --- a/_addons_bindings/zwave/doc/popp/pope700052_0_0.md +++ b/_addons_bindings/zwave/doc/popp/pope700052_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *POPE700052*, manufactured by *Popp & Co* with The POPE700052 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The POPE700052 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The POPE700052 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/748) to improve the documentation. +### Wakeup Information +The POPE700052 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the POPE700052 -: diff --git a/_addons_bindings/zwave/doc/popp/pope700168_0_0.md b/_addons_bindings/zwave/doc/popp/pope700168_0_0.md index c8b1a7f5aa..715f71b43a 100644 --- a/_addons_bindings/zwave/doc/popp/pope700168_0_0.md +++ b/_addons_bindings/zwave/doc/popp/pope700168_0_0.md @@ -8,16 +8,34 @@ title: POPE700168 - ZWave # POPE700168 POPP Rain-Sensor This describes the Z-Wave device *POPE700168*, manufactured by *Popp & Co* with the thing type UID of ```popp_pope700168_00_000```. +The device is in the category of *Sensor*, defining Device used to measure something. + ![POPE700168 product image](https://www.cd-jackson.com/zwave_device_uploads/588/588_default.png) The POPE700168 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The POPE700168 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The POPE700168 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/588) to improve the documentation. +The POPP Rain-Sensor is a Rain Measuring Sensor Device for Europe + +### Inclusion Information + +Put controller in inclusion mode, push the Z-Wave button once + +### Exclusion Information + +Put controller in exclusion mode, push the Z-Wave button once + +### Wakeup Information + +The POPE700168 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + +Push the Z-Wave button once ## Channels @@ -68,20 +86,20 @@ Detailed information on each parameter can be found in the sections below. | Param | Name | Description | |-------|-------|-------------| -| 1 | Rain Counter | Ths values shows the total count of rain from the moment of inclusion in mm waterlevel. By writing this value this counter can be reset. Size: 2 Byte, Default Value: 0 | -| 2 | Rain Start Command | This BASIC Set Command value is sent out into Association Group 2 when the device detects start of rain Size: 1 Byte, Default Value: 99 | -| 3 | Rain Stop Command | This BASIC Set Command value is sent out into Association Group 2 when the device detects stop of rain Size: 1 Byte, Default Value: 0 | -| 4 | Meter Multiplier | This multiplier allows to adapt the display to certain controllers not being able to handle very low numbers. Size: 2 Byte, Default Value: 1 only 1/10/100/1000 | -| 5 | Heavy Rain | This threshold defines when a heavy rain condition is hit. In most countries this is defined as > 15 mm rain per hour. The default value however is to turn this function off. Size: 1 Byte, Default Value: 255 | -| 6 | Heavy Rain Start Command | This BASIC Set Command value is sent out into Association Group 3 when the device detects start of heavy rain Size: 1 Byte, Default Value: 99 | -| 7 | Heavy Rain Stop Command | This BASIC Set Command value is sent out into Association Group 3 when the device detects stop of heavy rain Size: 1 Byte, Default Value: 0 | +| 1 | Rain Counter | total count of rain | +| 2 | Rain Start Command | Send rain start command to group 2 | +| 3 | Rain Stop Command | Send rain stop to group 2 | +| 4 | Meter Multiplier | Adapt the display | +| 5 | Heavy Rain | Threshold defines heavy rain condition | +| 6 | Heavy Rain Start Command | Send heavy rain start to group 3 | +| 7 | Heavy Rain Stop Command | Send heavy rain stop to group 3 | | | Wakeup Interval | Sets the interval at which the device will accept commands from the controller | | | Wakeup Node | Sets the node ID of the device to receive the wakeup notifications | ### Parameter 1: Rain Counter +total count of rain Ths values shows the total count of rain from the moment of inclusion in mm waterlevel. By writing this value this counter can be reset. Size: 2 Byte, Default Value: 0 - Values in the range 0 to 32000 may be set. The manufacturer defined default value is ```0```. @@ -91,8 +109,8 @@ This parameter has the configuration ID ```config_1_2``` and is of type ```INTEG ### Parameter 2: Rain Start Command +Send rain start command to group 2 This BASIC Set Command value is sent out into Association Group 2 when the device detects start of rain Size: 1 Byte, Default Value: 99 - Values in the range 0 to 99 may be set. The manufacturer defined default value is ```99```. @@ -102,8 +120,8 @@ This parameter has the configuration ID ```config_2_1``` and is of type ```INTEG ### Parameter 3: Rain Stop Command +Send rain stop to group 2 This BASIC Set Command value is sent out into Association Group 2 when the device detects stop of rain Size: 1 Byte, Default Value: 0 - Values in the range 0 to 99 may be set. The manufacturer defined default value is ```0```. @@ -113,8 +131,8 @@ This parameter has the configuration ID ```config_3_1``` and is of type ```INTEG ### Parameter 4: Meter Multiplier +Adapt the display This multiplier allows to adapt the display to certain controllers not being able to handle very low numbers. Size: 2 Byte, Default Value: 1 only 1/10/100/1000 - Values in the range 1 to 1000 may be set. The manufacturer defined default value is ```1```. @@ -124,8 +142,8 @@ This parameter has the configuration ID ```config_4_2``` and is of type ```INTEG ### Parameter 5: Heavy Rain +Threshold defines heavy rain condition This threshold defines when a heavy rain condition is hit. In most countries this is defined as > 15 mm rain per hour. The default value however is to turn this function off. Size: 1 Byte, Default Value: 255 - Values in the range 0 to 255 may be set. The manufacturer defined default value is ```255```. @@ -135,8 +153,8 @@ This parameter has the configuration ID ```config_5_1``` and is of type ```INTEG ### Parameter 6: Heavy Rain Start Command +Send heavy rain start to group 3 This BASIC Set Command value is sent out into Association Group 3 when the device detects start of heavy rain Size: 1 Byte, Default Value: 99 - Values in the range 0 to 99 may be set. The manufacturer defined default value is ```99```. @@ -146,8 +164,8 @@ This parameter has the configuration ID ```config_6_1``` and is of type ```INTEG ### Parameter 7: Heavy Rain Stop Command +Send heavy rain stop to group 3 This BASIC Set Command value is sent out into Association Group 3 when the device detects stop of heavy rain Size: 1 Byte, Default Value: 0 - Values in the range 0 to 99 may be set. The manufacturer defined default value is ```0```. diff --git a/_addons_bindings/zwave/doc/qubino/smartplug_0_0.md b/_addons_bindings/zwave/doc/qubino/smartplug_0_0.md index e30ec682f7..72d501e15d 100644 --- a/_addons_bindings/zwave/doc/qubino/smartplug_0_0.md +++ b/_addons_bindings/zwave/doc/qubino/smartplug_0_0.md @@ -47,10 +47,6 @@ Manual inclusion - enable exclusion mode on main controller - press service button (S) on module 3 times within 3 seconds (please note: configuration parameters will not be reset!) -### Wakeup Information - -Press the Service button (S) 3 times within 3 seconds. - ## Channels The following table summarises the channels available for the Smart Plug 16A -: diff --git a/_addons_bindings/zwave/doc/qubino/zmnhba_0_0.md b/_addons_bindings/zwave/doc/qubino/zmnhba_0_0.md index df1d7805e8..d341ea1782 100644 --- a/_addons_bindings/zwave/doc/qubino/zmnhba_0_0.md +++ b/_addons_bindings/zwave/doc/qubino/zmnhba_0_0.md @@ -8,11 +8,40 @@ title: ZMNHBA - ZWave # ZMNHBA Flush 2 relays This describes the Z-Wave device *ZMNHBA*, manufactured by *[Goap](http://www.qubino.com/)* with the thing type UID of ```qubino_zmnhba_00_000```. +The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. + +![ZMNHBA product image](https://www.cd-jackson.com/zwave_device_uploads/208/208_default.png) + + The ZMNHBA supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/208) to improve the documentation. +This Z-Wave module is used for switching on or off two electrical devices (e.g. lights, fans, etc ...). +The module can be controlled either through Z-Wave network or through the wall switches. +The module is designed to be mounted inside a “flush mounting box”, hidden behind a traditional wall switch. +Module measures power consumption of two electrical devices and supports connection of digital temperature sensor. + +### Inclusion Information + +- Connect module to power supply, +- bring module within maximum 1 meter (3 feet) of the main controller, +- enable add/remove mode on main controller, +- auto-inclusion (30 minutes after connected to power supply) or +- press service button S for more than 2 second or +- press push button I1 three times within 3s (3 times change switch state within 3 + seconds). + +### Exclusion Information + +- Connect module to power supply +- bring module within maximum 1 meter (3 feet) of the main controller, +- enable add/remove mode on main controller, +- press service button S for more than 6 second or +- press push button I1 five times within 3s (5 times change switch state within 3 seconds). + +By this function all parameters of the module are set to default values and own ID is deleted. +If service button S is pressed more than 2 and less than 6second module is excluded, but configuration parameters are not set to default values ## Channels diff --git a/_addons_bindings/zwave/doc/qubino/zmnhda_0_0.md b/_addons_bindings/zwave/doc/qubino/zmnhda_0_0.md index 7938e0de78..aef1313518 100644 --- a/_addons_bindings/zwave/doc/qubino/zmnhda_0_0.md +++ b/_addons_bindings/zwave/doc/qubino/zmnhda_0_0.md @@ -10,11 +10,39 @@ This describes the Z-Wave device *ZMNHDA*, manufactured by *[Goap](http://www.qu The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. +![ZMNHDA product image](https://www.cd-jackson.com/zwave_device_uploads/209/209_default.png) + + The ZMNHDA supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/209) to improve the documentation. +This Z-Wave module is used for dimming the bulb or to manage the speed of a fan. The module can be controlled either through a Z-Wave network or through the wall switch. + +The module is designed to be mounted inside a “flush mounting box” and is hidden behind a traditional wall switch. + +Module measures power consumption of bulb or fan and supports connection of digital temperature sensor. + +### Inclusion Information + +- Connect module to power supply, +- bring module within maximum 1 meter (3 feet) of the main controller, +- enable add/remove mode on main controller, +- auto-inclusion (30 minutes after connected to power supply) or +- press service button S for more than 2 seconds or +- press push button I1 three times within 3s (3 times change switch state within 3 seconds). + +### Exclusion Information + +- Connect module to power supply, +- bring module within maximum 1 meter (3 feet) of the main controller, +- enable add/remove mode on main controller, +- press service button S for more than 6 seconds or +- press push button I1 five times within 3s (5 times change switch state within 3 seconds) + +By this function all parameters of the module are set to default values and own ID is deleted. + +If service button S is pressed more than 2 and less than 6 second module is excluded, but configuration parameters are not set to default values. ## Channels @@ -357,6 +385,10 @@ This group supports 4 nodes. | COMMAND_CLASS_BASIC_V0| | | COMMAND_CLASS_SENSOR_BINARY_V0| Linked to BASIC| +### Documentation Links + +* [User manual v6](https://www.cd-jackson.com/zwave_device_uploads/209/Qubino-Flush-dimmer-user-manual-V6-eng.pdf) + --- Did you spot an error in the above definition or want to improve the content? diff --git a/_addons_bindings/zwave/doc/reitz/05443_0_0.md b/_addons_bindings/zwave/doc/reitz/05443_0_0.md index ff6ee6f814..075df46239 100644 --- a/_addons_bindings/zwave/doc/reitz/05443_0_0.md +++ b/_addons_bindings/zwave/doc/reitz/05443_0_0.md @@ -11,7 +11,7 @@ This describes the Z-Wave device *Duwi ZW WS - 05443*, manufactured by *Reitz-Gr ![Duwi ZW WS - 05443 product image](https://www.cd-jackson.com/zwave_device_uploads/54/54_default.jpg) -The Duwi ZW WS - 05443 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Duwi ZW WS - 05443 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -21,6 +21,10 @@ Press inclusion button for 2 seconds ### Wakeup Information +The Duwi ZW WS - 05443 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Button triple press on on/off ## Channels diff --git a/_addons_bindings/zwave/doc/reitz/zwesj300_0_0.md b/_addons_bindings/zwave/doc/reitz/zwesj300_0_0.md index 86c91cc5b2..fd1954b2c0 100644 --- a/_addons_bindings/zwave/doc/reitz/zwesj300_0_0.md +++ b/_addons_bindings/zwave/doc/reitz/zwesj300_0_0.md @@ -8,12 +8,15 @@ title: ZW ESJ 300 - ZWave # ZW ESJ 300 Duwi ZW ESJ 300 Blind Control This describes the Z-Wave device *ZW ESJ 300*, manufactured by *Reitz-Group.de* with the thing type UID of ```reitz_zwesj300_00_000```. -The ZW ESJ 300 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZW ESJ 300 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/563) to improve the documentation. +### Wakeup Information +The ZW ESJ 300 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZW ESJ 300 -: diff --git a/_addons_bindings/zwave/doc/remotec/zrc100_0_0.md b/_addons_bindings/zwave/doc/remotec/zrc100_0_0.md index a0d1419537..d26760fb4c 100644 --- a/_addons_bindings/zwave/doc/remotec/zrc100_0_0.md +++ b/_addons_bindings/zwave/doc/remotec/zrc100_0_0.md @@ -13,7 +13,7 @@ The device is in the category of *Remote Control*, defining Any portable or hand ![ZRC-100 product image](https://www.cd-jackson.com/zwave_device_uploads/404/404_default.png) -The ZRC-100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZRC-100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -23,6 +23,10 @@ Hold the up + down arrow keys simultaneously for 3 seconds and select "Learning ### Wakeup Information +The ZRC-100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Manually by pressing any button ## Channels diff --git a/_addons_bindings/zwave/doc/remotec/zrc90_0_0.md b/_addons_bindings/zwave/doc/remotec/zrc90_0_0.md index fb0bfe5e60..e2c02723b9 100644 --- a/_addons_bindings/zwave/doc/remotec/zrc90_0_0.md +++ b/_addons_bindings/zwave/doc/remotec/zrc90_0_0.md @@ -13,12 +13,15 @@ The device is in the category of *Remote Control*, defining Any portable or hand ![ZRC-90 product image](https://www.cd-jackson.com/zwave_device_uploads/361/361_default.jpg) -The ZRC-90 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZRC-90 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/361) to improve the documentation. +### Wakeup Information +The ZRC-90 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZRC-90 -: diff --git a/_addons_bindings/zwave/doc/rtc/ct200_0_0.md b/_addons_bindings/zwave/doc/rtc/ct200_0_0.md index 7254760b20..be20a626ba 100644 --- a/_addons_bindings/zwave/doc/rtc/ct200_0_0.md +++ b/_addons_bindings/zwave/doc/rtc/ct200_0_0.md @@ -27,12 +27,6 @@ The Vivint Element Thermostat is a Z-Wave® compliant thermostat. It has an onbo The Vivint Element can be excluded from the Z-Wave network process similar to the inclusion process. Set your primary controller to EXCLUDE. -### Wakeup Information - -When your thermostat is running on battery power, the Z-Wave radio will turn off to help conserve battery life. The Thermostat Z-Wave radio module supports Z-Wave beaming, which allows other devices in the network to wake up the Z-Wave module and accept commands and then go back to sleep. - -When your thermostat is running on C-Wire power, the Z-Wave radio will stay on and actively help route messages within the Z-Wave network. The thermostat’s node type is fixed when it is included to the Z-Wave network; if the C-Wire is present and powered when including to the network, the thermostat will remain an alwayslistening node until it is removed from the network. - ## Channels The following table summarises the channels available for the CT200 -: diff --git a/_addons_bindings/zwave/doc/samsungsds/hmdm100_0_0.md b/_addons_bindings/zwave/doc/samsungsds/hmdm100_0_0.md index f7d454e193..83ce228fbf 100644 --- a/_addons_bindings/zwave/doc/samsungsds/hmdm100_0_0.md +++ b/_addons_bindings/zwave/doc/samsungsds/hmdm100_0_0.md @@ -27,10 +27,6 @@ triple press the inclusing button Triple press inclusion button -### Wakeup Information - -triple press inclusion button - ## Channels The following table summarises the channels available for the hmdm100 -: diff --git a/_addons_bindings/zwave/doc/schlage/be369_0_0.md b/_addons_bindings/zwave/doc/schlage/be369_0_0.md index d7224ec036..451c557273 100644 --- a/_addons_bindings/zwave/doc/schlage/be369_0_0.md +++ b/_addons_bindings/zwave/doc/schlage/be369_0_0.md @@ -37,10 +37,6 @@ Shares same hardware as FE599 lock (lever version). 4. Press 0 5. The Schlage button will blink three times to confirm -### Wakeup Information - -Unknown - ## Channels The following table summarises the channels available for the BE369 -: diff --git a/_addons_bindings/zwave/doc/schlage/be468_0_0.md b/_addons_bindings/zwave/doc/schlage/be468_0_0.md index 5077041b84..406deeb092 100644 --- a/_addons_bindings/zwave/doc/schlage/be468_0_0.md +++ b/_addons_bindings/zwave/doc/schlage/be468_0_0.md @@ -39,10 +39,6 @@ To verify enrollment: Same as inclusion -### Wakeup Information - -N/A - ## Channels The following table summarises the channels available for the BE468 -: diff --git a/_addons_bindings/zwave/doc/schlage/be469_0_0.md b/_addons_bindings/zwave/doc/schlage/be469_0_0.md index e158dd8b7a..c38c9c01e2 100644 --- a/_addons_bindings/zwave/doc/schlage/be469_0_0.md +++ b/_addons_bindings/zwave/doc/schlage/be469_0_0.md @@ -35,10 +35,6 @@ To verify enrollment: Same as inclusion -### Wakeup Information - -N/A - ## Channels The following table summarises the channels available for the BE469 -: diff --git a/_addons_bindings/zwave/doc/sensative/1101011_0_0.md b/_addons_bindings/zwave/doc/sensative/1101011_0_0.md index d2173f683d..60b5642ae0 100644 --- a/_addons_bindings/zwave/doc/sensative/1101011_0_0.md +++ b/_addons_bindings/zwave/doc/sensative/1101011_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet The 11-01-011 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The 11-01-011 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The 11-01-011 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -33,6 +33,10 @@ The 11-01-011 does not permanently listen for messages sent from the controller ### Wakeup Information +The 11-01-011 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Wake up Strips manually for Z-Wave communication. - Place the round magnet at the rounded edge. diff --git a/_addons_bindings/zwave/doc/sensative/1102011_0_0.md b/_addons_bindings/zwave/doc/sensative/1102011_0_0.md index 2d55df05c7..4f106173f6 100644 --- a/_addons_bindings/zwave/doc/sensative/1102011_0_0.md +++ b/_addons_bindings/zwave/doc/sensative/1102011_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet The 11 02 011 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The 11 02 011 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The 11 02 011 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -33,6 +33,10 @@ Set your controller to remove mode (see your controller’s manual). Follow the ### Wakeup Information +The 11 02 011 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Wake up Strips manually for Z-Wave communication. Place the magnet at the rounded edge. When the LED blinks, move the magnet away. Repeat twice within 10 seconds. ## Channels diff --git a/_addons_bindings/zwave/doc/shenzhen/doorsensorin_0_0.md b/_addons_bindings/zwave/doc/shenzhen/doorsensorin_0_0.md index f0e2d3ddc4..3e8d8550ec 100644 --- a/_addons_bindings/zwave/doc/shenzhen/doorsensorin_0_0.md +++ b/_addons_bindings/zwave/doc/shenzhen/doorsensorin_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *Door Sensor IN*, manufactured by *[Shenzhen Ne The Door Sensor IN supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The Door Sensor IN does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Door Sensor IN does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/477) to improve the documentation. +### Wakeup Information +The Door Sensor IN does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the Door Sensor IN -: diff --git a/_addons_bindings/zwave/doc/shenzhen/doorwindowsensor_0_0.md b/_addons_bindings/zwave/doc/shenzhen/doorwindowsensor_0_0.md index 60ca7ac8b7..990c47989f 100644 --- a/_addons_bindings/zwave/doc/shenzhen/doorwindowsensor_0_0.md +++ b/_addons_bindings/zwave/doc/shenzhen/doorwindowsensor_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Door*, defining Door sensors. The Door/Window Sensor supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The Door/Window Sensor does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Door/Window Sensor does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -47,6 +47,10 @@ gateway operating manual) ### Wakeup Information +The Door/Window Sensor does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + You can press the button once to wake up the device and send wakeup notification to controller. If press successfully, the LED will blink one time. The minimum wakeup interval is 300s (5 minutes) diff --git a/_addons_bindings/zwave/doc/shenzhen/floodsensor_0_0.md b/_addons_bindings/zwave/doc/shenzhen/floodsensor_0_0.md index b6ea72f932..615ba523c2 100644 --- a/_addons_bindings/zwave/doc/shenzhen/floodsensor_0_0.md +++ b/_addons_bindings/zwave/doc/shenzhen/floodsensor_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet The Flood sensor supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The Flood sensor does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Flood sensor does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -43,6 +43,10 @@ Flood/Water detection ### Wakeup Information +The Flood sensor does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + You can press the button once to wake up the device and send wakeup notification to controller. If press successfully, the LED will blink one time. diff --git a/_addons_bindings/zwave/doc/shenzhen/motionsensor_0_0.md b/_addons_bindings/zwave/doc/shenzhen/motionsensor_0_0.md index a6975fc2f9..eab5ec61ae 100644 --- a/_addons_bindings/zwave/doc/shenzhen/motionsensor_0_0.md +++ b/_addons_bindings/zwave/doc/shenzhen/motionsensor_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Motion Detector*, defining Motion sensors/dete The Motion Sensor supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The Motion Sensor does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Motion Sensor does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -53,6 +53,10 @@ gateway operating manual) ### Wakeup Information +The Motion Sensor does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + You can press the button once to wake up the device and send wakeup notification to controller. If press successfully, the LED will blink one time. diff --git a/_addons_bindings/zwave/doc/shenzhen/motionsensorin_0_0.md b/_addons_bindings/zwave/doc/shenzhen/motionsensorin_0_0.md index 9392e5fb4a..a835e74bbd 100644 --- a/_addons_bindings/zwave/doc/shenzhen/motionsensorin_0_0.md +++ b/_addons_bindings/zwave/doc/shenzhen/motionsensorin_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *Motion Sensor IN*, manufactured by *[Shenzhen The Motion Sensor IN supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The Motion Sensor IN does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Motion Sensor IN does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/478) to improve the documentation. +### Wakeup Information +The Motion Sensor IN does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the Motion Sensor IN -: diff --git a/_addons_bindings/zwave/doc/shenzhen/nasab01z_0_0.md b/_addons_bindings/zwave/doc/shenzhen/nasab01z_0_0.md index d678574fff..ec77a1a857 100644 --- a/_addons_bindings/zwave/doc/shenzhen/nasab01z_0_0.md +++ b/_addons_bindings/zwave/doc/shenzhen/nasab01z_0_0.md @@ -36,10 +36,6 @@ The siren alarm can be included to the Z-wave network by pressing on the code bu 3. Quickly, triple click the code button, LED light will flash red for 5 times. 4. Wait for the main controller to delete the sensor. -### Wakeup Information - -Press code button once, LED will blink one time. - ## Channels The following table summarises the channels available for the NAS-AB01Z -: diff --git a/_addons_bindings/zwave/doc/shenzhen/nasds01z_0_0.md b/_addons_bindings/zwave/doc/shenzhen/nasds01z_0_0.md index 5d4469d4dc..1c1c6e0319 100644 --- a/_addons_bindings/zwave/doc/shenzhen/nasds01z_0_0.md +++ b/_addons_bindings/zwave/doc/shenzhen/nasds01z_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *NAS-DS01Z*, manufactured by *[Shenzhen Neo Ele The NAS-DS01Z supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The NAS-DS01Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The NAS-DS01Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/458) to improve the documentation. +### Wakeup Information +The NAS-DS01Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the NAS-DS01Z -: diff --git a/_addons_bindings/zwave/doc/shenzhen/sirenalarm_0_0.md b/_addons_bindings/zwave/doc/shenzhen/sirenalarm_0_0.md deleted file mode 100644 index 3e190f2113..0000000000 --- a/_addons_bindings/zwave/doc/shenzhen/sirenalarm_0_0.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -layout: documentation -title: Siren Alarm - ZWave ---- - -{% include base.html %} - -# Siren Alarm Siren Alarm -This describes the Z-Wave device *Siren Alarm*, manufactured by *[Shenzhen Neo Electronics Co., Ltd](http://www.szneo.com/)* with the thing type UID of ```shenzhen_sirenalarm_00_000```. - -![Siren Alarm product image](https://www.cd-jackson.com/zwave_device_uploads/522/522_default.png) - - -The Siren Alarm supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. - -## Overview - -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/522) to improve the documentation. - -## Channels - -The following table summarises the channels available for the Siren Alarm -: - -| Channel | Channel Id | Category | Item Type | -|---------|------------|----------|-----------| -| Switch | switch_binary | Switch | Switch | -| Alarm | alarm_general | Door | Switch | -| Battery Level | battery-level | Battery | Number | - -### Switch - -Switch the power on and off. - -The ```switch_binary``` channel supports the ```Switch``` item and is in the ```Switch``` category. - -### Alarm - -Indicates if an alarm is triggered. - -The ```alarm_general``` channel supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device. - -The following state translation is provided for this channel to the ```Switch``` item type -: - -| Value | Label | -|-------|-----------| -| OFF | Ok | -| ON | Alarm | - -### Battery Level - -Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading. - -The ```battery-level``` channel supports the ```Number``` item and is in the ```Battery``` category. - - - -## Device Configuration - -The following table provides a summary of the 7 configuration parameters available in the Siren Alarm. -Detailed information on each parameter can be found in the sections below. - -| Param | Name | Description | -|-------|-------|-------------| -| 1 | Configure Alarm music volume | Configure Alarm music volume | -| 2 | Alarm music duration time | Alarm music duration time | -| 3 | Door bell music duration time | Door bell music duration time | -| 4 | Door bell music volume | Door bell music volume | -| 5 | Alarm music index | Alarm music index | -| 6 | Door bell music index | Door bell music index | -| 7 | Default Siren on mode | Default Siren on mode | - -### Parameter 1: Configure Alarm music volume - -Configure Alarm music volume - -Values in the range 1 to 3 may be set. - -The manufacturer defined default value is ```2```. - -This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```. - - -### Parameter 2: Alarm music duration time - -Alarm music duration time - -Values in the range 0 to 255 may be set. - -The manufacturer defined default value is ```2```. - -This parameter has the configuration ID ```config_2_1``` and is of type ```INTEGER```. - - -### Parameter 3: Door bell music duration time - -Door bell music duration time - -Values in the range 0 to 255 may be set. - -The manufacturer defined default value is ```1```. - -This parameter has the configuration ID ```config_3_1``` and is of type ```INTEGER```. - - -### Parameter 4: Door bell music volume - -Door bell music volume - -Values in the range 1 to 3 may be set. - -The manufacturer defined default value is ```2```. - -This parameter has the configuration ID ```config_4_1``` and is of type ```INTEGER```. - - -### Parameter 5: Alarm music index - -Alarm music index - -Values in the range 1 to 10 may be set. - -The manufacturer defined default value is ```9```. - -This parameter has the configuration ID ```config_5_1``` and is of type ```INTEGER```. - - -### Parameter 6: Door bell music index - -Door bell music index - -Values in the range 1 to 10 may be set. - -The manufacturer defined default value is ```10```. - -This parameter has the configuration ID ```config_6_1``` and is of type ```INTEGER```. - - -### Parameter 7: Default Siren on mode - -Default Siren on mode -This parameter defines the default music index, volume and duration time for siren on. - -This parameter can be selected between ALARM MUSIC and DOOR BELL music. - -The settings for ALARM MUSIC defines by Param #1, #2, #5. - -The settings for DOOR BELL defines by Param #3, #4, #6. -Values in the range 1 to 2 may be set. - -The manufacturer defined default value is ```1```. - -This parameter has the configuration ID ```config_7_1``` and is of type ```INTEGER```. - - -## Association Groups - -Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic. - -The Siren Alarm supports 3 association groups. - -### Group 1: Group 1 - - -This group supports 5 nodes. - -### Group 2: Group 2 - - -This group supports 5 nodes. - -### Group 3: Group2 - - -This group supports 5 nodes. - -## Technical Information - -### Endpoints - -#### Endpoint 0 - -| Command Class | Comment | -|---------------|---------| -| COMMAND_CLASS_NO_OPERATION_V1| | -| COMMAND_CLASS_BASIC_V1| | -| COMMAND_CLASS_SWITCH_BINARY_V1| | -| COMMAND_CLASS_CONFIGURATION_V1| | -| COMMAND_CLASS_ALARM_V1| | -| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| | -| COMMAND_CLASS_BATTERY_V1| | -| COMMAND_CLASS_ASSOCIATION_V1| | -| COMMAND_CLASS_VERSION_V1| | - ---- - -Did you spot an error in the above definition or want to improve the content? -You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/522). diff --git a/_addons_bindings/zwave/doc/shenzhen/sosremotecontrol_0_0.md b/_addons_bindings/zwave/doc/shenzhen/sosremotecontrol_0_0.md index 1cb13734fd..e21067bcb2 100644 --- a/_addons_bindings/zwave/doc/shenzhen/sosremotecontrol_0_0.md +++ b/_addons_bindings/zwave/doc/shenzhen/sosremotecontrol_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Remote Control*, defining Any portable or hand The SOS/Remote Control supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The SOS/Remote Control does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The SOS/Remote Control does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -49,6 +49,11 @@ With 4 buttons, you can use Remote control for emergency call and set 6 differen 4\) Wait for removing SOS from the controller . +### Wakeup Information + +The SOS/Remote Control does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the SOS/Remote Control -: diff --git a/_addons_bindings/zwave/doc/sigma/m4179e_0_0.md b/_addons_bindings/zwave/doc/sigma/m4179e_0_0.md index 88b4a8206d..89fa77cdba 100644 --- a/_addons_bindings/zwave/doc/sigma/m4179e_0_0.md +++ b/_addons_bindings/zwave/doc/sigma/m4179e_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *M417_9E*, manufactured by *Sigma Designs (Form The M417_9E supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The M417_9E does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The M417_9E does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/422) to improve the documentation. +### Wakeup Information +The M417_9E does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the M417_9E -: diff --git a/_addons_bindings/zwave/doc/sigma/zwck8_0_0.md b/_addons_bindings/zwave/doc/sigma/zwck8_0_0.md index 37091d2d54..667b926db2 100644 --- a/_addons_bindings/zwave/doc/sigma/zwck8_0_0.md +++ b/_addons_bindings/zwave/doc/sigma/zwck8_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Wall Switch*, defining Any device attached to The K8 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The K8 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The K8 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -33,6 +33,10 @@ Note that this device incorrectly reports the manufacturer ID. This may be due t ### Wakeup Information +The K8 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Press and hold ca. 2 sec. both I and O keys on the top row (Group 2 keys). The LED indicator should turn ON if the battery has enough power and the Wall Controller works well. ## Channels diff --git a/_addons_bindings/zwave/doc/sunricher/zv9001k8dim_0_0.md b/_addons_bindings/zwave/doc/sunricher/zv9001k8dim_0_0.md index c9f0e3fe36..971bc2aaab 100644 --- a/_addons_bindings/zwave/doc/sunricher/zv9001k8dim_0_0.md +++ b/_addons_bindings/zwave/doc/sunricher/zv9001k8dim_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Wall Switch*, defining Any device attached to The ZV9001K8-DIM supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZV9001K8-DIM does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZV9001K8-DIM does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -53,6 +53,11 @@ and hold down both keys I and O at the top row (group 2) simultaneously on the w on and shows 3 short blinks and 1 long blink to indicate successful removing -> there shall be an indication on the master controller or gateway. +### Wakeup Information + +The ZV9001K8-DIM does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZV9001K8-DIM -: @@ -60,8 +65,13 @@ The following table summarises the channels available for the ZV9001K8-DIM -: | Channel | Channel Id | Category | Item Type | |---------|------------|----------|-----------| | switch_binary | switch_binary | Switch | Switch | +| switch_binary2 | switch_binary | Switch | Switch | +| switch_dimmer | switch_dimmer | DimmableLight | Dimmer | | Scene Number | scene_number | | Number | | Battery Level | battery-level | Battery | Number | +| switch_binary | switch_binary1 | Switch | Switch | +| switch_binary | switch_binary2 | Switch | Switch | +| switch_binary | switch_binary3 | Switch | Switch | ### switch_binary @@ -69,6 +79,19 @@ Switch the power on and off. The ```switch_binary``` channel supports the ```Switch``` item and is in the ```Switch``` category. +### switch_binary2 + +Switch the power on and off. + +The ```switch_binary``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### switch_dimmer + +The brightness channel allows to control the brightness of a light. + It is also possible to switch the light on and off. + +The ```switch_dimmer``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. + ### Scene Number Triggers when a scene button is pressed. @@ -81,6 +104,24 @@ Represents the battery level as a percentage (0-100%). Bindings for things suppo The ```battery-level``` channel supports the ```Number``` item and is in the ```Battery``` category. +### switch_binary + +Switch the power on and off. + +The ```switch_binary1``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### switch_binary + +Switch the power on and off. + +The ```switch_binary2``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### switch_binary + +Switch the power on and off. + +The ```switch_binary3``` channel supports the ```Switch``` item and is in the ```Switch``` category. + ## Device Configuration @@ -128,6 +169,8 @@ This group supports 20 nodes. |---------------|---------| | COMMAND_CLASS_NO_OPERATION_V1| | | COMMAND_CLASS_BASIC_V1| | +| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC| +| COMMAND_CLASS_SWITCH_MULTILEVEL_V1| | | COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | | COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| | | COMMAND_CLASS_CENTRAL_SCENE_V3| | @@ -141,6 +184,21 @@ This group supports 20 nodes. | COMMAND_CLASS_VERSION_V2| | | COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | | COMMAND_CLASS_SECURITY_V0| | +#### Endpoint 1 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V1| | +#### Endpoint 2 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V1| Linked to BASIC| +#### Endpoint 3 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V1| Linked to BASIC| ### Documentation Links diff --git a/_addons_bindings/zwave/doc/telldus/tzdw100_0_0.md b/_addons_bindings/zwave/doc/telldus/tzdw100_0_0.md index 3ac47272b0..cedce8c202 100644 --- a/_addons_bindings/zwave/doc/telldus/tzdw100_0_0.md +++ b/_addons_bindings/zwave/doc/telldus/tzdw100_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *TZDW-100*, manufactured by *[Telldus Technolog The TZDW-100 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The TZDW-100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The TZDW-100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/312) to improve the documentation. +### Wakeup Information +The TZDW-100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the TZDW-100 -: diff --git a/_addons_bindings/zwave/doc/telldus/tzwp102_0_0.md b/_addons_bindings/zwave/doc/telldus/tzwp102_0_0.md new file mode 100644 index 0000000000..681554aa2e --- /dev/null +++ b/_addons_bindings/zwave/doc/telldus/tzwp102_0_0.md @@ -0,0 +1,132 @@ +--- +layout: documentation +title: TZWP-102 - ZWave +--- + +{% include base.html %} + +# TZWP-102 Telldus socket and energy meter +This describes the Z-Wave device *TZWP-102*, manufactured by *[Telldus Technologies AB](http://www.telldus.com/)* with the thing type UID of ```telldus_tzwp102_00_000```. + +The device is in the category of *Power Outlet*, defining Small devices to be plugged into a power socket in a wall which stick there. + +![TZWP-102 product image](https://www.cd-jackson.com/zwave_device_uploads/863/863_default.png) + + +The TZWP-102 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. + +## Overview + +Telldus Z-Wave Plug-in Switch Mini, small size, clean design with energy metering and overcurrent protection. With its small size and clean design, it fits into your home interior design very well also it is possible to use two devices side by side in most electrical outlets. LED indicator can be turned off to not disturb in dark rooms. Control lighting, chargers and other electronic equipment up to 2300 W (resistive load). + +With energy consumption measuring you don’t only see the actual consumption, it can also help to find out if your connected device is ok or not or turn off the mobile charger when the mobile phone is fully charged for safe operation. + +The device acts as a repeater for the Z-Wave network. + +### Inclusion Information + +**Automatically add device to network** + +When the device is inserted into an electrical outlet it’s in automatic add mode (Network Wide Inclusion, NWI). This means that the device is added automatically when the Z-Wave controller enters add mode. + +**Manually add device to network** + +Start the add mode on the Z-Wave controller. Press the button on the device three times fast. The device will now be added into the Z-Wave network. + +### Exclusion Information + +Start the exclusion mode on the Z-Wave controller. Press the button on the device three times fast. The device will now be removed from the Z-Wave network. + +## Channels + +The following table summarises the channels available for the TZWP-102 -: + +| Channel | Channel Id | Category | Item Type | +|---------|------------|----------|-----------| +| Switch | switch_binary | Switch | Switch | +| Scene Number | scene_number | | Number | +| Electric meter (volts) | meter_voltage | Energy | Number | +| Electric meter (watts) | meter_watts | Energy | Number | +| Electric meter (amps) | meter_current | Energy | Number | +| Electric meter (kWh) | meter_kwh | Energy | Number | + +### Switch + +Switch the power on and off. + +The ```switch_binary``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### Scene Number + +Triggers when a scene button is pressed. + +The ```scene_number``` channel supports the ```Number``` item. + +### Electric meter (volts) + +Indicates the instantaneous voltage. + +The ```meter_voltage``` channel supports the ```Number``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device. + +### Electric meter (watts) + +Indicates the instantaneous power consumption. + +The ```meter_watts``` channel supports the ```Number``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device. + +### Electric meter (amps) + +Indicates the instantaneous current consumption. + +The ```meter_current``` channel supports the ```Number``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device. + +### Electric meter (kWh) + +Indicates the energy consumption (kWh). + +The ```meter_kwh``` channel supports the ```Number``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device. + + + +## Device Configuration + +The device has no configuration parameters configured. + +## Association Groups + +Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic. + +The device does not support associations. +## Technical Information + +### Endpoints + +#### Endpoint 0 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_NO_OPERATION_V1| | +| COMMAND_CLASS_BASIC_V1| | +| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC| +| COMMAND_CLASS_SCENE_ACTIVATION_V1| | +| COMMAND_CLASS_SCENE_ACTUATOR_CONF_V1| | +| COMMAND_CLASS_METER_V3| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| | +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_CONFIGURATION_V1| | +| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| | +| COMMAND_CLASS_POWERLEVEL_V1| | +| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_VERSION_V2| | +| COMMAND_CLASS_SECURITY_V0| | + +### Documentation Links + +* [Technical Manual](https://www.cd-jackson.com/zwave_device_uploads/863/TZWP-102-technical-manual.pdf) + +--- + +Did you spot an error in the above definition or want to improve the content? +You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/863). diff --git a/_addons_bindings/zwave/doc/thermofloor/tf016_0_0.md b/_addons_bindings/zwave/doc/thermofloor/tf016_0_0.md index 0b87b4daba..8c481da0f9 100644 --- a/_addons_bindings/zwave/doc/thermofloor/tf016_0_0.md +++ b/_addons_bindings/zwave/doc/thermofloor/tf016_0_0.md @@ -40,6 +40,7 @@ The following table summarises the channels available for the TF016 -: | Channel | Channel Id | Category | Item Type | |---------|------------|----------|-----------| +| Thermostat State | switch_binary | Switch | Switch | | Sensor (temperature) | sensor_temperature | Temperature | Number | | Electric meter (kWh) | meter_kwh | Energy | Number | | Thermostat mode | thermostat_mode | Temperature | Number | @@ -47,6 +48,12 @@ The following table summarises the channels available for the TF016 -: | Setpoint (furnace) | thermostat_setpoint | Temperature | Number | | Setpoint (economy) | thermostat_setpoint | Temperature | Number | +### Thermostat State + +Switch the power on and off. + +The ```switch_binary``` channel supports the ```Switch``` item and is in the ```Switch``` category. + ### Sensor (temperature) Indicates the current temperature. diff --git a/_addons_bindings/zwave/doc/thermofloor/ztrm2_2_6.md b/_addons_bindings/zwave/doc/thermofloor/ztrm2_2_6.md index 438c27dd72..16d973f1af 100644 --- a/_addons_bindings/zwave/doc/thermofloor/ztrm2_2_6.md +++ b/_addons_bindings/zwave/doc/thermofloor/ztrm2_2_6.md @@ -217,7 +217,7 @@ Detailed information on each parameter can be found in the sections below. | 5 | Floor minimum temperature limit (FLo) | Floor minimum temperature limit (FLo) | | 6 | Floor maximum temperature (FHi) | Floor maximum temperature (FHi) | | 7 | Air minimum temperature limit (ALo) | Air minimum temperature limit (ALo) | -| 8 | Air maximum temperature limet (AHi) | Air maximum temperature limet (AHi) | +| 8 | Air maximum temperature limit (AHi) | Air maximum temperature limit (AHi) | | 9 | FP mode P setting (PLo) | FP mode P setting (PLo) | | 10 | Heating mode setpoint (CO) | Heating mode setpoint (CO) | | 11 | Energy saving mode setpoint (ECO) | Energy saving mode setpoint (ECO) | @@ -239,10 +239,10 @@ Detailed information on each parameter can be found in the sections below. ### Parameter 1: Operation mode Operation mode -1\. Value = 0, Off (default) -2\. Value = 1, Heating mode -3\. Value = 2, Cooling mode (not implemented) -4\. Value = 11, Energy saving mode +Value = 0, Off (default) +Value = 1, Heating mode +Value = 2, Cooling mode (not implemented) +Value = 11, Energy saving mode The following option values may be configured -: | Value | Description | @@ -260,12 +260,12 @@ This parameter has the configuration ID ```config_1_1``` and is of type ```INTEG ### Parameter 2: Sensor mode Sensor mode -1\. Value = 0, F-mode, floor sensor mode -2\. Value = 1, A-mode, internal room sensor mode (default) -3\. Value = 2, AF-mode, internal sensor and floor sensor mode -4\. Value = 3, A2-mode, external room sensor mode -5\. Value = 4, P-mode, power regulator mode -6\. Value = 5, FP-mode, floor sensor and power regulator mode +Value = 0, F-mode, floor sensor mode +Value = 1, A-mode, internal room sensor mode (default) +Value = 2, AF-mode, internal sensor and floor sensor mode +Value = 3, A2-mode, external room sensor mode +Value = 4, P-mode, power regulator mode +Value = 5, FP-mode, floor sensor and power regulator mode The following option values may be configured -: | Value | Description | @@ -311,17 +311,8 @@ This parameter has the configuration ID ```config_3_1``` and is of type ```INTEG Temperature control hysteresis (DIFF I) 1\. Value = 0 - 30, 0.3C - 3.0C (default is 0.5C) -2\. Value = 1, Mode 1: level-controlled input -3\. Value = 2, Mode 2: falling-edge controlled input -4\. Value = 3, Mode 3: raising-edge controlled input (standard) When using a water-based heating, the recommended hysteresis is a minimum of 1.0C -The following option values may be configured, in addition to values in the range 0 to 30 -: - -| Value | Description | -|--------|-------------| -| 1 | Mode 1: level-controlled input | -| 2 | Mode 2: falling-edge controlled input | -| 3 | Mode 3: raising-edge controlled input (standard) | +Values in the range 0 to 30 may be set. The manufacturer defined default value is ```5```. @@ -361,9 +352,9 @@ The manufacturer defined default value is ```50```. This parameter has the configuration ID ```config_7_2``` and is of type ```INTEGER```. -### Parameter 8: Air maximum temperature limet (AHi) +### Parameter 8: Air maximum temperature limit (AHi) -Air maximum temperature limet (AHi) +Air maximum temperature limit (AHi) 1\. Value = 50 - 400, 5.0C - 40.0C, default = 40.0C) Values in the range 50 to 400 may be set. @@ -529,11 +520,7 @@ Temperature report interval Time interval between consecutive temperature reports. Temperature reports can also be sent as a result of polling. -The following option values may be configured -: - -| Value | Description | -|--------|-------------| -| 0 | Reporting of temperature disabled | +Values in the range 0 to 32767 may be set. The manufacturer defined default value is ```60```. @@ -563,11 +550,7 @@ Meter report interval Time interval between consecutive meter reports. Meter reports can also be sent as a result of polling. -The following option values may be configured -: - -| Value | Description | -|--------|-------------| -| 0 | Reporting of metering values is disabled | +Values in the range 0 to 32767 may be set. The manufacturer defined default value is ```60```. diff --git a/_addons_bindings/zwave/doc/things.md b/_addons_bindings/zwave/doc/things.md index c94626bc38..7c5e3eac9d 100644 --- a/_addons_bindings/zwave/doc/things.md +++ b/_addons_bindings/zwave/doc/things.md @@ -7,7 +7,7 @@ title: Things Summary - ZWave # Things Supported by the Z-Wave Binding -The binding supports a total of 740 things from 110 manufacturers. +The binding supports a total of 748 things from 109 manufacturers. The list below summarises the things currently supported, and links to more detailed information about each thing. @@ -68,9 +68,9 @@ and links to more detailed information about each thing. | AEON Labs | [ZW100](aeon/zw100_1_8.md) | 1.8 to 1.9 | ```aeon_zw100_01_008``` | Sensor | | AEON Labs | [ZW100](aeon/zw100_1_10.md) | 1.10 | ```aeon_zw100_01_010``` | Sensor | | AEON Labs | [ZW111](aeon/zw111_0_0.md) | | ```aeon_zw111_00_000``` | Wall Switch | -| AEON Labs | [ZW112](aeon/zw112_0_0.md) | | ```aeon_zw112_00_000``` | | -| AEON Labs | [ZW116](aeon/zw116_0_0.md) | | ```aeon_zw116_00_000``` | | -| AEON Labs | [ZW117](aeon/zw117_0_0.md) | | ```aeon_zw117_00_000``` | | +| AEON Labs | [ZW112](aeon/zw112_0_0.md) | | ```aeon_zw112_00_000``` | Door | +| AEON Labs | [ZW116](aeon/zw116_0_0.md) | | ```aeon_zw116_00_000``` | Wall Switch | +| AEON Labs | [ZW117](aeon/zw117_0_0.md) | | ```aeon_zw117_00_000``` | Power Outlet | | AEON Labs | [ZW120](aeon/zw120_0_0.md) | | ```aeon_zw120_00_000``` | Sensor | | AEON Labs | [ZW121](aeon/zw121_0_0.md) | | ```aeon_zw121_00_000``` | Light Bulb | | AEON Labs | [ZW122](aeon/zw122_0_0.md) | | ```aeon_zw122_00_000``` | Sensor | @@ -116,9 +116,9 @@ and links to more detailed information about each thing. | Danfoss | [DTHERMZ6](danfoss/dthermz6_0_0.md) | | ```danfoss_dthermz6_00_000``` | | | Danfoss | [HRVCCM](danfoss/hrvccm_0_0.md) | | ```danfoss_hrvccm_00_000``` | | | Danfoss | [LC-13](danfoss/lc13_0_0.md) | | ```danfoss_lc13_00_000``` | HVAC | -| Danfoss | [LCZ251](danfoss/lcz251_0_0.md) | | ```danfoss_lcz251_00_000``` | | +| Danfoss | [LCZ251](danfoss/lcz251_0_0.md) | | ```danfoss_lcz251_00_000``` | Radiator Control | | Danfoss | [MT02650](danfoss/mt02650_0_0.md) | | ```danfoss_mt02650_00_000``` | | -| Defaro | [DAD-101 Dimmer](defaro/dad101_0_0.md) | | ```defaro_dad101_00_000``` | Wall Switch | +| Defaro | [DAD-101](defaro/dad101_0_0.md) | | ```defaro_dad101_00_000``` | Wall Switch | | Defaro | [DAS-102](defaro/das102_0_0.md) | | ```defaro_das102_00_000``` | Wall Switch | | Defaro | [DSI-101 binary switch](defaro/dsi101_0_0.md) | | ```defaro_dsi101_00_000``` | Wall Switch | | Devolo | [09813](devolo/09813_0_0.md) | | ```devolo_09813_00_000``` | Smoke Detector | @@ -128,13 +128,12 @@ and links to more detailed information about each thing. | Devolo | [MT2652](devolo/mt2652_0_0.md) | | ```devolo_mt2652_00_000``` | Wall Switch | | Devolo | [MT2653](devolo/mt2653_0_0.md) | | ```devolo_mt2653_00_000``` | | | Devolo | [MT02755](devolo/mt2755_0_0.md) | | ```devolo_mt2755_00_000``` | | -| Devolo | [MT2756](devolo/mt2756_0_0.md) | | ```devolo_mt2756_00_000``` | | +| Devolo | [MT2756](devolo/mt2756_0_0.md) | | ```devolo_mt2756_00_000``` | Sensor | | Devolo | [MT02792](devolo/mt2792_0_0.md) | | ```devolo_mt2792_00_000``` | Power Outlet | | Devolo | [PAN11](devolo/pan11_0_0.md) | | ```devolo_pan11_00_000``` | | | Devolo | [ph-pse02](devolo/phpse02_0_0.md) | | ```devolo_phpse02_00_000``` | Siren | | Devolo | [PST02-1B](devolo/pst021b_0_0.md) | | ```devolo_pst021b_00_000``` | | | Diehl AKO | [SES FS-ZW](diehl/sesfszw_0_0.md) | | ```diehl_sesfszw_00_000``` | | -| Digital Home Systems Pty Ltd, | [DHS-WIN-BLW-DHS](digitalhome/dhswinblw_0_0.md) | | ```digitalhome_dhswinblw_00_000``` | Blinds | | D-Link | [DCH-Z110](dlink/dchz110_0_0.md) | | ```dlink_dchz110_00_000``` | | | D-Link | [DCH-Z120](dlink/dchz120_0_0.md) | | ```dlink_dchz120_00_000``` | | | D-Link | [DCH-Z310](dlink/dchz310_0_0.md) | | ```dlink_dchz310_00_000``` | Smoke Detector | @@ -196,7 +195,8 @@ and links to more detailed information about each thing. | Everspring | [SF812](everspring/sf812_0_0.md) | | ```everspring_sf812_00_000``` | Smoke Detector | | Everspring | [SM103](everspring/sm103_0_0.md) | | ```everspring_sm103_00_000``` | Door | | Everspring | [SP103](everspring/sp103_0_0.md) | | ```everspring_sp103_00_000``` | | -| Everspring | [SP814](everspring/sp814_0_0.md) | | ```everspring_sp814_00_000``` | | +| Everspring | [SP814](everspring/sp814_0_0.md) | | ```everspring_sp814_00_000``` | Motion Detector | +| Everspring | [SP816](everspring/sp816_0_0.md) | | ```everspring_sp816_00_000``` | Motion Detector | | Everspring | [ST812](everspring/st812_0_0.md) | | ```everspring_st812_00_000``` | | | Everspring | [ST814](everspring/st814_0_0.md) | | ```everspring_st814_00_000``` | | | Everspring | [ST815](everspring/st815_0_0.md) | | ```everspring_st815_00_000``` | | @@ -205,7 +205,7 @@ and links to more detailed information about each thing. | Evolve | [LDM-15W](evolve/ldm15w_0_0.md) | | ```evolve_ldm15w_00_000``` | | | Evolve | [LFM-20](evolve/lfm20_0_0.md) | | ```evolve_lfm20_00_000``` | | | Evolve | [LOM15](evolve/lom15_0_0.md) | | ```evolve_lom15_00_000``` | Wall Switch | -| Evolve | [LPM-15](evolve/lpm15_0_0.md) | | ```evolve_lpm15_00_000``` | | +| Evolve | [LPM-15](evolve/lpm15_0_0.md) | | ```evolve_lpm15_00_000``` | Power Outlet | | Evolve | [LRM-AS](evolve/lrmas_0_0.md) | | ```evolve_lrmas_00_000``` | Wall Switch | | Evolve | [LSM-15](evolve/lsm15_0_0.md) | | ```evolve_lsm15_00_000``` | | | Evolve | [LTM-5](evolve/ltm5_0_0.md) | | ```evolve_ltm5_00_000``` | | @@ -229,14 +229,14 @@ and links to more detailed information about each thing. | Fibargroup | [FGFS101](fibaro/fgfs101_0_0.md) | 3.0 | ```fibaro_fgfs101_00_000``` | Sensor | | Fibargroup | [FGFS101](fibaro/fgfs101_3_2.md) | 3.2 to 23.0 | ```fibaro_fgfs101_03_002``` | Sensor | | Fibargroup | [FGFS101](fibaro/fgfs101_23_23.md) | 23.23 | ```fibaro_fgfs101_23_023``` | Sensor | -| Fibargroup | [FGGC001](fibaro/fggc001_0_0.md) | | ```fibaro_fggc001_00_000``` | | +| Fibargroup | [FGGC001](fibaro/fggc001_0_0.md) | | ```fibaro_fggc001_00_000``` | Remote Control | | Fibargroup | [FGK101](fibaro/fgk101_0_0.md) | 2.3 | ```fibaro_fgk101_00_000``` | Door | | Fibargroup | [FGK101](fibaro/fgk101_2_5.md) | 2.5 to 2.5 | ```fibaro_fgk101_02_005``` | Door | | Fibargroup | [FGK101](fibaro/fgk101_3_2.md) | 3.2 | ```fibaro_fgk101_03_002``` | Door | | Fibargroup | [FGKF601](fibaro/fgkf601_0_0.md) | | ```fibaro_fgkf601_00_000``` | | | Fibargroup | [FGMS001](fibaro/fgms001_0_0.md) | 2.8 | ```fibaro_fgms001_00_000``` | Motion Detector | | Fibargroup | [FGMS001](fibaro/fgms001_3_2.md) | 3.2 | ```fibaro_fgms001_03_002``` | Motion Detector | -| Fibargroup | [FGPB101](fibaro/fgpb101_0_0.md) | | ```fibaro_fgpb101_00_000``` | | +| Fibargroup | [FGPB101](fibaro/fgpb101_0_0.md) | | ```fibaro_fgpb101_00_000``` | Remote Control | | Fibargroup | [FGR221](fibaro/fgr221_0_0.md) | | ```fibaro_fgr221_00_000``` | Blinds | | Fibargroup | [FGR222](fibaro/fgr222_24_24.md) | 24.24 | ```fibaro_fgr222_24_024``` | Blinds | | Fibargroup | [FGRGBW](fibaro/fgrgbw_0_0.md) | | ```fibaro_fgrgbw_00_000``` | Wall Switch | @@ -283,13 +283,15 @@ and links to more detailed information about each thing. | Jasco Products | [GE 14292](ge/ge14292_0_0.md) | | ```ge_ge14292_00_000``` | | | Jasco Products | [GE 14294 (ZW3005)](ge/ge14294_0_0.md) | | ```ge_ge14294_00_000``` | Wall Switch | | Jasco Products | [GE 14295](ge/ge14295_0_0.md) | | ```ge_ge14295_00_000``` | | +| Jasco Products | [GE/Jasco 14299](ge/ge14299_0_0.md) | | ```ge_ge14299_00_000``` | Wall Switch | | Jasco Products | [GE/Jasco 14321](ge/ge14321_0_0.md) | | ```ge_ge14321_00_000``` | HVAC | | Jasco Products | [GE 28167 (ZW3104)](ge/ge28167zw3104_0_0.md) | | ```ge_ge28167zw3104_00_000``` | | | Jasco Products | [GE 28169](ge/ge28169_0_0.md) | | ```ge_ge28169_00_000``` | Power Outlet | | Jasco Products | [GE Plug in Smart Switch](ge/gepluginsmartswitch_0_0.md) | | ```ge_gepluginsmartswitch_00_000``` | | | Jasco Products | [GE ZW4004](ge/gezw4004_0_0.md) | | ```ge_gezw4004_00_000``` | | +| Jasco Products | [Motion Dimmer Switch](ge/motiondimmerswitch_0_0.md) | | ```ge_motiondimmerswitch_00_000``` | Wall Switch | | Jasco Products | [GE Outdoor Switch](ge/outdoorswitch_0_0.md) | | ```ge_outdoorswitch_00_000``` | | -| Jasco Products | [32563](ge/smartdoorsensor_0_0.md) | | ```ge_smartdoorsensor_00_000``` | | +| Jasco Products | [32563](ge/smartdoorsensor_0_0.md) | | ```ge_smartdoorsensor_00_000``` | Sensor | | Jasco Products | [ZW1001](ge/zw1001_0_0.md) | | ```ge_zw1001_00_000``` | | | Jasco Products | [ZW3003, GE 12724](ge/zw3003_0_0.md) | | ```ge_zw3003_00_000``` | | | Jasco Products | [ZW3101](ge/zw3101_0_0.md) | | ```ge_zw3101_00_000``` | | @@ -341,6 +343,7 @@ and links to more detailed information about each thing. | HomeSeer Technologies | [HS-WD200+](homeseer/hswd200_0_0.md) | | ```homeseer_hswd200_00_000``` | Wall Switch | | HomeSeer Technologies | [HS-WS100+](homeseer/hsws100_0_0.md) | | ```homeseer_hsws100_00_000``` | | | HomeSeer Technologies | [HS-WS200+](homeseer/hsws200_0_0.md) | | ```homeseer_hsws200_00_000``` | Wall Switch | +| Honeywell | [39358](honeywell/39358_0_0.md) | | ```honeywell_39358_00_000``` | Wall Switch | | Honeywell | [TH6320ZW](honeywell/th6320zw_0_0.md) | | ```honeywell_th6320zw_00_000``` | HVAC | | Honeywell | [TH8320ZW](honeywell/th8320zw_0_0.md) | | ```honeywell_th8320zw_00_000``` | | | Horstmann Controls Limited | [ASR-ZW](horstmann/asrzw_0_0.md) | | ```horstmann_asrzw_00_000``` | | @@ -369,7 +372,7 @@ and links to more detailed information about each thing. | Inovelli | [ZW37](inovelli/zw37_0_0.md) | | ```inovelli_zw37_00_000``` | | | Intermatic | [CA3500](intermatic/ca3500_0_0.md) | | ```intermatic_ca3500_00_000``` | | | Intermatic | [CA3750](intermatic/ca3750_0_0.md) | | ```intermatic_ca3750_00_000``` | | -| Intermatic | [CA600](intermatic/ca600_0_0.md) | | ```intermatic_ca600_00_000``` | | +| Intermatic | [CA600](intermatic/ca600_0_0.md) | | ```intermatic_ca600_00_000``` | Wall Switch | | Intermatic | [CA8900](intermatic/ca8900_0_0.md) | | ```intermatic_ca8900_00_000``` | | | Intermatic | [HA-01C](intermatic/ha01c_0_0.md) | | ```intermatic_ha01c_00_000``` | | | Intermatic | [HA02](intermatic/ha02_0_0.md) | | ```intermatic_ha02_00_000``` | | @@ -407,7 +410,7 @@ and links to more detailed information about each thing. | Leviton | [VRMX1](leviton/vrmx11lz_0_0.md) | | ```leviton_vrmx11lz_00_000``` | Wall Switch | | Leviton | [VRP03](leviton/vrp03_0_0.md) | | ```leviton_vrp03_00_000``` | | | Leviton | [VRPA1](leviton/vrpa1_0_0.md) | | ```leviton_vrpa1_00_000``` | | -| Leviton | [VRPD3](leviton/vrpd3_0_0.md) | | ```leviton_vrpd3_00_000``` | | +| Leviton | [VRPD3](leviton/vrpd3_0_0.md) | | ```leviton_vrpd3_00_000``` | Power Outlet | | Leviton | [VRR15-1LZ](leviton/vrr151lz_0_0.md) | | ```leviton_vrr151lz_00_000``` | Power Outlet | | Leviton | [VRS05](leviton/vrs05_0_0.md) | | ```leviton_vrs05_00_000``` | | | Leviton | [VRS15](leviton/vrs15_0_0.md) | | ```leviton_vrs15_00_000``` | Wall Switch | @@ -416,7 +419,7 @@ and links to more detailed information about each thing. | Linear Corp | [GoControl GC-TBZ48](linear/gctbz48_0_0.md) | | ```linear_gctbz48_00_000``` | HVAC | | Linear Corp | [LB60Z-1](linear/lb60z1_0_0.md) | | ```linear_lb60z1_00_000``` | Light Bulb | | Linear Corp | [NGD00Z-4](linear/ngd00z4_0_0.md) | | ```linear_ngd00z4_00_000``` | Garage Door | -| Linear Corp | [PD300Z-2](linear/pd300z2_0_0.md) | | ```linear_pd300z2_00_000``` | | +| Linear Corp | [PD300Z-2](linear/pd300z2_0_0.md) | | ```linear_pd300z2_00_000``` | Light Bulb | | Linear Corp | [PS15EMZ51](linear/ps15emz51_0_0.md) | | ```linear_ps15emz51_00_000``` | | | Linear Corp | [PS15Z](linear/ps15z_0_0.md) | | ```linear_ps15z_00_000``` | | | Linear Corp | [WA00Z-1](linear/wa00z1_0_0.md) | | ```linear_wa00z1_00_000``` | | @@ -424,7 +427,7 @@ and links to more detailed information about each thing. | Linear Corp | [WADWAZ-1](linear/wadwaz1_0_0.md) | | ```linear_wadwaz1_00_000``` | Door | | Linear Corp | [WAPIRZ-1](linear/wapirz_0_0.md) | | ```linear_wapirz_00_000``` | Motion Detector | | Linear Corp | [WD500Z-1](linear/wd500z_0_0.md) | | ```linear_wd500z_00_000``` | Wall Switch | -| Linear Corp | [WO15Z](linear/wo15z_0_0.md) | | ```linear_wo15z_00_000``` | | +| Linear Corp | [WO15Z](linear/wo15z_0_0.md) | | ```linear_wo15z_00_000``` | Power Outlet | | Linear Corp | [WS15Z-1](linear/ws15z_0_0.md) | | ```linear_ws15z_00_000``` | Wall Switch | | Linear Corp | [WT00Z-1](linear/wt00z1_0_0.md) | | ```linear_wt00z1_00_000``` | | | Locstar Technology Co., Ltd | [LS-8015-ZW](locstar/ls8015zw_0_0.md) | | ```locstar_ls8015zw_00_000``` | | @@ -474,6 +477,7 @@ and links to more detailed information about each thing. | Fantem | [FT098](oomi/ft098_0_0.md) | | ```oomi_ft098_00_000``` | Light Bulb | | Fantem | [FT111](oomi/ft111_0_0.md) | | ```oomi_ft111_00_000``` | Wall Switch | | Fantem | [FT121](oomi/ft121_0_0.md) | | ```oomi_ft121_00_000``` | Light Bulb | +| Fantem | [FT130](oomi/ft130_0_0.md) | | ```oomi_ft130_00_000``` | Wall Switch | | Fantem | [FT132](oomi/ft132_0_0.md) | | ```oomi_ft132_00_000``` | Wall Switch | | permundo GmbH | [PSC132ZW](permundo/psc132zw_0_0.md) | | ```permundo_psc132zw_00_000``` | Wall Switch | | permundo GmbH | [PSC152ZW](permundo/psc152zw_0_0.md) | | ```permundo_psc152zw_00_000``` | Blinds | @@ -483,13 +487,14 @@ and links to more detailed information about each thing. | Philio Technology Corp | [PAN03](philio/pan03_0_0.md) | | ```philio_pan03_00_000``` | | | Philio Technology Corp | [PAN04](philio/pan04_0_0.md) | | ```philio_pan04_00_000``` | Wall Switch | | Philio Technology Corp | [PAN05-1B](philio/pan05_0_0.md) | | ```philio_pan05_00_000``` | Wall Switch | -| Philio Technology Corp | [PAN06](philio/pan06_0_0.md) | | ```philio_pan06_00_000``` | Wall Switch | +| Philio Technology Corp | [PAN06](philio/pan06_0_0.md) | 1.7 | ```philio_pan06_00_000``` | Wall Switch | +| Philio Technology Corp | [PAN06](philio/pan06_1_8.md) | 1.8 | ```philio_pan06_01_008``` | Wall Switch | | Philio Technology Corp | [Philio PAN07-1A](philio/pan071a_0_0.md) | | ```philio_pan071a_00_000``` | | | Philio Technology Corp | [PAN08-1a](philio/pan081a_0_0.md) | | ```philio_pan081a_00_000``` | | | Philio Technology Corp | [PAN08](philio/pan08_0_0.md) | | ```philio_pan08_00_000``` | Blinds | | Philio Technology Corp | [PAN11](philio/pan11_0_0.md) | | ```philio_pan11_00_000``` | | | Philio Technology Corp | [PAN16](philio/pan16_1_2.md) | 1.2 | ```philio_pan16_01_002``` | | -| Philio Technology Corp | [PAT02-A](philio/pat02a_0_0.md) | | ```philio_pat02a_00_000``` | | +| Philio Technology Corp | [PAT02-A](philio/pat02a_0_0.md) | | ```philio_pat02a_00_000``` | Sensor | | Philio Technology Corp | [PAT02-B](philio/pat02b_0_0.md) | | ```philio_pat02b_00_000``` | | | Philio Technology Corp | [PAT02-C](philio/pat02c_0_0.md) | | ```philio_pat02c_00_000``` | | | Philio Technology Corp | [PSE02](philio/pse02_0_0.md) | | ```philio_pse02_00_000``` | | @@ -516,14 +521,14 @@ and links to more detailed information about each thing. | Popp & Co | [123610](popp/123610_0_0.md) | | ```popp_123610_00_000``` | | | Popp & Co | [123665](popp/123665_0_0.md) | | ```popp_123665_00_000``` | | | Popp & Co | [POPE700052](popp/pope700052_0_0.md) | | ```popp_pope700052_00_000``` | | -| Popp & Co | [POPE700168](popp/pope700168_0_0.md) | | ```popp_pope700168_00_000``` | | +| Popp & Co | [POPE700168](popp/pope700168_0_0.md) | | ```popp_pope700168_00_000``` | Sensor | | Prodrive Technologies | [ED2.0](prodrive/ed20_0_0.md) | | ```prodrive_ed20_00_000``` | | | Qees | [P313A](qees/p313a_0_0.md) | | ```qees_p313a_00_000``` | | | Qees | [Qees Wall](qees/qeeswall_0_0.md) | | ```qees_qeeswall_00_000``` | | | Goap | [Smart Plug 16A](qubino/smartplug_0_0.md) | | ```qubino_smartplug_00_000``` | Power Outlet | | Goap | [ZMNHAA](qubino/zmnhaa_0_0.md) | | ```qubino_zmnhaa_00_000``` | Wall Switch | | Goap | [ZMNHAD](qubino/zmnhad_0_0.md) | | ```qubino_zmnhad_00_000``` | Wall Switch | -| Goap | [ZMNHBA](qubino/zmnhba_0_0.md) | | ```qubino_zmnhba_00_000``` | | +| Goap | [ZMNHBA](qubino/zmnhba_0_0.md) | | ```qubino_zmnhba_00_000``` | Wall Switch | | Goap | [ZMNHBD](qubino/zmnhbd_0_0.md) | | ```qubino_zmnhbd_00_000``` | Wall Switch | | Goap | [ZMNHCA](qubino/zmnhca_0_0.md) | | ```qubino_zmnhca_00_000``` | Blinds | | Goap | [ZMNHCD](qubino/zmnhcd_0_0.md) | 4.0 | ```qubino_zmnhcd_00_000``` | | @@ -589,9 +594,9 @@ and links to more detailed information about each thing. | Shenzhen Neo Electronics Co., Ltd | [Flood sensor](shenzhen/floodsensor_0_0.md) | | ```shenzhen_floodsensor_00_000``` | Sensor | | Shenzhen Neo Electronics Co., Ltd | [Motion Sensor](shenzhen/motionsensor_0_0.md) | | ```shenzhen_motionsensor_00_000``` | Motion Detector | | Shenzhen Neo Electronics Co., Ltd | [Motion Sensor IN](shenzhen/motionsensorin_0_0.md) | | ```shenzhen_motionsensorin_00_000``` | | +| Shenzhen Neo Electronics Co., Ltd | [NAS-AB01Z](shenzhen/nasab01z_0_0.md) | | ```shenzhen_nasab01z_00_000``` | Siren | | Shenzhen Neo Electronics Co., Ltd | [NAS-DS01Z](shenzhen/nasds01z_0_0.md) | | ```shenzhen_nasds01z_00_000``` | | | Shenzhen Neo Electronics Co., Ltd | [NAS-WR01ZE](shenzhen/powerplug_0_0.md) | | ```shenzhen_powerplug_00_000``` | Power Outlet | -| Shenzhen Neo Electronics Co., Ltd | [Siren Alarm](shenzhen/sirenalarm_0_0.md) | | ```shenzhen_sirenalarm_00_000``` | | | Shenzhen Neo Electronics Co., Ltd | [SOS/Remote Control](shenzhen/sosremotecontrol_0_0.md) | | ```shenzhen_sosremotecontrol_00_000``` | Remote Control | | SIEGENIA-AUBI KG | [Sensoair](siegeniaaubi/sensoair_0_0.md) | | ```siegeniaaubi_sensoair_00_000``` | | | Sigma Designs (Former Zensys) | [M417_9E](sigma/m4179e_0_0.md) | | ```sigma_m4179e_00_000``` | | @@ -605,14 +610,15 @@ and links to more detailed information about each thing. | Steinel | [RS LED D2 Z-Wave](steinel/rsledd2_0_0.md) | | ```steinel_rsledd2_00_000``` | Light Bulb | | Steinel | [XLED Home 2](steinel/xledhome2_0_0.md) | | ```steinel_xledhome2_00_000``` | Light Bulb | | Stelpro | [STZW402](stelpro/stzw402_0_0.md) | | ```stelpro_stzw402_00_000``` | | -| Sunricher | [ZV9001K8-DIM](sunricher/zv9001k8dim_0_0.md) | | ```sunricher_zv9001k8dim_00_000``` | Wall Switch | | Sunricher | [ZV9001T4-DIM](sunricher/zv9001t4dim_0_0.md) | | ```sunricher_zv9001t4dim_00_000``` | Wall Switch | | Sunricher | [ZV9102FA-CCT](sunricher/zv9102facct_0_0.md) | | ```sunricher_zv9102facct_00_000``` | Light Bulb | | Systemair Sverige AS | [29990](systemair/29990_0_0.md) | | ```systemair_29990_00_000``` | HVAC | | Telldus Technologies AB | [TZDW-100](telldus/tzdw100_0_0.md) | | ```telldus_tzdw100_00_000``` | | | Telldus Technologies AB | [TZWP-100](telldus/tzwp100_0_0.md) | | ```telldus_tzwp100_00_000``` | Power Outlet | +| Telldus Technologies AB | [TZWP-102](telldus/tzwp102_0_0.md) | | ```telldus_tzwp102_00_000``` | Power Outlet | | ThermoFloor | [TF016](thermofloor/tf016_0_0.md) | 1.7 | ```thermofloor_tf016_00_000``` | HVAC | | ThermoFloor | [TF016](thermofloor/tf016_1_8.md) | 1.8 | ```thermofloor_tf016_01_008``` | HVAC | +| ThermoFloor | [Heatit Z-TRM 2](thermofloor/ztrm2_2_6.md) | 2.6 | ```thermofloor_ztrm2_02_006``` | HVAC | | TKB Home | [GR308](tkb/gr308_0_0.md) | | ```tkb_gr308_00_000``` | | | TKB Home | [TSM02](tkb/tsm02_0_0.md) | | ```tkb_tsm02_00_000``` | Sensor | | TKB Home | [TZ04](tkb/tz04_0_0.md) | | ```tkb_tz04_00_000``` | | @@ -657,7 +663,7 @@ and links to more detailed information about each thing. | Vision Security | [PID15903](vision/pid15903_0_0.md) | | ```vision_pid15903_00_000``` | Power Outlet | | Vision Security | [ZD2102](vision/zd2102_0_0.md) | | ```vision_zd2102_00_000``` | Door | | Vision Security | [ZD2102-5](vision/zd2102plus_0_0.md) | | ```vision_zd2102plus_00_000``` | Door | -| Vision Security | [ZD2105](vision/zd2105_0_0.md) | | ```vision_zd2105_00_000``` | | +| Vision Security | [ZD2105](vision/zd2105_0_0.md) | | ```vision_zd2105_00_000``` | Door | | Vision Security | [ZD2201](vision/zd2201_0_0.md) | | ```vision_zd2201_00_000``` | Sensor | | Vision Security | [ZF5201EU-5](vision/zf5201eu_0_0.md) | | ```vision_zf5201eu_00_000``` | Sensor | | Vision Security | [ZG8101](vision/zg8101_0_0.md) | | ```vision_zg8101_00_000``` | | @@ -697,6 +703,7 @@ and links to more detailed information about each thing. | Willis Electric Co., Ltd. | [ZW691](willis/zw691_0_0.md) | | ```willis_zw691_00_000``` | Power Outlet | | Wintop | [iModuleDouble](wintop/1122r_1_4.md) | 1.4 | ```wintop_1122r_01_004``` | | | Wintop | [PlugInSwitch](wintop/dhsitswpdhs_0_0.md) | | ```wintop_dhsitswpdhs_00_000``` | | +| Wintop | [DHS-WIN-BLW-DHS](wintop/dhswinblwdhs_0_0.md) | | ```wintop_dhswinblwdhs_00_000``` | Blinds | | Wintop | [DHSZWDMIW01](wintop/dhszwdmiw01_0_0.md) | | ```wintop_dhszwdmiw01_00_000``` | | | Wintop | [Digital Home Systems](wintop/digitalhomesystems_0_0.md) | | ```wintop_digitalhomesystems_00_000``` | | | Wintop | [EasyPlug](wintop/easyplug_0_0.md) | | ```wintop_easyplug_00_000``` | | @@ -737,6 +744,7 @@ and links to more detailed information about each thing. | Zooz | [ZSE33](zooz/zse33_0_0.md) | | ```zooz_zse33_00_000``` | | | Zooz | [ZSE40](zooz/zse40_0_0.md) | | ```zooz_zse40_00_000``` | Sensor | | Z-Wave.Me | [06436](zwaveme/06436_0_0.md) | | ```zwaveme_06436_00_000``` | | +| Z-Wave.Me | [Haseman FGR-316-DIN](zwaveme/fgr316_0_0.md) | | ```zwaveme_fgr316_00_000``` | Power Outlet | | Z-Wave.Me | [HS1DS](zwaveme/hs1ds_0_0.md) | | ```zwaveme_hs1ds_00_000``` | Window | | Z-Wave.Me | [KFOB](zwaveme/kfob_0_0.md) | | ```zwaveme_kfob_00_000``` | | | Z-Wave.Me | [WALLC-S](zwaveme/wallcs_0_0.md) | | ```zwaveme_wallcs_00_000``` | Wall Switch | diff --git a/_addons_bindings/zwave/doc/tkb/gr308_0_0.md b/_addons_bindings/zwave/doc/tkb/gr308_0_0.md index 95cda6f915..eaf5a3c38b 100644 --- a/_addons_bindings/zwave/doc/tkb/gr308_0_0.md +++ b/_addons_bindings/zwave/doc/tkb/gr308_0_0.md @@ -8,12 +8,15 @@ title: GR308 - ZWave # GR308 Lifting Controller (Blinds Controller) This describes the Z-Wave device *GR308*, manufactured by *TKB Home* with the thing type UID of ```tkb_gr308_00_000```. -The GR308 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The GR308 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/712) to improve the documentation. +### Wakeup Information +The GR308 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the GR308 -: diff --git a/_addons_bindings/zwave/doc/tkb/tsm02_0_0.md b/_addons_bindings/zwave/doc/tkb/tsm02_0_0.md index 67da49b858..3981f60f54 100644 --- a/_addons_bindings/zwave/doc/tkb/tsm02_0_0.md +++ b/_addons_bindings/zwave/doc/tkb/tsm02_0_0.md @@ -12,12 +12,15 @@ The device is in the category of *Sensor*, defining Device used to measure somet The TSM02 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The TSM02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The TSM02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/162) to improve the documentation. +### Wakeup Information +The TSM02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the TSM02 -: diff --git a/_addons_bindings/zwave/doc/tkb/tz55d_0_0.md b/_addons_bindings/zwave/doc/tkb/tz55d_0_0.md index 66b007777f..06eb66768c 100644 --- a/_addons_bindings/zwave/doc/tkb/tz55d_0_0.md +++ b/_addons_bindings/zwave/doc/tkb/tz55d_0_0.md @@ -17,7 +17,15 @@ The TZ55D supports routing. This allows the device to communicate using other ro ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/516) to improve the documentation. +Dual Paddle Wall Dimmer, AC230V 50Hz, 1380W×2 + +### Inclusion Information + +Pressing On/Off button three times within 1.5 seconds will enter inclusion mode. + +### Exclusion Information + +Pressing On/Off button three times within 1.5 seconds will enter exclusion mode. ## Channels @@ -53,13 +61,115 @@ The ```scene_number``` channel supports the ```Number``` item. ## Device Configuration -The device has no configuration parameters configured. +The following table provides a summary of the 5 configuration parameters available in the TZ55D. +Detailed information on each parameter can be found in the sections below. + +| Param | Name | Description | +|-------|-------|-------------| +| 1 | Night Light | LED Mode | +| 2 | Memory Function | Switch memory function | +| 3 | Invert Switch | Reverse switch direction | +| 4 | LED Transmission Indication | Set LED flickering mode | +| 5 | Suspend Group 4 | Disable transmitting commands to devices that are in Group 4 | +| | Switch All Mode | Set the mode for the switch when receiving SWITCH ALL commands | + +### Parameter 1: Night Light + +LED Mode +The LED on the switch will by default, turn ON when the load attached is turn OFF. To make the LED turn ON when the load attached is turn ON instead, set parameter 1 to a value of 1. +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```. + + +### Parameter 2: Memory Function + +Switch memory function +Stated in the above form, switch by default value is 1, when the value is 0, switch memory function not open; when the value is 1, open switch memory function. +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_2_1``` and is of type ```INTEGER```. + + +### Parameter 3: Invert Switch + +Reverse switch direction +To change the top of the switch to OFF and the bottom of the switch ON, set parameter 3 to 1. +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. +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```0```. + +This parameter has the configuration ID ```config_3_1``` and is of type ```INTEGER```. + + +### Parameter 4: LED Transmission Indication + +Set LED flickering mode +The switch 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 2), or to flicker for only 1 second when it begins transmitting (set to 1). +By default, the switch is set to flicker for only 1 second. +Values in the range 0 to 2 may be set. + +The manufacturer defined default value is ```1```. + +This parameter has the configuration ID ```config_4_1``` and is of type ```INTEGER```. + + +### Parameter 5: Suspend Group 4 + +Disable transmitting commands to devices that are in Group 4 +You may wish to disable transmitting commands to Z-Wave devices that are in Group 4 without “disassociating” those devices from from the group. Setting parameter 5 to the value of 1 will stop the switch from transmitting to devices that are “associated” into Group 4. +Values in the range 0 to 1 may be set. + +The manufacturer defined default value is ```0```. + +This parameter has the configuration ID ```config_5_1``` and is of type ```INTEGER```. + +### Switch All Mode + +Set the mode for the switch when receiving SWITCH ALL commands. + +The following option values may be configured -: +| Value | Description | +|--------|-------------| +| 0 | Exclude from All On and All Off groups | +| 1 | Include in All On group | +| 2 | Include in All Off group | +| 255 | Include in All On and All Off groups | + +This parameter has the configuration ID ```switchall_mode``` and is of type ```INTEGER```. + ## Association Groups Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic. -The device does not support associations. +The TZ55D supports 4 association groups. + +### Group 1: Lifeline + +Group 1 Control +This group supports 5 nodes. + +### Group 2: On/Off Dimmer 1 + +Group 2 Control +This group supports 5 nodes. + +### Group 3: On/off dimmer 2 + +Group 3 Control +This group supports 5 nodes. + +### Group 4: Wireless + +Group 4 Control +This group supports 5 nodes. + ## Technical Information ### Endpoints diff --git a/_addons_bindings/zwave/doc/tkb/tz75_0_0.md b/_addons_bindings/zwave/doc/tkb/tz75_0_0.md index 3345790d7d..1a2d7aed6b 100644 --- a/_addons_bindings/zwave/doc/tkb/tz75_0_0.md +++ b/_addons_bindings/zwave/doc/tkb/tz75_0_0.md @@ -17,7 +17,21 @@ The TZ75 supports routing. This allows the device to communicate using other rou ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/801) to improve the documentation. +This in-wall Roller Shutter Controller is able to detect the position of the shutter by using the patterned power measuring method, so it can not only be positioned fully up or down, but can also be adjusted to any position between 0 and 100%. + +Installation hint: lt is important to carry out a shutter calibration process. Press the On/Off button over 3 seconds and release it before the 6th second, the roller shutter controller will start the shutter calibration process. The process is composed of three continue stages. The shutter move to the BOTTOM in first stage, and move to the TOP in second stage, and move to the BOTTOM again in 1-second intervals third stage. Then the TZ75 will know the total range of UP and DOWN. + +### Inclusion Information + +1\. Have Z-Wave controller entered inclusion mode. + +2\. Pressing On/Off button three times within 1.5 seconds will enter inclusion mode. + +### Exclusion Information + +1\. Have Z-Wave controller entered exclusion mode. + +2\. Pressing On/Off button three times within 1.5 seconds will enter exclusion mode. ## Channels @@ -85,16 +99,16 @@ Detailed information on each parameter can be found in the sections below. | Param | Name | Description | |-------|-------|-------------| -| 1 | Watt meter report periode | Watt meter report periode | +| 1 | Watt meter report period | Watt meter report period | | 2 | KWH Meter Report period | KWH Meter Report period | | 3 | Treshold of watt for load caution | Treshold of watt for load caution | | 4 | Treshold of KWH for load caution | Treshold of KWH for load caution | | | Switch All Mode | Set the mode for the switch when receiving SWITCH ALL commands | -### Parameter 1: Watt meter report periode - -Watt meter report periode +### Parameter 1: Watt meter report period +Watt meter report period +If the setting is configured for 1 hour (set value =720), the TZ75 will report its instant power consumption every 1 hour to the node of the corresponding group. The maximum interval to report its instant power consumption is 45 hours (5s\*32767/3600=45h). Values in the range 1 to 32767 may be set. The manufacturer defined default value is ```720```. @@ -105,7 +119,7 @@ This parameter has the configuration ID ```config_1_2``` and is of type ```INTEG ### Parameter 2: KWH Meter Report period KWH Meter Report period - +If the setting is configured for 1 hour (set value =6), the TZ75 will report its accumulated power consumption (KW/h) every 1 hour to the node of the corresponding group. The maximum interval to report its accumulated power consumption (KW/h) is 227.55 days (10min\*32767/1440=227.55 days). Values in the range 1 to 32767 may be set. The manufacturer defined default value is ```6```. @@ -116,7 +130,9 @@ This parameter has the configuration ID ```config_2_2``` and is of type ```INTEG ### Parameter 3: Treshold of watt for load caution Treshold of watt for load caution +This is the maximum power consuption which is allowed during acivation of the Roller Shutter relays up or down. Set the threshold high enough to prevent from overloads in winter etc. when the motor needs slightly more power. +When an overload state occurs, the TZ75 gets disabled and the LED flashes in 0.5 second intervals. The overload state can be cleared by disconnecting and reconnecting the TZ75 main power. Values in the range 10 to 1100 may be set. The manufacturer defined default value is ```1100```. @@ -127,7 +143,7 @@ This parameter has the configuration ID ```config_3_2``` and is of type ```INTEG ### Parameter 4: Treshold of KWH for load caution Treshold of KWH for load caution - +The default value 0 will disable the KWh warning. Values in the range 0 to 10000 may be set. The manufacturer defined default value is ```0```. @@ -178,7 +194,7 @@ This group supports 1 nodes. | COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| | | COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | | COMMAND_CLASS_CONFIGURATION_V1| | -| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| | +| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V2| | | COMMAND_CLASS_POWERLEVEL_V1| | | COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| | | COMMAND_CLASS_ASSOCIATION_V2| | diff --git a/_addons_bindings/zwave/doc/tkb/tz77_0_0.md b/_addons_bindings/zwave/doc/tkb/tz77_0_0.md index 158e85197e..486120c8db 100644 --- a/_addons_bindings/zwave/doc/tkb/tz77_0_0.md +++ b/_addons_bindings/zwave/doc/tkb/tz77_0_0.md @@ -13,7 +13,7 @@ The device is in the category of *Light Bulb*, defining Devices that illuminate ![TZ77 product image](https://www.cd-jackson.com/zwave_device_uploads/842/842_default.jpg) -The TZ77 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The TZ77 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -32,6 +32,11 @@ Pressing ON/OFF button three times within 1.5 seconds will enter inclusion mode. Pressing ON/OFF button three times within 1.5 seconds will enter exclusion mode. +### Wakeup Information + +The TZ77 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the TZ77 -: diff --git a/_addons_bindings/zwave/doc/uei/45601_0_0.md b/_addons_bindings/zwave/doc/uei/45601_0_0.md index 3b4e55a4a9..737d13c9a2 100644 --- a/_addons_bindings/zwave/doc/uei/45601_0_0.md +++ b/_addons_bindings/zwave/doc/uei/45601_0_0.md @@ -8,12 +8,15 @@ title: 45601 - ZWave # 45601 Advanced Remote Wireless Lighting Control This describes the Z-Wave device *45601*, manufactured by *Universal Electronics Inc.* with the thing type UID of ```uei_45601_00_000```. -The 45601 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The 45601 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/768) to improve the documentation. +### Wakeup Information +The 45601 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the 45601 -: diff --git a/_addons_bindings/zwave/doc/ufairy/tp807zg_0_0.md b/_addons_bindings/zwave/doc/ufairy/tp807zg_0_0.md index 833a914b70..3590875ac9 100644 --- a/_addons_bindings/zwave/doc/ufairy/tp807zg_0_0.md +++ b/_addons_bindings/zwave/doc/ufairy/tp807zg_0_0.md @@ -13,7 +13,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet ![TP-807ZG product image](https://www.cd-jackson.com/zwave_device_uploads/837/837_default.jpg) -The TP-807ZG does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The TP-807ZG does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -27,6 +27,11 @@ press the button 3 times quickly press the button 3 times quickly +### Wakeup Information + +The TP-807ZG does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the TP-807ZG -: diff --git a/_addons_bindings/zwave/doc/ufairy/zse02_0_0.md b/_addons_bindings/zwave/doc/ufairy/zse02_0_0.md index 40a1070e4f..0be67d60ea 100644 --- a/_addons_bindings/zwave/doc/ufairy/zse02_0_0.md +++ b/_addons_bindings/zwave/doc/ufairy/zse02_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet The ZSE02 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZSE02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZSE02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -23,6 +23,11 @@ The ZSE02 does not permanently listen for messages sent from the controller - it Press the button on the motion sensor TWICE quickly to enable motion detection, make sure the button is pushed in when you finish the process. +### Wakeup Information + +The ZSE02 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZSE02 -: diff --git a/_addons_bindings/zwave/doc/vda/euboiler_0_0.md b/_addons_bindings/zwave/doc/vda/euboiler_0_0.md index 979fd8e941..1689a32485 100644 --- a/_addons_bindings/zwave/doc/vda/euboiler_0_0.md +++ b/_addons_bindings/zwave/doc/vda/euboiler_0_0.md @@ -8,12 +8,15 @@ title: Vitrum I EU Boiler - ZWave # Vitrum I EU Boiler Vitrum touch timer switch Dual Relay This describes the Z-Wave device *Vitrum I EU Boiler*, manufactured by *VDA* with the thing type UID of ```vda_euboiler_00_000```. -The Vitrum I EU Boiler does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Vitrum I EU Boiler does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/683) to improve the documentation. +### Wakeup Information +The Vitrum I EU Boiler does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the Vitrum I EU Boiler -: diff --git a/_addons_bindings/zwave/doc/vemmio/mt100_0_0.md b/_addons_bindings/zwave/doc/vemmio/mt100_0_0.md index 5f57dc1cb2..e3bc8d6809 100644 --- a/_addons_bindings/zwave/doc/vemmio/mt100_0_0.md +++ b/_addons_bindings/zwave/doc/vemmio/mt100_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet The MT-100 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The MT-100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The MT-100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -35,6 +35,10 @@ When prompted by the controller, press quickly one of the Z-wave button 3 times ### Wakeup Information +The MT-100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + You can press the button once to wake up the device and send wakeup notification to controller -the LED will flash once. ## Channels diff --git a/_addons_bindings/zwave/doc/vision/zd2102_0_0.md b/_addons_bindings/zwave/doc/vision/zd2102_0_0.md index 51938c8844..821bacd117 100644 --- a/_addons_bindings/zwave/doc/vision/zd2102_0_0.md +++ b/_addons_bindings/zwave/doc/vision/zd2102_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Door*, defining Door sensors. The ZD2102 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZD2102 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZD2102 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/105) to improve the documentation. +### Wakeup Information +The ZD2102 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZD2102 -: diff --git a/_addons_bindings/zwave/doc/vision/zd2102plus_0_0.md b/_addons_bindings/zwave/doc/vision/zd2102plus_0_0.md index 6c5307b9bb..08789da068 100644 --- a/_addons_bindings/zwave/doc/vision/zd2102plus_0_0.md +++ b/_addons_bindings/zwave/doc/vision/zd2102plus_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Door*, defining Door sensors. The ZD2102-5 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZD2102-5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZD2102-5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/816) to improve the documentation. +### Wakeup Information +The ZD2102-5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZD2102-5 -: diff --git a/_addons_bindings/zwave/doc/vision/zd2105_0_0.md b/_addons_bindings/zwave/doc/vision/zd2105_0_0.md index 18839e1e44..29edf3f851 100644 --- a/_addons_bindings/zwave/doc/vision/zd2105_0_0.md +++ b/_addons_bindings/zwave/doc/vision/zd2105_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Door*, defining Door sensors. The ZD2105 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZD2105 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZD2105 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -37,6 +37,10 @@ Note: All user and network settings will be cleared and the device reset to fact ### Wakeup Information +The ZD2105 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Awake Mode: It will be triggering after opening the cover, also the red LED will keep on lasting 10 seconds and ZD2105 will send “Wake Up Notification” after 10 seconds. If ZD2105 received “Wake Up No More Information” command then the red LED will go off or it will wait 10 seconds then go off. It will proceed all the commands after sending the “Wake Up Notification” diff --git a/_addons_bindings/zwave/doc/vision/zd2201_0_0.md b/_addons_bindings/zwave/doc/vision/zd2201_0_0.md index 286d123464..82e6934757 100644 --- a/_addons_bindings/zwave/doc/vision/zd2201_0_0.md +++ b/_addons_bindings/zwave/doc/vision/zd2201_0_0.md @@ -15,12 +15,17 @@ The device is in the category of *Sensor*, defining Device used to measure somet The ZD2201 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZD2201 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZD2201 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview Contact/temperature/humidity/luminance sensor. Can also be called Zipato Quad Sensor (Z+). +### Wakeup Information + +The ZD2201 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZD2201 -: diff --git a/_addons_bindings/zwave/doc/vision/zf5201eu_0_0.md b/_addons_bindings/zwave/doc/vision/zf5201eu_0_0.md index e5be6dd2aa..58ed78eda4 100644 --- a/_addons_bindings/zwave/doc/vision/zf5201eu_0_0.md +++ b/_addons_bindings/zwave/doc/vision/zf5201eu_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet The ZF5201EU-5 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZF5201EU-5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZF5201EU-5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -31,6 +31,10 @@ For “Exclusion” from (removing from) a network: Put the Z-Wave™ Interface ### Wakeup Information +The ZF5201EU-5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + ”Awake” mode: it is to leave the “Sleep” mode by removing the cover of ZF5201, to allow the Z-Wave™ Interface Controller to do “Inclusion”, “Exclusion”, “Association” and to reply and receive the commands from controller ## Channels diff --git a/_addons_bindings/zwave/doc/vision/zg8101_0_0.md b/_addons_bindings/zwave/doc/vision/zg8101_0_0.md index beb925401c..a1ee55394b 100644 --- a/_addons_bindings/zwave/doc/vision/zg8101_0_0.md +++ b/_addons_bindings/zwave/doc/vision/zg8101_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *ZG8101*, manufactured by *[Vision Security](ht The ZG8101 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZG8101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZG8101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/103) to improve the documentation. +### Wakeup Information +The ZG8101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZG8101 -: diff --git a/_addons_bindings/zwave/doc/vision/zl7101_0_0.md b/_addons_bindings/zwave/doc/vision/zl7101_0_0.md index 2066c748f4..db50af3fba 100644 --- a/_addons_bindings/zwave/doc/vision/zl7101_0_0.md +++ b/_addons_bindings/zwave/doc/vision/zl7101_0_0.md @@ -8,12 +8,15 @@ title: ZL7101 - ZWave # ZL7101 Lamp Dimmer Module This describes the Z-Wave device *ZL7101*, manufactured by *[Vision Security](http://www.visionsecurity.com.tw/)* with the thing type UID of ```vision_zl7101_00_000```. -The ZL7101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZL7101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/371) to improve the documentation. +### Wakeup Information +The ZL7101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZL7101 -: diff --git a/_addons_bindings/zwave/doc/vision/zm1602_0_0.md b/_addons_bindings/zwave/doc/vision/zm1602_0_0.md index ea059f18cc..1fd0960ae8 100644 --- a/_addons_bindings/zwave/doc/vision/zm1602_0_0.md +++ b/_addons_bindings/zwave/doc/vision/zm1602_0_0.md @@ -18,7 +18,17 @@ The ZM1602 supports routing. This allows the device to communicate using other r ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/109) to improve the documentation. +Thanks for choosing the Vision’s wireless siren & strobe alarm of the home security device. This sensor is a Z-Wave™ enabled device (interoperable, two-way RF mesh networking technology) and is fully compatible with any Z-Wave™ enabled network and it’s security framework. Every mains powered Z-Wave™ enabled device acts as a signal repeater and multiple devices result in more possible transmission routes which helps eliminate “RF dead-sports”. + +Z-Wave™ enabled devices displaying the Z-Wave™ logo can also be used with it regardless of the manufacturer, and ours can also be used in other manufacturer’s Z-Wave™ enabled networks. This product will sound a loud siren and flash a strobe light when an alarm message or alert is received on any Z-Wave™ enabled network. When the ZM 1602 main power has dropped out, the backup batteries will automatically install. When the device is secure included into Z-Wave network, above communication will be encrypted + +### Inclusion Information + +For “Inclusion” in (adding to) a network: Put the Z-Wave™ Interface Controller into “inclusion” mode, and following its instruction to add the ZM 1602 to your controller. To get in the “inclusion” mode, the distance between siren and controller is suggested to be in one meter. Open the bracket and press the program switch of ZM 1602 for 1 second at least & release to be included. After setting, the LED Setting Lighting should go off, if not, please try again. (After sending one time’s Z-Wave NIF and not be included then it will send 4 times NWI in every 4 ~ 6 seconds for auto inclusion. The LED Setting Light will flash again if the siren has not been included or the LED Setting Light will go off after inclusion.) + +### Exclusion Information + +For “Exclusion” from (removing from) a network: Set up the Z-Wave™ Interface Controller into “exclusion” mode, and following its instruction to delete the ZM 1602 from your controller. Press the Tamper Switch of ZM 1602 for 1 second at least & release to be excluded. 9. Note: a. LED setting light will flash continuously in Exclusion condition. b. All user and network settings will be cleared and the device reset to factory defaults when the device is excluded. c. ZM 1602 can only connect to DC 12~39V, AC 9~28V Power adaptor d. ZM 1602 is extremely LOUD, please don’t near your ear when you test! ## Channels diff --git a/_addons_bindings/zwave/doc/vision/zp3102_0_0.md b/_addons_bindings/zwave/doc/vision/zp3102_0_0.md index 0997ca59b2..d836c1f9fc 100644 --- a/_addons_bindings/zwave/doc/vision/zp3102_0_0.md +++ b/_addons_bindings/zwave/doc/vision/zp3102_0_0.md @@ -11,12 +11,15 @@ This version of the device is limited to firmware versions below 7.99 The ZP3102 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZP3102 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZP3102 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/104) to improve the documentation. +### Wakeup Information +The ZP3102 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZP3102 -: diff --git a/_addons_bindings/zwave/doc/vision/zp3102_8_0.md b/_addons_bindings/zwave/doc/vision/zp3102_8_0.md index cbeccba89a..3ba1703cae 100644 --- a/_addons_bindings/zwave/doc/vision/zp3102_8_0.md +++ b/_addons_bindings/zwave/doc/vision/zp3102_8_0.md @@ -13,7 +13,7 @@ The device is in the category of *Motion Detector*, defining Motion sensors/dete The ZP3102 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZP3102 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZP3102 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -29,6 +29,10 @@ Put the Z-Wave Interface Controller into “exclusion” mode, and following its ### Wakeup Information +The ZP3102 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Remove the rear cover to wake up the device, or set the wake up interval time from 10 minutes to 1 week. The battery will be drained quickly if you fail to replace the cover after using that method to wake up the device. ## Channels diff --git a/_addons_bindings/zwave/doc/vision/zp3103_0_0.md b/_addons_bindings/zwave/doc/vision/zp3103_0_0.md index 324d1dcf97..5677a12324 100644 --- a/_addons_bindings/zwave/doc/vision/zp3103_0_0.md +++ b/_addons_bindings/zwave/doc/vision/zp3103_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *ZP3103*, manufactured by *[Vision Security](ht The ZP3103 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZP3103 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZP3103 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/316) to improve the documentation. +### Wakeup Information +The ZP3103 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZP3103 -: diff --git a/_addons_bindings/zwave/doc/vision/zs5101_0_0.md b/_addons_bindings/zwave/doc/vision/zs5101_0_0.md index 7b43761a19..998c90721c 100644 --- a/_addons_bindings/zwave/doc/vision/zs5101_0_0.md +++ b/_addons_bindings/zwave/doc/vision/zs5101_0_0.md @@ -13,7 +13,7 @@ This describes the Z-Wave device *ZS5101*, manufactured by *[Vision Security](ht The ZS5101 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZS5101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZS5101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -29,6 +29,10 @@ For "Exclusion" from (removing from) a network: Put the Z-Wave Interface Control ### Wakeup Information +The ZS5101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + "Awake" mode: it is to leave the "Sleep" mode by removing the cover of ZS5101, to allow the Z-Wave Interface Controller to do "Inclusion", "Exclusion", "Association" and to reply and receive the commands from controller. ## Channels diff --git a/_addons_bindings/zwave/doc/vision/zs6101_0_0.md b/_addons_bindings/zwave/doc/vision/zs6101_0_0.md index 0222fe90d4..ee04497359 100644 --- a/_addons_bindings/zwave/doc/vision/zs6101_0_0.md +++ b/_addons_bindings/zwave/doc/vision/zs6101_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Smoke Detector*, defining Smoke detectors. The ZS6101 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZS6101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZS6101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/106) to improve the documentation. +### Wakeup Information +The ZS6101 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZS6101 -: diff --git a/_addons_bindings/zwave/doc/vision/zs6301_0_0.md b/_addons_bindings/zwave/doc/vision/zs6301_0_0.md index 2f2fa8b144..0df4f7a90b 100644 --- a/_addons_bindings/zwave/doc/vision/zs6301_0_0.md +++ b/_addons_bindings/zwave/doc/vision/zs6301_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *ZS6301*, manufactured by *[Vision Security](ht The ZS6301 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZS6301 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZS6301 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/107) to improve the documentation. +### Wakeup Information +The ZS6301 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZS6301 -: diff --git a/_addons_bindings/zwave/doc/vision/zse40_0_0.md b/_addons_bindings/zwave/doc/vision/zse40_0_0.md index a84970c594..8b0edaf612 100644 --- a/_addons_bindings/zwave/doc/vision/zse40_0_0.md +++ b/_addons_bindings/zwave/doc/vision/zse40_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Motion Detector*, defining Motion sensors/dete The ZSE40 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZSE40 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZSE40 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -51,6 +51,10 @@ The led indicator will flash 3 times when you take the batteries out and put the ### Wakeup Information +The ZSE40 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Use the Wake Up command to set wake-up interval for the sensor (from 10 minutes to 1 week) to report back to the controller. You can also press and release the Z-Wave button once to wake up the device manually. ## Channels diff --git a/_addons_bindings/zwave/doc/willis/nzw30t_0_0.md b/_addons_bindings/zwave/doc/willis/nzw30t_0_0.md index 488b18bb07..9b13d072f7 100644 --- a/_addons_bindings/zwave/doc/willis/nzw30t_0_0.md +++ b/_addons_bindings/zwave/doc/willis/nzw30t_0_0.md @@ -37,10 +37,6 @@ To remove your device, here’s what you need to do: - Press the UP button on your switch 6x rapidly (in a second or so) - Hopefully your device has been removed -### Wakeup Information - -N/A - ## Channels The following table summarises the channels available for the NZW30T -: diff --git a/_addons_bindings/zwave/doc/willis/zen21_0_0.md b/_addons_bindings/zwave/doc/willis/zen21_0_0.md index d0fe6f704c..4a2f5a3d82 100644 --- a/_addons_bindings/zwave/doc/willis/zen21_0_0.md +++ b/_addons_bindings/zwave/doc/willis/zen21_0_0.md @@ -66,10 +66,6 @@ If you are unable to include the Z-Wave switch to your controller, please try on Please repeat the process following all steps carefully if the first attempt is unsuccessful -### Wakeup Information - -The switch will be reset to factory defaults only by exclusion using a Z-Wave controller. You may use any certified Z-Wave controller to exclude and reset the switch. This device may not be reset manually when the network’s primary controller is missing or otherwise inoperable. NOTE: All previously recorded activity and custom settings will be erased from the device’s memory. - ## Channels The following table summarises the channels available for the ZEN21 -: diff --git a/_addons_bindings/zwave/doc/willis/zw691_0_0.md b/_addons_bindings/zwave/doc/willis/zw691_0_0.md index 2a5e5acbb4..ed22f51ccd 100644 --- a/_addons_bindings/zwave/doc/willis/zw691_0_0.md +++ b/_addons_bindings/zwave/doc/willis/zw691_0_0.md @@ -13,12 +13,15 @@ The device is in the category of *Power Outlet*, defining Small devices to be pl ![ZW691 product image](https://www.cd-jackson.com/zwave_device_uploads/775/775_default.png) -The ZW691 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZW691 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/775) to improve the documentation. +### Wakeup Information +The ZW691 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZW691 -: diff --git a/_addons_bindings/zwave/doc/digitalhome/dhswinblw_0_0.md b/_addons_bindings/zwave/doc/wintop/dhswinblwdhs_0_0.md similarity index 61% rename from _addons_bindings/zwave/doc/digitalhome/dhswinblw_0_0.md rename to _addons_bindings/zwave/doc/wintop/dhswinblwdhs_0_0.md index 9b70556947..9cab7985d4 100644 --- a/_addons_bindings/zwave/doc/digitalhome/dhswinblw_0_0.md +++ b/_addons_bindings/zwave/doc/wintop/dhswinblwdhs_0_0.md @@ -6,16 +6,22 @@ title: DHS-WIN-BLW-DHS - ZWave {% include base.html %} # DHS-WIN-BLW-DHS Blind controller -This describes the Z-Wave device *DHS-WIN-BLW-DHS*, manufactured by *[Digital Home Systems Pty Ltd,](https://digitalhomesystems.com.au/)* with the thing type UID of ```digitalhome_dhswinblw_00_000```. +This describes the Z-Wave device *DHS-WIN-BLW-DHS*, manufactured by *Wintop* with the thing type UID of ```wintop_dhswinblwdhs_00_000```. The device is in the category of *Blinds*, defining Roller shutters, window blinds, etc.. -![DHS-WIN-BLW-DHS product image](https://www.cd-jackson.com/zwave_device_uploads/850/850_default.jpg) +![DHS-WIN-BLW-DHS product image](https://www.cd-jackson.com/zwave_device_uploads/859/859_default.png) +The DHS-WIN-BLW-DHS supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. + ## Overview -The DHS Z-Wave AC Motor Shutter Controller DHS-WIN-BLW-DHS is Z-Wave Shutter device specifically designed for use in smart homes and offices. The product allows to operate roller blinds/shutters wirelessly using a Z-wave enabled (AUS/NZ version 921.42 MHz) controllers (compatible universal remote controllers, control panels, gateways, PC with Z-Wave USB dongle) or manually via connected manual switch. The shutter controller can act as a wireless repeater to ensure that commands intended for another device in the network are received. This is useful to eliminate “RF deadspots” when the radio range of the Z-Wave network is inuenced. This function is part of the Z-Wave network functionality and is set up via Z-Wave controller. +The DHS Z-Wave AC Motor Shutter Controller DHS-WIN-BLW-DHS is Z-Wave Shutter device specifically designed for use in smart homes and offices. + +The product allows to operate roller blinds/shutters wirelessly using a Z-wave enabled (AUS/NZ version 921.42 MHz) controllers (compatible universal remote controllers, control panels, gateways, PC with Z-Wave USB dongle) or manually via connected manual switch. + +The shutter controller can act as a wireless repeater to ensure that commands intended for another device in the network are received. This is useful to eliminate “RF deadspots” when the radio range of the Z-Wave network is influenced. This function is part of the Z-Wave network functionality and is set up via Z-Wave controller. ### Inclusion Information @@ -36,20 +42,28 @@ The following table summarises the channels available for the DHS-WIN-BLW-DHS -: | Channel | Channel Id | Category | Item Type | |---------|------------|----------|-----------| -| Blinds | blinds_control | Blinds | Rollershutter | -| Blinds | blinds_control | Blinds | Rollershutter | +| Switch | switch_binary | Switch | Switch | +| Dimmer | switch_dimmer | DimmableLight | Dimmer | +| Scene Number | scene_number | | Number | + +### Switch -### Blinds +Switch the power on and off. -Provides start / stop control of blinds. +The ```switch_binary``` channel supports the ```Switch``` item and is in the ```Switch``` category. -The ```blinds_control``` channel supports the ```Rollershutter``` item and is in the ```Blinds``` category. +### Dimmer -### Blinds +The brightness channel allows to control the brightness of a light. + It is also possible to switch the light on and off. -Provides start / stop control of blinds. +The ```switch_dimmer``` channel supports the ```Dimmer``` item and is in the ```DimmableLight``` category. -The ```blinds_control``` channel supports the ```Rollershutter``` item and is in the ```Blinds``` category. +### Scene Number + +Triggers when a scene button is pressed. + +The ```scene_number``` channel supports the ```Number``` item. @@ -60,24 +74,27 @@ Detailed information on each parameter can be found in the sections below. | Param | Name | Description | |-------|-------|-------------| -| 1 | Buttons mode | Buttons mode | -| 2 | Automatically close after | If not zero, automatically close blind after a user deö ned time | -| 3 | What to do on RF close command | How to interpret RF Off command | -| 4 | Typical click timeout | Typical time used to diff erentiate click, hold, double and triple clicks | -| 5 | Invert buttons | | -| 6 | Action on button press or hold | Which command should be sent to Association group on button press or hold | -| 7 | LED mode | Set LED indication mode | +| 1 | Buttons mode | Set number and type of directly connected buttons | +| 2 | Automatically close after | If not zero, automatically close blind after a user defined time | +| 3 | What to do on RF close command | What to do on RF close command | +| 4 | Typical click timeout | Typical time used to differentiate click, hold, double and triple clicks | +| 5 | Invert buttons | Invert buttons | +| 6 | Action on button press or hold | Which command sent to Association group on button press or hold. | +| 7 | Set LED indication mode | | | 10 | Full close time | Time to go from opened to closed state | | 11 | Full open time | Time to go from closed to open state | -| 12 | Node Id of the blocking device | Id of the device which can block movement of the blind | -| 13 | Command from the blocking node | Which command from the blocking node indicates blocking is disabled | -| 14 | Invert open and close relays | Exchange open and close relays | +| 12 | Node Id of the blocking device | Node Id of the blocking device | +| 13 | On which command from blocking node to enable the protection | On which command from blocking node to enable the protection | +| 14 | Invert open and close relays | Invert open and close relays | | | Switch All Mode | Set the mode for the switch when receiving SWITCH ALL commands | ### Parameter 1: Buttons mode -Buttons mode -One push button: One button is used (chose any), press while moving up and down stops, while stopped moves to opposite direction to previous. // Two buttons with neutral position: Up click moves up if stopped and stops if moving down, Down click moves down if stopped and stops if moving up, Hold Up/Down moves in up/down, Release stops. // Two toggle switch: Switch to Up/Down moves up/down. // Two paddles with Power and Direction: Hold Up button to move blinds up. If Down button is pressed, blinds will move down. Release Up button to stop. +Set number and type of directly connected buttons +- One push button: One button is used (chose any), press while moving up and down stops, while stopped moves to opposite direction to previous. +- Two buttons with neutral position: Up click moves up if stopped and stops if moving down, Down click moves down if stopped and stops if moving up, Hold Up/Down moves in up/down, Release stops. +- Two toggle switch: Switch to Up/Down moves up/down. +- Two paddles with Power and Direction: Hold Up button to move blinds up. If Down button is pressed, blinds will move down. Release Up button to stop. The following option values may be configured -: | Value | Description | @@ -87,16 +104,16 @@ The following option values may be configured -: | 2 | Two toggle switch | | 3 | Two buttons with neutral position | -The manufacturer defined default value is ```3``` ( Two buttons with neutral position). +The manufacturer defined default value is ```3``` (Two buttons with neutral position). This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```. ### Parameter 2: Automatically close after -If not zero, automatically close blind after a user deö ned time +If not zero, automatically close blind after a user defined time -Values in the range 0 to 10 may be set. +Values in the range 0 to 255 may be set. The manufacturer defined default value is ```0```. @@ -105,8 +122,8 @@ This parameter has the configuration ID ```config_2_2``` and is of type ```INTEG ### Parameter 3: What to do on RF close command -How to interpret RF Off command -Defines how to interpret RF Off command. Can be used in conjunction with Auto Close function: Ignore - to open the door by motion detectors and close it back after some amount of time: in case of multiple motion detectors each would try to open that would break logics Open - to open on both On and Off paddle press on the remote and close after some amount of time. Button close click will still work (if button operations are not disabled). Note that Dim Down command will still begin close motion. +What to do on RF close command + The following option values may be configured -: | Value | Description | @@ -123,7 +140,7 @@ This parameter has the configuration ID ```config_3_1``` and is of type ```INTEG ### Parameter 4: Typical click timeout -Typical time used to diff erentiate click, hold, double and triple clicks +Typical time used to differentiate click, hold, double and triple clicks Values in the range 1 to 100 may be set. @@ -134,7 +151,7 @@ This parameter has the configuration ID ```config_4_1``` and is of type ```INTEG ### Parameter 5: Invert buttons - +Invert buttons The following option values may be configured -: @@ -150,23 +167,23 @@ This parameter has the configuration ID ```config_5_1``` and is of type ```INTEG ### Parameter 6: Action on button press or hold -Which command should be sent to Association group on button press or hold -Defines which command should be sent to Association group on button press or hold. Scene mode will send 1 for Up event, 2 for Stop, 3 for Down. +Which command sent to Association group on button press or hold. + The following option values may be configured -: | Value | Description | |--------|-------------| -| 1 | Switch On, Off and dim | +| 1 | Basic | | 2 | Send Scene | -The manufacturer defined default value is ```1``` (Switch On, Off and dim). +The manufacturer defined default value is ```1``` (Basic). This parameter has the configuration ID ```config_6_1``` and is of type ```INTEGER```. -### Parameter 7: LED mode +### Parameter 7: Set LED indication mode + -Set LED indication mode The following option values may be configured -: @@ -186,7 +203,7 @@ This parameter has the configuration ID ```config_7_1``` and is of type ```INTEG ### Parameter 10: Full close time Time to go from opened to closed state -Time to go from opened to closed state. Used to estimate the current level. Note that in Permanent motion mode the reported value would 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 opened to closed state. Used to estimate the current level. Note that in Permanent motion mode the reported value would be Closed or Opened, while all Basic and Multilevel Set values (1-99, 255) would Open except 0 value that would Close Values in the range 0 to 255 may be set. The manufacturer defined default value is ```60```. @@ -197,7 +214,7 @@ This parameter has the configuration ID ```config_10_1``` and is of type ```INTE ### Parameter 11: Full open time Time to go from closed to open state -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 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 be Closed or Opened, while all Basic and Multilevel Set values (1-99, 255) would Open except 0 value that would Close Values in the range 0 to 255 may be set. The manufacturer defined default value is ```60```. @@ -207,7 +224,7 @@ This parameter has the configuration ID ```config_11_1``` and is of type ```INTE ### Parameter 12: Node Id of the blocking device -Id of the device which can block movement of the blind +Node Id of the blocking device Id of the device which commands would be interpreted not as Open/Close, but as block/unblock. Useful with door opening detector: if the door is open, block the blind not to break shades while they move. Values in the range 0 to 24 may be set. @@ -216,26 +233,26 @@ The manufacturer defined default value is ```0```. This parameter has the configuration ID ```config_12_1``` and is of type ```INTEGER```. -### Parameter 13: Command from the blocking node - -Which command from the blocking node indicates blocking is disabled +### Parameter 13: On which command from blocking node to enable the protection +On which command from blocking node to enable the protection +Defines which command from blocking device to interpret as closed door and hence, unprotected. The following option values may be configured -: | Value | Description | |--------|-------------| -| 1 | on On | -| 1 | on Off | +| 0 | On | +| 1 | Off | -The manufacturer defined default value is ```0```. +The manufacturer defined default value is ```0``` (On). This parameter has the configuration ID ```config_13_1``` and is of type ```INTEGER```. ### Parameter 14: Invert open and close relays -Exchange open and close relays -Allow exchanging open and close relays if blind control is wired to the motor incorrectly +Invert open and close relays + The following option values may be configured -: | Value | Description | @@ -270,12 +287,12 @@ The DHS-WIN-BLW-DHS supports 2 association groups. ### Group 1: Click, press and hold of up/down buttons - +Click, press and hold of up/down buttons This group supports 10 nodes. -### Group 2: Send reports on blind state change - +### Group 2: Send Reports on blind state change +Send Reports on blind state change This group supports 10 nodes. ## Technical Information @@ -286,26 +303,27 @@ This group supports 10 nodes. | Command Class | Comment | |---------------|---------| -| COMMAND_CLASS_BASIC_V0| | -| COMMAND_CLASS_SWITCH_BINARY_V0| Linked to BASIC| -| COMMAND_CLASS_SWITCH_MULTILEVEL_V0| | -| COMMAND_CLASS_SWITCH_ALL_V0| | -| COMMAND_CLASS_SCENE_ACTIVATION_V0| | -| COMMAND_CLASS_SCENE_ACTUATOR_CONF_V0| | -| COMMAND_CLASS_CONFIGURATION_V0| | -| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V0| | -| COMMAND_CLASS_PROTECTION_V0| | -| COMMAND_CLASS_NODE_NAMING_V0| | -| COMMAND_CLASS_ASSOCIATION_V0| | -| COMMAND_CLASS_VERSION_V0| | -| COMMAND_CLASS_INDICATOR_V0| | -| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V0| | +| COMMAND_CLASS_NO_OPERATION_V1| | +| COMMAND_CLASS_BASIC_V1| | +| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC| +| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| | +| COMMAND_CLASS_SWITCH_ALL_V1| | +| COMMAND_CLASS_SCENE_ACTIVATION_V1| | +| COMMAND_CLASS_SCENE_ACTUATOR_CONF_V1| | +| COMMAND_CLASS_CONFIGURATION_V1| | +| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| | +| COMMAND_CLASS_PROTECTION_V1| | +| COMMAND_CLASS_NODE_NAMING_V1| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_VERSION_V1| | +| COMMAND_CLASS_INDICATOR_V1| | +| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V2| | ### Documentation Links -* [User Guide](https://www.cd-jackson.com/zwave_device_uploads/850/DHS-Shutter-ACController-Manual.pdf) +* [User Guide](https://www.cd-jackson.com/zwave_device_uploads/859/DHS-Shutter-ACController-Manual.pdf) --- Did you spot an error in the above definition or want to improve the content? -You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/850). +You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/859). diff --git a/_addons_bindings/zwave/doc/wintop/itemp_0_0.md b/_addons_bindings/zwave/doc/wintop/itemp_0_0.md index cfa87f8972..feba6db531 100644 --- a/_addons_bindings/zwave/doc/wintop/itemp_0_0.md +++ b/_addons_bindings/zwave/doc/wintop/itemp_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Sensor*, defining Device used to measure somet The ITEMP supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ITEMP does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ITEMP does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/216) to improve the documentation. +### Wakeup Information +The ITEMP does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ITEMP -: diff --git a/_addons_bindings/zwave/doc/wintop/multisensor_0_0.md b/_addons_bindings/zwave/doc/wintop/multisensor_0_0.md index cfe4806cce..321e327802 100644 --- a/_addons_bindings/zwave/doc/wintop/multisensor_0_0.md +++ b/_addons_bindings/zwave/doc/wintop/multisensor_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *Multisensor*, manufactured by *Wintop* with th The Multisensor supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The Multisensor does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Multisensor does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/326) to improve the documentation. +### Wakeup Information +The Multisensor does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the Multisensor -: diff --git a/_addons_bindings/zwave/doc/wintop/wtrfid_0_0.md b/_addons_bindings/zwave/doc/wintop/wtrfid_0_0.md index dfba2ba28c..ffa25aa2f6 100644 --- a/_addons_bindings/zwave/doc/wintop/wtrfid_0_0.md +++ b/_addons_bindings/zwave/doc/wintop/wtrfid_0_0.md @@ -13,12 +13,15 @@ This describes the Z-Wave device *WTRFID*, manufactured by *Wintop* with the thi The WTRFID supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The WTRFID does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The WTRFID does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/217) to improve the documentation. +### Wakeup Information +The WTRFID does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the WTRFID -: diff --git a/_addons_bindings/zwave/doc/zipato/hmhs1ca_0_0.md b/_addons_bindings/zwave/doc/zipato/hmhs1ca_0_0.md index 81b49a9f8b..8615573c37 100644 --- a/_addons_bindings/zwave/doc/zipato/hmhs1ca_0_0.md +++ b/_addons_bindings/zwave/doc/zipato/hmhs1ca_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *HM-HS1CA*, manufactured by *[Zipato](http://ww The HM-HS1CA supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HM-HS1CA does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HM-HS1CA does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/741) to improve the documentation. +### Wakeup Information +The HM-HS1CA does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the HM-HS1CA -: diff --git a/_addons_bindings/zwave/doc/zipato/hmhs1wlz_0_0.md b/_addons_bindings/zwave/doc/zipato/hmhs1wlz_0_0.md index 63f9b5045b..c33a692ae8 100644 --- a/_addons_bindings/zwave/doc/zipato/hmhs1wlz_0_0.md +++ b/_addons_bindings/zwave/doc/zipato/hmhs1wlz_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Sensor*, defining Device used to measure somet The HM-HS1WL-Z supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HM-HS1WL-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HM-HS1WL-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -99,6 +99,10 @@ Long press the networking button, then power on (put into the battery), ID code ### Wakeup Information +The HM-HS1WL-Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + The manual doesn't say, but I've found that tapping the tamper sensor once makes the device blink and that seems to wake it up. ## Channels diff --git a/_addons_bindings/zwave/doc/zipato/hs1sa_0_0.md b/_addons_bindings/zwave/doc/zipato/hs1sa_0_0.md index 8f01ce40d7..a3282f2aae 100644 --- a/_addons_bindings/zwave/doc/zipato/hs1sa_0_0.md +++ b/_addons_bindings/zwave/doc/zipato/hs1sa_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Smoke Detector*, defining Smoke detectors. The HS1SA supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The HS1SA does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The HS1SA does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/804) to improve the documentation. +### Wakeup Information +The HS1SA does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the HS1SA -: diff --git a/_addons_bindings/zwave/doc/zipato/nenaspd01z_0_0.md b/_addons_bindings/zwave/doc/zipato/nenaspd01z_0_0.md index 813495319c..6bd6824b60 100644 --- a/_addons_bindings/zwave/doc/zipato/nenaspd01z_0_0.md +++ b/_addons_bindings/zwave/doc/zipato/nenaspd01z_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *NE-NAS-PD01Z*, manufactured by *[Zipato](http: The NE-NAS-PD01Z supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The NE-NAS-PD01Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The NE-NAS-PD01Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/735) to improve the documentation. +### Wakeup Information +The NE-NAS-PD01Z does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the NE-NAS-PD01Z -: diff --git a/_addons_bindings/zwave/doc/zipato/zd2102plus_0_0.md b/_addons_bindings/zwave/doc/zipato/zd2102plus_0_0.md index 9403c4df3a..c15ece40b4 100644 --- a/_addons_bindings/zwave/doc/zipato/zd2102plus_0_0.md +++ b/_addons_bindings/zwave/doc/zipato/zd2102plus_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Door*, defining Door sensors. The ZD2102-5 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZD2102-5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZD2102-5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/713) to improve the documentation. +### Wakeup Information +The ZD2102-5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZD2102-5 -: diff --git a/_addons_bindings/zwave/doc/zipato/zp3102_0_0.md b/_addons_bindings/zwave/doc/zipato/zp3102_0_0.md index e75a4db30d..5223debd0d 100644 --- a/_addons_bindings/zwave/doc/zipato/zp3102_0_0.md +++ b/_addons_bindings/zwave/doc/zipato/zp3102_0_0.md @@ -10,7 +10,7 @@ This describes the Z-Wave device *ZP3102*, manufactured by *[Zipato](http://www. The ZP3102 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZP3102 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZP3102 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -26,6 +26,10 @@ Put your Z-Wave Controller into “exclusion” mode, and follow the instruction ### Wakeup Information +The ZP3102 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + Remove the rear cover to wake up the device, or set the wake up interval time from 10 minutes to 1 week. The battery will be drained quickly if you fail to replace the cover after using that method to wake up the device. ## Channels diff --git a/_addons_bindings/zwave/doc/zooz/zen23_0_0.md b/_addons_bindings/zwave/doc/zooz/zen23_0_0.md index 7c2c12d789..4f2c65769f 100644 --- a/_addons_bindings/zwave/doc/zooz/zen23_0_0.md +++ b/_addons_bindings/zwave/doc/zooz/zen23_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *ZEN23*, manufactured by *[Zooz](http://www.get The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. -The ZEN23 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZEN23 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/649) to improve the documentation. +### Wakeup Information +The ZEN23 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZEN23 -: diff --git a/_addons_bindings/zwave/doc/zooz/zse08_0_0.md b/_addons_bindings/zwave/doc/zooz/zse08_0_0.md index a381a85c88..bad39542bb 100644 --- a/_addons_bindings/zwave/doc/zooz/zse08_0_0.md +++ b/_addons_bindings/zwave/doc/zooz/zse08_0_0.md @@ -15,7 +15,7 @@ The device is in the category of *Door*, defining Door sensors. The ZSE08 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZSE08 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZSE08 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -92,6 +92,10 @@ If the first attempt is unsuccessful, please repeat the process following all st ### Wakeup Information +The ZSE08 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + If you change settings and parameters for the sensor, you may need to wake it up manually for the changes to be recorded. Press and release the Z-Wave button ONCE to wake the device up. The LED indicator will flash ONCE. The sensor’s wake-up interval is set to 12 hours by default to save battery life. Though not recommended, you can change the wake-up interval using your controller’s advanced settings if available. Minimum value: 300s (5 minutes), maximum value: 16,777,200s (around 194 days). Accepted values need to match minute intervals, so 300, 360, 420, etc. ## Channels diff --git a/_addons_bindings/zwave/doc/zooz/zse09_0_0.md b/_addons_bindings/zwave/doc/zooz/zse09_0_0.md index af8e57e9e9..d927a3bc65 100644 --- a/_addons_bindings/zwave/doc/zooz/zse09_0_0.md +++ b/_addons_bindings/zwave/doc/zooz/zse09_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Sensor*, defining Device used to measure somet The ZSE09 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZSE09 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZSE09 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/584) to improve the documentation. +### Wakeup Information +The ZSE09 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZSE09 -: diff --git a/_addons_bindings/zwave/doc/zooz/zse30_0_0.md b/_addons_bindings/zwave/doc/zooz/zse30_0_0.md index ca0c3a2f53..a994686cd8 100644 --- a/_addons_bindings/zwave/doc/zooz/zse30_0_0.md +++ b/_addons_bindings/zwave/doc/zooz/zse30_0_0.md @@ -13,7 +13,7 @@ This describes the Z-Wave device *ZSE30*, manufactured by *[Zooz](http://www.get The ZSE30 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZSE30 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZSE30 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview @@ -62,6 +62,10 @@ If the first attempt is unsuccessful, please repeat the process following all st ### Wakeup Information +The ZSE30 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + If you change settings and parameters for the sensor, you may need to wake it up manually for the changes to be recorded. Press and release the Z-Wave button THREE TIMES to wake the device up. The LED indicator will flash ONCE. The sensor’s wake-up interval is set to 12 hours by default to save battery life. Though not recommended, you can change the wake-up interval using your controller’s advanced settings if available. Minimum value: 300s (5 minutes), maximum value: 16,777,200s (around 194 days). Accepted values need to match minute intervals, so 300, 360, 420, etc ## Channels diff --git a/_addons_bindings/zwave/doc/zooz/zse40_0_0.md b/_addons_bindings/zwave/doc/zooz/zse40_0_0.md index 89b79bab5e..f8d078b10a 100644 --- a/_addons_bindings/zwave/doc/zooz/zse40_0_0.md +++ b/_addons_bindings/zwave/doc/zooz/zse40_0_0.md @@ -15,11 +15,53 @@ The device is in the category of *Sensor*, defining Device used to measure somet The ZSE40 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZSE40 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZSE40 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/491) to improve the documentation. +- 4 smart sensors in 1 compact device +- 7 levels of motion sensitivity to choose from +- 3 modes for motion / temp led indicator notifications +- Built-in tamper protection +- Low battery alerts +- Z-Wave Plus with improved 500 chip for faster and safer wireless communication +- Security enabled Z-Wave device with AES signal encryption + +**Factory Reset** + +If your primary controller is missing or inoperable, you may need to reset the device to factory settings. To complete the reset process manually, remove the back cover to trigger tamper switch. Press and release the Z-Wave button 10 TIMES quickly (within 10 seconds). NOTE: All previously recorded activity and custom settings will be erased from the device’s memory. + +### Inclusion Information + +1. Install the batteries and bring the 4-in-1 sensor as close to your Z-Wave gateway controller as possible +2. Put your Z-Wave controller in inclusion mode +3. Press and release the Z-Wave button TWICE quickly. The sensor will enter secure inclusion mode. +4. A new 4-in-1 sensor should appear on your controller’s device list + +Q: I have not been able to add the device to my network after several attempts, what do I do now? + +A: If you are unable to include the Z-Wave sensor to your controller, please try one of the following: + +- Bring the 4-in-1 sensor closer to your Z-Wave controller +- Press and release the Z-Wave button quickly several times once you put the controller in the inclusion mode to ensure the command has gone through +- Put your controller in the EXCLUSION mode and press and release the Z-Wave button, then try adding it to your network again + +### Exclusion Information + +1. Bring the 4-in-1 sensor as close to your Z-Wave gateway controller as possible +2. Put your Z-Wave controller in exclusion mode +3. Press and release the Z-Wave button TWICE quickly +4. The device should disappear from your controller’s device list. + +The led indicator will flash 3 times when you take the batteries out and put them back in to indicate the device has been successfully excluded. Please repeat the process following all steps carefully if the led indicator blinks only once when you re-insert the batteries + +### Wakeup Information + +The ZSE40 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. + +Use the Wake Up command to set wake-up interval for the sensor (from 10 minutes to 1 week) to report back to the controller. You can also press and release the Z-Wave button once to wake the device up manually. ## Channels @@ -27,7 +69,6 @@ The following table summarises the channels available for the ZSE40 -: | Channel | Channel Id | Category | Item Type | |---------|------------|----------|-----------| -| Motion | sensor_binary | Door | Switch | | Binary Sensor | sensor_binary | Door | Switch | | Sensor (relative humidity) | sensor_relhumidity | Humidity | Number | | Sensor (luminance) | sensor_luminance | Temperature | Number | @@ -36,19 +77,6 @@ The following table summarises the channels available for the ZSE40 -: | Alarm (tamper) | alarm_tamper | | Switch | | Battery Level | battery-level | Battery | Number | -### Motion - -Indicates if a sensor has triggered. - -The ```sensor_binary``` channel supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device. - -The following state translation is provided for this channel to the ```Switch``` item type -: - -| Value | Label | -|-------|-----------| -| ON | Triggered | -| OFF | Untriggered | - ### Binary Sensor Indicates if a sensor has triggered. diff --git a/_addons_bindings/zwave/doc/zwaveme/fgr316_0_0.md b/_addons_bindings/zwave/doc/zwaveme/fgr316_0_0.md new file mode 100644 index 0000000000..93327b4bcf --- /dev/null +++ b/_addons_bindings/zwave/doc/zwaveme/fgr316_0_0.md @@ -0,0 +1,294 @@ +--- +layout: documentation +title: Haseman FGR-316-DIN - ZWave +--- + +{% include base.html %} + +# Haseman FGR-316-DIN DIN Rail 6x2kW Universal Switch / 4xInputs +This describes the Z-Wave device *Haseman FGR-316-DIN*, manufactured by *Z-Wave.Me* with the thing type UID of ```zwaveme_fgr316_00_000```. + +The device is in the category of *Power Outlet*, defining Small devices to be plugged into a power socket in a wall which stick there. + +![Haseman FGR-316-DIN product image](https://www.cd-jackson.com/zwave_device_uploads/734/734_default.jpg) + + +The Haseman FGR-316-DIN supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data from other devices. + +## Overview + +- 6CH relay switch (max. 16A) +- Digital temperature sensor +- Digital input +- 2x analogue inputs 0-10V and 4-20mA (for general use) + +### Inclusion Information + +Push 3 times + +### Exclusion Information + +Push 3 times + +## Channels + +The following table summarises the channels available for the Haseman FGR-316-DIN -: + +| Channel | Channel Id | Category | Item Type | +|---------|------------|----------|-----------| +| Switch | switch_binary | Switch | Switch | +| Binary Sensor | sensor_binary | Door | Switch | +| Sensor (temperature) | sensor_temperature | Temperature | Number | +| Sensor (general) | sensor_general | | Number | +| Alarm (access) | alarm_access | Door | Switch | +| Battery Level | battery-level | Battery | Number | +| Switch 1 | switch_binary1 | Switch | Switch | +| Switch 2 | switch_binary2 | Switch | Switch | +| Switch 3 | switch_binary3 | Switch | Switch | +| Switch 4 | switch_binary4 | Switch | Switch | +| Switch 5 | switch_binary5 | Switch | Switch | +| Switch 6 | switch_binary6 | Switch | Switch | +| Sensor (general) 7 | sensor_general7 | | Number | +| Sensor (general) 8 | sensor_general8 | | Number | +| Sensor (temperature) 9 | sensor_temperature9 | Temperature | Number | +| Binary Sensor 10 | sensor_binary10 | Door | Switch | +| Alarm (access) 10 | alarm_access10 | Door | Switch | + +### Switch + +Switch the power on and off. + +The ```switch_binary``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### Binary Sensor + +Indicates if a sensor has triggered. + +The ```sensor_binary``` channel supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device. + +The following state translation is provided for this channel to the ```Switch``` item type -: + +| Value | Label | +|-------|-----------| +| ON | Triggered | +| OFF | Untriggered | + +### Sensor (temperature) + +Indicates the current temperature. + +The ```sensor_temperature``` channel supports the ```Number``` item and is in the ```Temperature``` category. This is a read only channel so will only be updated following state changes from the device. + +### Sensor (general) + + + +The ```sensor_general``` channel supports the ```Number``` item. This is a read only channel so will only be updated following state changes from the device. + +### Alarm (access) + +Indicates if the access control alarm is triggered. + +The ```alarm_access``` channel supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device. + +The following state translation is provided for this channel to the ```Switch``` item type -: + +| Value | Label | +|-------|-----------| +| OFF | Ok | +| ON | Alarm | + +### Battery Level + +Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading. + +The ```battery-level``` channel supports the ```Number``` item and is in the ```Battery``` category. + +### Switch 1 + +Switch the power on and off. + +The ```switch_binary1``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### Switch 2 + +Switch the power on and off. + +The ```switch_binary2``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### Switch 3 + +Switch the power on and off. + +The ```switch_binary3``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### Switch 4 + +Switch the power on and off. + +The ```switch_binary4``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### Switch 5 + +Switch the power on and off. + +The ```switch_binary5``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### Switch 6 + +Switch the power on and off. + +The ```switch_binary6``` channel supports the ```Switch``` item and is in the ```Switch``` category. + +### Sensor (general) 7 + + + +The ```sensor_general7``` channel supports the ```Number``` item. This is a read only channel so will only be updated following state changes from the device. + +### Sensor (general) 8 + + + +The ```sensor_general8``` channel supports the ```Number``` item. This is a read only channel so will only be updated following state changes from the device. + +### Sensor (temperature) 9 + +Indicates the current temperature. + +The ```sensor_temperature9``` channel supports the ```Number``` item and is in the ```Temperature``` category. This is a read only channel so will only be updated following state changes from the device. + +### Binary Sensor 10 + +Indicates if a sensor has triggered. + +The ```sensor_binary10``` channel supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device. + +The following state translation is provided for this channel to the ```Switch``` item type -: + +| Value | Label | +|-------|-----------| +| ON | Triggered | +| OFF | Untriggered | + +### Alarm (access) 10 + +Indicates if the access control alarm is triggered. + +The ```alarm_access10``` channel supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device. + +The following state translation is provided for this channel to the ```Switch``` item type -: + +| Value | Label | +|-------|-----------| +| OFF | Ok | +| ON | Alarm | + + + +## Device Configuration + +The device has no configuration parameters configured. + +## Association Groups + +Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic. + +The device does not support associations. +## Technical Information + +### Endpoints + +#### Endpoint 0 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_NO_OPERATION_V1| | +| COMMAND_CLASS_BASIC_V1| | +| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC| +| COMMAND_CLASS_SENSOR_BINARY_V2| | +| COMMAND_CLASS_SENSOR_MULTILEVEL_V7| | +| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | +| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| | +| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | +| COMMAND_CLASS_MULTI_CHANNEL_V2| | +| COMMAND_CLASS_CONFIGURATION_V1| | +| COMMAND_CLASS_ALARM_V5| | +| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| | +| COMMAND_CLASS_POWERLEVEL_V1| | +| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| | +| COMMAND_CLASS_BATTERY_V1| | +| COMMAND_CLASS_WAKE_UP_V2| | +| COMMAND_CLASS_ASSOCIATION_V2| | +| COMMAND_CLASS_VERSION_V2| | +| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| | +#### Endpoint 1 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC| +#### Endpoint 2 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC| +#### Endpoint 3 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC| +#### Endpoint 4 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC| +#### Endpoint 5 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC| +#### Endpoint 6 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC| +#### Endpoint 7 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_SENSOR_MULTILEVEL_V7| Linked to BASIC| +#### Endpoint 8 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_SENSOR_MULTILEVEL_V7| Linked to BASIC| +#### Endpoint 9 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_SENSOR_MULTILEVEL_V7| Linked to BASIC| +#### Endpoint 10 + +| Command Class | Comment | +|---------------|---------| +| COMMAND_CLASS_BASIC_V0| | +| COMMAND_CLASS_SENSOR_BINARY_V2| | +| COMMAND_CLASS_ALARM_V5| | + +### Documentation Links + +* [Haseman Z-Wave DIN Rail 6 x 2kW Universal Switch module specifications](https://www.cd-jackson.com/zwave_device_uploads/734/Haseman-Z-Wave-DIN-Rail-6x2kW-Universal-Switch-module-DIN-6CH-RELAY-DATA.pdf) + +--- + +Did you spot an error in the above definition or want to improve the content? +You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/734). diff --git a/_addons_bindings/zwave/doc/zwaveme/kfob_0_0.md b/_addons_bindings/zwave/doc/zwaveme/kfob_0_0.md index 4be9185d74..dd74d53368 100644 --- a/_addons_bindings/zwave/doc/zwaveme/kfob_0_0.md +++ b/_addons_bindings/zwave/doc/zwaveme/kfob_0_0.md @@ -11,12 +11,15 @@ This describes the Z-Wave device *KFOB*, manufactured by *Z-Wave.Me* with the th ![KFOB product image](https://www.cd-jackson.com/zwave_device_uploads/146/146_default.png) -The KFOB does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The KFOB does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/146) to improve the documentation. +### Wakeup Information +The KFOB does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the KFOB -: diff --git a/_addons_bindings/zwave/doc/zwaveme/wallcs_0_0.md b/_addons_bindings/zwave/doc/zwaveme/wallcs_0_0.md index 9a5e0bcf4c..aec251b464 100644 --- a/_addons_bindings/zwave/doc/zwaveme/wallcs_0_0.md +++ b/_addons_bindings/zwave/doc/zwaveme/wallcs_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Wall Switch*, defining Any device attached to The WALLC-S supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The WALLC-S does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The WALLC-S does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/145) to improve the documentation. +### Wakeup Information +The WALLC-S does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the WALLC-S -: diff --git a/_addons_bindings/zwave/doc/zwaveme/wcd2_0_0.md b/_addons_bindings/zwave/doc/zwaveme/wcd2_0_0.md index e71646f511..63bdcd14ac 100644 --- a/_addons_bindings/zwave/doc/zwaveme/wcd2_0_0.md +++ b/_addons_bindings/zwave/doc/zwaveme/wcd2_0_0.md @@ -12,12 +12,15 @@ The device is in the category of *Wall Switch*, defining Any device attached to The WCD2 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The WCD2 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The WCD2 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/147) to improve the documentation. +### Wakeup Information +The WCD2 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the WCD2 -: diff --git a/_addons_bindings/zwave/doc/zwaveme/zme06443_0_0.md b/_addons_bindings/zwave/doc/zwaveme/zme06443_0_0.md index f8250ed822..00afadc3bd 100644 --- a/_addons_bindings/zwave/doc/zwaveme/zme06443_0_0.md +++ b/_addons_bindings/zwave/doc/zwaveme/zme06443_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *ZME_06443*, manufactured by *Z-Wave.Me* with t The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch. -The ZME_06443 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZME_06443 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/148) to improve the documentation. +### Wakeup Information +The ZME_06443 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZME_06443 -: diff --git a/_addons_bindings/zwave/doc/zwaveme/zmekfobs_0_0.md b/_addons_bindings/zwave/doc/zwaveme/zmekfobs_0_0.md index ac07d4d31a..0b65f3f23b 100644 --- a/_addons_bindings/zwave/doc/zwaveme/zmekfobs_0_0.md +++ b/_addons_bindings/zwave/doc/zwaveme/zmekfobs_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Remote Control*, defining Any portable or hand The ZME_KFOB-S supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZME_KFOB-S does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZME_KFOB-S does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/548) to improve the documentation. +### Wakeup Information +The ZME_KFOB-S does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZME_KFOB-S -: diff --git a/_addons_bindings/zwave/doc/zwaveme/zmerc2_0_0.md b/_addons_bindings/zwave/doc/zwaveme/zmerc2_0_0.md index 7959c90195..31ca87e00f 100644 --- a/_addons_bindings/zwave/doc/zwaveme/zmerc2_0_0.md +++ b/_addons_bindings/zwave/doc/zwaveme/zmerc2_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *ZME_RC2*, manufactured by *Z-Wave.Me* with the The ZME_RC2 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ZME_RC2 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ZME_RC2 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/149) to improve the documentation. +### Wakeup Information +The ZME_RC2 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ZME_RC2 -: diff --git a/_addons_bindings/zwave/doc/zwaveme/zweather_0_0.md b/_addons_bindings/zwave/doc/zwaveme/zweather_0_0.md index 909a38c62a..9309756c67 100644 --- a/_addons_bindings/zwave/doc/zwaveme/zweather_0_0.md +++ b/_addons_bindings/zwave/doc/zwaveme/zweather_0_0.md @@ -10,12 +10,15 @@ This describes the Z-Wave device *Z-Weather*, manufactured by *Z-Wave.Me* with t The Z-Weather supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The Z-Weather does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The Z-Weather does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/258) to improve the documentation. +### Wakeup Information +The Z-Weather does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the Z-Weather -: diff --git a/_addons_bindings/zwave/doc/zwaveproducts/ws100_0_0.md b/_addons_bindings/zwave/doc/zwaveproducts/ws100_0_0.md index cf86cad7a8..0c23854c21 100644 --- a/_addons_bindings/zwave/doc/zwaveproducts/ws100_0_0.md +++ b/_addons_bindings/zwave/doc/zwaveproducts/ws100_0_0.md @@ -8,12 +8,15 @@ title: WS-100 - ZWave # WS-100 Switch This describes the Z-Wave device *WS-100*, manufactured by *Z Wave Products Inc.* with the thing type UID of ```zwaveproducts_ws100_00_000```. -The WS-100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The WS-100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/592) to improve the documentation. +### Wakeup Information +The WS-100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the WS-100 -: diff --git a/_addons_bindings/zwave/doc/zyxel/st812_0_0.md b/_addons_bindings/zwave/doc/zyxel/st812_0_0.md index 9bb14c109a..02c001c659 100644 --- a/_addons_bindings/zwave/doc/zyxel/st812_0_0.md +++ b/_addons_bindings/zwave/doc/zyxel/st812_0_0.md @@ -15,12 +15,15 @@ The device is in the category of *Sensor*, defining Device used to measure somet The ST812 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices. -The ST812 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. +The ST812 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information. ## Overview -No device information is provided in the database. Consider [updating the database](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/327) to improve the documentation. +### Wakeup Information +The ST812 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour. + +The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device. ## Channels The following table summarises the channels available for the ST812 -: diff --git a/_addons_persistences/rrd4j/readme.md b/_addons_persistences/rrd4j/readme.md index 976045f0eb..1625585d4b 100644 --- a/_addons_persistences/rrd4j/readme.md +++ b/_addons_persistences/rrd4j/readme.md @@ -21,7 +21,8 @@ In contrast to a "normal" database such as db4o, a round-robin database does not This service cannot be directly queried, because of the data compression. You could not provide precise answers for all questions. -NOTE: rrd4j is for storing numerical data only. Attempting to use rrd4j to store complex datatypes (eg. for restore-on-startup) will not work. +NOTE: rrd4j is for storing numerical data only. +Attempting to use rrd4j to store complex datatypes (e.g. for restore-on-startup) will not work. @@ -34,8 +35,6 @@ NOTE: rrd4j is for storing numerical data only. Attempting to use rrd4j to store - - ## Configuration This service can be configured in the file `services/rrd4j.cfg`. @@ -48,12 +47,12 @@ This service can be configured in the file `services/rrd4j.cfg`. where: -* Sections in `[square brackets]` are optional. -* `` is a name you choose for the datasource. -* See [Datasource types](#datasource-types) for an explanation of ``. -* See [Heartbeat, MIN, MAX](#heartbeat-min-max) for an explanation of ``, ``, `` and `U`. -* See [Step\(s\)](#steps) for an explanation of ``, ``, ``, ``, and ``. -* `` is explained in +- Sections in `[square brackets]` are optional. +- `` is a name you choose for the datasource. +- See [Datasource types](#datasource-types) for an explanation of ``. +- See [Heartbeat, MIN, MAX](#heartbeat-min-max) for an explanation of ``, ``, `` and `U`. +- See [Step\(s\)](#steps) for an explanation of ``, ``, ``, ``, and ``. +- `` is explained in Round-robin databases (RRDs) have fixed-length so-called "archives" for storing values. One RRD can have (in general) several datasources and each datasource can have several archives. openHAB only supports one datasource per RRD, which is named DATASOURCE_STATE. @@ -61,10 +60,10 @@ Round-robin databases (RRDs) have fixed-length so-called "archives" for storing Depending on the data to be stored, several types for datasources exist: -* **COUNTER** represents a ever-incrementing value (historically this was used for packet counters or traffic counters on network interfaces, a typical home-automation application would be your electricity meter). If you store the values of this counter in a simple database and make a chart of that, you'll most likely see a nearly flat line, because the increments per time are small compared to the absolute value (e.g. your electricity meter reads 60567 kWh, and you add 0.5 kWh per hour, than your chart over the whole day will show 60567 at the start and 60579 at the end of your chart. That is nearly invisible. RRD4J helps you out and will display the difference from one stored value to the other (depending on the selected size). Please note that the persistence extensions will return difference instead of the actual values if you use this type; this especially leads to wrong values if you try to restoreOnStartup! -* **GAUGE** represents the reading of e.g. a temperature sensor. You'll see only small deviation over the day and your values will be within a small range, clearly visible within a chart. -* **ABSOLUTE** is like a counter, but RRD4J assumes that the counter is reset when the value is read. So these are basically the delta values between the reads. -* **DERIVE** is like a counter, but it can also decrease and therefore have a negative delta. +- **COUNTER** represents a ever-incrementing value (historically this was used for packet counters or traffic counters on network interfaces, a typical home-automation application would be your electricity meter). If you store the values of this counter in a simple database and make a chart of that, you'll most likely see a nearly flat line, because the increments per time are small compared to the absolute value (e.g. your electricity meter reads 60567 kWh, and you add 0.5 kWh per hour, than your chart over the whole day will show 60567 at the start and 60579 at the end of your chart. That is nearly invisible. RRD4J helps you out and will display the difference from one stored value to the other (depending on the selected size). Please note that the persistence extensions will return difference instead of the actual values if you use this type; this especially leads to wrong values if you try to restoreOnStartup! +- **GAUGE** represents the reading of e.g. a temperature sensor. You'll see only small deviation over the day and your values will be within a small range, clearly visible within a chart. +- **ABSOLUTE** is like a counter, but RRD4J assumes that the counter is reset when the value is read. So these are basically the delta values between the reads. +- **DERIVE** is like a counter, but it can also decrease and therefore have a negative delta. ### Heartbeat, MIN, MAX @@ -76,21 +75,33 @@ Step (set in `.def=,,[|U],[|U],` with step in Sets the timeintervall(seconds) between consecutive readings. --Steps or Granularity (set in ` .archives=,,,` +- Steps or Granularity (set in `.archives=,,,` -Steps are the number of consecutive readings that are used the create a single entry into the database for this timeintervall. The timeintervall covered is calculated by Step(seconds)*Steps. +Steps are the number of consecutive readings that are used the create a single entry into the database for this timeintervall. +The timeintervall covered is calculated by (step x step) seconds. -Now for the archives: As already said, each datasource can have several archives. Think of an archive as a drawer with a fixed number of boxes in it. Each steps*step seconds (the step is globally defined for the RRD, 60s in our example) the most-left box is emptied, the content of all boxes is moved one box to the left and new content is added to the most right box. The "steps" value is defined per archive it is the third parameter in the archive definition. The number of boxes is defined as the fourth parameter. +Now for the archives: As already said, each datasource can have several archives. +Think of an archive as a drawer with a fixed number of boxes in it. +Each (step x step) seconds (the step is globally defined for the RRD, 60s in our example) the most-left box is emptied, the content of all boxes is moved one box to the left and new content is added to the most right box. +The "steps" value is defined per archive it is the third parameter in the archive definition. +The number of boxes is defined as the fourth parameter. -The purpose to have several archives is raised if a different granuality is needed while displaying data for different timespans. In the above examples data for each second are saved for the last hour (granularity 1), looking at the last four houres a granularity of 10 (i.e. 10 readings are consolidated to one reading) is used and so forth. For the first archive (and maybe the only one) a steps-size of one should be used. This way a sample is taken after each step. In this special case the selection of the consolidationfunction is of no effect (a single reading is equal to the MAX, MIN, AVERAGE and LAST of this reading). +The purpose to have several archives is raised if a different granularity is needed while displaying data for different timespans. +In the above examples data for each second are saved for the last hour (granularity 1), looking at the last four hours a granularity of 10 (i.e. 10 readings are consolidated to one reading) is used and so forth. +For the first archive (and maybe the only one) a steps-size of one should be used. +This way a sample is taken after each step. +In this special case the selection of the consolidation function is of no effect (a single reading is equal to the MAX, MIN, AVERAGE and LAST of this reading). ### Example -So in the above examples, we have 480 boxes, which each represent the value of one minute (Step is set to 60s, Granularity = 1). If more than one value is added to the database within (steps*step) second (and thus more than one value would be stored in one box), the "consolidation function" is used. OpenHAB uses AVERAGE as default for numeric values, so if you add 20 and 21 within one minute, 20.5 would be stored. 480 minutes is 8 hours, so we have a 8h with the granularity of one minute. +So in the above examples, we have 480 boxes, which each represent the value of one minute (Step is set to 60s, Granularity = 1). +If more than one value is added to the database within (step x step) seconds (and thus more than one value would be stored in one box), the "consolidation function" is used. +openHAB uses AVERAGE as default for numeric values, so if you add 20 and 21 within one minute, 20.5 would be stored. +480 minutes is 8 hours, so we have a 8h with the granularity of one minute. The same goes for the next archives, for larger time spans, the stored values are less "exact". However, usually you are not interested in the exact temperature for a selected minute two years ago. -services/rrd4j.cfg +services/rrd4j.cfg: ``` ctr5min.def=COUNTER,900,0,U,300 @@ -98,7 +109,22 @@ ctr5min.archives=AVERAGE,0.5,1,365:AVERAGE,0.5,7,300 ctr5min.items=Item1,Item2 ``` -All item- and event-related configuration is done in the file `persistence/rrd4j.persist`. The strategy `everyMinute` must be used, otherwise no data will be persisted (stored). +All item- and event-related configuration is done in the file `persistence/rrd4j.persist`. +The strategy `everyMinute` (60 seconds) has to be used, otherwise no data will be persisted (stored). + +rrd4j.persist: + +```java +Strategies { + // for rrd charts, we need a cron strategy + everyMinute : "0 * * * * ?" +} + +Items { + // persist items on every change and every minute + * : strategy = everyChange, everyMinute +} +``` ## Troubleshooting diff --git a/_addons_transformations/exec/readme.md b/_addons_transformations/exec/readme.md index dc5d942bc2..5732753d4f 100644 --- a/_addons_transformations/exec/readme.md +++ b/_addons_transformations/exec/readme.md @@ -71,6 +71,21 @@ When the input argument for `%s` is 1234567 it will return the bytes formated in 1.2MiB ``` +### Usage as a Profile + +The functionality of this `TransformationService` can be used in a `Profile` on an `ItemChannelLink` too. +To do so, it can be configured in the `.items` file as follows: + +```java +String { channel=""[profile="transform:EXEC", function="", sourceFormat=""]} +``` + +The shell command to be executed has to be set in the `function` parameter. +The parameter `sourceFormat` is optional and can be used to format the input value **before** the transformation, i.e. `%.3f`. +If omitted the default is `%s`, so the input value will be put into the transformation without any format changes. + +Please note: This profile is a one-way transformation, i.e. only values from a device towards the item are changed, the other direction is left untouched. + # Further Reading * [Manual](http://man7.org/linux/man-pages/man1/date.1.html) and [tutorial](https://linode.com/docs/tools-reference/tools/use-the-date-command-in-linux/) for date. diff --git a/_addons_transformations/javascript/readme.md b/_addons_transformations/javascript/readme.md index 48212ebe3d..b92d7a3fa5 100644 --- a/_addons_transformations/javascript/readme.md +++ b/_addons_transformations/javascript/readme.md @@ -32,3 +32,18 @@ transform/getValue.js: return array[array.length - 1].length; })(input) ``` + +## Usage as a Profile + +The functionality of this `TransformationService` can be used in a `Profile` on an `ItemChannelLink` too. +To do so, it can be configured in the `.items` file as follows: + +```java +String { channel=""[profile="transform:JS", function="", sourceFormat=""]} +``` + +The Javascript file (from within the `transform` folder) to be used has to be set in the `function` parameter. +The parameter `sourceFormat` is optional and can be used to format the input value **before** the transformation, i.e. `%.3f`. +If omitted the default is `%s`, so the input value will be put into the transformation without any format changes. + +Please note: This profile is a one-way transformation, i.e. only values from a device towards the item are changed, the other direction is left untouched. diff --git a/_addons_transformations/jsonpath/readme.md b/_addons_transformations/jsonpath/readme.md index 03a0623b56..d335380b3d 100644 --- a/_addons_transformations/jsonpath/readme.md +++ b/_addons_transformations/jsonpath/readme.md @@ -71,6 +71,21 @@ Means it does not return a valid JSON `[ 23.2 ]` but `23.2`, `[ "Outside" ]` but This makes it possible to use it in labels or output channel of things and get Numbers or Strings instead of JSON arrays. A query which returns multiple elements as list is not supported. +## Usage as a Profile + +The functionality of this `TransformationService` can be used in a `Profile` on an `ItemChannelLink` too. +To do so, it can be configured in the `.items` file as follows: + +```java +String { channel=""[profile="transform:JSONPATH", function="", sourceFormat=""]} +``` + +The JSONPath expression to be used has to be set in the `function` parameter. +The parameter `sourceFormat` is optional and can be used to format the input value **before** the transformation, i.e. `%.3f`. +If omitted the default is `%s`, so the input value will be put into the transformation without any format changes. + +Please note: This profile is a one-way transformation, i.e. only values from a device towards the item are changed, the other direction is left untouched. + ## Further Reading * An extended [introduction](https://www.w3schools.com/js/js_json_intro.asp) can be found at W3School. diff --git a/_addons_transformations/map/readme.md b/_addons_transformations/map/readme.md index de1b9f9606..de481b401e 100644 --- a/_addons_transformations/map/readme.md +++ b/_addons_transformations/map/readme.md @@ -37,3 +37,18 @@ OFF=0 | `1` | `ON` | | `OFF` | `0` | | `key` | `value` | + +## Usage as a Profile + +The functionality of this `TransformationService` can be used in a `Profile` on an `ItemChannelLink` too. +To do so, it can be configured in the `.items` file as follows: + +```java +String { channel=""[profile="transform:MAP", function="", sourceFormat=""]} +``` + +The mapping filename (within the `transform` folder) has to be set in the `function` parameter. +The parameter `sourceFormat` is optional and can be used to format the input value **before** the transformation, i.e. `%.3f`. +If omitted the default is `%s`, so the input value will be put into the transformation without any format changes. + +Please note: This profile is a one-way transformation, i.e. only values from a device towards the item are changed, the other direction is left untouched. \ No newline at end of file diff --git a/_addons_transformations/regex/readme.md b/_addons_transformations/regex/readme.md index 2344bb4c54..ca5df27bc0 100644 --- a/_addons_transformations/regex/readme.md +++ b/_addons_transformations/regex/readme.md @@ -97,6 +97,21 @@ To use a dot as litteral in the regex it has to be escape `\.`, but in a string The first backslash escapes the second backslash in the string so it can be used in the regex. Using a backslash in a Regex as literal `\\` will have this form `"\\\\"`. +## Usage as a Profile + +The functionality of this `TransformationService` can be used in a `Profile` on an `ItemChannelLink` too. +To do so, it can be configured in the `.items` file as follows: + +```java +String { channel=""[profile="transform:REGEX", function="", sourceFormat=""]} +``` + +The regular expression to be executed has to be set in the `function` parameter. +The parameter `sourceFormat` is optional and can be used to format the input value **before** the transformation, i.e. `%.3f`. +If omitted the default is `%s`, so the input value will be put into the transformation without any format changes. + +Please note: This profile is a one-way transformation, i.e. only values from a device towards the item are changed, the other direction is left untouched. + ## Further Reading * A full [introduction](https://www.w3schools.com/jsref/jsref_obj_regexp.asp) for regular expression is available at W3School. diff --git a/_addons_transformations/scale/readme.md b/_addons_transformations/scale/readme.md index efc3e8551d..ef34b5f745 100644 --- a/_addons_transformations/scale/readme.md +++ b/_addons_transformations/scale/readme.md @@ -12,55 +12,70 @@ install: auto {% include base.html %} -# Scale Transformation Service - -The Scale Transformation Service is a an easy to handle tool that can help you with the discretization of number inputs. -It transforms a given input by matching it to specified ranges. -The input string must be in numerical format. - -The file is expected to exist in the `transform` configuration directory and its ending has to be `.scale`. -It should follow the format given in the table below. - -Range expressions always contain two parts. -The range to scale on, which is located left from the equality sign and the corresponding output string on the right of it. -A range consists of two bounds. Both are optional, the range is then open. Both bounds can be inclusive or exclusive. - -| Scale Expression | Returns XYZ when the given value is | -|------------------|------------------------------------------------------------| -| `[12..23]=XYZ` | `between (or equal to) 12 and 23` | -| `]12..23[=XYZ` | `between 12 and 23 (12 and 23 are excluded in this case.)` | -| `[..23]=XYZ` | `lower than or equal to 23` | -| `]12..]=XYZ` | `greater than 12` | - -These expressions are evaluated from top to bottom. -The first range that includes the value is selected. - -## Example - -The following example shows how to break down numeric UV values into fixed UV index categories. -We have an example UV sensor that sends numeric values from `0` to `100`, which we then want to scale into the [UV Index](https://en.wikipedia.org/wiki/Ultraviolet_index) range. - -Example item: - -```java -Number Uv_Sensor_Level "UV Level [SCALE(uvindex.scale):%s]" -``` - -Referenced scale file `uvindex.scale` in the `transform` folder: - -```python -[..3]=1 -]3..6]=2 -]6..8]=3 -]8..10]=4 -[10..100]=5 -``` - -Each value the item receives, will be categorized to one of the five given ranges. -Values **lower than or equal to 3** are matched with `[..3]=1`. -Greater values are catched in ranges with 2 values as criteria. -The only condition here is that the received value has to be lower or equal than `100` in our example, since we haven't defined other cases yet. -If **none** of the configured conditions matches the given value, the response will be empty. - -Please note that all ranges for values above **3** are opened with a `]`. -So the border values (3, 6, 8 and 10) are always transformed to the lower range, since the `]` excludes the given critera. +# Scale Transformation Service + +The Scale Transformation Service is a an easy to handle tool that can help you with the discretization of number inputs. +It transforms a given input by matching it to specified ranges. +The input string must be in numerical format. + +The file is expected to exist in the `transform` configuration directory and its ending has to be `.scale`. +It should follow the format given in the table below. + +Range expressions always contain two parts. +The range to scale on, which is located left from the equality sign and the corresponding output string on the right of it. +A range consists of two bounds. Both are optional, the range is then open. Both bounds can be inclusive or exclusive. + +| Scale Expression | Returns XYZ when the given value is | +|------------------|------------------------------------------------------------| +| `[12..23]=XYZ` | `between (or equal to) 12 and 23` | +| `]12..23[=XYZ` | `between 12 and 23 (12 and 23 are excluded in this case.)` | +| `[..23]=XYZ` | `lower than or equal to 23` | +| `]12..]=XYZ` | `greater than 12` | + +These expressions are evaluated from top to bottom. +The first range that includes the value is selected. + +## Example + +The following example shows how to break down numeric UV values into fixed UV index categories. +We have an example UV sensor that sends numeric values from `0` to `100`, which we then want to scale into the [UV Index](https://en.wikipedia.org/wiki/Ultraviolet_index) range. + +Example item: + +```java +Number Uv_Sensor_Level "UV Level [SCALE(uvindex.scale):%s]" +``` + +Referenced scale file `uvindex.scale` in the `transform` folder: + +```python +[..3]=1 +]3..6]=2 +]6..8]=3 +]8..10]=4 +[10..100]=5 +``` + +Each value the item receives, will be categorized to one of the five given ranges. +Values **lower than or equal to 3** are matched with `[..3]=1`. +Greater values are catched in ranges with 2 values as criteria. +The only condition here is that the received value has to be lower or equal than `100` in our example, since we haven't defined other cases yet. +If **none** of the configured conditions matches the given value, the response will be empty. + +Please note that all ranges for values above **3** are opened with a `]`. +So the border values (3, 6, 8 and 10) are always transformed to the lower range, since the `]` excludes the given critera. + +## Usage as a Profile + +The functionality of this `TransformationService` can be used in a `Profile` on an `ItemChannelLink` too. +To do so, it can be configured in the `.items` file as follows: + +```java +String { channel=""[profile="transform:SCALE", function="", sourceFormat=""]} +``` + +The filename (within the `transform` folder) of the scale file has to be set in the `function` parameter. +The parameter `sourceFormat` is optional and can be used to format the input value **before** the transformation, i.e. `%.3f`. +If omitted the default is `%s`, so the input value will be put into the transformation without any format changes. + +Please note: This profile is a one-way transformation, i.e. only values from a device towards the item are changed, the other direction is left untouched. diff --git a/_addons_transformations/xpath/readme.md b/_addons_transformations/xpath/readme.md index 07f17b03d7..1ef18b9d1c 100644 --- a/_addons_transformations/xpath/readme.md +++ b/_addons_transformations/xpath/readme.md @@ -111,6 +111,21 @@ end Now the resulting Number can also be used in the label to [change the color](https://docs.openhab.org/configuration/sitemaps.html#label-and-value-colors) or in a rule as value for comparison. +## Usage as a Profile + +The functionality of this `TransformationService` can be used in a `Profile` on an `ItemChannelLink` too. +To do so, it can be configured in the `.items` file as follows: + +```java +String { channel=""[profile="transform:XPATH", function="", sourceFormat=""]} +``` + +The XPath expression to be executed has to be set in the `function` parameter. +The parameter `sourceFormat` is optional and can be used to format the input value **before** the transformation, i.e. `%.3f`. +If omitted the default is `%s`, so the input value will be put into the transformation without any format changes. + +Please note: This profile is a one-way transformation, i.e. only values from a device towards the item are changed, the other direction is left untouched. + ## Further Reading * An [introduction](https://www.w3schools.com/xml/xpath_intro.asp) to XPath at W3School diff --git a/_addons_transformations/xslt/readme.md b/_addons_transformations/xslt/readme.md index 6d9795671c..af9aec735d 100644 --- a/_addons_transformations/xslt/readme.md +++ b/_addons_transformations/xslt/readme.md @@ -117,6 +117,21 @@ Fri, 18 Dec 2009 9:38 am PST 450 ``` +## Usage as a Profile + +The functionality of this `TransformationService` can be used in a `Profile` on an `ItemChannelLink` too. +To do so, it can be configured in the `.items` file as follows: + +```java +String { channel=""[profile="transform:XSLT", function="", sourceFormat=""]} +``` + +The XSLT file (from within the `transform` folder) to be used has to be set in the `function` parameter. +The parameter `sourceFormat` is optional and can be used to format the input value **before** the transformation, i.e. `%.3f`. +If omitted the default is `%s`, so the input value will be put into the transformation without any format changes. + +Please note: This profile is a one-way transformation, i.e. only values from a device towards the item are changed, the other direction is left untouched. + ## Further Reading * Extended introduction and more [examples](https://en.wikipedia.org/wiki/XSLT#XSLT_examples) at Wikipedia. diff --git a/concepts/units-of-measurement.md b/concepts/units-of-measurement.md index 10c3148dd6..ab31f56723 100644 --- a/concepts/units-of-measurement.md +++ b/concepts/units-of-measurement.md @@ -71,3 +71,117 @@ When creating QuantityType states the framework offers some useful packages and The `org.eclipse.smarthome.core.library.unit` package contains the classes `SIUnits`, `ImperialUnits` and `SmartHomeUnits` which provide units unique to either of the measurement systems and common units used in both systems. The `MetricPrefix` class provides prefixes like MILLI, CENTI, HECTO, etc. which are wrappers to create derived units. The `org.eclipse.smarthome.core.library.dimension` and `javax.measure.quantity` packages provide interfaces which are used to type the generic QuantityType and units. + +## List of Units + +All units which are currently supported by default are listed in the tables below. + + +Imperial: + +| Type | Unit | Symbol | +|-------------|-----------------|--------| +| Pressure | Inch of Mercury | inHg | +| Temperature | Fahrenheit | °F | +| Speed | Miles per Hour | mph | +| Length | Inch | in | +| Length | Foot | ft | +| Length | Yard | yd | +| Length | Chain | ch | +| Length | Furlong | fur | +| Length | Mile | mi | +| Length | League | lea | + +SI: + +| Type | Unit | Symbol | +|------------------------|-------------------------|--------| +| Acceleration | Metre per square Second | m/s2 | +| AmountOfSubstance | Mole | mol | +| Angle | Radian | rad | +| Angle | Degree | ° | +| Angle | Minute Angle | ' | +| Angle | Second Angle | '' | +| Area | Square Metre | m2 | +| ArealDensity | Dobson Unit | DU | +| CatalyticActivity | Katal | kat | +| Dimensionless | Percent | % | +| Dimensionless | Parts per Million | ppm | +| Dimensionless | Decibel | dB | +| ElectricPotential | Volt | V | +| ElectricCapacitance | Farad | F | +| ElectricCharge | Coulomb | C | +| ElectricConductance | Siemens | S | +| ElectricCurrent | Ampere | A | +| ElectricInductance | Henry | H | +| ElectricResistance | Ohm | Ω | +| Energy | Joule | J | +| Energy | Watt Second | Ws | +| Energy | Watt Hour | Wh | +| Energy | KiloWatt Hour | kWh | +| Force | Newton | N | +| Frequency | Hertz | Hz | +| Illuminance | Lux | lx | +| Intensity | Irradiance | W/m² | +| Length | Metre | m | +| Length | Kilometre | km | +| LuminousFlux | Lumen | lm | +| LuminousIntensity | Candela | cd | +| MagneticFlux | Weber | Wb | +| MagneticFluxDensity | Tesla | T | +| Mass | Kilogram | kg | +| Mass | Gram | g | +| Power | Watt | W | +| Pressure | Pascal | Pa | +| Pressure | hectoPascal | hPa | +| Pressure | Millimetre of Mercury | mmHg | +| Pressure | Bar | bar | +| Radioactivity | Becquerel | Bq | +| RadiationDoseAbsorbed | Gray | Gy | +| RadiationDoseEffective | Sievert | Sv | +| SolidAngle | Steradian | sr | +| Speed | Metre per Second | m/s | +| Speed | Kilometre per Hour | km/h | +| Speed | Knot | kn | +| Temperature | Kelvin | K | +| Temperature | Celsius | °C | +| Time | Second | s | +| Time | Minute | min | +| Time | Hour | h | +| Time | Day | d | +| Time | Week | week | +| Time | Year | y | +| Volume | Cubic Metre | m3 | + +Prefixes: + +| Name | Symbol | Value | +|-------|--------|-------| +| Yotta | Y | 10²⁴ | +| Zetta | Z | 10²¹ | +| Exa | E | 10¹⁸ | +| Peta | P | 10¹⁵ | +| Tera | T | 10¹² | +| Giga | G | 10⁹ | +| Mega | M | 10⁶ | +| Kilo | k | 10³ | +| Hecto | h | 10² | +| Deca | da | 10 | +| Deci | d | 10⁻¹ | +| Centi | c | 10⁻² | +| Milli | m | 10⁻³ | +| Micro | µ | 10⁻⁶ | +| Nano | n | 10⁻⁹ | +| Pico | p | 10⁻¹² | +| Femto | f | 10⁻¹⁵ | +| Atto | a | 10⁻¹⁸ | +| Zepto | z | 10⁻²¹ | +| Yocto | y | 10⁻²⁴ | + + +To use the prefixes simply add the prefix to the unit symbol e.g. + +Examples: +-milliAmpere - `mA` +-centiMetre - `cm` +-kiloWatt - `kW`