Skip to Content

Changes for page Zūm Discovery

Last modified by Alexander Mott on 2025/04/03 17:35
From version 12.1
edited by Alexander Mott
on 2022/10/06 14:25
Change comment: There is no comment for this version
To version 15.1
edited by Alexander Mott
on 2023/03/29 21:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,3 +1,7 @@
1 +(% class="box errormessage" %)
2 +(((
3 +Cresnet Discovery is not working on ZUMNET-JBOXs. Crestron has acknowledged a fix has been sent to QE. Discovery must be fixed before SHOWRUNNER™ can auto-discover hardware.
4 +)))
1 1  (% class="box warningmessage" %)
2 2  (((
3 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,10 +16,10 @@
16 16  
17 17  == Notes and Limitations ==
18 18  
19 -(% class="box errormessage" %)
23 +(% class="box warningmessage" %)
20 20  (((
21 21  * SHOWRUNNER™ version 3.014 or newer required
22 -* Zūm Wired firmware version 1.02.10 or greater required
26 +* Zūm Wired firmware .puf version 1.02.10 or greater required (ZUMNET-JBOX installed minimum version 1.001.00081)
23 23  * Disconnect from any ZUMNET devices you may be connected to in Toolbox prior to running the discovery commands
24 24  * Cresnet devices landed on Zūm Link will not be discovered (Crestron bug expected to be corrected in a future firmware release)
25 25  * One area will be created per ZUMNET-JBOX; if there are more areas than ZUMNET-JBOXs, additional areas must be created manually
... ... @@ -48,6 +48,8 @@
48 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
49 49  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
50 50  1*. If you do not manually configure the IP table, then SHOWRUNNER™ will automatically configure the IP-ID for each ZUMNET-JBOX during discovery
55 +1. Set the ZUMNET-JBOX into either Zūm ("App") mode or CNET mode as required for the program
56 +1*. Full control from SHOWRUNNER™ is only possible if all ZUMNET-JBOXs are in CNET mode. Odd behavior may result from conflicts between SHOWRUNNER™ and internal logic if the ZUMNET-JBOXs are not put into CNET mode
51 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
52 52  1. Disconnect from any ZUMNET-JBOXs and then connect to the processor in Toolbox
53 53  1. Run the command: ##sr discover zumnet true false##
... ... @@ -56,8 +56,7 @@
56 56  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
57 57  1**. One area will be created per ZUMNET-JBOX, and all hardware attached to that ZUMNET-JBOX will be assigned to that area
58 58  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
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
65 +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 61  
62 62  = Zūm Wireless Discovery =
63 63