HoneyWell AlarmServer on GitHub

[MattTW]

Yeah it is not obvious, but the root URL on the server does nothing but return that error you see. To run the app go to /app (note that per the readme in the github project the page will come back but it not currently working). Best call to make to see the current state is /api which will return a large json string for the state of the system including each zone.

For integrating with OpenHab, you will want to look at the plugin examples that have been written. Basically there are functions that get called for different system events, you implement the functions where you want to do something. One of the examples should give you a good start.

Matt

[rogerjbos]

Maybe someone can help me figure out how to use the REST API to access the HoneyAlarmServer. I have it installed and configured and when I run it the output.log file shows that it is connected to the envisalink, but I don't understand how to use the REST API. The IP address of my HoneyAlarmServer is 192.168.1.104, so if I use 192.168.1.104/api in the browser I should see a long json string, correct? I get an "Unable to connect" message.

Here is the output.log file which seems to look okay to me:

Sun, 29 Nov 2015 19:06:03 INFO <root alarmserver <module>> Alarm Server Starting
Sun, 29 Nov 2015 19:06:03 INFO <root alarmserver <module>> Currently Supporting Envisalink 2DS/3 only
Sun, 29 Nov 2015 19:06:03 INFO <root alarmserver <module>> Tested on a Honeywell Vista 15p + EVL-3
Sun, 29 Nov 2015 19:06:03 INFO <twisted log emit> Starting factory <__main__.EnvisalinkClientFactory instance at 0x76361260>
Sun, 29 Nov 2015 19:06:03 DEBUG <root alarmserver startedConnecting> Started to connect to Envisalink...
Sun, 29 Nov 2015 19:06:03 INFO <twisted log emit> Site starting on 8111
Sun, 29 Nov 2015 19:06:03 INFO <twisted log emit> Starting factory <twisted.web.server.Site instance at 0x76361378>
Sun, 29 Nov 2015 19:06:03 DEBUG <root alarmserver buildProtocol> TCP connection estblished to 192.168.1.142:4025
Sun, 29 Nov 2015 19:06:03 DEBUG <root alarmserver buildProtocol> resetting connection delay
Sun, 29 Nov 2015 19:06:03 DEBUG <root basePlugin look_for_subclass> searching plugins.basePlugin
Sun, 29 Nov 2015 19:06:03 INFO <root alarmserver connectionMade> Connected to 192.168.1.142:4025
Sun, 29 Nov 2015 19:06:03 DEBUG <root alarmserver lineReceived> ----------------------------------------
Sun, 29 Nov 2015 19:06:03 DEBUG <root alarmserver lineReceived> RX < Login:
Sun, 29 Nov 2015 19:06:03 DEBUG <root alarmserver send_data> TX > xxxxxx
Sun, 29 Nov 2015 19:06:03 DEBUG <root alarmserver lineReceived> ----------------------------------------
Sun, 29 Nov 2015 19:06:03 DEBUG <root alarmserver lineReceived> ----------------------------------------
Sun, 29 Nov 2015 19:06:03 DEBUG <root alarmserver lineReceived> RX < OK
Sun, 29 Nov 2015 19:06:03 INFO <root alarmserver handle_login_success> Password accepted, session created
Sun, 29 Nov 2015 19:06:03 DEBUG <root alarmserver lineReceived> ----------------------------------------
Sun, 29 Nov 2015 19:06:05 DEBUG <root alarmserver lineReceived> ----------------------------------------
Sun, 29 Nov 2015 19:06:05 DEBUG <root alarmserver lineReceived> RX < %00,01,1C28,08,00, DISARMED CHIME Ready to Arm $
Sun, 29 Nov 2015 19:06:05 DEBUG <root alarmserver lineReceived> ----------------------------------------
Sun, 29 Nov 2015 19:06:06 INFO <twisted log emit> Received SIGINT, shutting down.
Sun, 29 Nov 2015 19:06:06 DEBUG <root alarmserver shutdownEvent> Shutting down AlarmServer...
Sun, 29 Nov 2015 19:06:06 DEBUG <root alarmserver shutdownEvent> Disconnecting from Envisalink...
Sun, 29 Nov 2015 19:06:06 INFO <twisted log emit> Stopping factory <__main__.EnvisalinkClientFactory instance at 0x76361260>
Sun, 29 Nov 2015 19:06:06 INFO <twisted log emit> Main loop terminated.

[MattTW]

By default the server listens on port 8111. So you would want to do 192.168.1.104:8111/api

[rogerjbos]

Matt,

That worked. Thanks for contributing this software.

Thanks agian,

Roger

[neo]

Sorry for reviving this thread. I just found this app and thanks to the developer(s).

One question, was the proxy removed from the honeywell version? I've tried enabling it in the config but it never listens on any specified port. It'd be great if this were working as it'd give the option of both vera and siri at the same time rather than one or the other.

Thanks