Download Print this page

Communication To A Sleeping Device (Wakeup); Quick Troubleshooting; Firmware-Update Over The Air; Association - One Device Controls An Other Device - Philio PAT02-B Quick Start Manual

Temperature and humidity sensor
Hide thumbs Also See for PAT02-B:

Advertisement

13/10/2019
Pressing the tamper key three times within 1.5 seconds to manual inclusion with Z-Wave controller.
Exclusion
Pressing tamper key three times within 1.5 seconds to enter the exclusion mode.

Communication to a Sleeping device (Wakeup)

This device is battery operated and turned into deep sleep state most of the time to save battery life time. Communication with the device is limited. In order to
communicate with the device, a static controller C is needed in the network. This controller will maintain a mailbox for the battery operated devices and store
commands that can not be received during deep sleep state. Without such a controller, communication may become impossible and/or the battery life time is
significantly decreased.
This device will wakeup regularly and announce the wakeup state by sending out a so called Wakeup Notification. The controller can then empty the mailbox.
Therefore, the device needs to be configured with the desired wakeup interval and the node ID of the controller. If the device was included by a static controller this
controller will usually perform all necessary configurations. The wakeup interval is a tradeoff between maximal battery life time and the desired responses of the
device. To wakeup the device please perform the following action: When the device power on, the device will wake about 20 seconds. In this duration, the
controller can communicate with the device. Normally the device is always sleeping to save the battery energy.
Quick trouble shooting
Here are a few hints for network installation if things dont work as expected.
1. Make sure a device is in factory reset state before including. In doubt exclude before include.
2. If inclusion still fails, check if both devices use the same frequency.
3. Remove all dead devices from associations. Otherwise you will see severe delays.
4. Never use sleeping battery devices without a central controller.
5. Dont poll FLIRS devices.
6. Make sure to have enough mains powered device to benefit from the meshing

Firmware-Update over the Air

This device is capable of receiving a new firmware 'over the air'. The update function needs to be supported by the central controller. Once the controller starts the
update process, perform the following action to confirm the firmware update: The device support the Z-Wave firmware update via OTA. Let the controller into the
firmware update mode, and then press the tamper key once to start the update. After finish the firmware download, the LED will start flash in every 0.5 second. At
that time, please don't remove the battery , otherwise it will cause the firmware broken, and the device will no function. After the LED stop flash, it is recommended
that the user power up the device. Caution: After remove the battery, please wait about 30 seconds, and then re-install the battery.

Association - one device controls an other device

Z-Wave devices control other Z-Wave devices. The relationship between one device controlling another device is called association. In order to control a different
device, the controlling device needs to maintain a list of devices that will receive controlling commands. These lists are called association groups and they are
always related to certain events (e.g. button pressed, sensor triggers, ...). In case the event happens all devices stored in the respective association group will
receive the same wireless command wireless command, typically a 'Basic Set' Command.
Association Groups:
Group Number
1
2
Configuration Parameters
Z-Wave products are supposed to work out of the box after inclusion, however certain configuration can adapt the function better to user needs or unlock further
enhanced features.
IMPORTANT: Controllers may only allow configuring signed values. In order to set values in the range 128 ... 255 the value sent in the application shall be the
desired value minus 256. For example: To set a parameter to 200 it may be needed to set a value of 200 minus 256 = minus 56. In case of a two byte value the
same logic applies: Values greater than 32768 may needed to be given as negative values too.
Parameter 5: Operation Mode
Operation mode. Using bit to control.Bit0: Disable the Flood function.Bit1: Reserve.Bit2: Reserve.Bit3: Setting the temperature scale. 0: Fahrenheit, 1:CelsiusBit4:
Reserve.Bit5: Disable the temperature report after event triggered. (1:Disable, 0:Enable)Bit6: Reserve.Bit7: Reserve.
Size: 1 Byte, Default Value: 0
Setting
1
8
32
Parameter 7: Customer Function
Size: 1 Byte, Default Value: 0
manual.zwave.eu/backend/make.php?lang=en&sku=PHIEPAT02-B
manual.zwave.eu/backend/make.php?lang=en&sku=PHIEPAT02-B
Maximum
Description
Nodes
8
The group 1 is for receiving the report message, like triggered event, temperature, humidity etc.
8
The group 2 is for the light control, the device will send the Basic Set command to this group. And
each group support 8 nodes maximum.
Description
Disable the Flood function.
Setting the temperature scale. 0: Fahrenheit, 1:Celsius
Disable the temperature report after event triggered. (1:Disable, 0:Enable)
4/7

Advertisement

loading