Changes for page Zūm Discovery
Last modified by Austin Weygandt on 2025/05/02 20:21
From version 10.1
edited by Alexander Mott
on 2022/10/05 16:18
on 2022/10/05 16:18
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Zūm Discovery1 +Zūm Autodiscovery - 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 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]].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]]. 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,110 +10,68 @@ 10 10 11 11 (% class="row" %) 12 12 ((( 13 -If Zūm Wiredor Wirelessdevices 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™.13 +If Zūm Net devices have been configured using Crestron's Zūm App 14 14 15 - Thereare certain pre-requisites and limitationswhen building a SHOWRUNNER™ configuration this way, and it may sometimes be necessary make some adjustmentsto the final configuration, such as changing keypad types and moving loads between areas.15 += Zūm Wired = 16 16 17 - = Zūm Wired Discovery =17 +Lorem 18 18 19 -= =Notesand Limitations ==19 += Zūm Wireless = 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 -))) 29 29 30 -== Steps == 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* 31 31 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 26 +== Pre-Requisites: == 63 63 64 -= Zūm Wireless Discovery = 65 - 66 -== Notes and Limitations == 67 - 68 -(% class="box errormessage" %) 69 -((( 70 -* Processor with SHOWRUNNER™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired 71 -** For SHOWRUNNER™ versions prior to 3.014 and newer, replace **##sr discover zummesh##** commands with **##sr discover zum##** 72 -* ZUM-NETBRIDGES must already be acquired to their respective gateway 73 -* SHOWRUNNER™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices 74 -* Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command 75 -* Plug loads will not appear in the SHOWRUNNER™ UI 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. 76 76 ))) 77 77 78 78 (% class="box warningmessage" id="HCaution:" %) 79 79 ((( 80 -**Note:** SHOWRUNNER™ has two different approaches for Zūm Wireless Discovery35 +**Note:** SHOWRUNNER™ has two different approaches for Zūm Wireless Autodiscovery 81 81 82 82 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. 83 83 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. 84 84 ))) 85 85 86 -== Manual RF Gateway Assignment Instructions == 41 +(% class="row" %) 42 +((( 43 +== Option 1: Manual RF Gateway Claiming: == 87 87 88 -Use this method if you have multiple S HOWRUNNER™instances on the same network or have gateways used by other Crestron systems.45 +Use this method if you have multiple ShowRunner instances on the same network or have gateways used by other Crestron systems. 89 89 90 90 * Connect to the processor's console with Toolbox or your favorite SSH client. 91 -* Type ##sr devmgr ethernet query##and press enter. This queries the local network for RF Gateways.92 -* Type ##sr devmgr ethernet show devices##and press enter. This displays all found Crestron ethernet devices.93 -* For each gateway that you'd like this instance of S HOWRUNNER™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.94 -* Type ##sr discover zummeshfalse##and press enter.95 -* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 96 -* When the discovery is finished type ##sr save##and press enter to save the updated config.HOWRUNNER™must be restarted to complete the acquire process.97 -* Type ##progreset##and press enter to restart SHOWRUNNER™98 -* Once S HOWRUNNER™has finished restarting type##sr discover zummeshfalse##and press enter.HOWRUNNER™will be able to acquire the loads attached to the Zūm rooms at this point.99 -* Once completed S HOWRUNNER™is now ready for full Zūm control48 +* 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 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 +* 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 100 100 101 -== Claim All RFGatewaysInstructions==58 +== Option 2: Claim All Gateways: == 102 102 103 -Use this method when you have a single S HOWRUNNER™instance on a local network with all gateways being used for SHOWRUNNER™.60 +Use this method when you have a single ShowRunner instance on a local network with all gateways being used for ShowRunner. 104 104 105 105 * Connect to the processor's console with Toolbox or your favorite SSH client. 106 -* Type ##sr discover zummeshtrue##and press enter.107 -* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 108 -* 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,HOWRUNNER™must be restarted to complete the acquire process.109 -* Type ##progreset##and press enter to restart SHOWRUNNER™110 -* Once S HOWRUNNER™has finished restarting type##sr discover zummeshfalse##and press enter.HOWRUNNER™will be able to acquire the loads attached to the Zūm rooms at this point.111 -* Once completed S HOWRUNNER™is now ready for full Zūm control63 +* 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 112 112 113 113 == Examples == 114 114 115 -=== Manual Example === 116 116 73 +=== Example for Option 1: === 74 + 117 117 {{{MC4>sr devmgr ethernet query 118 118 Ethrenet AutoDiscovery Result: AutoDiscoveryOperationSuccess 119 119 MC4>sr devmgr ethernet show devices ... ... @@ -131,7 +131,7 @@ 131 131 MC4>sr ethernet device claim CEN-GWEXER-9E6ADA 132 132 Claimed ethernet device: CEN-GWEXER-9E6ADA 133 133 MC4>Update request from IP-ID-30 in Program 01 134 -MC4>sr discover zum meshfalse92 +MC4>sr discover zum false 135 135 Starting Zum Discovery without gateway claiming 136 136 MC4>Performing Discovery on 1 Gateways. 137 137 Evaluating 3 Devices on Gateway 30 ... ... @@ -164,7 +164,7 @@ 164 164 MC4>progreset 165 165 ... 166 166 CI ShowRunner startup completed successfully in 8072ms 167 -MC4>sr discover zum meshfalse125 +MC4>sr discover zum false 168 168 Starting Zum Discovery without gateway claiming 169 169 MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable) 170 170 Performing Discovery on 1 Gateways. ... ... @@ -215,9 +215,9 @@ 215 215 Removed Loads: 0 216 216 Zum Discovery Finished}}} 217 217 218 -=== Claim AllExample ===176 +=== Example for Option 2: === 219 219 220 -{{{MC4>sr discover zum meshtrue178 +{{{MC4>sr discover zum true 221 221 Starting Zum Discovery with gateway claiming 222 222 MC4>Found 1 Gateways to check. 223 223 Claimed Gateway SN: 1720JBH04269 at IP-ID: 30 ... ... @@ -253,7 +253,7 @@ 253 253 MC4>progreset 254 254 ... 255 255 CI ShowRunner startup completed successfully in 8072ms 256 -MC4>sr discover zum meshfalse214 +MC4>sr discover zum false 257 257 Starting Zum Discovery without gateway claiming 258 258 MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable) 259 259 Performing Discovery on 1 Gateways.