Wiki source code of Zūm Discovery

Last modified by Alexander Mott on 2026/06/05 18:07

Hide last authors
Alexander Mott 15.1 1 (% class="box errormessage" %)
2 (((
Alexander Mott 42.1 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.
Alexander Mott 23.1 4
Alexander Mott 22.1 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.
Alexander Mott 15.1 7 )))
Alexander Mott 16.1 8
Alexander Mott 1.1 9 (% class="box warningmessage" %)
10 (((
Alexander Mott 24.1 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]].
Alexander Mott 1.1 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
Scott Kohlmann 19.1 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™.
Alexander Mott 1.1 20
Scott Kohlmann 19.1 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.
Alexander Mott 1.1 22
Mark Kohlmann 34.1 23 = Discovery Filter (ShowRunnerCLC™ 3.062 or newer) =
Mark Kohlmann 33.1 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
Mark Kohlmann 34.1 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.
Mark Kohlmann 33.1 39
40 Command Syntax: ##"Type='Hostname' Settings='Expr1[,Expr2]'"##
41
42 Examples:
43
44 1. Only include hostnames that start with ZUMNET-06:
Mark Kohlmann 34.1 45 (% style="font-family:Menlo,Monaco,Consolas,Courier New,monospace; white-space:pre" %)sr discover filter "Type='Hostname' Settings='^ZUMNET-06'"
Mark Kohlmann 33.1 46 1. Include hostnames that start with ZUMNET-FL01 or contain FL03:
Mark Kohlmann 34.1 47 (% style="font-family:Menlo,Monaco,Consolas,Courier New,monospace; white-space:pre" %)sr discover filter "Type='Hostname' Settings='^ZUMNET-FL01,FL03'"
Mark Kohlmann 33.1 48
Mark Kohlmann 34.1 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
Mark Kohlmann 37.1 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
Alexander Mott 5.2 75 = Zūm Wired Discovery =
76
Alexander Mott 6.1 77 == Notes and Limitations ==
Alexander Mott 1.1 78
Alexander Mott 15.1 79 (% class="box warningmessage" %)
Alexander Mott 9.1 80 (((
Scott Kohlmann 19.1 81 * ShowRunnerCLC™ version 3.014 or newer required
Alexander Mott 13.1 82 * Zūm Wired firmware .puf version 1.02.10 or greater required (ZUMNET-JBOX installed minimum version 1.001.00081)
Craig Lewis 30.1 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
Alexander Mott 6.2 84 * Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release)
Craig Lewis 31.1 85 * ZUMLINK-IOs will not be discovered (Expected to be discoverable in future ShowRunnerCLC™ release)
Craig Lewis 32.1 86 * ZUMLINK-KPs will not be discovered on older versions of ShowRunnerCLC™ (v3.058 or newer will discover keypads and set as remote type)
Alexander Mott 6.2 87 * One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually
Craig Lewis 44.1 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.
Alexander Mott 9.1 89 )))
Alexander Mott 6.1 90
Alexander Mott 6.2 91 == Steps ==
92
Scott Kohlmann 19.1 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
Alexander Mott 7.1 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 
Scott Kohlmann 19.1 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
Alexander Mott 7.1 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
Alexander Mott 8.1 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
Craig Lewis 24.2 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)
Craig Lewis 24.3 109 1*. Set hostnames for the ZUMNETs.
110 1**. Zūm discovery will bring in hostnames.
Alexander Mott 7.1 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
Scott Kohlmann 19.1 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
Alexander Mott 7.1 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
Alexander Mott 13.1 120 1. Set the ZUMNET-JBOX into either Zūm ("App") mode or CNET mode as required for the program
Scott Kohlmann 19.1 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
Alexander Mott 8.1 123 1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox
Alexander Mott 36.1 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
Alexander Mott 38.1 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
Alexander Mott 14.1 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.
Alexander Mott 35.1 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
Alexander Mott 6.2 137
Alexander Mott 5.2 138 = Zūm Wireless Discovery =
Alexander Mott 1.1 139
Alexander Mott 5.2 140 == Notes and Limitations ==
Alexander Mott 1.1 141
Alexander Mott 16.2 142 (% class="box warningmessage" %)
Alexander Mott 9.1 143 (((
Austin Weygandt 41.1 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**
Scott Kohlmann 19.1 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##**
Alexander Mott 6.1 147 * ZUM-NETBRIDGES must already be acquired to their respective gateway
Scott Kohlmann 19.1 148 * ShowRunnerCLC™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices
Alexander Mott 6.1 149 * Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command
Scott Kohlmann 19.1 150 * Plug loads will not appear in the ShowRunnerCLC™ UI
Alexander Mott 4.1 151 )))
Alexander Mott 1.1 152
Alexander Mott 16.2 153 (% class="box infomessage" id="HCaution:" %)
Alexander Mott 3.1 154 (((
Scott Kohlmann 19.1 155 **Note:** ShowRunnerCLC™ has two different approaches for Zūm Wireless Discovery
Alexander Mott 4.1 156
Scott Kohlmann 19.1 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.
Alexander Mott 3.1 159 )))
Alexander Mott 1.1 160
Alexander Mott 40.1 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
Alexander Mott 6.2 193 == Manual RF Gateway Assignment Instructions ==
Alexander Mott 1.1 194
Scott Kohlmann 19.1 195 Use this method if you have multiple ShowRunnerCLC™ instances on the same network or have gateways used by other Crestron systems.
Alexander Mott 1.1 196
Alexander Mott 2.1 197 * Connect to the processor's console with Toolbox or your favorite SSH client.
Alexander Mott 9.1 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.
Scott Kohlmann 19.1 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.
Alexander Mott 45.1 201 * Run ##sr save## and then ##progreset##
Alexander Mott 9.1 202 * Type ##sr discover zummesh false## and press enter.
Alexander Mott 5.1 203 * Status messages and the results will be displayed on the console. The process should take about 3 minutes.
Scott Kohlmann 19.1 204 * 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.
205 * Type ##progreset## and press enter to restart ShowRunnerCLC™
206 * 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.
Alexander Mott 5.1 207 * Once completed SHOWRUNNER™ is now ready for full Zūm control
Alexander Mott 2.1 208
Alexander Mott 6.2 209 == Claim All RF Gateways Instructions ==
Alexander Mott 2.1 210
Scott Kohlmann 19.1 211 Use this method when you have a single ShowRunnerCLC™ instance on a local network with all gateways being used for ShowRunnerCLC™.
Alexander Mott 2.1 212
213 * Connect to the processor's console with Toolbox or your favorite SSH client.
Alexander Mott 38.2 214 * 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.
Alexander Mott 45.1 215 * Run ##sr save## and then ##progreset##
Alexander Mott 38.2 216 * Type ##sr discover zummesh false## and press enter.
Alexander Mott 5.1 217 * Status messages and the results will be displayed on the console. The process should take about 3 minutes.
Scott Kohlmann 19.1 218 * 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.
219 * Type ##progreset## and press enter to restart ShowRunnerCLC™
220 * 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.
221 * Once completed ShowRunnerCLC™ is now ready for full Zūm control
Alexander Mott 2.1 222
223 == Examples ==
224
Alexander Mott 5.2 225 === Manual Example ===
Alexander Mott 4.1 226
227 {{{MC4>sr devmgr ethernet query
228 Ethrenet AutoDiscovery Result: AutoDiscoveryOperationSuccess
229 MC4>sr devmgr ethernet show devices
230
231 +--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
232 | Adapter | Hostname | IP Address | IP-ID | ID |
233 +--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
234 | EthernetLANAdapter | CI-SJC-CEN-CI3-1-COM3 | 10.44.5.20 | 00 | CEN-CI3-1-C3COM-3 [v1.1620.00000, #008436E2] type:1 |
235 +--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
236 | EthernetLANAdapter | SB-DIN-CENCN-2 | 10.44.5.81 | 00 | DIN-CENCN-2-POE [v1.3544.00006, #8AB25AA3] |
237 +--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
238 | EthernetLANAdapter | CEN-GWEXER-9E6ADA | 10.44.5.120 | 00 | CEN-GWEXER [v1.4230.00015, #848210AD] |
239 +--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
240
241 MC4>sr ethernet device claim CEN-GWEXER-9E6ADA
242 Claimed ethernet device: CEN-GWEXER-9E6ADA
243 MC4>Update request from IP-ID-30 in Program 01
Alexander Mott 9.1 244 MC4>sr discover zummesh false
Alexander Mott 4.1 245 Starting Zum Discovery without gateway claiming
246 MC4>Performing Discovery on 1 Gateways.
Alexander Mott 2.1 247 Evaluating 3 Devices on Gateway 30
248 Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30
249 Dev: ZUM-NETBRIDGE addrssing to RF ID: 03
250 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 03
251 Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30
252 Dev: ZUM-NETBRIDGE addrssing to RF ID: 04
253 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 04
254 Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30
255 Dev: ZUM-NETBRIDGE addrssing to RF ID: 05
256 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 05
Alexander Mott 4.1 257 Querying cresnet
Alexander Mott 2.1 258 Discovering Zum Loads on 1 Gateways.
259 Discovering Zum Loads on 3 Devices.
260 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
261 Device: ZUM Netbridge 30:03 at 30:03 discovery result: .
262 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
263 Device: ZUM Netbridge 30:04 at 30:04 discovery result: .
264 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
265 Device: ZUM Netbridge 30:05 at 30:05 discovery result: .
266 RF Gateways: 0
267 RF Devices: 3
268 New Loads: 0
269 Modified Loads: 0
270 Removed Loads: 0
271 Zum Discovery Finished
272 MC4>sr save
273 Saved config
274 MC4>progreset
275 ...
276 CI ShowRunner startup completed successfully in 8072ms
Alexander Mott 9.1 277 MC4>sr discover zummesh false
Alexander Mott 2.1 278 Starting Zum Discovery without gateway claiming
279 MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable)
280 Performing Discovery on 1 Gateways.
281 Evaluating 3 Devices on Gateway 30
282 Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30
283 Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 03
284 Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30
285 Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 04
286 Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30
287 Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 05
288 Discovering Zum Loads on 1 Gateways.
289 Discovering Zum Loads on 3 Devices.
290 Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
291 Evaluating Device: ZUM-JBOX-20A-PLUG ShortAddress: 0000 Type: PlugLoad
292 Evaluating Device: ZUM-KP10C-BATT ShortAddress: 52E5 Type: Keypad
293 Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: DAF1 Type: OccupancySensor
294 Evaluating Device: ZUM-JBOX-5A-LV ShortAddress: 92EF Type: DimmableLoad
295 Load: Load37615 Added
296 NETBIRDGE: NewLoads: 1 ModifiedLoads: 0 RemovedLoads: 0
297 Device: ZUM Netbridge 30:03 at 30:03 discovery result: .
298 Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
299 Evaluating Device: ZUM-DALI ShortAddress: 740D Type: Unknown
300 Evaluating Device: ZUM-5A-LV ShortAddress: 0482 Type: DimmableLoad
301 Load: Load1154 Added
302 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 0000 Type: DimmableLoad
303 Load: Load0 Added
304 Evaluating Device: ZUM-KP10C-BATT ShortAddress: D766 Type: Keypad
305 Evaluating Device: ZUM-OL-PHO-BATT ShortAddress: 95ED Type: Photocell
306 Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: 44C2 Type: OccupancySensor
307 Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown
308 Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown
309 NETBIRDGE: NewLoads: 2 ModifiedLoads: 0 RemovedLoads: 0
310 Device: ZUM Netbridge 30:04 at 30:04 discovery result: .
311 Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
312 Evaluating Device: ZUM-SIM ShortAddress: 0000 Type: OccupancySensor, PartitionSensor
313 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: EBCF Type: DimmableLoad
314 Load: Load60367 Added
315 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 3CC1 Type: DimmableLoad
316 Load: Load15553 Added
317 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: F94A Type: DimmableLoad
318 Load: Load63818 Added
319 NETBIRDGE: NewLoads: 3 ModifiedLoads: 0 RemovedLoads: 0
320 Device: ZUM Netbridge 30:05 at 30:05 discovery result: .
321 RF Gateways: 0
322 RF Devices: 3
323 New Loads: 6
324 Modified Loads: 0
325 Removed Loads: 0
Alexander Mott 4.1 326 Zum Discovery Finished}}}
Alexander Mott 2.1 327
Alexander Mott 5.1 328 === Claim All Example ===
Alexander Mott 2.1 329
Alexander Mott 9.1 330 {{{MC4>sr discover zummesh true
Alexander Mott 4.1 331 Starting Zum Discovery with gateway claiming
332 MC4>Found 1 Gateways to check.
333 Claimed Gateway SN: 1720JBH04269 at IP-ID: 30
334 Update request from IP-ID-30 in Program 01
335 Claimed 1 Gateways. Waiting for queries to finish.
336 Performing Discovery on 1 Gateways.
Alexander Mott 2.1 337 Evaluating 3 Devices on Gateway 30
338 Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30
339 Dev: ZUM-NETBRIDGE addrssing to RF ID: 03
340 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 03
341 Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30
342 Dev: ZUM-NETBRIDGE addrssing to RF ID: 04
343 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 04
344 Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30
345 Dev: ZUM-NETBRIDGE addrssing to RF ID: 05
346 Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 05
347 Discovering Zum Loads on 1 Gateways.
348 Discovering Zum Loads on 3 Devices.
349 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
350 Device: ZUM Netbridge 30:03 at 30:03 discovery result: .
351 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
352 Device: ZUM Netbridge 30:04 at 30:04 discovery result: .
353 NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
354 Device: ZUM Netbridge 30:05 at 30:05 discovery result: .
355 RF Gateways: 0
356 RF Devices: 3
357 New Loads: 0
358 Modified Loads: 0
359 Removed Loads: 0
360 Zum Discovery Finished
361 MC4>sr save
362 Saved config
363 MC4>progreset
364 ...
365 CI ShowRunner startup completed successfully in 8072ms
Alexander Mott 9.1 366 MC4>sr discover zummesh false
Alexander Mott 2.1 367 Starting Zum Discovery without gateway claiming
368 MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable)
369 Performing Discovery on 1 Gateways.
370 Evaluating 3 Devices on Gateway 30
371 Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30
372 Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 03
373 Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30
374 Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 04
375 Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30
376 Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 05
377 Discovering Zum Loads on 1 Gateways.
378 Discovering Zum Loads on 3 Devices.
379 Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
380 Evaluating Device: ZUM-JBOX-20A-PLUG ShortAddress: 0000 Type: PlugLoad
381 Evaluating Device: ZUM-KP10C-BATT ShortAddress: 52E5 Type: Keypad
382 Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: DAF1 Type: OccupancySensor
383 Evaluating Device: ZUM-JBOX-5A-LV ShortAddress: 92EF Type: DimmableLoad
384 Load: Load37615 Added
385 NETBIRDGE: NewLoads: 1 ModifiedLoads: 0 RemovedLoads: 0
386 Device: ZUM Netbridge 30:03 at 30:03 discovery result: .
387 Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
388 Evaluating Device: ZUM-DALI ShortAddress: 740D Type: Unknown
389 Evaluating Device: ZUM-5A-LV ShortAddress: 0482 Type: DimmableLoad
390 Load: Load1154 Added
391 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 0000 Type: DimmableLoad
392 Load: Load0 Added
393 Evaluating Device: ZUM-KP10C-BATT ShortAddress: D766 Type: Keypad
394 Evaluating Device: ZUM-OL-PHO-BATT ShortAddress: 95ED Type: Photocell
395 Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: 44C2 Type: OccupancySensor
396 Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown
397 Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown
398 NETBIRDGE: NewLoads: 2 ModifiedLoads: 0 RemovedLoads: 0
399 Device: ZUM Netbridge 30:04 at 30:04 discovery result: .
400 Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
401 Evaluating Device: ZUM-SIM ShortAddress: 0000 Type: OccupancySensor, PartitionSensor
402 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: EBCF Type: DimmableLoad
403 Load: Load60367 Added
404 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 3CC1 Type: DimmableLoad
405 Load: Load15553 Added
406 Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: F94A Type: DimmableLoad
407 Load: Load63818 Added
408 NETBIRDGE: NewLoads: 3 ModifiedLoads: 0 RemovedLoads: 0
409 Device: ZUM Netbridge 30:05 at 30:05 discovery result: .
410 RF Gateways: 0
411 RF Devices: 3
412 New Loads: 6
413 Modified Loads: 0
414 Removed Loads: 0
415 Zum Discovery Finished
Alexander Mott 4.1 416 }}}