Changes for page Crestron Zūm Wireless
Last modified by Scott Kohlmann on 2023/04/20 22:28
From version 24.1
edited by Mark Kohlmann
on 2021/03/17 16:24
on 2021/03/17 16:24
Change comment:
There is no comment for this version
To version 17.1
edited by Mark Kohlmann
on 2020/11/10 18:58
on 2020/11/10 18:58
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -2,7 +2,7 @@ 2 2 3 3 ==== Integration Options ==== 4 4 5 -* **SHOWRUNNER™ Total Control** - The most comprehensive option. Allows seamless (see [[Caveats>>||anchor="caveats"]])integration of Zūm and non-Zūm Crestron lighting control products. Extensive feature set allows centralized control and management of Zūm rooms. Advanced scheduler provides more flexibility to the facility operator. This solution replaces the ZUM-FLOOR-HUB in the system design.5 +* **SHOWRUNNER™ Total Control** - The most comprehensive option. Allows seamless integration of Zūm and non-Zūm Crestron lighting control products. Extensive feature set allows centralized control and management of Zūm rooms. Advanced scheduler provides more flexibility to the facility operator. This solution replaces the ZUM-FLOOR-HUB in the system design. 6 6 * **SHOWRUNNER™ + AVBRIDGE + Serial Port** - Provides scene setting and load control via a dedicated AVBRIDGE in each Zūm room. Requires a dedicated serial port (C2N-IO/CEN-IO-COM2/etc) and a dedicated ZUMMESH-AVBRIDGE per room. 7 7 * **SHOWRUNNER™ + ZUM-FLOOR-HUB** - Provides limited scene recall and room status for Zūm rooms paired with the Floor Hub. SHOWRUNNER™ can export its own areas to the Floor Hub. 8 8 ... ... @@ -29,7 +29,7 @@ 29 29 |Scene Recall|Y ~*~*~*~*|Y ~*~*~*~*|Y|Y|Y 30 30 |Override Fade Time for Scene Recall ~*~*|Y|N|N|N|N 31 31 |Scene Save|Y ~*~*~*~*|Y ~*~*~*~*|N|N|Y 32 -|Load Control|Y ~*~** /~*~*~*~**|Y ~*~**|N|N|Y32 +|Load Control|Y ~*~**|Y ~*~**|N|N|Y 33 33 |Demand Response|Y|N|Y, separate triggers for SHOWRUNNER™ and ZUM-FLOOR-HUB required|Y|N 34 34 |Enable/Disable Occupancy|Y|Y|Y, from Floor Hub|Y|Y 35 35 |Override Occupancy Logic|Y|Y|N|N|N ... ... @@ -126,43 +126,19 @@ 126 126 SHOWRUNNER™: Y 127 127 Floor Hub: N 128 128 )))|N|N/A 129 -|Minimum NETBRIDGE Firmware|v1.12.0130 (PUF Zum MESHNET v1.06.09)|v1.010|N/A|See Crestron|See Crestron 130 -|Minimum Gateway Firmware|v1.4469.00011|N/A|N/A|See Crestron|See Crestron 131 -|Minimum SHOWRUNNER™ Version|2.198|2.198|N/A|N/A|N/A 132 132 133 133 {{{* Zūm Setup App works as long as the NETBRIDGE is physically near the iOS/Android device running the Zūm Setup App. 134 -** Fade time is automatically applied if scene is set longer than 1 second. Must be triggered from SHOWRUNNER™, cannot be triggered from Zūm keypad with current firmware (as of April 2020). 135 -*** Zūm wireless does not support direct coupling of fade times and the behavior is different internally within the dimmer versus other Crestron products. Raise/Lower level accuracy is not guaranteed. For best performance when settings scenes, set the slider manually which will send exact levels to the dimmer. 136 -**** Zūm wireless scenes cannot presently be read on command. Scenes should be created and saved from SHOWRUNNER™ directly. Saved scenes are stored directly on the Zūm wireless dimmer and in ShowRunner. ShowRunner will query the NETBRIDGE after scene recall and attempt to build scene information but operations are done one at a time. 137 - ***** Zūm wireless real time load status is not available. Any changes to loads performed using the raise/lower functions in room will not be propagated back to ShowRunner. Levels set by the daylight sensor with daylighting enabled will not be reported by ShowRunner.}}}131 +** Fade time is automatically applied if scene is set longer than 1 second. Must be triggered from SHOWRUNNER™, cannot be triggered from Zūm keypad with current firmware (as of April 2020). 132 +*** Zūm wireless does not support direct coupling of fade times and the behavior is different internally within the dimmer versus other Crestron products. Raise/Lower level accuracy is not guaranteed. For best performance when settings scenes, set the slider manually which will send exact levels to the dimmer. 133 +**** Zūm wireless scenes cannot presently be read on command. Scenes should be created and saved from SHOWRUNNER™ directly. Saved scenes are stored directly on the Zūm wireless dimmer and in ShowRunner. ShowRunner will query the NETBRIDGE after scene recall and attempt to build scene information but operations are done one at a time. 134 +}}} 138 138 139 -{{id name="caveats"/}} 140 - 141 141 ==== Caveats ==== 142 142 143 -* Consult Chief Integrations to verify sequence of operations if there are any concerns. Zum wireless is not a direct replacement for Crestron wired and infiNET EX wireless products. 144 144 * Zum Wireless has an internal rate limit that will shutdown communication if a number of commands are received in a short period of time. This can be seen when repeatedly pressing buttons on a keypad as well as repeatedly triggering actions from ShowRunner. 145 145 * Raise/Lower operations from ShowRunner cannot track directly with the load response, see ~*~** above. ShowRunner will poll the NETBRIDGE for current levels ~~3 seconds after the raise/lower is stopped to obtain current load levels. 146 146 * Lower operations can turn the load off. The load will not come on with a raise. This is a firmware behavior in the Zum hardware. 147 147 * Wireless control presents some additional latency possibilities. Commands required to provide full functionality (load control/raise/lower) with Zum wireless are more intensive than traditional Crestron hardware and may impact performance under heavy load. Local operation of the Zum wireless room is not impacted. 148 -* Real time load status is not available. Any changes to loads performed using the raise/lower functions in room will not be propagated back to ShowRunner. Levels set by the daylight sensor with daylighting enabled will not be reported by ShowRunner. 149 -* Keypad behaviors cannot be modified. Custom keypads can be implemented using the AVBRIDGE connected to the system via a serial port, Zum requires an AV specific keypad for this purpose. 150 -* Zum Partition Sensors do not report back to the system and cannot be used to handle room divide/combine logic. 151 -* Off Scene cannot be saved and is always room Off 152 -* Scenes 1 through 16 are supported and may be modified and saved. 153 -* Scenes with fade times greater than 1 second will result in loads being commanded individual from ShowRunner and may not be in sync depending on load quantity, RF gateway load, and RF signal integrity. Zum hardware does not support a fade time as part of the Scene setting. Fade times must be commanded from ShowRunner. Scene fade times will be ignored when scenes are activated by Zum keypads or internal occupancy logic. 154 -* Saving scenes from ShowRunner captures the levels set in ShowRunner at the time of the save. ShowRunner will attempt to learn scenes as they are recalled. 155 -* Override/Override Level features are not supported 156 -* Load disable is not supported 157 -* After hours logic is not supported 158 -* Blink before timeout is not supported 159 -* CCT control is presently not supported (ZUMMESH-JBOX-DALI support may be available in the future) 160 -* RGB loads are not supported 161 -* Minimum/Maximum Levels are not supported when loads are being recalled locally. ShowRunner will honor them when control occurs from ShowRunner except for raise/lower which is peformed on hardware. 162 -* Dimming curves are not supported when loads are being recalled locally. Use Zum app to adjust dimming curves if necessary. Recommended to leave ShowRunner dimming curve set to "Unaffected". 163 -* BACNET support requires a processor hardware license and ShowRunner BACNET license. BACNET point availability can be configured per Area. 164 -* Chief Integrations recommends one 3-series processor per building floor at a minimum. 165 -* Zummesh and infiNET EX devices are not officially supported on the same gateway, discuss with Crestron if needing both. 166 166 167 167 (% id="HTopologies" %) 168 168 ==== Topologies ====