New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mykevo now has captcha #17
Comments
yeah just saw this too. There are application for other systems that are going to break too. Hopefully kēvo will provide an api. Still surprise they don’t have one already |
I’m having the same problem. Hasn’t worked for days, logged into my pi to find “Error submitting login page: Error: bad status code 422” |
Guessing this is related :(
|
Hello this started for me this afternoon, this is what mine is showing ... it is also causing home bridge to shut itself down TypeError: Cannot read property 'statusCode' of undefined |
Same here... stopped working <12 hours ago with the same TLS socket error:
|
ditto on that |
I am new to this coding thing so I am asking all of the more experienced users here .. Is there any way to just be able to modify the plug in so it can mark the checkbox of the captcha when logging into the site? Thanks |
Well, seeing as captcha is designed and implemented specifically to prevent that I would say no;) |
@JKaya Ok Thanks! That's what I was afraid of. So is all hope lost in ever getting this lock to work with homekit and Siri again. |
Call kevo and complain. If enough people do it, maybe they will actually build a real api. Or more likely sell an add on to replace homebridge. What’s really annoying me is they released a new lock with apple HomeKit built in right around the time they started adding the captcha. Now it could be a coincidence, or the new product making them be more secure, but it could be there way of pushing the new lock |
@pmeisel123 I just called Kwikset to voice my concern and complain the rep also transferred me to an upper tier technical support and I had a conversation with them as well ... everyone here does need to call and wait on hold the hold time is bad!! I was on hold for 10min before someone answered ... but if you explain to the Kēvo rep and then get them to get you to a higher tech support they will listen ... and also please everyone here go to the kwikset portal on their website and voice a concern there and they may do something ... but we have to all make some noise for either full support or a Siri shortcut which could be added to the my Kēvo app |
I called in and opened a ticket as well, they said give the engineers a few weeks to look into it and I could call back on the case to see if there was any movement. Hopefully they can address or give us a true API to consume. |
I just started getting the same In the meantime, I've made a copy of my Homebridge config.json file and removed the part dealing with Kevo so that Homebridge can run properly:
|
I just gave up on them doing this the right way and bough the Schlage with HomeKit built in. It’s soooooo much faster and more reliable than the Kēvo setup was. Still holding out hope here though for the Kēvo for another door. |
@msaraceno Thank You for calling, @notasausage Please call and voice your concern and try to get to a level 2 tech support person and voice your concern there too, when I spoke to the tech person they said they would get it over to the app dev team ... so again the more people that call in and voice a concern the better... |
@bondjw07 I have put a premis on my front door but my kevo I had hooked up to my security gate/screendoor ... I'm going to try and put this on I just ordered it the Vocolinc Smart lock with HomeKit should be here tomorrow it has the Kwikset type of keys so I'm hoping to re-key it and at $129 I wish it would've been available when I bought my Premis ... |
As of Thursday night, the error disappeared for me and it’s been working. |
Yep, working for me now too. Thanks for the heads up! |
Working here too... as the web page still prompts for captcha they probably had a web developer filter the HTTP header for whatever User-Agent Homebridge/NPM declares and setup an exception.. awesome;) |
If there is a way for automatic script to bypass the captcha, doesn't that defeat the purpose of a captcha? Either way it is cool that it is working for people. I tried to log in remotely to my raspberry pi that runs homebridge, but apparently it went offline sometime last night, I will test this when I get home tonight.
|
Patience got the better of me and I broke down and updated to a Premis lock this past Monday. The good thing is they were able to address the issue. |
Works for me now, guess telling people to call in and complain worked. |
I've updated homebridge and homebridge-kevo and restarted, but I still get the bad status code 200 error. My account had been locked, but I called and got it unlocked, and I'm able to log in through mykevo.com. Was there something else I was supposed to do? |
@thomasqbrady FYI there was no update the homebridge-kevo. The fix was on kevo's website Couple of suggestions:
|
That's the weird thing. I don't get 500s… I get 200s (which shouldn't be a "bad" status code, right?).
|
hmm, interesting. Apparently you are getting a 200 after login, when you should get a redirect (302) after login. If you login is invalid they return a 200 instead of a 401. The bad news is that the captcha causes this problem. The good news is I suspect/hope you made a really simple easy to make mistake. When you account was locked I am betting they made you change your password, but since homebridge-kevo was broken you didn’t update your password stored in the config.json file. |
I did update the password, unfortunately, so that’s not it. How is this login happening? Are you using something like phantom to simulate a browser session? If so, could this be a cache issue (cookies or even HTML/javascript that’s cached)? |
It uses node.js to make an ajax call. It does store cookies in memory, but only after you are logged in, and that is all cleared after you restart homebridge. You can try going to /usr/local/lib/node_modules/homebridge-kevo/index.js (line 101) and add a console.log to have it print your user name and password. Maybe it is using a different config.json? you can also have it log the html of the page. Then you can look at the source and see the error. It might be that you are an exception who is still getting screwed by that captcha. With out seeing the response it is hard to tell if it is a username/password error vs a captcha error |
@thomasqbrady, did it ever start working for you? It does not work for me still, but I'm able to login with the same user/password in Safari. |
It did not. |
It's back to a 200 on both now. Here's the log of what I get in the body: |
Kevo, Kwikset are currently owned by Spectrum Brands, Madison WI USA. Feel free to hit up their support site, but maybe more effectively, https://twitter.com/KwiksetCorp to ask about a pseudo-random crypto hash as an API token to connect and manipulate locks via an API. If we ask for the same thing, across many media, and offer to help (in the US: 1099 $1 consultant willing to sign NDAs) they might accept some modernization of their system. |
Just started seeing this error again. What’s interesting when I signed into mykevo.com on my phone with the same account I stopped seeing this issue. I’m currently waiting to see what happens if I login and just timeout |
Made some changes, things seem to be working better now: Some suggestions:
|
Good News/Annoying News/Bad News/Question Good News: Annoying News Part I: Annoying News Part II: Bad News Part I: Bad News Part II: Question: |
Another option would be to copy the cookie contents from the desktop PC to homebridge however that would require additional development to this module (not much though as I believe it already implements session cookies) |
That could be tricky, because you would regularly need to copy the cookies over. One thing I left out of my above note (I just updated it), is that sessions do timeout. You should log in with a browser at least once a week to prevent issues. There is probably a good way to copy cookies automatically from your browser into homebridge, though I don't know it. Though you are right that is probably the long term solution |
Have there been any non-workaround updates to this since last September? I'm new to Homebridge, and am having this problem. |
Honestly I still surprised the work around work at all. Though while it does I just login via the website every few weeks. It should work as long as you don't log out from the website (just close the browser window/tab). BTW my original note said you needed to be logged in from the same network that isn't true. The real problem is if you fail the captcha too many times you account gets locked. It looks like now if you disable homebridge for a few minutes, then login via the website, your account will be unlocked. |
Is the workaround of logging in via browser still the way to make this work? thx |
I haven't found a way to make that work |
Yes. I’ve found as long as you don’t log out from the browser it works. I’ve also tweaked the code of my local copy to retry a few times after failure. I’ll post my changes when I have a chance |
Would you be able to share your code changes please @pmeisel123 |
2nd! |
@pmeisel123 @fab301s @SemoTech I actually have a fork that does a retry as well, unfortunately it has been years since I looked at it and I'm not even confident it still works. I just installed homebridge on a new RPi image so I no longer have the changes I did on my local. I may try to pick this back up but any work you have done @pmeisel123 would be great to see. |
@Tiger519, I'm getting an Unexpected status code 401, rather than a |
For the error make sure to login to kevo with your browser, and then close the browser window without logging out. I did try to make a platform version of this code, that would do one call to get the status of all the devices, but my knowledge of writting a homebridge app from scratch is very limited, and I quickly got stuck. And then the raspberry pi I was building it on got water damaged, and I lost my code. -- For my tweaks to the code, it has been a while since I have worked on this. But this is my index.js file now. I can't remember if I modified any other file The big change was adding KevoAccessory.prototype.multirequest and then using that all over the code
|
You're still getting a 401? That's definitely an authentication issue. I'll try to look into this a bit when I have time. |
This is what I get if I enable the plugin (v0.0.3):
Lock is most certainly Locked! |
The plugin stopped working this morning. When I log in to mykevo manually, I'm presented with a captcha. I'm afraid this may mean the death of this means of getting Kevo Plus to work. The plugin reports this:
Jun 06 09:04:52 raspberrypi homebridge[21315]: [06/06/2019, 09:04:52] [HK Front Door] Error submitting login page: Error: Bad status code 200
Jun 06 09:04:52 raspberrypi homebridge[21315]: [06/06/2019, 09:04:52] [HK Front Door] There was a problem logging into Kevo. Check your username and password.
Any hope of a fix?
Thanks,
Benjamin
The text was updated successfully, but these errors were encountered: