Skip to Content

Changes for page Zūm Net Device Setup

Last modified by Alexander Mott on 2025/07/10 21:27
From version 50.2
edited by Alexander Mott
on 2024/10/15 14:14
Change comment: There is no comment for this version
To version 54.2
edited by Alexander Mott
on 2025/07/10 21:24
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,8 +1,7 @@
1 -(% class="box warningmessage" %)
2 -(((
1 +{{warning}}
3 3  This article is for configuring Zūm Net devices using Crestron Toolbox. For instructions on configuring Zūm Wired rooms using the Crestron Zūm App, see [[this page>>SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Zūm App Overview.WebHome]].
4 4  For details on using the Zūm Discovery feature to automatically build a ShowRunnerCLC™ configuration based on the Zūm App settings, see [[this page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Program Configuration.Zūm Discovery.WebHome]].
5 -)))
4 +{{/warning}}
6 6  
7 7  {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
8 8  {{toc/}}
... ... @@ -128,28 +128,42 @@
128 128  
129 129  == Updating Firmware ==
130 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 -)))
130 +{{error}}
131 +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.
135 135  
136 -Updating firmware to the latest version is strongly recommended. The recommended process for updating Zūm Wired firmware is:
133 +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:
137 137  
135 +* ZUMNET-JBOX-DALI : 7 maximum secondary devices
136 +* ZUMNET-JBOX-~*~** : 14 maximum secondary devices
137 +* ZUMLINK-JBOX-~*~** : 14 maximum secondary devices
138 +
139 +These limitations do not apply to JBOXs operating in CNET mode //or// running firmware versions 3.x.x
140 +{{/error}}
141 +
142 +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:
143 +
138 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
145 +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
140 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
147 +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
148 +1. Use the Zūm Wired .puf file or the Firmware Updating Script tool built into ShowRunner™ to update all the ZUMNET-JBOXs
149 +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
150 +1. Verify that all the ZUMNET-JBOXs have successfully updated by using the Device Discovery Tool device export and checking the reported firmware version
151 +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
152 +1. If a ZUMNET-JBOX fails to update more than twice in a row, further investigation is required:
153 +1*. ZUMNET-JBOXs will update their firmware only after all connected Zūm Link devices have been successfully updated
154 +1**. If any connected Zūm Link devices have conflicting or duplicate IDs, the update will fail
155 +1**. Zūm Link cabling issues may also cause firmware updates to fail
156 +1*. An unstable network (Ethernet) connection to the ZUMNET-JBOX may also cause the update to fail
143 143  
144 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 145  
146 146  == Primary/Secondary Mode ==
147 147  
148 -(% class="box warningmessage" %)
149 -(((
162 +{{warning}}
150 150  Zūm Wired firmware v1.03.27 (device firmware v1.002.00026) updates the terminology from "master"/"slave" to "primary"/"secondary", and changes the ##zwms## command to ##zwps##
151 151  Devices running this newer firmware will not accept commands using "master"/"slave" as arguments.
152 -)))
165 +{{/warning}}
153 153  
154 154  ZUMNET-JBOXs can be in either "Primary" or "Secondary" mode. In most situations, "Primary" is the desired mode of operations, as "Secondary" mode effectively turns a ZUMNET-JBOX into a ZUMLINK-JBOX and prevents it from discovering devices on the Zūm Link bus or performing any logic. There are two scenarios in which a ZUMNET-JBOX should be configured in "Secondary" mode:
155 155  
... ... @@ -172,6 +172,10 @@
172 172  
173 173  == Zūm/Cresnet Mode ==
174 174  
188 +{{error}}
189 +ZUMNET-JBOXs on firmware 4.x.x and above that exceed the maximum allowable ZUMLINK device count must be kept in CNET mode and not be allowed into Zūm Mode.
190 +{{/error}}
191 +
175 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 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.
176 176  
177 177  Generally, ZUMNET-JBOXs do not need to be in Cresnet mode to work with ShowRunnerCLC™ except in specific cases:
... ... @@ -209,6 +209,12 @@
209 209  
210 210  === Zūm Mode Auto Switch ===
211 211  
229 +{{error}}ZUMNET-JBOXs on firmware 4.x.x and above that exceed the maximum allowable ZUMLINK device count must not have Auto Switch enabled. Doing so will result in unintended behavior, including improper app mode functionality and excessive rebooting once reconnected to the processor.
230 +{{/error}}
231 +
232 +{{warning}}With Auto Switch enabled, ZUMNET-JBOXs may overwrite the ShowRunnerCLC™ scenes upon reconnecting to the processor: disable auto switch or set scenes both in the App and in ShowRunnerCLC™ to avoid this issue
233 +{{/warning}}
234 +
212 212  Zūm Mode Auto Switch is a feature introduced by Crestron in November of 2022 with .puf firmware v1.04.05 (device firmware 1.004.00005). This feature is intended to address concerns that arose from projects using custom programs with ZUMNET-JBOX-* devices in CNET Mode. Previously, if a device in CNET Mode lost connection to the processor, then it would be impossible to maintain any sort of control over the lighting. With Zūm Mode Auto Switch enabled, a ZUMNET-JBOX running in CNET Mode will automatically switch to App Mode and process local logic in the event that it loses connection to the processor.
213 213  
214 214  Note that on 0-10V and switched JBOXs, the connected loads will flash once when rebooting. On ZUMNET-DALI-JBOX models, the JBOX will reboot once when switching to App mode and twice when switching back to CNET mode (once to switch to CNET, and a second time to switch to Legacy DALI mode)