Changes for page Zūm Discovery
Last modified by Austin Weygandt on 2025/05/02 20:21
From version 24.2
edited by Craig Lewis
on 2024/05/22 21:45
on 2024/05/22 21:45
Change comment:
There is no comment for this version
To version 12.1
edited by Alexander Mott
on 2022/10/06 14:25
on 2022/10/06 14:25
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,1 +1,1 @@ 1 -SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide. Program Configuration.WebHome1 +SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. craig\.lewis@chiefintegrations\.com1 +XWiki.alexander\.mott@chiefintegrations\.com - Content
-
... ... @@ -1,14 +9,6 @@ 1 -(% class="box errormessage" %) 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. 4 - 5 -**WARNING:** Cresnet Discovery is non-functional for ZUMNET-JBOXs with certain versions of Crestron Device Database. 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. 7 -))) 8 - 9 9 (% class="box warningmessage" %) 10 10 ((( 11 -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.SHOWRUNNER™ Installation Guide.Preparation.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]]. 12 12 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]]. 13 13 ))) 14 14 ... ... @@ -16,18 +16,18 @@ 16 16 {{toc/}} 17 17 {{/box}} 18 18 19 -If Zūm Wired or Wireless devices have been configured using Crestron's Zūm App, then it is possible to automatically build a S howRunnerCLC™ 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™. 20 20 21 -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.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. 22 22 23 23 = Zūm Wired Discovery = 24 24 25 25 == Notes and Limitations == 26 26 27 -(% class="box warningmessage" %)19 +(% class="box errormessage" %) 28 28 ((( 29 -* S howRunnerCLC™ version 3.014 or newer required30 -* Zūm Wired firmware .pufversion 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 31 31 * Disconnect from any ZUMNET devices you may be connected to in Toolbox prior to running the discovery commands 32 32 * Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release) 33 33 * One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually ... ... @@ -35,92 +35,86 @@ 35 35 36 36 == Steps == 37 37 38 -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 necessary30 +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 39 39 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. 40 40 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: 41 41 1*. Connect to the first ZUMNET-JBOX in Toolbox 42 42 1*. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 43 -1**. Note: The S howRunnerCLC™ built-in DHCP server is not meant to be used in production44 -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 addresses35 +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 45 45 1*. Set unique Connection IDs for each device hosted on the ZUMNET-JBOX so that their firmware can be updated 46 46 1*. Load the Zūm Wired firmware to the ZUMNET-JBOX 47 47 1*. Repeat the above steps for all ZUMNET-JBOXs 48 48 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 49 -1. Connect to each ZUMNET-JBOX in the Crestron Zūm App 50 -1*. Commission room through the app 51 -1**. configure keypad logic 52 -1**. configure occupancy sensor settings 53 -1**. calibrate photocell(s) 54 -1*. Set hostnames for the ZUMNETs for easy identification when hardware is discovered. 41 +1. Connect to first ZUMNET-JBOX in the Crestron Zūm App 55 55 1. Unique Connection IDs should be automatically assigned to any Zūm Link and Cresnet devices on the ZUMNET-JBOX 56 56 1*. If firmware was out-of-date, then this step should have already been completed 57 57 1*. If unique CIDs are not automatically assigned, connect to the JBOX in Toolbox and give the devices unique CIDs 58 58 1. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 59 59 1*. If firmware was out-of-date, then this step should have already been completed 60 -1*. Note: The S howRunnerCLC™ built-in DHCP server is not meant to be used in production61 -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 addresses47 +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 62 62 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 63 63 1*. If you do not manually configure the IP table, then SHOWRUNNER™ will automatically configure the IP-ID for each ZUMNET-JBOX during discovery 64 -1. Set the ZUMNET-JBOX into either Zūm ("App") mode or CNET mode as required for the program 65 -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 66 -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 67 67 1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox 68 68 1. Run the command: ##sr discover zumnet true false## 69 -1*. This command tells S howRunnerCLC™ to discover all ZUMMNET-JBOXs on the network, configure their IP tables, and then add corresponding IP Devices to the configuration54 +1*. This command tells SHOWRUNNER™ to discover all ZUMMNET-JBOXs on the network, configure their IP tables, and then add corresponding IP Devices to the configuration 70 70 1. Run the command: ##sr discover zumnet true true## 71 -1*. This command tells S howRunnerCLC™ 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 configuration56 +1*. This command tells SHOWRUNNER™ 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 72 72 1**. One area will be created per ZUMNET-JBOX, and all hardware attached to that ZUMNET-JBOX will be assigned to that area 73 73 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 74 -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 75 75 76 76 = Zūm Wireless Discovery = 77 77 78 78 == Notes and Limitations == 79 79 80 -(% class="box warningmessage" %)66 +(% class="box errormessage" %) 81 81 ((( 82 -* Processor with S howRunnerCLC™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired83 -** For S howRunnerCLC™ 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##** 84 84 * ZUM-NETBRIDGES must already be acquired to their respective gateway 85 -* S howRunnerCLC™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices71 +* SHOWRUNNER™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices 86 86 * Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command 87 -* Plug loads will not appear in the S howRunnerCLC™ UI73 +* Plug loads will not appear in the SHOWRUNNER™ UI 88 88 ))) 89 89 90 -(% class="box in fomessage" id="HCaution:" %)76 +(% class="box warningmessage" id="HCaution:" %) 91 91 ((( 92 -**Note:** S howRunnerCLC™ has two different approaches for Zūm Wireless Discovery78 +**Note:** SHOWRUNNER™ has two different approaches for Zūm Wireless Discovery 93 93 94 -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.95 -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.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. 96 96 ))) 97 97 98 98 == Manual RF Gateway Assignment Instructions == 99 99 100 -Use this method if you have multiple S howRunnerCLC™ 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. 101 101 102 102 * Connect to the processor's console with Toolbox or your favorite SSH client. 103 103 * Type ##sr devmgr ethernet query## and press enter. This queries the local network for RF Gateways. 104 104 * Type ##sr devmgr ethernet show devices## and press enter. This displays all found Crestron ethernet devices. 105 -* 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.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. 106 106 * Type ##sr discover zummesh false## and press enter. 107 107 * Status messages and the results will be displayed on the console. The process should take about 3 minutes. 108 -* 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.109 -* Type ##progreset## and press enter to restart S howRunnerCLC™110 -* 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.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. 111 111 * Once completed SHOWRUNNER™ is now ready for full Zūm control 112 112 113 113 == Claim All RF Gateways Instructions == 114 114 115 -Use this method when you have a single S howRunnerCLC™ 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™. 116 116 117 117 * Connect to the processor's console with Toolbox or your favorite SSH client. 118 118 * Type ##sr discover zummesh true## and press enter. 119 119 * Status messages and the results will be displayed on the console. The process should take about 3 minutes. 120 -* 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.121 -* Type ##progreset## and press enter to restart S howRunnerCLC™122 -* 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.123 -* Once completed S howRunnerCLC™ is now ready for full Zūm control106 +* 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 124 124 125 125 == Examples == 126 126