Skip to Content

Changes for page Zūm Discovery

Last modified by Austin Weygandt on 2025/05/02 20:21
From version 4.1
edited by Alexander Mott
on 2022/09/22 21:50
Change comment: There is no comment for this version
To version 8.1
edited by Alexander Mott
on 2022/09/23 00:00
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  
... ... @@ -10,29 +10,69 @@
10 10  
11 11  (% class="row" %)
12 12  (((
13 -If Zūm Net devices have been configured using Crestron's Zūm App
13 +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 =
15 +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
17 += Zūm Wired Discovery =
18 18  
19 -= Zūm Wireless =
19 +== Notes and Limitations ==
20 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
21 21  
22 -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.
23 -*Disconnect from the gateway before discovery as they cannot support multiple connections*
24 -*Plug loads do not appear in the UI*
27 +== Steps ==
25 25  
26 -== Pre-Requisites: ==
29 +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
30 +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.
31 +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: 
32 +1*. Connect to the first ZUMNET-JBOX in Toolbox
33 +1*. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 
34 +1**. Note: The SHOWRUNNER™ built-in DHCP server is not meant to be used in production
35 +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
36 +1*. Set unique Connection IDs for each device hosted on the ZUMNET-JBOX so that their firmware can be updated
37 +1*. Load the Zūm Wired firmware to the ZUMNET-JBOX
38 +1*. Repeat the above steps for all ZUMNET-JBOXs
39 +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
40 +1. Connect to first ZUMNET-JBOX in the Crestron Zūm App
41 +1. Unique Connection IDs should be automatically assigned to any Zūm Link and Cresnet devices on the ZUMNET-JBOX
42 +1*. If firmware was out-of-date, then this step should have already been completed
43 +1*. If unique CIDs are not automatically assigned, connect to the JBOX in Toolbox and give the devices unique CIDs
44 +1. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 
45 +1*. If firmware was out-of-date, then this step should have already been completed
46 +1*. Note: The SHOWRUNNER™ built-in DHCP server is not meant to be used in production
47 +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
48 +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
49 +1*. If you do not manually configure the IP table, then SHOWRUNNER™ will automatically configure the IP-ID for each ZUMNET-JBOX during discovery
50 +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
51 +1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox
52 +1. Run the command: ##sr discover zumnet true false##
53 +1*. This command tells SHOWRUNNER™ to discover all ZUMMNET-JBOXs on the network, configure their IP tables, and then add corresponding areas and loads to the configuration
54 +1*. One area will be created per ZUMNET-JBOX
55 +1. Run the command: ##sr discover zumnet true true##
56 +1*. This command tells SHOWRUNNER™ to discover all Zūm Link hardware on the previously discovered Zūm Net devices
57 +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
58 +1. Put all ZUMNET-JBOXs into CNET mode in order to allow full control from SHOWRUNNER™
59 +1*. Odd behavior may result from conflicts between SHOWRUNNER™ and internal logic if the ZUMNET-JBOXs are not put into CNET mode
27 27  
28 -* Zum NETBRIDGES acquired to their respective gateway (CEN-GWEXER/ZUMNET-GATEWAY)
29 -* ShowRunner installed and running on a 3-series processor on the same network as the gateway
30 -* NETBRIDGES do not need to have addresses assigned. ShowRunner will automatically address them. If devices all already addressed then their addresses will be honored.
61 += Zūm Wireless Discovery =
62 +
63 +== Notes and Limitations ==
64 +
65 +* Processor with SHOWRUNNER™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired
66 +** For SHOWRUNNER™ versions 3.014 and newer, replace ##sr discover zum## commands with ##sr discover zummesh##
67 +* ZUM-NETBRIDGES must already be acquired to their respective gateway
68 +* SHOWRUNNER™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices
69 +* Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command
70 +* Plug loads will not appear in the SHOWRUNNER™ UI
31 31  )))
32 32  
33 33  (% class="box warningmessage" id="HCaution:" %)
34 34  (((
35 -**Note:** SHOWRUNNER™ has two different approaches for Zūm Wireless Autodiscovery
75 +**Note:** SHOWRUNNER™ has two different approaches for Zūm Wireless Discovery
36 36  
37 37  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.
38 38  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.
... ... @@ -40,38 +40,37 @@
40 40  
41 41  (% class="row" %)
42 42  (((
43 -== Option 1: Manual RF Gateway Claiming: ==
83 +== Manual RF Gateway Assignment Instructions ==
44 44  
45 -Use this method if you have multiple ShowRunner instances on the same network or have gateways used by other Crestron systems.
85 +Use this method if you have multiple SHOWRUNNER™ instances on the same network or have gateways used by other Crestron systems.
46 46  
47 47  * Connect to the processor's console with Toolbox or your favorite SSH client.
48 48  * Type "//sr devmgr ethernet query//" and press enter. This queries the local network for RF Gateways.
49 49  * Type "//sr devmgr ethernet show devices//" and press enter. This displays all found Crestron ethernet devices.
50 -* 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.
90 +* 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.
51 51  * Type "//sr discover zum false//" and press enter.
52 -* Status messages and the results will be displayed on the console. The process should take about 3 minutes.
53 -* 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.
54 -* Type "//progreset//" and press enter to restart ShowRunner
55 -* Once ShowRunner has finished restarting type "//sr discover zum false//" and press enter. ShowRunner will be able to acquire the loads attached to the Zum rooms at this point.
56 -* Once completed ShowRunner is now ready for full Zum control
92 +* Status messages and the results will be displayed on the console. The process should take about 3 minutes.
93 +* 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.
94 +* Type "//progreset//" and press enter to restart SHOWRUNNER™
95 +* 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.
96 +* Once completed SHOWRUNNER™ is now ready for full Zūm control
57 57  
58 -== Option 2: Claim All Gateways: ==
98 +== Claim All RF Gateways Instructions ==
59 59  
60 -Use this method when you have a single ShowRunner instance on a local network with all gateways being used for ShowRunner.
100 +Use this method when you have a single SHOWRUNNER™ instance on a local network with all gateways being used for SHOWRUNNER™.
61 61  
62 62  * Connect to the processor's console with Toolbox or your favorite SSH client.
63 63  * Type "//sr discover zum true//" and press enter.
64 -* Status messages and the results will be displayed on the console. The process should take about 3 minutes.
65 -* 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.
66 -* Type "//progreset//" and press enter to restart ShowRunner
67 -* Once ShowRunner has finished restarting type "//sr discover zum false//" and press enter. ShowRunner will be able to acquire the loads attached to the Zum rooms at this point.
68 -* Once completed ShowRunner is now ready for full Zum control
104 +* Status messages and the results will be displayed on the console. The process should take about 3 minutes.
105 +* 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.
106 +* Type "//progreset//" and press enter to restart SHOWRUNNER™
107 +* 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.
108 +* Once completed SHOWRUNNER™ is now ready for full Zūm control
69 69  
70 70  == Examples ==
71 71  
112 +=== Manual Example ===
72 72  
73 -=== Example for Option 1: ===
74 -
75 75  {{{MC4>sr devmgr ethernet query
76 76  Ethrenet AutoDiscovery Result: AutoDiscoveryOperationSuccess
77 77  MC4>sr devmgr ethernet show devices
... ... @@ -173,7 +173,7 @@
173 173  Removed Loads: 0
174 174  Zum Discovery Finished}}}
175 175  
176 -=== Example for Option 2: ===
215 +=== Claim All Example ===
177 177  
178 178  {{{MC4>sr discover zum true
179 179  Starting Zum Discovery with gateway claiming