homebridge-alarm.com
homebridge-alarm.com copied to clipboard
bryan-bartow
Authentication failing from homebridge but appears to log on alarm.com
This morning I noticed that Home.app is showing "no response" errors for the Alarm.com integration that was working fine just a day or two ago. homebridge is reporting:
[2/26/2018, 9:52:04 AM] [Security Panel] Request djstarr/alarmdotcom/login/0.1.3 was unsuccessful:
- None of the output scenarios matched. See the raw data received in rawData
Yet on alarm.com it shows a successful login.
It appears that the wrapapi endpoints were modified a day or two ago. Is it possible that something regressed?
Confirming that this was working last night, but getting the same errors this morning.
I observed the same issue this morning. Login via the webpage or iOS app works just fine. I know that homebridge implementation worked fine yesterday.
So, I've found that if you go to alarm.com/pda/ and check the box "Keep me logged in" you get bumped to a new login page "https://www.alarm.com/login?m=no_session" but you can log in if you do not check the box. I am wondering if this is part of the issue at the moment?
I'm also seeing no response. The APIs show last modified 2 days ago but, as far as I know, nothing was actually changed. Not to mention it was working fine last night. The change must've been on alarm.com's side.
I noticed the change, researched it briefly and it looks like to me that the wrapapi endpoints are looking for different URLs from alarm.com. The may have updated the site?
When logging into the Alarm.com website this morning I found that a new dashboard has been implemented. Did a bit of investigation to find out the differences but WrapAPI is new to me and learning while doing.
Having the same issue. Armed fine last night but as of this morning it’s not working.
Same issue for me too. The alarm.com app and web interface are working fine, it’s just Homebridge/the Home app that aren’t working as of this morning.
Still seeing the same thing. Tried the Keep Me logged in toggle, but still get the same error.
So I did try to go over to alarm.com/pda, when I used to log in with my web browser, I would get the text only version of the alarm.com website. Now if i log in, its giving me the rich web app.. :(
Perhaps something that can be fixed with user agent trickery?
D★
On Feb 27, 2018, at 2:19 PM, Joe Williams [email protected] wrote:
So I did try to go over to alarm.com/pda, and if I logged in with my web browser, I would get the text only version of the alarm.com website. Now if i log in, its giving me the rich web app.. :(
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
I'm laid up sick in bed and will be traveling soon. I can't troubleshoot this but I can probably merge in a pull request and publish a new version if someone can narrow this down.
I made some changes and published version 0.7.4 which points to the latest API version rather than an explicit number. That should make it easier to troubleshoot by changing just the WrapAPI definition.
I fiddled with it a bit and it might have to do with how the WrapAPI login entry defines the success scenario. It looks for armingPanel and alarmState but they aren't being returned anymore, hence the "None of the output scenarios matched. See the raw data received in rawData"
I just confirmed my theory by making the success criteria optional and it started working. Now I just need to figure out what can be used as success criteria.
While I'm figuring that out, you can all just upgrade the plugin to 0.7.4 and switch your login alias to point to https://wrapapi.com/api/jdshkolnik/alarmdotcom/login/latest
I bumped the plugin to v1.0.0 since it's a bit old to be considered a pre-release.
@jdshkolnik Thanks for the quick work. Mine is working again. I updated the plugin, deleted the old "login" API, replaced it with your new link above and restarted homebridge.
Much appreciated!
D★
On Feb 27, 2018, at 9:59 PM, Andrew Vavricek [email protected] wrote:
Thanks for the quick work!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
Working perfectly now. Thank you so much for resolving this as quickly as you did. Hope you feel better soon.
Back in operation, thanks for your quick diagnosis and update!
Noted that the plugin is v0.0.1 rather than v1.0.0 as you noted in your previous post.
Thanks @jdshkolnik for jumping in on this. Hope you feel better real soon.
Sorry for the silly question - where do you update your login alias to point to https://wrapapi.com/api/jdshkolnik/alarmdotcom/login/latest? I've updated the code successfully, just not sure where I do this second step.
@DMBlakeley The plugin 1.0.0, the login API is 0.01.
@kpdillon Delete the login alias from here then go to the above URL and bookmark it.