Wiki source code of Zūm Discovery
Version 19.1 by Scott Kohlmann on 2023/04/21 13:58
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
15.1 | 1 | (% class="box errormessage" %) |
| 2 | ((( | ||
| |
18.1 | 3 | WARNING: Cresnet Discovery is not currently working on ZUMNET-JBOXs. Crestron has acknowledged a fix has been sent to QE. |
| 4 | |||
| |
19.1 | 5 | Downgrade ShowRunnerCLC™ to v3.018 in order to auto-discover hardware. ShowRunnerCLC™ can be subsequently upgraded once discovery is complete. |
| |
15.1 | 6 | ))) |
| |
16.1 | 7 | |
| |
1.1 | 8 | (% class="box warningmessage" %) |
| 9 | ((( | ||
| |
19.1 | 10 | 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.Wiring Guide.Zūm Wired System Overview.Crestron Zūm App Overview.WebHome]]. |
| |
1.1 | 11 | 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]]. |
| 12 | ))) | ||
| 13 | |||
| 14 | {{box cssClass="floatinginfobox" title="**CONTENTS**"}} | ||
| 15 | {{toc/}} | ||
| 16 | {{/box}} | ||
| 17 | |||
| |
19.1 | 18 | 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™. |
| |
1.1 | 19 | |
| |
19.1 | 20 | 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. |
| |
1.1 | 21 | |
| |
5.2 | 22 | = Zūm Wired Discovery = |
| 23 | |||
| |
6.1 | 24 | == Notes and Limitations == |
| |
1.1 | 25 | |
| |
15.1 | 26 | (% class="box warningmessage" %) |
| |
9.1 | 27 | ((( |
| |
19.1 | 28 | * ShowRunnerCLC™ version 3.014 or newer required |
| |
13.1 | 29 | * Zūm Wired firmware .puf version 1.02.10 or greater required (ZUMNET-JBOX installed minimum version 1.001.00081) |
| |
6.2 | 30 | * Disconnect from any ZUMNET devices you may be connected to in Toolbox prior to running the discovery commands |
| 31 | * Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release) | ||
| 32 | * One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually | ||
| |
9.1 | 33 | ))) |
| |
6.1 | 34 | |
| |
6.2 | 35 | == Steps == |
| 36 | |||
| |
19.1 | 37 | 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 |
| |
7.1 | 38 | 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. |
| 39 | 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: | ||
| 40 | 1*. Connect to the first ZUMNET-JBOX in Toolbox | ||
| 41 | 1*. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network | ||
| |
19.1 | 42 | 1**. Note: The ShowRunnerCLC™ built-in DHCP server is not meant to be used in production |
| 43 | 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 | ||
| |
7.1 | 44 | 1*. Set unique Connection IDs for each device hosted on the ZUMNET-JBOX so that their firmware can be updated |
| 45 | 1*. Load the Zūm Wired firmware to the ZUMNET-JBOX | ||
| 46 | 1*. Repeat the above steps for all ZUMNET-JBOXs | ||
| |
8.1 | 47 | 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 |
| |
7.1 | 48 | 1. Connect to first ZUMNET-JBOX in the Crestron Zūm App |
| 49 | 1. Unique Connection IDs should be automatically assigned to any Zūm Link and Cresnet devices on the ZUMNET-JBOX | ||
| 50 | 1*. If firmware was out-of-date, then this step should have already been completed | ||
| 51 | 1*. If unique CIDs are not automatically assigned, connect to the JBOX in Toolbox and give the devices unique CIDs | ||
| 52 | 1. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network | ||
| 53 | 1*. If firmware was out-of-date, then this step should have already been completed | ||
| |
19.1 | 54 | 1*. Note: The ShowRunnerCLC™ built-in DHCP server is not meant to be used in production |
| 55 | 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 | ||
| |
7.1 | 56 | 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 |
| 57 | 1*. If you do not manually configure the IP table, then SHOWRUNNER™ will automatically configure the IP-ID for each ZUMNET-JBOX during discovery | ||
| |
13.1 | 58 | 1. Set the ZUMNET-JBOX into either Zūm ("App") mode or CNET mode as required for the program |
| |
19.1 | 59 | 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 |
| 60 | 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 | ||
| |
8.1 | 61 | 1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox |
| 62 | 1. Run the command: ##sr discover zumnet true false## | ||
| |
19.1 | 63 | 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 |
| |
7.1 | 64 | 1. Run the command: ##sr discover zumnet true true## |
| |
19.1 | 65 | 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 |
| |
12.1 | 66 | 1**. One area will be created per ZUMNET-JBOX, and all hardware attached to that ZUMNET-JBOX will be assigned to that area |
| |
7.1 | 67 | 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 |
| |
14.1 | 68 | 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. |
| |
6.2 | 69 | |
| |
5.2 | 70 | = Zūm Wireless Discovery = |
| |
1.1 | 71 | |
| |
5.2 | 72 | == Notes and Limitations == |
| |
1.1 | 73 | |
| |
16.2 | 74 | (% class="box warningmessage" %) |
| |
9.1 | 75 | ((( |
| |
19.1 | 76 | * Processor with ShowRunnerCLC™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired |
| 77 | ** For ShowRunnerCLC™ versions prior to 3.014 and newer, replace **##sr discover zummesh##** commands with **##sr discover zum##** | ||
| |
6.1 | 78 | * ZUM-NETBRIDGES must already be acquired to their respective gateway |
| |
19.1 | 79 | * ShowRunnerCLC™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices |
| |
6.1 | 80 | * Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command |
| |
19.1 | 81 | * Plug loads will not appear in the ShowRunnerCLC™ UI |
| |
4.1 | 82 | ))) |
| |
1.1 | 83 | |
| |
16.2 | 84 | (% class="box infomessage" id="HCaution:" %) |
| |
3.1 | 85 | ((( |
| |
19.1 | 86 | **Note:** ShowRunnerCLC™ has two different approaches for Zūm Wireless Discovery |
| |
4.1 | 87 | |
| |
19.1 | 88 | 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. |
| 89 | 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. | ||
| |
3.1 | 90 | ))) |
| |
1.1 | 91 | |
| |
6.2 | 92 | == Manual RF Gateway Assignment Instructions == |
| |
1.1 | 93 | |
| |
19.1 | 94 | Use this method if you have multiple ShowRunnerCLC™ instances on the same network or have gateways used by other Crestron systems. |
| |
1.1 | 95 | |
| |
2.1 | 96 | * Connect to the processor's console with Toolbox or your favorite SSH client. |
| |
9.1 | 97 | * Type ##sr devmgr ethernet query## and press enter. This queries the local network for RF Gateways. |
| 98 | * Type ##sr devmgr ethernet show devices## and press enter. This displays all found Crestron ethernet devices. | ||
| |
19.1 | 99 | * 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. |
| |
9.1 | 100 | * Type ##sr discover zummesh false## and press enter. |
| |
5.1 | 101 | * Status messages and the results will be displayed on the console. The process should take about 3 minutes. |
| |
19.1 | 102 | * 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. |
| 103 | * Type ##progreset## and press enter to restart ShowRunnerCLC™ | ||
| 104 | * 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. | ||
| |
5.1 | 105 | * Once completed SHOWRUNNER™ is now ready for full Zūm control |
| |
2.1 | 106 | |
| |
6.2 | 107 | == Claim All RF Gateways Instructions == |
| |
2.1 | 108 | |
| |
19.1 | 109 | Use this method when you have a single ShowRunnerCLC™ instance on a local network with all gateways being used for ShowRunnerCLC™. |
| |
2.1 | 110 | |
| 111 | * Connect to the processor's console with Toolbox or your favorite SSH client. | ||
| |
9.1 | 112 | * Type ##sr discover zummesh true## and press enter. |
| |
5.1 | 113 | * Status messages and the results will be displayed on the console. The process should take about 3 minutes. |
| |
19.1 | 114 | * 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. |
| 115 | * Type ##progreset## and press enter to restart ShowRunnerCLC™ | ||
| 116 | * 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. | ||
| 117 | * Once completed ShowRunnerCLC™ is now ready for full Zūm control | ||
| |
2.1 | 118 | |
| 119 | == Examples == | ||
| 120 | |||
| |
5.2 | 121 | === Manual Example === |
| |
4.1 | 122 | |
| 123 | {{{MC4>sr devmgr ethernet query | ||
| 124 | Ethrenet AutoDiscovery Result: AutoDiscoveryOperationSuccess | ||
| 125 | MC4>sr devmgr ethernet show devices | ||
| 126 | |||
| 127 | +--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ | ||
| 128 | | Adapter | Hostname | IP Address | IP-ID | ID | | ||
| 129 | +--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ | ||
| 130 | | EthernetLANAdapter | CI-SJC-CEN-CI3-1-COM3 | 10.44.5.20 | 00 | CEN-CI3-1-C3COM-3 [v1.1620.00000, #008436E2] type:1 | | ||
| 131 | +--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ | ||
| 132 | | EthernetLANAdapter | SB-DIN-CENCN-2 | 10.44.5.81 | 00 | DIN-CENCN-2-POE [v1.3544.00006, #8AB25AA3] | | ||
| 133 | +--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ | ||
| 134 | | EthernetLANAdapter | CEN-GWEXER-9E6ADA | 10.44.5.120 | 00 | CEN-GWEXER [v1.4230.00015, #848210AD] | | ||
| 135 | +--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+ | ||
| 136 | |||
| 137 | MC4>sr ethernet device claim CEN-GWEXER-9E6ADA | ||
| 138 | Claimed ethernet device: CEN-GWEXER-9E6ADA | ||
| 139 | MC4>Update request from IP-ID-30 in Program 01 | ||
| |
9.1 | 140 | MC4>sr discover zummesh false |
| |
4.1 | 141 | Starting Zum Discovery without gateway claiming |
| 142 | MC4>Performing Discovery on 1 Gateways. | ||
| |
2.1 | 143 | Evaluating 3 Devices on Gateway 30 |
| 144 | Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30 | ||
| 145 | Dev: ZUM-NETBRIDGE addrssing to RF ID: 03 | ||
| 146 | Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 03 | ||
| 147 | Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30 | ||
| 148 | Dev: ZUM-NETBRIDGE addrssing to RF ID: 04 | ||
| 149 | Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 04 | ||
| 150 | Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30 | ||
| 151 | Dev: ZUM-NETBRIDGE addrssing to RF ID: 05 | ||
| 152 | Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 05 | ||
| |
4.1 | 153 | Querying cresnet |
| |
2.1 | 154 | Discovering Zum Loads on 1 Gateways. |
| 155 | Discovering Zum Loads on 3 Devices. | ||
| 156 | NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0 | ||
| 157 | Device: ZUM Netbridge 30:03 at 30:03 discovery result: . | ||
| 158 | NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0 | ||
| 159 | Device: ZUM Netbridge 30:04 at 30:04 discovery result: . | ||
| 160 | NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0 | ||
| 161 | Device: ZUM Netbridge 30:05 at 30:05 discovery result: . | ||
| 162 | RF Gateways: 0 | ||
| 163 | RF Devices: 3 | ||
| 164 | New Loads: 0 | ||
| 165 | Modified Loads: 0 | ||
| 166 | Removed Loads: 0 | ||
| 167 | Zum Discovery Finished | ||
| 168 | MC4>sr save | ||
| 169 | Saved config | ||
| 170 | MC4>progreset | ||
| 171 | ... | ||
| 172 | CI ShowRunner startup completed successfully in 8072ms | ||
| |
9.1 | 173 | MC4>sr discover zummesh false |
| |
2.1 | 174 | Starting Zum Discovery without gateway claiming |
| 175 | MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable) | ||
| 176 | Performing Discovery on 1 Gateways. | ||
| 177 | Evaluating 3 Devices on Gateway 30 | ||
| 178 | Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30 | ||
| 179 | Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 03 | ||
| 180 | Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30 | ||
| 181 | Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 04 | ||
| 182 | Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30 | ||
| 183 | Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 05 | ||
| 184 | Discovering Zum Loads on 1 Gateways. | ||
| 185 | Discovering Zum Loads on 3 Devices. | ||
| 186 | Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio | ||
| 187 | Evaluating Device: ZUM-JBOX-20A-PLUG ShortAddress: 0000 Type: PlugLoad | ||
| 188 | Evaluating Device: ZUM-KP10C-BATT ShortAddress: 52E5 Type: Keypad | ||
| 189 | Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: DAF1 Type: OccupancySensor | ||
| 190 | Evaluating Device: ZUM-JBOX-5A-LV ShortAddress: 92EF Type: DimmableLoad | ||
| 191 | Load: Load37615 Added | ||
| 192 | NETBIRDGE: NewLoads: 1 ModifiedLoads: 0 RemovedLoads: 0 | ||
| 193 | Device: ZUM Netbridge 30:03 at 30:03 discovery result: . | ||
| 194 | Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio | ||
| 195 | Evaluating Device: ZUM-DALI ShortAddress: 740D Type: Unknown | ||
| 196 | Evaluating Device: ZUM-5A-LV ShortAddress: 0482 Type: DimmableLoad | ||
| 197 | Load: Load1154 Added | ||
| 198 | Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 0000 Type: DimmableLoad | ||
| 199 | Load: Load0 Added | ||
| 200 | Evaluating Device: ZUM-KP10C-BATT ShortAddress: D766 Type: Keypad | ||
| 201 | Evaluating Device: ZUM-OL-PHO-BATT ShortAddress: 95ED Type: Photocell | ||
| 202 | Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: 44C2 Type: OccupancySensor | ||
| 203 | Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown | ||
| 204 | Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown | ||
| 205 | NETBIRDGE: NewLoads: 2 ModifiedLoads: 0 RemovedLoads: 0 | ||
| 206 | Device: ZUM Netbridge 30:04 at 30:04 discovery result: . | ||
| 207 | Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio | ||
| 208 | Evaluating Device: ZUM-SIM ShortAddress: 0000 Type: OccupancySensor, PartitionSensor | ||
| 209 | Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: EBCF Type: DimmableLoad | ||
| 210 | Load: Load60367 Added | ||
| 211 | Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 3CC1 Type: DimmableLoad | ||
| 212 | Load: Load15553 Added | ||
| 213 | Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: F94A Type: DimmableLoad | ||
| 214 | Load: Load63818 Added | ||
| 215 | NETBIRDGE: NewLoads: 3 ModifiedLoads: 0 RemovedLoads: 0 | ||
| 216 | Device: ZUM Netbridge 30:05 at 30:05 discovery result: . | ||
| 217 | RF Gateways: 0 | ||
| 218 | RF Devices: 3 | ||
| 219 | New Loads: 6 | ||
| 220 | Modified Loads: 0 | ||
| 221 | Removed Loads: 0 | ||
| |
4.1 | 222 | Zum Discovery Finished}}} |
| |
2.1 | 223 | |
| |
5.1 | 224 | === Claim All Example === |
| |
2.1 | 225 | |
| |
9.1 | 226 | {{{MC4>sr discover zummesh true |
| |
4.1 | 227 | Starting Zum Discovery with gateway claiming |
| 228 | MC4>Found 1 Gateways to check. | ||
| 229 | Claimed Gateway SN: 1720JBH04269 at IP-ID: 30 | ||
| 230 | Update request from IP-ID-30 in Program 01 | ||
| 231 | Claimed 1 Gateways. Waiting for queries to finish. | ||
| 232 | Performing Discovery on 1 Gateways. | ||
| |
2.1 | 233 | Evaluating 3 Devices on Gateway 30 |
| 234 | Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30 | ||
| 235 | Dev: ZUM-NETBRIDGE addrssing to RF ID: 03 | ||
| 236 | Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 03 | ||
| 237 | Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30 | ||
| 238 | Dev: ZUM-NETBRIDGE addrssing to RF ID: 04 | ||
| 239 | Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 04 | ||
| 240 | Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30 | ||
| 241 | Dev: ZUM-NETBRIDGE addrssing to RF ID: 05 | ||
| 242 | Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 05 | ||
| 243 | Discovering Zum Loads on 1 Gateways. | ||
| 244 | Discovering Zum Loads on 3 Devices. | ||
| 245 | NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0 | ||
| 246 | Device: ZUM Netbridge 30:03 at 30:03 discovery result: . | ||
| 247 | NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0 | ||
| 248 | Device: ZUM Netbridge 30:04 at 30:04 discovery result: . | ||
| 249 | NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0 | ||
| 250 | Device: ZUM Netbridge 30:05 at 30:05 discovery result: . | ||
| 251 | RF Gateways: 0 | ||
| 252 | RF Devices: 3 | ||
| 253 | New Loads: 0 | ||
| 254 | Modified Loads: 0 | ||
| 255 | Removed Loads: 0 | ||
| 256 | Zum Discovery Finished | ||
| 257 | MC4>sr save | ||
| 258 | Saved config | ||
| 259 | MC4>progreset | ||
| 260 | ... | ||
| 261 | CI ShowRunner startup completed successfully in 8072ms | ||
| |
9.1 | 262 | MC4>sr discover zummesh false |
| |
2.1 | 263 | Starting Zum Discovery without gateway claiming |
| 264 | MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable) | ||
| 265 | Performing Discovery on 1 Gateways. | ||
| 266 | Evaluating 3 Devices on Gateway 30 | ||
| 267 | Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30 | ||
| 268 | Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 03 | ||
| 269 | Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30 | ||
| 270 | Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 04 | ||
| 271 | Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30 | ||
| 272 | Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 05 | ||
| 273 | Discovering Zum Loads on 1 Gateways. | ||
| 274 | Discovering Zum Loads on 3 Devices. | ||
| 275 | Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio | ||
| 276 | Evaluating Device: ZUM-JBOX-20A-PLUG ShortAddress: 0000 Type: PlugLoad | ||
| 277 | Evaluating Device: ZUM-KP10C-BATT ShortAddress: 52E5 Type: Keypad | ||
| 278 | Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: DAF1 Type: OccupancySensor | ||
| 279 | Evaluating Device: ZUM-JBOX-5A-LV ShortAddress: 92EF Type: DimmableLoad | ||
| 280 | Load: Load37615 Added | ||
| 281 | NETBIRDGE: NewLoads: 1 ModifiedLoads: 0 RemovedLoads: 0 | ||
| 282 | Device: ZUM Netbridge 30:03 at 30:03 discovery result: . | ||
| 283 | Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio | ||
| 284 | Evaluating Device: ZUM-DALI ShortAddress: 740D Type: Unknown | ||
| 285 | Evaluating Device: ZUM-5A-LV ShortAddress: 0482 Type: DimmableLoad | ||
| 286 | Load: Load1154 Added | ||
| 287 | Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 0000 Type: DimmableLoad | ||
| 288 | Load: Load0 Added | ||
| 289 | Evaluating Device: ZUM-KP10C-BATT ShortAddress: D766 Type: Keypad | ||
| 290 | Evaluating Device: ZUM-OL-PHO-BATT ShortAddress: 95ED Type: Photocell | ||
| 291 | Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: 44C2 Type: OccupancySensor | ||
| 292 | Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown | ||
| 293 | Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown | ||
| 294 | NETBIRDGE: NewLoads: 2 ModifiedLoads: 0 RemovedLoads: 0 | ||
| 295 | Device: ZUM Netbridge 30:04 at 30:04 discovery result: . | ||
| 296 | Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio | ||
| 297 | Evaluating Device: ZUM-SIM ShortAddress: 0000 Type: OccupancySensor, PartitionSensor | ||
| 298 | Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: EBCF Type: DimmableLoad | ||
| 299 | Load: Load60367 Added | ||
| 300 | Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 3CC1 Type: DimmableLoad | ||
| 301 | Load: Load15553 Added | ||
| 302 | Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: F94A Type: DimmableLoad | ||
| 303 | Load: Load63818 Added | ||
| 304 | NETBIRDGE: NewLoads: 3 ModifiedLoads: 0 RemovedLoads: 0 | ||
| 305 | Device: ZUM Netbridge 30:05 at 30:05 discovery result: . | ||
| 306 | RF Gateways: 0 | ||
| 307 | RF Devices: 3 | ||
| 308 | New Loads: 6 | ||
| 309 | Modified Loads: 0 | ||
| 310 | Removed Loads: 0 | ||
| 311 | Zum Discovery Finished | ||
| |
4.1 | 312 | }}} |