Changes for page Zūm Discovery
Last modified by Austin Weygandt on 2025/05/02 20:21
From version 24.3
edited by Craig Lewis
on 2024/05/22 21:47
on 2024/05/22 21:47
Change comment:
There is no comment for this version
To version 3.1
edited by Alexander Mott
on 2022/09/22 21:47
on 2022/09/22 21:47
Change comment:
There is no comment for this version
Summary
-
Page properties (4 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Zūm Discovery1 +Zūm Autodiscovery - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide. Program Configuration.WebHome1 +SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. craig\.lewis@chiefintegrations\.com1 +XWiki.alexander\.mott@chiefintegrations\.com - Content
-
... ... @@ -1,14 +9,6 @@ 1 -(% class="box errormessage" %) 2 -((( 3 -**IMPORTANT:** When using ShowRunnerCLC™ with a ZUM-HUB4, **do not** discover Zūm Rooms using the Crestron HUB4 Web UI. During discovery, the HUB4 will claim ZUMNET-JBOXs and prevent ShowRunnerCLC™ from auto-discovering or registering the Zūm hardware for itself. 4 - 5 -**WARNING:** Cresnet Discovery is non-functional for ZUMNET-JBOXs with certain versions of Crestron Device Database. 6 -ShowRunnerCLC™ versions v3.019 through v3.041 must be either downgraded to v3.018 or upgraded to v3.042 or newer in order to perform auto-discover functions. 7 -))) 8 - 9 9 (% class="box warningmessage" %) 10 10 ((( 11 -This article is about automatically building a S howRunnerCLC™ configuration using the ZūmDiscovery feature of ShowRunnerCLC™. For instructions on configuring Zūm Wired rooms using the Crestron Zūm App, see [[this page>>SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.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]]. 12 12 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]]. 13 13 ))) 14 14 ... ... @@ -16,137 +16,72 @@ 16 16 {{toc/}} 17 17 {{/box}} 18 18 19 -If Zūm Wired or Wireless devices have been configured using Crestron's Zūm App, then it is possible to automatically build a ShowRunnerCLC™ configuration file using the Zūm Discovery feature that is built into ShowRunnerCLC™. 11 +(% class="row" %) 12 +((( 13 +If Zūm Net devices have been configured using Crestron's Zūm App 20 20 21 - Thereare certain pre-requisites and limitationswhen building a ShowRunnerCLC™ 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 = 22 22 23 - = Zūm Wired Discovery =17 +Lorem 24 24 25 -= =Notesand Limitations ==19 += Zūm Wireless = 26 26 27 -(% class="box warningmessage" %) 28 -((( 29 -* ShowRunnerCLC™ version 3.014 or newer required 30 -* Zūm Wired firmware .puf version 1.02.10 or greater required (ZUMNET-JBOX installed minimum version 1.001.00081) 31 -* Disconnect from any ZUMNET devices you may be connected to in Toolbox prior to running the discovery commands 32 -* Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release) 33 -* One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually 34 -))) 35 35 36 -== 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* 37 37 38 -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 39 -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. 40 -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: 41 -1*. Connect to the first ZUMNET-JBOX in Toolbox 42 -1*. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 43 -1**. Note: The ShowRunnerCLC™ built-in DHCP server is not meant to be used in production 44 -1**. If the ShowRunnerCLC™ built-in DHCP server was used to assign IP addresses to devices, it is still necessary to give those devices static IP addresses 45 -1*. Set unique Connection IDs for each device hosted on the ZUMNET-JBOX so that their firmware can be updated 46 -1*. Load the Zūm Wired firmware to the ZUMNET-JBOX 47 -1*. Repeat the above steps for all ZUMNET-JBOXs 48 -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 49 -1. Connect to each ZUMNET-JBOX in the Crestron Zūm App 50 -1*. Commission room through the app 51 -1**. configure keypad logic 52 -1**. configure occupancy sensor settings 53 -1**. calibrate photocell(s) 54 -1*. Set hostnames for the ZUMNETs. 55 -1**. Zūm discovery will bring in hostnames. 56 -1. Unique Connection IDs should be automatically assigned to any Zūm Link and Cresnet devices on the ZUMNET-JBOX 57 -1*. If firmware was out-of-date, then this step should have already been completed 58 -1*. If unique CIDs are not automatically assigned, connect to the JBOX in Toolbox and give the devices unique CIDs 59 -1. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 60 -1*. If firmware was out-of-date, then this step should have already been completed 61 -1*. Note: The ShowRunnerCLC™ built-in DHCP server is not meant to be used in production 62 -1*. If the ShowRunnerCLC™ built-in DHCP server was used to assign IP addresses to devices, it is still necessary to give those devices static IP addresses 63 -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 64 -1*. If you do not manually configure the IP table, then SHOWRUNNER™ will automatically configure the IP-ID for each ZUMNET-JBOX during discovery 65 -1. Set the ZUMNET-JBOX into either Zūm ("App") mode or CNET mode as required for the program 66 -1*. Full control from ShowRunnerCLC™ is only possible if all ZUMNET-JBOXs are in CNET mode. Odd behavior may result from conflicts between ShowRunnerCLC™ and internal logic if the ZUMNET-JBOXs are not put into CNET mode 67 -1. Repeat from step 3 until all ZUMNET-JBOXs that are to be controlled by ShowRunnerCLC™ have static IP addresses and unique CIDs for any hosted devices 68 -1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox 69 -1. Run the command: ##sr discover zumnet true false## 70 -1*. This command tells ShowRunnerCLC™ to discover all ZUMMNET-JBOXs on the network, configure their IP tables, and then add corresponding IP Devices to the configuration 71 -1. Run the command: ##sr discover zumnet true true## 72 -1*. This command tells ShowRunnerCLC™ 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 73 -1**. One area will be created per ZUMNET-JBOX, and all hardware attached to that ZUMNET-JBOX will be assigned to that area 74 -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 75 -1. If all steps have been performed successfully, then you should be able to use the ##sr show area##, ##sr show load##, ##sr show keypad##, and ##sr show occ## commands to see that the ZUMNET and ZUMLINK hardware has been discovered correctly. 26 +== Pre-Requisites: == 76 76 77 -= Zūm Wireless Discovery = 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. 78 78 79 -== Notes and Limitations == 80 - 81 -(% class="box warningmessage" %) 32 +(% class="box warningmessage" id="HCaution:" %) 82 82 ((( 83 -* Processor with ShowRunnerCLC™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired 84 -** For ShowRunnerCLC™ versions prior to 3.014 and newer, replace **##sr discover zummesh##** commands with **##sr discover zum##** 85 -* ZUM-NETBRIDGES must already be acquired to their respective gateway 86 -* ShowRunnerCLC™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices 87 -* Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command 88 -* Plug loads will not appear in the ShowRunnerCLC™ UI 34 +**Note,** SHOWRUNNER has two different types of Zum Wireless autodiscovery: 35 +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. 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. 89 89 ))) 90 90 91 -(% class="box infomessage" id="HCaution:" %) 92 -((( 93 -**Note:** ShowRunnerCLC™ has two different approaches for Zūm Wireless Discovery 39 +== Option 1: Claim All Gateways: == 94 94 95 -1. **Manual RF Gateway Assignment** - ShowRunnerCLC™ 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. 96 -1. **Claim All RF Gateways** - ShowRunnerCLC™ 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 ShowRunnerCLC™ or other Crestron systems on the same local network. 97 -))) 41 +Use this method when you have a single ShowRunner instance on a local network with all gateways being used for ShowRunner. 98 98 99 -== Manual RF Gateway Assignment Instructions == 100 - 101 -Use this method if you have multiple ShowRunnerCLC™ instances on the same network or have gateways used by other Crestron systems. 102 - 103 103 * Connect to the processor's console with Toolbox or your favorite SSH client. 104 -* Type ##sr devmgr ethernet query## and press enter. This queries the local network for RF Gateways. 105 -* Type ##sr devmgr ethernet show devices## and press enter. This displays all found Crestron ethernet devices. 106 -* 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##. ShowRunnerCLC™ will auto-assign an IP-ID. After all gateways have been claimed by ShowRunnerCLC™, proceed to the next step. 107 -* Type ##sr discover zummesh false## and press enter. 108 -* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 109 -* 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, ShowRunnerCLC™ must be restarted to complete the acquire process. 110 -* Type ##progreset## and press enter to restart ShowRunnerCLC™ 111 -* Once SHOWRUNNER™ has finished restarting type ##sr discover zummesh false## and press enter. ShowRunnerCLC™ will be able to acquire the loads attached to the Zūm rooms at this point. 112 -* Once completed SHOWRUNNER™ is now ready for full Zūm control 44 +* Type "//sr discover zum true//" and press enter. 45 +* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 46 +* 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. 47 +* Type "//progreset//" and press enter to restart ShowRunner 48 +* 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. 49 +* Once completed ShowRunner is now ready for full Zum control 113 113 114 -== ClaimAllRF GatewaysInstructions==51 +== Option 2: Manual RF Gateway Claiming: == 115 115 116 -Use this method whenyou havea single ShowRunnerCLC™instance onalocalnetworkwithallgatewaysbeingusedforShowRunnerCLC™.53 +Use this method if you have multiple ShowRunner instances on the same network or have gateways used by other Crestron systems. 117 117 118 118 * Connect to the processor's console with Toolbox or your favorite SSH client. 119 -* Type ##sr discover zummesh true## and press enter. 120 -* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 121 -* 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, ShowRunnerCLC™ must be restarted to complete the acquire process. 122 -* Type ##progreset## and press enter to restart ShowRunnerCLC™ 123 -* Once ShowRunnerCLC™ has finished restarting type ##sr discover zummesh false## and press enter. ShowRunnerCLC™ will be able to acquire the loads attached to the Zūm rooms at this point. 124 -* Once completed ShowRunnerCLC™ is now ready for full Zūm control 56 +* Type "//sr devmgr ethernet query//" and press enter. This queries the local network for RF Gateways. 57 +* Type "//sr devmgr ethernet show devices//" and press enter. This displays all found Crestron ethernet devices. 58 +* 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. 59 +* Type "//sr discover zum false//" and press enter. 60 +* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 61 +* 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. 62 +* Type "//progreset//" and press enter to restart ShowRunner 63 +* 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. 64 +* Once completed ShowRunner is now ready for full Zum control 125 125 126 126 == Examples == 127 127 128 -=== ManualExample ===68 +=== Example for Option 1: === 129 129 130 -{{{MC4>sr devmgr ethernet query 131 -Ethrenet AutoDiscovery Result: AutoDiscoveryOperationSuccess 132 -MC4>sr devmgr ethernet show devices 133 - 134 -+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 135 -| Adapter | Hostname | IP Address | IP-ID | ID | 136 -+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 137 -| EthernetLANAdapter | CI-SJC-CEN-CI3-1-COM3 | 10.44.5.20 | 00 | CEN-CI3-1-C3COM-3 [v1.1620.00000, #008436E2] type:1 | 138 -+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 139 -| EthernetLANAdapter | SB-DIN-CENCN-2 | 10.44.5.81 | 00 | DIN-CENCN-2-POE [v1.3544.00006, #8AB25AA3] | 140 -+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 141 -| EthernetLANAdapter | CEN-GWEXER-9E6ADA | 10.44.5.120 | 00 | CEN-GWEXER [v1.4230.00015, #848210AD] | 142 -+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 143 - 144 -MC4>sr ethernet device claim CEN-GWEXER-9E6ADA 145 -Claimed ethernet device: CEN-GWEXER-9E6ADA 146 -MC4>Update request from IP-ID-30 in Program 01 147 -MC4>sr discover zummesh false 148 -Starting Zum Discovery without gateway claiming 149 -MC4>Performing Discovery on 1 Gateways. 70 +{{{MC4>sr discover zum true 71 +Starting Zum Discovery with gateway claiming 72 +MC4>Found 1 Gateways to check. 73 +Claimed Gateway SN: 1720JBH04269 at IP-ID: 30 74 +Update request from IP-ID-30 in Program 01 75 +Claimed 1 Gateways. Waiting for queries to finish. 76 +Performing Discovery on 1 Gateways. 150 150 Evaluating 3 Devices on Gateway 30 151 151 Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30 152 152 Dev: ZUM-NETBRIDGE addrssing to RF ID: 03 ... ... @@ -157,7 +157,6 @@ 157 157 Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30 158 158 Dev: ZUM-NETBRIDGE addrssing to RF ID: 05 159 159 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 05 160 -Querying cresnet 161 161 Discovering Zum Loads on 1 Gateways. 162 162 Discovering Zum Loads on 3 Devices. 163 163 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0 ... ... @@ -177,7 +177,7 @@ 177 177 MC4>progreset 178 178 ... 179 179 CI ShowRunner startup completed successfully in 8072ms 180 -MC4>sr discover zum meshfalse106 +MC4>sr discover zum false 181 181 Starting Zum Discovery without gateway claiming 182 182 MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable) 183 183 Performing Discovery on 1 Gateways. ... ... @@ -226,17 +226,31 @@ 226 226 New Loads: 6 227 227 Modified Loads: 0 228 228 Removed Loads: 0 229 -Zum Discovery Finished}}} 155 +Zum Discovery Finished 156 +}}} 230 230 231 -=== Claim AllExample ===158 +=== Example for Option 2: === 232 232 233 -{{{MC4>sr discover zummesh true 234 -Starting Zum Discovery with gateway claiming 235 -MC4>Found 1 Gateways to check. 236 -Claimed Gateway SN: 1720JBH04269 at IP-ID: 30 237 -Update request from IP-ID-30 in Program 01 238 -Claimed 1 Gateways. Waiting for queries to finish. 239 -Performing Discovery on 1 Gateways. 160 +{{{MC4>sr devmgr ethernet query 161 +Ethrenet AutoDiscovery Result: AutoDiscoveryOperationSuccess 162 +MC4>sr devmgr ethernet show devices 163 + 164 ++--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 165 +| Adapter | Hostname | IP Address | IP-ID | ID | 166 ++--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 167 +| EthernetLANAdapter | CI-SJC-CEN-CI3-1-COM3 | 10.44.5.20 | 00 | CEN-CI3-1-C3COM-3 [v1.1620.00000, #008436E2] type:1 | 168 ++--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 169 +| EthernetLANAdapter | SB-DIN-CENCN-2 | 10.44.5.81 | 00 | DIN-CENCN-2-POE [v1.3544.00006, #8AB25AA3] | 170 ++--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 171 +| EthernetLANAdapter | CEN-GWEXER-9E6ADA | 10.44.5.120 | 00 | CEN-GWEXER [v1.4230.00015, #848210AD] | 172 ++--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 173 + 174 +MC4>sr ethernet device claim CEN-GWEXER-9E6ADA 175 +Claimed ethernet device: CEN-GWEXER-9E6ADA 176 +MC4>Update request from IP-ID-30 in Program 01 177 +MC4>sr discover zum false 178 +Starting Zum Discovery without gateway claiming 179 +MC4>Performing Discovery on 1 Gateways. 240 240 Evaluating 3 Devices on Gateway 30 241 241 Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30 242 242 Dev: ZUM-NETBRIDGE addrssing to RF ID: 03 ... ... @@ -247,6 +247,7 @@ 247 247 Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30 248 248 Dev: ZUM-NETBRIDGE addrssing to RF ID: 05 249 249 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 05 190 +Querying cresnet 250 250 Discovering Zum Loads on 1 Gateways. 251 251 Discovering Zum Loads on 3 Devices. 252 252 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0 ... ... @@ -266,7 +266,7 @@ 266 266 MC4>progreset 267 267 ... 268 268 CI ShowRunner startup completed successfully in 8072ms 269 -MC4>sr discover zum meshfalse210 +MC4>sr discover zum false 270 270 Starting Zum Discovery without gateway claiming 271 271 MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable) 272 272 Performing Discovery on 1 Gateways. ... ... @@ -316,4 +316,5 @@ 316 316 Modified Loads: 0 317 317 Removed Loads: 0 318 318 Zum Discovery Finished 319 -}}} 260 + }}} 261 +)))