DEVELCO PRODUCTS HESZB-110 Heat Alarm Instruction Manual

Heat Alarm – HESZB-120
Technical manual
Revised 06.12.2017

HESZB-110 Heat Alarm

Copyright © Develco Products A/S
All rights reserved.
Develco Products assumes no responsibility for any errors, which may appear in this manual. Furthermore, Develco Products reserves the right to alter the hardware, software, and/or specifications detailed herein at any time without notice, and Develco Products does not make any commitment to update the information contained herein.
All the trademarks listed herein are owned by their respective owners.

Cautionary notes

Develco Products A/S reserves the right to make changes to any product to improve reliability without further notice. Develco Products A/S does not assume any liability arising out of the application or use of any product or circuit described herein; neither does it convey any license under patent rights or the rights of third parties.

Features

2.1 Heat Alarm – HESZB-120
Temperature monitoring for optimal fire detection.
With the Heat Alarm from Develco Products, you will never have to worry about fire in your home again. The Heat Alarm can be installed where smoke or fumes are part of the atmosphere to prevent false alarms.
A heat based fire alarm is specifically useful in environments where a traditional optical smoke sensor can cause false detections. This Heat Alarm is designed for installation in private homes or garages with risk for smoky, dusty, or humid environment, as for  example kitchen area, living room with wooden stove burner, garage area, washing and drying area.
The thermo sensitive detector with wireless communication detects both rapidly increased heat and absolute heat levels. It will alert you about fire with a loud sound as a warning or via a smart home solution.
The Heat Alarm is battery powered and easily mounted to the ceiling
2.2 IAS Zone
The Heat Alarm is implemented as a IAS Zone ZigBee end point according to ZigBee Home Automation profile “IAS Zone”.
2.3 Temperature
The temperature sensor measures temperature with a resolution of 0.1°C.
It supports standard ZigBee reporting (on change or interval).
The end point is configured as the Home Automation profile “Temperature Sensor”

2.4 Key features
Key features are:

• Alarm sensor – IAS Zone
• Warning device – IAS WD
• Binary Input cluster
• Temperature sensor
• Certified ZigBee Home Automation application profile
• ZigBee PRO is supported
• RoHS compliant according to the EU Directive 2002/95/EC.
• Standard ZigBee Home Automation security and stack settings are used

Endpoints

The device implements the following standard HA devices on different end points.

3.1 ZigBee Device Object (ZDO)

• End point number 0x00
• Application profile Id 0x0000
• Application device Id 0x0000
• Supports all mandatory clusters

3.2 IAS Zone

• End point number 0x23
• Application profile Id 0x0104 (Home Automation)
• Application device Id 0x0402

3.3 Temperature Sensor

• End point number 0x26
• Application profile Id 0x0104 (Home Automation)
• Application device Id 0x0302

3.4 Develco Utility

• Application profile Id 0xC0C9 (Develco Products private profile)
• Application device Id 0x0001
• Manufactor code for Develco Products is 0x1015
• Private profile for internal Develco Products use only.

Reference documents:
053474r18ZB_CSG-ZigBee-Specification.pdf
075123r03ZB_AFG-ZigBee_Cluster_Library_Specification.pdf
053520r27ZB_HA_PTG-Home-Automation-Profile.pdf
075356r15ZB_ZSE-ZSE-AMI_Profile_Specification.pdf
They can all be downloaded from: http://www.zigbee.org/Products/DownloadZigBeeTechnicalDocuments.aspx

Supported Clusters

4.1 Common clusters for each end point
The ZCL “General Function Domain” clusters in this section are implemented as server clusters. Refer to ZigBee Cluster Library Specification. http://www.zigbee.org/Specifications.aspx
4.1.1 Basic – Cluster id 0x0000
Only the first set has mandatory attributes, also the optional attributes that can be relevant to a Develco Products’ device are all in set 0x000
4.1.1.1 Attribute

4.1.1.1.1 ManufacturerName
“Develco Products A/S”
4.1.1.1.2 ModelIdentifier
“HESZB-120”
4.1.1.2 Manufacture Specific Attribute

ZCL header setting – Manufactor code for Develco Products is 0x1015
4.1.2 Identify – Cluster id 0x0003
4.1.2.1 Attribute

4.1.2.2 Commands
The identify cluster has 2 commands as server.

The identify cluster has 1 command as client.

4.2 IAS Zone Device – EP 0x23
4.2.1 IAS Zone – Cluster id 0x0500
The IAS Zone cluster is described in ZigBee Cluster Library Specification
4.2.1.1 Attribute

Bit0: Alarm 1
Bit3: Battery (30 days left)
Bit4: Supervision reports
Bit5: Restore reports
Bit 8: Test
0x0010| IAS CIE Address| Valid 64-bit IEEE address| M|
0x0011| ZoneID| Uint8| M|

