skip to navigation
skip to content

Not Logged In

pyonep 0.8.1

Python bindings for Exosite API over HTTP JSON RPC.

Latest Version: 0.13.5

About pyonep

The pyonep package is an API library with Python bindings to the
following Exosite One Platform APIs:

- RPC:
- Provisioning/Device Management:

__Warning__: version 0.8.0 requires changes to applications that used
earlier versions of the provision module. See below for information about
[migrating your applications from 0.7.x to 0.8.0](#migrating-to-080)

Note that this library does not yet support the HTTP Data Interface. See
below for more information.

Supports Python 2.5 through 3.3.

License is BSD, Copyright 2014, Exosite LLC (see LICENSE file)


Install from Python package index:


$ pip install pyonep

Or install from source:


$ git clone
$ cd pyonep
$ python install

Note: If you'd rather not install the package, you can also copy the
./pyonep/pyonep folder into the same folder as your script, or
add the ./pyonep/pyonep folder to your sys.path.

If you're running a version of Python earlier than 2.6 you'll need the
python-simplejson package, available here:

Getting A CIK

Access to the Exosite API requires a Client Identification Key (CIK).
If you're just getting started with the API and have signed up with a
community portal, here's how you can find a CIK:

1.) Log in:

2.) Click on "devices" on the menu on the left

3.) Click on a device to open its properties

4.) The device's CIK is displayed on the left

Once you have a CIK, you can substitute it in the examples below.


Write and read from a device dataport:


from pyonep import onep

o = onep.OnepV1()

cik = 'INSERT_CIK'
dataport_alias = 'INSERT_ALIAS'
val_to_write = '1'

{"alias": dataport_alias},

isok, response =
{'alias': dataport_alias},
{'limit': 1, 'sort': 'desc', 'selection': 'all'})

if isok:
# expect Read back [[1374522992, 1]]
print("Read back %s" % response)
print("Read failed: %s" % response)


Get information about a device:


from pyonep import onep
from pprint import pprint

o = onep.OnepV1()

cik = 'INSERT_CIK'
dataport_alias = 'INSERT_ALIAS'
val_to_write = '1'

# get information about the client
{'alias': ''}))

RPC API documentation:

Buffered Access

The pyonep library includes a module that provides buffered access to the
RPC API, which may offer better performance in some cases.

See examples/read\_write\ for more details.

Example Scripts

Examples are located in [examples/](examples). To run them, first modify them with your
device information.

