I just changed the device handler lines of code given just above by @tweason and it works again!
This is a device handler I wish would stay working. I love this one! Thanks so much!
I just changed the device handler lines of code given just above by @tweason and it works again!
This is a device handler I wish would stay working. I love this one! Thanks so much!
When the /user/remote_locks/command/lock.json is called to get the status of my lock I get an internal server error response. I suspect when you end up getting logged out youâre going to have the same error.
Now when I look at the response body after calling /signin and it says my recaptcha is invalid.
I never had any âinvalid recaptchaâ errors. I only had login errors. Over the past week, I have had the âjammedâ problem a couple times, but when it was happening there were also problems with the mykevo website. So far other than the initial issues that started in July, my locks have been working pretty well. They have been automatically unlocking when my phoneâs presence is detected and locking when I tell my google assistant to lock them through an IFTTT command. Have you changed your code in any way other than updating the URL?
I have not changed anything other than the lines of code I listed above and only by adding the WWW
Mine appears to have been working fine since then.
Good afternoon, I have installed the Device Handler and changed the URL to be the https:\www.mykevo.com and I am still getting a status of âJammedâ, any suggestions? Thanks in advance.
The âJammedâ status results whenever the device handler isnât connecting to the website. I would start by double checking your log in credentials and Lock ID in the device preferences.
Is the lock IF the name of the lock?
I found it. I had the wrong ID m. Thank you very much!
So, I read this thread on getting this to work, but as a newbie Iâm completely lost here. Hate to pull up a thread from a year ago but Iâm interested in getting this to work. Can someone put together a step by step tutorial for the process to get this set up?
Hi Kevo folks, Kevo sent me a survey today which I answered with negative opinions stating firmly of their need for an open developers API.
Please feel free to provide similar feedback to them.
Newbie here. I am following the instructions on the github page to create a device.
The âtypeâ list doesnât show âKB: Kevo plus lockâ or âKeevo unofficialâ. I have scrolled up and down and looked at each line. Any idea?
Not going to happen. The driver and app are obsolete.
Thanks for responding. I am fine with it being an unsupported best effort solution but does not going to happen mean that it will not be available to use at all?