Skip to Content

Changes for page Zūm Discovery

Last modified by Austin Weygandt on 2025/05/02 20:21
From version 1.2
edited by Alexander Mott
on 2022/09/22 21:31
Change comment: There is no comment for this version
To version 21.1
edited by Alexander Mott
on 2023/10/11 16:37
Change comment: There is no comment for this version

Summary

Details

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