Changes for page Zūm Discovery
Last modified by Alexander Mott on 2025/04/03 17:35
From version 10.1
edited by Alexander Mott
on 2022/10/05 16:18
on 2022/10/05 16:18
Change comment:
There is no comment for this version
To version 21.1
edited by Alexander Mott
on 2023/10/11 16:37
on 2023/10/11 16:37
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,6 +1,18 @@ 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 + 1 1 (% class="box warningmessage" %) 2 2 ((( 3 -This article is about automatically building a S HOWRUNNER™ 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 +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]]. 4 4 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]]. 5 5 ))) 6 6 ... ... @@ -8,20 +8,18 @@ 8 8 {{toc/}} 9 9 {{/box}} 10 10 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™. 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™. 14 14 15 -There are certain pre-requisites and limitations when building a S HOWRUNNER™ 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 +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. 16 16 17 17 = Zūm Wired Discovery = 18 18 19 19 == Notes and Limitations == 20 20 21 -(% class="box errormessage" %)31 +(% class="box warningmessage" %) 22 22 ((( 23 -* S HOWRUNNER™ version 3.014 or newer required24 -* Zūm Wired firmware version 1.02.10 or greater required 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) 25 25 * Disconnect from any ZUMNET devices you may be connected to in Toolbox prior to running the discovery commands 26 26 * Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release) 27 27 * One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually ... ... @@ -29,13 +29,13 @@ 29 29 30 30 == Steps == 31 31 32 -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 necessary42 +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 33 33 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. 34 34 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: 35 35 1*. Connect to the first ZUMNET-JBOX in Toolbox 36 36 1*. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 37 -1**. Note: The S HOWRUNNER™ built-in DHCP server is not meant to be used in production38 -1**. If the S HOWRUNNER™ 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 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 39 39 1*. Set unique Connection IDs for each device hosted on the ZUMNET-JBOX so that their firmware can be updated 40 40 1*. Load the Zūm Wired firmware to the ZUMNET-JBOX 41 41 1*. Repeat the above steps for all ZUMNET-JBOXs ... ... @@ -46,69 +46,70 @@ 46 46 1*. If unique CIDs are not automatically assigned, connect to the JBOX in Toolbox and give the devices unique CIDs 47 47 1. Configure a static IP address for the ZUMNET-JBOX if there is no DHCP server on the network 48 48 1*. If firmware was out-of-date, then this step should have already been completed 49 -1*. Note: The S HOWRUNNER™ built-in DHCP server is not meant to be used in production50 -1*. If the S HOWRUNNER™ built-in DHCP server was used to assign IP addresses to devices, it is still necessary to give those devices static IP addresses59 +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 51 51 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 52 52 1*. If you do not manually configure the IP table, then SHOWRUNNER™ will automatically configure the IP-ID for each ZUMNET-JBOX during discovery 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 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 54 54 1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox 55 55 1. Run the command: ##sr discover zumnet true false## 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 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 58 58 1. Run the command: ##sr discover zumnet true true## 59 -1*. This command tells SHOWRUNNER™ to discover all Zūm Link hardware on the previously discovered Zūm Net devices 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 60 60 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 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 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. 63 63 64 64 = Zūm Wireless Discovery = 65 65 66 66 == Notes and Limitations == 67 67 68 -(% class="box errormessage" %)79 +(% class="box warningmessage" %) 69 69 ((( 70 -* Processor with S HOWRUNNER™ version 2.190 or newer must be running on the same network as the gateway(s) to be acquired71 -** For S HOWRUNNER™ versions prior to 3.014 and newer, replace **##sr discover zummesh##** commands with **##sr discover zum##**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##** 72 72 * ZUM-NETBRIDGES must already be acquired to their respective gateway 73 -* S HOWRUNNER™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices84 +* ShowRunnerCLC™ will automatically address any ZUM-NETBRIDGES that do not need have addresses assigned, but will still honor any already addressed devices 74 74 * Disconnect from any RF gateways you may be connected to in Toolbox prior to running the discovery command 75 -* Plug loads will not appear in the S HOWRUNNER™ UI86 +* Plug loads will not appear in the ShowRunnerCLC™ UI 76 76 ))) 77 77 78 -(% class="box warningmessage" id="HCaution:" %)89 +(% class="box infomessage" id="HCaution:" %) 79 79 ((( 80 -**Note:** S HOWRUNNER™ has two different approaches for Zūm Wireless Discovery91 +**Note:** ShowRunnerCLC™ has two different approaches for Zūm Wireless Discovery 81 81 82 -1. **Manual RF Gateway Assignment** - S HOWRUNNER™ 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.83 -1. **Claim All RF Gateways** - S HOWRUNNER™ 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.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. 84 84 ))) 85 85 86 86 == Manual RF Gateway Assignment Instructions == 87 87 88 -Use this method if you have multiple S HOWRUNNER™ instances on the same network or have gateways used by other Crestron systems.99 +Use this method if you have multiple ShowRunnerCLC™ instances on the same network or have gateways used by other Crestron systems. 89 89 90 90 * Connect to the processor's console with Toolbox or your favorite SSH client. 91 91 * Type ##sr devmgr ethernet query## and press enter. This queries the local network for RF Gateways. 92 92 * Type ##sr devmgr ethernet show devices## and press enter. This displays all found Crestron ethernet devices. 93 -* 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 HOWRUNNER™ will auto-assign an IP-ID. After all gateways have been claimed by SHOWRUNNER™, proceed to the next step.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. 94 94 * Type ##sr discover zummesh false## and press enter. 95 95 * Status messages and the results will be displayed on the console. The process should take about 3 minutes. 96 -* 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 HOWRUNNER™ must be restarted to complete the acquire process.97 -* Type ##progreset## and press enter to restart S HOWRUNNER™98 -* Once SHOWRUNNER™ has finished restarting type ##sr discover zummesh false## and press enter. S HOWRUNNER™ will be able to acquire the loads attached to the Zūm rooms at this point.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. 99 99 * Once completed SHOWRUNNER™ is now ready for full Zūm control 100 100 101 101 == Claim All RF Gateways Instructions == 102 102 103 -Use this method when you have a single S HOWRUNNER™ instance on a local network with all gateways being used for SHOWRUNNER™.114 +Use this method when you have a single ShowRunnerCLC™ instance on a local network with all gateways being used for ShowRunnerCLC™. 104 104 105 105 * Connect to the processor's console with Toolbox or your favorite SSH client. 106 106 * Type ##sr discover zummesh true## 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 HOWRUNNER™ must be restarted to complete the acquire process.109 -* Type ##progreset## and press enter to restart S HOWRUNNER™110 -* Once S HOWRUNNER™ 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 -* Once completed S HOWRUNNER™ is now ready for full Zūm control119 +* 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 112 112 113 113 == Examples == 114 114 ... ... @@ -304,4 +304,3 @@ 304 304 Removed Loads: 0 305 305 Zum Discovery Finished 306 306 }}} 307 -)))