Proper procedure for adding a secondary Z-Troller?

[VirtualPanther]

Hello,
I have a single z-troller as my primary controller, connected to Hometroller S3 running Homeseer Pro, latest version. After installing two Yale locks, it became apparent that despite my adding a couple of beaming dimmers and outlets next to each of the locks, communication is still nowhere near reliable.

My whole house is Cat6 wired, as well as covered with 3 Wi-Fi access points. So, I decided to buy another Z-Troller along with serial-to-Ethernet adapter and place it next to the lock with most communication problems. Kind of expensive solution, but I am hoping that (a) my lock communication problems will disappear and(b) overall coverage of the house will improve.

I am afraid of loosing all of the data on my primary controller in the process of adding another one. I know I can back it up. I will do that. But what is the ideal sequence of steps to add another Z-Troller as a secondary controller? How is the procedure different when using serial-to-Ethernet adapter? I added the adapter as an option available when placing Z-Troller in the cart in Homeseer store. I have no idea what brand it is.

It seems that every time I add something, I first try to follow steps in instructions (if those are available), guided by prior experience. After that I have to remove the device from HomeSeer and search the forums for hours on end, looking for troubleshooting steps. Yale locks have proven to be an especially huge PITA. As I can see from forums, I am not alone...

So, another z-troller, as a secondary controller, connected to serial-to-Ethernet adapter. Open the UPS box, unpack everything, then...

[rmasonjr]

Follow the instructions in this thread:
http://board.homeseer.com/showthread.php?t=127572

[VirtualPanther]

Follow the instructions in this thread:
http://board.homeseer.com/showthread.php?t=127572

Thank you for the link. The guide seems to be quite thorough. Once the z-troller arrives, I will try following it. Hopefully, my Yale lock will finally communicate with Homeseer then.

One question, though: according to that guide, all of my future devices still will be added to the primary controller, with their information copied over to the secondary via Homeseer. However, the guide says that the routes are not copied over, which makes sense. The whole point of my adding a secondary controller is to fix the communication problem between the primary controller and some of the more distant devices. So, once I add that secondary controller, does each device need to be individually asociated with either the primary or the secondary controller? For example, when it comes to my most burning problem - Yale lock, do i have to manually go under its root device and associate it with the new secondary controller, in order to have it talk to that one, and not try and fail (like now) to reach the primary controller?

[rmasonjr]

correct. You go into each device and you will see a new pulldown to select the interface to use.

[VirtualPanther]

correct. You go into each device and you will see a new pulldown to select the interface to use.

Easy enough. With my problematic lock, I know I want to use the new interface. But how do you decide with other devices. I mean, if you change the interface on a device, you may very well be removing it from a well-working route for some other device, right? Initially I thought that all z-trollers on the same system will auto-configure routes, without manual intervention. But it sounds like it is up to me to pick and choose which devices will be associated with one or the other z-troller. Doesn't sound like the best scenario...

[VirtualPanther]

OK, so I my secondary z-troller arrived. After a bit of mocking around, it was successfully added to HomeSeer via Ethernet address (GlobalCache serial to Ethernet converter). I followed the procedure described in the post linked above and now all of the devices that I wanted to be associated with the new controller are.

So, what's the problem, you ask?

Very simple. Now most of my devices that are associated with my primary controller have numerous errors. Errors when I try to optimize them, errors when i try to change configuration, etc.

I understand that now that some of my devices previously associated with my primary controller are associated with a secondary controller, that changes the return routes for ALL devices. That is pretty much what the How-to page says: optimize everything. I tried. Failed. So I manually optimized each of the devices I wanted to be associated with a new secondary controller - 4 times each, followed by a full optimization - and they all succeeded. Then I tried optimizing, device after device, those that remain with primary controller and optimization fails each and every time, repeatedly. So do my attempts at rescanning those devices.

How do I fix this nightmare? Prior to my purchasing these damn locks everything was working so well...

[VirtualPanther]

Just tried "Optimize Network" from "Manage interface" page: every single node failed, regardless which controller is it associated with:

"The operation did not succeed, Add Return Route was not attempted. Check the log for any additional information"

[rmasonjr]

this is one of the reasons I feel that z-wave needs a lot of hand-holding. I had to really go through a lot of the same things when I added my second ztroller. First thing, if you are on v.49 then you might be having the same issues that I and others are having. Secondly, and it may be a little late, but maybe just associate 1 or 2 devices to the new controller so that you 'ease' into it. How many devices do you have?

[VirtualPanther]

this is one of the reasons I feel that z-wave needs a lot of hand-holding. I had to really go through a lot of the same things when I added my second ztroller. First thing, if you are on v.49 then you might be having the same issues that I and others are having. Secondly, and it may be a little late, but maybe just associate 1 or 2 devices to the new controller so that you 'ease' into it. How many devices do you have?

I am on 2.5.0.49 now. Worked fine, until the locks were added...

I have 40 nodes, which have created 144 "devices".

I did plan on "easing in", but in order to get the lock working, some of the devices around that lock needed to be associated with the new secondary z-troller too...

Really boggles my mind that all of the old devices that worked perfectly will not optimize at all now. I'd bet i could have simply removed all of those outlets and switches that are now associated with a secondary controller, and each of the remaining devices would still optimize...

Now, after spending over $500 on additional technology needed to get the $250 lock working, I am faced with inability to optimize ANY node associated with my old primary controller

So much for fixing things. First, added a bunch of "beaming" switches and outlets without any improvement. Now, added a secondary controller and a serial-to-Ethernet interface: got one lock and switches around it working on that new controller. The main controller can't fix/create any routes to- and from any of the remaining devices...

[kevini]

I found that z-health runs fine even through the full optimize does not work for some devices.

Put on z-health for a couple of nights and it should clear up your issues.