EyezOn Forum

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

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 ...

Yeah the Web UI is only half working at best. The type of data that the Honeywell/Ademco alarm can provide isn't really compatible with what was originally created for the DSC version of the Web UI. So some basic rework is necessary in what/how info is shown in the UI. I have started making updates ...

You can do SSL if you create and set up the server keys correctly, it is documented in the project readme. That is how I have it for my setup. Which brings up a good point, that is another value add of this kind of solution, contrast this with the "native" TPI interface that isn't encrypted at all ...

Thanks for the reply K-man. How does one become a registered developer? If that is in these forums anywhere, then I missed it. I will see if I can capture a couple of the bugs I mentioned. I do have debug info at the app level which shows the issues, I will set up a packet sniffer and see what is ...

Hi - I have created an alarm server app for Ademco/Honeywell alarm systems that use Envisalink. It is a GitHub project that is based on the DSC AlarmServer project that is also on Github that was written by others. The APIs between the DSC And Honeywell/Ademco versions are so different that it did ...

Since you asked, K-Man, I have a few thoughts about the Ademco version of the TPI: - As I think others have pointed out on this forum, the %01 zone state change event seems buggy. You indicated it is based on keypad "Fault" messages, but even assuming that some zone state changes could be missed ...