Skip to main content

Unofficial Python bindings and helpers for the unpublished Cozify API.

Project description

Unofficial Python3 API bindings for the (unpublished) Cozify API. Includes high-level helpers for easier use of the APIs, for example an automatic authentication flow, and low-level 1:1 API functions.


The recommended way is to install from PyPi:

sudo -H pip3 install cozify

or clone the master branch of this repo (master stays at current release) and:

sudo python3 install

To develop python-cozify clone the devel branch and submit pull requests against the devel branch. New releases are cut from the devel branch as needed.

Basic usage

These are merely some simple examples, for the full documentation see:

read devices, extract multisensor data

from cozify import hub, multisensor
devices = hub.getDevices()

only authenticate

from cozify import cloud
# authenticate() is interactive and usually triggered automatically
# authentication data is stored in ~/.config/python-cozify/python-cozify.cfg

authenticate with a non-default state storage

from cozify import cloud, config
# authentication and other useful data is now stored in the defined location instead of ~/.config/python-cozify/python-cozify.cfg
# you could also use the environment variable XDG_CONFIG_HOME to override where config files are stored

Keeping authentication valid

If the cloud token expires, the only option to get a new one is an interactive prompt for an OTP. Since most applications will want to avoid that as much as possible there are a few tips to keep a valid token alive. At the time of writing tokens are valid for 28 days during which they can be seamlessly refreshed.

In most cases it isn’t necessary to directly call cloud.refresh() if you’re already using to test token validity. will also perform a refresh check after a successful ping unless explicitly told not to do so.

To refresh a token you can call as often as you want:


By default keys older than a day will be re-requested and otherwise no refresh is performed. The refresh can be forced:


And the expiry duration can be altered (also when calling

# or, expiry=datetime.timedelta(days=20))


pytest is used for unit tests. Test coverage is still quite spotty and under active development. Certain tests are marked as “live” tests and require an active authentication state and a real hub to query against. Live tests are non-destructive.

During development you can run the test suite right from the source directory:

pytest -v cozify/
# or include the live tests as well:
pytest -v cozify/ --live

To run the test suite on an already installed python-cozify:

pytest -v --pyargs cozify
# or including live tests:
pytest -v --pyargs cozify --live

Current limitations

  • Token functionality is sanity-checked up to a point and renewal is attempted. This however is new code and may not be perfect.
  • For now there are only read calls. New API call requests are welcome as issues or pull requests!
  • authentication flow is as automatic as possible but if the Cozify Cloud token expires we can’t help but request it and ask it to be entered. If you are running a daemon that requires authentication and your cloud token expires, run just the authenticate() flow in an interactive terminal and then restart your daemon.

Sample projects

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for cozify, version 0.2.10
Filename, size File type Python version Upload date Hashes
Filename, size cozify-0.2.10.tar.gz (15.5 kB) File type Source Python version None Upload date Hashes View

Supported by

Pingdom Pingdom Monitoring Google Google Object Storage and Download Analytics Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page