Wiki source code of Zūm Discovery

Version 37.1 by Mark Kohlmann on 2025/01/15 00:56

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