Changes for page Zūm Discovery

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -10,34 +10,68 @@
10	10
11	11	(% class="row" %)
12	12	(((
13		-If Zūm Wired or Wireless devices have been configured using Crestron's Zūm App, then it is possible to automatically build a SHOWRUNNER™ configuration file using the Autodiscovery feature that is built into SHOWRUNNER™.
	13	+If Zūm Wired or Wireless devices have been configured using Crestron's Zūm App, then it is possible to automatically build a SHOWRUNNER™ configuration file using the Zūm Discovery feature that is built into SHOWRUNNER™.
14	14
15	15	There are certain pre-requisites and limitations when building a SHOWRUNNER™ 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.
16	16
17	17	= Zūm Wired Discovery =
18	18
19		-Lorem
	19	+== Notes and Limitations ==
20	20
21		-= Zūm Wireless Discovery =
	21	+* SHOWRUNNER™ version 3.014 or newer required
	22	+* Zūm Wired firmware version 1.02.10 or greater required
	23	+* Disconnect from any ZUMNET devices you may be connected to in Toolbox prior to running the discovery commands
	24	+* Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release)
	25	+* One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually
22	22
23		-*Disconnect from the gateway before discovery as they cannot support multiple connections*
24		-*Plug loads do not appear in the UI*
	27	+== Steps ==
25	25
26		-== Notes and Limitations ==
	29	+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
	30	+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.
	31	+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:
	32	+1*. Connect to the first ZUMNET-JBOX in Toolbox
	33	+1*. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network
	34	+1**. Note: The SHOWRUNNER™ built-in DHCP server is not meant to be used in production
	35	+1**. If the SHOWRUNNER™ built-in DHCP server was used to assign IP addresses to devices, it is still necessary to give those devices static IP addresses
	36	+1*. Set unique Connection IDs for each device hosted on the ZUMNET-JBOX so that their firmware can be updated
	37	+1*. Load the Zūm Wired firmware to the ZUMNET-JBOX
	38	+1*. Repeat the above steps for all ZUMNET-JBOXs
	39	+1*. Once all the ZUMNET-JBOXs have pushed the new firmware to their hosted devices, proceed to the next step
	40	+1. Connect to first ZUMNET-JBOX in the Crestron Zūm App
	41	+1. Unique Connection IDs should be automatically assigned to any Zūm Link and Cresnet devices on the ZUMNET-JBOX
	42	+1*. If firmware was out-of-date, then this step should have already been completed
	43	+1*. If unique CIDs are not automatically assigned, connect to the JBOX in Toolbox and give the devices unique CIDs
	44	+1. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network
	45	+1*. If firmware was out-of-date, then this step should have already been completed
	46	+1*. Note: The SHOWRUNNER™ built-in DHCP server is not meant to be used in production
	47	+1*. If the SHOWRUNNER™ built-in DHCP server was used to assign IP addresses to devices, it is still necessary to give those devices static IP addresses
	48	+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
	49	+1*. If you do not manually configure the IP table, then SHOWRUNNER™ will automatically configure the IP-ID for each ZUMNET-JBOX during discovery
	50	+1. Repeat from step 3 until all ZUMNET-JBOXs that are to be controlled by SHOWRUNNER™ have static IP addresses and unique CIDs for any hosted devices
	51	+1. Connect to the processor in Toolbox and run the command: ##sr discover zumnet true false##
	52	+1*. This command tells SHOWRUNNER™ to discover all ZUMMNET-JBOXs on the network, configure their IP tables, and then add corresponding areas and loads to the configuration
	53	+1*. One area will be created per ZUMNET-JBOX
	54	+1. Run the command: ##sr discover zumnet true true##
	55	+1*. This command tells SHOWRUNNER™ to discover all Zūm Link hardware on the previously discovered Zūm Net devices
	56	+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
	57	+1. Put all ZUMNET-JBOXs into CNET mode in order to allow full control from SHOWRUNNER™
	58	+1*. Odd behavior may result from conflicts between SHOWRUNNER™ and internal logic if the ZUMNET-JBOXs are not put into CNET mode
27	27
28		-* SHOWRUNNER™ version 2.190 or newer required
29		-* Disconnect from any RF gateways you are connected to prior to running the autodiscovery command,
	60	+= Zūm Wireless Discovery =
30	30
31		-== Pre-Requisites ==
	62	+== Notes and Limitations ==
32	32
33		-* Zum NETBRIDGES acquired to their respective gateway (CEN-GWEXER/ZUMNET-GATEWAY)
34		-* SHOWRUNNER™ installed and running on a 3-series processor on the same network as the gateway
35		-* NETBRIDGES do not need to have addresses assigned. SHOWRUNNER™ will automatically address them. If devices all already addressed then their addresses will be honored.
	64	+* Processor with SHOWRUNNER™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired
	65	+** For SHOWRUNNER™ versions 3.014 and newer, replace ##sr discover zum## commands with ##sr discover zummesh##
	66	+* ZUM-NETBRIDGES must already be acquired to their respective gateway
	67	+* SHOWRUNNER™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices
	68	+* Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command
	69	+* Plug loads will not appear in the SHOWRUNNER™ UI
36	36	)))
37	37
38	38	(% class="box warningmessage" id="HCaution:" %)
39	39	(((
40		-**Note:** SHOWRUNNER™ has two different approaches for Zūm Wireless Autodiscovery
	74	+**Note:** SHOWRUNNER™ has two different approaches for Zūm Wireless Discovery
41	41
42	42	1. **Manual RF Gateway Assignment** - SHOWRUNNER™ 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.
43	43	1. **Claim All RF Gateways** - SHOWRUNNER™ 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 SHOWRUNNER™ or other Crestron systems on the same local network.
...	...	@@ -45,7 +45,7 @@
45	45
46	46	(% class="row" %)
47	47	(((
48		-== Manual RF Gateway Assignment ==
	82	+== Manual RF Gateway Assignment Instructions ==
49	49
50	50	Use this method if you have multiple SHOWRUNNER™ instances on the same network or have gateways used by other Crestron systems.
51	51
...	...	@@ -60,7 +60,7 @@
60	60	* Once SHOWRUNNER™ has finished restarting type "//sr discover zum false//" and press enter. SHOWRUNNER™ will be able to acquire the loads attached to the Zūm rooms at this point.
61	61	* Once completed SHOWRUNNER™ is now ready for full Zūm control
62	62
63		-== Claim All RF Gateways ==
	97	+== Claim All RF Gateways Instructions ==
64	64
65	65	Use this method when you have a single SHOWRUNNER™ instance on a local network with all gateways being used for SHOWRUNNER™.
66	66