Changes for page Zūm Net Device Setup
Last modified by Alexander Mott on 2024/10/22 19:55
From version 50.2
edited by Alexander Mott
on 2024/10/15 14:14
on 2024/10/15 14:14
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -126,23 +126,6 @@ 126 126 127 127 Zūm Net devices have a two additional settings not present for other devices: Primary/Secondary mode and Zūm/Cresnet mode. ZUMNET-JBOX-DALI have a third setting for Group/Legacy DALI mode, and all ZUMNET-JBOX-* that are in CNET mode can optionally be configured to automatically switch back and forth between CNET and App mode depending on whether the control processor is reachable. 128 128 129 -== Updating Firmware == 130 - 131 -(% class="box errormessage" %) 132 -((( 133 -Per Crestron's Zūm Wired firmware v4.01.06.02 release notes, devices running firmware v3.09.05 or earlier "are not supported for upgrade via the Zum App / Hub / or Toolbox" and users should contact Crestron True Blue Support for upgrade paths when required. 134 -))) 135 - 136 -Updating firmware to the latest version is strongly recommended. The recommended process for updating Zūm Wired firmware is: 137 - 138 -1. Ensure that the ZUMNET-JBOX for the room is in Primary / Zūm Mode (see below) so that it will re-address all connected Zūm Link devices 139 -1. Connect to the ZUMNET-JBOX in Network Device Tree View to verify that all expected Zūm Link devices are online and that there are no conflicting or duplicate IDs 140 -1*. We have run into issues where devices will not always be uniquely addressed, typically as a result of cabling termination issues (incorrect pin-out or use of "EZ RJ45" passthrough connectors) 141 -1*. Occasionally, ZUMLINK-KP will be stuck at ID 03 after the ZUMNET-JBOX has been put into Primary/App Mode - in these cases, briefly disconnecting the keypad, reconnecting it, and waiting a few minutes will allow the keypad to be re-addressed 142 -1. adsf 143 - 144 -Alternatively, rooms can be updated through the Crestron Zūm App as of firmware v1.03.54, however only one room can be upgraded at a time and your mobile device will become occupied for the duration of the firmware upgrade (15-45 minutes depending on firmware version and quantity of Zūm Wired devices in the room) 145 - 146 146 == Primary/Secondary Mode == 147 147 148 148 (% class="box warningmessage" %) ... ... @@ -172,24 +172,8 @@ 172 172 173 173 == Zūm/Cresnet Mode == 174 174 175 -Zūm Mode (also known as App Mode) is the default setting for ZUMNET-JBOXs shipping on newer firmware, and allows them to be configured from the Crestron Zūm Appas long as a ZUMLINK-KP is connected to the JBOX. If a ZUMNET-JBOX is put into Cresnet mode, it will no longer be able to be configured using the Crestron Zūm App and all internal logic will be disabled.158 +Zūm Mode (also known as App Mode) is the default setting for new ZUMNET-JBOXs, and allows them to be configured from the Crestron Zūm App. If a ZUMNET-JBOX is put into Cresnet mode, it will no longer be able to be configured using the Crestron Zūm App and all internal logic will be disabled. Generally, Cresnet mode is only required if non-Zūm Link devices are connected to the ZUMNET-JBOX (e.g. a GL-EXP-DIMU-CN phase dimmer or C2N-CBD-P Cameo keypads) or if certain ShowRunnerCLC™ features are required (such as changing the dimming response curve). 176 176 177 -Generally, ZUMNET-JBOXs do not need to be in Cresnet mode to work with ShowRunnerCLC™ except in specific cases: 178 - 179 -* ZUMNET-JBOX-DALI controllers are being used in legacy mode 180 -* Site-specific security requirements do not allow for wireless connectivity to the lighting controls 181 -* Certain ShowRunnerCLC™ features are required (such as changing the dimming response curve) 182 -* On older versions of firmware, Cresnet mode was required if non-Zūm Link devices were connected to the ZUMNET-JBOX (e.g. a GL-EXP-DIMU-CN phase dimmer or C2N-CBD-P Cameo keypads) 183 -** This is no longer the case on recent firmware, and ZUMNET-JBOXs with Cresnet hardware connected to them can be left in Zūm/App mode, though the Cresnet hardware will not be able to function without the control processor 184 - 185 -When a ZUMNET-JBOX is in Zūm Mode and configured to communicate with a processor running ShowRunnerCLC™ software, it is operating in a kind of "App Plus" mode, where any actions that are defined in ShowRunnerCLC™ are performed "on top of" the actions defined in the App: 186 - 187 -* A keypad with actions defined in the Zūm App will perform actions defined in ShowRunnerCLC™ in addition to those App-defined actions while the ZUMNET-JBOX is in Zūm Mode 188 -** This is useful when trying to add functionality to a keypad, such as allowing the keypad to control devices not available in the Zūm App (e.g. shades, loads that are controlled by other ZUMNET-JBOXs or Cresnet load controllers, etc.), but can cause confusion in other situations where there are conflicts between the App-defined actions and the ShowRunnerCLC™-defined actions (e.g. if a rocker keypad with the default All On and All Off actions defined in the App is programmed in ShowRunnerCLC™ to act as a single load toggle, it will not work correctly) 189 -** A ZUMLINK-KP that is disabled from ShowRunnerCLC™ (i.e. by using the Keypad Disable function) will not perform any actions 190 -** A ZUMLINK-KP that has null actions defined in the Zūm App will only perform those actions that are defined in ShowRunnerCLC™ 191 -* If occupancy sensor load assignments in the App do not match ShowRunnerCLC™, then odd behavior may result 192 - 193 193 The commands to view or change the Zūm/Cresnet mode are: 194 194 195 195 * View current mode: ##zwmode##