User's Manual

USER MANUAL PREVIEW

PTM 535BZ – BLUETOOTH AND ZIGBEE GREEN POWER PUSHBUTTON TRANSMITTER

5.6.12 ZGP_SOURCE_ID

Each PTM 535BZ module uses a unique four-byte address (ZGP Source ID) to identify itself

as the originator of ZGP radio telegrams as described in Chapter 4.4.

The ZGP Source ID is assigned by Zigbee Alliance and cannot be changed by the user. For

PTM 535BZ devices, the ZGP Source ID has the format 0x015n:nnnn. The structure of the

ZGP_SOURCE_ID register is shown in Figure 46 below.

Figure 46 – ZGP_SOURCE_ID

5.6.13 ZGP_COMMAND_0 … ZGP_COMMAND_7

As described in Chapter 4.4.1.3, PTM 535BZ will transmit user-defined ZGP commands if a

Device ID other than 0x07 is configured. In this case, PTM 535BZ will select the appropriate

command to be sent from the command table shown in Table 8 according to the status of

the INPUT1 and INPUT2 signals and the ECO 200 action.

Setting the value of a ZGP_COMMAND_x (x = 0…7) register to 0xFF will cause PTM 535BZ no

to transmit a data telegram. This can for instance be useful is PTM 535BZ should only transmit

a data telegram upon button press but not on release.

5.6.14 SECURITY_KEY1, SECURITY_KEY2 and SECURITY_KEY3

As described in Chapter 2.5, PTM 535BZ by default uses SECURITY_KEY1 for the authentica-

tion of transmitted data telegrams and for the generation of Resolvable Private Addresses.

SECURITY_KEY1 is NFC-readable and can be read via the SECURITY_KEY1 register.

It is possible to select using SECURITY_KEY2 instead of SECURITY_KEY1 via the

ZGP_SEC_CONFIG register (if PTM 535BZ transmits ZGP telegrams) or via the

BLE_SEC_CONFIG register (if PTM 535BZ transmits BLE telegrams). SECURITY_KEY2 is not

NFC readable; it can only be written by the user.

SECURITY_KEY3 is an optional key for the encryption of the security key within the ZGP

commissioning telegram. SECURITY_KEY3 is not NFC readable; it can only be written by the

user.