Changes for page Zūm Discovery

Last modified by Alexander Mott on 2025/04/03 17:35

From version 22.1
edited by Alexander Mott
on 2023/12/08 18:34
Change comment: There is no comment for this version
To version 11.1
edited by Alexander Mott
on 2022/10/05 16:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,17 +12,6 @@
1 -(% class="box errormessage" %)
2 -(((
3 -**WARNING:** Cresnet Discovery is non-functional for ZUMNET-JBOXs with certain versions of Crestron Device Database.
4 -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.
5 -)))
6 -
7 -(% class="box errormessage" %)
8 -(((
9 -**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.
10 -)))
11 -
12 12  (% class="box warningmessage" %)
13 13  (((
14 -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.Wiring Guide.Zūm Wired System Overview.Crestron Zūm App Overview.WebHome]].
3 +This article is about automatically building a SHOWRUNNER™ configuration using the Zūm Discovery feature of SHOWRUNNER™. For instructions on configuring Zūm Wired rooms using the Crestron Zūm App, see [[this page>>SHOWRUNNER™ Setup Guide.Wiring Guide.Zūm Wired System Overview.Crestron Zūm App Overview.WebHome]].
15 15  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]].
16 16  )))
17 17  
... ... @@ -19,18 +19,18 @@
19 19  {{toc/}}
20 20  {{/box}}
21 21  
22 -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™.
11 +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™.
23 23  
24 -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.
13 +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.
25 25  
26 26  = Zūm Wired Discovery =
27 27  
28 28  == Notes and Limitations ==
29 29  
30 -(% class="box warningmessage" %)
19 +(% class="box errormessage" %)
31 31  (((
32 -* ShowRunnerCLC™ version 3.014 or newer required
33 -* Zūm Wired firmware .puf version 1.02.10 or greater required (ZUMNET-JBOX installed minimum version 1.001.00081)
21 +* SHOWRUNNER™ version 3.014 or newer required
22 +* Zūm Wired firmware version 1.02.10 or greater required
34 34  * Disconnect from any ZUMNET devices you may be connected to in Toolbox prior to running the discovery commands
35 35  * Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release)
36 36  * One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually
... ... @@ -38,13 +38,13 @@
38 38  
39 39  == Steps ==
40 40  
41 -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. [[Install SHOWRUNNER™>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.WebHome]] on the processor and configure the processor as necessary
42 42  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.
43 43  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: 
44 44  1*. Connect to the first ZUMNET-JBOX in Toolbox
45 45  1*. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 
46 -1**. Note: The ShowRunnerCLC™ built-in DHCP server is not meant to be used in production
47 -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
35 +1**. Note: The SHOWRUNNER™ built-in DHCP server is not meant to be used in production
36 +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 48  1*. Set unique Connection IDs for each device hosted on the ZUMNET-JBOX so that their firmware can be updated
49 49  1*. Load the Zūm Wired firmware to the ZUMNET-JBOX
50 50  1*. Repeat the above steps for all ZUMNET-JBOXs
... ... @@ -55,70 +55,69 @@
55 55  1*. If unique CIDs are not automatically assigned, connect to the JBOX in Toolbox and give the devices unique CIDs
56 56  1. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 
57 57  1*. If firmware was out-of-date, then this step should have already been completed
58 -1*. Note: The ShowRunnerCLC™ built-in DHCP server is not meant to be used in production
59 -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
47 +1*. Note: The SHOWRUNNER™ built-in DHCP server is not meant to be used in production
48 +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
60 60  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
61 61  1*. If you do not manually configure the IP table, then SHOWRUNNER™ will automatically configure the IP-ID for each ZUMNET-JBOX during discovery
62 -1. Set the ZUMNET-JBOX into either Zūm ("App") mode or CNET mode as required for the program
63 -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
64 -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
51 +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
65 65  1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox
66 66  1. Run the command: ##sr discover zumnet true false##
67 -1*. This command tells ShowRunnerCLC™ to discover all ZUMMNET-JBOXs on the network, configure their IP tables, and then add corresponding IP Devices to the configuration
54 +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
55 +1*. One area will be created per ZUMNET-JBOX
68 68  1. Run the command: ##sr discover zumnet true true##
69 -1*. This command tells ShowRunnerCLC™ to 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
70 -1**. One area will be created per ZUMNET-JBOX, and all hardware attached to that ZUMNET-JBOX will be assigned to that area
57 +1*. This command tells SHOWRUNNER™ to discover all Zūm Link hardware on the previously discovered Zūm Net devices
71 71  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
72 -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.
59 +1. Put all ZUMNET-JBOXs into CNET mode in order to allow full control from SHOWRUNNER™
60 +1*. Odd behavior may result from conflicts between SHOWRUNNER™ and internal logic if the ZUMNET-JBOXs are not put into CNET mode
73 73  
74 74  = Zūm Wireless Discovery =
75 75  
76 76  == Notes and Limitations ==
77 77  
78 -(% class="box warningmessage" %)
66 +(% class="box errormessage" %)
79 79  (((
80 -* Processor with ShowRunnerCLC™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired
81 -** For ShowRunnerCLC™ versions prior to 3.014 and newer, replace **##sr discover zummesh##** commands with **##sr discover zum##**
68 +* Processor with SHOWRUNNER™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired
69 +** For SHOWRUNNER™ versions prior to 3.014 and newer, replace **##sr discover zummesh##** commands with **##sr discover zum##**
82 82  * ZUM-NETBRIDGES must already be acquired to their respective gateway
83 -* ShowRunnerCLC™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices
71 +* SHOWRUNNER™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices
84 84  * Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command
85 -* Plug loads will not appear in the ShowRunnerCLC™ UI
73 +* Plug loads will not appear in the SHOWRUNNER™ UI
86 86  )))
87 87  
88 -(% class="box infomessage" id="HCaution:" %)
76 +(% class="box warningmessage" id="HCaution:" %)
89 89  (((
90 -**Note:** ShowRunnerCLC™ has two different approaches for Zūm Wireless Discovery
78 +**Note:** SHOWRUNNER™ has two different approaches for Zūm Wireless Discovery
91 91  
92 -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.
93 -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.
80 +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.
81 +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.
94 94  )))
95 95  
96 96  == Manual RF Gateway Assignment Instructions ==
97 97  
98 -Use this method if you have multiple ShowRunnerCLC™ instances on the same network or have gateways used by other Crestron systems.
86 +Use this method if you have multiple SHOWRUNNER™ instances on the same network or have gateways used by other Crestron systems.
99 99  
100 100  * Connect to the processor's console with Toolbox or your favorite SSH client.
101 101  * Type ##sr devmgr ethernet query## and press enter. This queries the local network for RF Gateways.
102 102  * Type ##sr devmgr ethernet show devices## and press enter. This displays all found Crestron ethernet devices.
103 -* 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.
91 +* 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##. SHOWRUNNER™ will auto-assign an IP-ID. After all gateways have been claimed by SHOWRUNNER™, proceed to the next step.
104 104  * Type ##sr discover zummesh false## and press enter.
105 105  * Status messages and the results will be displayed on the console. The process should take about 3 minutes.
106 -* 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.
107 -* Type ##progreset## and press enter to restart ShowRunnerCLC
108 -* 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.
94 +* 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, SHOWRUNNER™ must be restarted to complete the acquire process.
95 +* Type ##progreset## and press enter to restart SHOWRUNNER
96 +* Once SHOWRUNNER™ has finished restarting type ##sr discover zummesh false## and press enter. SHOWRUNNER™ will be able to acquire the loads attached to the Zūm rooms at this point.
109 109  * Once completed SHOWRUNNER™ is now ready for full Zūm control
110 110  
111 111  == Claim All RF Gateways Instructions ==
112 112  
113 -Use this method when you have a single ShowRunnerCLC™ instance on a local network with all gateways being used for ShowRunnerCLC™.
101 +Use this method when you have a single SHOWRUNNER™ instance on a local network with all gateways being used for SHOWRUNNER™.
114 114  
115 115  * Connect to the processor's console with Toolbox or your favorite SSH client.
116 116  * Type ##sr discover zummesh true## and press enter.
117 117  * Status messages and the results will be displayed on the console. The process should take about 3 minutes.
118 -* 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.
119 -* Type ##progreset## and press enter to restart ShowRunnerCLC
120 -* 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.
121 -* Once completed ShowRunnerCLC™ is now ready for full Zūm control
106 +* 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, SHOWRUNNER™ must be restarted to complete the acquire process.
107 +* Type ##progreset## and press enter to restart SHOWRUNNER
108 +* Once SHOWRUNNER™ has finished restarting type ##sr discover zummesh false## and press enter. SHOWRUNNER™ will be able to acquire the loads attached to the Zūm rooms at this point.
109 +* Once completed SHOWRUNNER™ is now ready for full Zūm control
122 122  
123 123  == Examples ==
124 124