4.2.1.1.1 Zone State
The device will automatically start to scan the network for an IAS Zone client in a predefine interval. When the client is found it will automatically attempt to enrol. When it has successfully enrolled the Zone Status command is send every 5 minutes.
The attribute value will change from not enrolled (0x00) to Enrolled (0x01)
4.2.1.1.2 IAS CIE Address
Attribute specifies the address that commands generated by the server shall be sent to.
To un-enroll the device the back end system has to write a new address into this attribute. Any value is valid. If the back end system writes an IEEE adr then it will try to enrol to this devices represented by the IEEE adr.
4.2.1.1.3 ZoneID
A unique reference number allocated by the CIE at zone enrollment time.
Used by IAS devices to reference specific zones when communicating with the CIE. The ZoneID of each zone stays fixed until that zone is unenrolled
4.2.1.2 Commands
The IAS Zone cluster has 2 commands as server.

report to the coordinator every 5 min
0x01| Zone Enroll Request| Bits| 16| 16| M|
Data type| 16 bit enum| UINT16
Field name| Zone type| Manufacturer code

Init sequence – when the device has join the network it start to scan for an IAS zone client cluster. If a client is found a Zone enroll request command is send and a Zone Enroll response is expected. If it doesn’t receive a response within 15 sec it gives up and will continue to scan x number of attempts. When the init sequence is over it will enter a state where it scans for a client every 12 hour.
The following bits are supported in Zone status:
Bit0: Alarm 1
Bit3: Battery
Bit4: Supervision reports
Bit5: Restore reports
Bit8: Test
Note: How to clear a alarm in the “Zone status”
The sensor requests ZCL Default Response on the Zone Status Change notification, if any new Alarm bit has been set. Until the IAS CIE has acknowledged the received alarm by sending the mandated Default Response, the Alarm bits are not cleared – even if there is no longer an alarm situation. When the Default Response is received, a new Zone Status Change notification is sent with the Alarm bits cleared, if the alarm situation has disappeared since sending the Zone Status message with alarm set.
Bit3: When the battery is below 2.8 VDC. Battery bit is set high and “Zone Status” is transmitted to the coordinator.
4.2.2 Power Configuration – Cluster id 0x0001
The power configuration cluster is described in ZigBee Cluster Library Specification
4.2.2.1 Attribute

supported
0x0031| BatterySize| enum8| CR123A (0x08)| O|
0x0033| BatteryQuantity| Uint8| 1| O|
0x0034| BatteryRatedVoltage| Uint8| 30| O| Unit is in 100 mV
0x0036| Battery Voltage Min Thres hold| Uint8| 25| | Unit is in 100 mV
0x003E| BatteryAlarmState| Map32| | O| Bit0: BatteryVoltageMinThreshold Is set if BatteryVoltage has been below
BatteryVoltageMinThreshold or other internal circuits has deemed the supply to be inadequate.
This bit will only reset after a power cycle.
The condition will also be shown on the MMI LED, see MMI description.
Reportable. Default Min 12 hours, max 12 hours

Note: The attribute “BatteryVoltage” is measuring the battery voltage, in units of 100mV.
4.2.3 Poll Control – Cluster id 0x0020
The poll control cluster is described in ZigBee Cluster Library Specification
This cluster provides a mechanism for the management of an end device’s MAC Data Request rate. For the purposes of this cluster, the term “poll” always refers to the sending of a MAC Data Request from the end device to the end device’s parent.
This cluster can be used for instance by a configuration device to make an end device responsive for a certain period of time so that the device can be managed by the controller.
4.2.3.1 Attribute

Start up, auto scan for client poll control cluster on the coordinator. If it is support on the coordinator an auto bind is created and the heat alarm will send a check-in command in the interval specified in attribute “Check- inInterval.
The coordinator has to reply with a check-in response. The sensor supports the following commands send from the client (Typically the coordinator).

• 0x00 Check-in Response,
• 0x01 Fast Poll Stop,
• 0x02 Set Long Poll Interval,
• 0x03 Set Short Poll Interval,

If it doesn’t find a poll client it will search again periodically.
4.2.4 IAS WD – Cluster id 0x0502
The IAS WD cluster is described in ZigBee Cluster Library Specification.
Using this cluster, a ZigBee device can access a ZigBee enabled IAS WD device and issue alarm warning indications (heat siren) when a system alarm condition is detected.
4.2.4.1 Attribute

The MaxDuration attribute specifies the maximum time in seconds that the siren will sound continuously, regardless of start/stop commands.
4.2.4.2 Commands
The IAS WD cluster has 1 command as server.

