Changes for page Zūm Discovery
Last modified by Alexander Mott on 2025/04/03 17:35
From version 20.1
edited by Alexander Mott
on 2023/10/11 16:36
on 2023/10/11 16:36
Change comment:
There is no comment for this version
To version 9.1
edited by Alexander Mott
on 2022/10/05 16:17
on 2022/10/05 16:17
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- 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 S howRunnerCLC™ 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]]. 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,18 +20,20 @@ 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 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™. 24 24 25 -There are certain pre-requisites and limitations when building a S howRunnerCLC™ 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 +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. 26 26 27 27 = Zūm Wired Discovery = 28 28 29 29 == Notes and Limitations == 30 30 31 -(% class="box warningmessage" %)21 +(% class="box errormessage" %) 32 32 ((( 33 -* S howRunnerCLC™ version 3.014 or newer required34 -* Zūm Wired firmware .pufversion 1.02.10 or greater required(ZUMNET-JBOX installed minimum version 1.001.00081)23 +* SHOWRUNNER™ version 3.014 or newer required 24 +* Zūm Wired firmware version 1.02.10 or greater required 35 35 * Disconnect from any ZUMNET devices you may be connected to in Toolbox prior to running the discovery commands 36 36 * Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release) 37 37 * One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually ... ... @@ -39,13 +39,13 @@ 39 39 40 40 == Steps == 41 41 42 -1. [[Install S howRunner™>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.WebHome]] on the processor and configure the processor as necessary32 +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 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 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 45 1*. Connect to the first ZUMNET-JBOX in Toolbox 46 46 1*. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 47 -1**. Note: The S howRunnerCLC™ built-in DHCP server is not meant to be used in production48 -1**. If the S howRunnerCLC™ built-in DHCP server was used to assign IP addresses to devices, it is still necessary to give those devices static IP addresses37 +1**. Note: The SHOWRUNNER™ built-in DHCP server is not meant to be used in production 38 +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 49 49 1*. Set unique Connection IDs for each device hosted on the ZUMNET-JBOX so that their firmware can be updated 50 50 1*. Load the Zūm Wired firmware to the ZUMNET-JBOX 51 51 1*. Repeat the above steps for all ZUMNET-JBOXs ... ... @@ -56,70 +56,72 @@ 56 56 1*. If unique CIDs are not automatically assigned, connect to the JBOX in Toolbox and give the devices unique CIDs 57 57 1. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 58 58 1*. If firmware was out-of-date, then this step should have already been completed 59 -1*. Note: The S howRunnerCLC™ built-in DHCP server is not meant to be used in production60 -1*. If the S howRunnerCLC™ built-in DHCP server was used to assign IP addresses to devices, it is still necessary to give those devices static IP addresses49 +1*. Note: The SHOWRUNNER™ built-in DHCP server is not meant to be used in production 50 +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 61 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 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 53 +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 66 66 1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox 67 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 56 +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 57 +1*. One area will be created per ZUMNET-JBOX 69 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 59 +1*. This command tells SHOWRUNNER™ to discover all Zūm Link hardware on the previously discovered Zūm Net devices 72 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. 61 +1. Put all ZUMNET-JBOXs into CNET mode in order to allow full control from SHOWRUNNER™ 62 +1*. Odd behavior may result from conflicts between SHOWRUNNER™ and internal logic if the ZUMNET-JBOXs are not put into CNET mode 74 74 75 75 = Zūm Wireless Discovery = 76 76 77 77 == Notes and Limitations == 67 +))) 78 78 79 -(% class="box warningmessage" %)69 +(% class="box errormessage" %) 80 80 ((( 81 -* Processor with S howRunnerCLC™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired82 -** For S howRunnerCLC™ versions prior to 3.014 and newer, replace **##sr discover zummesh##** commands with **##sr discover zum##**71 +* Processor with SHOWRUNNER™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired 72 +** For SHOWRUNNER™ versions prior to 3.014 and newer, replace **##sr discover zummesh##** commands with **##sr discover zum##** 83 83 * ZUM-NETBRIDGES must already be acquired to their respective gateway 84 -* S howRunnerCLC™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices74 +* SHOWRUNNER™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices 85 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 S howRunnerCLC™ UI76 +* Plug loads will not appear in the SHOWRUNNER™ UI 87 87 ))) 88 88 89 -(% class="box in fomessage" id="HCaution:" %)79 +(% class="box warningmessage" id="HCaution:" %) 90 90 ((( 91 -**Note:** S howRunnerCLC™ has two different approaches for Zūm Wireless Discovery81 +**Note:** SHOWRUNNER™ has two different approaches for Zūm Wireless Discovery 92 92 93 -1. **Manual RF Gateway Assignment** - S howRunnerCLC™ 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** - S howRunnerCLC™ 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.83 +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. 84 +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. 95 95 ))) 96 96 87 +(% class="row" %) 88 +((( 97 97 == Manual RF Gateway Assignment Instructions == 98 98 99 -Use this method if you have multiple S howRunnerCLC™ instances on the same network or have gateways used by other Crestron systems.91 +Use this method if you have multiple SHOWRUNNER™ instances on the same network or have gateways used by other Crestron systems. 100 100 101 101 * Connect to the processor's console with Toolbox or your favorite SSH client. 102 102 * Type ##sr devmgr ethernet query## and press enter. This queries the local network for RF Gateways. 103 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##. S howRunnerCLC™ will auto-assign an IP-ID. After all gateways have been claimed by ShowRunnerCLC™, proceed to the next step.96 +* 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. 105 105 * Type ##sr discover zummesh false## and press enter. 106 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, S howRunnerCLC™ must be restarted to complete the acquire process.108 -* Type ##progreset## and press enter to restart S howRunnerCLC™109 -* Once SHOWRUNNER™ has finished restarting type ##sr discover zummesh false## and press enter. S howRunnerCLC™ will be able to acquire the loads attached to the Zūm rooms at this point.99 +* 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. 100 +* Type ##progreset## and press enter to restart SHOWRUNNER™ 101 +* 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. 110 110 * Once completed SHOWRUNNER™ is now ready for full Zūm control 111 111 112 112 == Claim All RF Gateways Instructions == 113 113 114 -Use this method when you have a single S howRunnerCLC™ instance on a local network with all gateways being used for ShowRunnerCLC™.106 +Use this method when you have a single SHOWRUNNER™ instance on a local network with all gateways being used for SHOWRUNNER™. 115 115 116 116 * Connect to the processor's console with Toolbox or your favorite SSH client. 117 117 * Type ##sr discover zummesh true## and press enter. 118 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, S howRunnerCLC™ must be restarted to complete the acquire process.120 -* Type ##progreset## and press enter to restart S howRunnerCLC™121 -* Once S howRunnerCLC™ 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 S howRunnerCLC™ is now ready for full Zūm control111 +* 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. 112 +* Type ##progreset## and press enter to restart SHOWRUNNER™ 113 +* 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. 114 +* Once completed SHOWRUNNER™ is now ready for full Zūm control 123 123 124 124 == Examples == 125 125 ... ... @@ -315,3 +315,4 @@ 315 315 Removed Loads: 0 316 316 Zum Discovery Finished 317 317 }}} 310 +)))