Kevo Plus door locks now working in Home Assistant

Got an email today from Kevo about the amount of traffic tied to my account, so this setup might not be the best idea…

Still going strong. I never got a response as to whether the traffic I was generating was excessive, or if they wanted me to increase my scan_interval. It seems they were mainly just checking to ensure it wasn’t an issue with my setup.

Used this guide to install on an hassbian image, change paths to hass to homeassistant. Checked and python2 is installed. Getting SyntaxError: anything I am missing?

    >>> from pykevoplus import Kevo
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/srv/homeassistant/lib/python3.4/site-packages/pykevoplus/__init__.py", line 317
    print repr(kevolock)
             ^

Judging by the error, it’s attempting to run in Python3, which won’t work. Try reinstalling and running the command in the terminal to ensure it’s working.

Tried to reinstall and getting the same error. Executing python2 or course says it can’t find the pykevoplus file.

Don’t want to hijack the thread. I don’t think it is an issue with the script. I think if is me not being able to execute a simple script (completely new HA and python) .

Pi user python is showing version 2.7
Homeassistant user showing python 3.4
Executing $ python in homeassistant is giving me the error as shown earlier
Executing $ python2 is file not being found

Maybe attempt to install python2 on the homeassistant account?

sudo apt-get install python2.7

I’ve updated the library to work in python3 to eliminate the issues your having. I’ll update this post tonight with more details.

I have updated the pykevoplus library written by cseelye to python3. The installation is a bit different as is some of the scripting.

I have hopes that someone will eventually pick up from where I have left off and create a full fledged component for using the pykevoplus library. As it stands now, we have very basic status information, and the ability to lock and unlock the device. There is currently no proper error handling or any ability to alert the user to bolt jams or low battery situations.

These instructions assume that you’re running within a virtual environment on a raspberry pi, so you may have to adjust directories slightly You will need to create additional scripts for each lock. These instructions only cover a single lock named "front door."

1. Install pykevoplus v2.0

$ wget -O pykevoplus_v2.0.tar.gz https://github.com/Bahnburner/pykevoplus/archive/v2.0.tar.gz
$ sudo pip3 install pykevoplus_v2.0.tar.gz

2. Create directories for your scripts

$ mkdir /home/hass/.homeassistant/kevo
$ cd /home/hass/.homeassistant/kevo

3. Get your Lock ID’s

$ python
>>> from pykevoplus import Kevo
>>> locks = Kevo.GetLocks("***USERNAME***", "***PASSWORD***")
>>> for lock in locks:
...    print(repr(lock))
...

Output

KevoLock(name=Front Door, id=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, state=Locked)

We will be using the lock ID returned from that command in the following scripts

4. Create the following files in /home/hass/.homeassistant/kevo
status-front.py

from pykevoplus import KevoLock
lock = KevoLock.FromLockID("xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "***USERNAME***", "***PASSWORD***")
print(lock.GetBoltState())

lock-front.py

from pykevoplus import KevoLock
lock = KevoLock.FromLockID("xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "***USERNAME***", "***PASSWORD***")
lock.Lock()
print(lock.GetBoltState())

unlock-front.py

from pykevoplus import KevoLock
lock = KevoLock.FromLockID("xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "***USERNAME***", "***PASSWORD***")
lock.Unlock()
print(lock.GetBoltState())

5. Fix permissions

$ chmod 755 -R ./

6. Add the switch to your configuration.yaml

- platform: command_line
  scan_interval: 30
  switches:
    door_front:
      command_on: "python3 /home/hass/.homeassistant/kevo/lock-front.py"
      command_off: "python3 /home/hass/.homeassistant/kevo/unlock-front.py"
      command_state: "python3 /home/hass/.homeassistant/kevo/status-front.py"
      value_template: >
        {% if value == "Locked" %}
          true
        {% elif value == "Unlocked" %}
          false
        {% else %}
        {% endif %}

Why not turn this into an official HA component? Have you reached out to the HA core team to see if this is something they would allow a PR for?

I’m on the market for a smart lock now, and would only go the BT (Kevo) route if I could get it working with HA and have “One-Touch” unlock. Having to pull out the phone and open an app, or manually entering in a code just seems old school to me. Might as well just pull out yer key.

Sounds like this Kevo/HA integration is still very much a shim with limited functionality.

I don’t have enough knowledge of python to migrate this to a full HA component. I’ve asked a few other devs if they would like to take on the project, but without a device to test on, none were willing to help.

I’ve gone ahead and created a custom component and it all seems to work on my own setup. If you get your python3 version of pykevoplus onto PyPI, then my custom component can be fully released and potentially turned into a full official component.

2 Likes

Holy crap. THANK YOU!

Let me work on that.

Done.

Uploaded as pykevocontrol, but the package still installs as pykevoplus to ensure there’s no changes needed to scripting.

I’m actually running into issues getting it to install your version of the package as a dependency. Once I get this figured out, I’ll throw it on github and let you play with it.

Interesting. Do you think it’s a issue with the new and old version sharing a package name? I can always change the entire project to pykevocontrol and reupload if it helps.

I tested on a fresh venv before uploading to pypi and had no issues installing or checking the status of my locks.

I don’t think it’s an issue on your part. For some reason, my home assistant install is not installing the dependency. I’ve gone and uploaded my latest version to github here. If you throw that kevo.py into your home assistant environment at CONFIG_DIRECTORY/custom_components/lock, you can then add

lock:
  platform: kevo
  email: [email protected]
  password: xxxxxxxx

to your configuration.yaml and you should be ready to roll.

Let me know how it works for you and if you run into any issues.

Just reuploaded a new commit of the custom component where I’ve fixed my stupid mistake. Let me know if you get a chance to try it.

I’ll be in installing it as soon as I get home. I was out with the wife running errands.

Working well so far.

Great. I’m going to put together what I need to submit this as a pull request so that it can be an official component included in a future HA release.

1 Like