I just connected a VRC0P to my PC with the intention of using it to programmatically toggle a few HM-AM001 appliance modules scattered throughout the home.
If I know the node number for the AM I want, it is easy enough to turn the module on/off: ">N5ON" ">N5OFF"
But I am having some issues obtaining a list of node numbers from the VRC0P:
- ">?N" lists on/off/dimmer status for somewhere between 2-5 of the nodes, but not all of them
- LumenLink takes several hours to probe the network, and AFAICT they are doing it incorrectly anyway. Their strategy is to send 4,176 total commands in the form of: ">?FIx,y,0,z", with z ranging from 1-232. This usually times out after 1-2 seconds. On my network this procedure does not work, as all of the nodes respond to instance 1 only.
- I suppose I could hard-code the node numbers on the PC, but it seems like they change around when I muck with my primary remote. I would rather have a way to uniquely identify each appliance module so I don't ever have to change the associations on the PC side.
A few additional questions:
- Is it possible to query each node for a unique serial number? How about manufacturer, class codes, etc.? The only data I seem to get from ">?FI" is the number of matches.
- Are there any interesting "SE" commands for appliance modules?
- When I program a primary/secondary remote, it has the ability to detect when I have pushed the button on one of the appliance modules. Is there a way to do this on ZRC0P?
- Has anybody else noticed that with old VRC0P firmwares ($Leviton(C) 2008 V2.2S/Z-Wave 3.11) there is an off-by-one bug regarding the node numbers?
- All of this seemed so much easier with X10, because X10 let me set the numbers myself. How do Z-Wave users cope with the fact that the network auto-assigns the node numbers and it isn't under your control?
My VRC0P is running the latest FW from leviton.com: $Leviton(C) 2008 V2.31S/Z-Wave 3.11
If I know the node number for the AM I want, it is easy enough to turn the module on/off: ">N5ON" ">N5OFF"
But I am having some issues obtaining a list of node numbers from the VRC0P:
- ">?N" lists on/off/dimmer status for somewhere between 2-5 of the nodes, but not all of them
- LumenLink takes several hours to probe the network, and AFAICT they are doing it incorrectly anyway. Their strategy is to send 4,176 total commands in the form of: ">?FIx,y,0,z", with z ranging from 1-232. This usually times out after 1-2 seconds. On my network this procedure does not work, as all of the nodes respond to instance 1 only.
- I suppose I could hard-code the node numbers on the PC, but it seems like they change around when I muck with my primary remote. I would rather have a way to uniquely identify each appliance module so I don't ever have to change the associations on the PC side.
A few additional questions:
- Is it possible to query each node for a unique serial number? How about manufacturer, class codes, etc.? The only data I seem to get from ">?FI" is the number of matches.
- Are there any interesting "SE" commands for appliance modules?
- When I program a primary/secondary remote, it has the ability to detect when I have pushed the button on one of the appliance modules. Is there a way to do this on ZRC0P?
- Has anybody else noticed that with old VRC0P firmwares ($Leviton(C) 2008 V2.2S/Z-Wave 3.11) there is an off-by-one bug regarding the node numbers?
- All of this seemed so much easier with X10, because X10 let me set the numbers myself. How do Z-Wave users cope with the fact that the network auto-assigns the node numbers and it isn't under your control?
My VRC0P is running the latest FW from leviton.com: $Leviton(C) 2008 V2.31S/Z-Wave 3.11