1. Overview This document provides guide lines and reference configurations for the physical inputs of ubisys ZigBee devices, like C4, D1(-R), S1(-R), S2(-R) and J1(-R). These are the same configurations offered via the ubisys Smart Home app for iOS and Android.
2. Introduction Most ubisys ZigBee devices with physical input contacts allow very flexible configuration of those inputs. For example, a mechanical switch with two stable positions can be connected to a single input and the input configured to send on commands in one position and off commands the other position, or toggle commands in each position.
3. Recipes 3.1. General Overview Please make yourself familiar with the ubisys device setup cluster first. A description of this cluster is available in the Technical Reference manuals of ubisys C4, D1(-R), S1(-R), S2(-R) and J1(-R). In a nutshell, this cluster allows configuration of binary inputs. It maps state transitions, e.g. “released” to “pressed”, to over-the-air application layer commands, e.g.
“toggle” command. 3.3.1. Example This would be a configuration for C4, which assigns each of the four inputs as a stationary switch (two stable positions) to a corresponding on/off cluster instance on the primary, secondary, tertiary, and quaternary level control switch endpoints.
Page 7
#1: six bytes 5 InputAndOptions: 0x00 6 Transition: released -> pressed 7 Source: Endpoint #1 (hosts primary on/off client cluster on C4) 8 06 00 Cluster ID: 0x0006 - on/off 9 ZCL Command Template: Toggle element #2: six bytes InputAndOptions: 0x00 Transition: any ->...
“off” command. 3.4.1. Example This would be a configuration for C4, which assigns each of the four inputs as a stationary switch (two stable positions) to a corresponding on/off cluster instance on the primary, secondary, tertiary, and quaternary level control switch endpoints.
Page 9
#1: six bytes 5 InputAndOptions: 0x00 6 Transition: released -> pressed 7 Source: Endpoint #1 (hosts primary on/off client cluster on C4) 8 06 00 Cluster ID: 0x0006 - on/off 9 ZCL Command Template: On element #2: six bytes InputAndOptions: 0x00 Transition: any ->...
3.5.1. Example This would be a configuration for C4, which assigns each of the four inputs as a momentary switch (one stable position) to a corresponding on/off cluster instance on the primary, secondary, tertiary, and quaternary level control switch endpoints.
3.7. Double Momentary Switch (Push Buttons) as Dimmer Switch Related C++ class: CZigBeeDeviceSetupInputPatternDoublePushLevel. This is a more complex recipe designed for dimming a light, or generally speaking adjusting the level (intensity, speed, brightness, …) of a level controllable output utilizing two momentary switches (push buttons, one stable position).
up direction, another one for the down direction. The idea is that each transition from the released state to the pressed state fires a “move up/open” command for the first button (“move down/close” command for the second button), and each transition from the pressed to the released state fires a “stop”...
Here, the blind moves as long as either switch is turned on. As soon as it is turned off, motion stops. The same approach can be applied to a C4, which allows two connect four switches and thus provides two window covering controllers (or a mix of one window covering controller plus one or two other functions).
“recall scene” command for another scene. 3.10.1. Example This would be a configuration for C4, which assigns each of the four inputs as a stationary switch (two stable positions) to a corresponding scene cluster instance on the primary, secondary, tertiary, and quaternary level control switch endpoints.
3.11.1. Example This would be a configuration for C4, which assigns each of the four inputs as a stationary switch (two stable positions) to a corresponding scene cluster instance on the primary, secondary, tertiary, and quaternary level control switch endpoints. Each switch can recall two separate scenes (they need not address the same group).
Page 20
#2: six bytes InputAndOptions: 0x00 Transition: pressed -> kept-pressed Source: Endpoint #1 (hosts primary scene client cluster on C4) 05 00 Cluster ID: 0x0005 - scenes 05 9a 78 bc ZCL Command Template: Recall scene, group ID = 0x789a, scene ID = ...
Page 21
& binding. For the raw functionality, it is not strictly required, though. [2] Qualified customers may license C (at least C11 language support is required) and Java classes from ubisys, which help with identification and assembly of usage patterns.
4. Revision History Revision Date Remarks 01/24/2013 Initial Version 12/19/2014 Added advanced support for recall scene command. Recall scene commands are now always sent to the group ID in the payload and don’t require an entry in the binding table 11/25/2014 Preliminary version (for internal use only).
Need help?
Do you have a question about the C4 and is the answer not in the manual?
Questions and answers