Changes for page Zūm Discovery

Last modified by Alexander Mott on 2025/04/03 17:35

From version 19.1
edited by Scott Kohlmann
on 2023/04/21 13:58
Change comment: There is no comment for this version
To version 27.1
edited by Craig Lewis
on 2024/05/29 15:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.WebHome
1 +SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Program Configuration.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.scott\.kohlmann@chiefintegrations\.com
1 +XWiki.craig\.lewis@chiefintegrations\.com
Content
... ... @@ -1,13 +1,14 @@
1 1  (% class="box errormessage" %)
2 2  (((
3 -WARNING: Cresnet Discovery is not currently working on ZUMNET-JBOXs. Crestron has acknowledged a fix has been sent to QE.
3 +**IMPORTANT:** When using ShowRunnerCLC™ with a ZUM-HUB4, **do not** discover Zūm Rooms using the Crestron HUB4 Web UI. During discovery, the HUB4 will claim ZUMNET-JBOXs and prevent ShowRunnerCLC™ from auto-discovering or registering the Zūm hardware for itself.
4 4  
5 -Downgrade ShowRunnerCLC™ to v3.018 in order to auto-discover hardware. ShowRunnerCLC™ can be subsequently upgraded once discovery is complete.
5 +**WARNING:** Cresnet Discovery is non-functional for ZUMNET-JBOXs with certain versions of Crestron Device Database.
6 +ShowRunnerCLC™ versions v3.019 through v3.041 must be either downgraded to v3.018 or upgraded to v3.042 or newer in order to perform auto-discover functions.
6 6  )))
7 7  
8 8  (% class="box warningmessage" %)
9 9  (((
10 -This article is about automatically building a ShowRunnerCLC™ configuration using the Zūm Discovery feature of ShowRunnerCLC™. For instructions on configuring Zūm Wired rooms using the Crestron Zūm App, see [[this page>>SHOWRUNNER™ Setup Guide.Wiring Guide.Zūm Wired System Overview.Crestron Zūm App Overview.WebHome]].
11 +This article is about automatically building a ShowRunnerCLC™ configuration using the Zūm Discovery feature of ShowRunnerCLC™. 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]].
11 11  For instructions on configuring Zūm Net devices using Crestron Toolbox, see [[this page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.ZUMNET-JBOX Setup.WebHome]].
12 12  )))
13 13  
... ... @@ -29,6 +29,7 @@
29 29  * Zūm Wired firmware .puf version 1.02.10 or greater required (ZUMNET-JBOX installed minimum version 1.001.00081)
30 30  * Disconnect from any ZUMNET devices you may be connected to in Toolbox prior to running the discovery commands
31 31  * Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release)
33 +* ZUMLINK-KPs will not be discovered (Expected to be discoverable in future release)
32 32  * One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually
33 33  )))
34 34  
... ... @@ -45,7 +45,13 @@
45 45  1*. Load the Zūm Wired firmware to the ZUMNET-JBOX
46 46  1*. Repeat the above steps for all ZUMNET-JBOXs
47 47  1*. Once all the ZUMNET-JBOXs have pushed the new firmware to their hosted devices, disconnect from them in Toolbox and proceed to the next step
48 -1. Connect to first ZUMNET-JBOX in the Crestron Zūm App
50 +1. Connect to each ZUMNET-JBOX in the Crestron Zūm App
51 +1*. Commission room through the app
52 +1**. configure keypad logic
53 +1**. configure occupancy sensor settings
54 +1**. calibrate photocell(s)
55 +1*. Set hostnames for the ZUMNETs.
56 +1**. Zūm discovery will bring in hostnames.
49 49  1. Unique Connection IDs should be automatically assigned to any Zūm Link and Cresnet devices on the ZUMNET-JBOX
50 50  1*. If firmware was out-of-date, then this step should have already been completed
51 51  1*. If unique CIDs are not automatically assigned, connect to the JBOX in Toolbox and give the devices unique CIDs