4.2.4.2.1 Command – Start warning
This command starts the WD operation. The WD alerts the surrounding area by audible (siren).
The Start Warning command payload shall be formatted as illustrated

1 = Siren On
Warning duration| 2 byte| Warning duration is sec

Note: The start warning command doesn’t set the alarm bit in the IAS Zone status.
The alarm is only triggered if the devices detect fire.
4.2.5 OTA Upgrade – Cluster id 0x0019
The cluster provides a ZigBee standard way to upgrade devices in the network via OTA messages. The devices support the client side of the cluster.
When the devices has joined a network it will automatically auto scan for a OTA upgrade server in the network. If it finds a server an auto bind is created and ones every 24 hour it will automatically send its “current file version” to the OTA upgrade server. It is the server that initiate the firmware upgrade process.

Above attribute description is to be found in section 6.7 “OTA Cluster Attributes” in ZigBee document – “zigbeeota-upgrade-cluster-specification” provided by the ZigBee alliance.
4.2.5.2 Commands
The OTA Client cluster can send the following commands

4.2.5.3 OTA Upgrade Messages Diagram

4.2.6 Time – Cluster id 0x000A
The Time cluster is a general cluster for time it is based on a UTC time in seconds since 0 hrs 0 mins 0 sec on 1st January 2000. Refer to [Z2] for ZigBee specification of the time cluster.
The device will use this clusters as a client – provided that a suitable Time Server is available on the network (most likely on the Gateway)
4.2.6.1 Attribute

update its clock by synchronizing through this cluster
0x0001| TimeStatus| 8 bit bitmap| 00000xxx| M|

4.2.7 Binary Input Cluster – Cluster id 0x000F
The Binary input cluster is described in ZigBee Cluster Library Specification
4.2.7.1 Attribute

will no longer follow the physical input, but will be writeable
0x0055| PresentValue| Bool| False (0) or True (1)| M| Reflects the state of the Heat alarm, unless it is disabled by setting the OutOfService attribute to True.
Reportable. Default Min 1 sec, max 10 min
0x0067| Reliabillity| Enum8| | O| 0 – No Fault Detected Reportable.
0x006F| StatusFlag| Map8| 0x00-0x0F| M| Bit1:  Fault.  If  set,  the  source can be read in the Reliability attribute Reportable. Default Min 1 sec, max 10 min

4.3 Temperature Sensor Device – EP 0x26
4.3.1 Temperature Measurement – Cluster id 0x0402
The temperature measurement cluster is described in ZigBee Cluster Library Specification section 4.4
4.3.1.1 Attribute

4.3.1.1.1 MeasuredValue
Default reporting is set to
Min reporting interval: 60 sec
Max reporting interval: 600 sec
Reportable Change: 0.1 °C
If the temperature value is stable it will be send every 10 minutes.
If the temperature changes more than 0.1 °C it will be reported but not faster than every 1 minute since last reporting value.
Note: Min reporting interval 0 sec is invalid when reportable change is configured.
4.3.1.1.2 MinMeasuredValue
The temperature sensor is NOT supporting temperature measurements below 0 degrees Celsius 4.3.1.1.3 MaxMeasuredValue
The temperature sensor is NOT supporting temperature measurements above 50 degrees Celsius

MMI user guide

5.1 Push Button Menu
Pushing the button on a device provides the user with several possibilities.
Pushing the button for longer (push, hold for a few seconds, and release) allows the user to set the device into a desired mode. A mode change happens at 5 second interval. Below, these modes are illustrated in a state chart.When cycling through the menu modes, the state is indicated by a number of 100ms blinks on the LED. The device is supporting the ZigBee standardized EZ- mode Commissioning.
5.1.1 EZ mode – Initiator
If the devices is not on the network EZ-Mode Network Steering is invoked when the user enter this menu. The led blinks once every 1 sec until the devices has joined the network. If the device was already on the network it will broadcast the PermitJoin messages. It is the trust center policy that decides if the device is allowed to join the network.
When the device has joined the network EZ-Mode Finding and Binding is invoked and the device start to blink every 3 sec until a cluster match is found. When a match is found or the cluster examine is finished the blinking stops and the device sends a messages to the target device to stop the identify time.
The following clusters are support in EZ-mode finding and binding:

• Temperature cluster
• Power configuration cluster

