Leviton RF Installer Tool

[vc1234]

I had to relocate a z wave plug in module to a new Chrismas tree location.  So, I excluded the module from the old location and included it at a new location (one floor down).
 
It worked fine except that the Node it was changed by incrementing the last used number.
 
Two questions:
 
1. Is it possible to reuse the old node id somehow from the installer app ?  I am assuming that the answer is "no", but I may be wrong.
 
2. Was it really necessary to exclude/include ? Could I just "Rediscover Node"/"Update Routes" routing from the installer app ?
 
Thanks.

 

[wkearney99]

While I'm not thrilled about the added expenses, I'm planning on just getting more devices to control seasonal lighting.  I even keep 'em plugged into an outlet in a closet near the attic (not up in the heat/cold).  Better to let them remain visible and communicating rather than having to remember to reprogram them every time they're needed.
 
How readily does z-wave handle devices retaining their programming but being moved to what would likely be a different section of the mesh?

 

[drvnbysound]

I had to relocate a z wave plug in module to a new Chrismas tree location.  So, I excluded the module from the old location and included it at a new location (one floor down).
 
It worked fine except that the Node it was changed by incrementing the last used number.
 
Two questions:
 
1. Is it possible to reuse the old node id somehow from the installer app ?  I am assuming that the answer is "no", but I may be wrong.
 
2. Was it really necessary to exclude/include ? Could I just "Rediscover Node"/"Update Routes" routing from the installer app ?
 
Thanks.

 
I don't know a way to force RFIT to re-use a node ID; if anyone has any OCD tendencies this will drive you crazy. I've actually re-learned my entire network before to remove some of the larger gaps I initially had.
 
I think you could have just rediscovered/update routes and have been fine. I only exclude if the device is completely leaving the network (e.g. sold device to someone else).

 

[drvnbysound]

While I'm not thrilled about the added expenses, I'm planning on just getting more devices to control seasonal lighting.  I even keep 'em plugged into an outlet in a closet near the attic (not up in the heat/cold).  Better to let them remain visible and communicating rather than having to remember to reprogram them every time they're needed.
 
How readily does z-wave handle devices retaining their programming but being moved to what would likely be a different section of the mesh?

 
I don't think there would be an issue, but as above, I would "update routes" and it should be fine... should be!
 
Having said that, I ended up just installing receptacles in the locations where we have seasonal lighting plugged in. That way I never have to change anything. The outlet itself actually turns on/off as scheduled throughout the year, but we don't use that one for anything else so there is no impact.

 

[pete_c]

Personally it is a time consuming effort relating to automating Christmas lighting.
 
Here when I was using Z-Wave for the Christmas stuff I did leave the modules plugged in and labeled with a piece tape telling me a bit about the switch.  I did the same for my Insteon and UPB switches utilized for Christmas over one or two seaons. 
 
That said though I have gone back now over the years to using the KISS principle of setting X10 switches to the same house code and having them all gone on en masse at the same time.  Works and allows me to spend more time with the installation of the lighting versus having to concern myself with the automation of the lighting.

 

[wkearney99]

Having said that, I ended up just installing receptacles in the locations where we have seasonal lighting plugged in. That way I never have to change anything. The outlet itself actually turns on/off as scheduled throughout the year, but we don't use that one for anything else so there is no impact.

 
Indeed, that's what I did for the outside lighting.  For several locations half the outlet is on a switch dedicated for 'Holiday' lighting.  Can't expect to the same thing for an interior wall outlet though.  For those I use in-line devices.  I'd use on-wall plug-in devices if Lutron actually made ones that would work with Radio RA2 (they don't).  Likewise I'd entertain in-wall outlets in one or two places, but nada from Lutron for that and RA2.
 
Along those lines, I greatly prefer on-wall gizmos that have local control.  I'm really disappointed the Leviton units don't have a way to toggle power on the device itself.  I've had to resort to using a WeMo and really find them unreliable.  Anyone else making an on-wall z-wave switch that has a local control button?  (sorry, for the thread hijack though)

 

[vc1234]

While I'm not thrilled about the added expenses, I'm planning on just getting more devices to control seasonal lighting.  I even keep 'em plugged into an outlet in a closet near the attic (not up in the heat/cold).  Better to let them remain visible and communicating rather than having to remember to reprogram them every time they're needed.
 
How readily does z-wave handle devices retaining their programming but being moved to what would likely be a different section of the mesh?

There were two motivating factors:

1. I had an unused plug-in module at a location where we used to put the tree. So, it was sort of wasteful/ugly abandoning the old pluggable module at the unused location.
 
2. I did not have time to get an new module on time anyway, so I had to re-use the unused module. Plus it has an on/off button and can be controled locally if needed.
 
The ability to re-use a node id is important in my case because in my elk I have an adjacent block of X11 addresses being used for cheap motion detection.  There is a danger of overflowing into that block if the node ids just keep being incremented.
 
I vaguely recall from previous discussions on this forum that the leviton installer allegedly has ability to reserve "future ids", but I could not find the menu item that does that.

 

[Frunple]

