Changes for page Zūm Discovery

Last modified by Austin Weygandt on 2025/05/02 20:21

From version 21.1
edited by Alexander Mott
on 2023/10/11 16:37
Change comment: There is no comment for this version
To version 2.1
edited by Alexander Mott
on 2022/09/22 21:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Zūm Discovery
1 +Zūm Autodiscovery
Content
... ... @@ -1,18 +13,6 @@
1 -(% class="box errormessage" %)
2 -(((
3 -WARNING: Cresnet Discovery is not currently working on ZUMNET-JBOXs. Crestron has acknowledged a fix has been sent to QE.
4 -
5 -Downgrade ShowRunnerCLC™ to v3.018 in order to auto-discover hardware. ShowRunnerCLC™ can be subsequently upgraded once discovery is complete.
6 -)))
7 -
8 -(% class="box errormessage" %)
9 -(((
10 -**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.
11 -)))
12 -
13 13  (% class="box warningmessage" %)
14 14  (((
15 -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 Autodiscovery 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]].
16 16  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]].
17 17  )))
18 18  
... ... @@ -20,131 +20,71 @@
20 20  {{toc/}}
21 21  {{/box}}
22 22  
23 -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 +(% class="row" %)
12 +(((
13 +If Zūm Net devices have been configured using Crestron's Zūm App
24 24  
25 -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.
15 += m Wired =
26 26  
27 -= Zūm Wired Discovery =
17 +Lorem
28 28  
29 -== Notes and Limitations ==
19 += Zūm Wireless =
30 30  
31 -(% class="box warningmessage" %)
32 -(((
33 -* ShowRunnerCLC™ version 3.014 or newer required
34 -* Zūm Wired firmware .puf version 1.02.10 or greater required (ZUMNET-JBOX installed minimum version 1.001.00081)
35 -* Disconnect from any ZUMNET devices you may be connected to in Toolbox prior to running the discovery commands
36 -* Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release)
37 -* One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually
38 -)))
39 39  
40 -== Steps ==
22 +As of version 2.190 ShowRunner can discover RF Gateways and attached Zum NETBRIDGES. ShowRunner will find all devices, set them up, create areas and loads.
23 +*Disconnect from the gateway before discovery as they cannot support multiple connections*
24 +*Plug loads do not appear in the UI*
41 41  
42 -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
43 -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.
44 -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: 
45 -1*. Connect to the first ZUMNET-JBOX in Toolbox
46 -1*. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 
47 -1**. Note: The ShowRunnerCLC™ built-in DHCP server is not meant to be used in production
48 -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
49 -1*. Set unique Connection IDs for each device hosted on the ZUMNET-JBOX so that their firmware can be updated
50 -1*. Load the Zūm Wired firmware to the ZUMNET-JBOX
51 -1*. Repeat the above steps for all ZUMNET-JBOXs
52 -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
53 -1. Connect to first ZUMNET-JBOX in the Crestron Zūm App
54 -1. Unique Connection IDs should be automatically assigned to any Zūm Link and Cresnet devices on the ZUMNET-JBOX
55 -1*. If firmware was out-of-date, then this step should have already been completed
56 -1*. If unique CIDs are not automatically assigned, connect to the JBOX in Toolbox and give the devices unique CIDs
57 -1. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 
58 -1*. If firmware was out-of-date, then this step should have already been completed
59 -1*. Note: The ShowRunnerCLC™ built-in DHCP server is not meant to be used in production
60 -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
61 -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
62 -1*. If you do not manually configure the IP table, then SHOWRUNNER™ will automatically configure the IP-ID for each ZUMNET-JBOX during discovery
63 -1. Set the ZUMNET-JBOX into either Zūm ("App") mode or CNET mode as required for the program
64 -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
65 -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
66 -1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox
67 -1. Run the command: ##sr discover zumnet true false##
68 -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
69 -1. Run the command: ##sr discover zumnet true true##
70 -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
71 -1**. One area will be created per ZUMNET-JBOX, and all hardware attached to that ZUMNET-JBOX will be assigned to that area
72 -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
73 -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.
26 +== **Pre-Requisites:** ==
74 74  
75 -= Zūm Wireless Discovery =
28 +* Zum NETBRIDGES acquired to their respective gateway (CEN-GWEXER/ZUMNET-GATEWAY)
29 +* ShowRunner installed and running on a 3-series processor on the same network as the gateway
30 +* NETBRIDGES do not need to have addresses assigned. ShowRunner will automatically address them. If devices all already addressed then their addresses will be honored.
76 76  
77 -== Notes and Limitations ==
32 +=== **Caution:** ===
78 78  
79 -(% class="box warningmessage" %)
80 -(((
81 -* Processor with ShowRunnerCLC™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired
82 -** For ShowRunnerCLC™ versions prior to 3.014 and newer, replace **##sr discover zummesh##** commands with **##sr discover zum##**
83 -* ZUM-NETBRIDGES must already be acquired to their respective gateway
84 -* ShowRunnerCLC™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices
85 -* Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command
86 -* Plug loads will not appear in the ShowRunnerCLC™ UI
87 -)))
34 +* ShowRunner has 2 discovery approaches.
35 +** Option 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.
36 +** Option 2: 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.
88 88  
89 -(% class="box infomessage" id="HCaution:" %)
90 -(((
91 -**Note:** ShowRunnerCLC™ has two different approaches for Zūm Wireless Discovery
38 +== Option 1: Claim All Gateways: ==
92 92  
93 -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.
94 -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.
95 -)))
40 +Use this method when you have a single ShowRunner instance on a local network with all gateways being used for ShowRunner.
96 96  
97 -== Manual RF Gateway Assignment Instructions ==
98 -
99 -Use this method if you have multiple ShowRunnerCLC™ instances on the same network or have gateways used by other Crestron systems.
100 -
101 101  * Connect to the processor's console with Toolbox or your favorite SSH client.
102 -* Type ##sr devmgr ethernet query## and press enter. This queries the local network for RF Gateways.
103 -* Type ##sr devmgr ethernet show devices## and press enter. This displays all found Crestron ethernet devices.
104 -* 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.
105 -* Type ##sr discover zummesh false## and press enter.
106 -* Status messages and the results will be displayed on the console. The process should take about 3 minutes.
107 -* 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.
108 -* Type ##progreset## and press enter to restart ShowRunnerCLC™
109 -* 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.
110 -* Once completed SHOWRUNNER™ is now ready for full Zūm control
43 +* Type "//sr discover zum true//" and press enter.
44 +* Status messages and the results will be displayed on the console. The process should take about 3 minutes.
45 +* 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.
46 +* Type "//progreset//" and press enter to restart ShowRunner
47 +* Once ShowRunner has finished restarting type "//sr discover zum false//" and press enter. ShowRunner will be able to acquire the loads attached to the Zum rooms at this point.
48 +* Once completed ShowRunner is now ready for full Zum control
111 111  
112 -== Claim All RF Gateways Instructions ==
50 +== Option 2: Manual RF Gateway Claiming: ==
113 113  
114 -Use this method when you have a single ShowRunnerCLC™ instance on a local network with all gateways being used for ShowRunnerCLC™.
52 +Use this method if you have multiple ShowRunner instances on the same network or have gateways used by other Crestron systems.
115 115  
116 116  * Connect to the processor's console with Toolbox or your favorite SSH client.
117 -* Type ##sr discover zummesh true## and press enter.
118 -* Status messages and the results will be displayed on the console. The process should take about 3 minutes.
119 -* 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.
120 -* Type ##progreset## and press enter to restart ShowRunnerCLC™
121 -* 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.
122 -* Once completed ShowRunnerCLC™ is now ready for full Zūm control
55 +* Type "//sr devmgr ethernet query//" and press enter. This queries the local network for RF Gateways.
56 +* Type "//sr devmgr ethernet show devices//" and press enter. This displays all found Crestron ethernet devices.
57 +* 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.
58 +* Type "//sr discover zum false//" and press enter.
59 +* Status messages and the results will be displayed on the console. The process should take about 3 minutes.
60 +* 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.
61 +* Type "//progreset//" and press enter to restart ShowRunner
62 +* Once ShowRunner has finished restarting type "//sr discover zum false//" and press enter. ShowRunner will be able to acquire the loads attached to the Zum rooms at this point.
63 +* Once completed ShowRunner is now ready for full Zum control
123 123  
124 124  == Examples ==
125 125  
126 -=== Manual Example ===
67 +=== Example for Option 1: ===
127 127  
128 -{{{MC4>sr devmgr ethernet query
129 -Ethrenet AutoDiscovery Result: AutoDiscoveryOperationSuccess
130 -MC4>sr devmgr ethernet show devices
131 -
132 -+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
133 -| Adapter | Hostname | IP Address | IP-ID | ID |
134 -+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
135 -| EthernetLANAdapter | CI-SJC-CEN-CI3-1-COM3 | 10.44.5.20 | 00 | CEN-CI3-1-C3COM-3 [v1.1620.00000, #008436E2] type:1 |
136 -+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
137 -| EthernetLANAdapter | SB-DIN-CENCN-2 | 10.44.5.81 | 00 | DIN-CENCN-2-POE [v1.3544.00006, #8AB25AA3] |
138 -+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
139 -| EthernetLANAdapter | CEN-GWEXER-9E6ADA | 10.44.5.120 | 00 | CEN-GWEXER [v1.4230.00015, #848210AD] |
140 -+--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
141 -
142 -MC4>sr ethernet device claim CEN-GWEXER-9E6ADA
143 -Claimed ethernet device: CEN-GWEXER-9E6ADA
144 -MC4>Update request from IP-ID-30 in Program 01
145 -MC4>sr discover zummesh false
146 -Starting Zum Discovery without gateway claiming
147 -MC4>Performing Discovery on 1 Gateways.
69 +{{{MC4>sr discover zum true
70 +Starting Zum Discovery with gateway claiming
71 +MC4>Found 1 Gateways to check.
72 +Claimed Gateway SN: 1720JBH04269 at IP-ID: 30
73 +Update request from IP-ID-30 in Program 01
74 +Claimed 1 Gateways. Waiting for queries to finish.
75 +Performing Discovery on 1 Gateways.
148 148  Evaluating 3 Devices on Gateway 30
149 149  Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30
150 150  Dev: ZUM-NETBRIDGE addrssing to RF ID: 03
... ... @@ -155,7 +155,6 @@
155 155  Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30
156 156  Dev: ZUM-NETBRIDGE addrssing to RF ID: 05
157 157  Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 05
158 -Querying cresnet
159 159  Discovering Zum Loads on 1 Gateways.
160 160  Discovering Zum Loads on 3 Devices.
161 161  NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
... ... @@ -175,7 +175,7 @@
175 175  MC4>progreset
176 176  ...
177 177  CI ShowRunner startup completed successfully in 8072ms
178 -MC4>sr discover zummesh false
105 +MC4>sr discover zum false
179 179  Starting Zum Discovery without gateway claiming
180 180  MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable)
181 181  Performing Discovery on 1 Gateways.
... ... @@ -224,17 +224,31 @@
224 224  New Loads: 6
225 225  Modified Loads: 0
226 226  Removed Loads: 0
227 -Zum Discovery Finished}}}
154 +Zum Discovery Finished
155 +}}}
228 228  
229 -=== Claim All Example ===
157 +=== Example for Option 2: ===
230 230  
231 -{{{MC4>sr discover zummesh true
232 -Starting Zum Discovery with gateway claiming
233 -MC4>Found 1 Gateways to check.
234 -Claimed Gateway SN: 1720JBH04269 at IP-ID: 30
235 -Update request from IP-ID-30 in Program 01
236 -Claimed 1 Gateways. Waiting for queries to finish.
237 -Performing Discovery on 1 Gateways.
159 +{{{MC4>sr devmgr ethernet query
160 +Ethrenet AutoDiscovery Result: AutoDiscoveryOperationSuccess
161 +MC4>sr devmgr ethernet show devices
162 +
163 ++--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
164 +| Adapter | Hostname | IP Address | IP-ID | ID |
165 ++--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
166 +| EthernetLANAdapter | CI-SJC-CEN-CI3-1-COM3 | 10.44.5.20 | 00 | CEN-CI3-1-C3COM-3 [v1.1620.00000, #008436E2] type:1 |
167 ++--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
168 +| EthernetLANAdapter | SB-DIN-CENCN-2 | 10.44.5.81 | 00 | DIN-CENCN-2-POE [v1.3544.00006, #8AB25AA3] |
169 ++--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
170 +| EthernetLANAdapter | CEN-GWEXER-9E6ADA | 10.44.5.120 | 00 | CEN-GWEXER [v1.4230.00015, #848210AD] |
171 ++--------------------+-------------------------------+-------------+-------+----------------------------------------------------------------------------------+
172 +
173 +MC4>sr ethernet device claim CEN-GWEXER-9E6ADA
174 +Claimed ethernet device: CEN-GWEXER-9E6ADA
175 +MC4>Update request from IP-ID-30 in Program 01
176 +MC4>sr discover zum false
177 +Starting Zum Discovery without gateway claiming
178 +MC4>Performing Discovery on 1 Gateways.
238 238  Evaluating 3 Devices on Gateway 30
239 239  Claiming ZUM-NETBRIDGE SN: 1726NEJ01096 from IP-ID: 30
240 240  Dev: ZUM-NETBRIDGE addrssing to RF ID: 03
... ... @@ -245,6 +245,7 @@
245 245  Claiming ZUM-NETBRIDGE SN: 1914NEJ03098 from IP-ID: 30
246 246  Dev: ZUM-NETBRIDGE addrssing to RF ID: 05
247 247  Setting up RF Device 'ZUM-NETBRIDGE' on Gateway 30 at RF-ID 05
189 +Querying cresnet
248 248  Discovering Zum Loads on 1 Gateways.
249 249  Discovering Zum Loads on 3 Devices.
250 250  NETBIRDGE: NewLoads: 0 ModifiedLoads: 0 RemovedLoads: 0
... ... @@ -264,7 +264,7 @@
264 264  MC4>progreset
265 265  ...
266 266  CI ShowRunner startup completed successfully in 8072ms
267 -MC4>sr discover zummesh false
209 +MC4>sr discover zum false
268 268  Starting Zum Discovery without gateway claiming
269 269  MC4>Notice: SimplSharpPro[App01] # 2020-07-21 22:19:46 # Recalling startup scenes (if applicable)
270 270  Performing Discovery on 1 Gateways.
... ... @@ -314,4 +314,5 @@
314 314  Modified Loads: 0
315 315  Removed Loads: 0
316 316  Zum Discovery Finished
317 -}}}
259 + }}}
260 +)))