EyezOn Forum

Yes you did answer your own question. If there are any contact numbers programmed into the panel it will try and call them and if it doesn't succeed, you will get a FTC (fail to communicate) error. As well, if TLM is programmed (Telephone Line Monitoring), will will generate a trouble on that too. Y...

Unfortunately no. There is no external expansion bus on the Alexor, nor the Impassa self-contained systems, so the Envisalink module cannot work with them.

Yes this can be done, it is just nobody ever asked before.

I'll put it on the to-do list, strange as it may be ...

I saw a beta of this working about two years ago, so it is obviously feasible. You can see that Envisacor has put a PC-LINK header on the '2DS (IP170D), but they are calling it an expansion port now. So I guess that's a solid "maybe in the future".

It's a bug in 1.4.X, it is trying to contact a secondary server that isn't defined. It is fixed in the upcoming 1.5.X release.

Yes, all the Envisalinks work with the PC1555. It will not work with the older PC1550 series that DSC called "Classic".

I'm personally hoping to see more Android and iPhone apps coming out now that Envisacor has released the local API for beta testing. Any developer can now control/access their security system directly over IP using the Envisalink 2DS.

The response from Envisacor is always that the local web interface will be a low priority compared to adding features like the brand new third-party-interface (TPI) that is now in beta testing (see my post on this board). The local web page should be thought of as a nice thing to have, but it is not...

We'll add this to the "To-Do" list.

You can change the partition name now, under the partition tab in your account, but it doesn't seem to carry over to the log.

The IT-100 is based on the PC5401. The IP5401 will be very close (if not the same) to the IT-100 command set.

If you know of any HA developers who may be interested in the trying out this third-party interface (TPI), let them know.