Skip to Content

Changes for page Zummesh Dynamic White/CCT

Last modified by Mark Kohlmann on 2026/01/08 20:58
From version 10.1
edited by Scott Kohlmann
on 2023/04/21 14:09
Change comment: There is no comment for this version
To version 13.1
edited by Mark Kohlmann
on 2026/01/08 16:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.scott\.kohlmann@chiefintegrations\.com
1 +XWiki.mark\.kohlmann@chiefintegrations\.com
Content
... ... @@ -1,5 +1,16 @@
1 -Zum wireless supports dynamic white using DALI Groups 2,4,6,8,10,12,14,16 (1,3,5,7,9,11,13,15 for console purposes).  Setup must be performed manually on the NETBRIDGE.  Once done, ShowRunner can use the CCT channels to provide CCT data to the fixtures.  Input from ShowRunnerCLC™ requires setting the scene recall for the CCT group to 255.  Any value of 0-254 will be sent to the CCT channel directly and the input from ShowRunnerCLC™ will be ignored.
1 +{{warning}}
2 +Caveats:
2 2  
4 +* Only intensity/CCT fixtures are supported.  This will not work with warm/cool fixtures.
5 +* NETBRIDGE must be attached to the ZUMMESH-JBOX-DALI.  Only 1 ZUMMESH-JBOX-DALI is supported per room.  Use Zum Wired or DIN-DALI-2/DIN-DLI if more capabilities are needed.
6 +* Supports up to 8 CCT channels, DALI Groups 2,4,6,8,10,12,14,16 on the Zum app (0 based - 1,3,5,7,9,11,13,15 for ShowRunner/console purposes)
7 +* Zum Scene must have the CCT channel set to 255 to accept input from ShowRunner.  Values of 0-254 will be sent directly to the group as fixed colors.
8 +* Setup must be done from the gateway console
9 +* **Loads must be manually changed to BusIndex 3 in the ShowRunner config or added from the UI with BusIndex 3.  Normally DALI loads are BusIndex 2.**
10 +{{/warning}}
11 +
12 +Zum wireless supports dynamic white using DALI Groups 2,4,6,8,10,12,14,16 (1,3,5,7,9,11,13,15 for ShowRunner/console purposes).  Setup must be performed manually on the NETBRIDGE.  Once done, ShowRunner can use the CCT channels to provide CCT data to the fixtures.  Input from ShowRunnerCLC™ requires setting the scene recall for the CCT group to 255.  Any value of 0-254 will be sent to the CCT channel directly and the input from ShowRunnerCLC™ will be ignored.
13 +
3 3  ==== Typical Setup for up to 6 zones, 5 fixture types: ====
4 4  
5 5  (% border="1" style="width:600px" %)
... ... @@ -21,33 +21,27 @@
21 21  |14|-|-|Intensity
22 22  |15|-|-|Color
23 23  
24 -==== Caveats: ====
25 -
26 -* Only intensity/CCT fixtures are supported.  This will not work with warm/cool fixtures.
27 -* NETBRIDGE must be attached to the ZUMMESH-JBOX-DALI.  Only 1 ZUMMESH-JBOX-DALI is supported per room.  Use Zum Wired or DIN-DALI-2 if more capabilities are needed.
28 -* Supports up to 8 CCT channels, DALI Groups 2,4,6,8,10,12,14,16 (1,3,5,7,9,11,13,15 for console purposes)
29 -* Zum Scene must have the CCT channel set to 255 to accept input from ShowRunner.  Values of 0-254 will be sent directly to the group as fixed colors.
30 -* Setup must be done from the gateway console
31 -
32 32  ==== Setup Steps: ====
33 33  
34 -1. Address all DALI drivers attached to the JBOX.  This can be done via the gateway console or via the Zum app on iOS/Android.
35 -Command: //rfrcon <**NetbridgeID**> DALIGLOBALADDRESS <**Action**>//
37 +1. (((
38 +Address all DALI drivers attached to the JBOX.  This can be done via the gateway console or via the Zum app on iOS/Android.
39 +##Command: //rfrcon <**NetbridgeID**> DALIGLOBALADDRESS <**Action**>//
36 36  **Action**: 0=stop, 1=start, 3=get status
37 -Example (NETBRIDGE RF-ID 1A): //rfrcon 1A DALIGLOBALADDRESS 1//
41 +Example (NETBRIDGE RF-ID 1A): //rfrcon 1A DALIGLOBALADDRESS 1//##
42 +)))
38 38  1. Create DALI Groups.  If group already exists then go to step 3. This must be done from the gateway console.
39 -Command: //rfrcon <**NetbridgeID**> DALIGROUPADDDELETE <**GroupID**> <**Operation**> <**GroupName**>//
44 +##Command: //rfrcon <**NetbridgeID**> DALIGROUPADDDELETE <**GroupID**> <**Operation**> <**GroupName**>//
40 40  **GroupID: **0 to 15
41 41  **Operation:** 0=Delete Group, 1=Add Intensity Group, 3=Add Color Group
42 42  **GroupName: **Name of the group, no spaces, 16 characters max
43 -Example (NETBRIDGE RF-ID 1A): //rfrcon 1A DALIGROUPADDDELETE 8 3 TypeF1-Color//
48 +Example (NETBRIDGE RF-ID 1A): //rfrcon 1A DALIGROUPADDDELETE 8 3 TypeF1-Color//##
44 44  1. Modify DALI Group to color, only needed if step 2 was not done.  If step 2 was performed skip this step.
45 -Command: //rfrcon <**NetbridgeID**> DALIGROUPSETTWRITE <**GroupID**> 14 <**GroupType**>//
50 +##Command: //rfrcon <**NetbridgeID**> DALIGROUPSETTWRITE <**GroupID**> 14 <**GroupType**>//
46 46  **GroupID: **0 to 15
47 47  **GroupType:** 0=Intensity, 1=Color
48 -Example: (NETBRIDGE RF-ID 1A): //rfrcon 1A DALIGROUPSETTWRITE 8 14 1//
53 +Example: (NETBRIDGE RF-ID 1A): //rfrcon 1A DALIGROUPSETTWRITE 8 14 1//##
49 49  1. Set Scene settings for Color Support.  Enables or uses a fixed value for color temperature on color groups.
50 -Command: rfrcon <**NetbridgeID**> DALIGROUPCOMMAND 4 <**GroupID**> <**SceneID**> <**SceneLevel**> <**Action**> <**FadeTime**>
55 +##Command: rfrcon <**NetbridgeID**> DALIGROUPCOMMAND 4 <**GroupID**> <**SceneID**> <**SceneLevel**> <**Action**> <**FadeTime**>
51 51  **GroupID**: 0 to 15 (odd for color)
52 52  **SceneID**: Scene number (1 to 16)
53 53  **SceneLevel**: 255 for ShowRunner control, 0-254 for fixed scene level
... ... @@ -54,4 +54,4 @@
54 54  **Action**: 0=Remove Scene, 1=Add Scene
55 55  **FadeTime**: Fade time in 1/10th of a second
56 56  Example (NETBRIDGE RF-ID 1A): //rfrcon 1A DALIGROUPCOMMAND 4 8 1 255 1 10//
57 -Example (NETBRIDGE RF-ID 1A): //rfrcon 1A DALIGROUPCOMMAND 4 15 1 255 1 10//
62 +Example (NETBRIDGE RF-ID 1A): //rfrcon 1A DALIGROUPCOMMAND 4 15 1 255 1 10//##