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
on 2022/09/22 21:50
Change comment:
There is no comment for this version
To version 9.1
edited by Alexander Mott
on 2022/10/05 16:17
on 2022/10/05 16:17
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Zūm Autodiscovery1 +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,75 @@ 10 10 11 11 (% class="row" %) 12 12 ((( 13 -If Zūm Netdevices have been configured using Crestron's Zūm App13 +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 - Lorem17 += Zūm Wired Discovery = 18 18 19 -= ZūmWireless=19 +== Notes and Limitations == 20 20 21 +(% class="box errormessage" %) 22 +((( 23 +* SHOWRUNNER™ version 3.014 or newer required 24 +* Zūm Wired firmware version 1.02.10 or greater required 25 +* Disconnect from any ZUMNET devices you may be connected to in Toolbox prior to running the discovery commands 26 +* Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release) 27 +* One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually 28 +))) 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* 30 +== Steps == 25 25 26 -== Pre-Requisites: == 32 +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 33 +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. 34 +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: 35 +1*. Connect to the first ZUMNET-JBOX in Toolbox 36 +1*. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 37 +1**. Note: The SHOWRUNNER™ built-in DHCP server is not meant to be used in production 38 +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 39 +1*. Set unique Connection IDs for each device hosted on the ZUMNET-JBOX so that their firmware can be updated 40 +1*. Load the Zūm Wired firmware to the ZUMNET-JBOX 41 +1*. Repeat the above steps for all ZUMNET-JBOXs 42 +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 43 +1. Connect to first ZUMNET-JBOX in the Crestron Zūm App 44 +1. Unique Connection IDs should be automatically assigned to any Zūm Link and Cresnet devices on the ZUMNET-JBOX 45 +1*. If firmware was out-of-date, then this step should have already been completed 46 +1*. If unique CIDs are not automatically assigned, connect to the JBOX in Toolbox and give the devices unique CIDs 47 +1. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 48 +1*. If firmware was out-of-date, then this step should have already been completed 49 +1*. Note: The SHOWRUNNER™ built-in DHCP server is not meant to be used in production 50 +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 51 +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 52 +1*. If you do not manually configure the IP table, then SHOWRUNNER™ will automatically configure the IP-ID for each ZUMNET-JBOX during discovery 53 +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 54 +1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox 55 +1. Run the command: ##sr discover zumnet true false## 56 +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 57 +1*. One area will be created per ZUMNET-JBOX 58 +1. Run the command: ##sr discover zumnet true true## 59 +1*. This command tells SHOWRUNNER™ to discover all Zūm Link hardware on the previously discovered Zūm Net devices 60 +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 61 +1. Put all ZUMNET-JBOXs into CNET mode in order to allow full control from SHOWRUNNER™ 62 +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 - *ZumNETBRIDGES acquired to theirrespectivegateway(CEN-GWEXER/ZUMNET-GATEWAY)29 - * ShowRunner installed and running on a 3-series processor on the same network as the gateway30 - *NETBRIDGES donotneed to have addressesassigned.ShowRunner will automatically addressthem. If devicesall already addressedthen their addresses will be honored.64 += Zūm Wireless Discovery = 65 + 66 +== Notes and Limitations == 31 31 ))) 32 32 69 +(% class="box errormessage" %) 70 +((( 71 +* Processor with SHOWRUNNER™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired 72 +** For SHOWRUNNER™ versions prior to 3.014 and newer, replace **##sr discover zummesh##** commands with **##sr discover zum##** 73 +* ZUM-NETBRIDGES must already be acquired to their respective gateway 74 +* SHOWRUNNER™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices 75 +* Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command 76 +* Plug loads will not appear in the SHOWRUNNER™ UI 77 +))) 78 + 33 33 (% class="box warningmessage" id="HCaution:" %) 34 34 ((( 35 -**Note:** SHOWRUNNER™ has two different approaches for Zūm Wireless Autodiscovery81 +**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 GatewayClaiming:==89 +== Manual RF Gateway Assignment Instructions == 44 44 45 -Use this method if you have multiple S howRunnerinstances on the same network or have gateways used by other Crestron systems.91 +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 -* Type "//sr devmgr ethernet query//"and press enter. This queries the local network for RF Gateways.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 S howRunnerto use, use the hostname from the table of found ethernet devices."//sr ethernet device claim CEN-GWEXER-9E6ADA//".howRunnerwill auto-assign an IP-ID.howRunnerproceed to the next step.51 -* Type "//sr discover zum false//"and press enter.52 -* Status messages and the results will be displayed on the console. 53 -* When the discovery is finished type "//sr save//"and press enter to save the updated config.howRunnermust be restarted to complete the acquire process.54 -* Type "//progreset//"and press enter to restart ShowRunner55 -* Once S howRunnerhas finished restarting type"//sr discover zum false//"and press enter.howRunnerwill be able to acquire the loads attached to the Zum rooms at this point.56 -* Once completed S howRunneris now ready for full Zum control94 +* Type ##sr devmgr ethernet query## and press enter. This queries the local network for RF Gateways. 95 +* Type ##sr devmgr ethernet show devices## and press enter. This displays all found Crestron ethernet devices. 96 +* 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. 97 +* Type ##sr discover zummesh false## and press enter. 98 +* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 99 +* 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. 100 +* Type ##progreset## and press enter to restart SHOWRUNNER™ 101 +* 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. 102 +* Once completed SHOWRUNNER™ is now ready for full Zūm control 57 57 58 -== Option 2:Claim All Gateways:==104 +== Claim All RF Gateways Instructions == 59 59 60 -Use this method when you have a single S howRunnerinstance on a local network with all gateways being used for ShowRunner.106 +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 -* Type "//sr discover zum true//"and press enter.64 -* Status messages and the results will be displayed on the console. 65 -* When the discovery is finished type "//sr save//"and press enter to save the updated config.howRunnermust be restarted to complete the acquire process.66 -* Type "//progreset//"and press enter to restart ShowRunner67 -* Once S howRunnerhas finished restarting type"//sr discover zum false//"and press enter.howRunnerwill be able to acquire the loads attached to the Zum rooms at this point.68 -* Once completed S howRunneris now ready for full Zum control109 +* Type ##sr discover zummesh true## and press enter. 110 +* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 111 +* 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. 112 +* Type ##progreset## and press enter to restart SHOWRUNNER™ 113 +* 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. 114 +* Once completed SHOWRUNNER™ is now ready for full Zūm control 69 69 70 70 == Examples == 71 71 118 +=== 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 ... ... @@ -89,7 +89,7 @@ 89 89 MC4>sr ethernet device claim CEN-GWEXER-9E6ADA 90 90 Claimed ethernet device: CEN-GWEXER-9E6ADA 91 91 MC4>Update request from IP-ID-30 in Program 01 92 -MC4>sr discover zum false 137 +MC4>sr discover zummesh false 93 93 Starting Zum Discovery without gateway claiming 94 94 MC4>Performing Discovery on 1 Gateways. 95 95 Evaluating 3 Devices on Gateway 30 ... ... @@ -122,7 +122,7 @@ 122 122 MC4>progreset 123 123 ... 124 124 CI ShowRunner startup completed successfully in 8072ms 125 -MC4>sr discover zum false 170 +MC4>sr discover zummesh false 126 126 Starting Zum Discovery without gateway claiming 127 127 MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable) 128 128 Performing Discovery on 1 Gateways. ... ... @@ -173,9 +173,9 @@ 173 173 Removed Loads: 0 174 174 Zum Discovery Finished}}} 175 175 176 -=== Example for Option 2:===221 +=== Claim All Example === 177 177 178 -{{{MC4>sr discover zum true 223 +{{{MC4>sr discover zummesh true 179 179 Starting Zum Discovery with gateway claiming 180 180 MC4>Found 1 Gateways to check. 181 181 Claimed Gateway SN: 1720JBH04269 at IP-ID: 30 ... ... @@ -211,7 +211,7 @@ 211 211 MC4>progreset 212 212 ... 213 213 CI ShowRunner startup completed successfully in 8072ms 214 -MC4>sr discover zum false 259 +MC4>sr discover zummesh false 215 215 Starting Zum Discovery without gateway claiming 216 216 MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable) 217 217 Performing Discovery on 1 Gateways.