open-zwave-1.5/ 0000775 0000000 0000000 00000000000 12644742024 0013457 5 ustar 00root root 0000000 0000000 open-zwave-1.5/.gitignore 0000664 0000000 0000000 00000001502 12644742024 0015445 0 ustar 00root root 0000000 0000000 .dep/
.lib/
MinOZW
cpp/src/vers.cpp
libopenzwave.a
libopenzwave.pc
libopenzwave.so*
libopenzwave.so
*.obj
/cpp/build/windows/vs2010/Debug/*.log
/cpp/build/windows/vs2010/Debug/OpenZWave.tlog/*.tlog
/cpp/build/windows/vs2010/Debug/OpenZWave.tlog/*.lastbuildstate
*.idb
*.pdb
*.log
*.tlog
/dotnet/build/vs2010/Debug/app.res
Debug
/dotnet/examples/OZWForm/src/OZWForm.csproj
/dotnet/examples/OZWForm/src/OZWForm.sdf
/dotnet/examples/OZWForm/src/OZWForm.sln
/dotnet/examples/OZWForm/src/OZWForm.v12.suo
*.cache
*.res
*.lib
*.dll
*.metagen
*.exp
*.exe
OZWForm.exe.config
OZWForm.vshost.exe.config
OZWForm.vshost.exe.manifest
*.resources
/dotnet/examples/OZWForm/src/bin/x86/Release/OZW_Log.txt
/dotnet/examples/OZWForm/src/bin/x86/Release
/dotnet/examples/OZWForm/src/obj/x86/Release
.gitignore
/cpp/build/windows/winversion.cpp
.distfiles open-zwave-1.5/ChangeLog 0000664 0000000 0000000 00000055455 12644742024 0015247 0 ustar 00root root 0000000 0000000 Version 1.5
- Rename zwcfg_*.xml to zwcache_*.xml to reflect its not a config file, but a cache. (Justin)
Version 1.4
- Released 10th Jan, 2016
Version 1.3
- Added support for Merten Plug-in Roller Shutter Module (Marco)
- Fixed Issue 383 - Update Remotec ZXT-120 Config file thanks to yy.bendavid & gizmocuz (Alex)
- Fixed Issue 392 - Add Qubino ZMNHJA2 Config file thanks to nicoserveur (Alex)
- Fixed Issue 394 - Add 2GIG CT100 USA version device thanks to mldkfa (Alex)
- Fixed Issue 387 - Add Zipato RFID Config file thanks to jeanfrancois.auger (Alex)
- Fixed Issue 391 - Update zwave.key keyfob config thanks to gizmocuz (Alex)
- Fixed Issue 397 - Update remotec ZXT-120 config thanks to gizmocuz (Alex)
- Fixed Issue 396 - Add Z-Wave.me RaZberry thanks to steph10200 (Alex)
- Fixed Issue 398 - Add Z-Wave.me USB Stick thanks to ugo.viti (Alex)
- Fixed Issue 389 - Add Evolve LRM-AS/LSM-15 Config file thanks to Gwmullin (Alex)
- Fixed Issue 386 - Add Duwi and Z-Wave.Me Config files thanks to pim.vanderhaven (Alex)
- Fixed Issue 401 - Add Toon/Quby devices (Alex)
- Added new manufacturers and new devices (Alex)
- Add Wenzhou TSP01 Config file thanks to Jan (Alex)
- Standardize some of the Logging Messages so its easier to parse (Justin)
- Implemented Issue 325 - Add a GetChangeVerfied method to the Manager and Value classes to
determine if a Value is checked upon refresh from a device (Justin)
- Fixed issue 350 - FreeBSD Makefile updates and a few patches (Justin)
- Fixed issue 395 - Clear the ListItems Vector before populating with new
values (Justin)
- Fixed issue 402 - Clean vers.cpp when we issue a make clean (Justin)
- Fixed issue 405 - Add new ID's for Fibaro FGD211 and FGS221 (Justin)
- Fixed issue 406 - Add Remotec ZFM-80 (Justin)
- Fixed issue 410 - Add Vision ZP3102 (Justin)
- Fixed issue 412 - Updated Zipato RGB Bulb Config (Justin)
- Fixed Issue 343 - Add Exceptions instead of Exit for some fatal errors
Also, add Exceptions if any of the GetValue or SetValue calls in the
Manager class are passed invalid ValueID's (Justin)
- Fixed duplicate Vision devices and added a missing id for ZP3102 (Alex)
- Fixed Issue 417 - Add Z-Wave.Me ZME_UZB1 USB Stick thanks to Ugo (Alex)
- Add new Aeon Repeater device (Alex)
- Fixed a crash in the LogFile Class when the destructor was called
(Justin)
- Fix Issue 426 - Upon restarts of OZW, we restarted the entire discovery
process again (Justin)
- Fix a off by 1 issue with the Security CC that was causing the
Assoication Set Failures on Secured Devices. (Justin)
- Added Aeon Labs Smart Energy Switch V2 that supports the Security CC but
doesn't support the Basic CC - Related to issue 427 (Justin)
- Fixed issue 420 - Dotnet Patch from scopollif. (Justin)
- Fixed issue 415 - add 2Gig CT101 Thermostat (Justin)
- Started Implementing the Central Scene CC - With a good start by
tmartinez69009 - We still need to figure out the Capabilities decode -
Issue 367 (Justin)
- Fixed issue 425 - Bail out of Decrypting Packets if they are too short
(Justin)
- Fixed Fibaro FGD211 device config, removed automatic association for group 1&2 (Alex)
- Updated Z-Wave.Me device list thanks to Willem (Alex)
- Fixed Issue 431 - Update Fibaro fgrgbwm441 config thanks to Piotr (Alex)
- Fixed Issue 433 - Update Fibaro fgwpe config thanks to Piotr (Alex)
- Fixed Issue 439 - Update Fibaro FGMS001 config thanks to Jug (Alex)
- Fixed Issue 434 - Update Fibaro fgbs001 config thanks to Piotr (Alex)
- Fixed Issue 436 - Update Fibaro fgd211 config thanks to Piotr (Alex)
- Fixed Issue 437 - Update Qubino ZMNHDA2 config thanks to Piotr (Alex)
- Added Aeon Siren Gen5 device thanks to Alle (Alex)
- Added GE 12724 3-Way Dimmer Switch device thanks to Dax (Alex)
- Added additional Fibaro FGBS001 device id thanks to Stef (Alex)
- Added ConnectHome CH-201 device thanks to Tehnoinstyle (Alex)
- Detect if the Controller Supports SUC - If not, Dont try to become a SUC
when starting up (Justin)
- Add Sigma Designs UZB Z-Wave USB Adapter (Justin)
- Make sure LogLevels parsed are within range (Justin)
- Fix IntervalBetweenPolls always being false regardless of Options.xml
setting. (Justin)
- Make sure we refresh all UserCodes upto the first available slot unless
RefreshAllUserCodes is true in Options.xml (Justin)
- Added Qubino ZMNHIA2 device thanks to Paul (Alex)
- Fixed Issue 444 - Added Aeon Aeon Labs Micro Smart Energy Dimmer thanks
to yy (Alex)
- Fixed Issue 430 - Spelling Mistake (Justin)
- Add Support for CommandClasses that are marked as Controlling (versus
Controlled) to be able to still query the Device for Data. This is needed
for the CentralScene CC which is implemented as Controlling on most
devices (Justin)
- CentralScene CC should be able to query for number of Scene's supported.
Needs further testing with other devices (only BeNext at the moment is
tested) (Justin)
- When refreshing the ConfigParams on a device, place the messages in the
MsgQueue_Query queue rather tha the MsgQueue_Send queue. This should help
the "responsiveness" of OZW during startup if a user sends a message and
there is a big backlog in the Send Queue (Justin)
- Fixed issue 452 - Fix the ValueID for Door_Lock index to report correct
status. (Justin)
- Fixed issue 448 - Dont request Basic Get if we have a mapped Class during
startup (Justin)
- Added Everspring HAN02 device thanks to lookwhatthecat (Alex)
- Fixed issue 453 - Don't crash if we skip notifications due to invalid
ValueID's (Justin)
- Fixed issue 456 - Added NorthQ NQ-9021 device thanks to manu (Alex)
- Fixed issue 455 - Fixed Fibaro FGD211 device config thanks to Wouter (Alex)
- Fixed Popp 123580 Plug-in Dimmer device config thanks to Tom (Alex)
- Fixed issue 457 - Added zwave.me KFOB-S device thanks to Tony (Alex)
- Updated BeNext TagReader device config thanks to Rob (Alex)
- Added Philio PST02-1B device thanks to Thaui (Alex)
- Updated BeNext TagReader device config (Alex)
- Fixed issue 449 - Update Wenzhou TZ67 device config thanks to bas (Alex)
- Fixed issue 367 - Implement CentralScene with lots of testing by
TMartinez (Justin)
- Update our Mutex's to use Scoped Locks instead. This saves us from having
to track Lock/Unlocks. Implemented for the m_nodeMutex in the
DriverClass. We should also port the Polling and Send Mutex's as well.
This fixes issue 451 (Justin)
- Fixed issue 459 - Alarm Class Version 2 (Justin)
- Fix DoorLockLogging Class not saving the Max Number of records (Justin)
- Fixed issue 470 - Qubino ZMNHDA2 device update thanks to kvervloesem (Alex)
- Fixed Issue 462 - Fix Builds on FreeBSD - From Stromnet (Justin)
- Added Vision Z-Wave USB Stick device thanks to GizMoCuz (Alex)
- Fixed issue 469 - Added Fibaro Smoke Detector FGSD-002 thanks to tmartine (Alex)
- Fix LogImpl crash if no filename was configured (pull req 488) (Stromnet)
- Update Fibaro Smoke Sensor device, interview process wouldn't complete (Alex)
- Fixed issue 464 - Added/Updated Polycontrol keypad/doorlock devices thanks to santal (Alex)
- Fixed issue 495 - Added Fibaro FGD211 device thanks to nechry (Alex)
- Fixed issue 496 - Added Aeon-Labs Z-Stick Gen5 thanks to nechry (Alex)
- Don't kill Notifications for ValueAdded and ValueRemoved as they might
not exist right then (Justin)
- Pull Request #516 - Add Philio PST02-1C thanks to Ugoviti (Justin)
- Pull Request #517 - Add Aeon Labs Gen5 thanks to Ugoviti (Justin)
- Pull Request #515 - Add Widom USB104 Universal Relay Switch thanks to Ugoviti (Justin)
- Pull Request #508 - Update Fibaro FGFS101 Association Groups thanks to Nechry (Justin)
- Pull Request #504 - CRC16Encap CC Support from xs4 (Justin)
- Pull Request #522 - Dragon Tech In wall dimmer from Stevejbauer (Justin)
- Fix Issue #523 - Add Wenzhou Door/Window Sensor from whiteduck22 (Justin)
- Pull Request #534 - Add Aeon Labs Recessed Door Sensor Gen5 from xxv (Justin)
- Pull Request #532 - Fix Aeon Labs DoorWindow Sensor Config from Nechry (Justin)
- Pull Request #529 - Updated Config for the Zipato MiniKeyPad from Nechry (Justin)
- Pull Request #528 and #527 - Add Aeon Labs Key Fob Gen5 Config from Nechry (Justin)
- Add new ID's for BeNext Energy Switch from Rob (Justin)
- Depreciate the ControllerCommand method in the Manager class and replace with direct
function calls (Justin)
- Pull Request #538 and #541 - Add SwiidInter to manufacturer_specific from Nechry (Justin)
- Pull Request #545 - Add Philio PST02-A 4 in 1 MultiSensor from Nechry (Justin)
- Pull Request #565 - Add MultiInstanceAssociation CommandClass from xs4 (Justin)
- Pull Request #546 - Update Philio PST02-A Config from Nechry (Justin)
- Pull Request #547 & #549 - New Config File for Philio PST02-B from Nechry (Justin)
- Pull Request #548 - Update Config file for Philio PST02-C from Nechry (Justin)
- Pull Request #550 - Config File for Vision zd2102 from Ugoviti (Justin)
- Fix a crash when dumping the Queue to the Log, reported by Gizmocuz (Justin)
- Pull Request #555 - Update the dotNet wrapper and OZWForm to use the new
Manager Methods that replace the BeginControllerCommand Method. From
JKlessens (Justin)
- Pull Request #564 - Add Cooper Configs from Stevejbauer (Justin)
- Pull Request #561 - Add Version String Method from Ikkemaniac (Justin)
- Pull Request #562 - Fix Windows Build Event with wrong directory from douglasbeck (Justin)
- Pull Request #567 and Issue 566 - Add Fibaro FGS221 from Nechry and
DanielLast (Justin)
- Pull Request #574 - Add Fibaro FGS212 Config from Nechry (Justin)
- Pull Request #576 - Fix up Qubino ZMNHBA2 Help from DavZero (Justin)
- Pull Request #578 - Add NodOn SmartPlug, Swiid SwiidPlug and update
ZME_064435 Config fron Nechry (Justin)
- Pull Request #580 - Add zwave.me Razberry ZWave+ adapter from Nechry
(Justin)
- Pull Request #581 - Update Zipato Minikeypad from Nechry (Justin)
- Fixed issue #352 - Security Rewrite (Justin)
- Fixed issue #467 - Fixed Aeon Labs Multisensor Gen5 (Justin)
- Fixed issue #471 - Fixed Vision ZD2102 (Justin)
- Fixed issue #472 - Fixed Aeon Labs Siren Gen5 (Justin)
- Fixed issue #473 - Fixed Philio PST02-1C Slim Multisensor (Justin)
- Fixed issue #540 - Depreciate the BeginControllerCommand Method for
dedicated methods in the Manager Class - Applications should update their
code to use the new API instead. (Justin)
- Pull Request #587 - Add Zwave.me ZME_WALLC-S Secure Wall Controller from
xs4 (Justin)
- Fixed issue #586 - Compile Error on newer GCC's (Justin)
- Fixed issue #568 - Compile Error on new OSX (Justin)
- Update the device_classes.xml with the latest known mappings (Justin)
- Enable NWI when adding nodes if HighPower is also enabled (Justin)
- Pull Request #596 - Aeotec Z-Stick Gen5 and GE 12722 on/Off Relay from
SpudGunMan (Justin)
- Pull Request #595 - Aeotec Smart Switch Gen5 Config Updates from Gert
Boer and Nechry (Justin)
- Pull Request #594 - Aeotec Minimote Config Updates from Nechry (Justin)
- Update Aeon Labs to Aeotec as thats their Retail name (Justin)
- Pull Request #598 - Update Config Files for Fibaro FGS212 and FGS222 from
Nechry (Justin)
- If we recieve a cleartext message for a Secured CommandClass, drop the
message (Configurable - Set EnforceSecureReception to false in
options.xml) (Justin)
- Add Aeotec LED Bulb, MultiSensor 6 and SmartSwitch 6 Configs (Justin)
- Add Aeotec DSC24 identification and Everspring AD147 identification + config
- Add Schlage BE469NXCEN TouchScreen DeadBolt from Rushidesai (Justin)
- Pull Request #622 - Aeotec Micro Smart Energy Switch from Ugoviti (Justin)
- Issue #628 - Update Everspring SP814 Config file from iarmstrong (Justin)
- Issue #621 - Add Apache License for the cpp/build/sh2ju.sh script from Alteholz (Justin)
- Issue #585 - Possible fix for Node 0/255 when adding new nodes. (Justin)
- Issue #626 & #381 - Fix Segfault when trying to get a Empty/unpopulated
ValueList (when we get a ValueAdded Notificiation)
- Issue #637 - Change Color Channels ValueID from Config to System Genre (Justin)
- Issue #635 and #636 - Add widom energy driven switch from RobyBob64 (Justin)
- Issue #632 - Add Horstmann SES 301 Temp Sensor from ado464 (Justin)
- Pull Request #639 - Update ZME_06433 with bugfixes and new options from
cyr123 (Justin)
- Pull Request #640 - Add FGD212 Dimmer 2 Config from xs4 (Justin)
- Pull Request #641 - Update ZMNHBA2 Config from xs4 (Justin)
- Add Aeotec Smart Dimmer 6 Config (Justin)
- Pull Request #649 - Add Everspring st812-Flood Detector from Warp95 (Justin)
- Pull Request #648 - Added configuration file for Merten 50x5xx Roller Shutter Module from Sascha (Justin)
- Pull Request #641 - A Large set of Config File updates from the Jeedom team (Justin)
- Issue #656 - Update ZME064435 and ZME05470 with Scene Activation Command
Class from CompaTech (Justin)
- Pull Request #655 - Update BeNext Devices from ewgast (Justin)
- Issue #658 - Reset a Message SendAttempts value when moving to the
Wakeup Queue, otherwise it gets dropped when we attempt to send it when
the device wakes up as it exceeds the retry count. (Justin)
- Issue #416 and Pull Request #506 - ValueShort and ValueSchedule were
using wrong Value Storage enums. Enhance Value::VerifyRefreshedValue to
handle almsot all types (Except Schedule) (Justin)
- Issue #501 - Fix ThermostatFanMode when checking for Valid Modes (Justin)
- Pull Request #659 - Added configuration file for D-Link Corp and DCH-Z110 Door/Window 3in1 sensor
from psixilambda (Justin)
- Issue #446 - Fix Visual Studio 2015 breakage. (Justin)
- Pull Request #664 - Add ZMHAD1 Qubino support from Wackoracoon (Justin)
- Pull Request #665 - Add ZMNHBD2 Flush 2 Relay from emdioh (Justin)
- Pull Request #668 - Add some new variables to pkg-config from Ekarak (Justin)
- Add a ozw_config file as a replacement for pkg-config and update pkgconfig install dirs (Justin)
- Pull Request #670 - Typo: Changes "Temerature" to "Temperature" from cslarsen (Justin)
- Added Aeotec DoorBell and Dry Contact Sensor (Justin)
- Issue #672 - Infinate Loop when refreshing ZWPlus Command Class (Justin)
- Issue #674 - Fix crash on Central Scene Message (Justin)
- Issue #671 - Updated Zwave.me ZME_WALLC-S Config file from rgroothuis (Justin)
- Pull Request #676 - Fix Windows Build Version and a few enhancements to
the dotNet wrapper from bufferUnderrun (Justin)
- OOhhhh. Pretty Colors (Justin)
- Pull Request #677 - Update for Linear Dimmers PD300Z-2 and WD500Z-1 from vexofp (Justin)
- Added Aeotec DoorBell and Dry Contact Sensors config files (Justin)
- Issue #679 - Add Thermofloor TF 016 Terhmostat from Cog (Justin)
- Pull Request #686 - Add Australian Z-Stick Gen5 from phil-nelson (Justin)
- Pull Request #693 - Notification::GetAsString needs to be Const from Ekarak (Justin)
- Merge a few fixes from Gizmocuz for VisualStudio Warnings (Justin)
- Update of Deb files from Lucas Nussbaum (Justin)
- Pull Request #700 - Updated Linear switch configs and added Enerwave ZWN-SC7 config from Vexofp (Justin)
- Pull Request #696 - Config for HomeSeer HSM200, add config parameters for schlage touchscreen deadbolts from gwmullin (Justin)
- Issue #698 - Add config file for Vision CP3102 from Erik-NA (Justin)
- Issue #692 - Add Wenzhou TZ68 config file from gsolem (Justin)
- DotNet Wrapper fix for GetAllScenese from Bas Prins (Justin)
- Issue #688 - Qubino ZMNHDD1 Z-Wave Plus flush dimmer from bbqkees (Justin)
- Issue #701 - FreeBSD Fixes from stromnet (Justin)
- Issue #703 - Updated Config file for Benext DoorSensor from gizmocus (Justin)
- Issue #702 - Config file for Qubino ZMNHND1 Flush Relay from hanscbecker (Justin)
- Pull Request #705 - config files for fortrezz MIMOlite from gwmullin (Justin)
- Pull Request #706 - config files for Qubino ZMNHCDx from guillaumezin (Justin)
- Pull Request #711 - config files for POPP Wall Plug Switch Schuko from hellqvist (Justin)
- Add additional codes for Fibaro FGRM222 Roller Shutter from proohu01 (Justin)
- Add ZME_064381 IP44 Plug-in Switch config from Geoff Coupe (Justin)
- Pull Request #712 - New Manager::GetValueListValues function to get the indexes of a List from out4b (Justin)
- Pull Request #710 - Added config files for Eurotronic Comet thermostatic radiator valve (Justin)
- Issue #714 - Z-Wave.Me ZME_KFOB-C 4 Button Key Fob config files from pbda (Justin)
- Issue #715 - Add Sensative Strips-MAZW config file from michapr (Justin)
- Issue #716 - Aeotec MultiSensor 6 config updates from michapr (Justin)
- Pull Request #720 - Added support for Merten Plug-in Roller Shutter Module from Marco (Justin)
- Pull Request #721 - Create POP009303.xml from armaesiea (Justin)
- Pull Request #724 - Update config/fibaro/fgd212.xml from MHediund (Justin)
- Pull Request #727 - Update DotNet Wrapper from bufferUnderrun (Justin)
- Pull Request #728 - Fix FreeBSD compile from durin42 (Justin)
- Store Manufacturer ID, Type and Product ID as shorts instead of strings. (Justin)
- Change QueryStage_Probe1 to QueryStage_CacheLoad to reflect this is where we start when loading a device from Cache (Justin)
- Issue #729 - Add Qubino Flush Dimmer ZMNHJD1 from Stephane guillard (Justin)
Version 1.2
- Released on 15/10/14
Version 1.1
- Fixed Command Class Recieved Message Counter when we are handling a
MultiInstanceMessageEncap Message (Justin)
- Fixed Issue 310 - Unbalanced Lock/Release in Manager::IsNodeFailed and
Manager::GetNodeQueryStage (Justin)
- For Sleeping Devices - Do Not automatically add WakeUp Class to these
devices if they advertise themselves as FrequentListening. This matches
the Logic in the QueryStage functions where we skip querying the Device
for Wakeup Configuration if its set as FLiRS. Needs some testing (Justin)
- Options.xml file can now live in both the System Config Path
(/etc/openzwave for example) or the Local Application Path. Local
Options.xml will override any System Options.xml (Justin)
- Updated the Include Paths so we only have to specify the top level src
directory for GCC, and the rest of the headers are specified as subdirs.
Based on work started by Svente Karisson (Justin)
- A few fixes for Windows Calls and various casts required to eliminate
warnings (Svente Karisson)
- Add a Error String if we fail to parse our Options.xml files (Justin)
- Added a Complete Door Lock Command Class (Justin)
- Change the Logic in the UserCode Command Class to only retrive UserCodes
upto the first available slot (Justin)
- Add a ValueButton to the UserCode class to refresh all UserCodes (Justin)
- Fixed Issue 301 - Updated Aeon Recessed Door Sensor (Justin)
- Fixed Issue 302 - New ID for Aeon Labs Door/Window Sensor (Justin)
- Fixed Issue 306 & 304 - Updated Fibaro FGMS Config File (Justin)
- Fixed Issue 308 - Add Zenzhou TZ65D Dual Wall Dimmer (Justin)
- Fixed Issue 309 - Add Config File for ZWave.Me Flush Mountable Switch (Justin)
- Fixed Issue 311 - Add Vision Siren (Justin)
- Fixed Issue 314 - Updated Fibaro RGBW Config File (Justin)
- Fixed Issue 318 - Updated Fibaro Wall Plug Config File (Justin)
- Fixed Issue 321 - Updated Fibaro FGRM222 Config File (Justin)
- Fixed Issue 324 - New Config file for Aeon Labs MiniMote (Justin)
- Added ZWave.Me iTemp Config file thanks to Willem Burgers (Justin)
- Added new id for Aeon Labs Micro Smart Engergy Illuminator G2 thanks to
jmeyer (Justin)
- Fixed Issue 329 - Update Fibaro FGD211 Config File (Alex)
- Fixed Issue 330 - Update Fibaro FGS211 Config File (Alex)
- Fixed Issue 331 - Update Fibaro RGBWM441 Config File (Alex)
- Add new id for GE Duplex Receptacle (Alex)
- Add 18 new ids for Vision devices (Alex)
- Add Device Qees RETO Plug-in Switch Plus Config File (Alex)
- Implement DoorLockLogging Command Class (Justin)
- Implement Security Command Class (Justin)
- Add a additional ID for Vision ZM1701 Deadbolt without Handle (Justin)
- Add a ID and Config file for Assa Abloy Real Living Cap-Touch Deadbolt
(Justin)
- Implement the TimeParameters Command Class (Justin)
- Fix up AssumeAwake Option for the Wakeup Class (Justin)
- Update BeNext Tag Reader Config File (Alex)
- Fixed Issue 335 - Update zwave.me KeyFob Config File (Alex)
- Fixed Issue 336 - Update Aeon Labs DoorSensor Config File (Alex)
- Fixed Issue 337 - Update Aeon Labs Multi Sensor Config File (Alex)
- Fixed Issue 338 - Update Aeon Labs Multi Sensor Config File (Alex)
- Fixed Issue 339 - Update Fibaro Door Opening Sensor Config File (Alex)
- Fixed Issue 340 - Add Remotec ZRC-100 Remote Control (Alex)
- Fixed Issue 301 - Add Philio PAN04-1 Relay Insert (Alex)
- Fixed Issue 341 - Corrected directory/filename errors in manufacturer xml (Alex)
- Fixed Issue 342 - Added 4 Qubino devices thanks to jeanfrancois (Alex)
- Fixed Issue 345 - Added new ids for Fibaro FGK101 and FGBS001 (Alex)
- Fixed Issue 351 - Added new ids for Vision VS6301 and updated Product Name (Justin)
- Fixed Issue 348 - Typo in Config Index Number for zwave.me ZME_06436 (Justin)
- Fix Several Warnings/Initilizers etc (Justin)
- Fixed Issue 357 - Fixed Qubino manufacturer id from 345 (dec) to 159 (hex) (Alex)
- Fixed Issue 356 - New ID for Fibaro FGMS001 (Alex)
- Do Not Open and Close the Log file on each message. Close it during the
Destructor (Justin)
- Race Condition in the RemoveDriver call and Notifications. Add a new
Notification about the Driver being removed, and by default turn off
NodeRemoved/ValueRemoved Notifications from being sent if the Driver is
being unloaded. WARNING: If you call any manager functions that require
the Driver after recieving this message, there is a high probability your
application will crash with a SegV (Justin)
- Fixed Issue 361 - Update Qubino ZMNHDA2 Config File, proper endpoint mapping (Alex)
- Fixed Issue 359 - Update Qubino ZMNHBA2 Config File, fixed invalid group 4 (Alex)
- Fixed Issue 360 - Add Config File for Popp 123658 (Alex)
- Fixed Issue 364 - Update Schlagelink iTemp Config File, removed invalid char (Alex)
- Fixed Issue 365 - Add Config File for Popp 123601 Plug-in Switch thanks to tony.b.hansson (Alex)
- Fixed Issue 366 - Add Config File for Popp 123580 Plug-in Dimmer thanks to tony.b.hansson (Alex)
- Fixed Issue 363 - Added new id for Schlagelink iTemp thanks to steph10200 (Alex)
- Fixed Issue 370 - Fixed Config File for zwave.me 06433 thanks to geilername (Alex)
- Fixed Issue 368 - Bounds Checking on our String Arrays (Justin)
- Fixed Issue 362 - Fix Mapping between ValueGenre Names and Enum's. This
might require you to delete your zwcfg_*.xml file if you encounter
problems (Justin)
- Fixed Issue 371 - Double ReleaseNodes on Invalid Node in GetNodeStatistics (Justin)
- Fixed Issue 372 - Mutex Unlocking in the Driver::isPolled method (Justin)
- Remove tinyxml.h include from our headers so we don't have to distribute
the TinyXML header files (Justin)
- Remove the hidapi.h include from our headers so we don't have to
distribute the hidapi header files (Justin)
- Fixed Issue 375 - Add Ecolink Garage Door Sensor - (Justin)
open-zwave-1.5/INSTALL 0000664 0000000 0000000 00000005055 12644742024 0014515 0 ustar 00root root 0000000 0000000 Minimal Install Guide for OpenZWave!
For Unix's (including Mac, bsd's etc)
=================
execute Make in the Top Level Directory
make
Libraries to link to (Static and Dynamic) will be in top level directory as
well (but you can change that as detailed below with LIBDIR)
To Install:
make install
Some Options you can set:
"BUILD=(release|debug)" - Build a Release or Debug Version of the Library
(Release is default)
"PREFIX=(path)" - Prefix to install the shared library into - Defaults to
/usr/local
"LIBDIR=/tmp" - Path to place the libraries into after complication. A poor
mans "make install" for simple Applications.
To use the options, specify them on the commandline when executing make eg:
"BUILD=debug PREFIX=/opt/local make"
What Gets installed:
When make install is called the following happens:
* Documentation:
if you have DoxyGen, API documentation is installed into
(PREFIX)/share/doc/openzwave-(version)/
* Shared Libary (libopenzwave.so.*):
The Shared Library is installed into either (prefix)/lib64 (on 64
bit platforms) or (prefix)/lib/ on 32 bit platforms)
* Header Files:
Installed into (prefix)/include/openzwave/
* pkg-config file:
Installed into (prefix)/lib(64)/pkgconfig/libopenzwave.pc
* Config files and Device Databases (manufacturer_specific.xml et al)
Installed into (prefix)/etc/openzwave/
* MinOZW example program:
Installed into (prefix)/bin/ directory
The Static Version of the library is never installed, but will be created in
top build directory after a successfull make.
Windows Versions
================
Visual Studio Solution Files and Mingw32 Makefiles are present in
cpp/build/windows/. Select the correct Visual Studio or Mingw32 directory
depending on the versions you have.
(Note, if building DLL's on Windows (currently a option in the vs2010
solution) - You have to ensure you application is compiled with exactly the
same compiler options and versions as OpenZWave - Otherwise strange things
might happen)
For the .NET dll, the solution files exist in the dotnet/build/ directory
Sample Programs
===============
For all platforms, there is a simple example program that will print out
events as they happen on your ZWave network. This sample is called MinOZW
and you can find the source in the cpp/examples directory. By default, these
examples are built during the Make Install Stage. If you want compile them
separately, you can use the "make examples" target.
For the .NET wrapper, there is a OZWForm application in
dotnet/examples/OZWForm/. Please read the README file in that directory for
further instructions
open-zwave-1.5/Makefile 0000664 0000000 0000000 00000003226 12644742024 0015122 0 ustar 00root root 0000000 0000000 #
# Makefile for OpenzWave Mac OS X applications
# Greg Satz
# GNU make only
# requires libudev-dev
.SUFFIXES: .d .cpp .o .a
.PHONY: default clean install
top_srcdir := $(abspath $(dir $(lastword $(MAKEFILE_LIST))))
top_builddir ?= $(CURDIR)
export top_builddir
PREFIX ?= /usr/local
export PREFIX
all:
CPPFLAGS=$(CPPFLAGS) $(MAKE) -C $(top_srcdir)/cpp/build/ -$(MAKEFLAGS)
CPPFLAGS=$(CPPFLAGS) $(MAKE) -C $(top_srcdir)/cpp/examples/MinOZW/ -$(MAKEFLAGS)
install:
$(MAKE) -C $(top_srcdir)/cpp/build/ -$(MAKEFLAGS) $(MAKECMDGOALS)
$(MAKE) -C $(top_srcdir)/cpp/examples/MinOZW/ -$(MAKEFLAGS) $(MAKECMDGOALS)
clean:
$(MAKE) -C $(top_srcdir)/cpp/build/ -$(MAKEFLAGS) $(MAKECMDGOALS)
$(MAKE) -C $(top_srcdir)/cpp/examples/MinOZW/ -$(MAKEFLAGS) $(MAKECMDGOALS)
cpp/src/vers.cpp:
CPPFLAGS=$(CPPFLAGS) $(MAKE) -C $(top_srcdir)/cpp/build/ -$(MAKEFLAGS) cpp/src/vers.cpp
check: xmltest
include $(top_srcdir)/cpp/build/support.mk
ifeq ($(XMLLINT),)
xmltest: $(XMLLINT)
$(error xmllint command not found.)
else
xmltest: $(XMLLINT)
@$(XMLLINT) --noout --schema $(top_srcdir)/config/device_classes.xsd $(top_srcdir)/config/device_classes.xml
@$(XMLLINT) --noout --schema $(top_srcdir)/config/options.xsd $(top_srcdir)/config/options.xml
@$(XMLLINT) --noout --schema $(top_srcdir)/config/manufacturer_specific.xsd $(top_srcdir)/config/manufacturer_specific.xml
@$(XMLLINT) --noout --schema $(top_srcdir)/config/device_configuration.xsd $(top_srcdir)/config/*/*.xml
endif
dist-update:
@echo "Updating List of Distribition Files"
@$(GIT) ls-files > .distfiles
@$(top_srcdir)/makedist
DIST_FORMATS ?= gzip
include $(top_srcdir)/distfiles.mk
include $(top_srcdir)/dist.mk
open-zwave-1.5/README.md 0000664 0000000 0000000 00000012650 12644742024 0014742 0 ustar 00root root 0000000 0000000 Open-ZWave Library
==================
Our goal is to create free software library that interfaces with selected Z-Wave PC controllers, allowing anyone to create applications that manipulate and respond to devices on a Z-Wave network, without requiring in-depth knowledge of the Z-Wave protocol.
This software is currently aimed at Application Developers who wish to incorporate Z-Wave functionality into their applications.
Our Homepage is at http://www.openzwave.net/ and our Github Page is located at https://github.com/OpenZWave/. If you wish to participate on our Mailing List, please visit https://groups.google.com/forum/#!forum/openzwave
## Getting Started
There is a example application on how to interface with the library called MinOZW. This currently offers a minimal example on how to monitor for changes and enable Polling of values. There are also plenty of other examples on the Internet that you can research.
## Getting Help
If you are using a Application that uses OZW, you should first check with the Application Developers for support. As OZW is a library used by dozens of large opensource home automation applications, we can not support application related issues here. If your application developer indicates the problem may be with OZW, please follow the guidelines below.
First thing you should do if you are running into troubles is search our [mailing list](https://groups.google.com/forum/#!forum/openzwave). There is a high chance that your problem may have already been discussed on the list.
If your still having problems, you should Generate a Log file and upload your Log to the [Log Analyzer on our homepage](http://www.openzwave.com/log-analyzer), which will check for common issues, and provide some basic recommendations. Please follow the instructions on that page to ensure your log file contains the relevant information.
If you think you have found a bug, please see the next section.
For General Questions/How Do I etc, please post a message to our [mailing list](https://groups.google.com/forum/#!forum/openzwave)
## Opening or Contributing to a Issue on Github
Z-Wave is a reasonably complex protocol, and thus, it almost always necessary for us to review a OZW Log file to determine what’s going on. As GitHub does not support attachments on Issues, please upload a [LogFile](http://www.openzwave.com/log-analyzer) and then create a issue on [GitHub](https://github.com/OpenZWave/open-zwave/issues). Please include a link to the LogFile Scan results (check the "Public Results" button on the results page and copy the URL it links to).
Not uploading a Log file will often mean that we are unable to provide any further help without seeing what’s going on, so please ensure you do this.
## Supporting New Devices
If your device is not recognized by OZW, it should still work as long as its compliant with the Z-Wave specifications. Our Device database is mainly community contributions, so please consult [this page](https://github.com/OpenZWave/open-zwave/wiki/Adding-Devices) on how to add the Device to the manufacturer_specific.xml file and generate a Configuration file for it.
## Contributing to OZW
We are happy to accept Pull Requests via GitHub. A few things to follow when preparing a Pull Request.
1. If you have added or changed any of the configuration files (eg, adding a new device) please run "make xmltest" from the root directory to ensure your XML is well formed.
2. Please add a entry to the ChangeLog describing the change you made.
3. If you are changing some internal code paths in OZW, please discuss on the mailing list prior to starting your work. Z-Wave is complex and there are lots of corner cases as far as proper support of the various (non-standard) devices out there. While it might sometimes seem overcomplicated, it most likely is there for a reason.
4. Finally, if you have signed a NDA with Sigma Designs, we are unable to accept your changes. OZW is developed by reverse engineering and consulting publically available information. We have not signed a NDA with Sigma, and do not want users to infringe upon their agreement with Sigma either.
## Final Words
As mentioned above, Open-ZWave is developed by mainly reverse engineering the protocol as well as consulting various public information on the Internet. We have not used any of the Sigma SDK’s or documentation and thus often it will take us a while to support new features of Z-Wave.
We have had very preliminary discussions with both the Z-Wave Alliance and Sigma previously but we do not have any "official" endorsement from either of them (though that is a goal for the developers). We do believe that OZW has benefited the Z-Wave ecosystem though, and have received feedback that we are well known by various Z-Wave Vendors.
That being said, although our license (LGPL) permits commercial applications (provided your follow the rules) we strong recommend you consult a lawyer prior to implementing OZW support into your application.
Of course, for Open Source applications, as long as you abide by our License (LGPL) we would love to welcome you the OZW community!
And for those that are wondering, you cannot use OZW to create Z-Wave Nodes. This is not the goal of the library, and we believe that if we started implementing a software stack that allowed users to start creating Z-Wave Nodes, Sigma designs would not be so happy about our existence. Hence please avoid discussing this topic on our mailing list .
open-zwave-1.5/config/ 0000775 0000000 0000000 00000000000 12644742024 0014724 5 ustar 00root root 0000000 0000000 open-zwave-1.5/config/2gig/ 0000775 0000000 0000000 00000000000 12644742024 0015554 5 ustar 00root root 0000000 0000000 open-zwave-1.5/config/2gig/ct100.xml 0000664 0000000 0000000 00000000325 12644742024 0017125 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/2gig/ct101.xml 0000664 0000000 0000000 00000000325 12644742024 0017126 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/2gig/ct30.xml 0000664 0000000 0000000 00000000325 12644742024 0017047 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/BeNext/ 0000775 0000000 0000000 00000000000 12644742024 0016111 5 ustar 00root root 0000000 0000000 open-zwave-1.5/config/BeNext/1poleswitch.xml 0000664 0000000 0000000 00000002762 12644742024 0021104 0 ustar 00root root 0000000 0000000
Set all configuration values to default values (factory settings).
The mode in which a different Z-Wave message is sent.
The time that a user has to activate the double button pressed scene, if time is passed then the single pressed button scene is notified. (value * 10 ms)
A signed integer to determine the offset of the temperature.
open-zwave-1.5/config/BeNext/2poleswitch.xml 0000664 0000000 0000000 00000002762 12644742024 0021105 0 ustar 00root root 0000000 0000000
Set all configuration values to default values (factory settings).
The mode in which a different Z-Wave message is sent.
The time that a user has to activate the double button pressed scene, if time is passed then the single pressed button scene is notified. (value * 10 ms)
A signed integer to determine the offset of the temperature.
open-zwave-1.5/config/BeNext/AlarmSound.xml 0000664 0000000 0000000 00000007552 12644742024 0020711 0 ustar 00root root 0000000 0000000
Set all configuration values to default values (factory settings)
Enables an internal routine that periodically checks the Z-Wave device in assocication group 2
Configure the time that the AlarmSound sends a new frame when previous frame was send successful
Configure the time that the AlarmSound sends a few frame when previous frame was send not successful
A (signed) offset to calibrate the onboard temperature sensor
A (signed) offset to calibrate the onboard temperature sensor
The index of the sound mode when a switch binary/basic set frame is received
The index of the sound mode when the AlarmSound will start when it is unplugged
The index of the sound mode when the AlarmSound will play when it is unable to reach the device in association group 2
Params 10 until 27 are the values to configure the sound and light thtat are played when index 1 is selected
Params 28 until 45 are the values to configure the sound and light thtat are played when index 2 is selected
Params 46 until 63 are the values to configure the sound and light thtat are played when index 3 is selected
Params 64 until 81 are the values to configure the sound and light thtat are played when index 4 is selected
Params 82 until 99 are the values to configure the sound and light thtat are played when index 5 is selected
Params 100 until 117 are the values to configure the sound and light thtat are played when index 6 is selected
open-zwave-1.5/config/BeNext/BuiltinDimmer.xml 0000664 0000000 0000000 00000012151 12644742024 0021377 0 ustar 00root root 0000000 0000000
Set all configuration values to default values (factory settings).
The way how the button reacts when press/released
The way the Built-in Dimmer reacts when light is turned on/off with button
This parameter is used to enable the dimming option of the product. When disabled the dimming and fading routine are disabled.
The maximum powerload in watts when light is turned on, when measured higher then this value the Inline Dimmer is automatically turned off.
The speed of dimming when activated (manual and RF). Dim speed is 1% per value (* 10 ms)
The speed of fading up when activated (manual and RF). Fade speed is 1% per value (* 10 ms)
The time window to repress button to start dimming. Toggle time is value (* 10ms)
A percentage that an energy value must be different compared to a previous sent value before an unsolicited meter report is sent. Minimum value = 10% Maximum value = 100%
A watt value that an energy value must be different compared to a previous sent value before an unsolicited meter report is sent. Minimum value = 5 watt Maximum value = 255 watt
A time value that has to be passed compared to a previous sent value before a unsolicited meter report is sent. Minimum value = 10 seconds Maximum value = 255 seconds
What to do with lamp status when power applied. If 0x00: Always switch light off when power applied. If > 0x00: Switch lamp on/off depending on last known lampstatus before power was disconnected.
The speed of fading up when activated (manual and RF). Fade speed is 1% per value (* 10 ms)
open-zwave-1.5/config/BeNext/DoorSensor.xml 0000664 0000000 0000000 00000005773 12644742024 0020744 0 ustar 00root root 0000000 0000000
Set all configuration values to default values (factory settings).
Configure what the external contact sends when triggered. (Default: 0)
Is not used but can still be set and requested.
Is not used but can still be set and requested.
To configure the operating mode. (Default: 1)
A signed integer to determine the offset of the temperature. (Default: 0)
Debounce time when the external contact is opened. (Default: 0)
Debounce time when the external contact is opened. (Default 0)
A delay from the wake up time to give the external contact a chance to change his status. (Default 0, value * 100 ms, 0 - 25,5 seconds)
open-zwave-1.5/config/BeNext/EnergySwitch.xml 0000664 0000000 0000000 00000002616 12644742024 0021253 0 ustar 00root root 0000000 0000000
Set all configuration values to default values (factory settings).
The state in what the switch is when power is supplied.
When the relay is switched it can't be switched again until the configured time has passed.
Show the led state compared to the relay state.
open-zwave-1.5/config/BeNext/HeatingControl.xml 0000664 0000000 0000000 00000005565 12644742024 0021566 0 ustar 00root root 0000000 0000000
Set all configuration values to default values (factory settings).
The interval that data is requested (and therefore updated) from the thermostat and boiler. Value in seconds.
The value that the room temperature must differ (compared to his previous send value) before an unsolicited room temperature report is send to the associated node. Value in 0.1 °C.
The value that the temperature setpoint must differ (compared to his previous send value) before an unsolicited temperature setpoint report is send to the associated node. Value in 0.1 °C .
TConfigure if the unsolicited reports are send with the CRC-16 encapsulation. Not that the receiving node should support this encapsulation to parse the Z-Wave frame!
Type of 'special' thermostat: NOTE: when remeha Celcia 20 support is set then any other thermostat can not be set (!) NOTE2: when Remeha Celcia 20 gives 'Fout 203' send cfg value again
Enable/Disable thermostat schedule inside the heatingcontroller.
open-zwave-1.5/config/BeNext/Molite.xml 0000664 0000000 0000000 00000004053 12644742024 0020066 0 ustar 00root root 0000000 0000000
Set all configuration values to default values (factory settings).
The time used in mode 2 to turn the sensor off. This Time will start running as soon as detection is seen.
The switch off time will start running as soon as mode timeout is done. Motion sensor is turned on and when movement is detected again the mode timeout (cfg param 1) will start running all over again. When switch off time is done a basic off message is sent to the associated node.
Sensitivity value between 0 and 127 (values above 127 will be reported as the set value but will be handled in SW as 127).
The mode that is entered after detection. If mode is 0 or higher then 3, that value will be reported after a get but will be handled in SW as mode 2.
open-zwave-1.5/config/BeNext/PluginDimmer.xml 0000664 0000000 0000000 00000010571 12644742024 0021233 0 ustar 00root root 0000000 0000000
Set all configuration values to default values (factory settings).
The way the Built-in Dimmer reacts when light is turned on/off with button
This parameter is used to enable the dimming option of the product. When disabled the dimming and fading routine are disabled.
The maximum powerload in watts when light is turned on, when measured higher then this value the Inline Dimmer is automatically turned off.
The speed of dimming when activated (manual and RF). Dim speed is 1% per value (* 10 ms)
The speed of fading up when activated (manual and RF). Fade speed is 1% per value (* 10 ms)
A percentage that an energy value must be different compared to a previous sent value before an unsolicited meter report is sent. Minimum value = 10% Maximum value = 100%
A watt value that an energy value must be different compared to a previous sent value before an unsolicited meter report is sent. Minimum value = 5 watt Maximum value = 255 watt
A time value that has to be passed compared to a previous sent value before a unsolicited meter report is sent. Minimum value = 10 seconds Maximum value = 255 seconds
What to do with lamp status when power applied. If 0x00: Always switch light off when power applied. If > 0x00: Switch lamp on/off depending on last known lampstatus before power was disconnected.
The speed of fading up when activated (manual and RF). Fade speed is 1% per value (* 10 ms)
open-zwave-1.5/config/BeNext/SceneController.xml 0000664 0000000 0000000 00000002017 12644742024 0021734 0 ustar 00root root 0000000 0000000
Set all configuration values to default values (factory settings).
The time that a user has to activate the double button pressed scene, if time is passed then the single pressed button scene is notified.
open-zwave-1.5/config/BeNext/TagReader.xml 0000664 0000000 0000000 00000004235 12644742024 0020475 0 ustar 00root root 0000000 0000000
Set all configuration values to default values (factory settings).
To configure the time the beep is automatically turned off in seconds.
To configure the timeout to wait for a WAKEUP_NO_MORE_INFORMATION before the error beep is automatically sound. The error beeps are fixed 8 beeps shortly after each other.
To configure the number of beeps per second. Every beep is fixed about 10ms.
To configure the operating mode. If any mode other then 3, that value will be reported after a get but will be handled in SW as mode 1.
The time (*10 ms) that the RFID circuit is started after home or away is pressed (default 100 = 100*10ms=1s)
open-zwave-1.5/config/POP009303.xml 0000664 0000000 0000000 00000015472 12644742024 0016574 0 ustar 00root root 0000000 0000000
In separate mode button 1 works with Group A, button 3 with Group C. Click is ON, Hold is dimming UP, Double click is OFF, Click-Hold is dimming DOWN. In pair button 1/3 are UP/DOWN correspondingly. Click is ON/OFF, Hold is dimming UP/DOWN. Single clicks works with Group A, double click with Group C.
In separate mode button 2 works with control group B, button 4 with control group D. Click is ON, Hold is dimming UP, Double click is OFF, Click-Hold is dimming DOWN. In pair button B/D are UP/DOWN correspondingly. Click is ON/OFF, Hold is dimming UP/DOWN. Single clicks works with Group B, double click with Group D.
This parameter defines the command to be sent to devices of control group A when the related button is pressed.
This parameter defines the command to be sent to devices of control group B when the related button is pressed.
This parameter defines the command to be sent to devices of control group C when the related button is pressed.
This parameter defines the command to be sent to devices of control group D when the related button is pressed.
If the Wall Controller wakes up and there is no controller nearby, several unsuccessful communication attempts will drain battery.
If the Wall Controller wakes up and there is no controller nearby, several unsuccessful communication attempts will drain battery.
open-zwave-1.5/config/act/ 0000775 0000000 0000000 00000000000 12644742024 0015473 5 ustar 00root root 0000000 0000000 open-zwave-1.5/config/act/lfm20.xml 0000664 0000000 0000000 00000000222 12644742024 0017131 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/act/zdm230.xml 0000664 0000000 0000000 00000013541 12644742024 0017240 0 ustar 00root root 0000000 0000000
Dimmers controlled by this switch will start dimming from their current level.
Disable transmitting commands to Z-Wave devices that are in Group 4 without disassociating those devices from the group.
In night-light mode the LED on the switch will turn ON when the switch is turned OFF.
Change the top of the switch to OFF and the bottom of the switch to ON. Note: If you invert the switches and also install the product upside down, remember the load will now be controlled by the right, not the left switch.
This dimmer will start dimming from its current level.
When you press and hold the bottom of the ZDM230 switch once, the Z-Wave devices that are associated into Group 1 are sent the Dim command. If this parameter is set to "Yes" the devices in Group 1 will not go to the same level as the ZDM230.
Indicates how many levels the dimmer will change for each dimming step.
This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change.
Indicates how many levels the dimmer will change for each dimming step.
This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change.
Indicates how many levels the dimmer will change for each dimming step.
This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change.
Units in Group 4 only track when the dimmer is being turned ON and OFF and not while dimming.
The ZDM230 can operate shade control devices via its group 2.
The ZDM230 can operate shade control devices via its group 3.
The ZDM230 will flicker its LED when it is transmitting to any of its 4 groups. This flickering can be set to not flicker at all, to flicker the entire time it is transmitting, or to flicker for only 1 second when it begins transmitting.
Poll Group 2 Interval
Poll Group 2
open-zwave-1.5/config/act/zdw103.xml 0000664 0000000 0000000 00000010447 12644742024 0017253 0 ustar 00root root 0000000 0000000
Dimmers controlled by this switch will start dimming from their current level.
In night-light mode the LED on the switch will turn ON when the switch is turned OFF.
Change the top of the switch to OFF and the bottom of the switch to ON.
This dimmer will start dimming from its current level.
Indicates how many levels the dimmer will change for each dimming step.
This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change.
Indicates how many levels the dimmer will change for each dimming step.
This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change.
Indicates how many levels the dimmer will change for each dimming step.
This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change.
The ZDW103 can operate shade control devices via its group 2.
The ZDW103 can operate shade control devices via its group 3.
The ZDW103 will flicker its LED when it is transmitting to any of its 4 groups. This flickering can be set to not flicker at all, to flicker the entire time it is transmitting, or to flicker for only 1 second when it begins transmitting.
open-zwave-1.5/config/act/zdw232.xml 0000664 0000000 0000000 00000016527 12644742024 0017263 0 ustar 00root root 0000000 0000000
The ZDW232 can send Dim commands to Z-Wave enabled dimmers. The Dim command has a start level embedded
in it. A dimmer receiving this command will start dimming from that start level. However, the command also has a
bit that indicates whether the dimmer should ignore the start level. If the bit is set to 1, the dimmer will ignore the
start level and instead start dimming from its current level. If this bit is set to 0, the dimmer will not ignore the start
level.
You may wish to disable transmitting commands to Z-Wave devices that are in Group 4 without "un-associating"
those devices from the group. Setting parameter 2 to the value of 1 will stop the ZDW232 from transmitting to devices
that are "associated" into Group 4.
It is possible that you may only want the units in Group 4 to track when the dimmer is being turned ON and OFF
and not when dimming.
In night-light mode the LED on the switch will turn ON when the switch is turned OFF.
To change the top of the switch to OFF and the bottom of the switch to ON, set parameter 4 to 1.
The ZDW232 can be set to ignore the start level that is part of the dim command, regardless of whether the command
is telling the dimmer to ignore the start level or not ignore the start level embedded in the command (see Parameter
1). Setting parameter 5 to a value of 1 (factory default) will cause the ZDW232 to ignore the start level and to dim
or brighten from its current level. Setting the value to 0 will cause the ZDW232 to dim or brighten from the level in
the command.
When you press and hold the bottom of the ZDW232 switch once, the Z-Wave devices that areassociated into Group
1 are sent the Dim command. If parameter 6 is set to 0, after you release the switch, the ZDW232 will command
devices in that group to go to the same level of the ZDW232. If parameter 6 is set to a value of 1 (factory default)
the devices in Group 1 will not go to the same level of the ZDW232.
Indicates how many levels the dimmer will change for each dimming step.
This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change.
Indicates how many levels the dimmer will change for each dimming step.
This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change.
Indicates how many levels the dimmer will change for each dimming step.
This value indicates in 10 millisecond resolution, how often the dim level will change. For example, if you set this parameter to 1, then every 10ms the dim level will change. If you set it to 255, then every 2.55 seconds the dim level will change.
After the ZDW232 is commanded to stop dimming, it will then command the Z-Wave devices in Group 4 to the
ZDW232's new level. To prevent the ZDW232 from commanding the Z-Wave devices in Group 4 during this particular
occurrence, set Parameter 13 to the value of 1.
The ZDW232 can operate shade control devices via its group 2 if this configuration parameter is set to 1.
The ZDW232 can operate shade control devices via its group 3 if this configuration parameter is set to 1.
The ZDW232 will flicker its LED when it is transmitting to any of its 4 groups. This flickering can be set to not flicker at all, to flicker the entire time it is transmitting, or to flicker for only 1 second when it begins transmitting.
Poll Group 2 Interval
Poll Group 2
open-zwave-1.5/config/act/zir010.xml 0000664 0000000 0000000 00000006041 12644742024 0017243 0 ustar 00root root 0000000 0000000
The ZIR010 can be configured to operate in 1 of 3 modes.
Those modes are:
Lighting Mode (factory default)
Alarm Mode
Sensor Mode
To change the mode of operation:
For Lighting Mode: Send a value of 0 to Configuration Parameter #17.
For Alarm Mode: Send a value of 1 to Configuration Parameter #17.
For Sensor Mode: Send a value of 2 to Configuration Parameter # 17.
Information reproduced from: http://www.pepper1.net/zwavedb/uploads/resources/bdf086a9388325a2fb8b8aa298e24e512faec65d.pdf
The configuration parameter that can be used to adjust the amount of delay before the OFF or IDLE command is transmitted is Configuration Parameter # 18.
This parameter can be configured with the value of 0 through 255.
Where 0 means no delay and 255 means 255 minutes of delay.
Default appears to be 1 min.
Information reproduced from: http://www.pepper1.net/zwavedb/uploads/resources/bdf086a9388325a2fb8b8aa298e24e512faec65d.pdf
The ZIR010 can be disabled from sending commands unsolicited without removing associated devices by
setting Configuration Parameter # 19 to 0 (when asked for number of bytes, select 1).
Setting it back to 1 will re-enable the ZIR010.
Information reproduced from: http://www.pepper1.net/zwavedb/uploads/resources/bdf086a9388325a2fb8b8aa298e24e512faec65d.pdf
The time the ZIR010 stays awake can be adjusted from 15 seconds to 45 seconds by sending a value of 15
to 45 to the ZIR010 using Configuration Parameter # 22 (when asked for the number of bytes, select 1).
This awake time period starts over every time the ZIR010 receives a command or request.
Defaults to 30 seconds.
Information reproduced from: http://www.pepper1.net/zwavedb/uploads/resources/bdf086a9388325a2fb8b8aa298e24e512faec65d.pdf
open-zwave-1.5/config/act/zrp110.xml 0000664 0000000 0000000 00000000424 12644742024 0017252 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/act/zrw103.xml 0000664 0000000 0000000 00000003356 12644742024 0017272 0 ustar 00root root 0000000 0000000
Dimmers controlled by this switch will start dimming from their current level.
In night-light mode the LED on the switch will turn ON when the switch is turned OFF.
Change the top of the switch to OFF and the bottom of the switch to ON.
The ZRW103 will flicker its LED when it is transmitting to any of its 4 groups. This flickering can be set to not flicker at all, to flicker the entire time it is transmitting, or to flicker for only 1 second when it begins transmitting.
open-zwave-1.5/config/aeotec/ 0000775 0000000 0000000 00000000000 12644742024 0016164 5 ustar 00root root 0000000 0000000 open-zwave-1.5/config/aeotec/alms.xml 0000664 0000000 0000000 00000007146 12644742024 0017652 0 ustar 00root root 0000000 0000000
Stay awake for 10 minutes after batteries are inserted
How long should the device associated to multi sensor keep state On before sending it Off command (if the value is bigger than 255, the value would be rounded to next integer in minutes)
Enable Motion Sensor
Which commands to send when PIR motion sensor triggered
Reset to default parameters number 101-103. Any value other then 0 will initiate this reset.
Which reports need to send automatically in timing intervals for group 1. Bitsets: 0 -> Battery report, 5 -> Temperature, 6 -> Humidity, 7 -> Luminosity
Which reports need to send automatically in timing intervals for group 2. Bitsets: 0 -> Battery report, 5 -> Temperature, 6 -> Humidity, 7 -> Luminosity
Which reports need to send automatically in timing intervals for group 3. Bitsets: 0 -> Battery report, 5 -> Temperature, 6 -> Humidity, 7 -> Luminosity
Reset to default parameters number 111-113. Any value other then 0 will initiate this reset.
The interval of sending report group 1. 1 to 2678400 seconds
The interval of sending report group 2. 1 to 2678400 seconds
The interval of sending report group 3. 1 to 2678400 seconds
Reset to factory defaults.
open-zwave-1.5/config/aeotec/doorbell_gen5.xml 0000664 0000000 0000000 00000012300 12644742024 0021422 0 ustar 00root root 0000000 0000000
Set the repetitions for playing doorbell ringtone.
Value=1 to 255, the range of repetition is 1 to 100.
Note: If the time of playing doorbell ringtone is more than 20s,
the volume of ringtone will reduce to silence no matter how
many repetitions of doorbell ringtone are set.
Set the default doorbell ringtone.
Value=1-100, Specify the ringtone as default.
Select a ringtone to play.
Value=0, stop playing.
Value=1-100, play the specified ringtone.
Value=255, play the default ringtone.
Value=other, ignore.
Playback Control
Set the volume of ringtone.
Define functions of "Button -" and "Button+".
Button - is previous, Button+ is next.
Define functions of "Button -" and "Button+" when short
pressing and long pressing it.
Get Wireless Button Battery Status
Defines the automated status notification of an associated device when status changes
Defines the automated status notification of an associated device when the wireless button battery level changes
Pair the Wireless Button with Doorbell.
Value=0x55555555, Start the Wireless Button pairing mode and
the blue Led will blink slowly, short press the Wireless Button
once, if the blue Led change to be solid, which means the pairing
is successful. Otherwise, repeat the steps.
It will automatically exit the pairing mode after 8s if there is no
pressing action of the Wireless Button.
Note:
You can send this configuration Get CC to ask the pairing result:
If configuration report value=0x00000000, which means the
pairing is failed.
If configuration report value =0xFFFFFFFF, which means the
pairing is successful.
Enable/disable Configuration Locked
Reset to the default configuration.
open-zwave-1.5/config/aeotec/doorwindow.xml 0000664 0000000 0000000 00000004261 12644742024 0021104 0 ustar 00root root 0000000 0000000
Default setting: Open: FF, Close: 00
Default setting: Disable
Default setting: Open: FF, Close: 00
Which reports need to send automatically in timing intervals for group 1. Bitsets: 0->Battery report, 4->Sensor Binary, 8->Basic Set, Default setting: 0x00000100 (Basic Set)
Ideal Setting for OZW is 17 (Sensor Binary and Battery Report)
Device Tag
Reset to factory defaults.
open-zwave-1.5/config/aeotec/drycontactsensor.xml 0000664 0000000 0000000 00000005642 12644742024 0022321 0 ustar 00root root 0000000 0000000
Which value of the Sensor Binary Report will be sent when
the Sensor is triggered On.
Enable/disable wake up 10 minutes when re-power on the
Sensor.
Which value of the Basic Report will be sent when
the Sensor is triggered On.
Set the low battery value.
Set the interval time of battery report.
Value=0, disable the battery report for a interval time.
Value=1 to 0x7FFFFFFF, the interval time of battery report is
set.
Note:
1, if the value is less than 10, the time unit is second.
If the value is more than 10, the time unit is 4 minutes, which
means if the value is more than 10 and less than 240, the
interval time is 4 minutes. If the value is more than 240 and
less than 480, the interval is 8 minutes.
2, if the current battery report falls below the low battery
value (configurable parameter 39), it will send battery
report=0xFF.
Defines the type of report sent.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 bits 7-1 reserved
bits 0 - Basic Report
Value 4 (lsb) bits 7-4 reserved
bit 3 Sensor Binary
bit 2-0 reserved
Reset to the default configuration.
open-zwave-1.5/config/aeotec/dsd31.xml 0000664 0000000 0000000 00000005000 12644742024 0017617 0 ustar 00root root 0000000 0000000
Select the Siren Sound and Volume
Enable to send notifications to associated devices (Group 1) when the state of Siren changed
Partner ID
Enable/disable Lock Configuration
Reset to the default configuration.
open-zwave-1.5/config/aeotec/hdss_gen5.xml 0000664 0000000 0000000 00000014314 12644742024 0020570 0 ustar 00root root 0000000 0000000
Current Overload Protection. Load will be closed when
the Current more than 39.5A and the time more than 5
seconds
LED status after power on
Enables automatic notifications to associated devices whenever there is a state change.
Enable/disable Wattage threshold and percent.
The minimum change in wattage for a report to be sent.
Minimum change in percent of wattage to send a report.
Set report types for groups 1, 2 and 3 to default. Reverts to 0
after set.
Defines the type of report sent for reporting group 1. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb) bits 7-4 reserved
bit 3 MRC (KWH)
bit 2 MRC (watt)
bit 1 MSRC (Current)
bit 0 MRC (Voltage)
The MRC(KWH) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(KWh) automatically.
The MRC(Watt) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(wattage) automatically.
The MSRC flag signals that Report Group 1 send(1) or don't send(0)
Multilevel Sensor Report Command(wattage) automatically.
Defines the type of report sent for reporting group 2. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb) bits 7-4 reserved
bit 3 MRC (KWH)
bit 2 MRC (watt)
bit 1 MSRC (Current)
bit 0 MRC (Voltage)
The MRC(KWH) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(KWh) automatically.
The MRC(Watt) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(wattage) automatically.
The MSRC flag signals that Report Group 1 send(1) or don't send(0)
Multilevel Sensor Report Command(wattage) automatically.
Defines the type of report sent for reporting group 3. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb) bits 7-4 reserved
bit 3 MRC (KWH)
bit 2 MRC (watt)
bit 1 MSRC (Current)
bit 0 MRC (Voltage)
The MRC(KWH) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(KWh) automatically.
The MRC(Watt) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(wattage) automatically.
The MSRC flag signals that Report Group 1 send(1) or don't send(0)
Multilevel Sensor Report Command(wattage) automatically.
Set time interval for sending reports for groups 1, 2 and 3 to default.
Defines the time interval when the defined report for group 1 is sent.
Defines the time interval when the defined report for group 2 is sent.
Defines the time interval when the defined report for group 3 is sent.
Lock/ unlock all configuration parameters
Reset to the default configuration.
open-zwave-1.5/config/aeotec/hem.xml 0000664 0000000 0000000 00000021453 12644742024 0017464 0 ustar 00root root 0000000 0000000
Voltage to calculate wattage from amperage. US=120. EU,ANZ=240.
Automatic report only when power is changed.
Threshold change in wattage to induce a automatic report (whole HEM).
Threshold change in wattage to induce a automatic report (Clamp 1).
Threshold change in wattage to induce a automatic report (Clamp 2).
Threshold change in wattage to induce a automatic report (Clamp 3).
Percentage change in wattage to induce a automatic report (whole HEM).
Percentage change in wattage to induce a automatic report (Clamp 1).
Percentage change in wattage to induce a automatic report (Clamp 2).
Percentage change in wattage to induce a automatic report (Clamp 3).
Accumulate energy when Battery Powered.
This byte denotes whether the product is using batteries (value = 0) or using USB power (value = 1).
Reset to default parameters number 101-103. Any value other then 0 will initiate this reset.
Which reports need to send in group1. Format is as follows:
Byte 1 (msb): Reserved
Byte 2: Reserved
Byte 3: Bit 7: reserved
Bit 6: reserved
Bit 5: Auto Send Meter Report (for kWh) at the group time interval (Clamp 3)
Bit 4: Auto Send Meter Report (for kWh) at the group time interval (Clamp 2)
Bit 3: Auto Send Meter Report (for kWh) at the group time interval (Clamp 1)
Bit 2: Auto Send Meter Report (for watts) at the group time interval (Clamp 3)
Bit 1: Auto Send Meter Report (for watts) at the group time interval (Clamp 2)
Bit 0: Auto Send Meter Report (for watts) at the group time interval (Clamp 1)
Byte 4 (lsb): Bit 7: reserved
Bit 6: reserved
Bit 5: reserved
Bit 4: reserved
Bit 3: Auto Send Meter Report (for kWh) at the group time interval (whole HEM)
Bit 2: Auto Send Meter Report (for watts) at the group time interval (whole HEM)
Bit 1: Auto Send Multilevel Sensor Report (for watts) at the group time interval (whole HEM)
Bit 0: Auto Send Battery Report at the group time interval (whole HEM)
Which reports need to send in group2. Format is as follows:
Byte 1 (msb): Reserved
Byte 2: Reserved
Byte 3: Bit 7: reserved
Bit 6: reserved
Bit 5: Auto Send Meter Report (for kWh) at the group time interval (Clamp 3)
Bit 4: Auto Send Meter Report (for kWh) at the group time interval (Clamp 2)
Bit 3: Auto Send Meter Report (for kWh) at the group time interval (Clamp 1)
Bit 2: Auto Send Meter Report (for watts) at the group time interval (Clamp 3)
Bit 1: Auto Send Meter Report (for watts) at the group time interval (Clamp 2)
Bit 0: Auto Send Meter Report (for watts) at the group time interval (Clamp 1)
Byte 4 (lsb): Bit 7: reserved
Bit 6: reserved
Bit 5: reserved
Bit 4: reserved
Bit 3: Auto Send Meter Report (for kWh) at the group time interval (whole HEM)
Bit 2: Auto Send Meter Report (for watts) at the group time interval (whole HEM)
Bit 1: Auto Send Multilevel Sensor Report (for watts) at the group time interval (whole HEM)
Bit 0: Auto Send Battery Report at the group time interval (whole HEM)
Which reports need to send in group3. Format is as follows:
Byte 1 (msb): Reserved
Byte 2: Reserved
Byte 3: Bit 7: reserved
Bit 6: reserved
Bit 5: Auto Send Meter Report (for kWh) at the group time interval (Clamp 3)
Bit 4: Auto Send Meter Report (for kWh) at the group time interval (Clamp 2)
Bit 3: Auto Send Meter Report (for kWh) at the group time interval (Clamp 1)
Bit 2: Auto Send Meter Report (for watts) at the group time interval (Clamp 3)
Bit 1: Auto Send Meter Report (for watts) at the group time interval (Clamp 2)
Bit 0: Auto Send Meter Report (for watts) at the group time interval (Clamp 1)
Byte 4 (lsb): Bit 7: reserved
Bit 6: reserved
Bit 5: reserved
Bit 4: reserved
Bit 3: Auto Send Meter Report (for kWh) at the group time interval (whole HEM)
Bit 2: Auto Send Meter Report (for watts) at the group time interval (whole HEM)
Bit 1: Auto Send Multilevel Sensor Report (for watts) at the group time interval (whole HEM)
Bit 0: Auto Send Battery Report at the group time interval (whole HEM)
Reset to default parameters number 111-113. Any value other then 0 will initiate this reset.
The interval of sending report group 1.
The interval of sending report group 2.
The interval of sending report group 3.
Re-calibrate (will destroy factory calibration). CONTACT AEON LABS before using.
Device tag.
Reset to the default configuration.
open-zwave-1.5/config/aeotec/hemg2.xml 0000664 0000000 0000000 00000020422 12644742024 0017710 0 ustar 00root root 0000000 0000000
If the reverse clamping pliers, negative power is detected.
Automatic report only when power is changed.
Threshold change in wattage to induce a automatic report (whole HEM).
Threshold change in wattage to induce a automatic report (Clamp 1).
Threshold change in wattage to induce a automatic report (Clamp 2).
Threshold change in wattage to induce a automatic report (Clamp 3).
Percentage change in wattage to induce a automatic report (whole HEM).
Percentage change in wattage to induce a automatic report (Clamp 1).
Percentage change in wattage to induce a automatic report (Clamp 2).
Percentage change in wattage to induce a automatic report (Clamp 3).
Reset to default parameters number 101-103. Any value other then 0 will initiate this reset.
Which reports need to send in group1. Format is as follows:
Byte 1 (msb): Reserved
Byte 2: Reserved
Byte 3: Bit 7: reserved
Bit 6: reserved
Bit 5: Auto Send Meter Report (for kWh) at the group time interval (Clamp 3)
Bit 4: Auto Send Meter Report (for kWh) at the group time interval (Clamp 2)
Bit 3: Auto Send Meter Report (for kWh) at the group time interval (Clamp 1)
Bit 2: Auto Send Meter Report (for watts) at the group time interval (Clamp 3)
Bit 1: Auto Send Meter Report (for watts) at the group time interval (Clamp 2)
Bit 0: Auto Send Meter Report (for watts) at the group time interval (Clamp 1)
Byte 4 (lsb): Bit 7: reserved
Bit 6: reserved
Bit 5: reserved
Bit 4: reserved
Bit 3: Auto Send Meter Report (for kWh) at the group time interval (whole HEM)
Bit 2: Auto Send Meter Report (for watts) at the group time interval (whole HEM)
Bit 1: Auto Send Multilevel Sensor Report (for watts) at the group time interval (whole HEM)
Bit 0: Auto Send Battery Report at the group time interval (whole HEM)
Which reports need to send in group2. Format is as follows:
Byte 1 (msb): Reserved
Byte 2: Reserved
Byte 3: Bit 7: reserved
Bit 6: reserved
Bit 5: Auto Send Meter Report (for kWh) at the group time interval (Clamp 3)
Bit 4: Auto Send Meter Report (for kWh) at the group time interval (Clamp 2)
Bit 3: Auto Send Meter Report (for kWh) at the group time interval (Clamp 1)
Bit 2: Auto Send Meter Report (for watts) at the group time interval (Clamp 3)
Bit 1: Auto Send Meter Report (for watts) at the group time interval (Clamp 2)
Bit 0: Auto Send Meter Report (for watts) at the group time interval (Clamp 1)
Byte 4 (lsb): Bit 7: reserved
Bit 6: reserved
Bit 5: reserved
Bit 4: reserved
Bit 3: Auto Send Meter Report (for kWh) at the group time interval (whole HEM)
Bit 2: Auto Send Meter Report (for watts) at the group time interval (whole HEM)
Bit 1: Auto Send Multilevel Sensor Report (for watts) at the group time interval (whole HEM)
Bit 0: Auto Send Battery Report at the group time interval (whole HEM)
Which reports need to send in group3. Format is as follows:
Byte 1 (msb): Reserved
Byte 2: Reserved
Byte 3: Bit 7: reserved
Bit 6: reserved
Bit 5: Auto Send Meter Report (for kWh) at the group time interval (Clamp 3)
Bit 4: Auto Send Meter Report (for kWh) at the group time interval (Clamp 2)
Bit 3: Auto Send Meter Report (for kWh) at the group time interval (Clamp 1)
Bit 2: Auto Send Meter Report (for watts) at the group time interval (Clamp 3)
Bit 1: Auto Send Meter Report (for watts) at the group time interval (Clamp 2)
Bit 0: Auto Send Meter Report (for watts) at the group time interval (Clamp 1)
Byte 4 (lsb): Bit 7: reserved
Bit 6: reserved
Bit 5: reserved
Bit 4: reserved
Bit 3: Auto Send Meter Report (for kWh) at the group time interval (whole HEM)
Bit 2: Auto Send Meter Report (for watts) at the group time interval (whole HEM)
Bit 1: Auto Send Multilevel Sensor Report (for watts) at the group time interval (whole HEM)
Bit 0: Auto Send Battery Report at the group time interval (whole HEM)
Reset to default parameters number 111-113. Any value other then 0 will initiate this reset.
The interval of sending report group 1.
The interval of sending report group 2.
The interval of sending report group 3.
Device tag.
Reset to the default configuration.
open-zwave-1.5/config/aeotec/keyfob.xml 0000664 0000000 0000000 00000013521 12644742024 0020167 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/aeotec/keyfob2.xml 0000664 0000000 0000000 00000002263 12644742024 0020252 0 ustar 00root root 0000000 0000000
Enable selective Group Mode or Scene Mode when the Key Fob is in Use mode
Reset configuration set up to default setting
open-zwave-1.5/config/aeotec/ledbulb.xml 0000664 0000000 0000000 00000006327 12644742024 0020327 0 ustar 00root root 0000000 0000000
Enable/disable to send out a report when the color is changed
Enable/disable the function of using External Switch to turn on/off the bulb
Enable/disable the function of using External Switch to changes the bulb color
Reboot/save/exit Colorful mode
Colorful mode configuration (See table)
Color index configuration when the bulb is in Multi color mode (See table)
Enable to send notifications to associated devices (Lifeline) when the state of LED Bulb is changed
Lock/ unlock all configuration parameters
Reset to the default configuration
open-zwave-1.5/config/aeotec/minimote.xml 0000664 0000000 0000000 00000010522 12644742024 0020527 0 ustar 00root root 0000000 0000000
Default Mode – The button on the Minimote uses the factory default functions for operation instead of any special functionality related to the below modes. Scene Mode – The button on the Minimote executes a scene from data received for Parameters Numbers 0-239 related to the button being pressed. Add Mode – The button on the Minimote is able to include/add devices into the Z-Wave network. Remove Mode – The button on the Minimote is able to remove devices from the Z-Wave network. Association Mode – The button on the Minimote is able to associate one device to another. Learn Mode – The button on the Minimote is able to allow the Minimote to be included into other Z-Wave networks and to learn Z-Wave network information.
Enable selective Group Mode or Scene Mode when Button is in Use.
NOTE: Minimote firmware 1.17 or higher is required, firmware 1.19 is highly recommended.
open-zwave-1.5/config/aeotec/msesv2.xml 0000664 0000000 0000000 00000016000 12644742024 0020122 0 ustar 00root root 0000000 0000000
This is actually a double byte value. The LSB defines the total time the device needs to blink in seconds. The MSB defines the on/off interval of the blink in tenths of seconds.
Current Overload Protection. Load will be closed when 3
the Current more than 2.7A and the time more than 2
minutes
Enables automatic notifications to associated devices whenever there is a state change.
Enable/disable Wattage threshold and percent.
The minimum change in wattage for a report to be sent.
Minimum change in percent of wattage to send a report.
Set report types for groups 1, 2 and 3 to default. Reverts to 0
after set.
Defines the type of report sent for reporting group 1. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb) bits 7-4 reserved
bit 3 MRC (KWH)
bit 2 MRC (watt)
bit 1 MSRC (Current)
bit 0 MRC (Voltage)
The MRC(KWH) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(KWh) automatically.
The MRC(Watt) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(wattage) automatically.
The MSRC flag signals that Report Group 1 send(1) or don't send(0)
Multilevel Sensor Report Command(wattage) automatically.
Defines the type of report sent for reporting group 2. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb) bits 7-4 reserved
bit 3 MRC (KWH)
bit 2 MRC (watt)
bit 1 MSRC (Current)
bit 0 MRC (Voltage)
The MRC(KWH) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(KWh) automatically.
The MRC(Watt) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(wattage) automatically.
The MSRC flag signals that Report Group 1 send(1) or don't send(0)
Multilevel Sensor Report Command(wattage) automatically.
Defines the type of report sent for reporting group 3. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb) bits 7-4 reserved
bit 3 MRC (KWH)
bit 2 MRC (watt)
bit 1 MSRC (Current)
bit 0 MRC (Voltage)
The MRC(KWH) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(KWh) automatically.
The MRC(Watt) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(wattage) automatically.
The MSRC flag signals that Report Group 1 send(1) or don't send(0)
Multilevel Sensor Report Command(wattage) automatically.
Set time interval for sending reports for groups 1, 2 and 3 to default.
Defines the time interval when the defined report for group 1 is sent.
Defines the time interval when the defined report for group 2 is sent.
Defines the time interval when the defined report for group 3 is sent.
Turn external button mode
Device tag.
Reset to the default configuration.
open-zwave-1.5/config/aeotec/multisensor6.xml 0000664 0000000 0000000 00000020345 12644742024 0021364 0 ustar 00root root 0000000 0000000
Stay awake for 10 minutes after batteries are inserted
How long should the device associated to multi sensor keep state On before sending it Off command (if the value is bigger than 255, the value would be rounded to next integer in minutes)
Enable Motion Sensor
Which commands to send when PIR motion sensor triggered
OZW Ideal Value is Binary Sensor Report
Configure low battery value
Value=10 to 50.
Enable/disable the selective reporting only when measurements reach a certain threshold or percentage
set in the threshold settings. This is used to reduce network
traffic.
Threshold change in temperature to induce an automatic report.
Note:
1. When the unit is Celsius, threshold=Value.
2. When the unit is Fahrenheit, threshold=Value*1.8. The accuracy is 0.1.
3. The high byte is the part of integer, the low byte is the fractional part.
Threshold change in humidity to induce an automatic report.
Note:
The accuracy is 0.1.
The high byte is the part of integer, the low byte is the fractional part.
Threshold change in luminance to induce an automatic report.
Threshold change in battery level to induce an automatic report.
Note:
The accuracy is 0.1.
The high byte is the part of integer, the low byte is the fractional part.
Threshold change in ultraviolet to induce an automatic report.
Enable/disable to send the alarm report of low temperature(Less than 15 Degress C)
Reset The Reporting Group Configuration (101 to 103) to default
Which reports need to send automatically in timing intervals for group 1. Bitsets: 0 -> Battery report, 4 -> Ultraviolet, 5 -> Temperature, 6 -> Humidity, 7 -> Luminosity
Which reports need to send automatically in timing intervals for group 2. Bitsets: 0 -> Battery report, 4 -> Ultraviolet, 5 -> Temperature, 6 -> Humidity, 7 -> Luminosity
Which reports need to send automatically in timing intervals for group 3. Bitsets: 0 -> Battery report, 4 -> Ultraviolet, 5 -> Temperature, 6 -> Humidity, 7 -> Luminosity
Reset The Reporting Group Interval Configuration (111 to 113) to default
The interval of sending report group 1. 1 to 2678400 seconds
The interval of sending report group 2. 1 to 2678400 seconds
The interval of sending report group 3. 1 to 2678400 seconds
The calibration value = standard value ‐ measure value.
E.g. If measure value =25.3°C and the standard value = 23.2°C, so the calibration value= 23.2°C ‐ 25.3°C= ‐2.1°C (0xFFEB).
If the measure value =30.1°C and the standard value = 33.2°C, so the calibration value= 33.2°C ‐ 30.1°C=3.1°C (0x001F).
The calibration value = standard value ‐ measure value.
E.g. If measure value =80RH and the standard value = 75RH, so the calibration value= 75RH – 80RH= ‐5RH (0xFFFB).
If the measure value =85RH and the standard value = 90RH, so the calibration value= 90RH – 85RH=5RH (0x0005).
The calibration value = standard value ‐ measure value.
E.g. If measure value =800Lux and the standard value = 750Lux, so the calibration value= 750 – 800= ‐50 (0xFFCE).
If the measure value =850Lux and the standard value = 900Lux, so the calibration value= 900 – 850=50 (0x0032).
The calibration value = standard value ‐ measure value.
E.g. If measure value =9 and the standard value = 8, so the calibration value= 8 – 9= ‐1 (0xFE).
If the measure value =7 and the standard value = 9, so the calibration value= 9 – 7=2 (0x02).
Enable/disable Lock Configuration
Reset to factory defaults.
open-zwave-1.5/config/aeotec/multisensor_gen5.xml 0000664 0000000 0000000 00000012765 12644742024 0022223 0 ustar 00root root 0000000 0000000
Stay awake for 10 minutes after batteries are inserted
How long should the device associated to multi sensor keep state On before sending it Off command (if the value is bigger than 255, the value would be rounded to next integer in minutes)
Enable Motion Sensor
Which commands to send when PIR motion sensor triggered
OZW Ideal Value is Binary Sensor Report
Enable/disable the selective reporting only when measurements reach a certain threshold or percentage
set in the threshold settings. This is used to reduce network
traffic.
Threshold change in temperature to induce an automatic report.
Note:
1. When the unit is Celsius, threshold=Value.
2. When the unit is Fahrenheit, threshold=Value*1.8. The accuracy is 0.1.
3. The high byte is the part of integer, the low byte is the fractional part.
Threshold change in humidity to induce an automatic report.
Note:
The accuracy is 0.1.
The high byte is the part of integer, the low byte is the fractional part.
Threshold change in luminance to induce an automatic report.
Threshold change in battery level to induce an automatic report.
Note:
The accuracy is 0.1.
The high byte is the part of integer, the low byte is the fractional part.
Enable/disable to send the alarm report of low temperature(Less than 15 Degress C)
Which reports need to send automatically in timing intervals for group 1. Bitsets: 0 -> Battery report, 5 -> Temperature, 6 -> Humidity, 7 -> Luminosity
Which reports need to send automatically in timing intervals for group 2. Bitsets: 0 -> Battery report, 5 -> Temperature, 6 -> Humidity, 7 -> Luminosity
Which reports need to send automatically in timing intervals for group 3. Bitsets: 0 -> Battery report, 5 -> Temperature, 6 -> Humidity, 7 -> Luminosity
The interval of sending report group 1. 1 to 2678400 seconds
The interval of sending report group 2. 1 to 2678400 seconds
The interval of sending report group 3. 1 to 2678400 seconds
Enable/disable Lock Configuration
Reset to factory defaults.
open-zwave-1.5/config/aeotec/panicbtn.xml 0000664 0000000 0000000 00000002275 12644742024 0020512 0 ustar 00root root 0000000 0000000
Enable selective Group Mode or Scene Mode when the Panic Button is in Use mode
Reset configuration set up to default setting
open-zwave-1.5/config/aeotec/recessed_doorsensor.xml 0000664 0000000 0000000 00000006403 12644742024 0022763 0 ustar 00root root 0000000 0000000
0, Open: FF, Close: 00; 1, Open: 00, Close: FF;
Default setting: 0
0, Open: FF, Close: 00; 1, Open: 00, Close: FF;
Default setting: 0
0, Disable, 1, Enable;
Default setting: 0
This parameter is available when the low battery checking
function is activated or the device was waked up by other
actions (i.e. the z-wave button trigger, magnet switch
trigger and the Wake Up Interval Set timeout trigger).
The Recessed Door Sensor will check the battery power
when it was wake up as other ways. For example: the
z-wave button trigger, magnet switch trigger and the
Wake Up Interval Set timeout trigger.
Default setting: 86640
Bitsets:
4 -> Sensor Binary
8 -> Basic Set
Default setting: 0x00000100 (Basic Set)
Device Tag
Reset to factory defaults.
open-zwave-1.5/config/aeotec/recessed_doorsensor_gen5.xml 0000664 0000000 0000000 00000007031 12644742024 0023677 0 ustar 00root root 0000000 0000000
Which value of the Sensor Binary Report will be sent when
the magnet switch to open/close.
Which value of the Basic Set will be sent when the magnet
switch to open/close.
Enable/disable the function of low battery checking, when
the current voltage is less than the warning voltage, it will
send the Battery Low Warning Report.
This parameter is available when the low battery checking
function is activated or the device was waked up by other
actions (i.e. the z-wave button trigger, magnet switch
trigger and the Wake Up Interval Set timeout trigger).
The Recessed Door Sensor will check the battery power
when it was wake up as other ways. For example: the
z-wave button trigger, magnet switch trigger and the
Wake Up Interval Set timeout trigger.
Default setting: 86640
To set which command will be sent to the associated nodes
when the magnet switch is triggered.
Bitsets:
4 -> Sensor Binary
8 -> Basic Set
Default setting: 0x100 (Basic Set)
OZW Ideal Setting: 0x10 (Sensor Binary Report)
Lock/ unlock all configuration parameters
Device Tag
Reset to factory defaults.
open-zwave-1.5/config/aeotec/sd6.xml 0000664 0000000 0000000 00000017500 12644742024 0017405 0 ustar 00root root 0000000 0000000
Load will be closed when the Current overruns (US 15.5A, Others 16.2) for more than 2 minutes
Configure the output load status after re-power on.
Defines the automated status notification of an associated device when status changes
Configure what the LED Ring displays during operations
Configure the RGB Value when in Night Light Mode.
Byte 1: Red Color
Byte 2: Green Color
Byte 3: Blue Color
Configure the brightness level of RGB LED (0%-100%) when it is in Energy Mode/momentary indicate mode.
Byte 1: Red Color
Byte 2: Green Color
Byte 3: Blue Color
Enable/disable Wattage threshold and percent.
The value represents the minimum change in wattage for a Report to be sent (default 25 W)
The value represents the minimum percentage change in wattage for a Report to be sent (Default 5)
Set report types for groups 1, 2 and 3 to default.
Defines the type of report sent for reporting group 1. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb)
bits 7-4 reserved
bit 3 KWH
bit 2 Watt
bit 1 Current
bit 0 Voltage
Defines the type of report sent for reporting group 1. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb)
bits 7-4 reserved
bit 3 KWH
bit 2 Watt
bit 1 Current
bit 0 Voltage
Defines the type of report sent for reporting group 1. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb)
bits 7-4 reserved
bit 3 KWH
bit 2 Watt
bit 1 Current
bit 0 Voltage
Set time interval for sending reports for groups 1, 2 and 3 to default.
Defines the time interval when the defined report for group 1 is sent.
Defines the time interval when the defined report for group 2 is sent.
Defines the time interval when the defined report for group 3 is sent.
Partner ID
Enable/disable Configuration Locked
Device tag.
Reset to the default configuration.
open-zwave-1.5/config/aeotec/ses.xml 0000664 0000000 0000000 00000013712 12644742024 0017504 0 ustar 00root root 0000000 0000000
Defines the contents of Multilevel Sensor Report after Multilevel Sensor Get received.
This is actually a double byte value. The LSB defines the total time the device needs to blink in seconds. The MSB defines the on/off interval of the blink in tenths of seconds.
Enables automatic notifications to associated devices whenever there is a state change.
Enable/disable Wattage threshold and percent.
The minimum change in wattage for a report to be sent.
Minimum change in percent of wattage to send a report.
Set report types for groups 1, 2 and 3 to default. Reverts to 0
after set.
Defines the type of report sent for reporting group 1. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb) bits 7-4 reserved
bit 3 MRC(KWH)
bit 2 MRC(watt)
bit 1 MSRC
bit 0 reserved
The MRC(KWH) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(KWh) automatically.
The MRC(Watt) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(wattage) automatically.
The MSRC flag signals that Report Group 1 send(1) or don't send(0)
Multilevel Sensor Report Command(wattage) automatically.
Defines the type of report sent for reporting group 2. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb) bits 7-4 reserved
bit 3 MRC(KWH)
bit 2 MRC(watt)
bit 1 MSRC
bit 0 reserved
The MRC(KWH) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(KWh) automatically.
The MRC(Watt) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(wattage) automatically.
The MSRC flag signals that Report Group 1 send(1) or don't send(0)
Multilevel Sensor Report Command(wattage) automatically.
Defines the type of report sent for reporting group 3. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb) bits 7-4 reserved
bit 3 MRC(KWH)
bit 2 MRC(watt)
bit 1 MSRC
bit 0 reserved
The MRC(KWH) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(KWh) automatically.
The MRC(Watt) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(wattage) automatically.
The MSRC flag signals that Report Group 1 send(1) or don't send(0)
Multilevel Sensor Report Command(wattage) automatically.
Set time interval for sending reports for groups 1, 2 and 3 to default.
Defines the time interval when the defined report for group 1 is sent.
Defines the time interval when the defined report for group 2 is sent.
Defines the time interval when the defined report for group 3 is sent.
Device tag.
Reset to the default configuration.
open-zwave-1.5/config/aeotec/ses2.xml 0000664 0000000 0000000 00000017470 12644742024 0017573 0 ustar 00root root 0000000 0000000
Configuration Value 1: 1‐255
Configuration Value 1 is to Specify the time that Smart Switch need blink, The unit is Second;
Configuration Value 2: 1‐255
Configuration Value 2 is to Specify the Cycle of on/off, the unit of it is 0.1 second.
Load will be closed when the Current overruns (EU 16.2A) for more than 2 minutes
Configure the output load status after re-power on.
Defines the automated status notification of an associated device when status changes
Enable/disable Wattage threshold and percent.
The value represents the minimum change in wattage for a Report to be sent (default 25 W)
The value represents the minimum percentage change in wattage for a Report to be sent (Default 5)
Set report types for groups 1, 2 and 3 to default.
Defines the type of report sent for reporting group 1. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb) bits 7-4 reserved
bit 3 MRC(KWH)
bit 2 MRC(watt)
bit 1 MSRC
bit 0 reserved
The MRC(KWH) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(KWh) automatically.
The MRC(Watt) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(wattage) automatically.
The MSRC flag signals that Report Group 1 send(1) or don't send(0)
Multilevel Sensor Report Command(wattage) automatically.
Defines the type of report sent for reporting group 2. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb) bits 7-4 reserved
bit 3 MRC(KWH)
bit 2 MRC(watt)
bit 1 MSRC
bit 0 reserved
The MRC(KWH) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(KWh) automatically.
The MRC(Watt) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(wattage) automatically.
The MSRC flag signals that Report Group 1 send(1) or don't send(0)
Multilevel Sensor Report Command(wattage) automatically.
Defines the type of report sent for reporting group 3. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb) bits 7-4 reserved
bit 3 MRC(KWH)
bit 2 MRC(watt)
bit 1 MSRC
bit 0 reserved
The MRC(KWH) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(KWh) automatically.
The MRC(Watt) flag signals that Report Group 1 send(1) or don't send(0)
Meter Report Command(wattage) automatically.
The MSRC flag signals that Report Group 1 send(1) or don't send(0)
Multilevel Sensor Report Command(wattage) automatically.
Set time interval for sending reports for groups 1, 2 and 3 to default.
Defines the time interval when the defined report for group 1 is sent.
Defines the time interval when the defined report for group 2 is sent.
Defines the time interval when the defined report for group 3 is sent.
Partner ID
Enable/disable Configuration Locked
Device tag.
Reset to the default configuration.
open-zwave-1.5/config/aeotec/ss6.xml 0000664 0000000 0000000 00000016337 12644742024 0017433 0 ustar 00root root 0000000 0000000
Load will be closed when the Current overruns (US 15.5A, Others 16.2) for more than 2 minutes
Configure the output load status after re-power on.
Configure the RGB Led Color for Testing
Defines the automated status notification of an associated device when status changes
Configure the RGB Value when in Night Light Mode.
Byte 1: Red Color
Byte 2: Green Color
Byte 3: Blue Color
Configure the brightness level of RGB LED (0%-100%) when it is in Energy Mode/momentary indicate mode.
Byte 1: Red Color
Byte 2: Green Color
Byte 3: Blue Color
Enable/disable Wattage threshold and percent.
The value represents the minimum change in wattage for a Report to be sent (default 25 W)
The value represents the minimum percentage change in wattage for a Report to be sent (Default 5)
Set report types for groups 1, 2 and 3 to default.
Defines the type of report sent for reporting group 1. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb) bits 7-4 reserved
bit 3 KWH
bit 2 Watt
bit 1 Current
bit 0 Voltage
Defines the type of report sent for reporting group 1. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb) bits 7-4 reserved
bit 3 KWH
bit 2 Watt
bit 1 Current
bit 0 Voltage
Defines the type of report sent for reporting group 1. 2 is multisensor report. 4 is meter report for watts. 8 is meter report for kilowatts.
Value 1 (msb) Reserved
Value 2 Reserved
Value 3 Reserved
Value 4 (lsb) bits 7-4 reserved
bit 3 KWH
bit 2 Watt
bit 1 Current
bit 0 Voltage
Set time interval for sending reports for groups 1, 2 and 3 to default.
Defines the time interval when the defined report for group 1 is sent.
Defines the time interval when the defined report for group 2 is sent.
Defines the time interval when the defined report for group 3 is sent.
Partner ID
Enable/disable Configuration Locked
Device tag.
Reset to the default configuration.
open-zwave-1.5/config/aeotec/watersensor.xml 0000664 0000000 0000000 00000003773 12644742024 0021274 0 ustar 00root root 0000000 0000000
Toggle the sensor binary report value when the Water Sensor is Triggered
Enable wake up 10 minutes when the power is switched on.
Toggle the basic set value when the Water Sensor is Triggered
To set which command will be sent to the associated nodes when the Water Sensor is triggered.
Bitsets:
1 -> Battery
4 -> Sensor Binary
8 -> Basic Set
12 -> Alarm
Default setting: 0x100 (Basic Set)
OZW Ideal Setting: 0x1011 (Battery, Sensor Binary Report, Alarm)
Reset to factory defaults.
open-zwave-1.5/config/aeotec/zstickgen5.xml 0000664 0000000 0000000 00000003556 12644742024 0021005 0 ustar 00root root 0000000 0000000
When the USB power supply, the LED indicator light configuration
1~10, other= ignore.
A total of 10 levels, level 1 as the weak output power, and so on, 10 for most output power level
Lock/ unlock all configuration parameters
Reset to the default configuration
open-zwave-1.5/config/assa_abloy/ 0000775 0000000 0000000 00000000000 12644742024 0017041 5 ustar 00root root 0000000 0000000 open-zwave-1.5/config/assa_abloy/RealLivingCapTouch.xml 0000664 0000000 0000000 00000001033 12644742024 0023243 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/cooper/ 0000775 0000000 0000000 00000000000 12644742024 0016213 5 ustar 00root root 0000000 0000000 open-zwave-1.5/config/cooper/RF9505-T.xml 0000664 0000000 0000000 00000004466 12644742024 0020002 0 ustar 00root root 0000000 0000000
The amount of time in seconds the switch will turn on for when panic mode is trigered. The configuration value is a signed single byte number. This value may represent a value with no units or may represent a value such as time. 0 to 127 (decimal) represents 0 to 127 seconds of time. -128 to -1 (negative decimal numbers) represents 128 to 255 seconds as calculated by this formula. Config value = desired time in seconds (or desired value) -256 For an example of 172 seconds: config value = 172 - 256 = -84 (decimal) or 0xAC (hex)
The amount of time in seconds the switch will turn off for when panic mode is triggered. The configuration value is a signed single byte number. This value may represent a value with no units or may represent a value such as time. 0 to 127 (decimal) represents 0 to 127 seconds of time. -128 to -1 (negative decimal numbers) represents 128 to 255 seconds as calculated by this formula. Config value = desired time in seconds (or desired value) -256 For an example of 172 seconds: config value = 172 - 256 = -84 (decimal) or 0xAC (hex)
Power up state of the device
Enables this device to participate in panic mode
open-zwave-1.5/config/cooper/RF9540-N.xml 0000664 0000000 0000000 00000011575 12644742024 0017772 0 ustar 00root root 0000000 0000000
The configuration value is a signed single byte number. This value may represent a value with no units or may represent a value such as time. 0 to 127 (decimal) represents 0 to 127 seconds of time. -128 to -1 (negative decimal numbers) represents 128 to 255 seconds as calculated by this formula. Config value = desired time in seconds (or desired value) -256 For an example of 172 seconds: config value = 172 - 256 = -84 (decimal) or 0xAC (hex)
The amount of time in seconds the switch will turn on for when panic mode is trigered. The configuration value is a signed single byte number. This value may represent a value with no units or may represent a value such as time. 0 to 127 (decimal) represents 0 to 127 seconds of time. -128 to -1 (negative decimal numbers) represents 128 to 255 seconds as calculated by this formula. Config value = desired time in seconds (or desired value) -256 For an example of 172 seconds: config value = 172 - 256 = -84 (decimal) or 0xAC (hex)
The amount of time in seconds the switch will turn off for when panic mode is triggered. The configuration value is a signed single byte number. This value may represent a value with no units or may represent a value such as time. 0 to 127 (decimal) represents 0 to 127 seconds of time. -128 to -1 (negative decimal numbers) represents 128 to 255 seconds as calculated by this formula. Config value = desired time in seconds (or desired value) -256 For an example of 172 seconds: config value = 172 - 256 = -84 (decimal) or 0xAC (hex)
Setting this to anything other than 0 will cause the value to be transmitted to devices in the association group when the switch is triggered. A setting other than 0 will likely result in undesired operation
Power up state of the device
Enables this switch to participate in panic mode
The amount of time in seconds the switch will take to reach the desired dim level. The configuration value is a signed single byte number. This value may represent a value with no units or may represent a value such as time. 0 to 127 (decimal) represents 0 to 127 seconds of time. -128 to -1 (negative decimal numbers) represents 128 to 255 seconds as calculated by this formula. Config value = desired time in seconds (or desired value) -256 For an example of 172 seconds: config value = 172 - 256 = -84 (decimal) or 0xAC (hex)
Ensures that LED / CFL bulbs turn on when the preset dim level is low. Enabling this feature may cause the lights brightness to momentarily be bright when the switch is turned on before reducing in brightness to desired level
The minimum dim level the switch will allow. The minimum level must always be at least 13 below the maximum level.
The maximum dim level the switch will allow. The maximum level must always be at least 13 above the minimum level.
open-zwave-1.5/config/danfoss/ 0000775 0000000 0000000 00000000000 12644742024 0016361 5 ustar 00root root 0000000 0000000 open-zwave-1.5/config/danfoss/living.xml 0000664 0000000 0000000 00000000352 12644742024 0020373 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/danfoss/z.xml 0000664 0000000 0000000 00000000512 12644742024 0017352 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/device_classes.xml 0000664 0000000 0000000 00000046007 12644742024 0020431 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/device_classes.xsd 0000664 0000000 0000000 00000005437 12644742024 0020431 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/device_configuration.xsd 0000664 0000000 0000000 00000025643 12644742024 0021644 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/dlink/ 0000775 0000000 0000000 00000000000 12644742024 0016025 5 ustar 00root root 0000000 0000000 open-zwave-1.5/config/dlink/dch-z110.xml 0000664 0000000 0000000 00000015670 12644742024 0020007 0 ustar 00root root 0000000 0000000
Setting the BASIC command value to turn on the light. The 0xFF (-1) means turn on the light.
For dimmer equipment 1 to 100 means the light strength. 0 means turn off the light.
Setting the illummination threshold to turn on the light. When the event triggered and the environment illumination lower then
the threshold, the device will turn on the light.
0 means turn off illumination detected function and never turn on the light.
1 means darkest.
99 means brightest.
100 means turn off illumination detected function. And always turn on the light.
* Notice * in none test mode, only the value in 1 to 99 will enable the illumination detected function and update the illumination value.
Bit 0: Reserved
Bit 1: Reserved
Bit 2: Disable the door/window function (1: Disable, 0: Enable).
Bit 3: Setting the temperature scale. 0: Fahrenheit, 1:Celsius.
Bit 4: Disable the illumination report after event triggered (1: Disable, 0: Enable).
Bit 5: Disable the temperature report after event triggered (1: Disable, 0: Enable).
Multi-Sensor Function switch. Using bit to control.
Bit 0: Disable magnetic integrate illumination to turn ON the lighting nodes in the association group 2 (1: Disable, 0: Enable).
Bit 1: Reserved always 1
Bit 2: Reserved always 1
Bit 3: Reserved
Bit 4: Disable delay 5 seconds to turn off the light, when door/window closed.
Bit 5: Disable auto turn off the light, after door/window opened to turn on the light. Notice: If bit2 is zero, this setting is useless. Notice: If the configuration No.9 is zero, this setting is useless.
Bit 6: Enable temperature monitoring. When this bit enabled the temperature changed 3 degree Fahrenheit. It will report. And also temp above 140 it will report every 64 seconds.
Customer function switch, using bit control.
Bit 0: Reserve.
Bit 1: Enable sending motion OFF report. Note: Depends on the Bit4, 0: Report Notification CC, Type: 0x07, Event: 0xFE 1: Sensor Binary Report, Type: 0x0C, Value: 0x00.
Bit 2: Enable PIR super sensitivity mode.
Bit 3: Enable don't send out BASIC OFF after door closed.
Bit 4: Notification Type, 0: Using Notification Report. 1: Using Sensor Binary Report.
Bit 5: Disable Multi CC in auto report.
Bit 6: Disable to report battery state when the device triggered.
Bit 7: Reserve.
After turn on the lighting, setting the delay time to turn off the lighting when the PIR motion is not detected.
8 seconds per tick, default tick is 4 (32 seconds). 0 means never send turn off light command.
The interval time for auto report the battery level. 0 means turn off auto report battery. The default value is 12. The tick time can setting by the configuration No.20.
The interval time for auto report the door/window state. 0 means turn off auto report door/window state. The default value is 12. The tick time can setting by the configuration No.20.
The interval time for auto report the illumination. 0 means turn off auto report illumination. The default value is 12. The tick time can setting by the configuration No.20.
The interval time for auto report the temperature. 0 means turn off auto report temperature. The default value is 12. The tick time can setting by the configuration No.20.
The interval time for auto report each tick. Setting this configuration will effect configuration No.10, No.11, No.12 and No.13. Caution: Setting to 0 means turn off all auto report function.
The temperature differential to report. 0 means turn off this function. The unit is Fahrenheit. Enable this function the device will detect every minutes. And when the temperature is over 140 degree Fahrenheit, it will continue report. Enable this functionality will cause some issue please see the detail in the "Temperature Report" section.
The illumination differential to report.0 means turn off this function. The unit is percentage. Enable this function the device will detect every minutes. Enable this functionality will cause some issue please see the detail in the "Illumination Report" section.
open-zwave-1.5/config/dragontech/ 0000775 0000000 0000000 00000000000 12644742024 0017042 5 ustar 00root root 0000000 0000000 open-zwave-1.5/config/dragontech/wd-100.xml 0000664 0000000 0000000 00000002357 12644742024 0020503 0 ustar 00root root 0000000 0000000
The orientation of the ON/OFF on the rocker switch can be inverted by changing the configuration item from 0 to 1
indicates the number of levels the lighting will change when the timer runs out
indicates the time duration of each level. The resolution is 10 miliseconds. for example, a default value of 3 means the timer runs out every 30 milliseconds.
open-zwave-1.5/config/duwi/ 0000775 0000000 0000000 00000000000 12644742024 0015674 5 ustar 00root root 0000000 0000000 open-zwave-1.5/config/duwi/ZWES1000.xml 0000664 0000000 0000000 00000000543 12644742024 0017511 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/duwi/ZWESJ300.xml 0000664 0000000 0000000 00000001370 12644742024 0017544 0 ustar 00root root 0000000 0000000
Continuous operation. 0x01-0x7F: 1-127 seconds in 1-second steps. 0x80-0xFE: 130-1390 seconds (0xFE) in 10 second-steps. 0xFF: 120 seconds (default;
open-zwave-1.5/config/enerwave/ 0000775 0000000 0000000 00000000000 12644742024 0016540 5 ustar 00root root 0000000 0000000 open-zwave-1.5/config/enerwave/zwn-sc7.xml 0000664 0000000 0000000 00000000352 12644742024 0020572 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/eurotronic/ 0000775 0000000 0000000 00000000000 12644742024 0017115 5 ustar 00root root 0000000 0000000 open-zwave-1.5/config/eurotronic/eur_cometz.xml 0000664 0000000 0000000 00000002130 12644742024 0022007 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/eurotronic/eur_stellaz.xml 0000664 0000000 0000000 00000002447 12644742024 0022177 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/everspring/ 0000775 0000000 0000000 00000000000 12644742024 0017110 5 ustar 00root root 0000000 0000000 open-zwave-1.5/config/everspring/ad146.xml 0000664 0000000 0000000 00000003003 12644742024 0020445 0 ustar 00root root 0000000 0000000
0 is off. 1 to 99 sets output level at specified value.
255 sets output level at last memorized level
Delaying time to report to Group 1
Remember the last status: 0 (do not remember) | 1 (remember)
0: Single Pole Double Throw (1: Toggle switch)
Output mode setting: 0 (dimming) | 1 (on/off)
open-zwave-1.5/config/everspring/ad147.xml 0000664 0000000 0000000 00000002563 12644742024 0020460 0 ustar 00root root 0000000 0000000
0 is off. 1 to 99 sets output level at specified value.
255 sets output level at last memorized level
Delaying time to report to Group 1
Remember the last status: 0 (do not remember) | 1 (remember)
Output mode setting: 0 (dimming) | 1 (on/off)
open-zwave-1.5/config/everspring/an145.xml 0000664 0000000 0000000 00000000701 12644742024 0020460 0 ustar 00root root 0000000 0000000
open-zwave-1.5/config/everspring/an158.xml 0000664 0000000 0000000 00000002542 12644742024 0020471 0 ustar 00root root 0000000 0000000
This is the time the switching status needs to remain
unchanged after a change to cause the device to send out a status
message. 0 is Disabled.
Enable or Disable Send Basic Command to Group 2 when the local
button press changes the switching state.
The device will report its meter value within the interval
set. Set to 0 will disable the autoreporting function.
open-zwave-1.5/config/everspring/an179.xml 0000664 0000000 0000000 00000002571 12644742024 0020476 0 ustar 00root root 0000000 0000000
Basic Set Command value
The delaying time to report to Group 1
Remember the last status on plug
0: Single Pole Double Throw (1: Toggle switch)