Can't add devices - how do I make Veralite the primary controller?

Community Playground General Discussions
1

Hello,

I’m having an issue where I can’t add new zwave devices. When I click to add (option 1), it pops up a “Please wait…” message and stays like that.

I tracked down a thread where someone has a similar issue and it’s because Vera is not the primary controller:
http://forum.micasaverde.com/index.php?topic=11337.0
I checked my settings and have the same “Role Slave SIS:NO PRI:NO” status.

I followed the advice in that thread but I get the error “Command failed - not primary controller” when I tried a controller shift.

If I issue “Reset Zwave network”, is it correct that I have to reconfigure all devices? Is there anything else I can try before that?

Thanks,
Jeff

2

The way I see it, you have three options:

  1. Have technical support look at it.

  2. Restore Vera and the Z-Wave dongle to a time before you shifted Vera to a secondary controller.

  3. Reset Z-Wave Network.

Reset Z-Wave Chip - This will restart or re-initialize the Z-Wave chip. It will not cause any loss of data.

Reset Z-Wave Network - This will completely erase the chip and you will have to reconfigure all devices as this will generate a new HomeID.

3

You can also use the Hack to switch to 2.78 and then back to 3.2 of the ZWave firmware and it’ll fix it. See this post:
http://forum.micasaverde.com/index.php/topic,10326.msg71538.html#msg71538

I had to do that on my Vera3 sometime back and it fixed it without having to rebuild my network.

Make backups etc, since it’s always good to have a fallback option.

4

Thanks for the replies! I’ll read more into the 2.78/3.2 workaround and try that. As long as I store backups, it seems like a safe thing to try. I’m really trying to avoid resetting the network because I have a lot of things set up right now.

One thing that doesn’t make sense to me is how this happened in the first place - the only controller I own is Veralite and I don’t see what I could have done to shift to secondary.

5

There’s a long-running bug that can result in the loss of PRI. There are many theories on “why” this happens, and which piece of the puzzle is specifically responsible for the issue (HW or Software), but it cropped up a lot on the Vera2 HW :wink:

I have a medium-sized Network, that would be a PITA to rebuild, so I waited until I switched to the Vera3 (UI5) to “fix” the problem - due to the availability of the the ZWave FW “Hack” to address it without rebuild.

6

Thanks guessed! I went through the downgrade/upgrade steps and I’m back in primary mode. Hopefully it will stick around for a while this time…

7

If you have danfoss thermostats MCV could have reset your network, I have tryed that.
Quote from mcv after I had included some devices. I asked mcv for help as I could not include, afterwards I asked why, and they reset it for yse with danfoss. Hope there will be come a fix for that.
"I’ve downgraded for you the z-wave to 2.78

The Danfoss radiators requires the z-wave Role to be set to SUC instead of Master.

This can be achieved by downgrading the z-wave firmware from 3.20 which comes installed by default on the units to 2.78.

After that press reload and the Role should be updated to SUC with SIS:YES PRI:YES"