Changes for page Zūm Net Device Setup

Last modified by Alexander Mott on 2024/10/22 19:55
From version 52.1
edited by Alexander Mott
on 2024/10/22 19:55
Change comment: There is no comment for this version
To version 49.1
edited by Alexander Mott
on 2024/01/05 18:49
Change comment: Renamed back-links.

Summary

Details

Page properties
Content
... ... @@ -126,39 +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 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 -Zūm Wired JBOXs operating as the Primary controller in App mode with firmware versions 4.x.x and above are limited in the number of secondary devices that can be supported on the Zūm Link bus:
136 -
137 -* ZUMNET-JBOX-DALI : 7 maximum secondary devices
138 -* ZUMNET-JBOX-~*~** : 14 maximum secondary devices
139 -* ZUMLINK-JBOX-~*~** : 14 maximum secondary devices
140 -
141 -These limitations do not apply to JBOXs operating in CNET mode //or// running firmware versions 3.x.x
142 -)))
143 -
144 -It is best practice to upgrade all Zūm Wired devices to the latest version, or at the very least update all devices to the same firmware version across the job. The recommended process for updating Zūm Wired firmware is:
145 -
146 -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
147 -1. Connect to the ZUMNET-JBOX in Network Device Tree View and verify that all expected Zūm Link devices are online and that there are no conflicting/duplicate IDs
148 -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)
149 -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's address to be changed
150 -1. Use the Zūm Wired .puf file or the Firmware Updating Script tool built into ShowRunner™ to update all the ZUMNET-JBOXs
151 -1*. Note that as part of the update process, the ZUMNET-JBOX will reboot, which will cycle the connected load and briefly interrupt Ethernet connection to any downstream ZUMNET-JBOXs or other Ethernet devices, which in rare instances will cause the firmware update to fail
152 -1. Verify that all the ZUMNET-JBOXs have successfully updated by using the Device Discovery Tool device export and checking the reported firmware version
153 -1. If any ZUMNET-JBOXs failed to update, try to update it again in case the update failure was caused by an upstream device rebooting
154 -1. If a ZUMNET-JBOX fails to update more than twice in a row, further investigation is required:
155 -1*. ZUMNET-JBOXs will update their firmware only after all connected Zūm Link devices have been successfully updated
156 -1**. If any connected Zūm Link devices have conflicting or duplicate IDs, the update will fail
157 -1**. Zūm Link cabling issues may also cause firmware updates to fail
158 -1*. An unstable network (Ethernet) connection to the ZUMNET-JBOX may also cause the update to fail
159 -
160 -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)
161 -
162 162  == Primary/Secondary Mode ==
163 163  
164 164  (% class="box warningmessage" %)
... ... @@ -188,24 +188,8 @@
188 188  
189 189  == Zūm/Cresnet Mode ==
190 190  
191 -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 App as 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).
192 192  
193 -Generally, ZUMNET-JBOXs do not need to be in Cresnet mode to work with ShowRunnerCLC™ except in specific cases:
194 -
195 -* ZUMNET-JBOX-DALI controllers are being used in legacy mode
196 -* Site-specific security requirements do not allow for wireless connectivity to the lighting controls
197 -* Certain ShowRunnerCLC™ features are required (such as changing the dimming response curve)
198 -* 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)
199 -** 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
200 -
201 -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:
202 -
203 -* 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
204 -** 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)
205 -** A ZUMLINK-KP that is disabled from ShowRunnerCLC™ (i.e. by using the Keypad Disable function) will not perform any actions
206 -** A ZUMLINK-KP that has null actions defined in the Zūm App will only perform those actions that are defined in ShowRunnerCLC™
207 -* If occupancy sensor load assignments in the App do not match ShowRunnerCLC™, then odd behavior may result
208 -
209 209  The commands to view or change the Zūm/Cresnet mode are:
210 210  
211 211  * View current mode: ##zwmode##