Wiki source code of Zūm Discovery

Version 35.1 by Alexander Mott on 2024/10/16 18:04

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