Role:Master SIS: NO PRI: YES

Can someone explain what this is and how can we control or change from primary or back to primary? I had an issue where as both SIS and PRI were set to yes and I was no longer able to get into include mode. Vera support fixed it but did not get much in the way of explaining what these do exactly.

Static Update Controller(SUC) ID Server(SIS) is an flag/function of legacy Z-Wave networks and is no longer applicable. On Vera, unless you are running old firmware on a Vera 2, 3 ,or Lite, it should be No and it is not something than can be changed or configured.

Pri: indicates the Primary or Master controller on the Z-Wave network. Only the Primary can add/include new Z-Wave devices to the network. In almost all cases, Vera should be Pri:Yes.

The Pri is another indicator that is not settable/configurable. This role is set by creating the Z-Wave network or by controller shifts, moving the master role from one controller to another. In rare cases, the the Z-Wave chip’s role can be corrupted and problems like not being able to include new devices will occur. There are a few options to resolve this like restoring from backup, replacing the firmware on the chip, seizing the network role…

You stated that yours was the primary, but you were still unable to include devices. This sounds like a truly hosed up chip. I suspect that they re-applied the chip firmware and possibly restored from backup in order to fix it.

Thanks for clearing this up.

If it is of any interest …

In order to improve the experience of my Danfoss Living Radiator valves (few.2.51) I was advised by Vera support (on my Vera3) to downgrade to firmware with SIS, so I’m running 2.78. (Suc SIS:YES PRI:YES

http://manuals.zwaveeurope.com/make.php?lang=en&type=&sku=DAN_LIVC_RAK

Danfoss allude to the rational of SUC in the above document. (Extract below)

[i]Known Problems in Z-Wave Networks: This device is sleeping and wakes up regularly. When waking up the device needs a wireless connection to the controller to get clock and heating schedule updates if needed. If no wireless connection to the controller can be found the device will enter an exception mode indicated by a flashing bell in conjunction with flashing antenna symbol on the LCD display. To exit this exception mode as soon as possible the device tries to reestablish a wireless connection by applying the so-called 'Lost' procedure defined by Z-Wave with the help of a Static Update Controller (SUC) in the network. In case of success the execption mode is terminated. In case of failure - e.g. because the controller is still shut off - the device will remain in the exception mode and repeats the 'Lost' process. This drains the battery very fast. To avoid this situation make sure the following requirements are made: (a) the thermostat has a stable direct wireless connection to the controller or (b) there is a static controller serving as SUC in the Z-Wave network and there is a valid route between the device and this SUC.[/i]