search

bryan-bartow / homebridge-alarm.com

Alarm.com plugin for Homebridge
ISC License
43 stars 11 forks source link

Home app does not communicate with security panel #29

Closed iflore closed 7 years ago

iflore commented 7 years ago

Hi, I think I set up everything as intended - test API calls worked properly with the alarm panel. (Have used the server key from wrapapi.com as the key in the config.json file as instructed.) When I run homebridge in terminal, the security panel icon appears next to homebridge in the home app, along with my nest and myq icons. But when I click on the security panel icon in the home app and try to arm / disarm / press home / night, there is no communication with the panel. I just get a push notice from home app announcing the command i just pressed. however the panel does not react to any of the commands. any assistance appreciated.

here's what terminal shows: [10/3/2016, 2:13:34 PM] [Security Panel] Initializing Alarmdotcom platform... [10/3/2016, 2:13:34 PM] [Error: You did not specify {'token'} or {'clientId','clientSecret','code'}, one set of which is required for the new API] [10/3/2016, 2:13:34 PM] Falling back to legacy API. [10/3/2016, 2:13:34 PM] [MyQ] Logged in with MyQ user ID 0

i think this is the error for myq - which works fine for now.

rest of output from terminal:

[10/3/2016, 2:13:37 PM] [Security Panel] Request iflore/alarmdotcom/lights/0.1.1 was unsuccessful:

[10/3/2016, 2:13:37 PM] Homebridge is running on port 49667.

i think these errors are because i don't have those devices connected to the panel...

appreciate any feedback. many thanks.

bryanbartow commented 7 years ago

@iflore Have you tried logging into the mobile version of the alarm.com site to make sure there aren't any nag screens or dialogs you need to dismiss?

The plugin should work whether or not you have locks and/or lights. I, myself, don't have either and the plugin works just fine.

iflore commented 7 years ago

Yes. There are no issues listed but homebridge is still not communicating with the panel.

Sent from my iPhone

On Oct 4, 2016, at 5:59 AM, Bryan Bartow notifications@github.com wrote:

@iflore Have you tried logging into the mobile version of the alarm.com site to make sure there aren't any nag screens or dialogs you need to dismiss?

The plugin should work whether or not you have locks and/or lights. I, myself, don't have either and the plugin works just fine.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

bryanbartow commented 7 years ago

@iflore This may be a stupid question, but are you sure you supplied the correct alarm.com credentials in the config file?

bryanbartow commented 7 years ago

Pinging @iflore. I'm going to close this if I don't hear back soon.

iflore commented 7 years ago

if you mean my username and login, yes - confirmed the info is correct

iflore commented 7 years ago

here's my config.json file, which is validated:

{ "bridge": { "username": "CC:22:33:E3:CE:30", "name": "Homebridge", "pin": "987-65-432" },

"platforms": [{
    "platform": "Nest",
    "username": "xxx",
    "password": "xxx"
}, {
    "platform": "LiftMaster2",
    "username": "xxx",
    "password": "xxx"
}, {
    "platform": "Alarmdotcom",
    "name": "Security Panel",
    "username": "xxx",
    "password": "xxx",
    "apiKey": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    "apiUsername": "xxx"
}]

}

bryanbartow commented 7 years ago

@iflore I just looked on WrapAPI and it doesn't look like you cloned either of the lights or locks calls. You'll need to clone those calls before the plugin can work, as outlined in the README

Here's a link to the WrapAPI search results page. Yours are at the bottom of page 2.

iflore commented 7 years ago

Thanks. I've cloned all of the calls in the list (even though I don't have lights or locks). But there is still no communication from homebridge to the panel. The test calls work fine, so there must be an error in the way I'm capturing those calls in the wrapapi key. I'm not sure if I did it correctly. What I did was to run each of the tests (initlogin and login first), clone each of the API calls / tests, and then I just generated a new API key. I used that output in the config.json file. I'm guessing this must be wrong?

On Thu, Oct 13, 2016 at 1:58 PM, Bryan Bartow notifications@github.com wrote:

@iflore https://github.com/iflore I just looked on WrapAPI and it doesn't look like you cloned either of the lights or locks calls. You'll need to clone those calls before the plugin can work, as outlined in the README https://github.com/bryanbartow/homebridge-alarm.com/blob/master/README.md

Here's a link to the WrapAPI search results page https://wrapapi.com/#/search?q=alarm.com&page=2&_k=gjn34t. Yours are at the bottom of page 2.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bryanbartow/homebridge-alarm.com/issues/29#issuecomment-253636809, or mute the thread https://github.com/notifications/unsubscribe-auth/AVjlyMZ1PJuyM5mGFZd9QBMk6CVZzxygks5qzptmgaJpZM4KNEMB .

Indy Flore 646.315.3975

bryanbartow commented 7 years ago

It looks now like all of your calls have a 1 appended to their names. That won't work because the plugin is looking for URLs at /username/callname and those call names are hard-coded in the plugin. You could fork the plugin and append a 1 to the call names or you can delete the calls and start over. Make sense?

bryanbartow commented 7 years ago

As an example, look at this line in the plugin: return this.send('login/0.1.0', {

You'll notice it's calling the login URL. Yours won't work because it's login1 and so on and so forth for all the other calls.

iflore commented 7 years ago

Ok. Thanks v much. Makes sense. Any idea how I delete the calls from wrap API?

Sent from my iPhone

On Oct 14, 2016, at 7:06 AM, Bryan Bartow notifications@github.com wrote:

As an example, look at this line in the plugin: return this.send('login/0.1.0', {

You'll notice it's calling the login URL. Yours won't work because it's login1 and so on and so forth for all the other calls.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

bryanbartow commented 7 years ago

@iflore No clue. Never tried, but I would imagine there has to be a way.

iflore commented 7 years ago

Agreed. I couldn’t figure it out. I tried changing the file names - there’s an option to edit and rename but it doesn’t seem to take effect…

On Oct 14, 2016, at 10:49 AM, Bryan Bartow notifications@github.com wrote:

@iflore https://github.com/iflore No clue. Never tried, but I would imagine there has to be a way.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bryanbartow/homebridge-alarm.com/issues/29#issuecomment-253872431, or mute the thread https://github.com/notifications/unsubscribe-auth/AVjlyGEeL-v7BWgBkKidJY9G_iLYi0W2ks5qz8CxgaJpZM4KNEMB.

bryanbartow commented 7 years ago

@iflore In my Endpoints dashboard, I'm able to delete any of my calls. Are you not able to delete yours?

iflore commented 7 years ago

THANKS, CHAMP!! I FINALLY GOT IT TO WORK…!

On Oct 14, 2016, at 11:11 AM, Bryan Bartow notifications@github.com wrote:

@iflore https://github.com/iflore In my Endpoints dashboard, I'm able to delete any of my calls. Are you not able to delete yours?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bryanbartow/homebridge-alarm.com/issues/29#issuecomment-253879398, or mute the thread https://github.com/notifications/unsubscribe-auth/AVjlyIVGisy7upxoGRuw0pPgqUFUtHgyks5qz8XsgaJpZM4KNEMB.