Skip to Content

Changes for page Zūm Discovery

Last modified by Austin Weygandt on 2025/05/02 20:21
From version 5.1
edited by Alexander Mott
on 2022/09/22 21:55
Change comment: There is no comment for this version
To version 12.1
edited by Alexander Mott
on 2022/10/06 14:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Zūm Autodiscovery
1 +Zūm Discovery
Content
... ... @@ -1,6 +1,6 @@
1 1  (% class="box warningmessage" %)
2 2  (((
3 -This article is about automatically building a SHOWRUNNER™ configuration using the Zūm Autodiscovery feature of SHOWRUNNER™. 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]].
3 +This article is about automatically building a SHOWRUNNER™ configuration using the Zūm Discovery feature of SHOWRUNNER™. 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]].
4 4  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]].
5 5  )))
6 6  
... ... @@ -8,67 +8,109 @@
8 8  {{toc/}}
9 9  {{/box}}
10 10  
11 -(% class="row" %)
12 -(((
13 -If Zūm Net devices have been configured using Crestron's Zūm App
11 +If Zūm Wired or Wireless devices have been configured using Crestron's Zūm App, then it is possible to automatically build a SHOWRUNNER™ configuration file using the Zūm Discovery feature that is built into SHOWRUNNER™.
14 14  
15 -= Zūm Wired =
13 +There are certain pre-requisites and limitations when building a SHOWRUNNER™ configuration this way, and it may sometimes be necessary make some adjustments to the final configuration, such as changing keypad types and moving loads between areas.
16 16  
17 -Lorem
15 += Zūm Wired Discovery =
18 18  
19 -= Zūm Wireless =
17 +== Notes and Limitations ==
20 20  
21 -As of version 2.190 ShowRunner can discover RF Gateways and attached Zum NETBRIDGES. ShowRunner will find all devices, set them up, create areas and loads.
22 -*Disconnect from the gateway before discovery as they cannot support multiple connections*
23 -*Plug loads do not appear in the UI*
19 +(% class="box errormessage" %)
20 +(((
21 +* SHOWRUNNER™ version 3.014 or newer required
22 +* Zūm Wired firmware version 1.02.10 or greater required
23 +* Disconnect from any ZUMNET devices you may be connected to in Toolbox prior to running the discovery commands
24 +* Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release)
25 +* One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually
26 +)))
24 24  
25 -== Pre-Requisites: ==
28 +== Steps ==
26 26  
27 -* Zum NETBRIDGES acquired to their respective gateway (CEN-GWEXER/ZUMNET-GATEWAY)
28 -* SHOWRUNNER™ installed and running on a 3-series processor on the same network as the gateway
29 -* NETBRIDGES do not need to have addresses assigned. SHOWRUNNER™ will automatically address them. If devices all already addressed then their addresses will be honored.
30 +1. [[Install SHOWRUNNER™>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.WebHome]] on the processor and configure the processor as necessary
31 +1*. Note that while Zūm Wired discovery will build a configuration, if a configuration file was provided then it should still be loaded as it may contain location data or non-Zūm devices.
32 +1. If the ZUMNET-JBOX firmware is too out-of-date to connect using the Crestron Zūm App, then there are some additional steps required: 
33 +1*. Connect to the first ZUMNET-JBOX in Toolbox
34 +1*. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 
35 +1**. Note: The SHOWRUNNER™ built-in DHCP server is not meant to be used in production
36 +1**. If the SHOWRUNNER™ built-in DHCP server was used to assign IP addresses to devices, it is still necessary to give those devices static IP addresses
37 +1*. Set unique Connection IDs for each device hosted on the ZUMNET-JBOX so that their firmware can be updated
38 +1*. Load the Zūm Wired firmware to the ZUMNET-JBOX
39 +1*. Repeat the above steps for all ZUMNET-JBOXs
40 +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
41 +1. Connect to first ZUMNET-JBOX in the Crestron Zūm App
42 +1. Unique Connection IDs should be automatically assigned to any Zūm Link and Cresnet devices on the ZUMNET-JBOX
43 +1*. If firmware was out-of-date, then this step should have already been completed
44 +1*. If unique CIDs are not automatically assigned, connect to the JBOX in Toolbox and give the devices unique CIDs
45 +1. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 
46 +1*. If firmware was out-of-date, then this step should have already been completed
47 +1*. Note: The SHOWRUNNER™ built-in DHCP server is not meant to be used in production
48 +1*. If the SHOWRUNNER™ built-in DHCP server was used to assign IP addresses to devices, it is still necessary to give those devices static IP addresses
49 +1. Optionally, manually configure the ZUMNET-JBOX IP table to point at the processor if you want to keep track of which ZUMNET-JBOX is at each IP-ID
50 +1*. If you do not manually configure the IP table, then SHOWRUNNER™ will automatically configure the IP-ID for each ZUMNET-JBOX during discovery
51 +1. Repeat from step 3 until all ZUMNET-JBOXs that are to be controlled by SHOWRUNNER™ have static IP addresses and unique CIDs for any hosted devices
52 +1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox
53 +1. Run the command: ##sr discover zumnet true false##
54 +1*. This command tells SHOWRUNNER™ to discover all ZUMMNET-JBOXs on the network, configure their IP tables, and then add corresponding IP Devices to the configuration
55 +1. Run the command: ##sr discover zumnet true true##
56 +1*. This command tells SHOWRUNNER™ to discover all Zūm Link hardware (including the internal ZUMNET-JBOX load controller) on the previously discovered Zūm Net devices and then add corresponding areas, loads, sensors, etc. to the configuration
57 +1**. One area will be created per ZUMNET-JBOX, and all hardware attached to that ZUMNET-JBOX will be assigned to that area
58 +1*. This command **does not** bring in Cresnet devices: those must be added to the configuration manually until this issue is fixed in the Zūm Wired firmware
59 +1. Put all ZUMNET-JBOXs into CNET mode in order to allow full control from SHOWRUNNER™
60 +1*. Odd behavior may result from conflicts between SHOWRUNNER™ and internal logic if the ZUMNET-JBOXs are not put into CNET mode
61 +
62 += Zūm Wireless Discovery =
63 +
64 +== Notes and Limitations ==
65 +
66 +(% class="box errormessage" %)
67 +(((
68 +* Processor with SHOWRUNNER™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired
69 +** For SHOWRUNNER™ versions prior to 3.014 and newer, replace **##sr discover zummesh##** commands with **##sr discover zum##**
70 +* ZUM-NETBRIDGES must already be acquired to their respective gateway
71 +* SHOWRUNNER™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices
72 +* Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command
73 +* Plug loads will not appear in the SHOWRUNNER™ UI
30 30  )))
31 31  
32 32  (% class="box warningmessage" id="HCaution:" %)
33 33  (((
34 -**Note:** SHOWRUNNER™ has two different approaches for Zūm Wireless Autodiscovery
78 +**Note:** SHOWRUNNER™ has two different approaches for Zūm Wireless Discovery
35 35  
36 36  1. **Manual RF Gateway Assignment** - SHOWRUNNER™ can be told which gateways it should scan. Use this approach if you have gateways that are used by multiple systems on the same local network.
37 37  1. **Claim All RF Gateways** - SHOWRUNNER™ will find all CEN-GWEXERs [ZUMNET-GATEWAY] on the network and will claim them as its own. **DO NOT** use this method if there are gateways used by different SHOWRUNNER™ or other Crestron systems on the same local network.
38 38  )))
39 39  
40 -(% class="row" %)
41 -(((
42 -== Manual RF Gateway Claiming ==
84 +== Manual RF Gateway Assignment Instructions ==
43 43  
44 44  Use this method if you have multiple SHOWRUNNER™ instances on the same network or have gateways used by other Crestron systems.
45 45  
46 46  * Connect to the processor's console with Toolbox or your favorite SSH client.
47 -* Type "//sr devmgr ethernet query//" and press enter. This queries the local network for RF Gateways.
48 -* Type "//sr devmgr ethernet show devices//" and press enter. This displays all found Crestron ethernet devices.
49 -* For each gateway that you'd like this instance of SHOWRUNNER™ to use, use the hostname from the table of found ethernet devices. For example if the gateway Hostname is CEN-GWEXER-9E6ADA type "//sr ethernet device claim CEN-GWEXER-9E6ADA//". SHOWRUNNER™ will auto-assign an IP-ID. After all gateways have been claimed by SHOWRUNNER™, proceed to the next step.
50 -* Type "//sr discover zum false//" and press enter.
89 +* Type ##sr devmgr ethernet query## and press enter. This queries the local network for RF Gateways.
90 +* Type ##sr devmgr ethernet show devices## and press enter. This displays all found Crestron ethernet devices.
91 +* For each gateway that you'd like this instance of SHOWRUNNER™ to use, use the hostname from the table of found ethernet devices. For example if the gateway Hostname is CEN-GWEXER-9E6ADA type ##sr ethernet device claim CEN-GWEXER-9E6ADA##. SHOWRUNNER™ will auto-assign an IP-ID. After all gateways have been claimed by SHOWRUNNER™, proceed to the next step.
92 +* Type ##sr discover zummesh false## and press enter.
51 51  * Status messages and the results will be displayed on the console. The process should take about 3 minutes.
52 -* When the discovery is finished type "//sr save//" and press enter to save the updated config. Due to an unknown quirk that we are looking into, SHOWRUNNER™ must be restarted to complete the acquire process.
53 -* Type "//progreset//" and press enter to restart SHOWRUNNER™
54 -* Once SHOWRUNNER™ has finished restarting type "//sr discover zum false//" and press enter. SHOWRUNNER™ will be able to acquire the loads attached to the Zūm rooms at this point.
94 +* When the discovery is finished type ##sr save## and press enter to save the updated config. Due to an unknown quirk that we are looking into, SHOWRUNNER™ must be restarted to complete the acquire process.
95 +* Type ##progreset## and press enter to restart SHOWRUNNER™
96 +* Once SHOWRUNNER™ has finished restarting type ##sr discover zummesh false## and press enter. SHOWRUNNER™ will be able to acquire the loads attached to the Zūm rooms at this point.
55 55  * Once completed SHOWRUNNER™ is now ready for full Zūm control
56 56  
57 -== Claim All RF Gateways ==
99 +== Claim All RF Gateways Instructions ==
58 58  
59 59  Use this method when you have a single SHOWRUNNER™ instance on a local network with all gateways being used for SHOWRUNNER™.
60 60  
61 61  * Connect to the processor's console with Toolbox or your favorite SSH client.
62 -* Type "//sr discover zum true//" and press enter.
104 +* Type ##sr discover zummesh true## and press enter.
63 63  * Status messages and the results will be displayed on the console. The process should take about 3 minutes.
64 -* When the discovery is finished type "//sr save//" and press enter to save the updated config. Due to an unknown quirk that we are looking into, SHOWRUNNER™ must be restarted to complete the acquire process.
65 -* Type "//progreset//" and press enter to restart SHOWRUNNER™
66 -* Once SHOWRUNNER™ has finished restarting type "//sr discover zum false//" and press enter. SHOWRUNNER™ will be able to acquire the loads attached to the Zūm rooms at this point.
106 +* When the discovery is finished type ##sr save## and press enter to save the updated config. Due to an unknown quirk that we are looking into, SHOWRUNNER™ must be restarted to complete the acquire process.
107 +* Type ##progreset## and press enter to restart SHOWRUNNER™
108 +* Once SHOWRUNNER™ has finished restarting type ##sr discover zummesh false## and press enter. SHOWRUNNER™ will be able to acquire the loads attached to the Zūm rooms at this point.
67 67  * Once completed SHOWRUNNER™ is now ready for full Zūm control
68 68  
69 69  == Examples ==
70 70  
71 -=== Claim Selectively (Manual) Example ===
113 +=== Manual Example ===
72 72  
73 73  {{{MC4>sr devmgr ethernet query
74 74  Ethrenet AutoDiscovery Result: AutoDiscoveryOperationSuccess
... ... @@ -87,7 +87,7 @@
87 87  MC4>sr ethernet device claim CEN-GWEXER-9E6ADA
88 88  Claimed ethernet device: CEN-GWEXER-9E6ADA
89 89  MC4>Update request from IP-ID-30 in Program 01
90 -MC4>sr discover zum false
132 +MC4>sr discover zummesh false
91 91  Starting Zum Discovery without gateway claiming
92 92  MC4>Performing Discovery on 1 Gateways.
93 93  Evaluating 3 Devices on Gateway 30
... ... @@ -120,7 +120,7 @@
120 120  MC4>progreset
121 121  ...
122 122  CI ShowRunner startup completed successfully in 8072ms
123 -MC4>sr discover zum false
165 +MC4>sr discover zummesh false
124 124  Starting Zum Discovery without gateway claiming
125 125  MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable)
126 126  Performing Discovery on 1 Gateways.
... ... @@ -173,7 +173,7 @@
173 173  
174 174  === Claim All Example ===
175 175  
176 -{{{MC4>sr discover zum true
218 +{{{MC4>sr discover zummesh true
177 177  Starting Zum Discovery with gateway claiming
178 178  MC4>Found 1 Gateways to check.
179 179  Claimed Gateway SN: 1720JBH04269 at IP-ID: 30
... ... @@ -209,7 +209,7 @@
209 209  MC4>progreset
210 210  ...
211 211  CI ShowRunner startup completed successfully in 8072ms
212 -MC4>sr discover zum false
254 +MC4>sr discover zummesh false
213 213  Starting Zum Discovery without gateway claiming
214 214  MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable)
215 215  Performing Discovery on 1 Gateways.
... ... @@ -260,4 +260,3 @@
260 260  Removed Loads: 0
261 261  Zum Discovery Finished
262 262  }}}
263 -)))