User's Manual

27
ASSA ABLOY Hospitality
66 3081 004-23
3.6 Adding locks to gateways
There may be cases where the locks will communicate directly with the GW.
To do this:
1. Choose Permit Joining on the GW and present the Discovery card at the lock
(see chapter 5 Issuing a ZigBee configuration card); the lock will chirp once
and/or show a green LED signal, depending on lock model. The lock will attach
itself to the GW on which Permit Joining has been made, and when the first
event is received the room number will automatically fill in.
Figure 31
2. Add the necessary locks and then choose Forbid Joining on the GW.
Note: RTs should not be connected to a GW which has got ENs connected to it.
3.7 Forcing parents
If a device such as an EN sees two RTs when it is in discovery mode (i.e. if 'permit
joining' has by mistake been made on two RTs belonging to different PANs at the
same time), it is possible that the EN will not join the desired RT – i.e. the RT with
which it has the strongest RF link. For this reason it is recommended that GWs, RTs
and ENs be installed in a systematic way to ensure all devices are connected to the
parent that makes the most sense.
If a situation arises in which a device is connected to the wrong parent, it is easy
enough to force the child device to leave the network and rejoin properly. If a right
click is made on the child device in SysMon, and the Leave network command is
chosen, the child device will deregister from the parent so another node can join.
The rejoining to a new parent is performed with the Permit Joining command.
An example when a child device is connected to the wrong parent would be that an
EN is within range of both RT-A and RT-B. Signal strength between the EN and RT-A
is 32%, while signal strength between the EN and RT-B is 75%. In this case it is a
good idea to force the EN to connect to RT-B.
To force the EN by using the Permit Joining command:
1. Right click on the EN and choose Leave Network. The EN will deregister
from RT-A.