- [](examples/ - writes to a resource and then reads back

- [](examples/ - gets information about a client, and demonstrates error handling

- [](examples/ - uses the onep module to send

- [](examples/ - demonstrates use of the datastore module

- [](examples/ - demonstrates use of the provisioning API

Note that to run the examples without installing the pyonep package, the
example script must be located in the root folder (with ./pyonep as a

For a Python example that fully exercises the RPC interface using the pyonep
library, see the Exosite command line interface:

General API Information

For more information on the API, see:

HTTP Data Interface

The HTTP Data Interface is a minimal HTTP API best suited to resource-constrained
devices or networks. It is limited to reading and writing data one point at a
time. An example of using Python to access this interface is here:

The API is documented here:

Migration from version 0.3

If you were previously using version 0.3 and want to upgrade to 0.7.4,
you will need to update the package name in your scripts. The package name
was updated from onepv1lib to pyonep. For example:


from onepv1lib import onep

...should be changed to:


from pyonep import onep

A global search and replace of onepv1lib to pyonep in your scripts should

Migrating to 0.8.0

Version 0.8.0 includes some breaking changes to provision module API to provide more consistent return values and error information. To migrate an existing application to pyonep 0.8.0 you will need to make a few changes to the way provision methods are called.

- Previously, methods in provision module either returned a.) `True` (success) or `False` (failure) or b.) `<response body="" string="">` (success) or `None` (failure). HTTP response details (e.g. status code) were not available to the caller without turning on logging and parsing stdout. With 0.8.0 all methods return a `ProvisionResponse` object with the following properties:

- `ProvisionResponse.body` is the response body, a string. The contents of this depend on the specific call, and may be of length 0. See [provision API documentation]( for details.
- `ProvisionResponse.status` is the HTTP status code
- `ProvisionResponse.isok` is a boolean representing whether the call succeeded (i.e. if the status code is < 400)

- Previously all exceptions associated with a call were being caught but not rethrown. With 0.8.0, HTTP exceptions are thrown to the caller. For example, if no connection is available, previously this would have written a message to the log and returned `None`. Now, a subclass of [`HTTPException`]( is thrown to the caller. This allows the caller to take appropriate action based on exactly what happened.

Here's an example of code based pyonep before 0.8.0:
import pyonep
provision = pyonep.Provision('', manage_by_cik=False)

# create a model
response = provision.model_create(vendortoken, model, clonerid, aliases=False)
if not response:
print('Unknown error occurred in model_create')

# list models
model_list = provision.model_list(vendortoken)
if model_list is not None:
print('Unknown error occurred in model_list')

Here's how that would be written to work with 0.8.0+:
import sys
import httplib
import pyonep

# the leading 'http://' is now optional but should be omitted
provision = pyonep.Provision('', manage_by_cik=False)

# create a model
response = provision.model_create(vendortoken, model, clonerid, aliases=False)
if not response.isok:
print('Error in model_create: {0} {1}'.format(response.status(), response.reason()))

# list models
response = provision.model_list(vendortoken)
if response.isok:
print('Error in model_list: {0} {1}'.format(response.status(), response.reason()))
except httplib.HTTPException:
ex = sys.exc_info()[1]
print('HTTPException: {0}'.format(ex))

You can also ask the provision module to raise an exception for HTTP statuses of 400 and above by passing `raise_api_exceptions=True` to the `Provision` constructore. This can consolidate code that handles API errors for a large number of provision calls. See the [provisioning example](examples/ to see how to do this.


0.8.1 (2014-02-11)

- support https, reuseconnection in
- don't log exceptions in, just raise them
- add example of error handling in examples/

0.8.0 (2014-02-05)

- return ProvisionResult from provision methods to provide more
information about success/failure (breaking change)
- refactor to use httplib, and share code with
- make version string available in pyonep.__version__, per PEP 396

0.7.13 (2014-01-31)

- add support for flush options

0.7.12 (2014-01-27)

- use generic RPC address

0.7.11 (2013-12-13)

- support options for listing command

0.7.10 (2013-12-07)

- add support for logging all request JSON

0.7.9 (2013-12-03)

- add support for Python 3.x

0.7.8 (2013-10-28)

- add reuseconnection for performance

0.7.7 (2013-9-26)

- add optional User-Agent string

0.7.6 (2013-8-18)

- improved HTTP logging

0.7.5 (2013-8-12)

- changed provisioning interface to manage by CIK
rather than vendor token by default
- fixed writegroup command
- added example code
- improved documentation

0.7.4 (2013-7-22)

- fixed support for python 2.5
- added example of using directly

0.7.3 (2013-7-19)

- fixed issue with format in python 2.6
- fixed exception messages

0.7.2 (2013-7-19)

- updated provisioning library for api change to use "meta" field
- updated provisioning library to use vendor token by default
- improved logging
- fixed issue record offset is 0 in datastore
- reverted back to using distutils for python 2.6 support

0.7.1 (2013-7-18)

- merge a few bug fixes from Exosite internal repo
- remove comment command
- fix multiple command example

0.7.0 (2013-7-18)

- renamed onepv1lib package to pyonep
- renamed onep_exceptions back to exceptions


- add usage command


- add support for https


- add support for sending multiple commands in a single request


- add provisioning library


- update example code


- initial version  
File Type Py Version Uploaded on Size
pyonep-0.8.1.tar.gz (md5) Source 2014-02-12 19KB
  • Downloads (All Versions):
  • 192 downloads in the last day
  • 1041 downloads in the last week
  • 4741 downloads in the last month