-
Notifications
You must be signed in to change notification settings - Fork 5
Update README.md #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
abhijit-mahajani-imgtec
merged 1 commit into
CreatorKit:dev
from
rahul-daga-imgtec:rahul-daga-imgtec-patch-1
Mar 22, 2016
Merged
Update README.md #11
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,71 @@ | ||
# flow_device_manager | ||
flow device manager application | ||
## Device Manager | ||
Device Manager application is used to provision the gateway device and constrained devices with access details to register with the FlowCloud. It runs on the gateway device and uses the Awalwm2m sdk to communicate with the awalwm2m server and client running on the same. | ||
Currently it can be used to : | ||
- Provision the gateway device | ||
- Check if the gateway device is provisioned or not | ||
- Provision the constrained device | ||
- Check if the constrained device is provisioned or not | ||
- List the constrained devices connected to the local server | ||
|
||
## Prerequisites | ||
Prior to running device manager, make sure that: | ||
- Awalwm2m client daemon(awa_clientd) is running. | ||
- Awalwm2m server daemon(awa_serverd) is running. | ||
|
||
**NOTE:** Please do "ps" on console to see "specific" process is running or not. | ||
|
||
## Using the ubus interface of Device Manager | ||
### Provisioning the gateway device: | ||
|
||
``` | ||
root@OpenWrt:/# ubus -t 60 call flow_device_manager provision_gateway_device '{"device_name":"MyCi40","device_type":"FlowGateway","licensee_id":7,"fcap":"XXXXXXXXXX", "licensee_secret":"XXXXXXXXXXXXXX"}' | ||
{ | ||
"provision_status": 0 | ||
} | ||
``` | ||
Status 0 : The device was provisioned successfully. | ||
Status 1 : Provisoning failed | ||
Status 2 : The device was already provisioned. | ||
|
||
### Checking if the gateway device is provisioned or not | ||
``` | ||
root@OpenWrt:/# ubus call flow_device_manager is_gateway_device_provisioned | ||
{ | ||
"provision_status": false | ||
} | ||
``` | ||
|
||
### Listing the devices connected to the gateway device | ||
``` | ||
root@OpenWrt:/# ubus call flow_device_manager get_client_list | ||
{ | ||
"clients": [ | ||
{ | ||
"clientId": "LedDevice", | ||
"is_device_provisioned": false | ||
} | ||
] | ||
} | ||
``` | ||
|
||
### Provisioning a constrained device: | ||
``` | ||
root@OpenWrt:/# ubus -t 60 call flow_device_manager provision_constrained_device '{"fcap":"XXXXXXXXXX", "client_id":"LedDevice", "licensee_id": 7, "device_type" : "FlowCreatorLED", "parent_id": "08 5A 24 DE A8 C2 0A 4B AB 24 4C F6 ED 5D 5F 62 "}' | ||
{ | ||
"status": 0 | ||
} | ||
``` | ||
**NOTE:** The parent id should be the same as the device id of the gateway device. It can be read from /etc/lwm2m/flow_access.cfg | ||
|
||
### Checking if the constrained device is provisioned or not | ||
``` | ||
root@OpenWrt:/# ubus call flow_device_manager is_constrained_device_provisioned '{"client_id":"LedDevice"}' | ||
{ | ||
"provision_status": false | ||
} | ||
|
||
``` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also worth adding "Logs for Device Manager application can be checked at /var/log/device_manager_appd" |
||
|
||
## Debugging | ||
|
||
The logs of device manager application can be found at /var/log/device_manager_ubusd |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add some description that its using Awalwm2m client/server sdk apis and add worth checking if these processes are there
Prior to running button gateway application, make sure that:
Awalwm2m client daemon(awa_clientd) is running.
Awalwm2m server daemon(awa_serverd) is running.
Awalwm2m bootstrap daemon(awa_bootstrapd) is running.