Bastet is a server which acts as a proxy between CoAP devices spread around the home and control scripts running on a server talking HTTP.

Bastet provides:

• CoAP <-> HTTP translation
• Data Logging
• Authentication

To start a Bastet server you just need to start the application with two commandline parameters:

--http 58242 --connection="Data Source=Bastet.sqlite;Version=3;New=True;" --setup -lni

This will start an interactive setup to configure Bastet. You can now visit http://localhost:58241 to see the Bastet status screen.

This is the port the http server will bind to

This is the database connection string, the example is a sqlite database on disk called Bastet.sqlite.

This indicates that the node should be "setup" cleanly, i.e. tables will be created, and a new user/password will be inserted. The username will be "Administrator" and password will be "password".

These flags indicate which addresses should be bound by the HTTP server.

-l will bind the "localhost" address

-n will bind the netBIOS machine name address

-i will bind all non localhost IPs

The main purpose of Bastet is to act as a proxy between your control scripts, which talk to Bastet using HTTP, and your home automation devices which talk to Bastet using CoAP. The root of the API is at http://localhost:58241/api.

• Authentication
• Users
• Claims
• Devices
• Devices (Proxying)
• Devices (Sensors)

Almost all of the API requires authentication to use, so this is the first thing to check out! There are two ways to authenticate your requests:

• A session cookie
• A session key in the query string

To get your session key POST to /authentication. You can send your parameters in one of three ways:

• HTTP basic auth
• "username" and "password" parameters in query string
• "username" and "password" fields in form data

This will return a your session key, as well as set a cookie with your session key. From here on you can either send the cookie along with your requests, or include sessionkey=thisismysupersecretsessionkey in your query string. To logout simply DELETE to /authentication and this session key will no longer be valid.

User permissions are managed with "claims". Certain actions require a user to have a certain claim to perform them, for example getting a list of all users (GET /users) requires the "list-users" claim.

• GET /users/{username}/claims
• Requires claims: "list-claims"

• POST /users/{username}/claims
• Requires claims: "create-claim"
• Body should be the name of the claim

• DELETE /users/{username}/claims
• Requires claims: "delete-claim"
• Body should be the name of the claim

• GET /users
• Requires claims: "list-users"

• GET /users/{username}

• POST /user
• Send "username" and "password" in Query string or form data