Z-Wave installation scheme

Choose of Primary Controller

It is important to think in advance about your installation scheme not to have to rebuild your network and re-include all devices again. It is extremly important to choose correctly the primary controller.

• If you have a large enough network, you will have to include distant devices and hence, either your primary controllers need to be portable or you have to use SIS to allow all controllers to include.

• Virtual Slave devices requires a bridge controller either as primary or as inclusion controller.

• The presence of secondary SUC controller allows you to shift the primary in case of lost of your previous primary. SUC makes your installation robust to controller failure.

TODO	Describe what happens when a primary request a slave to become SIS. Can this (old) primary request SIS to stop it's SIS functionality and return the primary privilege to the old primary? What device can do this (except for PC controller?) - I've never seen

Check me

Can I have SUC in a network with Primary SIS?

Primary controller type	With SUC included	Inclusion of distant devices	Other controllers can include	Recover a lost primary (primary shift)	Possibility to (re)assign SUC/SIS	Virtual Slave can be included
Portable	without SUC	∨	×	×	∨	×
	with SUC	∨	×	∨	∨	×
Static	without SUC	×	×	×	∨	×
	with SUC	×	×	∨	∨	×
Static SIS		∨	∨	×	∨	∨(with bridge controller included)
Static Bridge	without SUC	×	×	×	×*	∨
	with SUC	×	×	∨	×*	∨
Static Bridge SUC enabled in SIS mode		∨	∨	×	? (not tested)	∨

From this table we can conclude, that to use Virtual Slave devices (to have full functionality from AWZ) and include distant devices at he same time one should use one of the following configurations:

• use two controllers: SIS and Bridge
• use Bridge with SUC/SIS enabled capability as SIS (in this case you controller may be unable to communicate with FLiRS devices since SUC and FLiRS support can not be combined in Bridge firmware)

Inclusion order

Every controller in the Z-Wave network stores network topology (routing table). A controller is learned about the network topology only during (re-)inclusion precess.

If you don't use SUC/SIS, you have to learn controllers about new devices in the network manually. It is recommended to request neighbour update of all slave devices and re-include all controller at the end of your installation.

If you will use SUC or SIS, include them at the beginning of your installation. All devices included after the assignment of SUC/SIS will be informed about it's presence. This allows you not to update neighbour information and assign return route to SUC at the end of your installation.