Skip to Content
Last modified by Alexander Mott on 2023/07/07 15:17
From version 17.1
edited by Craig Lewis
on 2021/10/26 17:43
Change comment: There is no comment for this version
To version 29.1
edited by Alexander Mott
on 2022/11/17 16:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Appendix.Integration Options.CoAP with Crestron S# Library and Modules.WebHome
1 +SHOWRUNNER™ Integrations Guide.Integration Options.CoAP with Crestron S# Library and Modules.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.craig\.lewis@chiefintegrations\.com
1 +XWiki.alexander\.mott@chiefintegrations\.com
Content
... ... @@ -1,28 +1,71 @@
1 -===== __**Us [[NEWEST >>https://files.chiefintegrations.com/index.php/s/WHNzXrrZbB5jC3E]]version of showrunner.**__ =====
1 +===== Use ShowRunner version 3.010 or later =====
2 2  
3 -===== =====
3 +Terminology:
4 4  
5 -===== Host processor (LWAPI Server) Setup (DIN-AP3 @ 10.44.5.91) =====
5 +* Client Processor - Processor that will interact with hardware attached to the host procesor.
6 +* CWS - Crestron Web Server, the processor's internal web server
7 +* Host Processor (Server) - Processor that hosts the physical hardware
8 +* LWAPI - Lightweight API (CoAP)
9 +* User Page Auth - Requires a username and password to access the internal web server (CWS) on the processor.  3-series always has this enabled if authentication is activated.  4-series processors have an option to have user page auth on or not (default is off).
6 6  
11 +Steps:
12 +
13 +1. [[Setup Host Processor>>WebHome||anchor="Host processor (LWAPI Server) Setup (DIN-AP3 @ 10.44.5.91)"]]
14 +11. Verify processor configuration
15 +11. Verify LWAPI is enabled
16 +11. Create API User
17 +11. Create CWS User (if necessary)
18 +11. Save the configuration
19 +1. [[Setup Client Processor>>WebHome||anchor="Client processor (LWAPI Client) Setup (DIN-AP4) Version 3.011 or newer"]]
20 +11. Define the remote system
21 +11. Setup auth for the remote system
22 +11. Save the configuration
23 +1. Verify successful communications with the following commands:
24 +11. On host, verify the client shows up as a web session: ##sradmin sh web sess##
25 +11. On client, verify the session with the host: ##sr sh lwapi cli br##
26 +
27 +===== Host processor (LWAPI Server) Setup (e.g. DIN-AP3 @ 10.44.5.91) =====
28 +
7 7  Steps 1-3 and 5 always needed.
8 8  
9 9  1. If 3-series, Enable Authentication [##authentication on##] or SSL [##ssl self##] if not already enabled.  4-Series have authentication enabled by default.  User Page Auth should be turned off on 4-series.
10 -1. Enable LWAPI In Config (@ root level):
32 +1. Enable LWAPI
33 +From Console (v 3.011 or later; processor will automatically restart):
34 +## sr lwapi enable true##
35 +In Config (@ root level; reloading the configuration is required):
11 11  ## "LwApiEnable": true,
12 12   "LwApiSecurityLevel": "Auth",##
13 -1. Create an API User and record the Key and Secret.  User group must have //LWAPI //role and //Execute //permissions.  //Lightweight API Users// group has been created for this purpose:
38 +1. Create an API User and record the Key and Secret.  User group must have //LWAPI //role and //Execute //permissions.  This allows the  //Lightweight API Users// group has been created for this purpose:
14 14  ##DIN-AP3>sradmin add api user "Central Control" "Lightweight API Users"
15 15  API User Central Control generated with Group permissions Lightweight API Users and Key: (% style="color:blue" %)**YTd2pQn7sjwiOWD9NqCIWw**(%%) Secret: (% style="color:orange" %)**OeiQEFo_-EDfc7sQe_qRpeQzSkZjylV2roa76utpJLI**(%%)##
16 -
17 -1. If 3-series w/ auth enabled or 4-series with user page auth enabled then add a remote user with permissions to connect to the control system.  This is done by adding a local user to the system with connect privileges.  Sample values shown, do not re-use these.
41 +1. If 3-series w/ auth enabled or 4-series with user page auth enabled then add a remote user with permissions to connect to the control system.  This is done by adding a local user to the system with user privileges.  Sample values shown, do not re-use these.
18 18  ##DIN-AP3>adduser -N:(% style="color:purple" %)**lwapi**(%%) -P:(% style="color:darkgoldenrod" %)**dMFN9pJJXjWLGd7t**(%%)
19 19  User account was successfully created.
20 -DIN-AP3>addusertogroup -N:lwapi -G:Connects
21 -'lwapi' was successfully added to group 'Connects'.##
44 +DIN-AP3>addusertogroup -N:lwapi -G:Users
45 +'lwapi' was successfully added to group 'Users'.##
22 22  1. Save the configuration
23 23  
24 -===== Client processor (LWAPI Client) Setup (DIN-AP4) =====
48 +===== Client processor (LWAPI Client) Setup (e.g. DIN-AP4) Version 3.011 or newer =====
25 25  
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 +
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 + },##
59 +1. Add Users :
60 +if CWS User is not needed:
61 +##DIN-AP4>sr remote system auth (% style="color:darkcyan" %)**1**(%%) (% style="color:blue" %)**YTd2pQn7sjwiOWD9NqCIWw**(%%) (% style="color:orange" %)**OeiQEFo_-EDfc7sQe_qRpeQzSkZjylV2roa76utpJLI**(%%)##
62 +if CWS User is needed:
63 +##DIN-AP4>sr remote system auth (% style="color:darkcyan" %)**1**(%%) (% style="color:blue" %)**YTd2pQn7sjwiOWD9NqCIWw**(%%) (% style="color:orange" %)**OeiQEFo_-EDfc7sQe_qRpeQzSkZjylV2roa76utpJLI **(% style="color:purple" %)**lwapi**(%%)** (% style="color:darkgoldenrod" %)dMFN9pJJXjWLGd7t(%%)**
64 +Success##
65 +1. Save the configuration
66 +
67 +===== Client processor (LWAPI Client) Setup (e.g. DIN-AP4) Version 3.010 or earlier =====
68 +
26 26  Steps 1-3 and 6 always needed.
27 27  
28 28  1. Define remote system in the config: