Questions on migrating Zwave to the ISY

[gduprey]

Howdy,

 

When I started to get into ZWave 20+ months ago, I selected a MiCaseVerde controller (Vera3) for talking to Zwave devices based on their ZWave device support.  I selected the ISY for my Insteon lighting network and used a plugin on the MCV to "import" all the ISY devices into a unified whole.  It worked, mostly.

 

Problem is the MCV is (IMHO) unreliable and their development direction seems like it's only getting worse.  So I'm working to leave the MCV.  I've purchased (but not yet installed) the ISY ZWave module and will be installing it soon.

 

I also have a lot of custom software talking to the MCV that I have to migrate to talking directly to the ISY.  This is going to take a while.

 

My current thinking (which I'm very much open to more experienced peoples thoughts on) is that once I have the ZWave module installed and working, I'd "migrate" the Primary Zwave controller/device from the MCV to my ISY and leave the MCV as a secondary controller.  From what I have read, the MCV should be absolutely fine to continue sending and receiving commands (it just won't be able to manage inclusion/exclusion). Once I complete redeveloping all my custom software to talk to the ISY and nothing much uses the MCV, I'd just turn it off (possibly with a flame thrower).

 

My questions:

 

Is it really that simple?  Do I just put the go into "ZWave -> Receive/Learn mode" and then send tell the MCV to send it?  

 

How do I make the ISY "primary" after that, or does that automatically happen after learning all the devices?

 

Are there any concerns with security devices (like door looks) or battery devices when I do this migration?

 

When I do finally toss the MCV, do I need to do anything to let the rest of the ZWave network know it's no longer a secondary controller?  Or just turn it off?

 

Unfortunately, this is my first time with any Zwave controller migration and I really don't want to screw the house up.  Any pointers/experience/suggestions on any part of this would be much appreciated.

 

Thanks!

 

Gerry

P.S. for those who have been following along with the Zwave stuff in the development forums and possibly confused, my ISY with ZWave is at a separate condo I spend 1/2 my time at and the above is for my primary house where the ISY hasn't done Zwave (until this coming week).

[bgrubb1]

Gduprey, welcome to the dump vera membership, so happy I did

When I did my transition, I left both the ISY and the Vera as primary controllers and migrated one piece at a time.

First I did my IR wifi2ir controllers, then thermostats, Then did a remove device from vera, add device to ISY one at a time. that way I could move the affected software one piece at a time as well (GEM interface, DSC Linc, etc.) as well as programs (thermostat hour control etc.)  I use my ISY (and previously Vera) to do a lot of energy management, by doing it in steps, I never lost a KWh

took a few weekends, but never lost functionality that way

Just my 2 bits

...Barry

[MWareman]

Also, be aware the ISY does not yet support multi-channel devices. So many recent Fibrio and Aeotec (as well as other) devices are either only partly functional, or not functional on the ISY (yet). You would be best off either moving one device at a time or joining ISY to your MCV as a secondary device until full multi-channel is available on ISY.

 

The other thing you might notice is an incomplete SUC/SIS implementation on ISY as compared to the MCV. MCV supports remote inclusion devices, ISY does not.

[bgrubb1]

Good point, I ended up replacing a couple of sets of 3 way Zwave scene controller light switches with Insteon 3 way switches to complete the transition. ISY version 5 with 2 way was and is still not available

..Barry

[Michel Kohanim]

Hi Gerry,

 

Yes, it's easy to make ISY secondary xor primary controller. In both cases, though, you need to do something on the Vera side. The big caveat is: primary controller is in charge of IDs and routing tables so, if by any chance, you remove the primary controller, then everything will disappear.

 

One more suggestion: once you are done with your Z-Wave setup, make sure you do Z-Wave | Tools | Backup ... this will create a backup of the Z-Wave dongle into ISY which can later be used to restore it.

 

With kind regards,

Michel

[gduprey]

Howdy,

 

I've made my ISY a secondary to the Vera and all my devices came over (including my locks).  So that worked well!!

 

However, I now find that I want to make the ISY the primary and I cannot figure it out.  I put the ISY into Learn/Receive mode, then from the Vera3 I go to the Advanced ZWave options and press the Controller Shift button.  It says controller shifted, but nothing happens on the ISY and after a few minutes, the Vera3 console reloads and it looks like nothing happened.  The ISY console is still acting like a secondary (i.e. no include/exclude support, just learn) and in the Vera3 ZWave options, it still says "Master SIS:NO PRI:YES" under the "Role" listing.

 

I know that this isn't likely something the UDI folks can answer, but if there is anyone who was done this (added the ISY as a secondary and then later, wanted to change it to the primary), I'd very much appreciate hearing from you!!

 

Gerry

[Michel Kohanim]

HI Gerry,

 

I am sure it's possible since there are a few customers who have done it and it works (alas, once in a while, it causes major communication issues). I just do not know how they accomplished this feat. Procedurally what you are doing is 100% correct.

 

With kind regards,

Michel