beebotte/bbt_client_js

This package is a Javascript client library for interfacing with Beebotte, an open cloud platform for the Internet of Things and real time connected applications.

Beebotte JS Client

what	where
overview	http://beebotte.com/overview
tutorials	http://beebotte.com/tutorials
apidoc	http://beebotte.com/docs/clientapi
source	https://github.com/beebotte/bbt_client_js

Bugs / Feature Requests

Think you.ve found a bug? Want to see a new feature in beebotte? Please open an issue in github. Please provide as much information as possible about the issue type and how to reproduce it.

https://github.com/beebotte/bbt_client_js/issues

Install

Clone the source code from github, and add the source code to your project

git clone https://github.com/beebotte/bbt_client_js.git

Include it directly from beebotte

<script type="text/javascript" src="//beebotte.com/bbt.js"></script>

OR the minimified version

<script type="text/javascript" src="//beebotte.com/bbt.min.js"></script>

Usage

To fully use Beebotte, you need to be a registered user. If this is not the case, create your account at https://beebotte.com and note your access credentials.

As a reminder, Beebotte resource description uses a two levels hierarchy:

• Channel: physical or virtual connected object (an application, an arduino, a coffee machine, etc) providing some resources
• Resource: most elementary part of Beebotte, this is the actual data source (e.g. temperature from a domotics sensor)

For documentation, check the links under:

https://beebotte.com/overview

Dependencies

Beebotte Javascript client library uses Socket.io 1.0 and jQuery. You need to include them as well.

License

Copyright 2013 - 2017 Beebotte.

The MIT License

bbt_client_js's Issues

Problem with subscribe method

When a subscription is made to a channel with read access set to false; messages are still received on that channel.

Migrate to Socket.io 1.x

Use Socket.io 1.x instead of 0.9

Enable error messages by default

subscribe to wildcard channels (*.resource or *.*)

It would be good to extend wildcard support to channel names.
This allows a client to subscribe to *.someresource

Problem when publish data set to false

The following publish will not make it through:

bbt.publish({
    channel: 'mychannel',
    resource: 'myresource',
    data: false
})

Case insensitive authentication method

Authentication method is case sensitive. It assumes the value is lowercase.
This might lead to confusion when the user gives the value in uppercase:

auth_method: 'get'  // Accepted
auth_method: 'GET'  // Not accepted

Ease this constraint by allowing case insensitive auth_method parameter.

broken read from public resources

Reading from public resources is broken.

https://github.com/beebotte/bbt_client_js/blob/master/src/bbt.js#L687-L710

Impossible to establish clear text connections

When the connection is initiated with 'ssl' set to 'false', the session is still established with SSL encryption.

Messages not delivered when the resource is wildcard

When a user subscribes to a topic with resource set to wildcard ('channel.*'), events are received but the on message callback function is not called.