A Python library for interacting with Vivint Sky API.
I own a system by Vivint and was annoyed when I found they didn't post any information about how the API works. After looking over the internet I was able to find a few pieces of information and one gem written by Tim Harper. The homebridge site makes a claim that Tim used to be a Vivint employee which I have no reason to doubt and honestly his work would require some type of inside knowledge to the API.
My intent here was to combine all the work that has been done over the last couple of years and combine them into a working library so I can add an integration to the Home Automation System called Home Assistant (https://www.home-assistant.io/).
Name | Description | Link |
---|---|---|
Tim Harper | Tim released a version for Homebridge with very useful information on how the API works. This served as the main basis for how I wrote the integration. | https://github.com/timcharper/homebridge-vivint |
Reibart | Reibart did a lot work trying to reverse the API via browser calls. I used the information from this project to enhance this one. | https://github.com/Riebart/vivint.py |
Ovirs | Ovirs has some additions he made to Reibart work above and it contains information on other devices. | https://github.com/ovirs/pyvivint |
jhutchins | JHutchins did a homework project using the devices and his site contains some infmormatio on the thermostat API calls. | https://github.com/jhutchins/vivint |
Authentication is handled currently via username and password. I would recommend setting up a user on Vivint for just this purpose. This makes it easy to distinguish when events are coming from automation.
This does direct calls to the Vivint API and stores a session key that last 20 mins by default. I then check for the expiration of this key on each call in the future login again if its expired.
Message states and changes to devices are handled by PubNub. This API subscribes to the panels PubNub channel and is able to handle messages like doors opening and closing.
This is the root device and all child devices are attached to it. Looking at the API its possible for an account to have more than one panel and this makes attempts to handle that.
Feature | Status |
---|---|
Armed State | In Progress |
Update State | Not Implemented Yet |
PubNub | Working |
- Garage tilt sensors
- Glass break sensors
- Medical panic button
- Motion sensor
- Water sensor
- Water sensor heat
- Water sensor freeze
- Window/Door sensors
Sub class of devices sensors. They self identify as wireless. Not necessarily via wifi.
Feature | Status |
---|---|
Name | Working |
State | Working |
PubNub | Working |
I don't own one of these yet but there is enough information on the other sites I think to implement the features.
Feature | Status |
---|---|
Sub class of devices sensors. My locks are on Zigbee not wifi
Feature | Status |
---|---|
Name | Working |
State | Working |
PubNub | Working |
Remote control garage opener
Feature | Status |
---|---|
Water detection and temperatures are combine it to a single additional device calld a sensor_group
Feature | Status |
---|---|
Feature | Status |
---|---|
Name | Working |
Detection | Working |
Feature | Status |
---|---|