The EZ-mode time is hard coded to 3 minutes. This is the Minimum and recommended PermitJoin time broadcast for EZ-Mode Network Steering and minimum IdentifyTime set for EZ-Mode Finding and Binding. If the user enters the menu again another 3 minutes is started.
5.1.2 EZ mode – Target
If the devices is not on the network EZ-Mode Network Steering is invoked when the user enter this menu. The led blinks twice every 1 sec until the devices has joined the network. If the device was already on the network it will broadcast the PermitJoin messages. It is the trust center policy that decides if the device is allowed to join the network.
When the device has joined the network identify mode is invoke and the device start to blink twice every 3 sec until identify mode is stopped or after the EZ-mode time has expired. If the user enters the menu again another 3 minutes is started.
5.1.3 Factory reset
To allow a device to join a network, one either has to power up a device that has not previously joined a network or push the button until the Reset To Factory default mode is indicated – and subsequently release the button.
This will cause the device to reset to its factory default state and scan for a suitable coordinator.
5.2 Action on Power On
As a general rule, all end devices and routers that have not previously joined a network (or have been reset to factory default) will start up and search for a network with join permit open. In this mode, the LED will flash once every second.
Once the device has joined the network, is will start scanning for an OTA server, Time server, Poll control client and an IAS Zone client.
If a device has joined a network and is powered down, it will attempt to rejoin this network upon power up. For the first 30 seconds hereafter, the device will be available for communication. This time can be expanded using the poll control cluster functionality.

General network behaviour

6.1 Installation
When the device is virgin and powered for the first time it will start looking for a ZigBee PAN Coordinator or router to join. The device will scan each ZigBee channel starting from 11 to 24. The LED will flash once every second until it joins a device.

#Scan mode – 1
Scan all 16 ZigBee channels until join network or 15 minutes| #Sleep mode
MCU is in sleep mode (Radio off) 15 minutes| #Scan mode – 2
Scan all 16 ZigBee ch x 1 or until join network ~ 30 seconds| #Sleep mode
MCU is in sleep mode (Radio off) 15 minutes| #Scan mode – 2
Scan all 16 ZigBee chx 1 or until join network ~ 30 seconds
---|---|---|---|---

The device will start up using scan mode 1. To increase battery lifetime when the device is joining a network for the first time a scan mode 2 will be used after scan mode 1 has expired. Scan mode 1 it will only be executed one time when the device is powered. If the user invokes EZ-mode it will start scanning the next 3 minutes In section 5 “MMI” it is explained how to put the device into a join or leave network mode.
Network settings are stored in NV-memory are after a power cycle the device re-join the same network.
If the device has to join a new PAN coordinator the MMI menu supports a “Reset To Factory Fresh Settings” mode. This will erase all current network information.
6.2 Normal – Keep alive
The device is sending a “keep alive” message to the PAN coordinator every 15 minute to verify that the device is still connected to the network.
6.2.1 Network lost
If no “keep alive” responses are received 5 times in a row (Worst case 1h15m), the devices will start scanning as specified in the table below.
When the device is in scan mode the LED will flash once every second until it re-joins the network.
According to the ZigBee specification TX is NOT allowed to be enabled all the time and a TX silent period has to be defined.

#Scan mode – 1
Scan current ch 3 times Scan remaining 15 ch 1 time Scan all 16 ch 3 times
#Sleep mode
MCU is in sleep mode (Radio off) 15 minutes
#Scan mode – 2
Scan current ch 3 times
Scan remaining 15 ch 1 time
#Sleep mode
MCU is in sleep
mode (Radio off) 15 minutes
#Scan mode – 2
Scan current ch 3 times
Scan remaining 15 ch 1 time

6.3 Low battery
The current battery voltage can be read from the power configuration cluster described in section 4.3.1. The attribute “BatteryVoltage” is measuring the battery voltage, in units of 100mV.
Low batt LED indication – RED LED will blink twice every 60 second

Specifications

General|
---|---
Dimensions (Ø x H)| Ø 65 x 40 mm
Colour| White
Power supply| Battery: 1 x CR123 exchangeable
| Battery life: up to 5 years, 5 minutes reporting
Radio| Sensitivity: -98 dBm
| Output power: +8 dBm
Environment| IP class: IP20
| Operation temperature 0 to +50°C
| Relative humidity up to 95% non-condensing
Range| Minimum 100 meters (open field)
Function|
Heat sensor| Heat based fire sensing
| Siren output 85dB/3m
Temperature sensor| Range: 0 to +50°C
| Resolution: 0.1°C (accuracy: ±0.5°C)
| Sample time: config.: 2s – 65,000s
| Reporting: configurable
Communication|
Wireless protocol| ZigBee HA 1.2 certified
| ZigBee end-device
Certifications|
| RoHS compliant according to the EU Directive 2002/95/EC
| DIN EN 14604 and DIN 14676 certified

Contact Information

Technical support:
Please contact Develco Products for support.
products@develcoproducts.com
Sales:
Please contact Develco Products for information on prices, availability, and lead time.
info@develcoproducts.com

Develco Products A/S
Olof Palmes Allé 40
DK-8200 Aarhus N
http://develcoproducts.com
info@develcoproducts.com

References

• Develco Products - White label products for security, home care, and energy management.

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>