Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Related Manuals for Ubisys H1
Summary of Contents for Ubisys H1
- Page 1 ZIGBEE HEATING REGULATOR H1 REFERENCE MANUAL...
-
Page 2: Table Of Contents
5.3. Commissioning and operations on H1 .......... -
Page 3: Overview
1. Overview Thank you for purchasing the ubisys Heating Control H1. The H1 heating control is a smart, battery- powered radiator thermostat with integrated temperature sensor for radiator heating systems and is used for efficient room temperature control in private and commercial facilities. -
Page 4: Features
• On-board inverted-F antenna • Leverages ubisys Zigbee stack for best-in-class reliability and performance • Supports all channels in the 2.4 GHz band, i.e. channels 11-26 as per IEEE 802.15.4: Primary = { 11, 15, 20, 25 }; Secondary = { 12, 13, 14, 16, 17, 18, 19, 21, 22, 23, 24, 26 } •... -
Page 5: Installation
3. Installation Please refer to the installation guide of the product manual, which is included in the product package. It provides detailed installation instructions. -
Page 6: Initial Device Start-Up
After initial network commissioning to an open network succeeds, the quality of the Zigbee wireless connection is indicated in the upper left corner of H1’s display. the H1 will then prolong the joining window by three minutes by broadcasting a ZDO permit joining request command. -
Page 7: Man-Machine Interface (Mmi)
Figure 1, user can swiftly and effortlessly complete commissioning and operational tasks on the H1. The display succinctly showcases the progress and outcomes of a commissioning process, along with the temperature set-point and current operational status related to heating regulation, see e.g. - Page 8 Operation: Configure Weekly Schedule Create automated heating regulation based on pre-configured weekly set-point schedules. Note that, weekly schedules can be added, modified or removed not only through the MMI on the H1, but also upon receiving over-the-air ZCL commands from a management system.
-
Page 9: Interface
The label, on which this code is printed as a two-dimensional barcode (QR code), can be found on the inner surface of the housing, after removing the rotary dial of the device H1. The format specified in [R6], section 5.4.8.1.1, is used with a full 128-bit installation code + 16-bit CRC. -
Page 10: Application Endpoint #0 - Zigbee Device Object
The content string initiates with an EUI-64 address (prefixed by "Z:"). It is followed by a complete 128-bit installation code along with its 16-bit CRC checksum (prefixed by "I:"). Following that are the model identifier string "H1" (prefixed by "M:") and the manufacturer code 0x10f2 (prefixed by "M:"). 6.3. Application Endpoint #0 - Zigbee Device Object... -
Page 11: Application Endpoint #1 - Thermostat
6.4. Application Endpoint #1 - Thermostat Use this application endpoint to control the heating unit connected to output. This is a Finding & Binding initiator endpoint. The application endpoint exposes the following clusters: Cluster Direction Description 0x0000 Inbound Basic (Server) Provides basic information about the device, such as the manufacturer ID, vendor and model name, stack profile, ZCL version, production date, hardware revision etc. -
Page 12: Basic Cluster (Server)
Occupancy Sensing (Client) Receives attribute reports from other occupancy sensors. The ubisys ZigBee manufacturer ID is 0x10F2. This manufacturer code is used to identify OTA upgrade images, for accessing manufacturer-specific ZCL attributes and commands etc. 6.4.1. Basic Cluster (Server) The basic cluster might be accessible via more than one endpoint. Most of its attributes are singleton attributes, i.e. -
Page 13: Power Configuration Cluster (Server)
Query Identify Determines whether the device is currently identifying, and returns the remaining time if so. In the identify mode, the symbol as a F&B target will flash on the H1’s display for the specified identify duration. 6.4.4. Groups Cluster (Server) -
Page 14: Scenes Cluster (Server)
Attribute Type Description 0x0000 bitmap8, NameSupport read-only Always set to 0, this implementation does not support storing names for groups. 0xFFFD unsigned16 ClusterRevision The version of the cluster specification that this implementation adheres to. Cluster commands supported: Command Description 0x00 Add Group Adds the endpoint to a group. -
Page 15: Time Cluster (Server)
Command Description 0x06 Get Scene Membership Returns the set of scenes (within the scope of the specified group) currently stored on the device. 0x40 Enhanced Add Scene Similar to Add Scene with higher transition time resolution (10ths of a second instead of once second) 0x41 Enhanced View Scene Similar to View Scene with higher transition time resolution (10ths of a second instead of once second) -
Page 16: Thermostat Cluster (Server)
Represents the running mode of H1, i.e. the actual mode it is currently in. H1 supports “Off” and “Heat” the two options. 0x0020 enum8, StartOfWeek read-only Specifies the day of the week that H1 considers to be the start of week for weekly set point scheduling. “Monday” 0x0021 Unsigned8, NumberOfWeeklyTransitions read-only Specifies the number of weekly schedule transitions H1 is capable of handling. -
Page 17: Works With All Hubs Cluster (Server)
H1, becomes effective upon its reception. - Receiving this command, the H1 is enabled to create a new schedule if none available, add a new schedule to the existing ones or modify the existing ones on the associated days. - Page 18 ID 0xfc57 and manufacturer ID 0x1217 and can exist at most only once on each device node [R9]. This cluster provides an interface for enabling various features of the Works With All Hubs cluster on H1. Manufacturer-specific attributes supported:...
- Page 19 Attribute Type Description 0x0011 Unsigned8, PendingNetworkUpdateChannel read-only, This attribute describes the channel number of the only channel the device accepts in a ZDO Mgmt persistent Network Update command (and/or a Mgmt Network Enhanced Update command). 0x0012 Unsigned16, PendingNetworkUpdatePANID read-only, This attribute contains the only short PAN ID the device SHALL accept in a NLME Network Update persistent command.
-
Page 20: Identify Cluster (Client)
6.4.10. Identify Cluster (Client) The Identify cluster client takes on the role of the Finding & Binding initiator. Once activated, H1 initiates the identification process by broadcasting identify query request command to detect target(s) operating in identify mode. -
Page 21: Over-The-Air Upgrade Cluster (Client)
OTA server and back-end. If you operate the H1 together with the ZigBee/Ethernet Gateway ubisys G1, the latest firmware for H1 will always be available automatically and you do not need to request it explicitly. - Page 22 [1] Available in ZigBee stack version 1.60 and above. Legacy ZCP requirement – do not use in applications [2] Available in Zigbee stack version 1.56 and above. [3] Available in Zigbee stack version 1.61 and above. [4] Attribute ID changed since application version 1.5.0. Prior, it used to be 0x0003. [5] Attribute ID changed since application version 1.5.0.
-
Page 23: Thermostat Heating Setpoints Schedules
The Option 3 is always accessible. 7.2. Format of setpoint schedules If you create a setpoint schedule using the MMI on H1, the internally applied and stored schedule format, the so-called schedule slot format, is implemented. It differs sometimes slightly from the one... -
Page 24: Number Of Daily Heating Setpoint Schedules
- On H1 through MMI, this type of schedule slot is only applicable to a specified combination of week days. When transmitting a ZCL Thermostat cluster... -
Page 25: Examples
These over-the-air ZCL Thermostat cluster commands should be always sent to the endpoint and cluster 0x0201 of a target H1. For creating the ZCL Thermostat cluster SetWeeklySchedule command, both the schedule slot and the ZCL standard schedule transition formats for schedule configuration are showcased. - Page 26 ModeToReturn set 0x01 (Heat) • Example 4. Set the heating setpoint schedules for specific weekdays ◦ Set three heating setpoints on all workdays utilizing the ubisys schedule slot format: Following settings are intended on H1: Heating Period Parameter Value Start Time...
- Page 27 ▪ the new schedules will be applied ▪ the just added schedules can be modified either via MMI on H1 or upon receipt of further over-the-air ZCL thermostat schedule commands ▪ the heating regulation on the specified weekdays occurs according to these new schedules ▪...
- Page 28 ZCL standard schedule transition format, ▪ all currently stored schedules will be removed, if they are defined in the ubisys schedule slot format, if any ▪ the currently stored schedules for Monday to Friday will be replaced by the ones given in the received command frame, if any and applying the same standard transition format ▪...
-
Page 29: Physical Dimension
8. Physical Dimension Figure 3. Heating Control H1 – Dimensions If the ubisys heating control H1 does not fit on the valve of your radiator, you will probably need an adapter. The valve adapter is mounted between the H1 and your ... -
Page 30: Information
Orders for products sold under different brand names need to be placed with the respective vendor. For any customized versions, please contact ubisys sales. OEM customers may order these products with the dimming mode pre-configured to either “automatic”, “leading edge” or “trailing edge”. -
Page 31: General Terms & Conditions Of Business
10. General Terms & Conditions Of Business When placing your order you agree to be bound by our General Terms & Conditions of Business, “Allgemeine Geschäftsbedingungen”, which are available for download here: www.ubisys.de/en/smarthome/terms.html... -
Page 32: Declaration Of Conformity
11. Declaration Of Conformity We – ubisys technologies GmbH, Neumannstraße 10, 40235 Düsseldorf, Germany – declare under our sole responsibility that the ubisys Heating Regulator H1 with order codes as detailed in Chapter 9 under the trade name “ubisys” to which this declaration relates are in conformity with the following... -
Page 33: Revision History
12. Revision History Revision Date Remarks 17/08/2022 Initial draft 04/12/2023 Initial Public Version... -
Page 34: Contact
13. Contact ubisys technologies GmbH Neumannstr. 10 40235 Düsseldorf Germany T: +49. 211. 54 21 55 - 19 F: +49. 211. 54 21 55 - 99 www.ubisys.de info@ubisys.de...