Changes for page CoAP ShowRunner to ShowRunnerCLC™ Setup Instructions
Last modified by Alexander Mott on 2023/07/07 15:17
From version 29.1
edited by Alexander Mott
on 2022/11/17 16:58
on 2022/11/17 16:58
Change comment:
There is no comment for this version
To version 32.1
edited by Alexander Mott
on 2023/07/07 15:17
on 2023/07/07 15:17
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -CoAP ShowRunner to ShowRunner Setup Instructions 1 +CoAP ShowRunner to ShowRunnerCLC™ Setup Instructions - Content
-
... ... @@ -1,8 +1,8 @@ 1 -===== Use ShowRunner version 3.010 or later ===== 1 +===== Use ShowRunnerCLC™ version 3.010 or later ===== 2 2 3 3 Terminology: 4 4 5 -* Client Processor - Processor that will interact with hardware attached to the host procesor. 5 +* Client Processor - Processor that will interact with hardware attached to the host processor. 6 6 * CWS - Crestron Web Server, the processor's internal web server 7 7 * Host Processor (Server) - Processor that hosts the physical hardware 8 8 * LWAPI - Lightweight API (CoAP) ... ... @@ -21,7 +21,7 @@ 21 21 11. Setup auth for the remote system 22 22 11. Save the configuration 23 23 1. Verify successful communications with the following commands: 24 -11. On host, verify the client shows up as a web session: ##sr adminsh websess##24 +11. On host, verify the client shows up as a web session: ##sr sh lwapi serv cli## 25 25 11. On client, verify the session with the host: ##sr sh lwapi cli br## 26 26 27 27 ===== Host processor (LWAPI Server) Setup (e.g. DIN-AP3 @ 10.44.5.91) ===== ... ... @@ -50,12 +50,14 @@ 50 50 Steps 1-3 always needed. **Note:** host and client processors must be able to communicate with each other to use this method (i.e. the network must be configured and both processors must have SHOWRUNNER™ program and configuration loaded). 51 51 52 52 1. Define remote system in the config: 53 -## { 54 - "SystemId": (% style="color:darkcyan" %)1(%%), 55 - "IpAddressOrHostname": "10.44.5.91", 56 - "Label": "HUB-1-1", 57 - "ConnectionType": "LWAPI" 58 - },## 53 +## "RemoteSystems": [ 54 + { 55 + "SystemId": (% style="color:darkcyan" %)1(%%), 56 + "IpAddressOrHostname": "10.44.5.91", 57 + "Label": "HUB-1-1", 58 + "ConnectionType": "LWAPI" 59 + }, 60 + ],## 59 59 1. Add Users : 60 60 if CWS User is not needed: 61 61 ##DIN-AP4>sr remote system auth (% style="color:darkcyan" %)**1**(%%) (% style="color:blue" %)**YTd2pQn7sjwiOWD9NqCIWw**(%%) (% style="color:orange" %)**OeiQEFo_-EDfc7sQe_qRpeQzSkZjylV2roa76utpJLI**(%%)## ... ... @@ -69,12 +69,14 @@ 69 69 Steps 1-3 and 6 always needed. 70 70 71 71 1. Define remote system in the config: 72 -## { 73 - "SystemId": (% style="color:darkcyan" %)1(%%), 74 - "IpAddressOrHostname": "10.44.5.91", 75 - "Label": "HUB-1-1", 76 - "ConnectionType": "LWAPI" 77 - },## 74 +## "RemoteSystems": [ 75 + { 76 + "SystemId": (% style="color:darkcyan" %)1(%%), 77 + "IpAddressOrHostname": "10.44.5.91", 78 + "Label": "HUB-1-1", 79 + "ConnectionType": "LWAPI" 80 + }, 81 + ],## 78 78 1. Add remote user for LWAPI (this is the key and secret created on the host): 79 79 ##DIN-AP4>sradmin add remote user HUB-1 (% style="color:blue" %)**YTd2pQn7sjwiOWD9NqCIWw**(%%) (% style="color:orange" %)**OeiQEFo_-EDfc7sQe_qRpeQzSkZjylV2roa76utpJLI**(%%) 80 80 Remote User HUB-1 ((% style="color:green" %)//**1a920b8b-3ab8-44bd-bc7b-0fc77abf0a13**//(%%)) added with Group permissions Remote Connection##