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 40.1
edited by Alexander Mott
on 2025/04/03 17:35
on 2025/04/03 17:35
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Zūm Autodiscovery1 +Zūm Discovery - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide. DeviceAddressing.WebHome1 +SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Program Configuration.WebHome - Content
-
... ... @@ -1,6 +1,14 @@ 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 + 1 1 (% class="box warningmessage" %) 2 2 ((( 3 -This article is about automatically building a S HOWRUNNER™ configuration using the ZūmAutodiscovery feature of SHOWRUNNER™. For instructions on configuring Zūm Wired rooms using the Crestron Zūm App, see [[this page>>SHOWRUNNER™ Setup Guide.WiringGuide.Zūm Wired System Overview.Crestron11 +This article is about automatically building a ShowRunnerCLC™ configuration using the Zūm Discovery 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]]. 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 ... ... @@ -8,70 +8,211 @@ 8 8 {{toc/}} 9 9 {{/box}} 10 10 11 -(% class="row" %) 12 -((( 13 -If Zūm Net devices have been configured using Crestron's Zūm App 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™. 14 14 15 - =ZūmWired=21 +There are certain pre-requisites and limitations when building a ShowRunnerCLC™ 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 -Lore m23 += Discovery Filter (ShowRunnerCLC™ 3.062 or newer) = 18 18 19 - =ZūmWireless=25 +Discovered ethernet devices may be filtered using either a hostname or IP Address filter. The filter is configured from the command line interface. 20 20 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 +~|~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-|~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-|## 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* 36 +=== Hostname Filter === 25 25 26 - ==Pre-Requisites:==38 +The Hostname filter uses a regular expression to filter discovered ZUMNET GATEWAYs or JBOXs. Multiple expressions can be applied by using a comma to separate the expressions. 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. 40 +Command Syntax: ##"Type='Hostname' Settings='Expr1[,Expr2]'"## 41 + 42 +Examples: 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'" 48 + 49 +=== IP Address Filter === 50 + 51 +The IP Address filter will restrict discovered ZUMNET GATEWAYs or JBOXs to matching IP Addresses or IP Address ranges. Multiple addresses and ranges can be used. 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 +=== IP-ID Filter (Added in SR v3.067) === 63 + 64 +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. 65 + 66 +Command Syntax: ##"Type='IPID' Settings='IPID[,IPIDStart-IPIDEnd]'"## 67 + 68 +Examples: 69 + 70 +1. Only include a device with an IP-ID of 10 or 5A: 71 +(% style="font-family:Menlo,Monaco,Consolas,Courier New,monospace; white-space:pre" %)sr discover filter "Type='IPID' Settings='10,5A'" 72 +1. Include addresses between 11 and 4F and A0 and BF: 73 +(% style="font-family:Menlo,Monaco,Consolas,Courier New,monospace; white-space:pre" %)sr discover filter "Type='IPID' Settings='11-4F,A0-BF'" 74 + 75 += Zūm Wired Discovery = 76 + 77 +== Notes and Limitations == 78 + 79 +(% class="box warningmessage" %) 80 +((( 81 +* ShowRunnerCLC™ version 3.014 or newer required 82 +* Zūm Wired firmware .puf version 1.02.10 or greater required (ZUMNET-JBOX installed minimum version 1.001.00081) 83 +* 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 84 +* Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release) 85 +* ZUMLINK-IOs will not be discovered (Expected to be discoverable in future ShowRunnerCLC™ release) 86 +* ZUMLINK-KPs will not be discovered on older versions of ShowRunnerCLC™ (v3.058 or newer will discover keypads and set as remote type) 87 +* One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually 31 31 ))) 32 32 33 -(% class="box warningmessage" id="HCaution:" %) 90 +== Steps == 91 + 92 +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 93 +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. 94 +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: 95 +1*. Connect to the first ZUMNET-JBOX in Toolbox 96 +1*. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 97 +1**. Note: The ShowRunnerCLC™ built-in DHCP server is not meant to be used in production 98 +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 99 +1*. Set unique Connection IDs for each device hosted on the ZUMNET-JBOX so that their firmware can be updated 100 +1*. Load the Zūm Wired firmware to the ZUMNET-JBOX 101 +1*. Repeat the above steps for all ZUMNET-JBOXs 102 +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 103 +1. Connect to each ZUMNET-JBOX in the Crestron Zūm App 104 +1*. Commission room through the app 105 +1**. configure keypad logic 106 +1**. configure occupancy sensor settings 107 +1**. calibrate photocell(s) 108 +1*. Set hostnames for the ZUMNETs. 109 +1**. Zūm discovery will bring in hostnames. 110 +1. Unique Connection IDs should be automatically assigned to any Zūm Link and Cresnet devices on the ZUMNET-JBOX 111 +1*. If firmware was out-of-date, then this step should have already been completed 112 +1*. If unique CIDs are not automatically assigned, connect to the JBOX in Toolbox and give the devices unique CIDs 113 +1. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 114 +1*. If firmware was out-of-date, then this step should have already been completed 115 +1*. Note: The ShowRunnerCLC™ built-in DHCP server is not meant to be used in production 116 +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 117 +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 118 +1*. If you do not manually configure the IP table, then SHOWRUNNER™ will automatically configure the IP-ID for each ZUMNET-JBOX during discovery 119 +1. Set the ZUMNET-JBOX into either Zūm ("App") mode or CNET mode as required for the program 120 +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 121 +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 122 +1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox 123 +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 124 +1. Run the command: ##sr discover zumnet true true## to add ZUMNET-JBOXs, connected ZUMLINK devices, and some Cresnet devices (such as Cameo keypads) to the configuration. (Note 125 +1*. This command will update the ShowRunnerCLC™ configuration with: 126 +1**. One area per claimed ZUMNET-JBOX based on the Room Name set in the app 127 +1**. One ZUMNET-BRIDGE load controller per claimed ZUMNET-JBOX to allow the Zūm Room to communicate its current status (scene, occupancy, etc.) to ShowRunnerCLC™ 128 +1**. One entry for each ZUMLINK-KP, ZUMLINK-JBOX, and ZUMLINK occupancy sensor connected to each ZUMNET-JBOX 129 +1***. All devices and loads will be auto-labeled based on their connection information, //not// the names they are given in the Zūm App 130 +1***. Keypads will be brought in as "Remote" type and only follow the logic as defined in the Zūm App, allowing for scheduled enabling/disabling of keypads without adding any additional button functions from ShowRunnerCLC™ 131 +1***. Occupancy sensors will be brought in with "Use Hardware Logic" and only follow the logic as defined in the Zūm App 132 +1*. Optionally, run ##sr discover zumnet false true## to only add new ZUMLINK devices to the configuration. **Note that previously added ZUMLINK devices will be added again if their CID has been changed** 133 +1*. Run ##sr discover zumnet true false## to add ZUMNET-JBOXs without bringing in any devices. **Note that if a ZUMNET-JBOX already has an entry in its IP Table, ShowRunnerCLC™ will not claim it.** The ZUMNET-JBOX's IP Table must be cleared in order for it to be claimed by the ShowRunnerCLC™ program 134 +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. 135 +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 136 + 137 += Zūm Wireless Discovery = 138 + 139 +== Notes and Limitations == 140 + 141 +(% class="box warningmessage" %) 34 34 ((( 35 -**Note:** SHOWRUNNER™ has two different approaches for Zūm Wireless Autodiscovery 143 +* Processor with ShowRunnerCLC™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired 144 +** For ShowRunnerCLC™ versions prior to 3.014 and newer, replace **##sr discover zummesh##** commands with **##sr discover zum##** 145 +* ZUM-NETBRIDGES must already be acquired to their respective gateway 146 +* ShowRunnerCLC™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices 147 +* Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command 148 +* Plug loads will not appear in the ShowRunnerCLC™ UI 149 +* 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 150 +))) 36 36 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 -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. 152 +(% class="box infomessage" id="HCaution:" %) 153 +((( 154 +**Note:** ShowRunnerCLC™ has two different approaches for Zūm Wireless Discovery 155 + 156 +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. 157 +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. 39 39 ))) 40 40 41 -(% class="ro w" %)160 +(% class="box errormessage" id="HCaution:" %) 42 42 ((( 43 - ==Option1:ManualRFGatewayClaiming:==162 +**Note:** Due to what is believed to be an SSL issue, ShowRunnerCLC™ will sometimes fail to acquire Zūm Wireless gateways with the ##sr discover zummesh true## or ##sr ethernet device claim [Hostname]## commands. 44 44 45 - Usethis methodifyouhavemultiple ShowRunnerinstanceson thesamenetworkorhavegatewaysusedbyotherCrestronsystems.164 +To work around this issue, Zūm Wireless gateways need to be added to the "IpDevices" section of the SrConfig.json and then have their IP Tables manually updated using the ##addm [IP-ID] [Processor IP]## command. Once this has been done, the ##sr discover zummesh false## commands can be run as normal. 46 46 166 +Below is an example "IpDevices" section of a config with three gateways defined. Serial numbers are optional and can be deleted if not known. **Note:** the "IpId" here is decimal, whereas the actual IP-ID that is assigned from Text Console is in hexadecimal. You will need to convert between the two: e.g. decimal "48" corresponds to hexadecimal "30", decimal "74" would correspond to hexadecimal "4A", etc. 167 + 168 +{{{ "Eiscs": [], 169 + "IpDevices": [ 170 + { 171 + "Model": "CEN-GWEXER", 172 + "Name": "GW-1-1", 173 + "SerialNumber": "2402NEJ03956", 174 + "IpId": 48 175 + }, 176 + { 177 + "Model": "CEN-GWEXER", 178 + "Name": "GW-1-2", 179 + "SerialNumber": "2402NEJ03862", 180 + "IpId": 49 181 + }, 182 + { 183 + "Model": "CEN-GWEXER", 184 + "Name": "GW-2-1", 185 + "SerialNumber": "2402NEJ03887", 186 + "IpId": 50 187 + } 188 + ], 189 + "Keyswitches": [],}}} 190 +))) 191 + 192 +== Manual RF Gateway Assignment Instructions == 193 + 194 +Use this method if you have multiple ShowRunnerCLC™ instances on the same network or have gateways used by other Crestron systems. 195 + 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//".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.54 -* Type "//progreset//"and press enter to restart ShowRunner55 -* Once S howRunnerhas finished restarting type"//sr discover zum false//"and press enter.um rooms at this point.56 -* Once completed S howRunneris now ready for full Zum control197 +* Type ##sr devmgr ethernet query## and press enter. This queries the local network for RF Gateways. 198 +* Type ##sr devmgr ethernet show devices## and press enter. This displays all found Crestron ethernet devices. 199 +* 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. 200 +* Type ##sr discover zummesh false## and press enter. 201 +* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 202 +* 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. 203 +* Type ##progreset## and press enter to restart ShowRunnerCLC™ 204 +* 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. 205 +* Once completed SHOWRUNNER™ is now ready for full Zūm control 57 57 58 -== Option 2:Claim All Gateways:==207 +== Claim All RF Gateways Instructions == 59 59 60 -Use this method when you have a single ShowRunner instance on a local network with all gateways being used for ShowRunner. 209 +Use this method when you have a single ShowRunnerCLC™ instance on a local network with all gateways being used for ShowRunnerCLC™. 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. 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 212 +* Type ##sr discover zummesh true## and press enter. ShowRunnerCLC™ will auto-assign an IP-ID. After all gateways have been claimed by ShowRunnerCLC™, proceed to the next step. 213 +* Type ##sr discover zummesh false## and press enter. 214 +* Status messages and the results will be displayed on the console. The process should take about 3 minutes. 215 +* 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. 216 +* Type ##progreset## and press enter to restart ShowRunnerCLC™ 217 +* 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. 218 +* Once completed ShowRunnerCLC™ is now ready for full Zūm control 69 69 70 70 == Examples == 71 71 222 +=== 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 241 +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 274 +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:===325 +=== Claim All Example === 177 177 178 -{{{MC4>sr discover zum true 327 +{{{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 363 +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. ... ... @@ -262,4 +262,3 @@ 262 262 Removed Loads: 0 263 263 Zum Discovery Finished 264 264 }}} 265 -)))