DSC Will Not Respond

Plugins & Plugin Development DSC Alarm System
1

Ok I can’t make this work. I have tried several times and read this forum to whits end… Can I get a little help please?? I keep having this LUA error and it will not function. I have uninstalled, rebooted and reloaded. Followed the instructions from this forum.

What am I missing? See pics as well.

Here is my config;

DSC PS1616
Veralite FW: 1.6.641 SIP 192.168.1.127
EVL3 FW: 01.11.128 SIP 192.168.1.107

Thanks for whatever help you can give!!!

2

Did you change the EVL password?

3

If you have refer to http://forum.micasaverde.com/index.php?topic=12919.msg95241#msg95241

4

It is still the default “user”

The EVL shows the TPI online.

5

So it seems that the real problem might be with the DSC panel and its settings? It seems that the plugin is connecting but the DSC is not accepting the commands. Was there any info on what might need to be set on the DSC panel??

Thanks

6

Nil with the panel. There are a few additional setting in the Vera. See DSC Alarm Panel

7

Thanks I will see what I can come up with.

8

Does it matter what version of DSC PC1616 I have? I know my system is at least 8-9 years old.

9

Yes, if it is that old, it is probably the early model.

If you goes through the evisalink site, do you see the zones updating? This would be my starting point, is the evisalink communicating with the panel correctly

10

This seems to be working properly. see pic

11

We need the logs that contains the error message to establish the underlying issue.

12

The problem is not the version of DSC panel it is.

Panel Compatibility
DSC PowerSeries (1555, 1555 MX, 1575, 5010 (832), 5020 (864), 1616, 1832, 1864)

Except the new Neo PowerSeries, due to the fact it uses a CorBus vs a ComBus which is encrypted.

Sent from my Sprint iPhone 5s using Tapatalk

13

First off is the panel seeing the Evisalink module? It must be wired to the keypad bus (ComBus). Second did you enroll the module is the DSC panel? * 8 installer code “default is 5555” then 902 wait 1min for it to detect. Then do a 903, If it’s like the DSC IT-100 it will display as a keypad #8. Press # # to exit. If you are monitored, then the installed code had been changed and good luck getting it.

Sent from my Sprint iPhone 5s using Tapatalk

14

[quote=“computerjohn, post:13, topic:182502”]First off is the panel seeing the Evisalink module? It must be wired to the keypad bus (ComBus). Second did you enroll the module is the DSC panel? * 8 installer code “default is 5555” then 902 wait 1min for it to detect. Then do a 903, If it’s like the DSC IT-100 it will display as a keypad #8. Press # # to exit. If you are monitored, then the installed code had been changed and good luck getting it.

Sent from my Sprint iPhone 5s using Tapatalk[/quote]

It sees the EVL3 as a PC5400 module. Is this correct? I cleared it and re-enrolled. Still the same.

How do I get and send the logs?

15

Can you access the module interface via a browser?

Sent from my Sprint iPhone 5s using Tapatalk

16

[quote=“computerjohn, post:15, topic:182502”]Can you access the module interface via a browser?

Sent from my Sprint iPhone 5s using Tapatalk[/quote]

Yes and I can arm and disarm via browser as well.

17

Let’s walk through this again: there is no doubt, the EVL interface is operable and communicating with the panel; however, the is an Unidentified Vera issue which is specific to your setup and configuration. The original screen capture identifies the TPI is connected and this should match your Vera’s IP address… Note, it can only have one active TPI connection.

  1. Uninstall the current version.
  2. Log into apps.mios.com and install the new version 0.40 that was released by @guessed today.
  3. Follow the steps in the wiki, I.e.
    A. Select interface.
    B. Save and restart.
    C. Insert IP,
    D. Update zones. Save and restart
    E. Etc, etc. do not rush and if you receive an error, screen capture.

Below is some overview to logging on to your Vera to extract the logs. You only need the line with the errors and do not paste the whole log as it may contain sensitive information such as password or pins that are used for plugin. So vetting is required.

http://wiki.micasaverde.com/index.php/Logon_Vera_SSH
http://wiki.micasaverde.com/index.php/Luup_Debugging

18

Thanks for all of your help. I finally was fed up with the issue and completely reset the Vera and all devices.

Guess what…it works now!!!

LOL now my Leviton scene and zone controllers are trying to be difficult…:frowning:

Thanks again everyone for advice and support!!!