Leviton RF Installer Tool

[vc1234]

Right-click on All Devices in the left-hand panel. On that context menu, select Add Future Node.
 
If to pull up the RFIT Help, you can search for "Future Devices" and you'll have all the instructions.

Thanks for finding it, but that function does not appear to help much.
 
When I try to reserve future devices, the software simply increments the last max node id, it does not let me reuse a vacant number.  That does not solve my problem of reusing the former slot, therefore.

 

[drvnbysound]

Thanks for finding it, but that function does not appear to help much.
 
When I try to reserve future devices, the software simply increments the last max node id, it does not let me reuse a vacant number.  That does not solve my problem of reusing the former slot, therefore.

 
Understood. I was just answering the mail

 

[ddennerline]

I have moved Plugin modules around before without any routing update required. You will have to be careful if the module was used as a repeater for lock. Try to move the device and see if you notice any instability. Worst case is use the Diagnostic > Update Routes.
 
Unenroll  should be used as last resort because you will have to make sure that all nodes in your network have deleted that deviceID. I cannot count the number of times I had to un-enroll a lock and walk around the house hitting the "retry" button and praying all the devices routing tables get properly updated.
 
Someone with a different controller will have to confirm, but I believe all master controllers increment the DeviceID every time a new device is enrolled. This prevents conflicts.

 

[vc1234]

I have moved Plugin modules around before without any routing update required. You will have to be careful if the module was used as a repeater for lock. Try to move the device and see if you notice any instability. Worst case is use the Diagnostic > Update Routes.

 
Yes, I did it a while ago with another module, but because I've installed locks since, I was reluctant to do that for fear of breaking lock communication as you mentioned. As I keep comlaining about zwave, had I had an analyzer tool (at an acceptable price) to corroborate that there would be no performance impact/packet loss due to relocation, I'd  have used it to make sure that inter module communication was not impacted.  Even with the update routes option, one can never really be sure if the action was beneficial or detrimental in the absence of some objective measurement.
 

Unenroll  should be used as last resort because you will have to make sure that all nodes in your network have deleted that deviceID. I cannot count the number of times I had to un-enroll a lock and walk around the house hitting the "retry" button and praying all the devices routing tables get properly updated.
 
Someone with a different controller will have to confirm, but I believe all master controllers increment the DeviceID every time a new device is enrolled. This prevents conflicts.

It boggles my mind that a trivial problem like reusing vacant slots in the limited address space was implemented in the "tool"/RF USB firmware.

 

[Frunple]

Did you even attempt to try my suggestion?? I've done it numerous times and it will reuse the node id for you.

 

[vc1234]

Did you even attempt to try my suggestion?? I've done it numerous times and it will reuse the node id for you.

No, I did not because I was not sure about the suggestion implications.
 
Would not a new z-wave network be created if I change the installer network id ? That would mean that I'd need to re-include all the devices and the devices would get renumbered from scratch, no ?
 
Could you please describe the steps in more detail in case I am missing something ?

 

[Frunple]

The installer tool is not meant to be a part of your network. It's meant to configure the network, then be removed from it. In fact, it's meant to configure hundreds (or more) networks. So No, it won't "hurt" your network at all.
 
I don't remember the exact steps, been a while since I had to use it but save your network config, then go and create a new network. Include the installer tool in it so the tool is now going to be wiped clean basically. There may even be a menu option for this now that I'm thinking about it??
Then you go and add it back to your network in the same manner, and those "skipped" device ID's will be issued out to the next devices you add.
I even had a guy who had to have "this device" at "this ID"... wasn't easy, but I managed to do it.

 

[vc1234]

The installer tool is not meant to be a part of your network. It's meant to configure the network, then be removed from it. In fact, it's meant to configure hundreds (or more) networks. So No, it won't "hurt" your network at all.
 
I don't remember the exact steps, been a while since I had to use it but save your network config, then go and create a new network. Include the installer tool in it so the tool is now going to be wiped clean basically. There may even be a menu option for this now that I'm thinking about it??
Then you go and add it back to your network in the same manner, and those "skipped" device ID's will be issued out to the next devices you add.
I even had a guy who had to have "this device" at "this ID"... wasn't easy, but I managed to do it.

 
What you describe is creating a new network from scratch and re-enrolling *all* the existing devices.
 
My understanding is that when a device is enrolled/included, the primary controller assigns both the home network id and the node id to a new device.  That means that the old home network id cannot be used, obviously, requiring excluding/including all the devices for the sake of filling up the node id gap.
 
Someone, on another forum mentioned that Vera, as another example, does not reuse gaps either but rather keeps incrementing ids up to 232 and then wraps around and reuses available slots if any.  So, this defect of not reusing gaps (or giving it as an option) until the id > 232 appears to be residing in Zensys chip firmware  itself. 

 

[Frunple]

You are not including any devices in the new network.
 
As I said, the installer tool is meant be used in multiple networks. Create a new network with JUST the installer tool in it. DO NOT CHANGE ANYTHING IN YOUR DEVICES. Leave your existing network alone.
You just need to wipe the installer tool clean.
 
Or, don't do it and leave the unused id's as they are. It's really not as difficult as you're making it.

 

[vc1234]

You are not including any devices in the new network.
 
As I said, the installer tool is meant be used in multiple networks. Create a new network with JUST the installer tool in it. DO NOT CHANGE ANYTHING IN YOUR DEVICES. Leave your existing network alone.
You just need to wipe the installer tool clean.
 
Or, don't do it and leave the unused id's as they are. It's really not as difficult as you're making it.

Ok, I tried that:
 
 Created a new network with only the installer device in it (Node 1) and a new home network id.  Now what ?
 
How do I reuse the slots in the old network  ?

 

[drvnbysound]

Ok, I tried that:
 
 Created a new network with only the installer device in it (Node 1) and a new home network id.  Now what ?
 
How do I reuse the slots in the old network  ?

 
Close RFIT.
 
Re-open your saved configuration file - for your existing network.
 
Add new device.
 
Frunple is saying that when you re-join the USB dongle to "your network" that it will go back to assigning the unused IDs before incrementing to new ones.

 

[vc1234]

Close RFIT.
 
Re-open your saved configuration file - for your existing network.
 
Add new device.
 
Frunple is saying that when you re-join the USB dongle to "your network" that it will go back to assigning the unused IDs before incrementing to new ones.

1. Created a new network with only the installer device in it (Node 1) and a new home network id.
 
2. Re-opened my saved configuration file. The software tells me: "Configure RF Installer USB Stick To Match File".
 
3. Did what I was asked to do and now have the old home network with the old home network id.
 
4. Tried to add a new device.  The software/stick assigned the next consecutive number as it did before that exercise.
 
I expected exactly that sort of behavior, but decided to try anyway to see if I may be missing something.

 

[Frunple]

You're missing something...

 

[vc1234]

You're missing something...

That we agree on. Let's move to the interesting part: what exactly am I missing in the above sequence ?