CLI#

Mainflux CLI makes it easy to manage users, things, channels and messages.

CLI can be downloaded as separate asset from project realeses or it can be built with GNU Make tool:

Get the mainflux code

go get github.com/MainfluxLabs/mainflux

Build the mainflux-cli

make cli

which will build mainflux-cli in <project_root>/build folder.

Executing build/mainflux-cli without any arguments will output help with all available commands and flags:

Usage:
  mainflux-cli [command]

Available Commands:
  channels    Channels management
  help        Help about any command
  messages    Send or read messages
  provision   Create things and channels from a config file
  things      Things management
  users       Users management
  health      Mainflux Things service health check

Flags:
  -c, --content-type string    Mainflux message content type (default "application/senml+json")
  -h, --help                   help for mainflux-cli
  -a, --http-prefix string     Mainflux http adapter prefix (default "http")
  -i, --insecure               Do not check for TLS cert
  -l, --limit uint             limit query parameter (default 100)
  -m, --mainflux-url string    Mainflux host URL (default "http://localhost")
  -o, --offset uint            offset query parameter
  -t, --things-prefix string   Mainflux things service prefix
  -u, --users-prefix string    Mainflux users service prefix

Use "mainflux-cli [command] --help" for more information about a command.

It is also possible to use the docker image mainflux/cli to execute CLI command:

docker run -it --rm mainflux/cli -m http://<IP_SERVER> [command]

You can execute each command with -h flag for more information about that command, e.g.

mainflux-cli channels -h

will get you usage info:

Channels management: create, get, update or delete Channels and get list of Things connected to Channels

Usage:
  mainflux-cli channels [flags]
  mainflux-cli channels [command]

Available Commands:
  connections connections <channel_id> <user_token>
  create      create <JSON_channel> <user_token>
  delete      delete <channel_id> <user_token>
  get         get <channel_id | all> <user_token>
  update      update <JSON_string> <user_token>

Service#

Get Mainflux Things services health check#

mainflux-cli health

Users management#

Create User#

Mainflux has two options for user creation. Either everybody or just the admin is able to create new users. This option is dictated through policies and be configured through environment variable (MF_USERS_ALLOW_SELF_REGISTER). If only the admin is allowed to create new users, then the <user_token> is required because the token is used to verify that the requester is admin or not. Otherwise, the token is not used, since everybody can create new users. However, the token is still required, in order to be consistent. For more details, please see Authorization page.

if env `MF_USERS_ALLOW_SELF_REGISTER` is "true" then
  mainflux-cli users create <user_email> <user_password>
else
  mainflux-cli users create <user_email> <user_password> <admin_token>

MF_USERS_ALLOW_SELF_REGISTER is true by default. Therefore, you do not need to provide <admin_token> if MF_USERS_ALLOW_SELF_REGISTER is true. On the other hand, if you set MF_USERS_ALLOW_SELF_REGISTER to false, the Admin token is required for authorization. Therefore, you have to provide the admin token through third argument stated as <admin_token>.

Login User#

mainflux-cli users token <user_email> <user_password>

Retrieve User#

mainflux-cli users get <user_token>

Update User Metadata#

mainflux-cli users update '{"key1":"value1", "key2":"value2"}' <user_token>

Update User Password#

mainflux-cli users password <old_password> <password> <user_token>

System Provisioning#

Create Thing#

mainflux-cli things create '{"name":"myThing"}' <user_token>

Create Thing with metadata#

mainflux-cli things create '{"name":"myThing", "metadata": {\"key1\":\"value1\"}}' <user_token>

Provision Things#

mainflux-cli provision things <file> <user_token>

• file - A CSV or JSON file containing things (must have extension .csv or .json)
• user_token - A valid user auth token for the current system

Update Thing#

mainflux-cli things update '{"id":"<thing_id>", "name":"myNewName"}' <user_token>

Remove Thing#

mainflux-cli things delete <thing_id> <user_token>

Retrieve a subset list of provisioned Things#

mainflux-cli things get all --offset=1 --limit=5 <user_token>

Retrieve Thing By ID#

mainflux-cli things get <thing_id> <user_token>

Create Channel#

mainflux-cli channels create '{"name":"myChannel"}' <user_token>

Provision Channels#

mainflux-cli provision channels <file> <user_token>

• file - A CSV or JSON file containing channels (must have extension .csv or .json)
• user_token - A valid user auth token for the current system

Update Channel#

mainflux-cli channels update '{"id":"<channel_id>","name":"myNewName"}' <user_token>

Remove Channel#

mainflux-cli channels delete <channel_id> <user_token>

Retrieve a subset list of provisioned Channels#

mainflux-cli channels get all --offset=1 --limit=5 <user_token>

Retrieve Channel By ID#

mainflux-cli channels get <channel_id> <user_token>

Access control#

Connect Thing to Channel#

mainflux-cli things connect <thing_id> <channel_id> <user_token>

Bulk Connect Things to Channels#

mainflux-cli provision connect <file> <user_token>

• file - A CSV or JSON file containing thing and channel ids (must have extension .csv or .json)
• user_token - A valid user auth token for the current system

An example CSV file might be

<thing_id>,<channel_id>
<thing_id>,<channel_id>

in which the first column is thing IDs and the second column is channel IDs. A connection will be created for each thing to each channel. This example would result in 4 connections being created.

A comparable JSON file would be

{
    "thing_ids": [
        "<thing_id>",
        "<thing_id>"
    ],
    "channel_ids": [
        "<channel_id>",
        "<channel_id>"
    ]
}

Disconnect Thing from Channel#

mainflux-cli things disconnect <thing_id> <channel_id> <user_token>

Retrieve a subset list of Channels connected to Thing#

mainflux-cli things connections <thing_id> <user_token>

Retrieve a subset list of Things connected to Channel#

mainflux-cli channels connections <channel_id> <user_token>

Messaging#

Send a message over HTTP#

mainflux-cli messages send <channel_id> '[{"bn":"Dev1","n":"temp","v":20}, {"n":"hum","v":40}, {"bn":"Dev2", "n":"temp","v":20}, {"n":"hum","v":40}]' <thing_auth_token>

Read messages over HTTP#

mainflux-cli messages read <channel_id> <thing_auth_token>