Wiki source code of Zūm Discovery

Version 39.1 by Alexander Mott on 2025/04/03 16:11

version	line-number	content
15.1	1	(% class="box errormessage" %)
	2	(((
38.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.
23.1	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	=== 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
5.2	75	= Zūm Wired Discovery =
	76
6.1	77	== Notes and Limitations ==
1.1	78
15.1	79	(% class="box warningmessage" %)
9.1	80	(((
19.1	81	* ShowRunnerCLC™ version 3.014 or newer required
13.1	82	* Zūm Wired firmware .puf version 1.02.10 or greater required (ZUMNET-JBOX installed minimum version 1.001.00081)
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
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)
31.1	85	* ZUMLINK-IOs will not be discovered (Expected to be discoverable in future ShowRunnerCLC™ release)
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)
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
9.1	88	)))
6.1	89
6.2	90	== Steps ==
	91
19.1	92	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	93	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.
	94	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:
	95	1*. Connect to the first ZUMNET-JBOX in Toolbox
	96	1*. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network
19.1	97	1**. Note: The ShowRunnerCLC™ built-in DHCP server is not meant to be used in production
	98	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	99	1*. Set unique Connection IDs for each device hosted on the ZUMNET-JBOX so that their firmware can be updated
	100	1*. Load the Zūm Wired firmware to the ZUMNET-JBOX
	101	1*. Repeat the above steps for all ZUMNET-JBOXs
8.1	102	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	103	1. Connect to each ZUMNET-JBOX in the Crestron Zūm App
	104	1*. Commission room through the app
	105	1**. configure keypad logic
	106	1**. configure occupancy sensor settings
	107	1**. calibrate photocell(s)
24.3	108	1*. Set hostnames for the ZUMNETs.
	109	1**. Zūm discovery will bring in hostnames.
7.1	110	1. Unique Connection IDs should be automatically assigned to any Zūm Link and Cresnet devices on the ZUMNET-JBOX
	111	1*. If firmware was out-of-date, then this step should have already been completed
	112	1*. If unique CIDs are not automatically assigned, connect to the JBOX in Toolbox and give the devices unique CIDs
	113	1. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network
	114	1*. If firmware was out-of-date, then this step should have already been completed
19.1	115	1*. Note: The ShowRunnerCLC™ built-in DHCP server is not meant to be used in production
	116	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	117	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
	118	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	119	1. Set the ZUMNET-JBOX into either Zūm ("App") mode or CNET mode as required for the program
19.1	120	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
	121	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	122	1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox
36.1	123	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
38.1	124	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
	125	1*. This command will update the ShowRunnerCLC™ configuration with:
	126	1**. One area per claimed ZUMNET-JBOX based on the Room Name set in the app
	127	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™
	128	1**. One entry for each ZUMLINK-KP, ZUMLINK-JBOX, and ZUMLINK occupancy sensor connected to each ZUMNET-JBOX
	129	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
	130	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™
	131	1***. Occupancy sensors will be brought in with "Use Hardware Logic" and only follow the logic as defined in the Zūm App
	132	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*
	133	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
14.1	134	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	135	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	136
5.2	137	= Zūm Wireless Discovery =
1.1	138
5.2	139	== Notes and Limitations ==
1.1	140
16.2	141	(% class="box warningmessage" %)
9.1	142	(((
19.1	143	* Processor with ShowRunnerCLC™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired
	144	For ShowRunnerCLC™ versions prior to 3.014 and newer, replace ##sr discover zummesh## commands with ##sr discover zum##**
6.1	145	* ZUM-NETBRIDGES must already be acquired to their respective gateway
19.1	146	* ShowRunnerCLC™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices
6.1	147	* Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command
19.1	148	* Plug loads will not appear in the ShowRunnerCLC™ UI
28.1	149	* 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	150	)))
1.1	151
16.2	152	(% class="box infomessage" id="HCaution:" %)
3.1	153	(((
19.1	154	Note: ShowRunnerCLC™ has two different approaches for Zūm Wireless Discovery
4.1	155
19.1	156	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.
	157	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	158	)))
1.1	159
6.2	160	== Manual RF Gateway Assignment Instructions ==
1.1	161
19.1	162	Use this method if you have multiple ShowRunnerCLC™ instances on the same network or have gateways used by other Crestron systems.
1.1	163
2.1	164	* Connect to the processor's console with Toolbox or your favorite SSH client.
9.1	165	* Type ##sr devmgr ethernet query## and press enter. This queries the local network for RF Gateways.
	166	* Type ##sr devmgr ethernet show devices## and press enter. This displays all found Crestron ethernet devices.
19.1	167	* 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	168	* Type ##sr discover zummesh false## and press enter.
5.1	169	* Status messages and the results will be displayed on the console. The process should take about 3 minutes.
19.1	170	* 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.
	171	* Type ##progreset## and press enter to restart ShowRunnerCLC™
	172	* 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	173	* Once completed SHOWRUNNER™ is now ready for full Zūm control
2.1	174
6.2	175	== Claim All RF Gateways Instructions ==
2.1	176
19.1	177	Use this method when you have a single ShowRunnerCLC™ instance on a local network with all gateways being used for ShowRunnerCLC™.
2.1	178
	179	* Connect to the processor's console with Toolbox or your favorite SSH client.
38.2	180	* 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.
	181	* Type ##sr discover zummesh false## and press enter.
5.1	182	* Status messages and the results will be displayed on the console. The process should take about 3 minutes.
19.1	183	* 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.
	184	* Type ##progreset## and press enter to restart ShowRunnerCLC™
	185	* 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.
	186	* Once completed ShowRunnerCLC™ is now ready for full Zūm control
2.1	187
	188	== Examples ==
	189
5.2	190	=== Manual Example ===
4.1	191
	192	{{{MC4>sr devmgr ethernet query
	193	Ethrenet AutoDiscovery Result: AutoDiscoveryOperationSuccess
	194	MC4>sr devmgr ethernet show devices
	195
	196	+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
	197	\| Adapter \| Hostname \| IP Address \| IP-ID \| ID \|
	198	+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
	199	\| EthernetLANAdapter \| CI-SJC-CEN-CI3-1-COM3 \| 10.44.5.20 \| 00 \| CEN-CI3-1-C3COM-3 [v1.1620.00000, #008436E2] type:1 \|
	200	+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
	201	\| EthernetLANAdapter \| SB-DIN-CENCN-2 \| 10.44.5.81 \| 00 \| DIN-CENCN-2-POE [v1.3544.00006, #8AB25AA3] \|
	202	+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
	203	\| EthernetLANAdapter \| CEN-GWEXER-9E6ADA \| 10.44.5.120 \| 00 \| CEN-GWEXER [v1.4230.00015, #848210AD] \|
	204	+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
	205
	206	MC4>sr ethernet device claim CEN-GWEXER-9E6ADA
	207	Claimed ethernet device: CEN-GWEXER-9E6ADA
	208	MC4>Update request from IP-ID-30 in Program 01
9.1	209	MC4>sr discover zummesh false
4.1	210	Starting Zum Discovery without gateway claiming
	211	MC4>Performing Discovery on 1 Gateways.
2.1	212	Evaluating 3 Devices on Gateway 30
	213	Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30
	214	Dev: ZUM-NETBRIDGE addrssing to RF ID: 03
	215	Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 03
	216	Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30
	217	Dev: ZUM-NETBRIDGE addrssing to RF ID: 04
	218	Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 04
	219	Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30
	220	Dev: ZUM-NETBRIDGE addrssing to RF ID: 05
	221	Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 05
4.1	222	Querying cresnet
2.1	223	Discovering Zum Loads on 1 Gateways.
	224	Discovering Zum Loads on 3 Devices.
	225	NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
	226	Device: ZUM Netbridge 30:03 at 30:03 discovery result: .
	227	NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
	228	Device: ZUM Netbridge 30:04 at 30:04 discovery result: .
	229	NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
	230	Device: ZUM Netbridge 30:05 at 30:05 discovery result: .
	231	RF Gateways: 0
	232	RF Devices: 3
	233	New Loads: 0
	234	Modified Loads: 0
	235	Removed Loads: 0
	236	Zum Discovery Finished
	237	MC4>sr save
	238	Saved config
	239	MC4>progreset
	240	...
	241	CI ShowRunner startup completed successfully in 8072ms
9.1	242	MC4>sr discover zummesh false
2.1	243	Starting Zum Discovery without gateway claiming
	244	MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable)
	245	Performing Discovery on 1 Gateways.
	246	Evaluating 3 Devices on Gateway 30
	247	Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30
	248	Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 03
	249	Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30
	250	Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 04
	251	Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30
	252	Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 05
	253	Discovering Zum Loads on 1 Gateways.
	254	Discovering Zum Loads on 3 Devices.
	255	Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
	256	Evaluating Device: ZUM-JBOX-20A-PLUG ShortAddress: 0000 Type: PlugLoad
	257	Evaluating Device: ZUM-KP10C-BATT ShortAddress: 52E5 Type: Keypad
	258	Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: DAF1 Type: OccupancySensor
	259	Evaluating Device: ZUM-JBOX-5A-LV ShortAddress: 92EF Type: DimmableLoad
	260	Load: Load37615 Added
	261	NETBIRDGE: NewLoads: 1 ModifiedLoads: 0 RemovedLoads: 0
	262	Device: ZUM Netbridge 30:03 at 30:03 discovery result: .
	263	Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
	264	Evaluating Device: ZUM-DALI ShortAddress: 740D Type: Unknown
	265	Evaluating Device: ZUM-5A-LV ShortAddress: 0482 Type: DimmableLoad
	266	Load: Load1154 Added
	267	Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 0000 Type: DimmableLoad
	268	Load: Load0 Added
	269	Evaluating Device: ZUM-KP10C-BATT ShortAddress: D766 Type: Keypad
	270	Evaluating Device: ZUM-OL-PHO-BATT ShortAddress: 95ED Type: Photocell
	271	Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: 44C2 Type: OccupancySensor
	272	Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown
	273	Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown
	274	NETBIRDGE: NewLoads: 2 ModifiedLoads: 0 RemovedLoads: 0
	275	Device: ZUM Netbridge 30:04 at 30:04 discovery result: .
	276	Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
	277	Evaluating Device: ZUM-SIM ShortAddress: 0000 Type: OccupancySensor, PartitionSensor
	278	Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: EBCF Type: DimmableLoad
	279	Load: Load60367 Added
	280	Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 3CC1 Type: DimmableLoad
	281	Load: Load15553 Added
	282	Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: F94A Type: DimmableLoad
	283	Load: Load63818 Added
	284	NETBIRDGE: NewLoads: 3 ModifiedLoads: 0 RemovedLoads: 0
	285	Device: ZUM Netbridge 30:05 at 30:05 discovery result: .
	286	RF Gateways: 0
	287	RF Devices: 3
	288	New Loads: 6
	289	Modified Loads: 0
	290	Removed Loads: 0
4.1	291	Zum Discovery Finished}}}
2.1	292
5.1	293	=== Claim All Example ===
2.1	294
9.1	295	{{{MC4>sr discover zummesh true
4.1	296	Starting Zum Discovery with gateway claiming
	297	MC4>Found 1 Gateways to check.
	298	Claimed Gateway SN: 1720JBH04269 at IP-ID: 30
	299	Update request from IP-ID-30 in Program 01
	300	Claimed 1 Gateways. Waiting for queries to finish.
	301	Performing Discovery on 1 Gateways.
2.1	302	Evaluating 3 Devices on Gateway 30
	303	Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30
	304	Dev: ZUM-NETBRIDGE addrssing to RF ID: 03
	305	Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 03
	306	Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30
	307	Dev: ZUM-NETBRIDGE addrssing to RF ID: 04
	308	Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 04
	309	Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30
	310	Dev: ZUM-NETBRIDGE addrssing to RF ID: 05
	311	Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 05
	312	Discovering Zum Loads on 1 Gateways.
	313	Discovering Zum Loads on 3 Devices.
	314	NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
	315	Device: ZUM Netbridge 30:03 at 30:03 discovery result: .
	316	NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
	317	Device: ZUM Netbridge 30:04 at 30:04 discovery result: .
	318	NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
	319	Device: ZUM Netbridge 30:05 at 30:05 discovery result: .
	320	RF Gateways: 0
	321	RF Devices: 3
	322	New Loads: 0
	323	Modified Loads: 0
	324	Removed Loads: 0
	325	Zum Discovery Finished
	326	MC4>sr save
	327	Saved config
	328	MC4>progreset
	329	...
	330	CI ShowRunner startup completed successfully in 8072ms
9.1	331	MC4>sr discover zummesh false
2.1	332	Starting Zum Discovery without gateway claiming
	333	MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable)
	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: ZUMMESH-NETBRIDGE already claimed at RF ID: 03
	338	Claiming ZUM-NETBRIDGE SN: 1914NEJ03096 from IP-ID: 30
	339	Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 04
	340	Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30
	341	Dev: ZUMMESH-NETBRIDGE already claimed at RF ID: 05
	342	Discovering Zum Loads on 1 Gateways.
	343	Discovering Zum Loads on 3 Devices.
	344	Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
	345	Evaluating Device: ZUM-JBOX-20A-PLUG ShortAddress: 0000 Type: PlugLoad
	346	Evaluating Device: ZUM-KP10C-BATT ShortAddress: 52E5 Type: Keypad
	347	Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: DAF1 Type: OccupancySensor
	348	Evaluating Device: ZUM-JBOX-5A-LV ShortAddress: 92EF Type: DimmableLoad
	349	Load: Load37615 Added
	350	NETBIRDGE: NewLoads: 1 ModifiedLoads: 0 RemovedLoads: 0
	351	Device: ZUM Netbridge 30:03 at 30:03 discovery result: .
	352	Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
	353	Evaluating Device: ZUM-DALI ShortAddress: 740D Type: Unknown
	354	Evaluating Device: ZUM-5A-LV ShortAddress: 0482 Type: DimmableLoad
	355	Load: Load1154 Added
	356	Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 0000 Type: DimmableLoad
	357	Load: Load0 Added
	358	Evaluating Device: ZUM-KP10C-BATT ShortAddress: D766 Type: Keypad
	359	Evaluating Device: ZUM-OL-PHO-BATT ShortAddress: 95ED Type: Photocell
	360	Evaluating Device: ZUM-PIR-OCC-BATT ShortAddress: 44C2 Type: OccupancySensor
	361	Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown
	362	Evaluating Device: ZUM-DALI-GROUP ShortAddress: 740D Type: Unknown
	363	NETBIRDGE: NewLoads: 2 ModifiedLoads: 0 RemovedLoads: 0
	364	Device: ZUM Netbridge 30:04 at 30:04 discovery result: .
	365	Evaluating Device: ZUM-BLE ShortAddress: FFFA Type: BLERadio
	366	Evaluating Device: ZUM-SIM ShortAddress: 0000 Type: OccupancySensor, PartitionSensor
	367	Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: EBCF Type: DimmableLoad
	368	Load: Load60367 Added
	369	Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: 3CC1 Type: DimmableLoad
	370	Load: Load15553 Added
	371	Evaluating Device: ZUM-JBOX-16A-LV ShortAddress: F94A Type: DimmableLoad
	372	Load: Load63818 Added
	373	NETBIRDGE: NewLoads: 3 ModifiedLoads: 0 RemovedLoads: 0
	374	Device: ZUM Netbridge 30:05 at 30:05 discovery result: .
	375	RF Gateways: 0
	376	RF Devices: 3
	377	New Loads: 6
	378	Modified Loads: 0
	379	Removed Loads: 0
	380	Zum Discovery Finished
4.1	381	}}}