I had to relocate a z wave plug in module to a new Chrismas tree location.  So, I excluded the module from the old location and included it at a new location (one floor down).
 
It worked fine except that the Node it was changed by incrementing the last used number.
 
Two questions:
 
1. Is it possible to reuse the old node id somehow from the installer app ?  I am assuming that the answer is "no", but I may be wrong.
 
2. Was it really necessary to exclude/include ? Could I just "Rediscover Node"/"Update Routes" routing from the installer app ?
 
Thanks.

 
1) Yes. I believe if you change the network ID of the installer tool, then change back to the network you use, it'l re-issue that ID.
 
2) No. You can just move them around as you want and the network will "heal" itself.

 

[pete_c]

Here do not pay much attention to the Leviton Z-Wave stuff connected to the OmniPro 2 panel.  The Z-Wave devices do fine. (well as the UPB and X10 devices).
 
I do occassionally  / manually do the doo of watching the Homeseer Mothership Z-Wave plus network.  If I do not look it does it's automatic Z-Health thing and auto reroutes stuff if I happen to move a Z-Wave device.
 
I do do a light scan, full scan, optimize and fully optimize the Homeseer Z-Wave Plus network.  I do really pay much attention to it and I must do it because I like to push buttons. 
 
(kind of similiar when you are in some one else's automobile and push every button within reach to see what they do?)

 

[drvnbysound]

Indeed, that's what I did for the outside lighting.  For several locations half the outlet is on a switch dedicated for 'Holiday' lighting.  Can't expect to the same thing for an interior wall outlet though.  For those I use in-line devices.  I'd use on-wall plug-in devices if Lutron actually made ones that would work with Radio RA2 (they don't).  Likewise I'd entertain in-wall outlets in one or two places, but nada from Lutron for that and RA2.
 
Along those lines, I greatly prefer on-wall gizmos that have local control.  I'm really disappointed the Leviton units don't have a way to toggle power on the device itself.  I've had to resort to using a WeMo and really find them unreliable.  Anyone else making an on-wall z-wave switch that has a local control button?  (sorry, for the thread hijack though)

 
I think I have 3-5 indoor receptacles installed. The ones I have are from GE/Jasco and do have a local button that also controls the Zwave half of the receptacle; the other half is always on. The limitation I have here, is that the GE ones do not report feedback. In my case, I really don't care based on the purpose each these are used for...
 
These receptacles do support beaming, which was a requirement of mine as I have Zwave deadbolts as well. One of them we really almost never use, and I only placed it there as a signal repeater. Another is located where we place our Christmas tree, and we never plug anything else in that place any other time of the year; my rule for thus runs every day. I know I have another one in my son's BR and had initially programmed it to turn on at night, with a nightlight installed, and automatically turn off in the AM; this one also still runs daily and my wife has since re-arranged the room and she completely removed the nightlight from his room as well.

 

[drvnbysound]

There were two motivating factors:

1. I had an unused plug-in module at a location where we used to put the tree. So, it was sort of wasteful/ugly abandoning the old pluggable module at the unused location.
 
2. I did not have time to get an new module on time anyway, so I had to re-use the unused module. Plus it has an on/off button and can be controled locally if needed.
 
The ability to re-use a node id is important in my case because in my elk I have an adjacent block of X11 addresses being used for cheap motion detection.  There is a danger of overflowing into that block if the node ids just keep being incremented.
 
I vaguely recall from previous discussions on this forum that the leviton installer allegedly has ability to reserve "future ids", but I could not find the menu item that does that.

 
Yes. I will look again tonight, but there is a way to do this; I found it a few weeks ago when I was searching the Help for something else.

 

[drvnbysound]

1) Yes. I believe if you change the network ID of the installer tool, then change back to the network you use, it'l re-issue that ID.
 
2) No. You can just move them around as you want and the network will "heal" itself.

 
Yes, you can do that for managing different networks/installations, but the discussion was regarding DEVICE IDs. The Installer Tool automatically assigns the Device IDs without a way to really manually manage them.

 

[vc1234]

Yes. I will look again tonight, but there is a way to do this; I found it a few weeks ago when I was searching the Help for something else.

 
Oh, thanks, that would be super.

 

[Frunple]

Yes, you can do that for managing different networks/installations, but the discussion was regarding DEVICE IDs. The Installer Tool automatically assigns the Device IDs without a way to really manually manage them.

 
Yes, I know that. That's why I said it will re-issue that DEVICE ID.

 

[drvnbysound]

There were two motivating factors:

1. I had an unused plug-in module at a location where we used to put the tree. So, it was sort of wasteful/ugly abandoning the old pluggable module at the unused location.
 
2. I did not have time to get an new module on time anyway, so I had to re-use the unused module. Plus it has an on/off button and can be controled locally if needed.
 
The ability to re-use a node id is important in my case because in my elk I have an adjacent block of X11 addresses being used for cheap motion detection.  There is a danger of overflowing into that block if the node ids just keep being incremented.
 
I vaguely recall from previous discussions on this forum that the leviton installer allegedly has ability to reserve "future ids", but I could not find the menu item that does that.

 
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.