Changes for page Zūm Discovery
Last modified by Austin Weygandt on 2025/05/02 20:21
From version 37.1
edited by Mark Kohlmann
on 2025/01/15 00:56
on 2025/01/15 00:56
Change comment:
There is no comment for this version
To version 2.1
edited by Alexander Mott
on 2022/09/22 21:44
on 2022/09/22 21:44
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. mark\.kohlmann@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,193 +16,71 @@ 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 - = Discovery Filter (ShowRunnerCLC™ 3.062ornewer) =17 +Lorem 24 24 25 - Discoveredethernet devicesmaybe filtered usingeither a hostname or IP Addressfilter. The filter is configured from the command line interface.19 += Zūm Wireless = 26 26 27 -##+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ 28 -~| Command | Help | 29 -~|~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-|~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-| 30 -~| SR discover clear filter | Remove Discovery Filter | 31 -~| SR discover filter | Show Discovery Filter | 32 -~| SR discover filter (X:S) | Set Discovery Filter | 33 -~| - | (X):S:Filter String | 34 -~|~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-|~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-|## 35 35 36 -=== Hostname Filter === 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 - TheHostname filteruses a regular expression to filter discovered ZUMNET GATEWAYs or JBOXs. Multiple expressions can be applied by using a commato separate the expressions.26 +== **Pre-Requisites:** == 39 39 40 -Command Syntax: ##"Type='Hostname' Settings='Expr1[,Expr2]'"## 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. 41 41 42 - Examples:32 +=== **Caution:** === 43 43 44 -1. Only include hostnames that start with ZUMNET-06: 45 -(% style="font-family:Menlo,Monaco,Consolas,Courier New,monospace; white-space:pre" %)sr discover filter "Type='Hostname' Settings='^ZUMNET-06'" 46 -1. Include hostnames that start with ZUMNET-FL01 or contain FL03: 47 -(% style="font-family:Menlo,Monaco,Consolas,Courier New,monospace; white-space:pre" %)sr discover filter "Type='Hostname' Settings='^ZUMNET-FL01,FL03'" 34 +* ShowRunner has 2 discovery approaches. 35 +** Option 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 +** Option 2: 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. 48 48 49 -== =IPAddressFilter===38 +== Option 1: Claim All Gateways: == 50 50 51 - TheIP Addressfilterwill restrictdiscoveredZUMNETGATEWAYs orJBOXso matching IP AddressesorIP Address ranges.Multipleaddressesandrangescanbe used.40 +Use this method when you have a single ShowRunner instance on a local network with all gateways being used for ShowRunner. 52 52 53 -Command Syntax: ##"Type='IPAddress' Settings='Address[,AddressStart-AddressEnd]'"## 54 - 55 -Examples: 56 - 57 -1. Only include a device with an address of 192.168.0.10 or 192.168.0.50: 58 -(% style="font-family:Menlo,Monaco,Consolas,Courier New,monospace; white-space:pre" %)sr discover filter "Type='IPAddress' Settings='192.168.0.10,192.168.0.50'" 59 -1. Include addresses between 192.168.0.11 and 192.168.0.50 and 192.168.0.200 and 192.168.0.240: 60 -(% style="font-family:Menlo,Monaco,Consolas,Courier New,monospace; white-space:pre" %)sr discover filter "Type='IPAddress' Settings='192.168.0.11-192.168.0.50,192.168.0.200-192.168.0.240'" 61 - 62 - 63 -=== IP-ID Filter (Added in SR v3.067) === 64 - 65 -The IP-ID filter will restrict discovered ZUMNET GATEWAYs or JBOXs to matching IP-IDs or IP-ID ranges. Multiple IDs and ranges can be used. 66 - 67 -Command Syntax: ##"Type='IPID' Settings='IPID[,IPIDStart-IPIDEnd]'"## 68 - 69 -Examples: 70 - 71 -1. Only include a device with an IP-ID of 10 or 5A: 72 -(% style="font-family:Menlo,Monaco,Consolas,Courier New,monospace; white-space:pre" %)sr discover filter "Type='IPID' Settings='10,5A'" 73 -1. Include addresses between 11 and 4F and A0 and BF: 74 -(% style="font-family:Menlo,Monaco,Consolas,Courier New,monospace; white-space:pre" %)sr discover filter "Type='IPID' Settings='11-4F,A0-BF'" 75 - 76 -= Zūm Wired Discovery = 77 - 78 -== Notes and Limitations == 79 - 80 -(% class="box warningmessage" %) 81 -((( 82 -* ShowRunnerCLC™ version 3.014 or newer required 83 -* Zūm Wired firmware .puf version 1.02.10 or greater required (ZUMNET-JBOX installed minimum version 1.001.00081) 84 -* Disconnect from any ZUMNET devices you may be connected to in Toolbox and confirm all hardware (NETs and LINKs) are online prior to running the discovery commands 85 -* Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release) 86 -* ZUMLINK-IOs will not be discovered (Expected to be discoverable in future ShowRunnerCLC™ release) 87 -* ZUMLINK-KPs will not be discovered on older versions of ShowRunnerCLC™ (v3.058 or newer will discover keypads and set as remote type) 88 -* One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually 89 -))) 90 - 91 -== Steps == 92 - 93 -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 94 -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. 95 -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: 96 -1*. Connect to the first ZUMNET-JBOX in Toolbox 97 -1*. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 98 -1**. Note: The ShowRunnerCLC™ built-in DHCP server is not meant to be used in production 99 -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 100 -1*. Set unique Connection IDs for each device hosted on the ZUMNET-JBOX so that their firmware can be updated 101 -1*. Load the Zūm Wired firmware to the ZUMNET-JBOX 102 -1*. Repeat the above steps for all ZUMNET-JBOXs 103 -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 104 -1. Connect to each ZUMNET-JBOX in the Crestron Zūm App 105 -1*. Commission room through the app 106 -1**. configure keypad logic 107 -1**. configure occupancy sensor settings 108 -1**. calibrate photocell(s) 109 -1*. Set hostnames for the ZUMNETs. 110 -1**. Zūm discovery will bring in hostnames. 111 -1. Unique Connection IDs should be automatically assigned to any Zūm Link and Cresnet devices on the ZUMNET-JBOX 112 -1*. If firmware was out-of-date, then this step should have already been completed 113 -1*. If unique CIDs are not automatically assigned, connect to the JBOX in Toolbox and give the devices unique CIDs 114 -1. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 115 -1*. If firmware was out-of-date, then this step should have already been completed 116 -1*. Note: The ShowRunnerCLC™ built-in DHCP server is not meant to be used in production 117 -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 118 -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 119 -1*. If you do not manually configure the IP table, then SHOWRUNNER™ will automatically configure the IP-ID for each ZUMNET-JBOX during discovery 120 -1. Set the ZUMNET-JBOX into either Zūm ("App") mode or CNET mode as required for the program 121 -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 122 -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 123 -1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox 124 -1. If trying to Auto Discover on a job with multiple processors or you are returning to a job where new ZUMNET-JBOXs have been added and you only wish to Auto Discover those new devices, ShowRunnerCLC™ 3.062 and newer allow [[filtering based on hostname or IP address>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Program Configuration.Zūm Discovery.WebHome||anchor="HDiscoveryFilter28ShowRunnerCLC21223.062ornewer29"]] in order to limit the devices that are brought into the ShowRunnerCLC™ configuration 125 -1. Run the command: ##sr discover zumnet true true## 126 -1*. This command tells ShowRunnerCLC™ to both claim all 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 127 -1**. One area will be created per ZUMNET-JBOX, and all hardware attached to that ZUMNET-JBOX will be assigned to that area 128 -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 129 -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. 130 -1. If new Zūm Link hardware has been added, it is not necessary to do a full Auto Discovery to bring the new devices into ShowRunnerCLC™; instead you can just run ##sr discover zumnet false true## to bring in the new Zūm Link devices without claiming any new Zūm Net devices 131 - 132 -= Zūm Wireless Discovery = 133 - 134 -== Notes and Limitations == 135 - 136 -(% class="box warningmessage" %) 137 -((( 138 -* Processor with ShowRunnerCLC™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired 139 -** For ShowRunnerCLC™ versions prior to 3.014 and newer, replace **##sr discover zummesh##** commands with **##sr discover zum##** 140 -* ZUM-NETBRIDGES must already be acquired to their respective gateway 141 -* ShowRunnerCLC™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices 142 -* Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command 143 -* Plug loads will not appear in the ShowRunnerCLC™ UI 144 -* Newer GWEXER firmware enables SSL by default. Follow the instructions at [[SSL User Configuration>>doc:SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Appendix.SSL User Configuration.WebHome]] and manually add the IP Table entries on the GWEXER 145 -))) 146 - 147 -(% class="box infomessage" id="HCaution:" %) 148 -((( 149 -**Note:** ShowRunnerCLC™ has two different approaches for Zūm Wireless Discovery 150 - 151 -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. 152 -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. 153 -))) 154 - 155 -== Manual RF Gateway Assignment Instructions == 156 - 157 -Use this method if you have multiple ShowRunnerCLC™ instances on the same network or have gateways used by other Crestron systems. 158 - 159 159 * Connect to the processor's console with Toolbox or your favorite SSH client. 160 -* Type ##sr devmgr ethernet query## and press enter. This queries the local network for RF Gateways. 161 -* Type ##sr devmgr ethernet show devices## and press enter. This displays all found Crestron ethernet devices. 162 -* 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. 163 -* Type ##sr discover zummesh false## and press enter. 164 -* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 165 -* 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. 166 -* Type ##progreset## and press enter to restart ShowRunnerCLC™ 167 -* 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. 168 -* Once completed SHOWRUNNER™ is now ready for full Zūm control 43 +* Type "//sr discover zum true//" and press enter. 44 +* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 45 +* 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. 46 +* Type "//progreset//" and press enter to restart ShowRunner 47 +* 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. 48 +* Once completed ShowRunner is now ready for full Zum control 169 169 170 -== ClaimAllRF GatewaysInstructions==50 +== Option 2: Manual RF Gateway Claiming: == 171 171 172 -Use this method whenyou havea single ShowRunnerCLC™instance onalocalnetworkwithallgatewaysbeingusedforShowRunnerCLC™.52 +Use this method if you have multiple ShowRunner instances on the same network or have gateways used by other Crestron systems. 173 173 174 174 * Connect to the processor's console with Toolbox or your favorite SSH client. 175 -* Type ##sr discover zummesh true## and press enter. 176 -* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 177 -* 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. 178 -* Type ##progreset## and press enter to restart ShowRunnerCLC™ 179 -* 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. 180 -* Once completed ShowRunnerCLC™ is now ready for full Zūm control 55 +* Type "//sr devmgr ethernet query//" and press enter. This queries the local network for RF Gateways. 56 +* Type "//sr devmgr ethernet show devices//" and press enter. This displays all found Crestron ethernet devices. 57 +* 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. 58 +* Type "//sr discover zum false//" and press enter. 59 +* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 60 +* 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. 61 +* Type "//progreset//" and press enter to restart ShowRunner 62 +* 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. 63 +* Once completed ShowRunner is now ready for full Zum control 181 181 182 182 == Examples == 183 183 184 -=== ManualExample ===67 +=== Example for Option 1: === 185 185 186 -{{{MC4>sr devmgr ethernet query 187 -Ethrenet AutoDiscovery Result: AutoDiscoveryOperationSuccess 188 -MC4>sr devmgr ethernet show devices 189 - 190 -+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 191 -| Adapter | Hostname | IP Address | IP-ID | ID | 192 -+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 193 -| EthernetLANAdapter | CI-SJC-CEN-CI3-1-COM3 | 10.44.5.20 | 00 | CEN-CI3-1-C3COM-3 [v1.1620.00000, #008436E2] type:1 | 194 -+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 195 -| EthernetLANAdapter | SB-DIN-CENCN-2 | 10.44.5.81 | 00 | DIN-CENCN-2-POE [v1.3544.00006, #8AB25AA3] | 196 -+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 197 -| EthernetLANAdapter | CEN-GWEXER-9E6ADA | 10.44.5.120 | 00 | CEN-GWEXER [v1.4230.00015, #848210AD] | 198 -+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 199 - 200 -MC4>sr ethernet device claim CEN-GWEXER-9E6ADA 201 -Claimed ethernet device: CEN-GWEXER-9E6ADA 202 -MC4>Update request from IP-ID-30 in Program 01 203 -MC4>sr discover zummesh false 204 -Starting Zum Discovery without gateway claiming 205 -MC4>Performing Discovery on 1 Gateways. 69 +{{{MC4>sr discover zum true 70 +Starting Zum Discovery with gateway claiming 71 +MC4>Found 1 Gateways to check. 72 +Claimed Gateway SN: 1720JBH04269 at IP-ID: 30 73 +Update request from IP-ID-30 in Program 01 74 +Claimed 1 Gateways. Waiting for queries to finish. 75 +Performing Discovery on 1 Gateways. 206 206 Evaluating 3 Devices on Gateway 30 207 207 Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30 208 208 Dev: ZUM-NETBRIDGE addrssing to RF ID: 03 ... ... @@ -213,7 +213,6 @@ 213 213 Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30 214 214 Dev: ZUM-NETBRIDGE addrssing to RF ID: 05 215 215 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 05 216 -Querying cresnet 217 217 Discovering Zum Loads on 1 Gateways. 218 218 Discovering Zum Loads on 3 Devices. 219 219 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0 ... ... @@ -233,7 +233,7 @@ 233 233 MC4>progreset 234 234 ... 235 235 CI ShowRunner startup completed successfully in 8072ms 236 -MC4>sr discover zum meshfalse105 +MC4>sr discover zum false 237 237 Starting Zum Discovery without gateway claiming 238 238 MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable) 239 239 Performing Discovery on 1 Gateways. ... ... @@ -282,17 +282,31 @@ 282 282 New Loads: 6 283 283 Modified Loads: 0 284 284 Removed Loads: 0 285 -Zum Discovery Finished}}} 154 +Zum Discovery Finished 155 +}}} 286 286 287 -=== Claim AllExample ===157 +=== Example for Option 2: === 288 288 289 -{{{MC4>sr discover zummesh true 290 -Starting Zum Discovery with gateway claiming 291 -MC4>Found 1 Gateways to check. 292 -Claimed Gateway SN: 1720JBH04269 at IP-ID: 30 293 -Update request from IP-ID-30 in Program 01 294 -Claimed 1 Gateways. Waiting for queries to finish. 295 -Performing Discovery on 1 Gateways. 159 +{{{MC4>sr devmgr ethernet query 160 +Ethrenet AutoDiscovery Result: AutoDiscoveryOperationSuccess 161 +MC4>sr devmgr ethernet show devices 162 + 163 ++--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 164 +| Adapter | Hostname | IP Address | IP-ID | ID | 165 ++--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 166 +| EthernetLANAdapter | CI-SJC-CEN-CI3-1-COM3 | 10.44.5.20 | 00 | CEN-CI3-1-C3COM-3 [v1.1620.00000, #008436E2] type:1 | 167 ++--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 168 +| EthernetLANAdapter | SB-DIN-CENCN-2 | 10.44.5.81 | 00 | DIN-CENCN-2-POE [v1.3544.00006, #8AB25AA3] | 169 ++--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 170 +| EthernetLANAdapter | CEN-GWEXER-9E6ADA | 10.44.5.120 | 00 | CEN-GWEXER [v1.4230.00015, #848210AD] | 171 ++--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ 172 + 173 +MC4>sr ethernet device claim CEN-GWEXER-9E6ADA 174 +Claimed ethernet device: CEN-GWEXER-9E6ADA 175 +MC4>Update request from IP-ID-30 in Program 01 176 +MC4>sr discover zum false 177 +Starting Zum Discovery without gateway claiming 178 +MC4>Performing Discovery on 1 Gateways. 296 296 Evaluating 3 Devices on Gateway 30 297 297 Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30 298 298 Dev: ZUM-NETBRIDGE addrssing to RF ID: 03 ... ... @@ -303,6 +303,7 @@ 303 303 Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30 304 304 Dev: ZUM-NETBRIDGE addrssing to RF ID: 05 305 305 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 05 189 +Querying cresnet 306 306 Discovering Zum Loads on 1 Gateways. 307 307 Discovering Zum Loads on 3 Devices. 308 308 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0 ... ... @@ -322,7 +322,7 @@ 322 322 MC4>progreset 323 323 ... 324 324 CI ShowRunner startup completed successfully in 8072ms 325 -MC4>sr discover zum meshfalse209 +MC4>sr discover zum false 326 326 Starting Zum Discovery without gateway claiming 327 327 MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable) 328 328 Performing Discovery on 1 Gateways. ... ... @@ -372,4 +372,5 @@ 372 372 Modified Loads: 0 373 373 Removed Loads: 0 374 374 Zum Discovery Finished 375 -}}} 259 + }}} 260 +)))