how this will work

[drewbharris]

there will be a web server on the Pi with a RESTful API that it hit by the web application (the single page JS desktop browser application or the mobile application). on boot up, the web server will attempt to open a websocket client connection to the cloud server - the handshake process will include the UID of the client. then, calls made to the cloud API will be forwarded through the websocket connection to the client (the rpi).

local API:
/api/v1/:plug/:state

remote API:
/api/v1/:clientid/:plug/:state

if there's no active websocket connection, it means that the client (the rpi) is not internet connected.

[mike-anderson]

I think we should say deviceid, the client id should be implied in the session that is created when we authorize against the client user/password. Also there might be multiple devices per client.

[drewbharris]

That's a really good point, I'll change it to device ID.

Also. The device ID should be server-generated (to ensure no dupes) and provided to the device in the QR code generated by the mobile app.