It looks like you were right 
A user canāt apparently be logged twice (once in HA, and once in the mobile app) on kevoās serviceā¦
Cheers!
Thats why i created a new user in the Kevo App, that way i can have my phone logged in en HA logged in at the same time.
2 Likes
Is this project dead? I looked at the github and it does not look good. Just want to confirm before I buy some Kevo Locks
I gave up on use pyKevo a while ago. I have a Baldwin Evolved lock (same as Kevo) and it looks great and (as of more recently) been working better with the historically VERY buggy Kevo app. They do have a fully supported Alexa integration and I took advantage of that as it doesnāt appear Kevo will ever have a developer accessible API.
For HA, the way I get my lock to work consistently is by using a stable but convoluted workaround.
- I created a virtual Alexa device w/Amazon as a developer
- I then wrote a bash script that gets the authorization tokens from my Amazon account, uploads a prerecorded wav and stores the response. HA evokes the shell script via the shell command configuration integration.
Since the responses from Alexa are always the same, I could use a hash of the downloaded response to get the door status and update a custom sensor or switch but I havenāt done that - I honestly donāt worry about my door being locked/unlocked since we always naturally lock it after we get home.
The reason I did all this is so when I say āAlexa, Good Nightā HA is able to evoke a silent Alexa command to lock my door and when the household enters away mode HA will evoke the same lock command.
Now with all that said, I implemented all this before Alexa had routines - if I was to do it again today, I would create a āgood nightā routine in Alexa, have it tell Kevo to lock the side door and then have it evoke a HA script or automation - that would be a lot simpler but not as integrated.
If what you are looking for is a lock that will always report its status to HA, is natively controlled via HA, and always just works with HA then I would avoid anything Kevo - they arenāt developer friendly. I would look into a Schlage or a Kwikset z-wave lock - those locks will work natively with HA and will never depend on a company supported API that can disappear at any moment (e.g., Google Nest).
I sometimes wish I had gotten a nice z-wave lock but for us, not having a keypad on the outside was a priority because we live in an older style house and didnāt want to take away from the historic nature of the property. However, if you can live with a keypad on the outside of your door then I highly recommend the z-wave route.
I appreciate the effort but dont see the benefits. Ive been using pyKevo for over a year now without issue and it correctly reports states.
Is the pyKevo project local or does it require the kevo cloud endpoints?
Trying to keep all my smart home stuff local
pyKevo logs into the mykevo.com website with your credentials to pull the lock status and issue any lock/unlock commands. It is not local and can be blocked by Kevo or break if Kevo updates their website or if Kevo was to shutdown. There is no way to control the Kevo lock natively/locally even though it works over Bluetooth.
I havenāt used pyKevo in a while so it might be more stable now and/or perhaps Kevo has stopped updating their service as much so that could contribute to stability.
Local is the way to go. My garage doors use the MyQ service and they are buggy - they fall off HA (requiring restarts) and MyQ modifies their API every few months which breaks the pymyq integration and needs to be updated - it is just annoying.
Thanks for the reply. I might just have to wait until a lock like this can be local to my network.
Hi Will,
Really interesting.
Iām trying to find a way to connect my Weiser Halo (Kwikset 939) to HA. Since the Halo is a WiFi only lock and supports both Google Assistant and Alexa Iām thinking that I could probably leverage your Alexa developer workaround. Since Iām fairly new to the Alexa Developer woud you be able to share more details on how did youo create your virtual device and share your bash script so I can try to adjust it for Weiser Halo lock.
Thanks again!
Iād be glad to share that information. Iāll start working on a write up and will share it in a new post to the forum.
1 Like
Guess this is a bit late but just moved into a house with a Baldwin Evolved Lock and Kevo Plus bridgeā¦ This method is working great when I ssh and run the python scripts manually but no luck when adding to configuration.yaml (Command failed: python3). Installed hass directly on a rp4 - not sure if iām looking at a python config issue or if its failing because of the import in the script. Any idea what iām missing?
I avoided myQ on purpose even though my openers have the option for MyQ bridge or whatever they call it. On the not so important door that leads into the backyard I have the refoss/meross (non-homekit) opener and works with Smartthings (added to home app with homebridge/HOOBS). For the main door they sent me the same one but homekit version to try and works flawlessly.
Not loving how my Kevo locks are integrated with HOOBS (partly probably due to the bluetooth to kevo plus hub communication) - also read one thread saying any more than just a single kevo deadbolt can throw it off (HOOBS is always sending kevo errors - but never seemed to harm the bridge service until a recent HOOBS update but may have been caused but another plugin) For the moment I only have the front door added through HOOBS and removed my other 3 locks from the plugin and seems to working fine. On another note i have two kevo plus hubs (one in main house, other in detached garage) and they donāt seem to play well together even though I asked Kevo support first before trying. Seems like only one can be online at a time.
Keeping an eye on this for trying Kevo with Home Assistant instead of HOOBS and also waiting to hopefully see that the Ecobee switch+ API is added to the main ecobee integration.
Cheers and happy smart homing.
Hi Kevo folks, Kevo sent me a survey today which I answered in the negative stating their need for an API
Please feel free to provide similar feedback to them.
2 Likes
Filled it up!
1 Like
So to revive an old threadā¦
I have been fighting this for 2 days and I think I have something that works for me a lot more reliably. The custom components linked in this thread work but they are SUPER finicky. I have 2 locks and I constantly got the 500 error and the status never worked. If I managed to get the locks to actuate theyād immediately die after.
Prior to Home Assistant I had the locks in my HomeBridge and Apple Home with relatively few issues. The HomeBridge plugin works a lot better for some reason but when you try and add it to Home Assistant it lacks a serial number so if you have multiple locks only one will be added. I have added a serial number field to the HomeBridge plugin so that each lock is now āuniqueā and will be added.
For now you have to manually install this in Home Bridge until I figure out how to publish or the author accepts my pull request.
Just FYI Iām in the process of fixing this custom component
2 Likes
That is great news. I assume it will be available under HACS when youāre done?
Will there be support for multiple locks?
Will the locks have a unique ID in HA so they can be better managed through the GUI?
I have multiple Kevo locks and I have a ādevelopmentā HA instance running. So if you need someone to test, Iām more than happy to help.
Not sure to be honest, Iāve been having tons of problems with my Kevo locks as of late. Iāve been looking at Level Lock+ as an alternative. havenāt made a decision yet.
I have six Kevo locks. The main reason why I went the Kevo route was because the existing locks were already Kwikset locks. So one key still works for all doors. A couple of the doors the handle also has a lock as well as a deadbolt. So with both being Kwikset, it still allows for a single key.
Gladly buy you a beer if you get this working 