Skip to Content

Changes for page Zūm Discovery

Last modified by Alexander Mott on 2025/04/03 17:35
From version 6.7
edited by Alexander Mott
on 2022/09/22 23:57
Change comment: (Autosaved)
To version 7.1
edited by Alexander Mott
on 2022/09/22 23:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -26,7 +26,36 @@
26 26  
27 27  == Steps ==
28 28  
29 -1.
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
30 30  
31 31  = Zūm Wireless Discovery =
32 32