Skip to Content

Wiki source code of Zūm Discovery

Last modified by Craig Lewis on 2025/09/25 20:36
Show last authors
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 (% class="box warningmessage" %)
10 (((
11 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]].
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 )))
14
15 {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
16 {{toc/}}
17 {{/box}}
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™.
20
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.
22
23 = Discovery Filter (ShowRunnerCLC™ 3.062 or newer) =
24
25 Discovered ethernet devices may be filtered using either a hostname or IP Address filter.  The filter is configured from the command line interface.
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
36 === Hostname Filter ===
37
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.
39
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
88 * ZUMNET-JBOX-DALI will be created with only 1 broadcast load index 17. If ZUMNET is being setup in CNET mode as a LEGACY controller, the config will need to be updated to reflect the model as ZUMNET-JBOX-DALI-LEGACY.
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## to add ZUMNET-JBOXs, connected ZUMLINK devices, and some Cresnet devices (such as Cameo keypads) to the configuration. (Note
126 1*. This command will update the ShowRunnerCLC™ configuration with: 
127 1**. One area per claimed ZUMNET-JBOX based on the Room Name set in the app
128 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™
129 1**. One entry for each ZUMLINK-KP, ZUMLINK-JBOX, and ZUMLINK occupancy sensor connected to each ZUMNET-JBOX
130 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
131 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™
132 1***. Occupancy sensors will be brought in with "Use Hardware Logic" and only follow the logic as defined in the Zūm App
133 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**
134 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
135 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.
136 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
137
138 = Zūm Wireless Discovery =
139
140 == Notes and Limitations ==
141
142 (% class="box warningmessage" %)
143 (((
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 * Processor with ShowRunnerCLC™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired
146 ** For ShowRunnerCLC™ versions prior to 3.014 and newer, replace **##sr discover zummesh##** commands with **##sr discover zum##**
147 * ZUM-NETBRIDGES must already be acquired to their respective gateway
148 * ShowRunnerCLC™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices
149 * Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command
150 * Plug loads will not appear in the ShowRunnerCLC™ UI
151 )))
152
153 (% class="box infomessage" id="HCaution:" %)
154 (((
155 **Note:** ShowRunnerCLC™ has two different approaches for Zūm Wireless Discovery
156
157 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.
158 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.
159 )))
160
161 (% class="box errormessage" id="HCaution:" %)
162 (((
163 **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.
164
165 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.
166
167 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.
168
169 {{{ "Eiscs": [],
170 "IpDevices": [
171 {
172 "Model": "CEN-GWEXER",
173 "Name": "GW-1-1",
174 "SerialNumber": "2402NEJ03956",
175 "IpId": 48
176 },
177 {
178 "Model": "CEN-GWEXER",
179 "Name": "GW-1-2",
180 "SerialNumber": "2402NEJ03862",
181 "IpId": 49
182 },
183 {
184 "Model": "CEN-GWEXER",
185 "Name": "GW-2-1",
186 "SerialNumber": "2402NEJ03887",
187 "IpId": 50
188 }
189 ],
190 "Keyswitches": [],}}}
191 )))
192
193 == Manual RF Gateway Assignment Instructions ==
194
195 Use this method if you have multiple ShowRunnerCLC™ instances on the same network or have gateways used by other Crestron systems.
196
197 * Connect to the processor's console with Toolbox or your favorite SSH client.
198 * Type ##sr devmgr ethernet query## and press enter. This queries the local network for RF Gateways.
199 * Type ##sr devmgr ethernet show devices## and press enter. This displays all found Crestron ethernet devices.
200 * 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.
201 * Type ##sr discover zummesh false## and press enter.
202 * Status messages and the results will be displayed on the console. The process should take about 3 minutes.
203 * 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.
204 * Type ##progreset## and press enter to restart ShowRunnerCLC™
205 * 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.
206 * Once completed SHOWRUNNER™ is now ready for full Zūm control
207
208 == Claim All RF Gateways Instructions ==
209
210 Use this method when you have a single ShowRunnerCLC™ instance on a local network with all gateways being used for ShowRunnerCLC™.
211
212 * Connect to the processor's console with Toolbox or your favorite SSH client.
213 * 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.
214 * Type ##sr discover zummesh false## and press enter.
215 * Status messages and the results will be displayed on the console. The process should take about 3 minutes.
216 * 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.
217 * Type ##progreset## and press enter to restart ShowRunnerCLC™
218 * 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.
219 * Once completed ShowRunnerCLC™ is now ready for full Zūm control
220
221 == Examples ==
222
223 === Manual Example ===
224
225 {{{MC4>sr devmgr ethernet query
226 Ethrenet AutoDiscovery Result: AutoDiscoveryOperationSuccess
227 MC4>sr devmgr ethernet show devices
228
229 +--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
230 | Adapter | Hostname | IP Address | IP-ID | ID |
231 +--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
232 | EthernetLANAdapter | CI-SJC-CEN-CI3-1-COM3 | 10.44.5.20 | 00 | CEN-CI3-1-C3COM-3 [v1.1620.00000, #008436E2] type:1 |
233 +--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
234 | EthernetLANAdapter | SB-DIN-CENCN-2 | 10.44.5.81 | 00 | DIN-CENCN-2-POE [v1.3544.00006, #8AB25AA3] |
235 +--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
236 | EthernetLANAdapter | CEN-GWEXER-9E6ADA | 10.44.5.120 | 00 | CEN-GWEXER [v1.4230.00015, #848210AD] |
237 +--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
238
239 MC4>sr ethernet device claim CEN-GWEXER-9E6ADA
240 Claimed ethernet device: CEN-GWEXER-9E6ADA
241 MC4>Update request from IP-ID-30 in Program 01
242 MC4>sr discover zummesh false
243 Starting Zum Discovery without gateway claiming
244 MC4>Performing Discovery on 1 Gateways.
245 Evaluating 3 Devices on Gateway 30
246 Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30
247 Dev: ZUM-NETBRIDGE addrssing to RF ID: 03
248 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 03
249 Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30
250 Dev: ZUM-NETBRIDGE addrssing to RF ID: 04
251 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 04
252 Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30
253 Dev: ZUM-NETBRIDGE addrssing to RF ID: 05
254 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 05
255 Querying cresnet
256 Discovering Zum Loads on 1 Gateways.
257 Discovering Zum Loads on 3 Devices.
258 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
259 Device: ZUM Netbridge 30:03 at 30:03 discovery result: .
260 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
261 Device: ZUM Netbridge 30:04 at 30:04 discovery result: .
262 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
263 Device: ZUM Netbridge 30:05 at 30:05 discovery result: .
264 RF Gateways: 0
265 RF Devices: 3
266 New Loads: 0
267 Modified Loads: 0
268 Removed Loads: 0
269 Zum Discovery Finished
270 MC4>sr save
271 Saved config
272 MC4>progreset
273 ...
274 CI ShowRunner startup completed successfully in 8072ms
275 MC4>sr discover zummesh false
276 Starting Zum Discovery without gateway claiming
277 MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable)
278 Performing Discovery on 1 Gateways.
279 Evaluating 3 Devices on Gateway 30
280 Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30
281 Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 03
282 Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30
283 Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 04
284 Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30
285 Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 05
286 Discovering Zum Loads on 1 Gateways.
287 Discovering Zum Loads on 3 Devices.
288 Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
289 Evaluating Device: ZUM-JBOX-20A-PLUG ShortAddress: 0000 Type: PlugLoad
290 Evaluating Device: ZUM-KP10C-BATT ShortAddress: 52E5 Type: Keypad
291 Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: DAF1 Type: OccupancySensor
292 Evaluating Device: ZUM-JBOX-5A-LV ShortAddress: 92EF Type: DimmableLoad
293 Load: Load37615 Added
294 NETBIRDGE: NewLoads: 1 ModifiedLoads: 0 RemovedLoads: 0
295 Device: ZUM Netbridge 30:03 at 30:03 discovery result: .
296 Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
297 Evaluating Device: ZUM-DALI ShortAddress: 740D Type: Unknown
298 Evaluating Device: ZUM-5A-LV ShortAddress: 0482 Type: DimmableLoad
299 Load: Load1154 Added
300 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 0000 Type: DimmableLoad
301 Load: Load0 Added
302 Evaluating Device: ZUM-KP10C-BATT ShortAddress: D766 Type: Keypad
303 Evaluating Device: ZUM-OL-PHO-BATT ShortAddress: 95ED Type: Photocell
304 Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: 44C2 Type: OccupancySensor
305 Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown
306 Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown
307 NETBIRDGE: NewLoads: 2 ModifiedLoads: 0 RemovedLoads: 0
308 Device: ZUM Netbridge 30:04 at 30:04 discovery result: .
309 Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
310 Evaluating Device: ZUM-SIM ShortAddress: 0000 Type: OccupancySensor, PartitionSensor
311 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: EBCF Type: DimmableLoad
312 Load: Load60367 Added
313 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 3CC1 Type: DimmableLoad
314 Load: Load15553 Added
315 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: F94A Type: DimmableLoad
316 Load: Load63818 Added
317 NETBIRDGE: NewLoads: 3 ModifiedLoads: 0 RemovedLoads: 0
318 Device: ZUM Netbridge 30:05 at 30:05 discovery result: .
319 RF Gateways: 0
320 RF Devices: 3
321 New Loads: 6
322 Modified Loads: 0
323 Removed Loads: 0
324 Zum Discovery Finished}}}
325
326 === Claim All Example ===
327
328 {{{MC4>sr discover zummesh true
329 Starting Zum Discovery with gateway claiming
330 MC4>Found 1 Gateways to check.
331 Claimed Gateway SN: 1720JBH04269 at IP-ID: 30
332 Update request from IP-ID-30 in Program 01
333 Claimed 1 Gateways. Waiting for queries to finish.
334 Performing Discovery on 1 Gateways.
335 Evaluating 3 Devices on Gateway 30
336 Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30
337 Dev: ZUM-NETBRIDGE addrssing to RF ID: 03
338 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 03
339 Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30
340 Dev: ZUM-NETBRIDGE addrssing to RF ID: 04
341 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 04
342 Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30
343 Dev: ZUM-NETBRIDGE addrssing to RF ID: 05
344 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 05
345 Discovering Zum Loads on 1 Gateways.
346 Discovering Zum Loads on 3 Devices.
347 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
348 Device: ZUM Netbridge 30:03 at 30:03 discovery result: .
349 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
350 Device: ZUM Netbridge 30:04 at 30:04 discovery result: .
351 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
352 Device: ZUM Netbridge 30:05 at 30:05 discovery result: .
353 RF Gateways: 0
354 RF Devices: 3
355 New Loads: 0
356 Modified Loads: 0
357 Removed Loads: 0
358 Zum Discovery Finished
359 MC4>sr save
360 Saved config
361 MC4>progreset
362 ...
363 CI ShowRunner startup completed successfully in 8072ms
364 MC4>sr discover zummesh false
365 Starting Zum Discovery without gateway claiming
366 MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable)
367 Performing Discovery on 1 Gateways.
368 Evaluating 3 Devices on Gateway 30
369 Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30
370 Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 03
371 Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30
372 Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 04
373 Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30
374 Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 05
375 Discovering Zum Loads on 1 Gateways.
376 Discovering Zum Loads on 3 Devices.
377 Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
378 Evaluating Device: ZUM-JBOX-20A-PLUG ShortAddress: 0000 Type: PlugLoad
379 Evaluating Device: ZUM-KP10C-BATT ShortAddress: 52E5 Type: Keypad
380 Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: DAF1 Type: OccupancySensor
381 Evaluating Device: ZUM-JBOX-5A-LV ShortAddress: 92EF Type: DimmableLoad
382 Load: Load37615 Added
383 NETBIRDGE: NewLoads: 1 ModifiedLoads: 0 RemovedLoads: 0
384 Device: ZUM Netbridge 30:03 at 30:03 discovery result: .
385 Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
386 Evaluating Device: ZUM-DALI ShortAddress: 740D Type: Unknown
387 Evaluating Device: ZUM-5A-LV ShortAddress: 0482 Type: DimmableLoad
388 Load: Load1154 Added
389 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 0000 Type: DimmableLoad
390 Load: Load0 Added
391 Evaluating Device: ZUM-KP10C-BATT ShortAddress: D766 Type: Keypad
392 Evaluating Device: ZUM-OL-PHO-BATT ShortAddress: 95ED Type: Photocell
393 Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: 44C2 Type: OccupancySensor
394 Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown
395 Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown
396 NETBIRDGE: NewLoads: 2 ModifiedLoads: 0 RemovedLoads: 0
397 Device: ZUM Netbridge 30:04 at 30:04 discovery result: .
398 Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
399 Evaluating Device: ZUM-SIM ShortAddress: 0000 Type: OccupancySensor, PartitionSensor
400 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: EBCF Type: DimmableLoad
401 Load: Load60367 Added
402 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 3CC1 Type: DimmableLoad
403 Load: Load15553 Added
404 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: F94A Type: DimmableLoad
405 Load: Load63818 Added
406 NETBIRDGE: NewLoads: 3 ModifiedLoads: 0 RemovedLoads: 0
407 Device: ZUM Netbridge 30:05 at 30:05 discovery result: .
408 RF Gateways: 0
409 RF Devices: 3
410 New Loads: 6
411 Modified Loads: 0
412 Removed Loads: 0
413 Zum Discovery Finished
414 }}}