Changes for page Zūm Discovery
Last modified by Alexander Mott on 2025/04/03 17:35
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 6.2
edited by Alexander Mott
on 2022/09/22 23:32
on 2022/09/22 23:32
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,39 @@ 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 +* 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. 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. 31 += Zūm Wireless Discovery = 32 + 33 +== Notes and Limitations == 34 + 35 +* Processor with SHOWRUNNER™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired 36 +** For SHOWRUNNER™ versions 3.014 and newer, replace ##sr discover zum## commands with ##sr discover zummesh## 37 +* ZUM-NETBRIDGES must already be acquired to their respective gateway 38 +* SHOWRUNNER™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices 39 +* Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command 40 +* 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 Autodiscovery45 +**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:==53 +== 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.55 +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 S howRunnerto use, use the hostname from the table of found ethernet devices.howRunnerwill auto-assign an IP-ID.howRunnerproceed to the next step.60 +* 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. 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 S howRunner55 -* 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 control62 +* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 63 +* 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. 64 +* Type "//progreset//" and press enter to restart SHOWRUNNER™ 65 +* 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. 66 +* Once completed SHOWRUNNER™ is now ready for full Zūm control 57 57 58 -== Option 2:Claim All Gateways:==68 +== 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.70 +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. 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 S howRunner67 -* 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 control74 +* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 75 +* 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. 76 +* Type "//progreset//" and press enter to restart SHOWRUNNER™ 77 +* 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. 78 +* Once completed SHOWRUNNER™ is now ready for full Zūm control 69 69 70 70 == Examples == 71 71 82 +=== 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:===185 +=== Claim All Example === 177 177 178 178 {{{MC4>sr discover zum true 179 179 Starting Zum Discovery with gateway claiming