- The documentation is very detailed and includes integrated instructions for Elk and Leviton Z-Wave systems. There are detailed example rules lights, thermostats, and locks.
- The M1XSLZW board has been redesigned. From what little I can tell, the RS-485 connectivity, baud rate jumpers, and general purpose jumpers have been eliminated. Integrating the VRC0P+3 was painless. I believe the Motorola 9s08 (http://www.datasheet...-datasheet.html) is the same on both boards.
- The M1XSLZW does a complete scan of Z-Wave network on startup, so you don’t have to walk around to light switches and toggle them in order to get the entire system system correct.
- You no longer have to use LumenLink to build groups and scenes into the VRC0P+3. The Leviton RF Toolkit now synchronizes all the “Areas” into VRC0P+3.
- I could control the front door Kwikset lock immediately. Having a close all locks function when armed stay/away rule provides some extra piece of mind (if you forgot). I did install a VRP03+3 plugin dimmer halfway between Elk VRC0P+3 and front door. It does in fact take 6 seconds to fully lock door as documentation indicates.
- Using Leviton RF Toolkit provides a much better experience than ControlThink as primary controller. It’s much easier to build, deploy, and troubleshoot network.
- Lock low-battery support notification. This is a nice to have feature. I only have one lock right now and the lock light is supposed to flash red when batteries need to be replaced. But if someone had a Z-Wave lock on infrequently used entrance this would be helpful.
- Multitude of lock, unlock, bolt failed notifications (I have not tested this feature yet).
- Support for Z-wave Scenes (I have not test this feature yet).
- Support for Group “dimmer level” support
- A re-scan of Z-Wave network can be initiated by ElkRP rule (same as done during startup). You may run this task once a night just to make sure all your network status is accurate.
- Support for infrequent polling of devices. The ElkRP rule driven network scan is a good first step, but it takes quite a while to scan whole network. What I really want is ping devices during periods where network activity is low. These queries should have lower priority than ElkRP rules.
- Importing Leviton RF Toolkit lighting file – similar to recently added RadioRA2 solution. It’s a big pain to have to correlate and manual enter all the devices/groups/scenes into ElkRP
- Having to manipulate locks using a good number of ‘text’ string rules (i.e., >UNLOCK1) is odd. ElkRP should have “advance lock” class – similar to thermostats.
- (too late for this one). Board troubleshooting and activity status improvements using a more advanced mechanism that a single flashing led light (e.g., a two digit led).
Edited by d.dennerline, 30 June 2012 - 12:07 AM.