Skip to Content

Changes for page Zūm Discovery

Last modified by Craig Lewis on 2025/09/25 20:36
From version 43.1
edited by Craig Lewis
on 2025/09/25 20:36
Change comment: There is no comment for this version
To version 39.1
edited by Alexander Mott
on 2025/04/03 16:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.craig\.lewis@chiefintegrations\.com
1 +XWiki.alexander\.mott@chiefintegrations\.com
Content
... ... @@ -1,6 +1,6 @@
1 1  (% class="box errormessage" %)
2 2  (((
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.
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 4  
5 5  **WARNING:** Cresnet Discovery is non-functional for ZUMNET-JBOXs with certain versions of Crestron Device Database.
6 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.
... ... @@ -85,7 +85,6 @@
85 85  * ZUMLINK-IOs will not be discovered (Expected to be discoverable in future ShowRunnerCLC™ release)
86 86  * ZUMLINK-KPs will not be discovered on older versions of ShowRunnerCLC™ (v3.058 or newer will discover keypads and set as remote type)
87 87  * One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually
88 -* ZUMNET-JBOX-DALI will be created with only 1 broadcast load index 17. If ZUMNET is being setup as a LEGACY controller, the config will need to be updated to reflect the model as ZUMNET-JBOX-DALI-LEGACY.
89 89  )))
90 90  
91 91  == Steps ==
... ... @@ -141,7 +141,6 @@
141 141  
142 142  (% class="box warningmessage" %)
143 143  (((
144 -* **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**
145 145  * Processor with ShowRunnerCLC™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired
146 146  ** For ShowRunnerCLC™ versions prior to 3.014 and newer, replace **##sr discover zummesh##** commands with **##sr discover zum##**
147 147  * ZUM-NETBRIDGES must already be acquired to their respective gateway
... ... @@ -148,6 +148,7 @@
148 148  * ShowRunnerCLC™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices
149 149  * Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command
150 150  * Plug loads will not appear in the ShowRunnerCLC™ UI
149 +* 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
151 151  )))
152 152  
153 153  (% class="box infomessage" id="HCaution:" %)
... ... @@ -158,38 +158,6 @@
158 158  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.
159 159  )))
160 160  
161 -(% class="box errormessage" id="HCaution:" %)
162 -(((
163 -**Note:** Due to what is believed to be an SSL issue, ShowRunnerCLC™ will sometimes fail to acquire Zūm Wireless gateways with the ##sr discover zummesh true## or ##sr ethernet device claim [Hostname]## commands.
164 -
165 -To work around this issue, Zūm Wireless gateways need to be added to the "IpDevices" section of the SrConfig.json and then have their IP Tables manually updated using the ##addm [IP-ID] [Processor IP]## command. Once this has been done, the ##sr discover zummesh false## commands can be run as normal.
166 -
167 -Below is an example "IpDevices" section of a config with three gateways defined. Serial numbers are optional and can be deleted if not known. **Note:**  the "IpId" here is decimal, whereas the actual IP-ID that is assigned from Text Console is in hexadecimal. You will need to convert between the two: e.g. decimal "48" corresponds to hexadecimal "30", decimal "74" would correspond to hexadecimal "4A", etc.
168 -
169 -{{{ "Eiscs": [],
170 - "IpDevices": [
171 - {
172 - "Model": "CEN-GWEXER",
173 - "Name": "GW-1-1",
174 - "SerialNumber": "2402NEJ03956",
175 - "IpId": 48
176 - },
177 - {
178 - "Model": "CEN-GWEXER",
179 - "Name": "GW-1-2",
180 - "SerialNumber": "2402NEJ03862",
181 - "IpId": 49
182 - },
183 - {
184 - "Model": "CEN-GWEXER",
185 - "Name": "GW-2-1",
186 - "SerialNumber": "2402NEJ03887",
187 - "IpId": 50
188 - }
189 - ],
190 - "Keyswitches": [],}}}
191 -)))
192 -
193 193  == Manual RF Gateway Assignment Instructions ==
194 194  
195 195  Use this method if you have multiple ShowRunnerCLC™ instances on the same network or have gateways used by other Crestron systems.