The Vera Community forums have moved!

Advanced => Plugins & Plugin Development => Programming => DSC Alarm System Plugin => Topic started by: strangely on December 28, 2010, 01:50:09 am

Title: DSC Alarm System plugin
Post by: strangely on December 28, 2010, 01:50:09 am
Anybody using the DSC plugin with a DSC alarm system?
Title: Re: DSC plugin
Post by: strangely on December 28, 2010, 11:33:39 am
Anyone... am I alone? :-\
Title: Re: DSC plugin
Post by: myhomeserver on December 28, 2010, 01:00:34 pm
I wish, I have my whole place wired, but my system doesn't have the IT-100 interface board, not sure if it will support it, and the system has been off and not monitored for over 10 years.  But, every room has motion sensors and door/window sensors that I'd love to use.....

Title: Re: DSC plugin
Post by: strangely on December 28, 2010, 01:17:34 pm
Even if it doesn't support the IT100, a new board isn't terribly expensive. Even if you had to upgrade it, it's still a really cheap way to add sensors to Vera. I paid out about 205 bucks for the whole alarm kit and 65 for the IT100 and now have all the doors, downstairs windows and a PIR sensor all available to Vera now as sensors.

A DSC PC1832NK is only about $65; so for about $130 with the IT100 included (the cost of 2 or 3 Zwave sensor depending on the type) you could perhaps use everything again?

Of course, I'm not sure if your keypad is compatible and you would also either need a USB adapter or a WIZnet to interface it to Vera!

Also with the amount of batteries these HRDS1 zwave door sensors are eating recently, you'd save some money in the long run :)
Title: Re: DSC plugin
Post by: myhomeserver on December 28, 2010, 02:12:58 pm
Sounds like something I should do for short change...even the barn and garage is all wired up with D/W and motion sensors that use AAA batteries, so Im assuming they are 900Mhz or something to report back.  I've got limited know-how on this thing, a manual, 2 keypads and no codes and the batteries are all dead and transformers missing. 

I figure I'll wait till Vera is stable and running perfectly before I add more sensors, but thanks for the info and I know who I'll be PM'ing when Im ready :)

Title: Re: DSC plugin
Post by: fall-line on December 28, 2010, 02:19:33 pm
I'm not currently using it, but I had planned to buy a DSC alarm system primarily because of this plugin's existence.
Title: Re: DSC plugin
Post by: strangely on December 28, 2010, 04:39:43 pm
This was the kit I started with:

http://www.homesecuritystore.com/p-547-kit16-qp63-dsc-power-1616-security-system-kit.aspx

I found out my place was pre-wired already, so apart from about 5 wired door sensors (a couple of bucks each) and cheap tone generator / wire detector, it was all quite good value for money... I've got 5 doors hard wired, 3 windows with wireless sensors and a PIR motion sensor hooked up.
Just got to add some more window sensors (upstairs at some point), a glass break sensor and maybe some smoke detectors once I've figured out if there's a way to integrate them with either the existing smoke alarms or replace them without breaking code requirements or compromising safety in any way.
Title: Re: DSC plugin
Post by: fall-line on December 28, 2010, 05:49:26 pm
Thanks, that is the same kit I'd been looking at. Since you posed the question though, It doesn't appear that too many people are using the plugin. Do you think there is a danger of it being abandoned?
Title: Re: DSC plugin
Post by: strangely on December 28, 2010, 06:20:11 pm
Well the developer (Javier) I beleive no longer works for MCV. I think the plugin needs some work still due to some potential security issues and some other odd behaviors which I haven't worked out yet if it's  something I've misconfigured on the panel, or if it's not working or configured correct on the plugin side.

Sensors work fine and update almost instantly, but to arm it seems like I have to press the arm button twice; and likewise this morning I couldn't get a scene (that had arming included) to do the same...maybe for the same reason?!  Disarm doesnalthough work, although I suspect there are still some things I have to configure on the panel itself as my keyfob disarm button doesn't seem to work either, or it only works perhaps for stay arming?!

Notifications also don't seem to work for arming, or the panel actually being in "alarm" state.



I need to disconnect the siren to do some more in depth testin and troubleshooting as my wife will kill me, and in any case we have a young baby who won't appreciate growing up deaf either :)
Title: Re: DSC plugin
Post by: nswint on December 30, 2010, 09:55:53 am
Is the IT100 the same as the DSC5401?

I tried it awhile back with a usb-to-serial cable and had no luck.
Title: Re: DSC plugin
Post by: strangely on December 30, 2010, 11:49:28 am
I know the IT100 replaced it! The best way to find out would be to compare the developers guides to see if the implementation is the same, or similar enough to work for the majority of the supported commands.

I've attached the IT100 guide because I already had it.
Title: Re: DSC plugin
Post by: techsan on December 30, 2010, 12:55:20 pm
I have the IT-100 but have not wired it in yet. Is it worth the hassle?
Title: Re: DSC plugin
Post by: strangely on December 30, 2010, 01:54:20 pm
Depends on what you want to achieve?

For me yes because I can now use the sensors to trigger scenes etc and also get notifications about doors or alarm conditions. The sensors are also way more reliable than some of the Zwave equivalents.

I now also have more options to disarm or arm, along with also disarming via scene that's triggered when a PIN is entered on any of the Kwikset locks.
Title: Re: DSC plugin
Post by: nswint on December 30, 2010, 02:08:11 pm
Very much so.  I've been using the dsc5401 with Misterhouse for years and the hassle of not having to program the date for DST alone was worth the price paid for it.
Title: Re: DSC plugin
Post by: techsan on December 30, 2010, 03:23:18 pm
Well I guess that settles it for tonight's project!
Title: Re: DSC plugin
Post by: strangely on January 01, 2011, 02:19:48 pm
@techsan, did you get it up and running?

I can't get any notifications for alarm / disarm or any of the other notification types (some are under the partition and some under the parent device) and I wanted to see who else was running this, and if they had issues before raising a ticket?

I've also found that it seems to have an issue with 4 digit PINs; disarm (and one or two of the other buttons) wont function if you have the panel set to use 4 digit PIN's! You either have to change to 6 digit PINs, or pad the 4 digit one with 00 at the end.
Title: Re: DSC plugin
Post by: guessed on January 06, 2011, 12:39:43 am
I've also found that it seems to have an issue with 4 digit PINs; disarm (and one or two of the other buttons) wont function if you have the panel set to use 4 digit PIN's! You either have to change to 6 digit PINs, or pad the 4 digit one with 00 at the end.
I found a copy of the Spec for this interface here:

    http://www.baranharper.com/pdfs/dsc/it-100%252520developers%252520guide.pdf (http://www.baranharper.com/pdfs/dsc/it-100%252520developers%252520guide.pdf)

Page 6, "Partition Disarm Control - With Code" requires a 6-digit PIN, but the get_code(..) method isn't padding it out with 00's per the spec.  Similar for the arming code...

This method can be altered to "pad" as needed:
    http://code.mios.com/trac/mios_dscalarmpanel/browser/I_DscAlarmPanel2.xml#L116 (http://code.mios.com/trac/mios_dscalarmpanel/browser/I_DscAlarmPanel2.xml#L116)
Title: Re: DSC plugin
Post by: guessed on January 06, 2011, 01:01:11 am
I can't get any notifications for alarm / disarm or any of the other notification types (some are under the partition and some under the parent device) and I wanted to see who else was running this, and if they had issues before raising a ticket?

It's hard to tell from the code, but I believe it should be set at the Partition, but there might be a problem in this file:
    http://code.mios.com/trac/mios_dscalarmpanel/browser/D_DscAlarmPartition.json#L194

which should be changed from:
Code: [Select]
                                        "name": "Status",to
Code: [Select]
                                        "name": "PartitionStatus",
Of course, I could be wrong ;-)
Title: Re: DSC plugin
Post by: strangely on January 06, 2011, 03:20:56 am
OK I just tried that and unless the notification system is down, no dice I'm afraid!:(

I can see for the most part that the panel seems to communicating the corresponding statuses to the plugin, but nothing after that.

Any other ideas?
Title: Re: DSC plugin
Post by: guessed on January 06, 2011, 11:02:34 am
Turn on verbose logging and capture a bunch of the dumps for what should be the notification event.  Edit out all the "Password" data that would go into that, and then post it here.

Unfortunately the code is scant on "extra" logging, but we can probably work out the notifications component from it, since that's just interactions with [MiOS] Variables, which is all standard in the verbose logs.

NOTE: I believe you have to "
Title: Re: DSC plugin
Post by: strangely on January 06, 2011, 11:08:45 am
Tried that and hard reboot to see if that made a difference.

If I tail the log file, whats the best thing to grep it against to filter out all the other crap?

Probably wont be for a few days anyway as I'm off to CES today :)
Title: Re: DSC plugin
Post by: guessed on January 06, 2011, 12:05:11 pm
You can just Email me the whole [unfiltered] thing if you don't want to post it here.  It's actually some of the "other crap" (from Verbose Logging) that I'll likely want to look at :-)

Unfortunately the code doesn't have a centralized Logging function, so it's own log-lines aren't "tagged" for easy grepping.
Title: Re: DSC plugin
Post by: tosvus on January 12, 2011, 03:31:39 pm
sorry to barge in on this topic - but I'm looking at Vera as a potential home automation controller, and working with DSC. I'm in the situation that I have not made a final decision on either, but I think the DSC-1832 kit looks good and reasonably priced compared to similar offerings from GE. Also, the sensors seem more reasonably priced. The reason I need a non z-wave/x-10/insteon sensor in the first place is that I would really like glass-breaking sensors throughout my house.

Searching the forum and wiki, I have found very little info on 1832 compatibility (except some vague references seeming to indicate it should work). Technically what would be needed (if possible though)?

The parts I was thinking of buying;
DSC Power1832 Alarm Control Panel
RFK5500 - LCD Full-Message Keypad w/ Wireless Receiver
(actually a kit with those two items included)

To get communications going, I was thinking:
PCLINK-SCW - DSC Computer Interface
WIZnet Serial-to-Ethernet Gateway - WIZ110SR

Would this do the trick? I also see reference to IT-100 but not sure what this is needed for?

How does this work software wise? Does it use the plugin for GE, or some other plugin?

My goal (for now) is to:
-remotely activate/deactivate alarm, preferably through vera iphone app or mobile web?
-Have some sort of message sent to me if the alarm is triggered while away. (sms? email? )
-preferably have vera pick up on it and turn all lights in the house on, etc

Is this even possible?

Thanks a lot, and again,sorry for hijacking this thread...seems like you guys may be more in the know of DSC and Vera than anyone else though
Title: Re: DSC plugin
Post by: strangely on January 12, 2011, 04:35:52 pm
@tosvus

The 1832 will work fine and you will need to interface it to Vera with an IT-100 and then either a WIZ110SR or a regular USB to serial adapter.
Although the board has serial already, it can only be used for programming / initial setup via a PC with the DSC programming software unfortunately!

There is already a specific DSC plugin (written by MCV) and you'll be able to remotely enable or disable the alarm from a phone etc (via a scene) and also use the sensors to trigger other scenes if need be like lights etc! You can also disarm it if you like automatically from associating the disarm scene with an event like a PIN being entered from a lock keypad.

The sensors can also be used independent of the alarm being armed or not and like you said they are also cheap!

The only thing at the moment that isn't working for some reason is the SMS or email Alerts. I'm currently working with @guessed at the moment to work out why these aren't working.



Title: Re: DSC plugin
Post by: tosvus on January 12, 2011, 07:56:34 pm
Thank you for the quick and detailed response! I appreciate it very much. The rumors about the great user-community were not exaggerated it looks like :)

I hope the message issue gets resolved, though I have a little time before I will buy the main equipment. Ended up impulse-buying the Trane Thermostat at Radioshack for $59 today though!! (can't use it yet, but that was too good of a deal to pass up! :))

I'll be reading more (and probably posting more questions too!) :)

Thanks again.
Title: Re: DSC plugin
Post by: strangely on January 14, 2011, 01:06:16 pm
I bought my Alarm Kit from www.homesecuritystore.com as they seem to have the best prices. If you are going to set this up yourself then their support forum is also a good resource with some really helpful people.

The alarm panel itself was way easier and quicker to install and wire than the actual panel setup was, and I suggest you try and familiarize yourself with it now as there is quite a steep leaning curve to it and it was considerably more difficult than I imagined :)
Title: Re: DSC plugin
Post by: tosvus on January 14, 2011, 03:26:18 pm
Yes, they look like a good store. Hope I can manage the setup though :)
Title: Re: DSC plugin
Post by: SolarExec on January 18, 2011, 10:56:52 am
I finally got the DSC alarm installed in our new construction (a DSC Powerseries 1616). I want to integrate this with the VERA so just to be sure I've got this right... I need to buy the IT-100 and the WIZ110SR?
Title: Re: DSC plugin
Post by: strangely on January 18, 2011, 11:33:12 am
@SolarExec,

You have a few options:

(1) The IT100 and the WIZ110SR will give you good flexibility in terms of remotely connecting Vera to the panel as it can be pretty much connected anywhere on your network. The only disadvantage to the WIZnet is that it'll need to be connected to a 5V wall wart or some other source such as a USB port and adapter cable.

(2) If your Vera isn't too far from the panel and you have good wiring access to both, then you could run a Cat5/6 cable, and run RS232 over it (via some RJ45 to RS232 adapter plugs) directly from a supported USB to Serial adapter plugged into vera such as this one:
http://parts.digikey.com/1/parts/1501993-cable-economy-usb-rs232-srl-conv-uc232r-10-chipi.html

(3) The third option is locate the IT100 and the USB serial adapter near Vera, and then run cable (4 wire) back to either the panel keybus input or to the PIN pad since this is also on the same bus.

Title: Re: DSC plugin
Post by: guessed on January 18, 2011, 11:43:09 am
Also consider how you will supply Backup power to things.  Generally speaking the Alarm components are "backed" by a Battery, so they'll survive Grid outages (etc).

Things on your Ethernet network generally don't have this type of backup, so you'll lose connectivity to those components when the power is down. 

By placing them "all together" (Panel + IT100 + Vera + DSL Modem) you have a few more options to provide Power backup to all of them.  I have mine set this way, so I can survive for about 12 hrs if the power goes down.  As a result, I can continue to use Vera to notify me of problems in the house, such as Alarm breaches, and that the power itself went down.

You may not want this up front, but it's handy to have the option down the road.
Title: Re: DSC plugin
Post by: SolarExec on January 18, 2011, 12:21:53 pm
Thanks. Everything is within a few inches of each other on a little rack. I've got Vera hooked up to a netgear switch that also feeds the rest of the house. The switch is connected to the router and then to the cable modem. Does that mean I am better off with the USB to 232 adapter connected to the IT-100 and the Vera?

I noticed that the electrician selected a pretty cheap dsc (I should have supervised this purchase). We have 12 doors and 15 windows hard wired plus 2 glass breaks and 3 keypads. Should I upgrade the box to a better one (1864?)? It looks like he currently has this wired to 6 zones which won't give us a lot of information...

On the power, we have a backup generator that kicks on after 3-5 minutes so I was planning to put a battery backup in for all of this stuff to keep it going until the gen kicks on.
Title: Re: DSC plugin
Post by: strangely on January 18, 2011, 05:55:47 pm
You may want to consider either the 1832 or 1864 (you'll still need zone expanders also though)  as I think the 1616 only supports 16 hardwired zones and even then with the use of zone expanders. The key pads also support an extra zone or output.

Just be aware that if the contact switches have been wired in series, then you'll perhaps have to think about home running extra cabling to support the individual zones!

If your Vera is close, then go with the USB to serial adapter that I linked in my post as you won't have to worry about power to the WIZnet.
Title: Re: DSC plugin
Post by: SolarExec on January 18, 2011, 06:18:52 pm
Thanks! That is awesome. I will get to work on this and let you know how it goes... (Now if I could just find a decent dimmer switch that would work with our recessed LEDs  ???)
Title: Re: DSC plugin
Post by: strangely on January 19, 2011, 12:01:02 am
Ouch!

Maybe look at dimming capable LED's?
Title: Re: DSC plugin
Post by: techsan on January 23, 2011, 12:37:24 am
@ strangely...So I installed the IT100...custom made the alarm box to have the IT100 sit right below the alarm panel, the serial to usb is plugged in but Vera will not recognize that something is there. Could it be the USB to serial causing Vera not to recognize the alarm panel? I do have the DSC plugin already installed and have already done the reboot on the Vera. Thanks
Title: Re: DSC plugin
Post by: strangely on January 23, 2011, 01:06:29 am
Here are some pointers to check:

Is the LED on the IT100 flashing?
Is your serial adaptor a supported one?
Have you configured the plugin to use the USB to serial adapter in the MiOS developers serial tab?

You may also need a null modem cable or adaptor between the USB serial adapter and the IT100. I have mine plugged in via a cat5 cable and DB9 adapters back to a wiznet at the moment and I cant remember if the cat5 adapters I have are either wired straight, or as a null modem! From memory when I had mine wired to a USB adapter it needed the null modem adapter.
Title: Re: DSC plugin
Post by: techsan on January 24, 2011, 02:32:23 pm
Here are some pointers to check:

Is the LED on the IT100 flashing?
Is your serial adaptor a supported one?
Have you configured the plugin to use the USB to serial adapter in the MiOS developers serial tab? Yes, configured the plugin and I now have tabs listed as partitions. I have no idea where to go from here.  ???

You may also need a null modem cable or adaptor between the USB serial adapter and the IT100. I have mine plugged in via a cat5 cable and DB9 adapters back to a wiznet at the moment and I cant remember if the cat5 adapters I have are either wired straight, or as a null modem! From memory when I had mine wired to a USB adapter it needed the null modem adapter.

The IT100 is blinking once a second.
Not entirely sure if my adapter us supported, its an I/O crest usb to DB9 adapter. Product 3726 on Monoprice.
I have configured the plugin (not sure if correct however) and I now have partitions that are editable. I simply have no idea what info to put in. I have "Away" "Stay" "No Delay" "w/Code" and "Disarm" all listed as options in one of these partitions but they do nothing when selected.
Title: Re: DSC plugin
Post by: strangely on January 24, 2011, 03:25:41 pm
Can you see the serial port when you go to MiOS developers and the serial port configuration tab? Its in there that you need to set it to use the plugin.

If you don't see your serial adapter listed in there, then it's likely that its not supported.
Title: Re: DSC plugin
Post by: techsan on January 24, 2011, 04:23:38 pm
It shows PL2303 in the name field. Not sure if the attachment is visible but I added on in.
Title: Re: DSC plugin
Post by: strangely on January 24, 2011, 04:58:48 pm
Ok that's good!
In the used by device dropdown where its currently written as "Serial_Portlist xxx..." you need to select the plugin which will be whatever the DSC is named as ( I renamed mine so not sure what it was).

You'll also need to change the baud rate to 9600 which should be IT100 default. Don't forget to save after changing both these items.
Title: Re: DSC plugin
Post by: techsan on January 31, 2011, 01:14:43 pm
Hey Strangely,

I changed everything over, saved, and still no dice. The issue must be in my settings within the Vera dashboard but I don't have a comprehensive way to tell if I have them right as Vera sees the DSC but won't control it. About 60% of the time I get the "Luup starting I/O" for that device but even then I dont have any control.
Title: Re: DSC plugin
Post by: strangely on January 31, 2011, 03:25:29 pm
Did you try a Null modem cable between the IT100 and your serial adapter ?

Null modem means the pins within the DB9 connectors have pins 2 and 3 (TX and RX) crossed so that the TX of one is connected to the RX of the other and vice versa. If you have a cable between the two then you should check how its wired.
Title: Re: DSC plugin
Post by: JimMac on February 01, 2011, 08:37:43 am
I have a DSC PC4020 alarm panel and a PC4401 data link module.  After looking at the IT100 it looks like it is not for my DSC board but its function is similar to the PC4401.  Has anyone with a PC4020 tried to use the PC4401 to interface with Vera?  If not can someone who has the IT100 look at the PC4401 to see if there would be any compatibility problems using the DSC plugin with this hardware.
Title: Re: DSC plugin
Post by: strangely on February 01, 2011, 12:25:34 pm
From what I've read there isn't a world of difference, but none the less I guess theres enough to warrant different drivers when you look at other systems like charmed quark:

http://www.charmedquark.com/vb_forum/showthread.php?t=9606

Based on the above you have two options and thats to either edit the existing (or upcoming rewritten plugin). Do you have the developers guide for the PC4401?  Or alternately think about updating the panel to one of the power series ones perhaps? 
Title: Re: DSC plugin
Post by: techsan on February 03, 2011, 12:52:55 pm
Did you try a Null modem cable between the IT100 and your serial adapter ?

Null modem means the pins within the DB9 connectors have pins 2 and 3 (TX and RX) crossed so that the TX of one is connected to the RX of the other and vice versa. If you have a cable between the two then you should check how its wired.

I will have the null modem tonight and I'll give it a go! Hopefully I plug it in and it all plays nice. BTW thanks for all of your help on this. ;)
Title: Re: DSC plugin
Post by: computerjohn on February 13, 2011, 11:45:25 pm
Hello everyone,

So what's the story with the DSC interface.  Will the DSC TL150 TLINK interface work with Vera2?  I would prefer using CAT5 & connecting it to my home network instead of using outdated serial interface. Not to mention, putting my Vera2 in the basement next to my DSC panel.
Title: Re: DSC plugin
Post by: guessed on February 14, 2011, 12:38:39 am
Hello everyone,

So what's the story with the DSC interface.  Will the DSC TL150 TLINK interface work with Vera2?  I would prefer using CAT5 & connecting it to my home network instead of using outdated serial interface. Not to mention, putting my Vera2 in the basement next to my DSC panel.
It's coded to use the IT100 interface.  This can be attached to a TCP Network using either a WIZnet (which is what @strangely uses) or a RS-232 to Wifi Adapter (which is what I'm currently using to redevelop the plugin with)

The [new] code has branches to specifically handle the "over ethernet" initialization that the IT100 can be deployed with (like the WIZnet or Wifi options above) without need for anything intermediary.

Not sure what a TL150 is, so you'd need to do research on how compatible it is with the IT100, and it's command set.

If it's different, then you'd need to write a new Plugin.


Anyhow, the bulk of the re-write has been done, and @strangely is field testing my Alpha version to find the quirks.  Once the guts are working, it'll be checked into code.mios.com.  At that time, if the 'v2' common API/Interface hasn't evolved then
I'll ship @strangely back his Panel, and dev will stop.  He's generously loaned me a temp one to get it going, but I do have to return it at some point  ;)


PS: I've split/merged this post with the DSC Plugin one, since it wasn't related directly to the standardization effort in the Luup area.
Title: Re: DSC plugin
Post by: strangely on February 16, 2011, 01:58:37 am
@computerjohn,

From what I've read, the TL150 only supports arming and disarming the alarm (from an in built web page) and also for communication to a central station via IP, in lieu of having a pure POTS (telephone) based solution.

Either way, the WIZnet and IT100 would give you exactly what you need... essentially an IP connected panel that is interfaced with Vera allowing the sensors etc to be used for other automation tasks.
Title: Re: DSC plugin
Post by: computerjohn on February 21, 2011, 12:20:25 am
First sorry you the delayed response, but I have been busy with work & installing all my in-wall Z-Wave light switches.  Ok, sounds great guys..  Thank you so much.  Also, I'm a dealer. Any good places to buy the WIZnet??  Also is there any other configuration that must be done to the IT100 or is it plug 'n play with the WIZnet?
Title: Re: DSC plugin
Post by: strangely on February 21, 2011, 02:40:40 am
You can buy one here:

http://www.sparkfun.com/products/9476

Once you plug it in to the IT100 then there's nothing really to do there; however the WIZnet may need some configuration via its software tool so that you can set the baud rate etc, and then assign an IP to it. Once you have it set with a static IP then the rest is plain sailing :)
Title: Re: DSC plugin
Post by: computerjohn on February 21, 2011, 11:35:12 am
Great, again thank you!! 

You can buy one here:

http://www.sparkfun.com/products/9476

Once you plug it in to the IT100 then there's nothing really to do there; however the WIZnet may need some configuration via its software tool so that you can set the baud rate etc, and then assign an IP to it. Once you have it set with a static IP then the rest is plain sailing :)

Title: Re: DSC plugin
Post by: techsan on February 22, 2011, 05:45:45 pm
Alas I am back to pick the brains of those smarter that me with regard to the DSC plugin, or as I call it, the stress harbinger.

1. The DSC plugin has been installed according to the wiki, 2. serial adapter via IT100 is recognized by Vera and has been associated with the plugin 3. scenario has been attempted with null modem adapter as well as without, however I am still unable to control any functionality of the DSC panel.

If I associate all three of the parameters as discussed in the wiki, Vera seems to loop as if looking for a functionality that is not there (note: I do not have motion sensors or smoke sensors connected to the DSC). If I remove all of the parameters except for the actual "Active Partition" field Vera pulls back a tab for the partition and gives me the "Away, Stay, No Delay, w/Code, and Disarm" buttons..all of which do nothing.

Is there something I'm missing in the advanced tabs or the setup of these tabs that the wiki does not go into? The wiki makes it seem extremely plug and play after copying a few lines into empty fields but I have yet to find that ease of installation.

P.S. the IT100 continually blinks green whether or not the serial adapter is connected to the Vera or not. Is this normal? Does this only indicate the IT100 is communicating with the DSC?

Thanks all, aside from this topic alone Vera has been great to me.
Title: Re: DSC plugin
Post by: guessed on February 22, 2011, 10:04:32 pm
@techsan, If you can wait about 1-2wks we should be finished with initial testing on the Alpha version of the re-write. 

@strangely has been testing the code in the real world for ~1wk and I got a report from him earlier that he'd tested scene(s), notifications and arming/disarming with it and all was well.


Anyhow, at startup, the newer code creates an initial configuration with 1 Partition, and 6 Zones, and defaults configuration Parameters to represent this setup.  You can tweak these, but gives you a starting point (not a blank slate) so it's easier to modify to your needs.

It also attempts to read the Partition and Zone labels from the Panel, so if you have a DSC with AlphaNumerics (or a Programmer, like @strangely has) then those will show up automatically against the Partitions and Zones under MiOS.

At the moment, I have the code, but not any Wiki documentation for it.  My hope was to minimize the need for doc.... or to encourage @strangely to tweak that up... LOL  8)
Title: Re: DSC plugin
Post by: computerjohn on February 22, 2011, 10:27:27 pm
Hello everyone,

I have ordered my IT-100 & the WIZnet module today.  I should have them by the end of the week & plan on getting it working with my DSC panel & Vera 2 over the weekend.  

Now is the driver stable for me to have it working live & one thing I forgot to ask is do I need a NULL modem cable to connect the IT-100 to the WIZnet module?

Thanks Again,

John
Title: Re: DSC plugin
Post by: strangely on February 23, 2011, 01:31:55 am
Alas I am back to pick the brains of those smarter that me with regard to the DSC plugin, or as I call it, the stress harbinger.

1. The DSC plugin has been installed according to the wiki, 2. serial adapter via IT100 is recognized by Vera and has been associated with the plugin 3. scenario has been attempted with null modem adapter as well as without, however I am still unable to control any functionality of the DSC panel.

If I associate all three of the parameters as discussed in the wiki, Vera seems to loop as if looking for a functionality that is not there (note: I do not have motion sensors or smoke sensors connected to the DSC). If I remove all of the parameters except for the actual "Active Partition" field Vera pulls back a tab for the partition and gives me the "Away, Stay, No Delay, w/Code, and Disarm" buttons..all of which do nothing.

Is there something I'm missing in the advanced tabs or the setup of these tabs that the wiki does not go into? The wiki makes it seem extremely plug and play after copying a few lines into empty fields but I have yet to find that ease of installation.

P.S. the IT100 continually blinks green whether or not the serial adapter is connected to the Vera or not. Is this normal? Does this only indicate the IT100 is communicating with the DSC?

Thanks all, aside from this topic alone Vera has been great to me.

@techsan,

Before @guessed releases his new plugin, you may as well try to see if you can this working!

First of all ignore the current WiKi instructions for configuration and Just enter the following (you may have to delete what you've typed there already):

If you have one partition then under "ActivePartitions" enter the number 1, If you have two partitions then enter 1,2 etc etc.

And then its the same for the zones also, so assuming you have 10 zones set up and you know the zone numbers, then just enter them exactly as follows in the "MotionSensors" variable: 1,2,3,4,5,6,7,8,9,10 this is assuming your zone numbers are in series (mine are not and thus I have 1,2,3,4,5,9,10,11,12).
There is nothing else to type other than whats in bold above!

Once you have saved the above then enter your PIN number (beware this will be sent to MCV's servers!) and save again. If you have a four digit PIN (rather than 6 digits) then you'll need to pad the end of the PIN with 00, e.g 123400

The best way to establish if you have communications is to try to set the clock; If it updates then you should be good to go! If it doesn't work then try to either remove or insert the null modem and try again!

If none of the above works then something maybe wrong with your serial port setup!( perhaps post a picture of that?)

Oh and yes, the green light only indicates the IT100 is communicating with the panel!

Out of interest did you buy the IT100 new? The reason I ask was that if it was off eBay or similar (used), then somebody may have changed the baud rate and you may have to default it!
Title: Re: DSC plugin
Post by: strangely on February 23, 2011, 01:47:51 am


Now is the driver stable for me to have it working live & one thing I forgot to ask is do I need a NULL modem cable to connect the IT-100 to the WIZnet module?

Thanks Again,

John

I have a little bit more testing to perform as I haven't used the panel much due to being slammed at work, and also having some guests staying at my house, but the good news is it all seems to work well!

I have a few things to validate including verifying the plugin can read the zone labels (I need to program these from the PC interface as I don't have a PIN pad that supports them).

I'm fairly sure you'll need a null modem cable; however I'm not 100% certain due to the fact I wired mine a month or so back with a home made cat6 cable (that also contains my telephone wires) and jumps up the wall and through the attic to the other side of the room where my network and SIP  phone adapter live (this saved having wall warts supplying power to the WIZnet and the phone adapter in the panel). I guess I can crack the DSUB connectors open again and verify if you have trouble!

Title: Re: DSC plugin
Post by: strangely on February 23, 2011, 01:58:09 am
At the moment, I have the code, but not any Wiki documentation for it.  My hope was to minimize the need for doc.... or to encourage @strangely to tweak that up... LOL  8)
Let me see what I can do! :)
Title: DSC plugin
Post by: digitalperk on February 23, 2011, 04:05:13 pm
@guessed:

Have you made any progress on the DSC plugin standardized on V1 of S_AlarmPartition.xml? I would really like to have something for the SQ Remote, iVera and automator.app guys to look at. This is the missing thing for me.

Thanks
Title: Re: DSC plugin
Post by: guessed on February 23, 2011, 04:23:14 pm
@guessed:

Have you made any progress on the DSC plugin standardized on V1 of S_AlarmPartition.xml? I would really like to have something for the SQ Remote, iVera and automator.app guys to look at. This is the missing thing for me.

Thanks
See above posting.  I've also given a copy of the code to @computerjohn and he'll be running with it this weekend.  Assuming no significant negative feedback, I plan on checkin it in next week as an "Alpha".

That said, I don't want the Control Points using the "v1" interfaces, it really doesn't make sense since we cannot readily extend them to the broader set of Panels (etc) and it will likely entrench their limited design.


Instead, we need to focus on finalizing, and implementing against, the V2 spec that we have going in the overall "Alarm Panel Standardization" thread.  From what we have so far, it'll only take 2-3 days (tops) to augment the existing implementations to use it, so it's a weekend job (at least for the Paradox and DSC, and I'm assuming so for the Caddx also)

Title: Re: DSC plugin
Post by: computerjohn on February 24, 2011, 12:04:29 am
LOL!! Wall warts...   :D Too funny..  I could make one, but I know I should have one somewhere here..  I ordered another one as a 6' cable & as a 2" adapter.  Great thank you..



Now is the driver stable for me to have it working live & one thing I forgot to ask is do I need a NULL modem cable to connect the IT-100 to the WIZnet module?

Thanks Again,

John

I have a little bit more testing to perform as I haven't used the panel much due to being slammed at work, and also having some guests staying at my house, but the good news is it all seems to work well!

I have a few things to validate including verifying the plugin can read the zone labels (I need to program these from the PC interface as I don't have a PIN pad that supports them).

I'm fairly sure you'll need a null modem cable; however I'm not 100% certain due to the fact I wired mine a month or so back with a home made cat6 cable (that also contains my telephone wires) and jumps up the wall and through the attic to the other side of the room where my network and SIP  phone adapter live (this saved having wall warts supplying power to the WIZnet and the phone adapter in the panel). I guess I can crack the DSUB connectors open again and verify if you have trouble!


Title: Re: DSC plugin
Post by: computerjohn on February 25, 2011, 11:55:21 pm
Well I recieved the IT-100 & WIZnet module today.  :D  Now I was reading the VERY informitive 1 page instructions that came with the IT-100 (i'm being sarcastic). It states to use a straight thru cable. Is this being the case connecting to a PC or is this the case connecting it to the WIZnet module?
Title: Re: DSC plugin
Post by: strangely on February 26, 2011, 03:18:55 am
OK kudos for these manufactures for making these things crossed to start with, and to eliminate the need for a null modem cable; however it doesn't help when the other device may have done the same!

Anyway luckily it appears the WIZnet has not done this, and I just confirmed by cracking opening my custom cable that it is wired straight 2>2 and 3>3

No null modem adapter required for the IT100 and the WIZnet combo at least.
Title: Re: DSC plugin
Post by: computerjohn on February 26, 2011, 02:03:28 pm
Great..  I'll try working on it today when I get out of work.  The mfg date on my IT-100 is 1/2011 so it just came off the assy line.

OK kudos for these manufactures for making these things crossed to start with, and to eliminate the need for a null modem cable; however it doesn't help when the other device may have done the same!

Anyway luckily it appears the WIZnet has not done this, and I just confirmed by cracking opening my custom cable that it is wired straight 2>2 and 3>3

No null modem adapter required for the IT100 and the WIZnet combo at least.
Title: Re: DSC plugin
Post by: computerjohn on February 27, 2011, 11:33:03 pm
Well had a bunch of stuff to do today, but just finished installing my IT-100 & WIZnet modules.  I configured the WIZnet & now working on the plugin in VERA..  While I had my panel downed I had to move a motion sensor that I wanted to move for awhile. Keep you posted..
Title: Re: DSC plugin
Post by: computerjohn on February 27, 2011, 11:56:21 pm
SOS! Can't seem to get this plugin to work.
Title: Re: DSC plugin
Post by: strangely on February 28, 2011, 12:40:28 am
Are you sure you have the WIZnet configured correctly?

I assume you are using the new plug-in?
Title: Re: DSC plugin
Post by: computerjohn on February 28, 2011, 06:38:40 pm
I'm assuming its configured correctly, but I'm not sure if the plugin settings are right though. The plugin instructions were a little vague. As what are all the files I need to load, then when I create the device in vera what are all the fields that need to be filled, and when it display the device on vera what are all the settings I need to configure under advance. I was told to use the weather plugin as an example. I have the weather app working fine, this is far from close to the settings of the weather plugin.
Title: Re: DSC plugin
Post by: kwik5 on February 28, 2011, 09:54:01 pm
The DSC plugin hasn't worked for me either...

I have a brand new IT-100 plugged into a DSC PowerSeries PC1616. The cable I got from Monoprice and it is showing pl2303 in the serial port config, so looks like it's got the Prolific chipset.

I have tried putting the service id (urn:micasaverde-com:serviceId:AlarmPanel1) into all 3 variables like the help page explains and tried putting a "1" for the variables...all with the same result. After saving, the UI refreshes and acts like it's configuring the zwave device, opening the I/O port, running Luaa start. It just keeps doing this infinitely. If I try to send the access code I get "Delivery Failed".

I've tried re-installing the plugin too. I emailed tech support and got a reply on Feb. 8...

"We identified that problem in the firmware version you're running now and solved it. Our engineers are working on developing a new firmware version which will be out soon. You will be notified on the Dashboard when that happens and I can assure you that a lot of improvements happened, including this fix."

I hope the firmware fix comes soon. Does anyone else have any suggestions to make it work?
Title: Re: DSC plugin
Post by: strangely on February 28, 2011, 10:51:54 pm
Ok so a couple of things:

Don't follow the Wiki as the information will just confuse you.
The Wiki is also only applicable to MCV's plugin anyway.

If using the MCV plugin, then once you've uploaded all the files, created the plugin, and then associated the serial port, you then just need to follow my post here:

http://forum.micasaverde.com/index.php?topic=5154.msg33638#msg33638

If anyone is wanting to run the DSC version for the time being then I recommend downloading it from the MiOS marketplace as the only part that needs to be done then is associating it with a serial port.

I will write a guide, but the problem is that I'm running the V1 plugin by @ guessed which is already obsoleted by a V2 plug-in that he's nearly finished working on as part of a standardization effort for all the alarm vendor version.

I haven't started to run the V2 of the plugin yet so it seems silly to write something until I've played with it.
Title: Re: DSC plugin
Post by: computerjohn on February 28, 2011, 11:03:41 pm
strangely how's it going my friend.  First off, on the WIZNet. what should be the proper config? As should it state "connected vs not connected" on the config tool. Also, Under network, should the server IP be the same as the WIZnet IP or is that to be VERA's IP address. Operation Mode, leave it as Mixed or should it be set to client or server. Lastly baud rate leave it at 9600 or something different.  I need to iron out each one at a time. It will make things A LOT easier to debug.

As for the plugin I downloaded the lastest one from guessed, so I think it's V2.
Title: Re: DSC plugin
Post by: strangely on February 28, 2011, 11:12:04 pm
I'll take a screen grab of mine and post it in about 10 mins. You'll just need to copy everything other than my specific IP setup.
Title: Re: DSC plugin
Post by: kwik5 on February 28, 2011, 11:12:57 pm
Strangley, thanks for taking me back to your previous post on ignoring the wiki. It finally worked! I was testing all the settings and set off the alarm and woke up my whole neighborhood at 11pm!

Not sure if it had something to do with me updating the firmware from 1047 to 1186 or not.

Thanks again.
Title: Re: DSC plugin
Post by: computerjohn on February 28, 2011, 11:15:22 pm
Thanks you..  Much appreciated..   ;D I'll PM you my personal email address, not sure if you want to post your IP config on an unsecure site.

 
I'll take a screen grab of mine and post it in about 10 mins. You'll just need to copy everything other than my specific IP setup.
Title: Re: DSC plugin
Post by: strangely on February 28, 2011, 11:26:13 pm
Its OK to post here as its just a common NAT address :)

Mine is setup as DHCP, but I have my router set to assign this based on the MAC address. If this is not possible with your router then obviously the last thing you want is the address to change... so make it static.
Title: Re: DSC plugin
Post by: computerjohn on February 28, 2011, 11:35:28 pm
Glad to see that it worked for you.  Good heads up, last thing I need is to wake up the wife..

Strangley, thanks for taking me back to your previous post on ignoring the wiki. It finally worked! I was testing all the settings and set off the alarm and woke up my whole neighborhood at 11pm!

Not sure if it had something to do with me updating the firmware from 1047 to 1186 or not.

Thanks again.
Title: Re: DSC plugin
Post by: guessed on February 28, 2011, 11:54:44 pm
As for the plugin I downloaded the lastest one from guessed, so I think it's V2.
No, it's the same "v1" version that @strangely has.  I wanted to ensure that you could get the basics working for yourself before launching the [just converted] "v2" version upon you  8)

A very early, very preliminary, "v2" version is what I checked into the trunk area of the DSC's Trac space in the /trunk directory.

It's still evolving though, so it should not be picked up by users yet.  I'm using it as a vehicle to validate the "v2" Partition API under the "standardization track.  I also took the opportunity to gut the prior "v1" implementation code from it, to ensure that no CP owner would write against the old spec....  no wine before it's time ;)
Title: Re: DSC plugin
Post by: computerjohn on March 01, 2011, 12:22:07 am
I configured the WIZnet to your examples (I wasn't that far off), but still states Not Connected.  I'll have to down the panel tomorrow after work & power it up with the WIZnet connected to the IT-100.  See if that corrects it.
Title: Re: DSC plugin
Post by: strangely on March 01, 2011, 12:30:07 am
It will only show connected if something on the ethernet side is connected to something on the RS232 side. (Vera to the IT100 for example) If you don't have it linked with Vera and the IT100, then disconnected is correct. The connection state isn't to show that the configuration program is connected :) Its just a tell tale trouble shooting indication to show you if the respective devices have handshaken etc.

Don't forget that when you enter the IP for this in the plug-in in vera, then using mine as an example, you also need to enter the port number too... e.g 10.0.0.190:5000
Title: Re: DSC plugin
Post by: computerjohn on March 01, 2011, 12:49:14 am
Ah, that makes sense I guess. Would be nice if the WIZnet had a test function, so that we knew that it was communicating to a serial device. Thanks for the heads up.   ;)

It will only show connected if something on the ethernet side is connected to something on the RS232 side. (Vera to the IT100 for example) If you don't have it linked with Vera and the IT100, then disconnected is correct. The connection state isn't to show that the configuration program is connected :) Its just a tell tale trouble shooting indication to show you if the respective devices have handshaken etc.

Don't forget that when you enter the IP for this in the plug-in in vera, then using mine as an example, you also need to enter the port number too... e.g 10.0.0.190:5000
Title: Re: DSC plugin
Post by: computerjohn on March 04, 2011, 01:52:02 am
Still pulling my hair out. Though I did get to test my WIZnet with a serial loopback adapter tonight.  I found a really nice program that I can test serial ports via TCP. That at least confirms that my WIZnet is working. Now I have to hammer down the settings in Vera
Title: Re: DSC plugin
Post by: TimAlls on March 09, 2011, 08:30:02 am
Just checking in on the new DSC plugin. I was going over the IT-100 specs and was amazed that you can do anything with the alarm system. How is the new plugin coming along? ETA?
I am going to write Labview Code to read the alarm system while waiting for the new plugin to become available. Should be a fun project.
Regards
Tim Alls
AllSeas Yachts
Title: Re: DSC plugin
Post by: computerjohn on March 09, 2011, 06:23:10 pm
Hey guys,

Question, is it the new plugin that will work with the WIZnet?
Title: Re: DSC plugin
Post by: strangely on March 09, 2011, 10:37:27 pm
The old plugin can also work with the WIZnet :)

It seems OK other than a couple of things like notifications not working.
Title: Re: DSC plugin
Post by: computerjohn on March 10, 2011, 06:02:54 pm
Ok then is there to enter there a step by step that works?  I have tried under ip on the device and entered the address to the WIZnet and under com I have tried with no results with it communicating to the IT-100.  I tell it I have 13 zone and my dashboard now has 13 new devices. This shouldn't be this difficult. I'm getting ready to return the it-100 and WIZnet and just get a TL-150 and just access my DSC from a browser or a Android app.
Title: Re: DSC plugin
Post by: TimAlls on March 10, 2011, 06:31:08 pm
Just a quick note to help with debugging.....
First thing to do is connect to a computer running a text terminal. The IT-100 can be set to output Date and Time every 4 minutes. Once you see it coming through on the terminal you know for certain that serial communications have been properly setup. After that connect to Vera. I had to switch to the USB adapter in the "will work" section of listed devices to use with Vera! The Prolific based units never did work for me.
Regards
Tim Alls
AllSeas Yachts
Title: Re: DSC plugin
Post by: strangely on March 10, 2011, 10:19:04 pm
Ok then is there to enter there a step by step that works?  I have tried under ip on the device and entered the address to the WIZnet and under com I have tried with no results with it communicating to the IT-100.  I tell it I have 13 zone and my dashboard now has 13 new devices. This shouldn't be this difficult. I'm getting ready to return the it-100 and WIZnet and just get a TL-150 and just access my DSC from a browser or a Android app.
Have you entered the IP and port number?

It needs to be entered like this:

XX.XX.XX.XX:XXXX
For example mine is 10.0.0.192:5000 and I believe based on the on WIZnet instructions I posted previoulsy you should have your WIZnet setup on the same port anyway!

Don't return it, we'll get you working with it! Also the TL-150 wont give you access to the sensors, which is a major plus for having this linked in.
Title: Re: DSC plugin
Post by: computerjohn on March 11, 2011, 01:21:46 am
Yup, I'm using 192.168.xxx.xxx:xxxx & still nothing. I tested the WIZnet using a loopback plug on it with software that I can test serial ports using an IP address. That pasted no problem.  Is there anyway we can chat on this, this back & forth is getting no where..

Ok then is there to enter there a step by step that works?  I have tried under ip on the device and entered the address to the WIZnet and under com I have tried with no results with it communicating to the IT-100.  I tell it I have 13 zone and my dashboard now has 13 new devices. This shouldn't be this difficult. I'm getting ready to return the it-100 and WIZnet and just get a TL-150 and just access my DSC from a browser or a Android app.
Have you entered the IP and port number?

It needs to be entered like this:

XX.XX.XX.XX:XXXX
For example mine is 10.0.0.192:5000 and I believe based on the on WIZnet instructions I posted previoulsy you should have your WIZnet setup on the same port anyway!

Don't return it, we'll get you working with it! Also the TL-150 wont give you access to the sensors, which is a major plus for having this linked in.
Title: Re: DSC plugin
Post by: strangely on March 11, 2011, 02:33:21 am
@computerjohn

OK, just to check a few things:

Which type of DSC panel do you have? (hopefully power series I assume)
Make sure the IT-100 is wired via a straight cable to the WIZnet.
If you do have a cable then it might be worth taking it out of the equation for the time being!
Probably also worth making sure the IT-100 is working with default baud rate settings (procedure in the user guide I think for shorting some pins).
Is the IT-100 light blinking? The could probably be skipped if you tested it already with the loopback program you were talking about!?

Now if you have confirmed all of the above then I think we should get you running the new alpha version of the Plug-in!

Have you got SSH access?...
Can you ping the address of the WIZnet from vera?

Start by delete the old plug-in from within Vera and save.
Then delete the old plug-in files from /etc/cmh-ludl/ with rm –i *DSC* (confirmation of delete will be required).

Download the new V2 plug-in from here:
http://code.mios.com/trac/mios_dscalarmpanel/changeset/31/trunk?old_path=%2F&format=zip

Unzip the 7 files.
Upload them in the luup developers area.
Create the new plug-in with the picture as an example.

Once created it's going to tell you that the plug-in was created. Have a look at the room this was added to and check you can see the Plug-in icon (a computer chip)
Hit save.
Once Vera comes up then you'll know if its working because it would have created 6 Zones for you! These will not get created if the plug-in cannot communicate with the panel.

If you've gotten this far then trip a door sensor to see if the red running man appears.

If none of the above worked then if you use Skype or MSN or something similar then I can PM you my address or even just an email.
Title: Re: DSC plugin
Post by: computerjohn on March 14, 2011, 03:28:16 pm
Houston we have communication!!!!  YEAH!!!!!!!!!!!!!!!!!!!!!!   ;D
Title: Re: DSC plugin
Post by: strangely on March 14, 2011, 03:43:48 pm
Great News!
Title: Re: DSC plugin
Post by: computerjohn on March 14, 2011, 03:53:46 pm
A couple of problems though. I can not remote Arm. It stated it has been disabled.  So I went to the DSC plugin and changed the false to true, saved & it restarted. I then received an error message under DSC, Startup Lua failed when it started back up.  Did Guessed disable it for now?  Also, I have 13 Zone in my house..  Can I change it from 6 to 13 or has that been hard coded as well??
Title: Re: DSC plugin
Post by: computerjohn on March 14, 2011, 05:04:48 pm
Thanks to Guessed for writing the plugin, Strangely's help & figured a few things on my own.  My DSC panel is now communicating to my IT-100 interface using a WIZnet Ethernet Module.  After I gained access to my Vera via SSH program, I was able to view all my files & notice some confusing problems.  I have posted this to help others, since this issues drove me crazy for 2 weeks.

First off, Uninstall the old DSC Plugin in Vera using the Vera's web interface & save.

To gain access to Vera via SSH you will need a SSH client program. For Window users, I used a program called PuTTY. Very simple, no need to install, & it's free.

Just download the .exe file at http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html (http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html)

After you download it, run PuTTY.exe. Under Host Name type your IP address to your Vera (for example: 192.168.1.xx), leave Port number 22 alone & change connection

type to SSH, & click Open.

At Login type: root (hit Enter)
As for the password: it is located on the label under your Vera unit assigned to WiFI Pass. (hit Enter) (Thanks Strangely!!)

You now should have access to your Vera's Root directory, it should display the following:


BusyBox v1.15.3 (2010-06-10 18:19:49 PDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 Backfire (10.03, r21639) --------------------------
  * 1/3 shot Kahlua    In a shot glass, layer Kahlua
  * 1/3 shot Bailey's  on the bottom, then Bailey's,
  * 1/3 shot Vodka     then Vodka.
 ---------------------------------------------------
  ***      MiOS LTD. ( www.mios.com )        ***
  ***                                        ***
  ***               WARNING :                ***
  *** Any changes made to the system without ***
  *** guidance from MiOS support will VOID   ***
  *** your future Support requests           ***
 ---------------------------------------------------
root@MiOS_xxxxx:~# (the xxxxx will be your Vera's name)

Also note: I have no idea why there is a drink recipe on the shell banner. I did not place it there, but if you are under 21, please disregard!
WARNING!!!!!!!!!!!!! I CAN NOT STRESS THIS ENOUGH. If you delete or modify the wrong file you may brick your Vera!

You can not remove files in the cmh-ludl directory from the root directory. You will get an error message stating "Permission denied".
Instead type chdir /etc/cmh-ludl (hit enter)

It should now say root@MiOS_xxxxx:/etc/cmh-ludl#
To display a list of all the files in this folder, type ls (hit Enter, BTW that is LS in lowercase)

This is where I noticed a big program. The DSC files that are required & have the name DSC in them, have to be in upper case. (For example: D_DSCAlarmPanel1.xml)

Mine were (D_DscAlarmPanel1.xml), in Vera just as the web, the names are case sensitive! So, when creating a device in Vera you type D_DSCAlarmPanel1.xml, but in the

folder it was D_DSCAlarmPanel1.xml. The plugin will not work, since the name is not correct.

So, I had to remove all files associated with the DSC files. To do this type: rm -l *Dsc* (hit Enter, or whatever name) It will confirm if you want to do this. type

y and hit Enter. After all unwanted files have been deleted. type ls (hit Enter) & see if all unwanted files have been removed. If they have type exit and hit Enter.

The PuTTY program will close.

Download the latest DSC Plugin files from Guessed. (I'm not going to post the link to lastest files, since I have not been told it's ok.)
Extract the files onto a folder on your computer where you will rememeber where they are.

Access Vera via your browser.  Create a room named Alarm & Save. Now click onto MiOS Developers icon.
Click onto Luup Files tab and scroll to the bottom. You should see Upload Files with a Browse button. Click the Browse button & locate the folder where you have

extracted the plugin files. Select the first file & do the same for all 7 files. Click On the check off box Restart Luup after upload & click on Go. This will upload

all 7 files onto the /etc/cmh-ludl folder in Vera. Give it a minute.

Now Click on the Create Device tab. Fill out the following fields. (Thanks again Strangely)
Description: DSC
UpnpDevFilename: D_DSCAlarmPanel1.xml
UpnpImplFilename: I_DSCAlarmPanel1.xml
IpAddress: 192.168.1.xx:xxxx (IP address to your WIZnet & Port Number)
Room: Alarm
Click on Create Device and give it another minute.

Here is an issue I came across, the Save option, the needed System & 6 Partition Devices where not being displayed in Vera. So, here is what I did. I clicked onto

one of the switches edit icon (the wrench). I changed the name of the switch & closed the popup window using the X button.  The Save option was now showing. I

clicked on it & gave it a few minutes to save & restart. Low & behold my Alarm System & all 6 Partitions devices were now displaying. Also, the DSC plugin icon was a

computer chip, instead of the round ball it was showing.  I opened my front door (zone 1) & it showed a guy running.

Hope this helps everyone else that has been pulling their hair!!  I have a couple of issues that need to be address, but at least it's now communicating! :)  






Title: Re: DSC plugin
Post by: computerjohn on March 14, 2011, 05:13:16 pm
I have also spoken to rakstar the author of Home Buddy (Android OS) a couple of weeks ago and he told me that when I finally had it working, for me to send him the needed info & he would code it in Home Buddy so, you can control the alarm features. :D
Title: Re: DSC plugin
Post by: computerjohn on March 14, 2011, 06:47:49 pm
OK, created the additional zones. So, I'm currently running 13 zones.
Title: Re: DSC plugin
Post by: strangely on March 14, 2011, 07:06:02 pm
A couple of problems though. I can not remote Arm. It stated it has been disabled.  So I went to the DSC plugin and changed the false to true, saved & it restarted. I then received an error message under DSC, Startup Lua failed when it started back up.  Did Guessed disable it for now?  Also, I have 13 Zone in my house..  Can I change it from 6 to 13 or has that been hard coded as well??

To enable remote arming you must actually write "disarm" where false was written rather than true. (dont ask... this is an MCV requirement)
Title: Re: DSC plugin
Post by: computerjohn on March 14, 2011, 09:05:51 pm
Are you kidding me? O K.. LOL...  Let me try it now.
Title: Re: DSC plugin
Post by: guessed on March 14, 2011, 09:13:19 pm
A couple of problems though. I can not remote Arm. It stated it has been disabled.  So I went to the DSC plugin and changed the false to true, saved & it restarted. I then received an error message under DSC, Startup Lua failed when it started back up.  Did Guessed disable it for now?  Also, I have 13 Zone in my house..  Can I change it from 6 to 13 or has that been hard coded as well??

To enable remote arming you must actually write "disarm" where false was written rather than true. (dont ask... this is an MCV requirement)

I committed a fix for the error-reporting problem, so that it'll give a nicer error/warning when the EnableRemoteArm (or EnableRemotePanic) options have incorrect values, per the comments in this posting:
    http://forum.micasaverde.com/index.php?topic=5154.msg35068#msg35068

It'll be picked up when we bundle (etc).  You'll still need to read the values from the [eventual] Wiki page, since I don't want to make it obvious how to enable it for the "casual" hacker.

The acceptable Parameter values for EnableRemoteArm are:
    <blank> - All Arming and Disarming functions are disabled.
    false - (default) same as above
    arm - All Arming, and Stay-Arming, functions are enabled.  Disarming is disabled.
    disarm - Allow all Arming and Disarming modes.

... or you can just read the source code, since it's all in plain-text anyhow  8)


The exact values are not outlined, but the need for a general mode to "enable" this type of functionality, and not have it enabled out of the box, stems from the "legal" verbiage in one of their earlier Wiki pages here:

    http://wiki.micasaverde.com/index.php/Luup_Priority_Projects
Title: Re: DSC plugin
Post by: computerjohn on March 14, 2011, 10:07:23 pm
Great understandable..  It works great my dear friend.  I posted in detail how to correct the issues I was having. The lower case file names were a pain & I could of only seen that is SSH.  I have all 13 zones running & seem to be working.  But, I will be keeping my eyes open..

I do have a few questions, 1: Can I rename the title names? So instead of Zone 01 it will read Zone 01 Entrance, Zone 2 Garage, etc..  2: In the DSC plugin, it states Door Sensors, Motion, & Smokes. If I have more than zone 1 & 2 as door sensors can I place them there, instead of being setup as a motion? (Example Door: 1,2,4,7) 3: How the heck can I tell if the alarm is armed? The pad lock always shows unlocked even when armed.. 4: Remote arming is not possible. I even tried to access it via http://cp.mios.com/mobile on my Android phone & it shows the zones, but under DSC & even System it displays On & Off, neither one works.  I just send my data to Rakstar of Home Buddy since that is the main Vera software I use on my Android phone, so he can get the arming fuctions to work, I hope..

If you have any other input that work be great or if you need some testing done, please let me know.  Now that I have it working I can be a lot more help now.

John

 

A couple of problems though. I can not remote Arm. It stated it has been disabled.  So I went to the DSC plugin and changed the false to true, saved & it restarted. I then received an error message under DSC, Startup Lua failed when it started back up.  Did Guessed disable it for now?  Also, I have 13 Zone in my house..  Can I change it from 6 to 13 or has that been hard coded as well??

To enable remote arming you must actually write "disarm" where false was written rather than true. (dont ask... this is an MCV requirement)

I committed a fix for the error-reporting problem, so that it'll give a nicer error/warning when the EnableRemoteArm (or EnableRemotePanic) options have incorrect values, per the comments in this posting:
    http://forum.micasaverde.com/index.php?topic=5154.msg35068#msg35068

It'll be picked up when we bundle (etc).  You'll still need to read the values from the [eventual] Wiki page, since I don't want to make it obvious how to enable it for the "casual" hacker.

The acceptable Parameter values for EnableRemoteArm are:
    <blank> - All Arming and Disarming functions are disabled.
    false - (default) same as above
    arm - All Arming, and Stay-Arming, functions are enabled.  Disarming is disabled.
    disarm - Allow all Arming and Disarming modes.

... or you can just read the source code, since it's all in plain-text anyhow  8)


The exact values are not outlined, but the need for a general mode to "enable" this type of functionality, and not have it enabled out of the box, stems from the "legal" verbiage in one of their earlier Wiki pages here:

    http://wiki.micasaverde.com/index.php/Luup_Priority_Projects
Title: Re: DSC plugin
Post by: computerjohn on March 14, 2011, 10:12:31 pm
Arming & disarming is working..  Thanks again my friend.. 

A couple of problems though. I can not remote Arm. It stated it has been disabled.  So I went to the DSC plugin and changed the false to true, saved & it restarted. I then received an error message under DSC, Startup Lua failed when it started back up.  Did Guessed disable it for now?  Also, I have 13 Zone in my house..  Can I change it from 6 to 13 or has that been hard coded as well??

To enable remote arming you must actually write "disarm" where false was written rather than true. (dont ask... this is an MCV requirement)

Title: Re: DSC plugin
Post by: computerjohn on March 14, 2011, 10:19:12 pm
Guessed,

Another thing I forgot if you can shine some light on this possible glitch.  If you unplug the WIZnet from the IT-100 interface (example: power, CAT5 cable, or serial cable) & reconnect it, the IT-100 no longer communicates in Vera. You can refresh the page & still nothing, but if I make a change that requires me to save & Vera goes through it's loading process, it starts to communicate again. Any ideas??
Title: Re: DSC plugin
Post by: guessed on March 14, 2011, 10:26:56 pm
Great understandable..  It works great my dear friend.  I posted in detail how to correct the issues I was having. The lower case file names were a pain & I could of only seen that is SSH.  I have all 13 zones running & seem to be working.  But, I will be keeping my eyes open..
Yeap, the lowercase ones come from the the "MiOS Catalog" version of the plugin.  Since I branched the code completely, I chose to rename them so they could [theoretically] sit side-by-side in any deployment.

Quote
I do have a few questions, 1: Can I rename the title names? So instead of Zone 01 it will read Zone 01 Entrance, Zone 2 Garage, etc.. 
It sources the Name(s) from the Panel itself.  If you change them there (with some vendor-spec tool that @strangely uses) then it will pick them up next time a (Save) operation occurs, or Vera reboots... whichever comes first ;-)

Quote
2: In the DSC plugin, it states Door Sensors, Motion, & Smokes. If I have more than zone 1 & 2 as door sensors can I place them there, instead of being setup as a motion? (Example Door: 1,2,4,7)
Each "type" is represented by a corresponding parameter.  A given Zone can only appear in one of these parameters (not validated, currently, but required) and each Parameter is a comma-separated list of Zone #'s.

I default these a certain way, upon the initial plugin startup, to give users an idea of how they can change them.

You can have as many Door sensors as you want, just use a comma-list of them in the Parameter value.

Quote
3: How the heck can I tell if the alarm is armed? The pad lock always shows unlocked even when armed..
The Buttons light up "green" in the Dialog when a certain mode is in place.  If it's Armed, then the (Arm) button will light up green.  This can take 30 seconds (or longer) depending upon how long the exit delay is.

The Padlock itself will never show "locked" since I haven't go that combo working just yet.

Quote
4: Remote arming is not possible. I even tried to access it via http://cp.mios.com/mobile on my Android phone & it shows the zones, but under DSC & even System it displays On & Off, neither one works.  I just send my data to Rakstar of Home Buddy since that is the main Vera software I use on my Android phone, so he can get the arming functions to work, I hope..
Yeap, that's why we've been working on standardizing the interface for an Alarm "Partition".  Without that, no-one can build a UI to represent this function.

The first step is standardization, the next is implementing the panels against that standard, and the last is having the Control Points (SQRemote, Home Buddy, etc, etc) implement the spec with a fancy widget.

Right now, my focus is on implementing the "spec" for both the DSC and the Paradox Alarm units.

Separately, I've also let the SQRemote lads know about this effort, incase they want to build a device-specific UI for it.

As a fall-back, it's Scene-aware, so you can build scene buttons that do things like Arming (etc), and then call them from any Control Point that can invoke scene actions (short-term work-around)
Title: Re: DSC plugin
Post by: guessed on March 14, 2011, 10:42:45 pm
Guessed,

Another thing I forgot if you can shine some light on this possible glitch.  If you unplug the WIZnet from the IT-100 interface (example: power, CAT5 cable, or serial cable) & reconnect it, the IT-100 no longer communicates in Vera. You can refresh the page & still nothing, but if I make a change that requires me to save & Vera goes through it's loading process, it starts to communicate again. Any ideas??
Not sure, but I don't think that MiOS (particularly the newer builds) is as resistant as it should be to those events.  If you remove the USB-end of the RS-232 cable, you'll definitely have a problem, but removing the other end should fix itself when it's reconnected.

For the Network stuff it should reconnect, over time, but recent MiOS builds seem not to be doing that anymore (not sure why).  I have all my Network gear on 12v BBackup (for 12-16 hours of power) so I won't see that problem... most of the time, but I do see it during the development processes.
Title: Re: DSC plugin
Post by: guessed on March 14, 2011, 10:47:32 pm
oh, and if there are questions on the common/core API spec by the CP authors (and there will be), these should be driven to the "Alarm Panels and Interface standardization" thread here:

    http://forum.micasaverde.com/index.php?topic=3713.45

so they're centrally answered for all to discuss/comment on, etc, etc.
Title: Re: DSC plugin
Post by: computerjohn on March 14, 2011, 10:56:54 pm
Each Zone is named in the panel (example: Front Door, Garage, Basement, etc), but it did not bring that over to Vera of that's what you mean. 

Also, Arm is always green in Vera even when disarmed, thus why I have no idea when the system is armed without going into the System Device to see it's status.

I have attached pics..

Quote
I do have a few questions, 1: Can I rename the title names? So instead of Zone 01 it will read Zone 01 Entrance, Zone 2 Garage, etc.. 
It sources the Name(s) from the Panel itself.  If you change them there (with some vendor-spec tool that @strangely uses) then it will pick them up next time a (Save) operation occurs, or Vera reboots... whichever comes first ;-)

Quote
3: How the heck can I tell if the alarm is armed? The pad lock always shows unlocked even when armed..
The Buttons light up "green" in the Dialog when a certain mode is in place.  If it's Armed, then the (Arm) button will light up green.  This can take 30 seconds (or longer) depending upon how long the exit delay is.

The Padlock itself will never show "locked" since I haven't go that combo working just yet.

Quote
4: Remote arming is not possible. I even tried to access it via http://cp.mios.com/mobile on my Android phone & it shows the zones, but under DSC & even System it displays On & Off, neither one works.  I just send my data to Rakstar of Home Buddy since that is the main Vera software I use on my Android phone, so he can get the arming functions to work, I hope..
Yeap, that's why we've been working on standardizing the interface for an Alarm "Partition".  Without that, no-one can build a UI to represent this function.

The first step is standardization, the next is implementing the panels against that standard, and the last is having the Control Points (SQRemote, Home Buddy, etc, etc) implement the spec with a fancy widget.

Right now, my focus is on implementing the "spec" for both the DSC and the Paradox Alarm units.

Separately, I've also let the SQRemote lads know about this effort, incase they want to build a device-specific UI for it.

As a fall-back, it's Scene-aware, so you can build scene buttons that do things like Arming (etc), and then call them from any Control Point that can invoke scene actions (short-term work-around)
Title: Re: DSC plugin
Post by: computerjohn on March 14, 2011, 11:00:05 pm
So I should post all questions & problems there correct?

oh, and if there are questions on the common/core API spec by the CP authors (and there will be), these should be driven to the "Alarm Panels and Interface standardization" thread here:

    http://forum.micasaverde.com/index.php?topic=3713.45

so they're centrally answered for all to discuss/comment on, etc, etc.

Title: Re: DSC plugin
Post by: computerjohn on March 14, 2011, 11:05:29 pm
Even after I power cycled Vera it still shows all my zones arm in green and my alarm is not armed.
Title: Re: DSC plugin
Post by: strangely on March 14, 2011, 11:34:02 pm
The zone buttons for arm and disarm are independent of the alarm state. They are there so that they can be used for Vera scene automation like you would use any other type of sensor in Vera.
 If you want these to actually arm or disarm based on the alarm state then you will have to create a scene to do this.
Title: Re: DSC plugin
Post by: guessed on March 14, 2011, 11:44:04 pm
So I should post all questions & problems there correct?

oh, and if there are questions on the common/core API spec by the CP authors (and there will be), these should be driven to the "Alarm Panels and Interface standardization" thread here:

    http://forum.micasaverde.com/index.php?topic=3713.45

so they're centrally answered for all to discuss/comment on, etc, etc.


No.

Your questions will related to the specifics of the DSC Implementation.

@rakstar, who is a CP (Control Point) owner, will have questions about the common Specification.  He should direct his questions to the core/common SPEC thread as I posted above.

Similarly, others CP owners would do the same, so they can share experiences about writing the control, and the folks there (including me) can adapt the core/comment spec as needed.
Title: Re: DSC plugin
Post by: computerjohn on March 15, 2011, 03:02:50 am
No that's not what I'm referring to, guessed stated that arm button lit in green stated that the alarm is armed & that is not the case. By looking at the Dashboard you can not tell if the alarm is armed or not, without going into the System Device & check the status there.

The zone buttons for arm and disarm are independent of the alarm state. They are there so that they can be used for Vera scene automation like you would use any other type of sensor in Vera.
 If you want these to actually arm or disarm based on the alarm state then you will have to create a scene to do this.
Title: Re: DSC plugin
Post by: strangely on March 15, 2011, 03:36:23 am
Are you sure it doesn't show?

I just tested mine in stay mode and it indicates in 2 places if active or not! I only see Green indications in the second screenshot anyway.
Title: Re: DSC plugin
Post by: strangely on March 15, 2011, 04:15:56 am
Also, for the Zone label problem, you can also try the following to broadcast the labels:

*8[Installer code]*998*

If you have more than one keypad then you must do this from the one it was programmed from originally as the labels are held there it seems.

I have no idea if the above will work, but it seems for the label broadcast with the IT100 to work, I guess the labels need to be stored on the Alarm Panel itself perhaps and not the keypads? I programmed mine through the DLS tool as I didn't have a supporting alpha keypad at the time (I've since added one).

I have no idea if the above will store them on the panel also after doing this (I'd hope so?), but if it does then you will just need to hit the MiOS engine refresh button and wait for it to reload! I also find with Google chrome that (most likely the same with other browsers too) that once you've refreshed the MiOS engine, then you also have to a browser refresh to get them to appear.
Title: Re: DSC plugin
Post by: techsan on March 16, 2011, 10:56:04 pm
Eureka!!  ;D

It finally works! Imagine my shock this time when clicking the "ARM" button and hearing the alarm panel beep at me! @Guessed, great job on the new build, you and @Strangely have my many thanks for working on this endeavor!

Just as an FYI, with the new build, when I removed the null modem adapter and rebooted the Vera it worked like a charm. I am using the Monoprice USB to Serial adapter that comes up as PL2303 in Vera.

Thanks Again!
Title: Re: DSC plugin
Post by: strangely on March 17, 2011, 01:17:58 am
Great news!

Sorry about the null modem adapter, that may have been my fault to tell you to use it!  8)
Title: Re: DSC plugin
Post by: computerjohn on March 18, 2011, 12:58:09 am
Ah ok. I see status result on the button.  I still think either color coded status (Green for disarm/ready, Red for armed & perhaps Yellow for stay), just for examples or graphic icons. It would stand out a bit more.  Just an idea..  ;)  I'm referring to each Zone that the Arm is colored green on all of them & they system is disarmed.



Are you sure it doesn't show?

I just tested mine in stay mode and it indicates in 2 places if active or not! I only see Green indications in the second screenshot anyway.
Title: Re: DSC plugin
Post by: guessed on March 18, 2011, 01:14:21 am
We have extremely limited control over the UI elements, their colors/images, etc.  The button highlight color is green, and that's it.  There's no control over images, personalized ones, etc, etc.

For the Zones, the Arm/Bypass options aren't associated with the Partition's Arming state at all.

Folks tend to use these for Scene-scripting purposes, so this Panel code doesn't do anything with them.  There's also no way for me to remove them from the UI as their a standard component (as required by the Wiki posting above)
Title: Re: DSC plugin
Post by: computerjohn on March 18, 2011, 01:23:25 am
Wow, they are pretty strict on this huh?  Whatever happened to it being open source? LOL..

We have extremely limited control over the UI elements, their colors/images, etc.  The button highlight color is green, and that's it.  There's no control over images, personalized ones, etc, etc.

For the Zones, the Arm/Bypass options aren't associated with the Partition's Arming state at all.

Folks tend to use these for Scene-scripting purposes, so this Panel code doesn't do anything with them.  There's also no way for me to remove them from the UI as their a standard component (as required by the Wiki posting above)
Title: Re: DSC plugin
Post by: mcvovidiu on March 18, 2011, 10:56:01 am
Hi computerjohn,

There are pieces which are open source along with their copyrights and there are parts which are not open source. Of course OpenWRT's files and most of the shell files are viewable and editable at your own risk, but there is still a lot of work from our company which is not open source and I think will never be. Who said to you MiCasaVerde/MiOS 's software is open source?

As for the image and css files, those can be editable as well if you want. Again, you do it on your own risk but most of them will be overwritten when upgrading.

Thanks!
Title: Re: DSC plugin
Post by: computerjohn on March 18, 2011, 01:04:01 pm
No problem thanks for the heads up..  Check out any review on a google search & mostly all state Mi Casa Verde Vera is open source. That being stated, one would be thinking "it was open source"..   ;)

Hi computerjohn,

There are pieces which are open source along with their copyrights and there are parts which are not open source. Of course OpenWRT's files and most of the shell files are viewable and editable at your own risk, but there is still a lot of work from our company which is not open source and I think will never be. Who said to you MiCasaVerde/MiOS 's software is open source?

As for the image and css files, those can be editable as well if you want. Again, you do it on your own risk but most of them will be overwritten when upgrading.

Thanks!
Title: Re: DSC plugin
Post by: grybrd on March 18, 2011, 04:57:36 pm
After lurking on this thread for awhile I find that I can't get a DSC system with RS232 without a hardwired keyboard.  Any thoughts from you guys????
Title: Re: DSC plugin
Post by: strangely on March 18, 2011, 05:10:37 pm
Are you referring to the Alexor system?

The Power series panels can also use wireless sensors, but you would have to hard wire the keypad. Only the Alexor system supports wireless keypads. Unfortunately it doesn't look like the IT100 is compatible with the Alexor either?!

If wiring a keypad near a door is an issue then you can also think about either using some existing wiring, or maybe just mount the keypad somewhere convenient. You can still arm and disarm via either a phone or one of the wireless keyfobs.
Title: Re: DSC plugin
Post by: grybrd on March 18, 2011, 05:13:23 pm
@ strangely   ... is your suggestion to use vera as the 'operational' keypad???
Title: Re: DSC plugin
Post by: computerjohn on March 18, 2011, 10:50:31 pm
Last month when I spoke to tech support at DSC, the tech had mentioned that the Alexor system could do remote access via a cell phone, but does require the GSM interface to make this possible. Just that interface is not cheap & does require a plan so it will work.  He did state that they were planning to release an update that would allow the power series to use that same option. For me, I like the IT-100 option.

 
Are you referring to the Alexor system?
You can still arm and disarm via either a phone or one of the wireless keyfobs.
Title: Re: DSC plugin
Post by: computerjohn on March 18, 2011, 10:57:31 pm
Do you have the Alexor system? If so, it is very limited on what it can do.  If you don't have it yet. I would go with a Power Series panel.  That's what I have.  I'm using both hard wired & wireless on it.  In my option, going completely wireless can be very probmatic. It's a good option when installing a wireless door sensor or wireless motion is not possible. Even on wireless motions, they use a lot more battery power & tend to time out.

After lurking on this thread for awhile I find that I can't get a DSC system with RS232 without a hardwired keyboard.  Any thoughts from you guys????
Title: Re: DSC plugin
Post by: strangely on March 18, 2011, 11:29:00 pm
@ strangely   ... is your suggestion to use vera as the 'operational' keypad???

You'll still need the keypad for programming (not for the faint hearted) but they keyfobs are ample for arming  / disarming and you can still use something else like SQremote or the vera dashboard if need be!
Title: Re: DSC plugin
Post by: strangely on March 18, 2011, 11:36:34 pm
Even on wireless motions, they use a lot more battery power & tend to time out.

The DSC wireless motions actually quote up to 9 years of battery life! I have one and the only disadvantage seems to be that its a little bit slower.
Title: Re: DSC plugin
Post by: computerjohn on March 19, 2011, 12:03:21 am
9 years huh? Wow..  Of course that will vary to traffic (lots of movement) & conditions (hot & cold).  I have a friend of mine that has an alarm company & does monitoring as well for years.  What he told me on the wireless motions that he does not like is.  Lets say you are arming your home & while exiting the wireless motion see you. It sleeps for 4 min or so. Now, most alarms are set to count down for let's say 30sec to a minute while arming. While armed that zone in which that wireless motion is still sleeping. The risk someone breaking in & the motion not tripping while sleeping does not set well.  Granted it's a long shot, but not impossible.

Have you seen this?

Even on wireless motions, they use a lot more battery power & tend to time out.

The DSC wireless motions actually quote up to 9 years of battery life! I have one and the only disadvantage seems to be that its a little bit slower.
Title: Re: DSC plugin
Post by: strangely on March 19, 2011, 12:14:21 am
I know it sleeps when the there is a lot of activity in a room; however not sure of how long etc and how it decides.

All moot anyway since I have a long exit delay due the amount of time required by my wife to arm, get the baby in the car, exit and then close the garage door again.
Title: Re: DSC plugin
Post by: computerjohn on March 19, 2011, 12:22:45 am
lol...  I hear yeah. 

I know it sleeps when the there is a lot of activity in a room; however not sure of how long etc and how it decides.

All moot anyway since I have a long exit delay due the amount of time required by my wife to arm, get the baby in the car, exit and then close the garage door again.
Title: Re: DSC plugin
Post by: computerjohn on March 19, 2011, 12:24:43 am
Also heads up. For all you Android users.  I downloaded Dolphin Browser HD tonight & it works with Vera very nicely. It formats the page view for easy scrolling (no need to move left & right), real-time status on modules (states when transmitting), & you can remote arm & disarm your alarm..  Just thought I'd pass this along to everyone. This will work for remote alarm access for now, until Home Buddy & others can make it possible with their apps. BTW, you can also edit your scenes & modules.  ;D
Title: Re: DSC plugin
Post by: strangely on March 19, 2011, 02:58:02 am
Also heads up. For all you Android users.  I downloaded Dolphin Browser HD tonight & it works with Vera very nicely. It formats the page view for easy scrolling (no need to move left & right), real-time status on modules (states when transmitting), & you can remote arm & disarm your alarm..  Just thought I'd pass this along to everyone. This will work for remote alarm access for now, until Home Buddy & others can make it possible with their apps. BTW, you can also edit your scenes & modules.  ;D
You can also create a scene to arm and disarm which should show up in the smartphone interface.
Title: Re: DSC plugin
Post by: computerjohn on March 19, 2011, 11:41:25 pm
Really...  I must try this..   ;D  Thanks for the heads up!
Title: Re: DSC plugin
Post by: computerjohn on March 19, 2011, 11:48:08 pm
Off subject,

Can anyone tell me HOW THE HECK, can a stop this darn forum from scrolling to the top of the message window while posting a message?  For example, while posting a message that is longer than the window body, it will scroll to the top & I'm typing blind. I scroll down in that window & it goes right back to the top. I have checked setting & nothing. Any ideas????
Title: Re: DSC plugin
Post by: computerjohn on March 20, 2011, 12:05:46 am
Hey strangely here's an odd one.

I have named my Zones twice (i thought perhaps I didn't click save the first time). I logged into my Vera & my names that I manually entered are gone again & each zone is back at Zone 01, Zone 02, etc...  Any ideas on why this keeps on happening??

If it was the panel, wouldn't it just name each zone with the custom programming that I have in that panel (Front Door, basement, etc...)?
Title: Re: DSC plugin
Post by: strangely on March 20, 2011, 12:56:03 am
Its renaming the devices with the ones stored on the Panel itself. Before I programmed mine with DSC DLS software, I noticed by default that they were already listed as Zone 01 Zone 02 etc on the programming template I downloaded from my panel.

I think that the labels you have are only held on the Keypads, and they don't get stored on the panel once programmed; the ones on the panel are the ones the IT100 uses!

You can try a label broadcast from the keypad it was programmed from, but I have no idea if this broadcast is also stored on the panel.

Label broadcast:
*8[Installer code]*998*
Title: Re: DSC Alarm Plugin
Post by: huogas on March 20, 2011, 10:36:42 am
Thanks.  I have the IT100 as well as the TL150, so I'm trying to port Javier's code over to the "standard" interface, as well as implement the TL150 code to the standard i'd mentioned earlier.

The actual way to connect Vera to DSC is by using IT-100 and WIZ110SR.
I was under impression that the TL150 could replace both, but someone mentioned that the TL150 would be unable to provide to Vera the individual states of the sensors (Zone).

Could someone clarify if there is something new on this since the upper quote was published (in October)?

Thanks
Title: Re: DSC vs GE
Post by: huogas on March 20, 2011, 11:15:20 am
http://forum.micasaverde.com/index.php?topic=5996.msg35717#msg35717
DSC vs GE considerations.
Title: Re: DSC plugin
Post by: strangely on April 02, 2011, 12:35:44 pm
@computerjohn,  @TimAlls, and anyone else that may have installed the previous versions:

@guessed has updated the plug-in as part of the V2 standardization. It would be good if you could all update to the latest version and provide some feedback.

I've been using it for 2 or 3 weeks and it works great for me!

Setup (still needs some work) and files contained here:

http://code.mios.com/trac/mios_dscalarmpanel
Title: Re: DSC plugin
Post by: TimAlls on April 02, 2011, 12:56:45 pm
I will definitely give it a try. We have a few more days before the wiring is complete but I will give you some feedback when we bring it online.
Thanks
Tim

Have you tried it with the .1234 firmware?
Title: Re: DSC plugin
Post by: strangely on April 02, 2011, 02:17:37 pm
Yep, for about a week.
Title: Re: DSC plugin
Post by: TimAlls on April 02, 2011, 05:34:40 pm
Ok good....I want to be on the same firmware!
I will push forward with wiring on Monday and bring it online....shouldn't take long. I will have some feedback monday night.
Regards
Tim
Title: Re: DSC plugin Smoke Alarm
Post by: rws on April 03, 2011, 07:26:08 am
Hi all,
Thanks for all the info posted. Its been a big help getting going.
I've got my dsc zones  and vera working together but, when I enter any number in for the smoke sensors (I have 2) the server busy message comes up, opening i/o comes up, and this repeats over and over. I assume its searching for the smoke sensors and can't find them.

I asked the alarm guy about the smoke sensors hook up and he said 'Smoke detectors are not part of the zone configuration.  They are connected to the AUX + and to the PGM2 terminals.  They, by code, are armed all of the time.  You cannot arm/disarm smoke detectors, so they work 24/7.'

So... how do I get the smoke sensors integrated/recognized?
Thanks!
 
Title: Re: DSC plugin Smoke Alarm
Post by: strangely on April 03, 2011, 12:08:54 pm
Hi all,
Thanks for all the info posted. Its been a big help getting going.
I've got my dsc zones  and vera working together but, when I enter any number in for the smoke sensors (I have 2) the server busy message comes up, opening i/o comes up, and this repeats over and over. I assume its searching for the smoke sensors and can't find them.

I asked the alarm guy about the smoke sensors hook up and he said 'Smoke detectors are not part of the zone configuration.  They are connected to the AUX + and to the PGM2 terminals.  They, by code, are armed all of the time.  You cannot arm/disarm smoke detectors, so they work 24/7.'

So... how do I get the smoke sensors integrated/recognized?
Thanks!
 
That's true about the smokes being armed all the time, but they still should have a zone number and a special zone definition that tells the system that they are smokes, so as to keep them armed all the time. For hard wired ones, the zone definition is 08, and wireless its 88. if you have a programming manual, then its covered in section 5!

Did you use the new V2 plugin linked in the setup guide on code.mios.com? (my link several posts back).

Are you sure you have the zone number for the smokes correct? You would need to enter the correct number, not just "any" number as you mentioned above. I assume they are both wired to the same PGM, and therefore they are probably configured as one zone!
Title: Re: DSC plugin
Post by: rws on April 04, 2011, 07:23:01 am
I used the version from mios market place looks to be v. .9?
When I go tothe alarm panel and access zones here's what I get
Zone 1   Entry Door
Zone 2 Garage
Zone 3 Dining Windows
Zone 4 Guest Bed windows
Zone 5 Den Windows
Zone 6 MBR windows
Zone 7 M bath windows
Zone 8 Lanai Doors
Zone 9 Motion sensor

I'm in process of getting a manual sent.
thanks again.
Title: Re: DSC plugin
Post by: computerjohn on April 04, 2011, 04:31:13 pm
Hey Strangely,

Ok, I'll try it tonight. I'm fighting a damn cold, so a bit under the weather. Now, can I just upload the new files and power cycle Vera or do I have to remove the config and ssh into Vera and remove the files?

@computerjohn,  @TimAlls, and anyone else that may have installed the previous versions:

@guessed has updated the plug-in as part of the V2 standardization. It would be good if you could all update to the latest version and provide some feedback.

I've been using it for 2 or 3 weeks and it works great for me!

Setup (still needs some work) and files contained here:

http://code.mios.com/trac/mios_dscalarmpanel
Title: Re: DSC plugin
Post by: strangely on April 04, 2011, 11:20:25 pm
@rws,

If you can, then I recommend that you uninstall it, and use the one that I linked several version back:
http://code.mios.com/trac/mios_dscalarmpanel

The one from the MiOS place has a few problems, namely:

PIN codes will be included in your logs, and therefor sent to MCV's servers.
Notifications don't work.

You can also grab the programming manual here:
http://download.homesecuritystore.com/downloadmanual.aspx?FileName=POWERSERIES-PC1832_Ref.pdf


Title: Re: DSC plugin
Post by: strangely on April 04, 2011, 11:31:15 pm
Hey Strangely,

Ok, I'll try it tonight. I'm fighting a damn cold, so a bit under the weather. Now, can I just upload the new files and power cycle Vera or do I have to remove the config and ssh into Vera and remove the files?


Sorry but you'll need to remove it all as there's a bunch of stuff contained in the user data, json files within vera that will most likely not play nice.
So uninstall, restart the MiOS engine, and then add the new files and recreate etc!

Your best bet is to make a backup first, and if anything goes wrong... such as a latent bug (perhaps exposed by your specific config), or user error ;) then at least you have a working configuration to go back to!
Title: Re: DSC plugin Smoke Alarm
Post by: rws on April 05, 2011, 11:56:24 am
Hi all,
Thanks for all the info posted. Its been a big help getting going.
I've got my dsc zones  and vera working together but, when I enter any number in for the smoke sensors (I have 2) the server busy message comes up, opening i/o comes up, and this repeats over and over. I assume its searching for the smoke sensors and can't find them.

I asked the alarm guy about the smoke sensors hook up and he said 'Smoke detectors are not part of the zone configuration.  They are connected to the AUX + and to the PGM2 terminals.  They, by code, are armed all of the time.  You cannot arm/disarm smoke detectors, so they work 24/7.'

So... how do I get the smoke sensors integrated/recognized?
Thanks!
 
That's true about the smokes being armed all the time, but they still should have a zone number and a special zone definition that tells the system that they are smokes, so as to keep them armed all the time. For hard wired ones, the zone definition is 08, and wireless its 88. if you have a programming manual, then its covered in section 5!

Did you use the new V2 plugin linked in the setup guide on code.mios.com? (my link several posts back).

Are you sure you have the zone number for the smokes correct? You would need to enter the correct number, not just "any" number as you mentioned above. I assume they are both wired to the same PGM, and therefore they are probably configured as one zone!
Got the new version installed. Everything seems to work well but it still can't find smokes. I put in 08 for smokes (there are 2) and the program doesn't run endlessly like it did if I entered 1 or 1,2 but still nothing shows up as far as smoke detectors.
Also, i have renamed the zones on the UI4 but as soon as I opne or close a zone they revert back to Zone 1 Zone 2 etc. Any way to get the zone names to stay changed on the UI4 interface?
Thanks again
Title: Re: DSC plugin
Post by: rws on April 05, 2011, 12:19:56 pm
Plugged in "F' for smoke zone 'number' and it created Zone F .
Title: Re: DSC plugin
Post by: computerjohn on April 05, 2011, 01:32:02 pm
Grrrr..  :(  Ok, I'm home sick today, so I'll give it a try today.  Do I have to delete the files via SSH as well or will it overwrite?

Thanks Buddy,

John

Hey Strangely,

Ok, I'll try it tonight. I'm fighting a damn cold, so a bit under the weather. Now, can I just upload the new files and power cycle Vera or do I have to remove the config and ssh into Vera and remove the files?


Sorry but you'll need to remove it all as there's a bunch of stuff contained in the user data, json files within vera that will most likely not play nice.
So uninstall, restart the MiOS engine, and then add the new files and recreate etc!

Your best bet is to make a backup first, and if anything goes wrong... such as a latent bug (perhaps exposed by your specific config), or user error ;) then at least you have a working configuration to go back to!
Title: Re: DSC plugin
Post by: computerjohn on April 05, 2011, 03:27:27 pm
Ok, I removed the devices & deleted the plugin files via SSH just to be sure.  Just add the additional zones & waiting for Vera to start back up so I can test it.
Title: Re: DSC plugin
Post by: computerjohn on April 05, 2011, 03:50:15 pm
So far so good..  Remote arming is working & each zone show movement when tripped.  What were the changes made & are they visible or just the scenes in coding?
Title: Re: DSC plugin
Post by: TimAlls on April 05, 2011, 06:58:15 pm
Yehhhhhhh!
Upgraded to firmware ....1234......no problems yet.
Deleted old Alarm files
Added new Alarm files
Setup new device
copy and pasted XML names into slots as instructed
Added more doors
Added a motion sensor
All is well so far.
Thanks!
Thanks!
Thanks!
Tim Alls
AllSeas Yachts
Title: Re: DSC plugin
Post by: strangely on April 05, 2011, 10:34:07 pm
So far so good..  Remote arming is working & each zone show movement when tripped.  What were the changes made & are they visible or just the scenes in coding?
I forget now, mostly V2 standardization, updates to the arming/control screens, along with a sprinkle of new error / status messages, that can be displayed in the top corner of the dashboard.
... Oh and you can now set the time again!

@guessed would know for sure if there was anything really different, but I know it was a lot of work!
Title: Re: DSC plugin Smoke Alarm
Post by: strangely on April 05, 2011, 10:47:06 pm
Got the new version installed. Everything seems to work well but it still can't find smokes. I put in 08 for smokes (there are 2) and the program doesn't run endlessly like it did if I entered 1 or 1,2 but still nothing shows up as far as smoke detectors.
Also, i have renamed the zones on the UI4 but as soon as I opne or close a zone they revert back to Zone 1 Zone 2 etc. Any way to get the zone names to stay changed on the UI4 interface?
Thanks again
I just tried to rename mine to something else, and it does revert back to what I stored on the panel itself.

Zone 1 etc is the default name thats stored, and because the plugin reads these every time it starts (like after you rename and save), it then pulls the real name again. The dashboard then updates the next time a change occurs like you refresh etc.

Title: Re: DSC plugin
Post by: TimAlls on April 10, 2011, 12:12:38 pm
Reviving the thread for an update and question.....
I have been running for over a week with the new plugin and all is well!
I noticed today when i was accessing the system that we had an AC power failure over the weekend and the alarm picked it up and displayed it in the upper right hand box.
Question
How can I trigger and event so that power failures are recoded into MIOS for reference?
This would be good information to know.
Regards
Tim Alls
AllSeas Yachts
Title: Re: DSC plugin
Post by: strangely on April 10, 2011, 12:56:41 pm
Normally this is what the VendorCode support is for and there is some good and bad news here.

The bad news is that these don't currently work with Partition level codes, and AC power loss is one of them (code 802). In fact you just reminded me about this as I was supposed to raise a ticket for it.

The good news, that they do work for Panel level codes, and so you could create one for the trouble light being illuminated (840) which will work.
You won't know that its definitely an AC trouble, but at least it can alert you that something is wrong generally (e.g, phone line if used, AC loss, battery low, etc etc)


You should now get an notification for anything that throws the trouble light on.
Title: Re: DSC plugin
Post by: TimAlls on April 10, 2011, 01:11:25 pm
That's good enough for me....and no code to write!
Thanks again....
Regards,
Tim
Title: Re: DSC plugin Smoke Alarm
Post by: strangely on April 10, 2011, 01:34:39 pm
Also, i have renamed the zones on the UI4 but as soon as I opne or close a zone they revert back to Zone 1 Zone 2 etc. Any way to get the zone names to stay changed on the UI4 interface?
Thanks again

@rws

Can you try to do a label broadcast from the keypad that your labels were programmed from (assuming you have more than one) by entering the following:
*8[Installer code]*998*

I'd like to know if this fixes your Zone label issue where they revert to "Zone 1"... etc.
After doing this, you will need to restart the engine using the refresh icon in the dashboard, followed by a browser refresh or a zone trip.
Title: Re: DSC plugin Smoke Alarm
Post by: rws on April 10, 2011, 09:23:12 pm
Also, i have renamed the zones on the UI4 but as soon as I opne or close a zone they revert back to Zone 1 Zone 2 etc. Any way to get the zone names to stay changed on the UI4 interface?
Thanks again

@rws

Can you try to do a label broadcast from the keypad that your labels were programmed from (assuming you have more than one) by entering the following:
*8[Installer code]*998*

I'd like to know if this fixes your Zone label issue where they revert to "Zone 1"... etc.
After doing this, you will need to restart the engine using the refresh icon in the dashboard, followed by a browser refresh or a zone trip.
Won't be back there for a month but will give it a try then and let you know.
Title: Re: DSC plugin
Post by: computerjohn on April 12, 2011, 06:34:00 pm
I'm having some major issues. Started last night, on the dashboard it stated "DSC Startup Lua Failed".  So, I tried to power cycling Vera, DSC panel with IT-100 interface & WIZnet. Still same problem. I changed a description of one of my switches & told it to save & the error went away & was communicating with Vera once again.

I set the alarm this morning, still fine & Vera notified me it was armed. Got home a little while ago & notified me again that it disarmed. Then all hell broke loose. One text told me alarmed armed "which it wasn't", then received 5 other texts within 7min alarm disarmed. Now the dashboard is stating "DSC Startup Lua Failed" again.  What the heck is going on???

I had no issues with the other plug-in.  It is the plug-in or Vera?  I had another weird text at 6:20am that my pump in my 29gal fish tank turned off & then at 6:36am my pump in my 29gal fish tank turned on. It's suppost to be on all the time.    

Any ideas???
Title: Re: DSC plugin
Post by: strangely on April 12, 2011, 07:26:30 pm
Do you have any scenes that do the arming or disarming, perhaps any that are based on schedules?

The notifications at the moment are not reliable anyway, so I would not count that. However, regarding the plug-in failing to run, I get this occasionally, and its normally the result of the LuaUpnP process restarting itself due to a watchdog or something else. I also get random plugin failures with a few of my other RS232 devices, and so I don't think its the DSC plugin to blame here!

I'm currently trying to MCV to look into this also.

Do you have Verbose logging turned on by chance?
Title: Re: DSC plugin
Post by: computerjohn on April 12, 2011, 10:37:26 pm
That's the odd thing, no I don't have any scenes arming or disarming. As for the notification, is that a plug-in or Vera issue? 

Verbose logging turned on? I do have some logging, but I don't think I have the detail one on.  I'll have to double check..

Do you have any scenes that do the arming or disarming, perhaps any that are based on schedules?

The notifications at the moment are not reliable anyway, so I would not count that. However, regarding the plug-in failing to run, I get this occasionally, and its normally the result of the LuaUpnP process restarting itself due to a watchdog or something else. I also get random plugin failures with a few of my other RS232 devices, and so I don't think its the DSC plugin to blame here!

I'm currently trying to MCV to look into this also.

Do you have Verbose logging turned on by chance?
Title: Re: DSC plugin
Post by: TimAlls on April 14, 2011, 02:33:57 pm
I added the notification to my system for the trouble light but my Email quickly started to fill up with notice after notice! Is there a way for it to send it out once?
Regards
Tim Alls
AllSeas Yachts
Title: Re: DSC plugin
Post by: strangely on April 14, 2011, 05:58:27 pm
Sounds like you maybe having some troubles :)
On a serious note, are you having something else going on that maybe triggering the Trouble code, or was it that power was lost for a while and it kept sending it repeatably until it was restored? My guess is that the panel sends out the same code at set intervals until its cleared perhaps.

I'll try it on mine over the weekend and see if I can see the same behavior.
Title: Re: DSC plugin
Post by: TimAlls on April 14, 2011, 06:32:44 pm
No....no trouble here....just having fun with all these cool boys toys!
I left the trouble light on as a test because if I am away this is exactly what will be going out on the system. I think you are right....the notifications went out on a timed interval. I will check and see if there are any programming options as far as broadcasting. Does the Plugin Code generate an event everytime the message is recieved? One way to do it is to trigger events when the trouble light changes it's state.....
What do you think?
Regards
Tim
Title: Re: DSC plugin
Post by: strangely on April 15, 2011, 12:56:54 am
My guess is that the panel keeps sending it until it clears. I'll tail the log over the weekend with the trouble active and see if this is corroborated.

If this is true, then I doubt there will be any programming options to change this in the panel.
Title: Re: DSC plugin
Post by: TimAlls on April 15, 2011, 11:02:23 am
I will tie into the serial stream today and read it straight from the IT100
I will report back tonight with my findings.
Regards
Tim Alls
AllSeas Yachts
Title: Re: DSC plugin
Post by: TimAlls on April 16, 2011, 02:06:52 pm
The problem turns out to be more complicated....the system messages must be repeated when a zone is tripped...With notification of a System Event is on the message repeats every hour or so but when zones are tripped I get messages for both zone tripped and system error#.....I still need to look at the raw serial stream to validate......more to come.
Regards
Tim Alls
AllSeas Yachts
Title: Re: DSC plugin
Post by: guessed on April 16, 2011, 04:25:56 pm
You can see the Raw versions of these float by if you "tail -f LuaUPnP.log" from within Vera with Verbose logging enabled.

With the Beta versions of the DSC Alarm Plugin, you should be running with Verbose Logging anyhow, just in case something goes amiss and it needs to be debugged.
Title: Re: DSC plugin
Post by: TimAlls on April 16, 2011, 05:05:42 pm
Thanks,
I do have logging enable for the reasons you mentioned....
I will take a look. So far this is the only issue I have had and it really is a minor thing.
I am still on .1234 but with no door locks and ZWave running secondary so I don't run into many problems.
I have never looked at the Logs before....under a Windows machine do I need to download a program to link me to the console?
Also....I was going through the code for the plugin....over a thousand lines of code...wow! Made me think though, is this considered P Code that requires a lot of overhead to run like Basic? No compiled C code, DLLs or such for Vera? This is not my area of expertise but if one has 4 or 5 plugins running doesn't it bottle neck Vera?
Regards
Tim Alls
AllSeas Yachts
Title: Re: DSC Alarm System plugin
Post by: guessed on April 18, 2011, 12:25:35 am
Also....I was going through the code for the plugin....over a thousand lines of code...wow! Made me think though, is this considered P Code that requires a lot of overhead to run like Basic? No compiled C code, DLLs or such for Vera? This is not my area of expertise but if one has 4 or 5 plugins running doesn't it bottle neck Vera?
It's more about how much they do, how "active" they are, than how big the codebase is - although memory is limited so there's an ultimately limit to how many plugins that can be put in memory at the same time.

That said, I have the following Plugins running in my system:
a) 2x Alarm Systems (Paradox and DSC)
b) 2x SQBlaster drivers
c) 1x SQController driver (with it's own 2x Blaster drivers)
d) ~10 IR Plugins
e) 1x DirecTV Plugin
f) 1x Panasonic Plugin
g) 1x HDMI-CEC Plugins


again, most of these arent "active" in what they do, or the IO they handle, so things generally just tick along.

The DSC code is largely a set of jump-tables.  So for any given message that comes in, there's not that much code in the code-path that gets executed.

I see more [large] CPU spikes on my box from the log compression and other "background" maintenance stuff.  Most of my plugins are really just blocked for IO, only to wake for a short time before going back to sleep again.  

The Brultech will eventually challenge that, or I'll have to reset it to present it's data ~1m instead of ~1s
Title: Re: DSC Alarm System plugin
Post by: Ambrotos on April 18, 2011, 11:20:11 am
I've installed and configured the new plugin as described here:
http://code.mios.com/trac/mios_dscalarmpanel

All of my Zones are created properly, and they trigger as expected as I walk through the house and open/close doors. So, I know communication with the panel is working. I have 2 problems I was hoping someone could help with.

First, whenever I try to set EnableRemoteArm to "stay" (as described in the Trac page) I get the error "EnableRemoteArm parameter must be either blank, false or a value from the wiki...". For now, I've set it to "arm" and it's accepted it. Has anyone else seen this?

Secondly, I don't seem to be able to control the panel. On partition 1, when I select the PIN Options dropdown, type in my PIN, and hit Arm, nothing at all happens. I remember reading with the old DSC plugin you had the add "00" to the end of 4 digit PINs. Is that still the case? Either way, I don't imagine away arming should require the PIN. Anyone have any suggestions?

Thanks,

-A
Title: Re: DSC Alarm System plugin
Post by: guessed on April 18, 2011, 11:28:40 am
The wiki page is incorrect.  "stay" is not an accepted value (it's a clone of the Paradox Wiki page, where it does support that value.... but not for much longer)

The codebase now "pads" with 0's, if more digits are required. This is the config that I run in, so that part is definitely working.

@strangely may have a better idea on why it's not arming though.
Title: Re: DSC Alarm System plugin
Post by: TimAlls on April 18, 2011, 07:34:24 pm
I am new to logging....documentation say the password to the console is on the back of the VeraII....The only password is the WIFI password.....are they the same?
Regards
Tim Alls
AllSeas Yachts
Title: Re: DSC Alarm System plugin
Post by: huogas on April 18, 2011, 09:14:05 pm
Yes. It doesn't work ?
Title: Re: DSC Alarm System plugin
Post by: guessed on April 18, 2011, 09:24:14 pm
and if you haven't done it before, and would rather a browser-interface, the newer MiOS Revs have this:

     http://192.168.x.xxx/cgi-bin/cmh/log.sh?Device=LuaUPnP

it'll display "in-browser" and scroll by as the log output is produced.  Not sure when it was introduced, since it's not formally documented (etc)
Title: Re: DSC Alarm System plugin
Post by: TimAlls on April 18, 2011, 09:59:14 pm
Yes. It doesn't work ?
No it doesn't.....but Guessed method works...
Thanks!
Tim
Title: Re: DSC Alarm System plugin
Post by: strangely on April 18, 2011, 10:45:15 pm
The wiki page is incorrect.  "stay" is not an accepted value (it's a clone of the Paradox Wiki page, where it does support that value.... but not for much longer)
@strangely may have a better idea on why it's not arming though.

Now although I plagiarized a lot, I don't think this was something from your Paradox wiki page (I think this was added from email information)

@Ambrotos,

Can you try disarm and see if that works?
Title: Re: DSC Alarm System plugin
Post by: huogas on April 18, 2011, 11:03:45 pm
and if you haven't done it before, and would rather a browser-interface, the newer MiOS Revs have this:

     http://192.168.x.xxx/cgi-bin/cmh/log.sh?Device=LuaUPnP

it'll display "in-browser" and scroll by as the log output is produced.  Not sure when it was introduced, since it's not formally documented (etc)

WOW! Works perfectly! Thanks guessed.
Title: Re: DSC Alarm System plugin
Post by: guessed on April 18, 2011, 11:07:57 pm
The wiki page is incorrect.  "stay" is not an accepted value (it's a clone of the Paradox Wiki page, where it does support that value.... but not for much longer)
@strangely may have a better idea on why it's not arming though.

Now although I plagiarized a lot, I don't think this was something from your Paradox wiki page (I think this was added from email information)

;D, sorry about that.  I thought you'd copied that also.  I nuked that parameter-mode a long-long time ago due to problems in supporting it on the DSC Panel, esp once we moved to more modes than just Stay and Arm.  I must have forgotten to send you a PM on that one (I changed a lot in this code)
Title: Re: DSC Alarm System plugin
Post by: Ambrotos on April 19, 2011, 09:09:27 pm
Sorry for the delay in my reply.

@guessed: I changed the variable to be "disarm". Typing in the PIN and pressing disarm from the PIN options dropdown doesn't do anything either. Also, the Partition's status always shows "Ready", even when the system is armed.

-A
Title: Re: DSC Alarm System plugin
Post by: strangely on April 19, 2011, 11:06:29 pm
Stupid question and I need to ask... but I take it you saved after entering disarm?
Title: Re: DSC Alarm System plugin
Post by: TimAlls on April 20, 2011, 10:50:19 am
Just a quick update.....
I am still running .1234 firmware and everything seems to be good. The logging shows some error messages coming in from the serial interface on two second intervals but is because the system is still being wired and I am just running test right now.
One thing I wanted feedback on is the setup I have on my main entry door....I have programmed the DSC interface to think my door sensor is a motion sensor. Then I set it up to fire up the camera and record two seconds of JPGs and store them.....it gives me a record of everyone who passed through the door and when! For my application a real plus. Can you think of any down sides to this from a programming stand point?
Regards
Tim Alls
AllSeas Yachts
Title: Re: DSC Alarm System plugin
Post by: Ambrotos on April 20, 2011, 11:00:44 am
@strangely: hahaha... yes, I saved. Don't blame you for asking though  :)

Is there a particular log file or something that I should tail which may be helpful?

-A
Title: Re: DSC Alarm System plugin
Post by: strangely on April 20, 2011, 11:11:08 am
You'll want to turn on verbose logging and then tail /tmp/log/cmh/LuaUPnP.log
Title: Re: DSC Alarm System plugin
Post by: Ambrotos on April 20, 2011, 11:59:46 am
@strangely:

So, when I press Arm in the PIN Options dropdown, I see the following logged (obviously, I blanked the PIN)


Code: [Select]
10      04/20/11 11:50:12.140   JobHandler_LuaUPnP::HandleRequest id lu_action request pMem 0x949000/9736192 diff: 2150400 <0x4808>
10      04/20/11 11:50:12.230   sbrk JobHandler_LuaUPnP::HandleActionRequest from IP:0.0.0.0 pMem 0x949000/9736192 diff: 2150400 <0x4808>
08      04/20/11 11:50:12.231   JobHandler_LuaUPnP::HandleActionRequest device: 33 service: urn:micasaverde-com:serviceId:AlarmPartition2 action: RequestArmMode <0x4808>
08      04/20/11 11:50:12.232   JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=33 <0x4808>
08      04/20/11 11:50:12.232   JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:AlarmPartition2 <0x4808>
08      04/20/11 11:50:12.233   JobHandler_LuaUPnP::HandleActionRequest argument action=RequestArmMode <0x4808>
08      04/20/11 11:50:12.233   JobHandler_LuaUPnP::HandleActionRequest argument State=Armed <0x4808>
08      04/20/11 11:50:12.234   JobHandler_LuaUPnP::HandleActionRequest argument PINCode=XXXX <0x4808>
08      04/20/11 11:50:12.235   JobHandler_LuaUPnP::HandleActionRequest argument rand=0.2039023097226611 <0x4808>
50      04/20/11 11:50:12.236   luup_log:26: DSCAlarmPanel: debug Action::RequestArmMode Armed <0x4808>
50      04/20/11 11:50:12.237   luup_log:26: DSCAlarmPanel: debug extractPartition: Partition 1 <0x4808>
25      04/20/11 11:50:12.238   luup_io_write 26 size: 12 <0x4808>
51      04/20/11 11:50:12.240   0x30 0x33 0x33 0x31 0x3X 0x3X 0x3X 0x3X 0x30 0x30 0x46 0x39 0xd 0xa (0331XXXX00F9\r\n) <0x4808>
25      04/20/11 11:50:12.241   luup_io_write 26 result: 1 <0x4808>
10      04/20/11 11:50:12.357   luvd_get_info_data_request creating file buffer /data_request?id=lu_action&output_format=json&DeviceNum=33&serviceId=urn:micasaverde-com:serviceId:AlarmPartition2&action=RequestArmMode&State=Armed&PINCode=XXXX&rand=0.2039023097226611 pMem 0x949000/9736192 diff: 2150400 <0x4808>

Can you glean anything interesting from this? From the log, it looks to me like the plugin thinks communication with the panel went fine.

-A
Title: Re: DSC Alarm System plugin
Post by: computerjohn on April 20, 2011, 10:50:55 pm
Hello Guys,

Anyone update to the new 1.1.1245 beta yet?  It was released to everyone today, any ill effects with the DSC plug-in??
Title: Re: DSC Alarm System plugin
Post by: guessed on April 21, 2011, 08:39:10 am
Ambrotos,
Can I get a few more log lines after what you've shown?

I'd like to see what then panel responds with after the cmd is sent. Typically this would include log lines starting with 52.
Title: Re: DSC Alarm System plugin
Post by: Ambrotos on April 21, 2011, 10:39:04 am
@guessed:

I sent everything that I had. I tried again this morning, and waited for 60 seconds with nothing. The only message sent by the panel was the regular per-minute LCD date/time update message. Nothing at all starting with 52.

-A
Title: Re: DSC Alarm System plugin
Post by: guessed on April 21, 2011, 11:07:00 am
That's really odd.  When commands are sent, there are corresponding responses over the serial interface.  These come back (raw) as 52 in the log files, and then get processed by the DSC Alarm code.

Are your zones working correctly when you open/close them?  Are their status's being correctly reflected in Vera's dash? 

Ie the little red running man....
Title: Re: DSC Alarm System plugin
Post by: Ambrotos on April 21, 2011, 11:18:35 am
Yup, the zones update correctly. Also, the partition status updates properly when I arm/disarm the system from the keypad. It seems as though Vera's Rx is working properly, but Tx doesn't. For example, I don't think the "set time" option on the panel object works either.

-A
Title: Re: DSC Alarm System plugin
Post by: strangely on April 21, 2011, 11:27:58 am
Cable issue?
Title: Re: DSC Alarm System plugin
Post by: Ambrotos on April 21, 2011, 11:44:15 am
Yes, that's what I was wondering as well. But I've tested the Rx, Tx, and Gnd pins with a multimeter and they all work properly. It's just the IT-100 module, a manufactured (i.e. not home-made) null-modem cable, and a pl2302-based USB adapter, not a lot of uncertainty there.

I'll swap out the cable tonight and see if that helps, but I'm skeptical.

-A
Title: Re: DSC Alarm System plugin
Post by: strangely on April 21, 2011, 01:49:28 pm
You don't actually need a null modem cable as the IT100 already has the TX and RX swapped from the normal convention and requires a cable wired with pin 2>2, 3>3 and 5>5... The being said, I would expect it to not work at all!
Title: Re: DSC Alarm System plugin
Post by: computerjohn on April 21, 2011, 05:41:20 pm
Yes don't use a NULL modem cable. It should be straight thru. On mine, I have my WIZnet module connected to the IT-100 without a cable.
Title: Re: DSC Alarm System plugin
Post by: computerjohn on April 22, 2011, 12:11:16 am
Well, updated to the new 1.1.1245 version..  I'll test it out & see if there are any issues with the DSC plug-in.  I don't believe there should be any.  :)
Title: Re: DSC Alarm System plugin
Post by: computerjohn on April 22, 2011, 12:44:45 am
Hey I was reading all the changes made in the new Vera update. A whopping 99 changes, but one did catch my eye.

"The DSC plugin, and possibly others that use serial ports, did not work because the engine was trying to open the port twice. "

I wonder if this will fix the problem we have been getting from time to time with the plug-in not loading at times?
Title: Re: DSC Alarm System plugin
Post by: strangely on April 22, 2011, 03:36:18 am
No this was something different and it was actually fixed many many versions back! The change history doesn't show you what was fixed in each version, it just rolls and the list grows bigger with each release.
Title: Re: DSC Alarm System plugin
Post by: Ap15e on April 22, 2011, 08:22:58 am
You have to check the revision history of the Release Notes ...
Title: Re: DSC Alarm System plugin
Post by: strangely on April 22, 2011, 01:19:22 pm
Yes good point. although still not ideal, or easy to see! I'm also pretty sure that the changes span more versions than listed.
Title: Re: DSC Alarm System plugin
Post by: Kyle on April 24, 2011, 02:33:51 am
I've installed the files in the wiki and can arm/disarm the system fine. Like computerjohn, I'm unable to see the state the alarm is in(Armed, etc). Also if I trip a zone, I don't see the man running. Any ideas?

I've also looked through the logs and noticed a few things:

01      04/24/11 2:26:32.067    IOPort::Connect connect -1 127.0.0.1:3481 <0x4011>

01      04/24/11 2:26:36.172    LuaInterface::CallFunction-2 lu_incoming failed [string "..."]:830: bad argument #2 to 'format' (string expected, got nil) <0x4011>

Thanks!
-Kyle
Title: Re: DSC Alarm System plugin
Post by: guessed on April 24, 2011, 10:24:38 am
Kyle,
You'll need to enable Verbose logging in MiOS/Vera to get the more detailed logs.  It generally looks like the Plugin received an IO Command in an incorrect format, but the Verbose logging will tell us what it actually saw.
Title: Re: DSC Alarm System plugin
Post by: Kyle on April 24, 2011, 10:50:42 am
Kyle,
You'll need to enable Verbose logging in MiOS/Vera to get the more detailed logs.  It generally looks like the Plugin received an IO Command in an incorrect format, but the Verbose logging will tell us what it actually saw.

I turned on verbose logging, what parts of the log do you want me to paste to you?
Title: Re: DSC Alarm System plugin
Post by: guessed on April 24, 2011, 11:02:53 am
Lines starting with 5 (50, 51, 52) as well as the lines starting with 01 as you have above.  The 51 and 52 lines are the ones with the IO in them, there are others that might be interesting also but for now let's start with that.
Title: Re: DSC Alarm System plugin
Post by: Kyle on April 24, 2011, 12:11:29 pm
I searched through the log and here is what I've come up with. Thanks!

Title: Re: DSC Alarm System plugin
Post by: guessed on April 24, 2011, 02:52:55 pm
There are log lines missing.

Normally they'll come in tuples like this:
52   04/24/11 10:49:41.542   0x39 0x30 0x38 0x30 0x31 0x30 0x31 0x30 0x32 0x43 0x35 (908010102C5) <0x3c10>
50   04/24/11 10:49:41.543   luup_log:47: DSCAlarmPanel: debug processIncoming:: Command=908, Data='010102', Checksum=C5 <0x3c10>
50   04/24/11 10:49:41.544   luup_log:47: DSCAlarmPanel: debug Panel::Software Version 908 data: 010102 <0x3c10>


but you'll see that I'm sending an initialization command (to enumerate all the Zones/Partitions/etc) here:

51   04/24/11 10:49:41.400   0x30 0x30 0x32 0x39 0x32 0xd 0xa (00292rn) <0x402>


Then there's a 139ms gap until you see this, but there's no "52" log line prior:
01   04/24/11 10:49:41.539   LuaInterface::CallFunction-2 lu_incoming failed [string "..."]:830: bad argument #2 to 'format' (string expected, got nil) <0x3c10>


Can you go back over your logs to find the missing lines?  It's possible that some sort of corruption is going on, so checkout every log line between the two above timestamps.
Title: Re: DSC Alarm System plugin
Post by: Kyle on April 24, 2011, 11:24:26 pm
There are log lines missing.

Normally they'll come in tuples like this:
52   04/24/11 10:49:41.542   0x39 0x30 0x38 0x30 0x31 0x30 0x31 0x30 0x32 0x43 0x35 (908010102C5) <0x3c10>
50   04/24/11 10:49:41.543   luup_log:47: DSCAlarmPanel: debug processIncoming:: Command=908, Data='010102', Checksum=C5 <0x3c10>
50   04/24/11 10:49:41.544   luup_log:47: DSCAlarmPanel: debug Panel::Software Version 908 data: 010102 <0x3c10>


but you'll see that I'm sending an initialization command (to enumerate all the Zones/Partitions/etc) here:

51   04/24/11 10:49:41.400   0x30 0x30 0x32 0x39 0x32 0xd 0xa (00292rn) <0x402>


Then there's a 139ms gap until you see this, but there's no "52" log line prior:
01   04/24/11 10:49:41.539   LuaInterface::CallFunction-2 lu_incoming failed [string "..."]:830: bad argument #2 to 'format' (string expected, got nil) <0x3c10>


Can you go back over your logs to find the missing lines?  It's possible that some sort of corruption is going on, so checkout every log line between the two above timestamps.

oops.. I missed it.. I went back and looked, and here is what I have. I've also noticed that the only way for the status of my alarm to be updated in Vera is to reboot Vera.
Title: Re: DSC Alarm System plugin
Post by: guessed on April 25, 2011, 12:18:35 am
ok, so that content is really bad.  If it weren't for valid bytes at the end I'd have guess that the Baud rate was incorrectly set.

The next guesses are:

a) A non-grounded, or failing ground, cable on the RS-232 cable
b) A failing USB-Serial cable.

As far as I'm aware, there should never be a series of 0xFF bytes in the beginning of any response.
Title: Re: DSC Alarm System plugin
Post by: Kyle on April 25, 2011, 12:22:03 am
I'll try and switch the cable out now and see what happens!
Title: Re: DSC Alarm System plugin
Post by: Kyle on April 25, 2011, 01:31:23 am
lol, now I cant get the new cable to show up in Vera.. I'll let you know what happens when I get it to work.
Title: Re: DSC Alarm System plugin
Post by: Kyle on April 25, 2011, 09:39:07 am
ok, so that content is really bad.  If it weren't for valid bytes at the end I'd have guess that the Baud rate was incorrectly set.

The next guesses are:

a) A non-grounded, or failing ground, cable on the RS-232 cable
b) A failing USB-Serial cable.

As far as I'm aware, there should never be a series of 0xFF bytes in the beginning of any response.

You were right on! It was the cable...I changed the cable out and finally got it to show up on my Vera..and now it works perfect! Thanks!!
Title: Re: DSC Alarm System plugin
Post by: Ambrotos on April 26, 2011, 10:03:34 pm
Unfortunately my problem doesn't appear to be cable related. I've changed the cable, as well as the USB/Serial adapter, and I'm still seeing exactly the same problem. Namely, zone status displays properly in vera, but I cannot send any commands to the panel (arm/disarm/time/etc).

One other thing I've noticed is that the Partition status in Vera is often (not always) "NotReady", even though the P1832 itself reports that it's ready for arming.

Is there any additional testing or logging that I can do that might help with troubleshooting?

-A
Title: Re: DSC Alarm System plugin
Post by: strangely on April 26, 2011, 11:47:03 pm
Did you try it without the cable present and having the IT100 plugged in direct to the USB adapter? You mentioned you'd used a null modem cable, however you shouldn't require one due to the fact the IT100 is already swapping pins 2 and 3 from convention.

What sort of USB serial adapter did you use, and is it one of the compatible ones? They are not all created equal!
Title: Re: DSC Alarm System plugin
Post by: JimMac on April 27, 2011, 11:12:27 am
I added the DSC plugin over the weekend.  All seems to work except the name of the zones.  As each zone was added to Vera the name was briefly displayed as Zone1-14 as expected but within half a second all names were over written with an extended character.  (a black triangle with a ? in the middle).  the only way to determine what zone they are was to look in the advanced tab.   Any ideas what would cause this?   I have included some snap shots.
Vera 2, Firmware version 1.1.1245, on a newly rebuilt system.
Title: Re: DSC Alarm System plugin
Post by: TimAlls on April 27, 2011, 11:57:55 am
I had problems writing information to my DSC but could read the Zones just fine. It was not a cable or USB adapter issue. I had to remove all traces of the prior version and reinstall the Plugin following the directions to the letter!

In regard to Zone Labels.....make sure all the Zones are labeled the way you want on your DSC Keypad and then turn on the Label Broadcast from you Keypad. Once I did that all the labels came through perfect!

Hope this helps.

Regards
Tim Alls
Title: Re: DSC Alarm System plugin
Post by: JimMac on April 27, 2011, 12:19:32 pm
All zones are labeled and were broadcasted.  I know the broadcast worked because my second keypad picked up all the labels.  I guess my only option is to try to install it again.  I don't see a need to remove the plugin files since this is the first time installing this plugin plus I just finished a complete system rebuild.
Title: Re: DSC Alarm System plugin
Post by: JimMac on April 27, 2011, 12:55:21 pm
I re-installed the plugin and found some interesting results.  First time installed zones 1-6 show up labeled Zone1-6, not the labels I entered from my keypad.  When I change the DoorZones, MotionZones and SmokeZones under the "Advanced" tab to show the remaining zones on my PC5108 expansion board that is when all zone labels get corrupted.  If I adjust the zone numbers back to only 6 the labels stay corrupted.
My setup is as follows:
PC1832 Alarm board
PC1508 expansion board
IT-100
WIZnet

Edit:  I did some trouble shooting and I may have a bad smoke detector.  If I don't add it all labels show up as zone1-7 and 9-14 (less my smoke detector on zone 8 )
No warnings on my alarm panel so I will test it when I get back to my summer house.
Title: Re: DSC Alarm System plugin
Post by: computerjohn on April 27, 2011, 02:52:39 pm
The zone label names are being read from the panel and will over write whatever you name them in Vera each time you ARM the panel. You must name them in the panel and then broadcast it. This has been instructed before on here by Strangely. Go back a few pages. You will need the installer's code.

I added the DSC plugin over the weekend.  All seems to work except the name of the zones.  As each zone was added to Vera the name was briefly displayed as Zone1-14 as expected but within half a second all names were over written with an extended character.  (a black triangle with a ? in the middle).  the only way to determine what zone they are was to look in the advanced tab.   Any ideas what would cause this?   I have included some snap shots.
Vera 2, Firmware version 1.1.1245, on a newly rebuilt system.

Title: Re: DSC Alarm System plugin
Post by: JimMac on April 27, 2011, 04:05:50 pm
computerjohn

From what I understand is the labels are stored on the keypads and not in the alarm memory (not like my PC4020).  I replaced a much better board for the PC1832 but at least I have a connection to Vera.  The next time I'm at my summer home I will ask the keypad to broadcast the names.  When I do that is there anything I need to do with Vera during the broadcast? 
Title: Re: DSC Alarm System plugin
Post by: strangely on April 27, 2011, 06:20:57 pm
The labels are held in the panel, the keypads and probably also the IT100 since its also technically a keypad.
The panel is the master place they are stored if programmed from the DSC DLS software. The normal defaults on the Panel are Zone 1, Zone2 etc and I don't think will be overwritten by labels programed from a keypad or broadcast by a keypad.
I believe a new keypad will attempt to pull the default from panel unless its been programmed manually, or programmed via a broadcast from another keypad.

Basically if you installed your IT100 after this broadcast was performed initially, then it would have assumed the Zone1, Zone2 etc, or whatever is programmed on the panel I think!

If you perform the broadcast again from the keypad they were programmed from originally (has to be the one they programmed from), then this should update the IT100, and then Vera once the plugin restarts!

Label broadcast:
*8[Installer code]*998*
Title: Re: DSC Alarm System plugin
Post by: TimAlls on April 27, 2011, 07:00:47 pm
I programmed my labels from my KeyPad and later I hit broadcast....then they all came in as entered in the KeyPad.
They were Zone 1, Zone 2, Etc for weeks until I broadcast the labels as per your
Quote
Label broadcast:
*8[Installer code]*998*
Regards
Tim
Title: Re: DSC Alarm System plugin
Post by: JimMac on April 27, 2011, 11:22:11 pm
I'm going to look at this more closely since I did a broadcast after programming all zone names from the same keypad.  I used the DLS software to program the rest of the panel but when I looked for a way to label the zones I could only find one option but the software indicated that it was missing something from the account properties.  It did not say what was needed.  I ran a online update but that did not offer a solution.  In the software what number is used for zone labels and is there anything else needed other than the PC1832 driver? Maybe a wrong version of the PC1832 driver?
Title: Re: DSC Alarm System plugin
Post by: strangely on April 28, 2011, 12:04:15 am
Which version of DLS did you use? There's the version IV and also the 2002 version!
I used the IV version but cant remember where they were programmed there, and I can't check now since I had a hard disk crash on the PC I used, and all the data is lost! :( (criminally no back up either). I'll need to get the PC up an running again with a new disk and wait until I can re-install it, to be able to check for you!

Did you do the broadcast before or after the IT100 was installed?

I would try to rebroadcast, and if that doesn't fix it then you'll need to turn verbose logging, and then grab the log if you can, so that we can take a look!
Title: Re: DSC Alarm System plugin
Post by: JimMac on April 28, 2011, 06:21:00 am
I have the 2002 version with SP2.  I did a broadcast after the IT-100 was installed.  I'll look at a few things this weekend when I can access the panel.
Title: Re: DSC Alarm System plugin
Post by: Ambrotos on April 28, 2011, 10:45:47 am
@strangely

An excellent suggestion, as it turns out. As I mentioned before, I'd tried swapping my USB adapter, AND my serial cable (which is not a null modem, by the way... just a brain fart on my part when I said that). Unfortunately, I'd tested them separately. As it turns out, my problem appears to have been both the brand of USB adapter and a grounding problem on the cable. I'm still using a PL2303-based adapter just a different make.

Anyway, problem solved. I can arm/disarm the system from Vera. Now I can move on with programing in my scenes.

Andrew
Title: Re: DSC Alarm System plugin
Post by: harphaulingdad on April 28, 2011, 02:59:17 pm
My alarm company will not help me with the actual installation of the IT100 board, but they don't object to me putting it in. How difficult is the actual connection to the DSC panel? Are there any published step-by-step guides....the installation guide shows the wiring to the board, and I'm comfortable with that, but not certain where to go in the panel with the wiring to get everything properly connected. Thanks for any help you can provide.
Title: Re: DSC Alarm System plugin
Post by: techsan on April 28, 2011, 03:30:46 pm
How difficult is the actual connection to the DSC panel?...

It is extremely easy to wire in the IT100. The hardest part will be deciding how to mount it. On the 1 page illustration that comes in the box you will see the exact diagram. When you look at your DSC panel you will be adding a few short wires (I believe 3) from the IT100 to the panel so go ahead and make your own (I simply used cat5). The wire screw downs on the panel are the same ones used by the keypad and the DSC sees it as another keypad so keep in mind that you will be sharing those screw down holes with the existing keypads. In other words don't look for empty spaces to wire in the IT100. Once you have that wired in its a simple plug in of the Serial to USB adapter and that will be the last you need of the DSC panel. I did not need a Null adapter for my installation and chances are you will not either.
Title: Re: DSC Alarm System plugin
Post by: harphaulingdad on April 28, 2011, 03:38:18 pm
Thanks, techsan. I'm going to give it a try and hope for the best. May be coming back to ask more questions later.
Title: Re: DSC Alarm System plugin
Post by: strangely on April 28, 2011, 03:54:44 pm
Its actually 4 wires and they are marked by a color or letter on each of the screw terminals. If you use alarm wire or CAT5/6 then you just need to be aware that the colors in the wire may not correlate to whats written, but thats not a problem as long as you keep it consistent. All very easy really!

The IT100 is supposed to be mounted in the panel, however you could in theory mount it elsewhere in a location where you can tap into the existing keybus wiring going to your keypads.
Title: Re: DSC Alarm System plugin
Post by: harphaulingdad on April 28, 2011, 05:03:37 pm
Found the Keybus wiring in my panel. Was planning to use serial-to-bluetooth adapters to communicate between the system and Vera. But I just checked my Vera2 out, and there is no serial connector! I'll need to find another way to communicate....suggestions besides cabling, which will not be easy to do in my setup? Does the Vera require an actual serial connection through the USB port, or can it be through some other means such as serial-to-wireless on the IT100, and a virtual serial on the Vera2 using TCP/IP? Thanks for your insight.
Title: Re: DSC Alarm System plugin
Post by: strangely on April 28, 2011, 05:11:36 pm
You can do it with an RS232 to Ehternet adapter or RS232 to WiFi.

See the the "How does it work" part of the trac wiki for some examples:

http://code.mios.com/trac/mios_dscalarmpanel
Title: Re: DSC Alarm System plugin
Post by: TimAlls on April 28, 2011, 06:14:48 pm
In regards to the serial connection between the Vera and the IT100:
My DSC alarm panel is a long ways from my Vera but I had a Keypad about 10 feet from the Vera so I ran a 4 conductor cable from the Keypad to the Vera and installed the IT100 board next to the Vera.....works great and eliminated the need for a Ethernet to Serial converter.
Food for thought....
Regards
Tim
Title: Re: DSC Alarm System plugin
Post by: strangely on April 29, 2011, 03:34:18 am
In regards to the serial connection between the Vera and the IT100:
My DSC alarm panel is a long ways from my Vera but I had a Keypad about 10 feet from the Vera so I ran a 4 conductor cable from the Keypad to the Vera and installed the IT100 board next to the Vera.....works great and eliminated the need for a Ethernet to Serial converter.
Food for thought....
Regards
Tim
I had considered doing the same, but the cable run back to my vera isn't very far and I just reused a spare cat6 cable to run the RS232 over.  I may actually move the IT100 near vera anyway, and then re-wire the Cat6 cable to the Keybus instead as I'm thinking about buying an IP100D below, and it'll save running another cat6 cable to the alarm panel if I want to run both the IT 100 and the new module in tandem.

http://www.eye-zon.com/EYEZON2010/envisalink-ip100d-security-.php
I contacted the guys who make this, and they are considering publishing an API for it :)
Title: Re: DSC Alarm System plugin
Post by: harphaulingdad on May 09, 2011, 03:41:57 pm
One more question. I am purchasing an Itach WiFi to Serial Adapter, which uses -5 to 16V DC@300mA of current to run, provided by a wall power adapter. Will the Keybus power supply enough power to run this device so I won't need to plug it into an outlet, if I just connect it to the two power leads? Thanks again.
Title: Re: DSC Alarm System plugin
Post by: TimAlls on May 09, 2011, 07:49:28 pm
What do the arm / disarm buttons on each zone do? Reading the Wiki (MCV) it appears these are flags that do nothing.....
Question 2: if they don't do anything can I use them as general purpose variables? I could use the virtual binary switch but then I have more stuff on mu busy UI !
Regards
Tim
Title: Re: DSC Alarm System plugin
Post by: strangely on May 10, 2011, 12:01:24 am
One more question. I am purchasing an Itach WiFi to Serial Adapter, which uses -5 to 16V DC@300mA of current to run, provided by a wall power adapter. Will the Keybus power supply enough power to run this device so I won't need to plug it into an outlet, if I just connect it to the two power leads? Thanks again.
Well I know its 12V, but no idea of the current specifications (Google wasn't much help). I guess there'd be enough though, although this might depend on how may other devices are on the bus.
Title: Re: DSC Alarm System plugin
Post by: guessed on May 10, 2011, 12:05:09 am
What do the arm / disarm buttons on each zone do? Reading the Wiki (MCV) it appears these are flags that do nothing.....
Question 2: if they don't do anything can I use them as general purpose variables? I could use the virtual binary switch but then I have more stuff on mu busy UI !
Regards
Tim

In the DSC, they aren't used, so you're free to "play" with them.  I could partially wire them up, since some of the data is available, but I didn't so that you could use them as "variables" (common in scene scripting.... "do this only if that is armed")
Title: Re: DSC Alarm System plugin
Post by: strangely on May 10, 2011, 12:16:23 am
Are you sure they don't work? Well I'm pretty sure they worked in the older version of the plugin at least because I'm sure I used them, and had one or two being set by a timer for ones I only wanted to use for some nighttime only scenes. (now using Lua for this instead)
Title: Re: DSC Alarm System plugin
Post by: guessed on May 10, 2011, 12:32:09 am
Are you sure they don't work? Well I'm pretty sure they worked in the older version of the plugin at least because I'm sure I used them, and had one or two being set by a timer for ones I only wanted to use for some nighttime only scenes. (now using Lua for this instead)

I preset the value of "Armed" to "1" (on) when I'm creating the device, but the only time after that when it's supposed to change if if you click (Arm) or (Disarm) in the UI.

Right, so you can code against them yourself.  You can definitely change them manually, or via Scene's or Luup Scene code, but the Plugin itself won't set these as they're armed/bypassed via the KeyPad UI of the DSC.

@futzle's GE code will do that, but the Paradox and the DSC won't.
Title: Re: DSC Alarm System plugin
Post by: TimAlls on May 10, 2011, 01:05:59 am
Thanks for the info...the wiki documented command doesn't work for the DSC, what is the command to change the state of this variable?
Regards
Tim
Title: Re: DSC Alarm System plugin
Post by: guessed on May 10, 2011, 01:15:09 am
Thanks for the info...the wiki documented command doesn't work for the DSC, what is the command to change the state of this variable?
Regards
Tim

Do you have a Snippet of what you tried against the Zone device from the DSC?

Standard stuff like this:
    http://wiki.micasaverde.com/index.php/Luup_Scenes_Events#Arm_motion_sensor_.237

should work fine.  The "value" can only be "1" or "0"
Title: Re: DSC Alarm System plugin
Post by: Ambrotos on May 10, 2011, 07:58:11 pm
Is there any way to disable the plugin's auto-naming of sensor objects based on Zone Label? I have a LCD5501Z keypad, which is fixed message and doesn't support zone labeling. I just want to rename my sensors in Vera and have them stay that way, as opposed to being constantly overwritten with the panel's "default" values.

-A
Title: Re: DSC Alarm System plugin
Post by: strangely on May 11, 2011, 12:07:11 am
Not currently with the plugin, although I've added this as a feature request though.

You could always buy the serial cable ($16) and change them from your PC though!?
Title: Re: DSC Alarm System plugin
Post by: westguard on May 11, 2011, 03:49:08 am
Hi

I've managed to get everything working working with the DSC Alarm System Plugin other than the labeling.

I've tried the label broadcasting (*8[Installers Code]*998*) from one of my keypads but I am still not seeing the labels appear. I did the label broadcast command *after* labeling my zones.

A few more bits of information:

- Alarm control board: PC5010
- IT-100
- 3 keypads (one allows for labeling zones and I can see the zone names on the keypad)
- iVera 2 running firmware 1.1.1245 (Upgraded to Z-Wave version 3)

All other features (e.g. arming, detection of doors opening etc) are working great.

I've tried remote connecting to my alarm panel using DLS2002 but my modem won't connect. I will see if my alarm company can tell me if the control panel itself has labels configured.

Any help would be much appreciated. Either that or a way of turning off the auto-labeling would be great.

Many thanks

Mark
Title: Re: DSC Alarm System plugin
Post by: strangely on May 11, 2011, 03:56:42 am
I assume you did the broadcast form the keypad the labels were programmed from, and also after the IT100 was installed?
Title: Re: DSC Alarm System plugin
Post by: westguard on May 11, 2011, 03:59:59 am
Yes. The broadcast was done after everything was configured and communication with the IT100 was working with the iVera.
Title: Re: DSC Alarm System plugin
Post by: strangely on May 11, 2011, 04:04:03 am
I'd be interested to find out the model keypad you have that supports labels?
Title: Re: DSC Alarm System plugin
Post by: westguard on May 11, 2011, 04:11:49 am
I believe it is: LCD5500Z
Title: Re: DSC Alarm System plugin
Post by: Ambrotos on May 11, 2011, 10:42:12 am
@strangely:

I typically program the panel via DLS2002. The zone label options are found under the keypad module, aren't they? My keypad is a LCD5501z, which is fixed-message, so doesn't support zone labels. There isn't even a driver in DLS2002 for the 5501z. Is there something I'm missing? Somewhere else I can program zone labels? I'd always assumed the only way to get zone labels would be to purchase a newer keypad.

-A
Title: Re: DSC Alarm System plugin
Post by: TimAlls on May 11, 2011, 10:49:43 am
@guessed,
The code listed in the Wiki works fine...it was me!
I now have 16 virtual switches to work with! The reason I want the virtual switches is for the creation of complex scenes with lots of if, and, but, maybe, sortoff's, stuff in them...By using virtual switches for flags one can see what is happening in the code. For example:
If it is 30 minutes before sunrise turn on flag1.
If there has been no motion in the living room for one hour turn on flag2.
If the temperature is above 80 degrees turn on flag3

from there one can have simple logic:
turn on scene1 if (flag1=1 and flag2=1 and flag3=1)

The hardest thing for a newbie writing code is the inability to see whats going on!

Regards
Tim
Title: Re: DSC Alarm System plugin
Post by: strangely on May 11, 2011, 01:14:15 pm
I believe it is: LCD5500Z
I'll have to do some more research on this, but I think I remember seeing a post on one of the alarm support forums, that the label format was different (and incompatible perhaps?) between the older and newer keypads. If this is correct then this would also likely mean incompatible with the IT100.

This may be relevant as to why it doesn't work:

http://www.alarmhow.net/manuals/DSC/Keypads/PK5500%20Alpha/PK5500%20Global%20Broadcast%20Advisory.pdf
Or
http://www.doityourself.com/forum/electronic-alarms-home-security-devices/423955-pk5500-wont-broadcast-labels.html

I think you mentioned you had a PC5010
Title: Re: DSC Alarm System plugin
Post by: strangely on May 11, 2011, 01:26:57 pm

I typically program the panel via DLS2002. The zone label options are found under the keypad module, aren't they? My keypad is a LCD5501z, which is fixed-message, so doesn't support zone labels. There isn't even a driver in DLS2002 for the 5501z. Is there something I'm missing? Somewhere else I can program zone labels? I'd always assumed the only way to get zone labels would be to purchase a newer keypad.

-A
I had the DLSIV software installed (need to reinstall due to hard drive crash) and cant remember where the label programming was, although I think it was under the zone attributes rather than for the keypad.
I'll reinstall it anyway as I need to make a new backup of my panel in-case it fails for any reason
Title: Re: DSC Alarm System plugin
Post by: westguard on May 11, 2011, 05:03:05 pm
I'll have to do some more research on this, but I think I remember seeing a post on one of the alarm support forums, that the label format was different (and incompatible perhaps?) between the older and newer keypads. If this is correct then this would also likely mean incompatible with the IT100.

Yes you were right. The broadcast feature was not working because of the incompatibility problem. We resolved this by going in via DLS2002 and doing a global download/upload, not the IT100 is labelled up and the plugin is pulling back the correct label names.

Thanks for your help!
Title: Re: DSC Alarm System plugin
Post by: Ambrotos on May 11, 2011, 08:59:54 pm
@strangely:
I decided to give DLSIV a try, since DLS2002 clearly associated zone labels with individual keypads. You were right, in DLSIV, zone labels are a part of the basic zone definition table. So, problem solved. Thanks for the accidental tip  :D

-A
Title: Re: DSC Alarm System plugin
Post by: strangely on May 11, 2011, 11:22:54 pm
@strangely:
I decided to give DLSIV a try, since DLS2002 clearly associated zone labels with individual keypads. You were right, in DLSIV, zone labels are a part of the basic zone definition table. So, problem solved. Thanks for the accidental tip  :D

-A
No accident ;)
Title: Re: DSC Alarm System plugin
Post by: Ambrotos on May 12, 2011, 09:10:36 am
hahahaha... ok well, credit where credit is due then I guess :)
Title: Re: DSC Alarm System plugin
Post by: Cherokee180c on May 18, 2011, 08:24:17 pm
I have been reading this thread intently trying to figure out if my system will work with the Vera2. My DSC system is a Power 832 system, but the control panel cover says PC5010 on it.   Can i buy the IT-100 and WIZ adapter and tie into everything?  The system is totally hardwired with two Power 832 LCD display panels.

Also unfortunately I finished my basement and have very little access to where the alarm panel is located. My switch for the basement is on the other side of the basement though. Is there a way to mount the Vera2 by the alarm panel and hook up via wifi?  If not, do you know if they make flat ethernet cable as i might be able to run under my rug for about 12' and then along the floor boards to reach that corner of my basement. 

Lastly, is anyone getting rid of the traditional land line monitoring and just doing it yourself via Vera or are you just using it for remote status indication?  I have recently had Fios installed and one simple cut to the fiber optic cable takes everything down even on the current system and just leaves the local loud alarm on battery backup. Not sure what the monitoring company would know other than they lost phone connection when they poll the system.   I believe the only way to get around this is the GSM system, but that adds even more to the monthly cost.
Title: Re: DSC Alarm System plugin
Post by: strangely on May 19, 2011, 12:47:27 am
So I'm pretty sure the 832 will work with the IT100 and the plugin.

Wiring wise, you have a few options

1) you could see if you have some existing or spare pairs of wire elsewhere perhaps to run the keybus or RS232 over. For RS232 you need 3 wires and for the keybus you'd need 4. For spare pairs Look at your existing wire... Is it alarm wire, telephone wire, or cat5 perhaps? Also do you have old telephone wirering that could be used?
2) do you have a keypad that the IT100 could be wired up to?
3) use a WiFi to RS232 adapter instead of a wiznet!

For monitoring, I have mine hooked up to a linksys VoIP adapter, but I'm thinking about changing this at some stage.
Title: Re: DSC Alarm System plugin
Post by: Ambrotos on May 20, 2011, 09:39:21 am
@Cherokee180c:

Regarding the wiring, yes you can put Vera in wifi-client mode. I did this myself for a few months until I moved Vera down to the basement. Only two minor caveats:

-Vera's wifi MAC is obviously different from the Eth MAC, so it will get a different IP when switching between wired and wireless. Not a big deal, but can be confusing if you're not expecting it.
-Also, the wifi client configuration seems to take a while to complete during startup. Aside from meaning it'll take longer for the dashboard to be accessible after bootup, it also means that during upgrades you'll have to backup/restore configuration manually. It seems that the wifi connection isn't available until after the connection to mios.com configuration servers times out. Also not a big deal really, just trying to forestall the inevitable ticket :D

As for monitoring, I used to have my system connected to a UTStarcom VoIP adapter, which was registered with an Asterisk PBX I hosted myself. I know monitoring companies say they hate monitoring via VoIP due to unreliability, but I never had any problems. I shut that down though, and now I just monitor the system myself via Growl alerts on my iPhone (sent by Vera).


-A
Title: Re: DSC Alarm System plugin
Post by: Cherokee180c on May 20, 2011, 10:54:48 am
Thanks for the information. I am trying to figure out how the current POTS system works. If I get a power outage, the battery backup battery kicks in and since phone is still active, the DSC controller calls to the monitoring service and we get a phone call. However I have now switched everything over to Fios fiber, so one cut to that fiber cable and there is no communication going out from the DSC to anywhere. I assume that the only way the monitoring company will find this out is when some scheduled call from the DSC to the station does not occur on time?  Is this the way the current system works?  What is the timing between normal calls out from the system?  Maybe I am way off base on how the normal non event driven status updates work now. I think the only way around the cut wire scenario is to go GSM radio on battery backup?
Title: Re: DSC Alarm System plugin
Post by: Ambrotos on May 20, 2011, 02:22:29 pm
@Cherokee180c: I'm not terribly knowledgeable about the exchanges between the monitoring station and a DSC panel myself. I think you're right though in that it only makes sense for the panel to periodically check in with the monitoring system. Section 377 option 7 specifies the test transmission cycle in days/minutes. Maybe this is the transmission the monitoring system is expecting?

And yes, to deal with landline cuts, you'd need something like the DSC GS3060.

As for me, to deal with internet outages, I've got my NAT/Router set up with multiple redundant WAN ports. One is connected to my cable ISP, and the other is connected to my neighbor's DSL ISP.

-A
Title: Re: DSC Alarm System plugin
Post by: strangely on May 24, 2011, 02:00:01 am
You have a nice neighbor :) Good idea though, although I'd be just as worried about the phone line being cut rather than the cable. Phone lines are probably more of an obvious thing to cut anyway!
Title: Re: DSC Alarm System plugin
Post by: Cherokee180c on May 24, 2011, 08:37:44 am
I really like that solution if you have a good neighbor. The funny thing is that switching to IP adressible on the alarm could actually be an advantage if the thief doesnt understand how Fios works. I can't imagine anyone breaking into a house that clearly states it has an alam system without them first cutting the phone wires.   If they don't cut the fiber optic cable then your Internet is still up.  I have battery backup on my DSC alarm system and FIOS box, so if I add it to the router you are even covered for power out situation.   I talked to a local police officer last year after I had my first false alarm in 13 years. It turns out I had a bad motion sensor. He told me smash and grab is the most common method in broad day light when everyone is at work.  They kick in the door, rip out the speaker for the alarm and then grab what they can in 2-4 minutes before any police can respond. No standard alam system protects you from this. That is why I plan to have a camera system in the house. One IP addressable and one hidden motion onto SD so at least they might catch the bastages.
Title: Re: DSC Alarm System plugin
Post by: JimMac on May 25, 2011, 11:23:35 pm
From my previous posts I was having problems with labels using the plugin.  I think I have an idea why.  I have a PC1832, IT-100 and a WizNet.  I had found that my RFK5500 keypad needs to be located in slot 8.  The IT-100 is hard coded to also take slot 8.  With both on the same slot I can not broadcast the zone labels.  If I move the keypad to any other slot the zone broadcast function does not work.  I can disconnect the IT-100 and broadcast from the keypad with no problems except the IT-100 does not get the update so no zone labels in Vera.  I don't know of any work around for this.  Anyone else have this hardware and were able to get zone labels?  Is there any way I can force a zone broadcast using DLS2002 or DLS IV?

I'm thinking that I will need a second keypad that can use slot 1-7.  Remove the RFK5500 and do a zone broadcast from the second keypad.  I hope this allows the IT-100 to accept the broadcast.  Any other suggestions?
Title: Re: DSC Alarm System plugin
Post by: strangely on May 26, 2011, 12:02:55 am
If you have an RFK keypad then it actually takes 2 slots, one for the radio part, and one for the keypad. I had also read that the primary keypad needed to be in slot 8 also for the broadcast to work, and also the that the IT100 defaults to 8 (I'll see if I can find this info again and confirm, as it seems to contradict)

I have mine configured as such (i think):

RFK5001 (non alpha) in slot 1 (automatically assigned)
PK5500 (alpha) in slot 5 (I programmed this through DLS IIRC)
IT100 in slot 8 (I think this automatically picked itself)

Either way you should be able to change the assignments through DLS IV along with adding the labels directly to the panel and all should be good.

Mine may have just worked because initially I only had a non alpha keypad, and the whole thing was powered up initially with the IT100 present. The alpha keypad I added later.
Title: Re: DSC Alarm System plugin
Post by: JimMac on May 26, 2011, 08:17:26 am
I talked to DSC and the RFK5500 (with a PC5132 wireless and temp built in) needs to be in slot 8 in order to broadcast or communicate with DLS software.  It is one of the very few keypads that must have this slot.

I'm thinking of trying this:
Add a new PK5500 (no PC5132 wireless option) to slot 1
remove the IT-100
broadcast the labels from the RFK5500 to the PK5500

Once the PK5500 has the labels
remove the RFK5500
reconnect the IT-100

 Now if I use the PK5500 (slot 1) to broadcast I'm hopping that the IT-100 will pick up the zone labels.  Then I will reconnect the RFK5500.  I hope the IT-100 has non volatile memory so it doesn't loose the zone labels when the power is disconnected.  If this works it may be a pain in the butt but I don't think I will need to change my zone labels that often.
Once again has anyone tried this?
Title: Re: DSC Alarm System plugin
Post by: strangely on May 26, 2011, 11:10:31 am
If you assign your keypad to something like slot1 then you won't need to do a label broadcast if you program them directly to the panel with DLS, this way they automatically get cascaded down from the panel to everything and there is no commanded broadcast needed.

Title: Re: DSC Alarm System plugin
Post by: JimMac on May 26, 2011, 12:48:34 pm
I assume you mean my new PK5500 when you say "your keypad".   I will give this a try this weekend.  With the slot 8 conflict I have not been able to see the IT-100 as a device using either version of the DLS software.  I'm assuming that once the RFK5500 keypad is removed the IT-100 will show as a keypad on slot 8 when I run a device auto detect?
Title: Re: DSC Alarm System plugin
Post by: strangely on May 26, 2011, 03:06:58 pm
This is what I'd do.

1) Power off/remove battery
2) Remove the IT100 from the keybus
3) Power on/reconnect battery with IT100 removed.
4) Connect with DLS and "upload" your current configuration to the PC to edit against.
5) Reassign your current keypad to another slot (1 for example) I think you can ignore DSC as this is only in regard to broadcasting to other keypads, and although I think they are correct, its ability to not broadcast wont affect its operation or subsequent detection by DLS. (remember we are going to rely on the panel downloading the labels.
6) In DLS, add your Zone labels under each zone (you have to scroll a long way to the right to see this). Maybe consider making one of them slightly different from what you already had programmed through the keypad, this is so that you can see if it updates your keypad from the new panel based labels where you replaced the "Zone 01" etc
7) Download your new configuration back the panel.
8 ) Make sure everything is working.
9) Power off again (including battery)
10) Re-connect the IT100.
11) Power up again.
12) Restart the MiOS engine in Vera.
Title: Re: DSC Alarm System plugin
Post by: JimMac on May 26, 2011, 03:59:47 pm
Thanks strangely, I'll give that a try this weekend.
Title: Re: DSC Alarm System plugin
Post by: JimMac on May 28, 2011, 04:48:43 pm
Yehhh! I finally I managed to get the labels to show up... all but my 2 wire smoke detector.  Since 2 wire smoke detectors don't use zones how do I make them display on the GUI? 
Title: Re: DSC Alarm System plugin
Post by: strangely on May 29, 2011, 01:45:14 am
Not sure you can get the smoke to work, there was a post a while back in this thread where somebody else wanted to do the same and may have typed an S in the configuration???

I'm curious to how you got it working though? Did you follow my instructions roughly, or was something else required? I think this information will be useful to anyone else reading this thread, in case they encounter the same problem.
Title: Re: DSC Alarm System plugin
Post by: JimMac on May 29, 2011, 05:30:18 pm
Here is the process to correct my slot 8 conflict problem;

Power down the panel
Removed power from the IT-100
Power up the panel
Programmed the zones on the RFK5500 with DLS IV
Move the RFK5500 from slot 8 to slot 6 using the keypad, did a supervisory reset, checked the enrollment
Power down the panel, reconnected the IT-100
Used DLS-IV to push the zone labels to the IT-100 that is now in slot 8

 
Title: Re: DSC Alarm System plugin
Post by: harphaulingdad on May 31, 2011, 02:24:11 pm
I got my IT100 installed, along with an iTach serial-to-wifi connector. I see messages from the DSC to my Vera2 log, so I know I've got connectivity. But I cannot set anything through Vera2 to the DSC. I think it is because my iTach is listening on IP port 4999, and Vera2 is sending on another port #. Attached are the screenshots for the 3 places I know to configure the IP address Vera2 should talk to (the DSC panel and System devices), and I've included the port #, but don't think the syntax is correct. Anyone have any ideas on how to correct? Thank you.
Title: Re: DSC Alarm System plugin
Post by: strangely on June 01, 2011, 12:09:33 am
You seem to have entered the IP and port correctly and I'd say that this is either some type of setting issue with the iTach, or possibly a cable issue if you don't have it directly connected to the IT100.

Regarding a possible cabling issue, there was somebody a few pages back that had the same type of issue with a USB adapter.

For the iTach, what if anything does it allow you to change in the way of settings?

 
Title: Re: DSC Alarm System plugin
Post by: harphaulingdad on June 01, 2011, 10:37:35 am
The iTach allows basic changes of serial port speed, ip address, etc. I connected it directly to the IT100 without a serial cable. It could be that I need the serial cable between the two, but I wouldn't have thought so. I'm going to give that a try next chance I get. Thanks for the feedback!
Title: Re: DSC Alarm System plugin
Post by: strangely on June 01, 2011, 10:53:37 am
Well if it plugs in directly with no gender changer or cable required then I wouldn't worry about a cable.

It might be worth validating that the iTach works with something else first, and that you can get bidirectional communication. Do you have any other RS232 devices that it can be tested with using a PC or the test app that GC makes?
Title: Re: DSC Alarm System plugin
Post by: harphaulingdad on June 01, 2011, 12:33:07 pm
Before I go in and take things out of my panel, I'll try changing some parameters like the stop bits, parity, etc. Nothing was documented in the IT100 guide about those parameters, but they may be preventing data from Vera getting to the DSC.
Title: Re: DSC Alarm System plugin
Post by: strangely on June 01, 2011, 12:53:02 pm
The default for the IT100 should match whats listed here:

http://code.mios.com/trac/mios_dscalarmpanel

Namely 9600 8N1
Title: Re: DSC Alarm System plugin
Post by: harphaulingdad on June 01, 2011, 09:19:37 pm
If I am using TCP/IP as the transport, instead of the direct serial connection (via a WiFi-Serial adapter), should I have to configure a serial port on the DSC Device instance in Vera? If I go there (I/O), it does not list a serial port for me to configure, which sort of makes sense.

I left the IT100 at its default settings, which I believe are what you referenced in the previous post. The error I get when I try to poll or configure is "Delivery Failed." I"ll keep trying.

I've also noticed that after I configure my Zones with the locations like Zone 01 - Smoke Detectors, etc., then at some point the get reset back to the default Zone names.

Should I just uninstall all the DSC plugins/LUA code and start over perhaps?
Title: Re: DSC Alarm System plugin
Post by: strangely on June 01, 2011, 10:47:48 pm
OK first thing to check, where did you get the plugin from? Was it the Mios market place within Vera's dashboard, or from  "code.mios.com?" and a manual install?

I have mine also configured with an IP serial device (WIZnet), and the only thing to configure in Vera is the IP and port as you already seem to have listed.

Your iTach should handle the rest on the IP side, and you'll only need to configure the serial side with settings to match the IT100
Title: Re: DSC Alarm System plugin
Post by: harphaulingdad on June 02, 2011, 04:00:12 pm
Got it from the Vera Dashboard. Sounds like I need to try the other location.
Title: Re: DSC Alarm System plugin
Post by: strangely on June 02, 2011, 04:55:45 pm
Yes, you should delete that plugin, and install/follow the instructions from the one here:

http://code.mios.com/trac/mios_dscalarmpanel

The original one was never tested or coded with IP serial adapters in mind.
Title: Re: DSC Alarm System plugin
Post by: harphaulingdad on June 02, 2011, 05:17:03 pm
I actually did that, but made the mistake of also downloading the plugin from the Vera dashboard. I'll delete everything and start over again. Hopefully will correct my issues. Thanks for the pointers!
Title: Re: DSC Alarm System plugin
Post by: harphaulingdad on June 03, 2011, 11:31:38 am
Started over. Did the SSH cleanout suggested several pages back. Reinstalled the 7 files and followed the instructions exactly, and all seems to be working. Hitting the Save button on the Dashboard is a must to get everything working. Now for some fun!
Title: Re: DSC Alarm System plugin
Post by: strangely on June 03, 2011, 01:06:53 pm
Cool, good news.
Title: Re: DSC Alarm System plugin
Post by: harphaulingdad on June 03, 2011, 02:57:12 pm
Does anyone know where I could legally download the DSC DLS3 software for programming the DSC system? Since I've got an IP connection to the system, I believe this would allow me to change the keypad zone names. The previous version requires a serial connection, and I'm lazy enough to not want to open my panel now that I've got it working and put in the serial connection to my IT-100.
Title: Re: DSC Alarm System plugin
Post by: strangely on June 03, 2011, 03:11:51 pm
I can send you the DLSIV software, but you wont be able to program over the IT100. It has to be via the RS232 connector on the board.
Title: Re: DSC Alarm System plugin
Post by: stevenroka on June 19, 2011, 04:02:14 pm
I have installed everything and the wiznet serial adapter is not showing up.  The wiz110SR is connected to LAN port 1 on the back of the Vera 2.  I can ping the adapter at 192.168.1.10. Why is it not showing up in my serial port configuration?
Title: Re: DSC Alarm System plugin
Post by: strangely on June 19, 2011, 05:00:12 pm
If the WIZnet is set up correctly then the only thing you need to enter in the advanced tab of the DSC Plugin itself, is just the IP address and port of the WIZnet like this:

192.168.1.10:5000

The above is presuming that you are not using the IPserial plugin!



Title: Re: DSC Alarm System plugin
Post by: stevenroka on June 19, 2011, 05:18:47 pm
I've entered it under the advanced tab and all seems to be ok except when I click set clock, nothing happens and also, under the advanced tab, "controlled via" says no parent/please select.
Title: Re: DSC Alarm System plugin
Post by: strangely on June 19, 2011, 05:47:38 pm
Nothing needs to be selected for the controlled by dropdown.

Did you enter your PIN when you tried set time?
Title: Re: DSC Alarm System plugin
Post by: stevenroka on June 20, 2011, 11:12:23 pm
All is good now, thank you.  The one issue I have is with changing the zones.  After I rename a zone it changes it back to zone ... after a few minutes.  Anyway to make the Zone name stick?
Title: Re: DSC Alarm System plugin
Post by: strangely on June 20, 2011, 11:54:07 pm
All is good now, thank you.  The one issue I have is with changing the zones.  After I rename a zone it changes it back to zone ... after a few minutes.  Anyway to make the Zone name stick?
OK good news!

Renaming the Zone labels in Vera won't work I'm afraid. I suggest reading back a bit through this thread as there a few ways to get them to display the way you want in Vera.

Essentially if you already have Zone labels programmed that show up on your keypads, then its relatively easy with a "label broadcast". If not then you'll either have to program them with an full Alpha message keypad, or by using the DSC DLS software!

Title: Re: DSC Alarm System plugin
Post by: Kyle on June 21, 2011, 01:20:09 pm
I've noticed that when I click the ARM button by Pin Options, I have to enter a valid pin and it puts the system in stay mode. But when I click ARM under the One Touch Options, I don't have to enter a PIN and it puts the system in away mode. Shouldn't both ARM buttons put the system in the same mode? Or is this how the plug-in was designed?

Thanks
-Kyle
Title: Re: DSC Alarm System plugin
Post by: computerjohn on June 23, 2011, 11:13:54 pm
strangely how are you my friend?  Hope all is well..  Sorry I have been MIA, but been super busy & just got back from Aruba a week ago.  So what have I missed?
Title: Re: DSC Alarm System plugin
Post by: strangely on June 23, 2011, 11:26:07 pm
I've noticed that when I click the ARM button by Pin Options, I have to enter a valid pin and it puts the system in stay mode. But when I click ARM under the One Touch Options, I don't have to enter a PIN and it puts the system in away mode. Shouldn't both ARM buttons put the system in the same mode? Or is this how the plug-in was designed?

Thanks
-Kyle
I'll give this a try with mine also and see if the behavior is the same.
Title: Re: DSC Alarm System plugin
Post by: Kyle on June 24, 2011, 12:55:26 am
Maybe you can answer this for me too.. What do the iNight and Night buttons do? It seems to just put my system in stay mode.
Title: Re: DSC Alarm System plugin
Post by: strangely on June 24, 2011, 03:22:37 am
strangely how are you my friend?  Hope all is well..  Sorry I have been MIA, but been super busy & just got back from Aruba a week ago.  So what have I missed?

I'm good thanks :)

So apart from the other stuff going on with interface standardization, there's nothing to really update at the moment I'm afraid!
Title: Re: DSC Alarm System plugin
Post by: guessed on June 27, 2011, 09:59:44 pm
Maybe you can answer this for me too.. What do the iNight and Night buttons do? It seems to just put my system in stay mode.

On a DSC, that's what they do.

Some other Alarm systems support a "night mode", which is similar to stay, but some of the motion sensors are active (it's 1/2 way between Stay and Arm in the DSC)

For the standardization effort, we added a super-set of all commands so that these different Panel modes could be supported.  For Panels that don't have a specific mode, they "map" it to one of their existing modes.

The iXxxxxx are "instant" or no-delay versions, without the typical exit-delay that the other modes would have.  I wanted short labels ;)
Title: Re: Re: Re: DSC Alarm System plugin
Post by: computerjohn on June 27, 2011, 11:08:46 pm
strangely how are you my friend?  Hope all is well..  Sorry I have been MIA, but been super busy & just got back from Aruba a week ago.  So what have I missed?

I'm good thanks :)

So apart from the other stuff going on with interface standardization, there's nothing to really update at the moment I'm afraid!

That's ok buddy. I think I have to hard reset my Vera anyway. I have random lights turning on and my PRI setting is no. Not thrilled, since I have 50 devices.

Title: Re: DSC Alarm System plugin
Post by: Kyle on June 27, 2011, 11:20:52 pm
Maybe you can answer this for me too.. What do the iNight and Night buttons do? It seems to just put my system in stay mode.

On a DSC, that's what they do.

Some other Alarm systems support a "night mode", which is similar to stay, but some of the motion sensors are active (it's 1/2 way between Stay and Arm in the DSC)

For the standardization effort, we added a super-set of all commands so that these different Panel modes could be supported.  For Panels that don't have a specific mode, they "map" it to one of their existing modes.

The iXxxxxx are "instant" or no-delay versions, without the typical exit-delay that the other modes would have.  I wanted short labels ;)

That's why I'm a little confused. I figured that iNight and Night would put the alarm in Night mode. When my system is in stay mode and I hit *1 on a keypad, it will put the system in night mode and arm everything but whatever zone I have set to "night mode". But when I hit iNight and Night it just puts the system in stay mode..
Title: Re: Re: Re: DSC Alarm System plugin
Post by: strangely on June 27, 2011, 11:29:48 pm

That's ok buddy. I think I have to hard reset my Vera anyway. I have random lights turning on and my PRI setting is no. Not thrilled, since I have 50 devices.

If you have a backup of when it was working that includes a dongle backup, then you could most likely recover it doing a restore dongle firmware.
Title: Re: DSC Alarm System plugin
Post by: guessed on June 27, 2011, 11:54:47 pm
That's why I'm a little confused. I figured that iNight and Night would put the alarm in Night mode. When my system is in stay mode and I hit *1 on a keypad, it will put the system in night mode and arm everything but whatever zone I have set to "night mode". But when I hit iNight and Night it just puts the system in stay mode..
Ok, the (v1.1) Developer's Guide API that I had for the IT100 didn't have a code for triggering NightMode on a DSC.  If someone can find the code for that, then it would be simple enough to add it in.

Reading the spec I have, it's probably a code like 034...039.  It may be possible to work it out by looking at the Log output that the Plugin captures, and sifting through for the log line with "652" in it that would be printed out after doing the *1 thing that you mention.


@strangely, can you try this out sometime and let me know what the log output is?  If may not work if NightMode has some sort of DSC-Model# dependency, but it's worth giving it a shot.
Title: Re: Re: Re: Re: Re: DSC Alarm System plugin
Post by: computerjohn on June 28, 2011, 12:36:05 am

That's ok buddy. I think I have to hard reset my Vera anyway. I have random lights turning on and my PRI setting is no. Not thrilled, since I have 50 devices.

If you have a backup of when it was working that includes a dongle backup, then you could most likely recover it doing a restore dongle firmware.

I should, but since the sw update and the Z-Wave not setup on 3.20 the tech support stated it was best to just redo.  :(  Do i have to unpair each device first or can I just reset and pair each device again?

Title: Re: DSC Alarm System plugin
Post by: strangely on June 28, 2011, 02:07:15 am
I'm afraid the devices will have to be excluded either before or after you reset to be able to include them again.
Title: Re: DSC Alarm System plugin
Post by: strangely on June 28, 2011, 03:30:31 am
@strangely, can you try this out sometime and let me know what the log output is?  If may not work if NightMode has some sort of DSC-Model# dependency, but it's worth giving it a shot.

So I tried this a little while back but I stupidly armed it in away mode I think before hitting *1, and I'll need to do it again tomorrow in Stay mode when I'm not liable to wake the house up with keypads chirping etc. (I was lucky I never set the whole alarm off :) )

Looking at the IT100 documents I have it seems to be referenced:

Partition Armed - Descriptive Mode 652 (36, 35, 32h) 2 (Partition 1 - 8 (031-038h, *Mode) XX XX CR(0Dh) LF(0Ah)
This command indicates that a partition has been armed and the mode it has been armed in. This command is sent at the end of an Exit Delay and
after an alarm if the Bell Cutoff expires.
*Modes: 000 (30, 30, 30h) = Away
001 (30, 30, 31h) = Stay
002 (30, 30, 32h) = Away, No Delay
003 (30, 30, 33h) = Stay, No Delay
004 (30, 30, 34h) = Night

Looks like this was in the 1.0 version of the developers guide, but for some reason they took it out of the 1.1 version!

Anyways I'll try it again tomorrow and send you the log to confirm.
Title: Re: DSC Alarm System plugin
Post by: Kyle on June 28, 2011, 10:20:54 am
That's why I'm a little confused. I figured that iNight and Night would put the alarm in Night mode. When my system is in stay mode and I hit *1 on a keypad, it will put the system in night mode and arm everything but whatever zone I have set to "night mode". But when I hit iNight and Night it just puts the system in stay mode..
Ok, the (v1.1) Developer's Guide API that I had for the IT100 didn't have a code for triggering NightMode on a DSC.  If someone can find the code for that, then it would be simple enough to add it in.

Reading the spec I have, it's probably a code like 034...039.  It may be possible to work it out by looking at the Log output that the Plugin captures, and sifting through for the log line with "652" in it that would be printed out after doing the *1 thing that you mention.


@strangely, can you try this out sometime and let me know what the log output is?  If may not work if NightMode has some sort of DSC-Model# dependency, but it's worth giving it a shot.


I captured the log of setting night mode from the keypad. See the attached log file. Hope this helps
Title: Re: DSC Alarm System plugin
Post by: guessed on June 28, 2011, 11:44:47 am
You may have truncated the log output a little early, since there should be log lines after the ones you've shown.  From the output given so far, there's no indication of Night Mode being activated.

Given @strangely's information above, I was expecting to see something like:
Code: [Select]
    debug processIncoming:: Command=652, Data='14', Checksum=xx <0x3c10>
Title: Re: Alarm Panels and interface standardization
Post by: strangely on July 16, 2011, 03:22:42 am
[I also modified the JSON code for both the DSC and Paradox plugins to simplify the Device's Dialog (screenshot attached), and modified the Event/Scene section to use the RequestArmMode method exclusively (just in case we decommission the RequestQuickArmMode action)

These can all be seen in the trunk version of the DSC Alarm code (which @strangely is testing for me before I publish it wider)

The DSC changes seem so far to be OK, but I'll likely need a couple of days over the weekend to be sure.
Title: Re: DSC Alarm System plugin
Post by: jmmorgan on July 27, 2011, 07:42:04 pm
This is a great form and I was just able to install my DSC to my Vera and it works fine.  I can alarm and disalarm my system, but I can not find any "breach" event.  I tried "alarmed active", but it doesn't get trigger when I open a zone.  I am just trying to create a simple scene that will turn on one of my lights when the alarm is set off. 
Thanks
John
Title: Re: DSC Alarm System plugin
Post by: strangely on July 27, 2011, 08:32:03 pm
You don't need to configure a breach event to do that. Assuming that all of the individual door sensors are showing up in your dashboard, and you've configured them correctly, and you can see that they turn turn from a standing blue man when you open a door etc, to a running red man, then you just need to use one of these senors as the the "event" in your scene that controls the light.

The door sensors will work Independently with Vera, and don't depend on the actual alarm armed status.
Title: Re: DSC Alarm System plugin
Post by: jmmorgan on July 27, 2011, 08:36:47 pm
Thanks for the answer.  However, I just wanted to be notified if any zone is violated.  I really did not want to monitor all of them individually.
John
Title: Re: DSC Alarm System plugin
Post by: strangely on July 27, 2011, 08:49:47 pm
OK sorry I think I understand now, the attached is roughly how you should set it up, and this is presuming that the alarm was actually in the "armed" state (or it wont work). For the commands tab you just need a light selected.

Otherwise if you don't want to do this when the alarm is actually "armed" then you just need to create a scene that has multiple events configured for each of the sensors (one scene with multiple events)
Title: Re: DSC Alarm System plugin
Post by: jmmorgan on July 30, 2011, 11:55:30 am
Thanks.  I did that initially and it worked one time, but then stopped working.  I have reset everything and it works most of the time.  I think the problem is the DSC system has intermittant issue with updating the status of the alarm system (i.e. it says it is ready, when it is actually alarmed).

Now I am trying to get the smoke detector to work.  When I set off the smoke detector, it does set off the breach scene (because the alarm goes off), but I would also like to have another scene that emails me that the house is on fire  :(.  I have added an event for zone F, which should be trigger when the smoke detection goes off, but it doesn't.  Any help would be appreciated.
John
Title: DSC fire alarm
Post by: jmmorgan on August 05, 2011, 02:14:54 pm
I have the DSC 1832 connected to the Vera 2 panel and it works pretty well.  However, I have been unable to get Vera to respond to the fire alarm trigger. Currently it is set up as Zone F. I have tried all combination without success.  Does anyone know how to set it up?  Do I need to set up a serial port for it?  The other zones 1-8 do not have a serial port assigned to them and they work fine.  Any help would be appreciated.
John
Title: Re: DSC Alarm System plugin
Post by: strangely on August 05, 2011, 07:35:58 pm
Do you have a wireless or wired smokes? I presume wired?!

I've never tried this with my smokes (wireless).
Title: Re: DSC Alarm System plugin
Post by: jmmorgan on August 06, 2011, 08:17:14 am
It is a hard wire fire alarm to PGM2.  I have been trying to log it, but I can not capture all of the log out put.  Is there a way to download log files so that I can open them in a text program?
Thanks
John
Title: Re: DSC Alarm System plugin
Post by: jmmorgan on August 07, 2011, 10:06:57 am
So I have been able to log and understand the output somewhat.  There is a variable in the DSC device/module call AuxInputAlarm that get set to "1" when the fire alarm goes off.  However, I can not capture this as an event because the "DSC device/module" is not in the list of devices in the event tab.  Can the AuxInputAlarm variable be added to Zone F???
Thanks
John
Title: Re: DSC Alarm System plugin
Post by: jmmorgan on August 11, 2011, 06:58:26 pm
I was wondering if there is a way to put a command in the implementation file, which set the Zone F SecuritySensor1 variable: Tripped based upon the DSCAlarmPanel variable: AuxinputAlarm.  Therefore, when the fire alarm goes off and set AuxinputAlarm to 1, it also set the Zone F SecuritySensor1 variable: Tripped to 1.  I can then create a scene using Zone F device.  Any help would be greatly appreciated.
John
Title: Re: DSC Alarm System plugin
Post by: radarengineer on August 12, 2011, 11:03:27 pm
When I moved into my house last fall it had a DSC 832 PowerSeries Alarm System with a bad control board. I was able to get a really good deal on a new DSC 1832 system a few months ago with the intention of hooking it up to this plugin and all my existing sensors.

Anyway, long story short is earlier this week I finally ordered an IT-100. Today I finally wired up the alarm system and programmed it (in all honestly, it still needs a little tweaking!). The DSC programming is a little daunting but I think I finally have it down.

Just now I hooked up an old USB to serial adapter I had lying around, loaded up the plugin, and its working! I still need to finish adding my sensors to the alarm system. I have another 20 or so wireless door/window sensors to program in :o. But my wired sensors and the few wireless I've programmed so far are showing up great :)

But this is terrific. I think @strangely and @guessed have put in a lot of work on this? I just wanted to let you know I *really* appreciate it.
Title: Re: DSC Alarm System plugin
Post by: guessed on August 13, 2011, 01:43:13 pm
@radarengineer,
Glad to hear it's working for you.  Definitely a number of people have contributed to get this going to the level it's at today (dev, testing, docs etc)

If you'd like to contribute to the doc or anything, just let us know and we can get you an account/privs to edit the Wiki space.  I'm sure we can make things easier for other folks wanting to get up and running.
Title: Re: DSC Alarm System plugin
Post by: radarengineer on August 14, 2011, 03:52:40 pm
I might take you up on that, one thing that is missing from the wiki (although it is certainly mentioned here in the thread) is how to set the zone labels on the control panel.

I just ordered a pc-link and will be trying to set mine with DLS2002 when it arrives. I'll try to take comprehensive notes as I think that process is something that would be good to have documented.

I've been collecting some other information about programming a DSC system as I had to do mine from scratch. However, maybe that is information that we should let people find elsewhere.
Title: Uploading is not stripping the path out of the file name
Post by: jmmorgan on August 14, 2011, 04:03:07 pm
I am trying to up load a new DSCALarmPanel1.xml, but it is include my path in the name  "C%3A%5CUsers%5CJohn%5CDocuments%5CVera2%5CI_DSCAlarmPanel1.xml".  Therefore, it is not over writing the file and I have this new file - name "C%3A%5CUsers%5CJohn%5CDocuments%5CVera2%5CI_DSCAlarmPanel1.xml", which I do not want.  Any thought on how to avoid this.
Thanks
John
Title: Re: Uploading is not stripping the path out of the file name
Post by: guessed on August 14, 2011, 04:09:27 pm
Sounds like you used IE to upload the Plugin files.  If that's the case, use another Browser, as the Plugin upload functionality is known to have issues with IE.

@strangely, you may want to tweak the install instructions to reference this:
    http://wiki.micasaverde.com/index.php/Install_LUUP_Plugins

I've just modded it to include the "don't use IE" reference...

I am trying to up load a new DSCALarmPanel1.xml, but it is include my path in the name  "C%3A%5CUsers%5CJohn%5CDocuments%5CVera2%5CI_DSCAlarmPanel1.xml".  Therefore, it is not over writing the file and I have this new file - name "C%3A%5CUsers%5CJohn%5CDocuments%5CVera2%5CI_DSCAlarmPanel1.xml", which I do not want.  Any thought on how to avoid this.
Thanks
John

Title: Re: DSC Alarm System plugin
Post by: guessed on August 14, 2011, 04:56:19 pm
@radarengineer,
You have access to write/amend Wiki pages for it now.

I might take you up on that, one thing that is missing from the wiki (although it is certainly mentioned here in the thread) is how to set the zone labels on the control panel.

I just ordered a pc-link and will be trying to set mine with DLS2002 when it arrives. I'll try to take comprehensive notes as I think that process is something that would be good to have documented.

I've been collecting some other information about programming a DSC system as I had to do mine from scratch. However, maybe that is information that we should let people find elsewhere.
Title: Re: DSC Alarm System plugin
Post by: jmmorgan on August 14, 2011, 05:19:08 pm
Thanks for information about uploading files.  I think I have a work around for my fire alarm issue. My current 2 wire fire alarms system is connected to Aux and PGM 2 as outline in the DSC installation manual.  When the fire alarm goes off it set the Aux Input Alarm to 1, which is in the DCS panel device, but you cannot monitor it from this device.  Therefore, in the DSC panel, I set the smoke zones as “17”, which created a device Zone 17.  Then in the I_DSCAlarmPanel1.xml file I added four lines of code as below, which set the Zone 17 as tripped, or not, based upon the Aux Input alarm setting.



   ["631"] = {"panel", "Aux Input Alarm Set",
                function (cmd, data)    -- Aux input alarm
                setDSCPanelState("AuxInputAlarm", "1")
                local zone = extractZone("Zone-17")
                setZoneState(tonumber(zone), "1")
                task("Aux Input Alarm Set", TASK_ERROR_PERM)
            end},
        ["632"] = {"panel", "Aux Input Alarm Restore",
                function (cmd, data)    -- Aux input alarm restored
                setDSCPanelState("AuxInputAlarm", "0")
                local zone = extractZone("Zone-17")
                setZoneState(tonumber(zone), "0")               
                task("Aux Input Alarm Restore", TASK_SUCCESS)
            end},
Title: Re: DSC Alarm System plugin
Post by: guessed on August 14, 2011, 05:41:07 pm
@jmmorgan,
I'm not clear on why you have to do this.  When that [Panel] event occurs, it already triggers any Scene you've attached to the Panel itself, including the "Auxiliary Input Alarm" event - and it'll fire any Scene you've setup for that.

Is this not working?

You shouldn't need to have the intermediary device, and there's currently no way to us to set it's state correctly when the Alarm panel code restarts (for whatever reason)
Title: Re: DSC Alarm System plugin
Post by: jmmorgan on August 14, 2011, 07:31:48 pm
@guessed
When you set up a scene, you can not select the panel as a device in the event tab.  Is there someplace else you can select the panel?
John
Title: Re: DSC Alarm System plugin
Post by: guessed on August 14, 2011, 09:57:34 pm
The Panel Device itself has a bunch of events hanging off it, so you can define events against the Panel itself (this one included). 

It should be showing up, but I need @strangely to validate it's working on his end as I have no way to validate it at my end anymore (I returned the panel he loaned to me to develop the original code)

@guessed
When you set up a scene, you can not select the panel as a device in the event tab.  Is there someplace else you can select the panel?
John

Title: Re: DSC Alarm System plugin
Post by: macgeekbrian on August 15, 2011, 02:01:16 pm
Hi,

I've installed my DSC 1616, IT-100 and WizNet as instructed, and all seem to work fairly well, arm/disarm works, and the zones update as they are opened/closed/violated. Only problem is that the system status does not update at all on my Vera 2 (most current firmware, UI4).

Any clues where I might look for a problem? I have the WizNet plugged directly into the IT-100, so I think I've eliminated cabling as a possibility.

Also, has anyone tried to use SQ Remote to control their DSC through Vera? I'd like iPhone control, but haven't figured out how to make that leap.

Any help much appreciated...this forum is awesome! :)

Brian
Title: Re: DSC Alarm System plugin
Post by: macgeekbrian on August 15, 2011, 02:05:38 pm
UPDATE: fixed the status update issue...just needed to do a browser refresh, and now it updates perfectly. Duh. :)
Title: Re: DSC Alarm System plugin
Post by: strangely on August 15, 2011, 04:25:39 pm
I need @strangely to validate it's working on his end as I have no way to validate it at my end anymore
So the attached are the options that I see for events, I've never tested if Alarm Active works for anything other than an actual breach event (to notify me) which they do, and I'll have to set off a smoke at some point to check this works for them also; however I do have Wireless smokes and they are configured as Zones, and so I expect it work the same.
Title: Re: DSC Alarm System plugin
Post by: strangely on August 15, 2011, 04:34:17 pm

Also, has anyone tried to use SQ Remote to control their DSC through Vera? I'd like iPhone control, but haven't figured out how to make that leap.

So this is being worked on by all the Control Point integrators, and also with the respective Plugin writers to standardize this in order that SQRemote etc can do this.

The temporary work around is to create a separate scene for the each of the functions you want to achieve. I currently have the following:

Leave house (Turns everything off and Arms the Alarm)
Arm Stay
Arm Stay
Disarm

The only problem with the above is that you'll have to store the Pin code in the Scene.

Once you have the Scenes created and saved, then just reload SQRemote (or refresh its devices) and then assign a button the new Scenes.
 
Title: Re: DSC Alarm System plugin
Post by: automator.app on August 15, 2011, 05:25:22 pm

Also, has anyone tried to use SQ Remote to control their DSC through Vera? I'd like iPhone control, but haven't figured out how to make that leap.


Automator.app supports any mios device including alarms and works on both iPhones and iPads.
Title: Re: DSC Alarm System plugin
Post by: jmmorgan on August 15, 2011, 05:35:10 pm
@guessed
As @strangely stated, his smoke detector are wireless and set up as a zone, which works fine for that set up.  However, my smoke detectors are wired to PGM2 and not a zone.  When they go off, the alarm breach will be set ("alarm active").  However, someone breaking into the house would also set the "alarm active".  I would not know if someone broke into the house or the house is on fire.  I would have to check to see if all 16 zones were intack to determine that no one broke into the house, but rather the house is on fire.  That is why I did a work around to have the Auxalarminput set "Zone-17" as tripped, which represents my smoke detector - even though they are not on a Zone.
John
Title: Re: DSC Alarm System plugin
Post by: strangely on August 15, 2011, 06:00:43 pm
@guessed
As @strangely stated, his smoke detector are wireless and set up as a zone, which works fine for that set up.  However, my smoke detectors are wired to PGM2 and not a zone.  When they go off, the alarm breach will be set ("alarm active").  However, someone breaking into the house would also set the "alarm active".  I would not know if someone broke into the house or the house is on fire.  I would have to check to see if all 16 zones were intack to determine that no one broke into the house, but rather the house is on fire.  That is why I did a work around to have the Auxalarminput set "Zone-17" as tripped, which represents my smoke detector - even though they are not on a Zone.
John

Thats what Cameras are for :)

Seriously though, so long as I get a notification that something is going on, I'm happy, although I can see your point.



Title: Re: DSC Alarm System plugin
Post by: guessed on August 15, 2011, 09:16:40 pm
Still shouldn't have to do that, so I must have missed something in the JSON for the Panel.

You are supposed to "see" events for BOTH the Panel, and the Partition.  Each of these will be from a separate MiOS Device, one each for the Panel and Partition respectively.

The images that @strangely posted are for the Partition Device (#298 from the pictures).  There should be another Device (with a lesser Id) that's the Panel itself, upon which the other event types hang - notably for you is the one in this line of declaration:

    http://code.mios.com/trac/mios_dscalarmpanel/browser/trunk/D_DSCAlarmPanel1.json#L177

If that's missing, then either the JSON is missing in the install, or there's something amiss with it (which is always possible).  I didn't have a way to test that functionality when I first wrote it, but there are other events in there that should show up also that can be trialed.

Admittedly, it's not bubbled up as a device, but it should be bubbled as a Panel-level scene event that can be hooked into (for notifications and such)

@guessed
As @strangely stated, his smoke detector are wireless and set up as a zone, which works fine for that set up.  However, my smoke detectors are wired to PGM2 and not a zone.  When they go off, the alarm breach will be set ("alarm active").  However, someone breaking into the house would also set the "alarm active".  I would not know if someone broke into the house or the house is on fire.  I would have to check to see if all 16 zones were intack to determine that no one broke into the house, but rather the house is on fire.  That is why I did a work around to have the Auxalarminput set "Zone-17" as tripped, which represents my smoke detector - even though they are not on a Zone.
John

Title: Re: DSC Alarm System plugin
Post by: jmmorgan on August 16, 2011, 05:38:36 pm
Unfortunately, I can not select the alarm panel from the scene event menu.  It is device #13, but it does not show up in the list of devices.
John
Title: Re: DSC Alarm System plugin
Post by: chiphead on August 24, 2011, 02:12:01 pm
Using the plugin. 12 zones and 1 partition. Love it! Works well, just
have a request to the developer.
Please don't set the name of the zones at every Luup reload. If forces
the renaming of the zones.
Title: Re: DSC Alarm System plugin
Post by: strangely on August 24, 2011, 06:52:13 pm
Do you have zone names defined within your system?
Title: Re: DSC Alarm System plugin
Post by: radarengineer on August 30, 2011, 02:57:00 pm
@Strangely,

I was able to program my names in using dls2002 (my panel is 5.1 so I can't use the newer software). I was afraid it wouldn't work as my actual alarm panels don't support named zones. I want to keep pulling names from my system like it is set up now.

But I think it would be nice if users could supply a comma separated list of zone names? That would save people from having to buy a pclink and spend hours fighting with the dls software. I think the code would be pretty simple, when I get access to my vera again in a week or two I could take a crack at it?
Title: Re: DSC Alarm System plugin
Post by: balez1 on September 06, 2011, 08:26:18 am
Hi together,

I try the latest plugin DSC and test a few easy scene only with one alarm events.

Now I want to create a scene with a calendar and an event alarm state  'armed'
When I am away the alarm  state  armed is actived, then I can command a few device according to the calendar programmation.

When the alarm state 'armed' is false, then the scene is not actived, no device commanded.

How can I do to create this scene?
What is the code for alarm state 'armed'?
 Can I do some thing like this
armed= luup.variable_get(urn:schemas-micasaverde-com:device:AlarmPartition:2","Status",nn)
if(armed=="0")then
  return false
end


Thanks



Title: Re: DSC Alarm System plugin
Post by: balez1 on September 08, 2011, 06:20:49 pm
I found a heavy solution with a Virtual State Device.
I create two scene with alarm State   Armed and Disarmed
The scene trigger the Virtual State Device  ON/OFF
With the On OFF Switch, in the Luup Code of each enabled scene

local arme=luup.variable_get("urn:upnp-org:serviceId:SwitchPower1","Status",69)
if(arme=="0")then
  return false
end

I enable the scenes with alarm armed or not.

Is it not possible to change the code of the state of the Virtual State Device with the code of the state of the alarm Partition armed or disarmed, it will be more light .... ;D

Thanks
Title: Troubles with IT100
Post by: StephenMorris on September 26, 2011, 12:26:04 am
Looking for advice.

I have the IT-100 hooked up to a WizNet board and I don't think it's working correctly.
I connect to the WizNet via their DeviceTerminal.exe program, essentially 'Hyper-terminal' via WizNet.
Anyway, I get the output from the IT-100, time stamps and alerts, but I don't think I can send any commands.

If I understand correctly, I should be able to send a command such as 00090 and get back some sort of acknowledgment, but I get back nothing. And this seems wrong.

Question 1. Should I be getting something back from my 00090?
Question 2, if I am supposed to get something back, any ideas on what might be wrong? I have tried multiple straight through cables, both made by me 2,3,5 -> 2,3,5, and commercial with same result. I also tried a look back test of WizNet and that part seems to work, i.e. messages went both ways.

For grins, I tried your pluggin, I got the 6 zones with default names. When ever I try to do anything including setting the clock and get something like Device not Ready or something.

Advice?
Title: Re: DSC Alarm System plugin
Post by: strangely on September 26, 2011, 02:02:44 am


Do you see any of the zones trip (standing blue man turns to running red man) when a door opens?
Title: Re: DSC Alarm System plugin
Post by: StephenMorris on September 27, 2011, 06:28:13 pm
No running man...
Title: Re: DSC Alarm System plugin
Post by: strangely on September 28, 2011, 02:08:41 am
Is there any status messages such as the plugin failing where the clock in vera is?

For some suggestions:

Check that the baud rate settings are correct in the wiznet if you haven't done so already (9600). It may be worth confirming that the IT100 is using 9600 (it should be by default), but to confirm and reset it to default, it probably worth disconnecting it from the keybus, grounding pins 2 and 3 of the DB9 and then reconnecting the keybus until the LED flashes.

I think earlier in this thread somewhere I posted an example picture of how the wiznet should be configured, you may want to check that also.

Check that all the files are present by re-downloading them from code.mios.com and then uploading them to Vera again (I assume you got them from there?)

If all of that fails then you'll want to make sure that you have verbose logging enabled and grab the LuaUPnP.log from /tmp/log/cmh if your comfortable with this.
Title: Re: DSC Alarm System plugin
Post by: StephenMorris on September 28, 2011, 11:33:37 am
Thanks for the suggestions. I've arraigned to have a spare IT-100 delivered, so I'll give that a try this weekend too.
I have a feeling the one I have is either broken, or perhaps has a loose wire or something.

If the second one fails same as first, I'll be back with more info. I have looked at the logs in verbose mode and didn't see anything that looked like good communications. It did seem to connect, but that was about it.

More details later..

Thanks for the help, and much thanks for working on this plugin!

  Steve
Title: Re: DSC Alarm System plugin
Post by: StephenMorris on October 01, 2011, 08:17:14 pm
I have running man! :)

Not yet sure what it was, I changed two things. I swapped out the IT-100 AND I changed the wiznet board from "mixed" to "server".

I'm sure I have lots to learn now that it's working. But a quick question.
Now that I can presumably detect when someone disarms the system, can I tell which code was used, i.e. who did it?

Thanks much. Lots to learn, lots to do.

  Steve
Title: Re: DSC Alarm System plugin
Post by: strangely on October 01, 2011, 10:51:23 pm
Good News!!

So regarding the PIN code there is a notification for "A Pin code is entered" but I've never used it, and so I don't know if that works... It does work for locks though :)

I was just trying to see if I could set it up to do it, but my Vera seems to be stuck a bit between the UI5 and UI4, and the facility to do notifications seems to be missing.

@guessed may chime in before I get the chance to take a look as I'm on my way out of the door now, but he'll know if the IT-100 protocol supports that, and whether it was coded to work that way! I have suspicion it was!
Title: Re: DSC Alarm System plugin
Post by: guessed on October 02, 2011, 01:45:03 pm
The common interface supports it, but it looks like I left out that implementation in the DSC code...   oops.

ServiceID: urn:micasaverde-com:serviceId:AlarmPartition2
Variable: LastUser

Assuming the DSC gives it to me (still need to research) we'll need to define some semantics on when it's set, specifically whether it's set prior to the ArmMode, or after. 

I suggest we need to set it before setting the ArmMode, so that the user "Value" is readable in that event.  The downside will be that, in the User-entered-a-PIN Event, you will only be able to read the previous ArmMode, not the newly set one.
Title: Re: DSC Alarm System plugin
Post by: StephenMorris on October 02, 2011, 03:50:55 pm
More testing on the rough setup. I swapped back to the original IT-100, and that works fine. I think all the troubles was because I had the wiznet set to 'mixed' instead of server.

Regarding the user pin, I think it certainly would be useful to know Who armed or disarmed the system. In particular, this is a vacation house and I know that the cleaning people come on Thursday between 8-noon, but any other time is something to be concerned about. Similarly, I have codes that I give to various contractors and service people. They don't come except when I ask them to. So their code doing anything is of interest.

Not so interesting, is anyone using our family code. Though someone else might be interested in giving 'junior' his own code and tracking his return in the evening.

I don't have the zone names setup on my system as I don't have the installer code. I have contacted my installer and he's going to setup my system on it's own private installer code next week and give me that. That seems pretty reasonable to me.
That said, from my reading today on zone names, it would seem like it might be a good feature for your code, if you did have a way to override the zone names to handle the case where a user can't get the installer code.

Thanks a lot for all the work, that's gotten me this far, very much appreciated!
  Steve
Title: Re: DSC Alarm System plugin
Post by: guessed on October 04, 2011, 12:25:37 am
@strangely,
I've tagged 0.3 version of the DSC Code, can you pull it down sometime and test it a little before I link it from the docs?

The specific changed between 0.3 and 0.21 include:

a) Populating the LastUser Variable upon receipt of DSC 700 "User Closing", and 750 "User Opening", events
b) Populating the UserStatusData Variable upon receipt of any type of Partition event.
c) This build no longer requires the PINCode to be passed to the *Arm methods, and "acts" like a *QuickArm when you don't pass it in, per the change in the spec back in July.
d) Support for the ArmedInstant mode, per the spec rev in July for Florin

Users will be recorded something like "00005", leading zero's and all.  I can trim these out if you'd prefer, so let me know and we'll tweak before it's broadly rolled out.

I'm not exactly sure when the 700 and 750 alarm events occur relative to the other events that I get, so the "LastUser" may not be populated when people want it ;-)

It should at least make the "A PIN Code is entered" and "Vendor Status Code" both a little more usable.

The common interface supports it, but it looks like I left out that implementation in the DSC code...   oops.

ServiceID: urn:micasaverde-com:serviceId:AlarmPartition2
Variable: LastUser

Assuming the DSC gives it to me (still need to research) we'll need to define some semantics on when it's set, specifically whether it's set prior to the ArmMode, or after. 

I suggest we need to set it before setting the ArmMode, so that the user "Value" is readable in that event.  The downside will be that, in the User-entered-a-PIN Event, you will only be able to read the previous ArmMode, not the newly set one.
Title: Re: DSC Alarm System plugin
Post by: strangely on October 04, 2011, 07:17:36 pm
Been away for a couple of days traveling but will give it a go once I get back. It may not work for me anyway (or at least to test properly) since I think something is broken with my Vera after migrating back from UI5, and setting up of new notifications no longer seems possible.
Title: Re: DSC Alarm System plugin
Post by: broberts on October 13, 2011, 04:00:46 pm
So I've been reading this thread and believe I think things configured correctly (WizNet is in "server" mode, cable is straight-through, port and IP look correct, but alas no running man when I open doors.    :(

I'm experiencing the same sort issues StephenMorris was seeing -- creates devices ok, I can ping the Wiznet, the IT-100 is flashing, but I don't see any updates in the zones when they are tripped and I cannot arm via the "Partition 1" device in IU4.  When I click "Poll Now" on the parent device I named DSC, I get "Delivery Failed" -- but I don't see anything in /var/log/LuaUPnP.log pertaining to this device.  Am I looking in the wrong place?
Title: Re: DSC Alarm System plugin
Post by: strangely on October 13, 2011, 08:35:54 pm
Did you follow the setup instructions here?:

http://code.mios.com/trac/mios_dscalarmpanel

Also double check your cable or maybe use another one perhaps? Somebody else had this issue where the cable was bad.


/var/log/LuaUPnP.log is the right place to look, but make sure you have your Vera set for verbose logging in advanced and the log tab!
Title: Re: DSC Alarm System plugin
Post by: broberts on October 13, 2011, 08:45:12 pm
Indeed I did follow those directions and I have an extremely short cable run.  ;)
Title: Re: DSC Alarm System plugin
Post by: broberts on October 13, 2011, 08:58:09 pm
So I'm in verbose mode and when I did a refresh I see item in /tmp/log/cmh/LuaUPnP.log and I see things like this, but nothing is jumping as an error:
Code: [Select]
35 10/13/11 17:47:54.057 IOPort::Run starting for 15 <0x4011>
25 10/13/11 17:47:54.058 IOPort::Connect device 15 connecting to 192.168.xx.xx:5000 iodevice: 0 path (null) <0x4011>
25 10/13/11 17:47:54.059 IOPort::Connect connect 1: 192.168.xx.xx:5000 <0x4011>
25 10/13/11 17:47:54.062 IOPort::Connect connect 3: 192.168.xx.xx:5000 m_socket_handle 13 <0x4011>
25 10/13/11 17:47:54.062 IOPort::Connect OK 192.168.xx.xx:5000 <0x4011>
32 10/13/11 17:47:54.060 ThreadedClass::StartThread class 0x801ee8 started 0x4011 <0x402>
50 10/13/11 17:47:54.072 luup_log:15: DSCAlarmPanel: debug ActivePartitions: 1 <0x402>
50 10/13/11 17:47:54.073 luup_log:15: DSCAlarmPanel: debug Appending Child: 1 <0x402>
11 10/13/11 17:47:54.073 Child_Devices::AddChild id Partition-1 parent id  device type urn:schemas-micasaverde-com:device:DSCAlarmPartition:2 parent device: 15 devfile:D_DSCAlarmPartition2.xml desc:Partition 1 parms:  <0x402>
50 10/13/11 17:47:54.075 luup_log:15: DSCAlarmPanel: debug Door Sensors: 2,3,4,19,20 <0x402>
50 10/13/11 17:47:54.076 luup_log:15: DSCAlarmPanel: debug Appending Child: 2 <0x402>
11 10/13/11 17:47:54.077 Child_Devices::AddChild id Zone-2 parent id  device type urn:schemas-micasaverde-com:device:MotionSensor:1 parent device: 15 devfile:D_MotionSensor1.xml desc:Zone 2 parms: urn:micasaverde-com:serviceId:SecuritySensor1,Armed=1 <0x402>

Anything in particular I should be looking for?
Title: Re: DSC Alarm System plugin
Post by: broberts on October 13, 2011, 09:20:34 pm
I'm seeing: 
Code: [Select]
10 10/13/11 18:02:55.428 Device_Variable::m_szValue_set device: 14 service: urn:micasaverde-com:serviceId:HaDevice1 variable: Configured startup: 1 v:0x818168/NONE <0x400>
10 10/13/11 18:02:55.429 Device_Variable::m_szValue_set device: 15 service: urn:micasaverde-com:serviceId:DSCAlarmPanel1 variable: ActivePartitions startup: 1 v:(nil)/NONE <0x400>
10 10/13/11 18:02:55.430 Device_Variable::m_szValue_set device: 15 service: urn:micasaverde-com:serviceId:DSCAlarmPanel1 variable: DoorZones startup: 2,3,4,19,20 v:(nil)/NONE <0x400>
10 10/13/11 18:02:55.431 Device_Variable::m_szValue_set device: 15 service: urn:micasaverde-com:serviceId:DSCAlarmPanel1 variable: MotionZones startup: 5,6,7 v:(nil)/NONE <0x400>
10 10/13/11 18:02:55.432 Device_Variable::m_szValue_set device: 15 service: urn:micasaverde-com:serviceId:DSCAlarmPanel1 variable: SmokeZones startup: 1,8,9,10,17,18 v:(nil)/NONE <0x400>
10 10/13/11 18:02:55.432 Device_Variable::m_szValue_set device: 15 service: urn:micasaverde-com:serviceId:DSCAlarmPanel1 variable: EnableRemoteArm startup: stay v:(nil)/NONE <0x400>
10 10/13/11 18:02:55.433 Device_Variable::m_szValue_set device: 15 service: urn:micasaverde-com:serviceId:DSCAlarmPanel1 variable: EnableRemotePanic startup: false v:(nil)/NONE <0x400>
10 10/13/11 18:02:55.434 Device_Basic::m_eConfigured_set device 15 was 0 now 0 <0x400>
...
01 10/13/11 18:03:04.210 LuImplementation::StartLua running startup code for 15 I_DSCAlarmPanel1.xml failed <0x402>

And at the IU I now see
DSCAlarmPanel:
EnableRemoteArm Parameter must be either blank, false or a value from the wiki...

from the http://code.mios.com/trac/mios_dscalarmpanel  I tried

with the same basic result.  :(

What should I be looking for?
Title: Re: DSC Alarm System plugin
Post by: strangely on October 14, 2011, 12:43:15 am
Wow that is a short serial cable :)

As far the RemoteArm Parameter goes, leave it as disarm for the time being as that gives the plugin the least restrictions while you are testing!

Do you have anything else you can test the WIZnet with to confirm its working, or maybe temporarily try the alarm/IT100 with a USB-Serial Adapter?

Title: Re: DSC Alarm System plugin
Post by: strangely on October 14, 2011, 11:08:47 am
@strangely,
I've tagged 0.3 version of the DSC Code, can you pull it down sometime and test it a little before I link it from the docs?

I've been running the 0.3 versions for a few days and seems to be working fine in all respects including the new PIN code feature.

Do you need any logs, or more testing before you link the new version?

Might be worth getting @StephenMorris to give it a try since I'm not sure we'll use this function much (due to keyfobs and Kwickset locks that do the same type of function) and it would be good to get his input perhaps as I only have two PINs set up (mine and my Wife)
Title: Re: DSC Alarm System plugin
Post by: StephenMorris on October 14, 2011, 02:02:59 pm
Couple things.

I too love that short cable, brilliant!

I"m happy to try the new code, but the house is remote and while I have the use case baked, I haven't spent the time yet to figure out how to implement it. I need more time than I've had to figure this out. That said, if someone wants to be my guide, it would take less time, as otherwise, I will be learning the old fashion way.

I have been on hold because I didn't have Zone labels nor did I have the installer code. I had the installer come out this AM, and viola, I now have labels!


Thanks All!

  Steve
Title: Re: DSC Alarm System plugin
Post by: strangely on October 14, 2011, 02:44:07 pm
@StephenMorris,

Setup should be quite easy as you can just update the plugin files by uploading them from where you added them originally (Mios developers button and Luup files tab)

I can attach the files here to make it easy for you to find if you like?

All you need do to get it working is go to the notifications tab for the alarm partition child device (the one with the padlock) and create a new notification for a PIN code is entered for each of the PINs you want to monitor and against which MiOS user account you want the alert to go to.

The trickiest part for you will be to figure out which PIN represents which user as it will depend on what order they were originally inputted into the alarm. The user code that the plugin is looking out for starts with 0001 and increment 0002 etc for each PIN since you wont be entering the PINs directly when you set up the notification.

See the attached examples to help set up.
Title: Re: DSC Alarm System plugin
Post by: broberts on October 14, 2011, 04:47:12 pm
Thanks strangely! -- it was indeed a RS232 comm problem.  Wrong bps.  We have a running men now!

Question about the Zone labels:
When I first connected, I initially did a label broadcast from a keypad I had painstakenly stuck in nice labels before vera integration.  They didn't seem to take (ie. UI4 still showed "Zone X"

Worse my painstakenly put in labels seem to have been wiped out, and the vera label are not sticking (ie. I change one, then it goes back to "Zone X" when I change another.

Am I missing something here?
Title: Re: DSC Alarm System plugin
Post by: strangely on October 14, 2011, 06:46:40 pm
@broberts, great news!

Did you do a label broadcast when the IT100 was installed or after? If it was before then you'll need to redo it from the keypad that you programmed the labels from! Once that's done, the next time the plugin reloads, or something updates the dashboard, then the default Vera labels of zone01, zone02 etc will be replaced. Don't forget that the broadcast has to be from the keypad you did the label programming from originally!

Don't worry, Vera will not have overwritten the ones you painstakingly programmed from your keypad :) unfortunately labeling the zones either in the panel itself, or from a keypad (and label broadcast) are the only way to have them named the way you want them in Vera, the plugin currently doesn't support renaming the defaults like you would a Z-Wave device etc :(

Title: Re: DSC Alarm System plugin
Post by: broberts on October 15, 2011, 09:22:38 pm
I have my labels now -- thanks!

So I'm having a couple of issues:

#1 Sometimes the devices get stuck in the wrong state. e.g. a door sensor did trip, but it is cleared now ... but Vera still thinks it's open. I did a page reload, LUA restart, and a reboot, all to no effect.  The physical keypads show the correct info, but not UI4.   I finally needed to open and close the physical door to update the value.  How is it getting so out of sync? 

#2 I'm having trouble accessing the status via LUUP. I'm using (where 15 is the device # of the main DSC device):
   my_var=luup.variable_get("urn:micasaverde-com:serviceId:DSCAlarmPanel1","Armed",15)
What am I doing wrong?
Title: Re: DSC Alarm System plugin
Post by: strangely on October 15, 2011, 11:10:44 pm

Quote
#1 Sometimes the devices get stuck in the wrong state. e.g. a door sensor did trip, but it is cleared now ... but Vera still thinks it's open. I did a page reload, LUA restart, and a reboot, all to no effect.  The physical keypads show the correct info, but not UI4.   I finally needed to open and close the physical door to update the value.  How is it getting so out of sync? 
Hmm not sure about this as mine only ever goes out of sync if a door was opened when the plugin failed to load (I get this on random plugins from time to time, and is a bug in the MiOS engine).

It sounds like you may still be having communication problems perhaps?!
How many zones do you have? Have you used the EMI filter on the keybus wire to the IT100?
Might need to see the log to see whats really going on!

Quote
#2 I'm having trouble accessing the status via LUUP. I'm using (where 15 is the device # of the main DSC device):
   my_var=luup.variable_get("urn:micasaverde-com:serviceId:DSCAlarmPanel1","Armed",15)
What am I doing wrong?
Never tried this but I suspect you may need to be using the partition instead! *shines special @guessed Bat symbol in the sky*
Title: Re: DSC Alarm System plugin
Post by: guessed on October 16, 2011, 01:31:35 am
Events occur on the Partition, not on the Panel.  You'll see the Armed state in the Advanced tab of the Alarm's Partition objected if you hover the mouse over the name, you'll see the fully qualified ServideId to do with the ArmMode (or DetailedArmMode) variable.
Title: Re: DSC Alarm System plugin
Post by: StephenMorris on October 19, 2011, 10:14:10 pm
I won't be able to try the the PIN change for about a week and a half, but will be happy to do it then.
The setup as you described seems very easy. If I wanted to quality that by time of day and week, is there anyway to do that?
I.e. if pin code #2 is entered anytime other than 7-12am Wednesday.. then notify. I realize that's a bit advanced but certainly doing things based on time of day/time would be nice.

Last question, I think I can pull the svn version you checked, so no need to post the code.
When I update the files, do I have to delete the old ones, or do I just upload the new ones over top of the existing ones?

Thanks again!

  Steve
Title: Re: DSC Alarm System plugin
Post by: strangely on October 19, 2011, 11:00:16 pm
Quote
If I wanted to quality that by time of day and week, is there anyway to do that?
I.e. if pin code #2 is entered anytime other than 7-12am Wednesday..

Sounds possible with a little bit of luup code in the scene and there should be a few examples around in the forum of similar if you search.

Quote
When I update the files, do I have to delete the old ones, or do I just upload the new ones over top of the existing ones?

Nope just upload and restart and it will replace them! There's only two of the files that changed but I always overwrite all of them anyway.
Title: Re: DSC Alarm System plugin
Post by: guessed on October 19, 2011, 11:07:28 pm
In Luup, it's this bit of Scene snippet to add:
    http://wiki.micasaverde.com/index.php/Luup_Scenes_Events#Access_the_current_time

The event is still the same, but the Luup snippet is used to "fail" if the time is out of bounds, so the notification won't go out in that case.
Title: Re: DSC Alarm System plugin
Post by: StephenMorris on October 21, 2011, 10:12:04 pm
Looks promising. I loaded the change set 58 code, and using the debug feature, determined what my user code was from the log.
I then set two notifications, one for my code, and the other for my code + 1. I then disarmed the system, and got the notification for my user. I have two other users setup, but don't recall the codes, so I can't test that till I go on-site in another week and reset them.

I haven't tested the time base filtering, but other than a bit of trial and error for my first Lua program, it looks simple enough.
Also may filter or chain events to remove the ARMs and only trigger on the DISARMs. But all of this stuff is stock Lua stuff.

The GUI for creating multistage triggers seems awkward, seems like it can be done, but I would think I could set a notification that would only fire if two (or more) conditions were set. But again, that seems like a UI4 thing.

Thanks guys. I'll do more testing in a week, but so far so good.

Title: Re: DSC Alarm System plugin
Post by: guessed on October 21, 2011, 10:19:00 pm
Yup, version 58 is the same as this Tag:
    http://code.mios.com/trac/mios_dscalarmpanel/browser/tags/0.3 (http://code.mios.com/trac/mios_dscalarmpanel/browser/tags/0.3)

There's a variable that gets set each time someone performs an arming/disarming event, and you should be able to see that under the DSC Partition Device.  It'll give you the "User #" that you need in the other parts, esp if you've recently activated/deactivated via the Keypad - this should avoid the need to go to the Debug logs.
Title: Re: DSC Alarm System plugin
Post by: StephenMorris on October 21, 2011, 11:14:33 pm

Little more testing.. no problem that I've noticed with the user code, but I can't get it to arm in "away" mode, it keep going into "stay" mode.
I use the UI4 GUI to enter my code and enter ARM, and it goes into ExitDelay and then to Stay mode.
I'm not at the site, so all I can see is the log and the UI4 GUI.

50      10/21/11 23:02:41.232   luup_log:4: DSCAlarmPanel: debug Partition::User Opening 750 partition: 1 user: 0040 <0x3c10>
50      10/21/11 23:02:44.550   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=650, Data='1', Checksum=CC <0x3c10>
50      10/21/11 23:02:44.569   luup_log:4: DSCAlarmPanel: debug Partition::Ready 650 partition: 1 <0x3c10>
50      10/21/11 23:03:12.779   luup_log:4: DSCAlarmPanel: debug Action::RequestArmMode Armed <0xd40e>
50      10/21/11 23:03:12.780   luup_log:4: DSCAlarmPanel: debug extractPartition: Partition 1 <0xd40e>
50      10/21/11 23:03:12.818   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=500, Data='033', Checksum=2B <0x3c10>
50      10/21/11 23:03:13.269   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=904, Data='006', Checksum=33 <0x3c10>
50      10/21/11 23:03:13.269   luup_log:4: DSCAlarmPanel: debug Panel::Beep Status 904 data: 006 <0x3c10>
50      10/21/11 23:03:13.682   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=905, Data='0101', Checksum=60 <0x3c10>
50      10/21/11 23:03:13.682   luup_log:4: DSCAlarmPanel: debug Panel::Tone Status 905 data: 0101 <0x3c10>
50      10/21/11 23:03:13.836   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=656, Data='1', Checksum=D2 <0x3c10>
50      10/21/11 23:03:13.840   luup_log:4: DSCAlarmPanel: debug Partition::Exit Delay in Progress 656 partition: 1 <0x3c10>
50      10/21/11 23:03:13.862   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=903, Data='21', Checksum=FF <0x3c10>
50      10/21/11 23:03:13.863   luup_log:4: DSCAlarmPanel: debug Panel::LED Status Armed (ON) <0x3c10>
50      10/21/11 23:03:13.866   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=903, Data='41', Checksum=01 <0x3c10>
50      10/21/11 23:03:13.867   luup_log:4: DSCAlarmPanel: debug Panel::LED Status Bypass (ON) <0x3c10>
50      10/21/11 23:03:13.913   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=901, Data='00032Exit Delay in   Progress        ', Checksum=E4 <0x3c10>
50      10/21/11 23:03:13.913   luup_log:4: DSCAlarmPanel: debug Panel::LCD Update 90100032Exit Delay in   Progress         <0x3c10>
06      10/21/11 23:03:13.914   Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:DSCAlarmPanel1 variable: LCD was: Date     Time OCT 21/11 11:02p now: Exit Delay in   Pr
ogress #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x3c10>
50      10/21/11 23:03:47.600   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=905, Data='0301', Checksum=62 <0x3c10>
50      10/21/11 23:03:47.601   luup_log:4: DSCAlarmPanel: debug Panel::Tone Status 905 data: 0301 <0x3c10>
50      10/21/11 23:03:57.871   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=652, Data='11', Checksum=FF <0x3c10>
50      10/21/11 23:03:57.894   luup_log:4: DSCAlarmPanel: debug Partition::Partition Armed - Descriptive Mode 652, Partition 1 (Stay) <0x3c10>
50      10/21/11 23:03:57.900   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=903, Data='10', Checksum=FD <0x3c10>
50      10/21/11 23:03:57.902   luup_log:4: DSCAlarmPanel: debug Panel::LED Status Ready (OFF) <0x3c10>
50      10/21/11 23:03:57.927   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=901, Data='00032System Armed    in Stay Mode  <>', Checksum=94 <0x3c10>
50      10/21/11 23:03:57.928   luup_log:4: DSCAlarmPanel: debug Panel::LCD Update 90100032System Armed    in Stay Mode  <> <0x3c10>


Title: Re: DSC Alarm System plugin
Post by: rayjr13 on October 22, 2011, 06:24:18 pm
Not sure what my malfunction is but I get teh following status messgae in UI4  after my initla setup...


DSCAlarmPanel:
cannot send command: '001'

Using the it-100 and wiz110SR  and the short cable method.  cat5 back to home ethernet switch.  i can ping the wiz and the ip/port settings match up.  I'm not sure that i missed anything else


edit:  Ha Wiznet was in client mode, then mixed, looks like server was what was needed.  leaving it up in case someone else runs into the same.

BTW thanks for the development
Title: Re: DSC Alarm System plugin
Post by: strangely on October 22, 2011, 10:24:58 pm
Welcome to the MCVDSC world :)

Ah yes the infamous client mode! I guess I should get round to writing a bit of a troubleshooting guide on the Wiki. I posted the WIZnet settings here in this thread somewhere and I guess its gotten too many replies now for people to want to read all of it!
Title: Re: DSC Alarm System plugin
Post by: rayjr13 on October 22, 2011, 10:39:59 pm
 8)No definitely read...but the search function when i wanted to go back and find it...useless lol.
I had forgotten the wording that was posted.  I never did get the labels to poll and show for the zones, but realistically i like the length on the dashboard for new labels over the keypad char limit.  But they dont stick! *sigh*


Have a question though.  Which codes are the "Vendor Codes referring to?"  is this the SIA reporting code?  or is the something I missed reading the IT-100 manual.

thanks for replying.

oh also were there values somewhere (wiki?) for the EnableRemotePanic
Title: Re: DSC Alarm System plugin
Post by: strangely on October 22, 2011, 11:01:58 pm
Quote
I never did get the labels to poll and show for the zones,

Have you tried a label broadcast?

Quote
Which codes are the "Vendor Codes referring to?"
These are so that you can add extra events for things like a panel trouble light or something like that, if you have the developer guide then you can find them in there. I think only the partition level ones are working at the moment.

Quote
oh also were there values somewhere (wiki?) for the EnableRemotePanic
I thought it was but don't see it now; there's recently been some edits so it may have been removed! Let me do double check and get back to you.
Title: Re: DSC Alarm System plugin
Post by: guessed on October 22, 2011, 11:24:41 pm
The EnableRemotePanic option is <blank>, false or panic
Title: Re: DSC Alarm System plugin
Post by: rayjr13 on October 23, 2011, 08:41:57 am
Thanks I'll set to panic.

Broadcast yes, it said it completed after running for a few seconds, but no change on vera after save refresh and even power down and back up.  And like you said.before vera labels didnt overwrite keypad labels.  I even changed some zone numbers in the advanced device setting to make them reload.

I understand the purpose of vendor codes for your script but I didn't see "vendor codes" in the it-100 guide did I miss it or are they called something else?  Are these the SIA codes?

Thanks guys glad to see you are still working on this and available.
Title: Re: DSC Alarm System plugin
Post by: strangely on October 23, 2011, 12:50:43 pm
@rayjr13? How many keypads do you have?

The vendor codes aren't really listed as "vendor codes" but if you look in the 1.1 version of the guide then they are listed in bold on page 11-15 (this is the PDF page number not whats printed on the page) under the "command" column!

Not all of them work as some are tied to the panel device (parent) rather than the partition (child). For instance if you want to set up an event to notify you that AC power is lost (code 802) then this doesn't work, but the one for LED trouble does (840)
Title: Re: DSC Alarm System plugin
Post by: guessed on October 23, 2011, 01:57:34 pm
@strangely,
If you wanted to add/experiment with Panel states, you can hook it here:

    http://code.mios.com/trac/mios_dscalarmpanel/browser/trunk/I_DSCAlarmPanel1.xml#L811

and make a series of calls to setDSCPanelState(...) instead of the setPartitionState(...) calls I'm making for the Partition in this code:

    http://code.mios.com/trac/mios_dscalarmpanel/browser/trunk/I_DSCAlarmPanel1.xml#L817

You'd just have to work out how to change the data extraction a little, since the "partition" variable isn't in the messages for Panel events.
Title: Re: DSC Alarm System plugin
Post by: guessed on October 23, 2011, 02:03:15 pm
@StephenMorris,
@strangely might know better as he's more familiar with the Panel.

As far as I can see, it's going through the correct sequence, but at the last minute it's indicating it went into Stay-Arm mode for some reason (with some Bypasses set, perhaps?)



Little more testing.. no problem that I've noticed with the user code, but I can't get it to arm in "away" mode, it keep going into "stay" mode.
I use the UI4 GUI to enter my code and enter ARM, and it goes into ExitDelay and then to Stay mode.
I'm not at the site, so all I can see is the log and the UI4 GUI.

50      10/21/11 23:02:41.232   luup_log:4: DSCAlarmPanel: debug Partition::User Opening 750 partition: 1 user: 0040 <0x3c10>
50      10/21/11 23:02:44.550   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=650, Data='1', Checksum=CC <0x3c10>
50      10/21/11 23:02:44.569   luup_log:4: DSCAlarmPanel: debug Partition::Ready 650 partition: 1 <0x3c10>
50      10/21/11 23:03:12.779   luup_log:4: DSCAlarmPanel: debug Action::RequestArmMode Armed <0xd40e>
50      10/21/11 23:03:12.780   luup_log:4: DSCAlarmPanel: debug extractPartition: Partition 1 <0xd40e>
50      10/21/11 23:03:12.818   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=500, Data='033', Checksum=2B <0x3c10>
50      10/21/11 23:03:13.269   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=904, Data='006', Checksum=33 <0x3c10>
50      10/21/11 23:03:13.269   luup_log:4: DSCAlarmPanel: debug Panel::Beep Status 904 data: 006 <0x3c10>
50      10/21/11 23:03:13.682   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=905, Data='0101', Checksum=60 <0x3c10>
50      10/21/11 23:03:13.682   luup_log:4: DSCAlarmPanel: debug Panel::Tone Status 905 data: 0101 <0x3c10>
50      10/21/11 23:03:13.836   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=656, Data='1', Checksum=D2 <0x3c10>
50      10/21/11 23:03:13.840   luup_log:4: DSCAlarmPanel: debug Partition::Exit Delay in Progress 656 partition: 1 <0x3c10>
50      10/21/11 23:03:13.862   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=903, Data='21', Checksum=FF <0x3c10>
50      10/21/11 23:03:13.863   luup_log:4: DSCAlarmPanel: debug Panel::LED Status Armed (ON) <0x3c10>
50      10/21/11 23:03:13.866   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=903, Data='41', Checksum=01 <0x3c10>
50      10/21/11 23:03:13.867   luup_log:4: DSCAlarmPanel: debug Panel::LED Status Bypass (ON) <0x3c10>
50      10/21/11 23:03:13.913   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=901, Data='00032Exit Delay in   Progress        ', Checksum=E4 <0x3c10>
50      10/21/11 23:03:13.913   luup_log:4: DSCAlarmPanel: debug Panel::LCD Update 90100032Exit Delay in   Progress         <0x3c10>
06      10/21/11 23:03:13.914   Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:DSCAlarmPanel1 variable: LCD was: Date     Time OCT 21/11 11:02p now: Exit Delay in   Pr
ogress #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x3c10>
50      10/21/11 23:03:47.600   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=905, Data='0301', Checksum=62 <0x3c10>
50      10/21/11 23:03:47.601   luup_log:4: DSCAlarmPanel: debug Panel::Tone Status 905 data: 0301 <0x3c10>
50      10/21/11 23:03:57.871   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=652, Data='11', Checksum=FF <0x3c10>
50      10/21/11 23:03:57.894   luup_log:4: DSCAlarmPanel: debug Partition::Partition Armed - Descriptive Mode 652, Partition 1 (Stay) <0x3c10>
50      10/21/11 23:03:57.900   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=903, Data='10', Checksum=FD <0x3c10>
50      10/21/11 23:03:57.902   luup_log:4: DSCAlarmPanel: debug Panel::LED Status Ready (OFF) <0x3c10>
50      10/21/11 23:03:57.927   luup_log:4: DSCAlarmPanel: debug processIncoming:: Command=901, Data='00032System Armed    in Stay Mode  <>', Checksum=94 <0x3c10>
50      10/21/11 23:03:57.928   luup_log:4: DSCAlarmPanel: debug Panel::LCD Update 90100032System Armed    in Stay Mode  <> <0x3c10>
Title: Re: DSC Alarm System plugin
Post by: rayjr13 on October 23, 2011, 06:16:20 pm
@rayjr13? How many keypads do you have?

The vendor codes aren't really listed as "vendor codes" but if you look in the 1.1 version of the guide then they are listed in bold on page 11-15 (this is the PDF page number not whats printed on the page) under the "command" column!

Not all of them work as some are tied to the panel device (parent) rather than the partition (child). For instance if you want to set up an event to notify you that AC power is lost (code 802) then this doesn't work, but the one for LED trouble does (840)

I have one keypad and one partition

I have version 1.0 of the manual but i think i follow you.  IT-100 originated commands like 802.  but are there also the response codes, responded value back from an application command/request.

Asking the command "100"   may yield "840" if there is a trouble LED  like in the example of the guy who wanted to know if he had ac power loss or something like that.  the Trouble LED is probably the best way he's gonna know if there is/was an issue.

thanks for the clarification i'm crystal now
Title: Re: DSC Alarm System plugin
Post by: StephenMorris on October 25, 2011, 09:13:13 am
Still not on site so I can't know what the keypad actually says, but I have a second program that I use to monitor the DSC via the DSC Alarm Monitor iPhone apps, and a DSC TL150. Anyway DSC Alarm Monitor is reporting that the unit is in 'Away Armed' mode.

I won't know until I get there what the keypad really says, but it's starting to feel like perhaps a display problem with one or the other apps?

I did see the bypass in the log. No idea what that is about, I didn't set any bypass's.

Is there any more info I can get you?

 
Title: Re: DSC Alarm System plugin
Post by: strangely on October 25, 2011, 01:06:37 pm
It does sound like its a programming issue with the panel, especially if the TLink also reports it as stay mode; the TLink and the IT100 are essentially keypads anyway, so if they are reporting this then your keypads will also indicate this. I'm interested to find out what happens when you arm Away mode from the TLink also?

The bypass you see in the logs I think is correct as essentially it bypasses things like PIR sensors in stay mode and likely would also likely be doing this for whatever your problem is also.
Title: Re: DSC Alarm System plugin
Post by: broberts on October 27, 2011, 04:35:22 am
Quote
#1 Sometimes the devices get stuck in the wrong state. e.g. a door sensor did trip, but it is cleared now ... but Vera still thinks it's open. I did a page reload, LUA restart, and a reboot, all to no effect.  The physical keypads show the correct info, but not UI4.   I finally needed to open and close the physical door to update the value.  How is it getting so out of sync? 
Hmm not sure about this as mine only ever goes out of sync if a door was opened when the plugin failed to load (I get this on random plugins from time to time, and is a bug in the MiOS engine).

It sounds like you may still be having communication problems perhaps?!
How many zones do you have? Have you used the EMI filter on the keybus wire to the IT100?
Might need to see the log to see whats really going on!
Alright -- I was restarting the Lua engine a lot as I add in scenes, change labels, etc and I do see some plug-in load issues.  So I'll continue to watch this.

I have 15 zones (though I haven't figured how to access the PGM2 input for the smoke detector yet).  I don't think I have a comm issue (I don't see any comm errors in the log). 

I do see errors like this from time to time:
Code: [Select]
01 10/27/11 1:09:32.532 ZWJob_PollNode::Run job job#20 :pollnode #13 (0x7619f8) N:13 P:100 S:1 ZW_Send_Data to node 13 failed 1 req 0x8fad60/1 abort m_iFrameID 0 <0xc04>
01 10/27/11 1:10:19.143 Mongoose XXX-mg_stop1 0x764d10 1 2 <0x400>
01 10/27/11 1:10:21.160 Mongoose XXX-mg_stop2 0x764d10 2 2 <0x400>
01 10/27/11 1:10:21.161 Mongoose XXX-mg_stop3 0x764d10 2 2 <0x400>
01 10/27/11 1:10:21.162 Mongoose XXX-mg_stop4 0x764d10 8386480 2 <0x400>
01 10/27/11 1:10:23.180 ZWJob_PollNode::Abort job job#29 :pollnode #3 (0x861ba0) N:3 P:100 S:5 to node 3 failed 4 <0x400>
01 2011-10-27 1:10:23 caught signal 11 <0x400>
01 10/27/11 1:10:26.340 UPnPAction_Send::ParseState can't find name <0x400>
01 10/27/11 1:10:34.084 LuaInterface::CallFunction_Startup-1 device 15 function alarmStartup failed [string "..."]:643: bad argument #3 to 'format' (string expected, got no value) <0x402>
01 10/27/11 1:10:34.085 LuImplementation::StartLua running startup code for 15 I_DSCAlarmPanel1.xml failed <0x402>
Quote
#2 I'm having trouble accessing the status via LUUP. I'm using (where 15 is the device # of the main DSC device):
   my_var=luup.variable_get("urn:micasaverde-com:serviceId:DSCAlarmPanel1","Armed",15)
What am I doing wrong?
Never tried this but I suspect you may need to be using the partition instead! *shines special @guessed Bat symbol in the sky*
Thanks for the insight!
Title: update on Arm and User codes
Post by: StephenMorris on October 29, 2011, 11:51:19 am
I am on site today and did some more testing.

The Alarm on PIN code seems to be working fine. I was able to setup a couple more user codes and test that they fire the correct user.

As for the system ARMing in stay mode vs Away mode, here's what I learned.
Using the physical keypad, if I enter my key-code, the system will ARM in Stay mode. Of course if I open/close a door during the exit delay it would arm in Away mode.
If I press and hold the AWAY button, the system will arm in Away mode.

Going back to the trace that I sent you are sending code 33, which is ARM with Pin code,

Turns out in the pluggin I was entering in a PIN code and then hitting ARM, and it would send code 33 and it would end up in Stay mode.
Now that I understand that, I discover that I can hit ARM in the pluggin without a PIN code, and presumably you then send code 30, and I end up in AWAY mode. I tested that and it worked as expected, and I ended up in Arm Away mode, as desired.

So the confusion, was that I didn't understand that the PIN code in the pluggin was optional, and how the behaviour would differ depending on if I put it in or not.

At this point, I think the pluggin is working as designed, and I have no outstanding requests, or complaints. Only a minor suggest that you make it clearer that the PIN code is optional or some other way to clearly trigger an ARM. I don't have a great suggestion on that UI design.

As always thanks!

  Steve
Title: Re: update on Arm and User codes
Post by: guessed on November 01, 2011, 10:35:04 pm
At this point, I think the pluggin is working as designed, and I have no outstanding requests, or complaints. Only a minor suggest that you make it clearer that the PIN code is optional or some other way to clearly trigger an ARM. I don't have a great suggestion on that UI design.

Ok, interesting that there's some sort of config that let's "PIN Arm" downshift to "PIN Stay" if you don't Exit.  I never saw that in my testing, but I was using a single-Zone setup that @strangely had setup to get it functioning, so it's possible other things came into play in that minimum setup.

The "No PIN required" is newer functionality.  We used to have separate Buttons for PIN Arm and Instant Arm (and the corresponding other functions) but @mcvflorin requested we merge these recently.  ... with the resulting behavior being as you describe (assuming that the Instant Arm is enabled in the respective panel)

The doc hasn't caught up to that change just yet.


@strangely: let me know when you're ready for me to release the Tag, and I'll move the download link (or you can, I'm not fussed)
Title: Re: DSC Alarm System plugin
Post by: rayjr13 on November 05, 2011, 05:41:59 pm
 ??? ???

Alright still cant figure out what i'm missing i continue to try to broadcast the labels from the keypad using code [998].  it shows "broadcastin.." on the keypad but nothing changes opn vera when its done.  If i change the name in vera for the devices  a seconds after i rename and save, it refreshes back to Zone X.

any thoughts guys
Title: Re: DSC Alarm System plugin
Post by: strangely on November 05, 2011, 06:03:05 pm
Are you sure you used the keypad the labels were originally broadcast from? Also what are you typing in for the broadcast?

Maybe list the part numbers of the alarm system, keypad/s, and also if you know which slots the keypads are assigned to on the system?
Title: Re: DSC Alarm System plugin
Post by: rayjr13 on November 05, 2011, 06:31:47 pm
Only one keypad in the house.

Typing *8 Installer code * 998 *

Keypad is slot #8 ( I believe i will recheck)

PC5010 with LCD5500
Title: Re: DSC Alarm System plugin
Post by: strangely on November 05, 2011, 06:39:30 pm
OK so it sounds like the Keypad is conflicting with the IT100 (also uses slot 8 ), and you may have to move the Keypad to another slot and then attempt the broadcast again.
Title: Re: DSC Alarm System plugin
Post by: rayjr13 on November 05, 2011, 08:00:23 pm
The IT100 wears shades lol. J/k

I moved it from 18 to 17 partition 1 slot 7. Now lets see.

so far nothing.  rebroadcast and still no labels.  Zones are still not responding.  The keypad default was 18.

btw these are all wireless zones so zone 9-17.  I have no wired zones for 1-8
Title: Re: DSC Alarm System plugin
Post by: rayjr13 on November 05, 2011, 08:30:32 pm
so does the it-100 have a keypad partition/slot assignment somewhere?
Title: Re: DSC Alarm System plugin
Post by: strangely on November 05, 2011, 09:14:01 pm
Seems like the IT100 does indeed wear shades :) stupid bb code! (now corrected)

So yes the IT is hard coded for slot 8, and there was somebody else that had the same problem many posts back (@jimmac I think) that you've got.

I think so long as you can move the keypad away from 8, do the rebroadcast then you should be OK!

Title: Re: DSC Alarm System plugin
Post by: rayjr13 on November 05, 2011, 09:34:33 pm
set to slot 7 and nothing changed on vera
Title: Re: DSC Alarm System plugin
Post by: rayjr13 on November 05, 2011, 10:27:02 pm
 :(

dunno i changed it to slot 5 recheck enrollment [902]  then viewed it [903] saw Keypad 5, keypad 8, & PC5132 (wireless)

then rebroadcast, refreshed vera still nada
Title: Re: DSC Alarm System plugin
Post by: strangely on November 06, 2011, 12:03:14 am
Other than programing them directly to the panel with the DLS software, I'm kind of out of ideas.

You could try removing the power to the IT100 breifly and then maybe try the broadcast again?

The other thing you could do is make a post on the diysecurity.com forum and ask the question there perhaps? There are some weird and wonderful compatibility issues with these things depending on hardware and firmware versions, and maybe it's something like that?
Title: Re: DSC Alarm System plugin
Post by: rayjr13 on November 06, 2011, 12:08:18 am
really not going to stress it.  it works and the labels are what they are. maybe i will get motivated another weekend

thanks again
Title: Re: DSC Alarm System plugin
Post by: guessed on November 06, 2011, 12:26:58 am
@strangely,
It sounds like this one's a bit complex.  If you'd like, I can make this statement conditional, based upon some [new] Panel-Level configuration setting:

    http://code.mios.com/trac/mios_dscalarmpanel/browser/trunk/I_DSCAlarmPanel1.xml#L138

which would effectively disable the Labels being over-written from the Panel's values - allowing folks you set the manually.  I know you've asked for this before, but I've been reluctant to add it as it makes things less-automatic, but it sounds like there are use-cases where the current model isn't going to work (or actually adds complexity)

Let me know.  I'd have to code it blind, so you'd have to test it for me as it's likely I'll make a few mistakes  ;-)
Title: Re: DSC Alarm System plugin
Post by: strangely on November 06, 2011, 01:24:03 am
Sounds like a good thing to add if it doesn't cause you too much work?!
Title: Re: DSC Alarm System plugin
Post by: rayjr13 on November 06, 2011, 01:26:49 am
Besides that the labels can be much more descriptive using the plugin.  2cents
Title: Re: DSC Alarm System plugin
Post by: guessed on November 08, 2011, 08:40:29 am
@strangely,
I've built a 0.31 Tag, based upon the 0.3 tag that @StephenMorris was trying, with two additional fixes in it:

a) Add new EnableManualLabels Advanced parameter, default "false", that lets you override the Auto-labeling behavior
b) Fix a Button "Display" highlighting issue in the Partition.json file that @utz identified.

Can you try it sometime, and let me know so I can promote it to the version for the Wiki.
Title: Re: DSC Alarm System plugin
Post by: strangely on November 08, 2011, 10:36:12 am
Sure I'll try it today.
Title: Re: DSC Alarm System plugin
Post by: strangely on November 15, 2011, 12:31:35 pm
So I've been testing this for a couple of days with some of my sensors renamed and it seems to be working OK.

What was the other issue that was fixed concerning the highlighted button that @utz had?
Title: Re: DSC Alarm System plugin
Post by: guessed on November 15, 2011, 11:24:38 pm
In the Device dialog each of the arming buttons is supposed to highlight (green) when the panel is in that particular arming mode.

I didnt have that correctly set for Stay and Night modes.


Do you want to change the wiki's download link to use the new Label/Tag or shall I?
Title: Re: DSC Alarm System plugin
Post by: strangely on November 16, 2011, 12:20:41 am
I can do it, and I guess I should make an edit to point out how to enable renaming of the defaults.
Title: Re: DSC Alarm System plugin
Post by: jguidera on December 01, 2011, 04:09:41 pm
I've got the latest version of the file .31 (as far as I can tell) and in looking at the implementation xml I see the EnableManualLables flag, however I'm not seeing that parameter in the advanced tab of the system panel.  Should i?

[Update] ok it looks like I don't have the .31 files.  Next question is can I just upload the latest set of files or do I first need to delete the parent device, then the files and then re-create the device?  if I need to delete the files I assume I need to ssh into the box to do it?
Title: Re: DSC Alarm System plugin
Post by: guessed on December 01, 2011, 04:36:15 pm
@jguidera,
You just re-upload the new versions of the files, and then [Save] to force Vera to recognize them and pickup the new functionality.
Title: Re: DSC Alarm System plugin
Post by: jguidera on December 06, 2011, 09:14:09 am
@jguidera,
You just re-upload the new versions of the files, and then [Save] to force Vera to recognize them and pickup the new functionality.

Looks like that's working!
Title: Re: DSC Alarm System plugin
Post by: macgeekbrian on December 07, 2011, 02:59:16 pm
Hey Guessed, thanks for the manual zone label switch! It's great for folks who don't have a 5500 keypad (and/or don't want to mess with the label broadcast), and the labels carry through to SQ Remote. Awesome! :)

Brian
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 07, 2011, 05:15:15 pm
Finally got my DSC parts in and starting to get things installed. Right now I have the panel and keypad sitting on my desk connected to a wiznet card communicating with Vera. Now I need to start messing with my code in my android app to make sure things are working. I do see an issue, when I broadcasted the labels from the keypad, Vera picked up the labels, but there seems to be some weird spacing issues. I have attached showing what I mean.

- Garrett


Title: Re: DSC Alarm System plugin
Post by: strangely on December 07, 2011, 05:22:30 pm
Wow that's odd, maybe a UI5 issue? looks like its related to anything with an "O" in it only!

Title: Re: DSC Alarm System plugin
Post by: shady on December 07, 2011, 05:42:16 pm
I noticed they all seem to break (or space) after the 14th character.  Except for the DSC Alarm Panel device itself, but I assume this device wasn't a part of broadcasting the labels from the keypad
Title: Re: DSC Alarm System plugin
Post by: guessed on December 07, 2011, 11:22:27 pm
Garrett,
Are the spaces visible in the RAW sdata as well?  That'll really tell us if it's UI5 or the Plugin.

I just checked the DSC code, and there's nothing special in the label handling that I can see.
Title: Re: DSC Alarm System plugin
Post by: strangely on December 08, 2011, 12:07:44 am
Garrett, Which version of UI5 are you running?
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 08, 2011, 04:55:26 am
Garrett,
Are the spaces visible in the RAW sdata as well?  That'll really tell us if it's UI5 or the Plugin.

I just checked the DSC code, and there's nothing special in the label handling that I can see.

Yes, it is in the raw sdata. here is what my lu_sdata looks like for on of the sensors:

      {
         "name":"HT Sliding Doo  r",
         "altid":"Zone-9",
         "id":62,
         "category":4,
         "subcategory":3,
         "room":13,
         "parent":54,
         "armed":"1",
         "tripped":"0"
      },

Shady,

The DSC Alarm Panel, is the generated device when creating the plugin.

Strangely,

I am running on 1.5.201.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on December 08, 2011, 05:17:41 am
Ok, that's odd...

Can you set verbose logging (so I see the IO calls) and grep me the log lines during startup that contain either:

    570
    Broadcast Labels



I want to see what the panel is delivering to the plugin...


Thanks!
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 08, 2011, 05:37:24 am
Here you go:

50   12/08/11 5:36:36.305   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='001HT Motion Sens  or              ', Checksum=F9 <0x3c10>
50   12/08/11 5:36:36.306   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (001HT Motion Sens  or              ) <0x3c10>
50   12/08/11 5:36:36.373   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='002Zone    02                      ', Checksum=6C <0x3c10>
50   12/08/11 5:36:36.374   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (002Zone    02                      ) <0x3c10>
50   12/08/11 5:36:36.444   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='003Zone    03                      ', Checksum=6E <0x3c10>
50   12/08/11 5:36:36.445   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (003Zone    03                      ) <0x3c10>
50   12/08/11 5:36:36.513   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='004Zone    04                      ', Checksum=70 <0x3c10>
50   12/08/11 5:36:36.514   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (004Zone    04                      ) <0x3c10>
50   12/08/11 5:36:36.583   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='005Zone    05                      ', Checksum=72 <0x3c10>
50   12/08/11 5:36:36.584   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (005Zone    05                      ) <0x3c10>
50   12/08/11 5:36:36.665   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='006Zone    06                      ', Checksum=74 <0x3c10>
50   12/08/11 5:36:36.666   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (006Zone    06                      ) <0x3c10>
50   12/08/11 5:36:36.753   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='007Zone    07                      ', Checksum=76 <0x3c10>
50   12/08/11 5:36:36.754   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (007Zone    07                      ) <0x3c10>
50   12/08/11 5:36:36.804   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='008Zone    08                      ', Checksum=78 <0x3c10>
50   12/08/11 5:36:36.805   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (008Zone    08                      ) <0x3c10>
50   12/08/11 5:36:36.874   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='009HT Sliding Doo  r               ', Checksum=8F <0x3c10>
50   12/08/11 5:36:36.876   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (009HT Sliding Doo  r               ) <0x3c10>
50   12/08/11 5:36:36.952   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='010Garage Entry D  oor             ', Checksum=3A <0x3c10>
50   12/08/11 5:36:36.953   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (010Garage Entry D  oor             ) <0x3c10>
50   12/08/11 5:36:37.025   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='011Foyer Entry Do  or              ', Checksum=19 <0x3c10>
50   12/08/11 5:36:37.026   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (011Foyer Entry Do  or              ) <0x3c10>
50   12/08/11 5:36:37.112   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='012Zone    12                      ', Checksum=6E <0x3c10>
50   12/08/11 5:36:37.113   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (012Zone    12                      ) <0x3c10>
50   12/08/11 5:36:37.164   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='013Zone    13                      ', Checksum=70 <0x3c10>
50   12/08/11 5:36:37.165   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (013Zone    13                      ) <0x3c10>
50   12/08/11 5:36:37.234   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='014Zone    14                      ', Checksum=72 <0x3c10>
50   12/08/11 5:36:37.235   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (014Zone    14                      ) <0x3c10>
50   12/08/11 5:36:37.304   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='015Zone    15                      ', Checksum=74 <0x3c10>
50   12/08/11 5:36:37.305   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (015Zone    15                      ) <0x3c10>
50   12/08/11 5:36:37.385   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='016Zone    16                      ', Checksum=76 <0x3c10>
50   12/08/11 5:36:37.386   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (016Zone    16                      ) <0x3c10>
50   12/08/11 5:36:37.771   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='017Deck Entry Doo  r               ', Checksum=B1 __LEAK__ this:258048 start:258048 to 0xc30000 <0x3c10>
50   12/08/11 5:36:37.773   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (017Deck Entry Doo  r               ) <0x3c10>
50   12/08/11 5:36:37.780   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='018Zone    18                      ', Checksum=7A <0x3c10>
50   12/08/11 5:36:37.782   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (018Zone    18                      ) <0x3c10>
50   12/08/11 5:36:37.788   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='019Zone    19                      ', Checksum=7C <0x3c10>
50   12/08/11 5:36:37.789   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (019Zone    19                      ) <0x3c10>
50   12/08/11 5:36:37.795   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='020Zone    20                      ', Checksum=6C <0x3c10>
50   12/08/11 5:36:37.797   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (020Zone    20                      ) <0x3c10>
50   12/08/11 5:36:37.803   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='021Zone    21                      ', Checksum=6E __LEAK__ this:4096 start:262144 to 0xc31000 <0x3c10>
50   12/08/11 5:36:37.805   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (021Zone    21                      ) <0x3c10>
50   12/08/11 5:36:37.815   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='022Zone    22                      ', Checksum=70 __LEAK__ this:24576 start:286720 to 0xc37000 <0x3c10>
50   12/08/11 5:36:37.831   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (022Zone    22                      ) <0x3c10>
50   12/08/11 5:36:37.885   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='023Zone    23                      ', Checksum=72 __LEAK__ this:73728 start:360448 to 0xc49000 <0x3c10>
50   12/08/11 5:36:37.886   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (023Zone    23                      ) <0x3c10>
50   12/08/11 5:36:37.955   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='024Zone    24                      ', Checksum=74 __LEAK__ this:98304 start:458752 to 0xc61000 <0x3c10>
50   12/08/11 5:36:37.956   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (024Zone    24                      ) <0x3c10>
50   12/08/11 5:36:38.025   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='025Zone    25                      ', Checksum=76 <0x3c10>
50   12/08/11 5:36:38.026   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (025Zone    25                      ) <0x3c10>
50   12/08/11 5:36:38.122   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='026Zone    26                      ', Checksum=78 <0x3c10>
50   12/08/11 5:36:38.123   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (026Zone    26                      ) <0x3c10>
50   12/08/11 5:36:38.182   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='027Zone    27                      ', Checksum=7A <0x3c10>
50   12/08/11 5:36:38.183   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (027Zone    27                      ) <0x3c10>
50   12/08/11 5:36:38.245   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='028Zone    28                      ', Checksum=7C <0x3c10>
50   12/08/11 5:36:38.246   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (028Zone    28                      ) <0x3c10>
50   12/08/11 5:36:38.315   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='029Zone    29                      ', Checksum=7E <0x3c10>
50   12/08/11 5:36:38.316   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (029Zone    29                      ) <0x3c10>
50   12/08/11 5:36:38.385   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='030Zone    30                      ', Checksum=6E <0x3c10>
50   12/08/11 5:36:38.386   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (030Zone    30                      ) <0x3c10>
50   12/08/11 5:36:38.497   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='031Zone    31                      ', Checksum=70 <0x3c10>
50   12/08/11 5:36:38.498   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (031Zone    31                      ) <0x3c10>
50   12/08/11 5:36:38.779   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='032Zone    32                      ', Checksum=72 <0x3c10>
50   12/08/11 5:36:38.780   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (032Zone    32                      ) <0x3c10>
50   12/08/11 5:36:38.786   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='033Zone    33                      ', Checksum=74 <0x3c10>
50   12/08/11 5:36:38.787   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (033Zone    33                      ) <0x3c10>
50   12/08/11 5:36:38.813   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='034Zone    34                      ', Checksum=76 <0x3c10>
50   12/08/11 5:36:38.823   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (034Zone    34                      ) <0x3c10>
50   12/08/11 5:36:38.829   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='035Zone    35                      ', Checksum=78 <0x3c10>
50   12/08/11 5:36:38.852   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (035Zone    35                      ) <0x3c10>
50   12/08/11 5:36:38.859   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='036Zone    36                      ', Checksum=7A <0x3c10>
50   12/08/11 5:36:38.870   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (036Zone    36                      ) <0x3c10>
50   12/08/11 5:36:38.938   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='037Zone    37                      ', Checksum=7C <0x3c10>
50   12/08/11 5:36:38.939   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (037Zone    37                      ) <0x3c10>
50   12/08/11 5:36:38.978   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='038Zone    38                      ', Checksum=7E <0x3c10>
50   12/08/11 5:36:38.979   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (038Zone    38                      ) <0x3c10>
50   12/08/11 5:36:39.036   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='039Zone    39                      ', Checksum=80 <0x3c10>
50   12/08/11 5:36:39.037   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (039Zone    39                      ) <0x3c10>
50   12/08/11 5:36:39.106   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='040Zone    40                      ', Checksum=70 <0x3c10>
50   12/08/11 5:36:39.107   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (040Zone    40                      ) <0x3c10>
50   12/08/11 5:36:39.187   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='041Zone    41                      ', Checksum=72 <0x3c10>
50   12/08/11 5:36:39.188   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (041Zone    41                      ) <0x3c10>
50   12/08/11 5:36:39.256   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='042Zone    42                      ', Checksum=74 <0x3c10>
50   12/08/11 5:36:39.257   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (042Zone    42                      ) <0x3c10>
50   12/08/11 5:36:39.326   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='043Zone    43                      ', Checksum=76 <0x3c10>
50   12/08/11 5:36:39.327   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (043Zone    43                      ) <0x3c10>
50   12/08/11 5:36:39.396   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='044Zone    44                      ', Checksum=78 <0x3c10>
50   12/08/11 5:36:39.397   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (044Zone    44                      ) <0x3c10>
50   12/08/11 5:36:39.466   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='045Zone    45                      ', Checksum=7A <0x3c10>
50   12/08/11 5:36:39.467   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (045Zone    45                      ) <0x3c10>
50   12/08/11 5:36:39.548   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='046Zone    46                      ', Checksum=7C <0x3c10>
50   12/08/11 5:36:39.549   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (046Zone    46                      ) <0x3c10>
50   12/08/11 5:36:39.616   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='047Zone    47                      ', Checksum=7E <0x3c10>
50   12/08/11 5:36:39.617   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (047Zone    47                      ) <0x3c10>
50   12/08/11 5:36:39.686   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='048Zone    48                      ', Checksum=80 <0x3c10>
50   12/08/11 5:36:39.687   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (048Zone    48                      ) <0x3c10>
50   12/08/11 5:36:39.757   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='049Zone    49                      ', Checksum=82 <0x3c10>
50   12/08/11 5:36:39.757   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (049Zone    49                      ) <0x3c10>
50   12/08/11 5:36:39.840   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='050Zone    50                      ', Checksum=72 <0x3c10>
50   12/08/11 5:36:39.841   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (050Zone    50                      ) <0x3c10>
50   12/08/11 5:36:39.908   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='051Zone    51                      ', Checksum=74 <0x3c10>
50   12/08/11 5:36:39.909   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (051Zone    51                      ) <0x3c10>
50   12/08/11 5:36:39.977   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='052Zone    52                      ', Checksum=76 <0x3c10>
50   12/08/11 5:36:39.978   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (052Zone    52                      ) <0x3c10>
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 08, 2011, 05:39:34 am
50   12/08/11 5:36:40.047   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='053Zone    53                      ', Checksum=78 <0x3c10>
50   12/08/11 5:36:40.048   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (053Zone    53                      ) <0x3c10>
50   12/08/11 5:36:40.117   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='054Zone    54                      ', Checksum=7A <0x3c10>
50   12/08/11 5:36:40.118   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (054Zone    54                      ) <0x3c10>
50   12/08/11 5:36:40.187   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='055Zone    55                      ', Checksum=7C <0x3c10>
50   12/08/11 5:36:40.188   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (055Zone    55                      ) <0x3c10>
50   12/08/11 5:36:40.283   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='056Zone    56                      ', Checksum=7E <0x3c10>
50   12/08/11 5:36:40.284   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (056Zone    56                      ) <0x3c10>
50   12/08/11 5:36:40.337   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='057Zone    57                      ', Checksum=80 <0x3c10>
50   12/08/11 5:36:40.338   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (057Zone    57                      ) <0x3c10>
50   12/08/11 5:36:40.407   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='058Zone    58                      ', Checksum=82 <0x3c10>
50   12/08/11 5:36:40.408   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (058Zone    58                      ) <0x3c10>
50   12/08/11 5:36:40.477   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='059Zone    59                      ', Checksum=84 <0x3c10>
50   12/08/11 5:36:40.478   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (059Zone    59                      ) <0x3c10>
50   12/08/11 5:36:40.547   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='060Zone    60                      ', Checksum=74 <0x3c10>
50   12/08/11 5:36:40.548   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (060Zone    60                      ) <0x3c10>
50   12/08/11 5:36:40.629   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='061Zone    61                      ', Checksum=76 <0x3c10>
50   12/08/11 5:36:40.630   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (061Zone    61                      ) <0x3c10>
50   12/08/11 5:36:40.697   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='062Zone    62                      ', Checksum=78 <0x3c10>
50   12/08/11 5:36:40.699   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (062Zone    62                      ) <0x3c10>
50   12/08/11 5:36:40.767   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='063Zone    63                      ', Checksum=7A <0x3c10>
50   12/08/11 5:36:40.768   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (063Zone    63                      ) <0x3c10>
50   12/08/11 5:36:40.839   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='064Zone    64                      ', Checksum=7C <0x3c10>
50   12/08/11 5:36:40.841   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (064Zone    64                      ) <0x3c10>
50   12/08/11 5:36:40.907   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='065Fire Zone                       ', Checksum=59 <0x3c10>
50   12/08/11 5:36:40.908   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (065Fire Zone                       ) <0x3c10>
50   12/08/11 5:36:40.988   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='066System Has      Failed to Arm   ', Checksum=A1 <0x3c10>
50   12/08/11 5:36:40.990   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (066System Has      Failed to Arm   ) <0x3c10>
50   12/08/11 5:36:41.057   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='067Alarm Occurred  While Armed   <>', Checksum=99 <0x3c10>
50   12/08/11 5:36:41.058   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (067Alarm Occurred  While Armed   <>) <0x3c10>
50   12/08/11 5:36:41.127   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='101System                          ', Checksum=F3 <0x3c10>
50   12/08/11 5:36:41.128   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (101System                          ) <0x3c10>
50   12/08/11 5:36:41.197   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='102Partition 2                     ', Checksum=DB <0x3c10>
50   12/08/11 5:36:41.198   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (102Partition 2                     ) <0x3c10>
50   12/08/11 5:36:41.267   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='103Partition 3                     ', Checksum=DD <0x3c10>
50   12/08/11 5:36:41.268   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (103Partition 3                     ) <0x3c10>
50   12/08/11 5:36:41.389   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='104Partition 4                     ', Checksum=DF <0x3c10>
50   12/08/11 5:36:41.390   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (104Partition 4                     ) <0x3c10>
50   12/08/11 5:36:41.418   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='105Partition 5                     ', Checksum=E1 <0x3c10>
50   12/08/11 5:36:41.418   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (105Partition 5                     ) <0x3c10>
50   12/08/11 5:36:41.487   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='106Partition 6                     ', Checksum=E3 <0x3c10>
50   12/08/11 5:36:41.488   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (106Partition 6                     ) <0x3c10>
50   12/08/11 5:36:41.557   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='107Partition 7                     ', Checksum=E5 <0x3c10>
50   12/08/11 5:36:41.558   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (107Partition 7                     ) <0x3c10>
50   12/08/11 5:36:41.826   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='108Partition 8                     ', Checksum=E7 <0x3c10>
50   12/08/11 5:36:41.827   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (108Partition 8                     ) <0x3c10>
50   12/08/11 5:36:41.858   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='120Command O/P 1                   ', Checksum=8D <0x3c10>
50   12/08/11 5:36:41.859   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (120Command O/P 1                   ) <0x3c10>
50   12/08/11 5:36:41.866   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='121Command O/P 2                   ', Checksum=8F <0x3c10>
50   12/08/11 5:36:41.867   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (121Command O/P 2                   ) <0x3c10>
50   12/08/11 5:36:41.873   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='122Command O/P 3                   ', Checksum=91 <0x3c10>
50   12/08/11 5:36:41.873   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (122Command O/P 3                   ) <0x3c10>
50   12/08/11 5:36:41.923   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='123Command O/P 4                   ', Checksum=93 <0x3c10>
50   12/08/11 5:36:41.924   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (123Command O/P 4                   ) <0x3c10>
50   12/08/11 5:36:41.988   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='124Command O/P 1                   ', Checksum=91 <0x3c10>
50   12/08/11 5:36:41.989   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (124Command O/P 1                   ) <0x3c10>
50   12/08/11 5:36:42.069   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='125Command O/P 2                   ', Checksum=93 <0x3c10>
50   12/08/11 5:36:42.071   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (125Command O/P 2                   ) <0x3c10>
50   12/08/11 5:36:42.138   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='126Command O/P 3                   ', Checksum=95 <0x3c10>
50   12/08/11 5:36:42.139   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (126Command O/P 3                   ) <0x3c10>
50   12/08/11 5:36:42.208   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='127Command O/P 4                   ', Checksum=97 <0x3c10>
50   12/08/11 5:36:42.209   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (127Command O/P 4                   ) <0x3c10>
50   12/08/11 5:36:42.278   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='128Command O/P 1                   ', Checksum=95 <0x3c10>
50   12/08/11 5:36:42.279   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (128Command O/P 1                   ) <0x3c10>
50   12/08/11 5:36:42.350   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='129Command O/P 2                   ', Checksum=97 <0x3c10>
50   12/08/11 5:36:42.351   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (129Command O/P 2                   ) <0x3c10>
50   12/08/11 5:36:42.463   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='130Command O/P 3                   ', Checksum=90 <0x3c10>
50   12/08/11 5:36:42.464   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (130Command O/P 3                   ) <0x3c10>
50   12/08/11 5:36:42.512   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='131Command O/P 4                   ', Checksum=92 <0x3c10>
50   12/08/11 5:36:42.513   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (131Command O/P 4                   ) <0x3c10>
50   12/08/11 5:36:42.569   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='132Command O/P 1                   ', Checksum=90 <0x3c10>
50   12/08/11 5:36:42.570   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (132Command O/P 1                   ) <0x3c10>
50   12/08/11 5:36:42.638   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='133Command O/P 2                   ', Checksum=92 <0x3c10>
50   12/08/11 5:36:42.639   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (133Command O/P 2                   ) <0x3c10>
50   12/08/11 5:36:42.712   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='134Command O/P 3                   ', Checksum=94 <0x3c10>
50   12/08/11 5:36:42.713   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (134Command O/P 3                   ) <0x3c10>
50   12/08/11 5:36:42.790   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='135Command O/P 4                   ', Checksum=96 <0x3c10>
50   12/08/11 5:36:42.791   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (135Command O/P 4                   ) <0x3c10>
50   12/08/11 5:36:42.859   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='136Command O/P 1                   ', Checksum=94 <0x3c10>
50   12/08/11 5:36:42.860   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (136Command O/P 1                   ) <0x3c10>
50   12/08/11 5:36:42.929   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='137Command O/P 2                   ', Checksum=96 <0x3c10>
50   12/08/11 5:36:42.929   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (137Command O/P 2                   ) <0x3c10>
50   12/08/11 5:36:42.999   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='138Command O/P 3                   ', Checksum=98 <0x3c10>
50   12/08/11 5:36:43.000   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (138Command O/P 3                   ) <0x3c10>
50   12/08/11 5:36:43.069   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='139Command O/P 4                   ', Checksum=9A <0x3c10>
50   12/08/11 5:36:43.070   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (139Command O/P 4                   ) <0x3c10>
50   12/08/11 5:36:43.151   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='140Command O/P 1                   ', Checksum=8F <0x3c10>
50   12/08/11 5:36:43.152   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (140Command O/P 1                   ) <0x3c10>
50   12/08/11 5:36:43.219   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='141Command O/P 2                   ', Checksum=91 <0x3c10>
50   12/08/11 5:36:43.220   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (141Command O/P 2                   ) <0x3c10>
50   12/08/11 5:36:43.325   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='142Command O/P 3                   ', Checksum=93 <0x3c10>
50   12/08/11 5:36:43.326   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (142Command O/P 3                   ) <0x3c10>
50   12/08/11 5:36:43.359   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='143Command O/P 4                   ', Checksum=95 <0x3c10>
50   12/08/11 5:36:43.361   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (143Command O/P 4                   ) <0x3c10>
50   12/08/11 5:36:43.429   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='144Command O/P 1                   ', Checksum=93 <0x3c10>
50   12/08/11 5:36:43.430   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (144Command O/P 1                   ) <0x3c10>
50   12/08/11 5:36:43.511   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='145Command O/P 2                   ', Checksum=95 <0x3c10>
50   12/08/11 5:36:43.512   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (145Command O/P 2                   ) <0x3c10>
50   12/08/11 5:36:43.579   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='146Command O/P 3                   ', Checksum=97 <0x3c10>
50   12/08/11 5:36:43.580   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (146Command O/P 3                   ) <0x3c10>
50   12/08/11 5:36:43.650   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='147Command O/P 4                   ', Checksum=99 <0x3c10>
50   12/08/11 5:36:43.651   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (147Command O/P 4                   ) <0x3c10>
50   12/08/11 5:36:43.722   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='148Command O/P 1                   ', Checksum=97 <0x3c10>
50   12/08/11 5:36:43.723   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (148Command O/P 1                   ) <0x3c10>
50   12/08/11 5:36:43.789   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='149Command O/P 2                   ', Checksum=99 <0x3c10>
50   12/08/11 5:36:43.790   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (149Command O/P 2                   ) <0x3c10>
50   12/08/11 5:36:43.871   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='150Command O/P 3                   ', Checksum=92 <0x3c10>
50   12/08/11 5:36:43.872   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (150Command O/P 3                   ) <0x3c10>
50   12/08/11 5:36:43.940   luup_log:54: DSCAlarmPanel: debug processIncoming:: Command=570, Data='151Command O/P 4                   ', Checksum=94 <0x3c10>
50   12/08/11 5:36:43.941   luup_log:54: DSCAlarmPanel: debug Panel::Broadcast Labels (151Command O/P 4                   ) <0x3c10>
Title: Re: DSC Alarm System plugin
Post by: guessed on December 08, 2011, 05:46:45 am
Ok, the spaces are in the data stream coming from the panel itself, so you'll want to look at whatever is used to get that data in since it appears to be doing something odd.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 08, 2011, 06:11:28 am
Ok, the spaces are in the data stream coming from the panel itself, so you'll want to look at whatever is used to get that data in since it appears to be doing something odd.

The DSC panel is hooked up to an it-100 -> wisnet 110sr board and than to the network. I checked the labels on the keypad and there are no spaces where it is showing the characters. However, where the spaces show up in the labels, on the keypad, the character after the space is on the second line of the panel. So what shady brought up, the spaces occur after 14 characters.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 09, 2011, 09:39:24 am
Anyone willing to test and see if they get the same issue when having a label more than 14 characters long? If it can be reproduced, I was thinking of downloading the source and making some adjustments. Only issue is that my lua scripting experience is not that great.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: strangely on December 09, 2011, 11:27:21 am
Yeah I'll modify one of my labels tonight to match some of yours, as mine are a bit shorter.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 09, 2011, 11:30:14 am
I am looking at the dsc plugin now specificaly I_DSCAlarmPanel1.xml file. Trying to figure out where the labels are getting set and coming up with a modification of the code.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 09, 2011, 12:17:58 pm
I managed to add some code to the DSC plugin to remove the white space at the 15th character. If this is a common bug, than we can add something to the code. I added the following:

Code: [Select]
 
    --
    -- Remove white space after 14th character
    -- There seems to be a bug where after the 14th character, the label
    -- contains a white space. e.g. correct label: Foyer Entry Door
    -- broadcasted label: Foyer Entry Do or
    --
    local function removeCharacter(pos, str)
        return table.concat{str:sub(1,pos-1), str:sub(pos+2)}
    end

Added the following line in the setPanelLabel function under "if (code &gt;= 1 and code &lt;= 64) then" (line 134):

Code: [Select]
label = removeCharacter(15, label)

- Garrett
Title: Re: DSC Alarm System plugin
Post by: Kyle on December 11, 2011, 12:20:55 am
Anyone else having a problem with the plugin using IU5? I keep getting "remote arm is not enabled" And I know i have it set to "disarm" in the advanced tab. I also keep seeing "DSCAlarmPanel: Clearing..." and "DSCAlarmPanel: Keybus Fault Restored"
Title: Re: DSC Alarm System plugin
Post by: strangely on December 11, 2011, 12:31:37 am
I'm staying away from UI5 due to these types of issues for the time being. @garrettwp is running it though, so it would be good to see some feedback from him also.
Title: Re: DSC Alarm System plugin
Post by: Kyle on December 11, 2011, 12:37:17 am
I'm staying away from UI5 due to these types of issues for the time being. @garrettwp is running it though, so it would be good to see some feedback from him also.

Yeah I hear ya there man.. I even got the upgrade link from their facebook page...So its not like im using the update that was posted for the vera3...Hmm maybe i'll try and reinstall the plugin from the apps list.. Hopefully garrettwp sees this and responds with some feed back.. everything else i have seems to be working...
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 11, 2011, 12:59:00 am
I'll post real quick. I have not experienced anything out of the ordinary. But I am new to the DSC Alarm system. The only thing I experienced was the first 14 Character bug where it would add a space on the 15th character for the labels. I made a quick fix for this. Still playing around with the plugin and trying to make sure it works with my app.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: Kyle on December 11, 2011, 01:02:18 am
I'll post real quick. I have not experienced anything out of the ordinary. But I am new to the DSC Alarm system. The only thing I experienced was the first 14 Character bug where it would add a space on the 15th character for the labels. I made a quick fix for this. Still playing around with the plugin and trying to make sure it works with my app.

- Garrett

Did you do a fresh install with UI5? or was the plugin already installed on UI4?
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 11, 2011, 01:19:43 am
I've been running UI5 for some time. The plugin was a fresh install.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: Kyle on December 11, 2011, 01:20:28 am
I've been running UI5 for some time. The plugin was a fresh install.

- Garrett

I'll try and do a fresh install and see if that helps.. Thanks man!
Title: Re: DSC Alarm System plugin
Post by: Kyle on December 11, 2011, 01:58:52 am
Yeah, no such luck doing a fresh install.. Now I cant even get it to list my zones..I guess tomorrow i'll be going back to UI4..Too bad because it looks really nice..

UPDATE:

Downgraded and all is working well now.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 11, 2011, 12:59:21 pm
There is an issue with 1.5.233. I was on 1.5.201 and had no issues. Looks like something changed for the plugin support and the plugin needs to be updated.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: Kyle on December 11, 2011, 01:08:29 pm
There is an issue with 1.5.233. I was on 1.5.201 and had no issues. Looks like something changed for the plugin support and the plugin needs to be updated.

- Garrett

Well, im glad its not just me having the issue..
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 11, 2011, 03:34:15 pm
Anyone have any lua code that will arm the sensors in vera when the alarm is armed and disarm the sensors in vera when the alarm is disarmed?

- Garrett

Update:

I feel like an idiot. I did not realize that the event triggers where already there for me to create a scene and specify the devices to arm/bypass depending on the state.
Title: Re: DSC Alarm System plugin
Post by: strangely on December 12, 2011, 12:30:18 am
Interesting alternative to the IT100 perhaps:

http://forum.eyez-on.com/FORUM/viewtopic.php?f=6&t=197&sid=56050647187c8d921ce3c61d0d042e7f
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 12, 2011, 12:41:41 am
strangely,

Thanks for the link. After you mentioned this to me in a pm, I have been keeping an eye on picking one up. Nice to know that they are finally coming out with a local api for it.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: strangely on December 12, 2011, 12:50:31 am
From the notes, It looks like they are going to mirror the IT100 protocol but over TCP-IP :)

I wonder how much work the existing plugin would take to adapt? I guess its hard to tell at the current time with nothing released yet! @guessed, what do you think?
Title: Re: DSC Alarm System plugin
Post by: guessed on December 12, 2011, 01:03:58 am
If it looks and smells like and IT-100 over Ethernet then it'll work.  I can't imagine it would be hard to emulate, but they'll likely have licensing issues to sort out if they a 100% emulation.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 12, 2011, 01:04:17 am
I am still learning how the plugin works. Hopefully I can part take in helping out. Even though I do not have a board, I am thinking of emailing them to see what the api is like.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: strangely on December 12, 2011, 01:07:50 am
I have a feeling that all the boards like the IT100 and TL150 etc are actually made by this company anyway for DSC.
Title: Re: DSC Alarm System plugin
Post by: radarengineer on December 12, 2011, 10:56:38 pm
@strangely/@garrettwp, I exchanged some emails with the eyez-on sales department back in April right before I bought my TL150. At that time they only had the IP100D and I didn't want to wait around on the IP170D to get my security system installed.

However, I very clearly remember reading that they had designed the TL150 for DSC. I have been trying to find the source but I can't....

Either way, the sales department was very responsive so it is probably worth an email. It looks like a nice improvement to the TL150.
Title: Re: DSC Alarm System plugin
Post by: strangely on December 13, 2011, 12:27:04 am
@radarengineer, Yeah I think I also read this somewhere too!

I think I'd be only willing to buy one at the current price if I could use alarmrelay.com for my central monitoring needs, and if the API turns out to be *very* similar to the IT100.
I'm guessing there are going to be a lot of other people who would be in the same boat concerning monitoring, and they seem very reluctant to release information on this.
Title: Re: DSC Alarm System plugin
Post by: guessed on December 16, 2011, 10:21:24 pm
@strangely, @garrettwp,
I've created a merged version of the code from apps.mios.com, with @mcvflorin's changes for it to function under UI5, with the 0.31 tag for UI4.

This version has been tagged 0.32-UI5-merge, and it should work on both UI4 and UI5, but it needs validation before we link it as the primary release.

To accommodate UI5, it looks like the apps.mios.com rev tweaked the spacing on a few fields (due to bigger buttons?), which will need validation for UI4 impact, and also did some stuff that tweaks how it shows up in Scenes, which will need UI5 validation.

You can see these changes in the diffs on code.mios.com

Can you do whatever validation you can, then we can link?


@garrettwp, I haven't merged in your 14-char work-around, but will once we have a long-string validation/confirmation from one of the other DSC Users.
Title: Re: DSC Alarm System plugin
Post by: strangely on December 17, 2011, 12:20:09 am
I'll test out the plugin on my V2 running UI4, and the V3 running UI5 (1.5.215) tonight! I'm also off work for a couple of weeks now so I'll try and make some tests on Monday with long Zone labels to see If I can replicate the issue here.

Off topic, I'm also testing some new DirecTV software tonight that adds Pandora and few other things! :)
Title: Re: DSC Alarm System plugin
Post by: lord on December 17, 2011, 07:31:52 pm
Best regards to all forum members, I'm from chile and write right through the delivery google translation does not read write or speak English, but I think that today should not be an impediment for the smooth communication, so ask apologies if there are phrases or sentences that do not match.

 I am a central operator minitoreo alarm and seek help to operate the DLS IV, specifically how to change the language to Spanish English program, I understand that in DLS 2002 esra possible this operation Medinat a plugin.

 please who can give guidance on the matter or redirect contacted by this site.

 of at hand thanks.

 8)
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 18, 2011, 12:07:47 pm
I think there are still issues with the plugin implementation. None of my scenes are working when using any of the events for the DSC Alarm plugin.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: Kyle on December 18, 2011, 01:34:21 pm
I think there are still issues with the plugin implementation. None of my scenes are working when using any of the events for the DSC Alarm plugin.

- Garrett

Same here. Its not showing up with the rest of the devices when you try to add a trigger.
Title: Re: DSC Alarm System plugin
Post by: strangely on December 18, 2011, 02:16:29 pm
Best regards to all forum members, I'm from chile and write right through the delivery google translation does not read write or speak English, but I think that today should not be an impediment for the smooth communication, so ask apologies if there are phrases or sentences that do not match.

 I am a central operator minitoreo alarm and seek help to operate the DLS IV, specifically how to change the language to Spanish English program, I understand that in DLS 2002 esra possible this operation Medinat a plugin.

 please who can give guidance on the matter or redirect contacted by this site.

 of at hand thanks.

 8)
You might want to post this in either of these instead:
http://www.diyalarmforum.com/dsc-technical-questions/
http://www.diysecurityforum.com/index.php?PHPSESSID=c2rqlfrggu6iluq61ndqndc1k0&board=3.0
Title: Re: DSC Alarm System plugin
Post by: guessed on December 18, 2011, 06:59:34 pm
I think there are still issues with the plugin implementation. None of my scenes are working when using any of the events for the DSC Alarm plugin.

- Garrett
I assume you mean under UI5, correct?

If so, I can imagine that there are.  After going through all of the UI5 plugins, it seems to have been an almost pattern-based conversion to get them from their UI4 -> UI5 format of code.  I'd imagine there are going to be bumps as a result of that [forced incompatibility] conversion along with whatever comes from UI5 itself.

I'm still not even fully understanding the changes required, and how they all interact...  The UI4-UI5 Upgrade Wiki page gives an indication of the change, but not it's intent (etc)
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 18, 2011, 09:47:38 pm
I feel the same way. Still trying to understand the changes. Would like to try and fix the issues.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: mcvflorin on December 19, 2011, 05:10:11 am
it seems to have been an almost pattern-based conversion to get them from their UI4 -> UI5 format of code.  I'd imagine there are going to be bumps as a result of that [forced incompatibility] conversion along with whatever comes from UI5 itself.

It was a pattern-based conversion of the eventList to the new eventList2 ;D. I used the pattern-based Search&Replace from Notepad++. But I checked the result both with JSONLint and visually. Call me blind or stupid, but I just looked at the D_DSCAlarmPartition2.json file in the marketplace again and I cannot see anything that would cause the events not to work.

I'm still not even fully understanding the changes required, and how they all interact...  The UI4-UI5 Upgrade Wiki page gives an indication of the change, but not it's intent (etc)

I feel the same way. Still trying to understand the changes. Would like to try and fix the issues.

Can you tell me what's not clear so I can update that Wiki page?

Thanks.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 19, 2011, 05:19:37 am
It was a pattern-based conversion of the eventList to the new eventList2 ;D. I used the pattern-based Search&Replace from Notepad++. But I checked the result both with JSONLint and visually. Call me blind or stupid, but I just looked at the D_DSCAlarmPartition2.json file in the marketplace again and I cannot see anything that would cause the events not to work.

Than there must be an issue with how the new plugins work. They show up in the triggers section and I can set them up. But when the trigger actually takes place, the scene that contains that trigger will not get called.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: mcvflorin on December 19, 2011, 06:26:40 am
@garrettwp

Does this happens for all the plugins? I tested the DSC plugin on 1.5.215 and 1.5.232 and the notifications worked just fine.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 19, 2011, 01:14:08 pm
MCVFlorin,

It is not the notifications, it is the triggers. For example, I have a scene that is called "Alarm System Armed". I have all of my alarm sensors to go into "arm mode" when the alarm system is in an armed state.

Deivce: DSC Partition 1
What type of event is the trigger?: Armed state
Is Armed?: Device is Armed

When the panel goes into an arm mode or disarm mode, my scenes do not get run. So my Sensors do not change their arm mode, either arm or bypass.

- Garrett

p.s. one more thing, it seems that my sensors do not update to the correct state. My garage door sensor does not show that it has been triggered or it will get stuck in a triggered state when it is actually closed and fine. This is not an issue on 1.5.201.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 20, 2011, 05:20:02 am
MCVFlorin,

Aaron updated my Vera 3 to an internal beta build of 1.5.245 and it seems that the triggers are now working on this build. I will need to do more testing on the plugin. But things look promising.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: strangely on December 20, 2011, 10:52:45 pm
@garettwp / @guessed, the DLS software only allows labels of 14 characters maximum to be entered! What I did find though is that the DLS software allows entries for  "Zone Label Line1" (I only ever used less than 14) and "Zone Label Line2"

I guess this is a legacy thing and they extended it to add more characters!

So anyway, using the DLS software I created a label of more than 14 characters using Line1 and Line2, and after reprogramming and the restarting the MiOS engine, I seem to have reproduced it as per the attached! My guess the keypads remove this space, but maybe the IT100 cant!?

Based on the above, I think its safe to say that @garrettwp's modification is needed, unless there is a nicer way to do it!

Sorry this took a while to validate, but I had some other priorities.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on December 21, 2011, 12:49:58 am
Strangely,

No worries. Glad to see I am not the only one. I guess I could shorten my labels. But it can not hurt to add the extra code. I just added the code to the DSC plugin for Vera3 a few minutes ago. Everything seems to be working. I appreciate you taking the time confirming the issue.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: strangely on December 21, 2011, 03:04:12 am
OK, I've done some basic testing with the V2 on UI4 and the V3 on UI5, and it seems to be working so far OK with the new version.

I'll need to do some more testing with an empty house to be sure of everything though.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on January 02, 2012, 03:16:18 am
I noticed that the DSC plugin does not report the correct subcategory for the door zones. I looked at the I_DSCAlarmPanel1.xml file. I noticed that the device file for the door zones is set for MotionSensor1 device type. I changed this to DoorSensor1 for the device type and the xml file. It is now reporting the correct subcategory in the lu_sdata.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on January 02, 2012, 03:51:28 am
Can you make the changes you mention here, along with the confirmed 14-char changes, to trunk in code.mios.com?  I've given you access so you should be able to checkin and re-tag.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on January 02, 2012, 04:15:02 am
Gueesed,

Yes, I can add the changes. I did not want to go and just do it with out confirmation. I have not tested to see if the code.mios.com version works with UI5. I have been using MCVFlorin's files.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on January 02, 2012, 04:19:14 am
No problem.  Florin's changes have been "merged" with what's in the trunk of code.mios.com.

The bits missing, over what UI4 has, are some of the Dashboard arming controls (no TextField support in UI5, and some layout problems) and an overall validation that the DSC code works on UI5 in all other respects.
Title: Re: DSC Alarm System plugin
Post by: strangely on January 02, 2012, 12:21:16 pm
I've been running the version from code.mios.com for a week or so, and the only issues it seems to have is the garbled display of status, and also the lack of scene controls unless the advanced tab is used.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on January 02, 2012, 12:31:05 pm
I have been using MCVFlorin's version of the plugin and not code.mios. I can get my scenes to trigger based on the state of the panel. For example, I have a scene that will put all of the sensors into an arm state when the panel is "arm mode" and another scene to bypass the sensors when the panel is in "disarmed" state. It has been working fine. Not sure if the UI4 and UI5 code is causing it to conflict? Also my display for the panel does not get garbled.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: strangely on January 02, 2012, 12:37:14 pm
When I installed the plugin from the app area last week on a fresh V3 with 1.5.254, there was no status text at all, and the scene controls were also missing.

I think yours may have been working perhaps prior to the going to UI5, or installed in one of the earlier versions?

Title: Re: DSC Alarm System plugin
Post by: strangely on January 02, 2012, 12:50:56 pm
I can get my scenes to trigger based on the state of the panel. For example, I have a scene that will put all of the sensors into an arm state when the panel is "arm mode" and another scene to bypass the sensors when the panel is in "disarmed" state.

This works fine as you are using the sensors as the action to start with, and the panel state as a trigger, but try to create a scene that just arms the panel itself without using the advanced tab and you'll see the issue I'm referencing (see my picture) a few posts up.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on January 02, 2012, 01:07:07 pm
You are correct, I can not create a scene to activate a mode in the panel. I get the same circle with a line through it. As for the plugin, I have been on UI5 since August (first beta release). I have reinstalled the plugin, fresh when I got my Vera 3 and when MCVFlorin updated it to work with the changes to the plugin code.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: futzle on January 02, 2012, 03:38:15 pm
The no-entry sign in the scene editor can be banished by adding
Code: [Select]
"inScene":"1"to the top level of the static JSON file.  True, the buttons are also missing, so this only gets you so far.

To get the buttons back on the dashboard, feel free to pinch code from the static JSON file of the Caddx plugin on code.mios.com.  I implemented UI5 buttons for Arm and Stay last week.
Title: Re: DSC Alarm System plugin
Post by: strangely on January 02, 2012, 11:21:55 pm
I have reinstalled the plugin, fresh when I got my Vera 3 and when MCVFlorin updated it to work with the changes to the plugin code.
I just did an install of the plugin with a factory Fresh "Diet Vera" (Vera Light) from the app store, and the status message was there and with no corruption!

Seems I may have been a bit previous with my testing of it initially, and probably never waited until it updated status based on me arming it, as it was blank until I did this!

Title: Re: DSC Alarm System plugin
Post by: guessed on January 07, 2012, 05:30:45 pm
The no-entry sign in the scene editor can be banished by adding
Code: [Select]
"inScene":"1"to the top level of the static JSON file.  True, the buttons are also missing, so this only gets you so far.

To get the buttons back on the dashboard, feel free to pinch code from the static JSON file of the Caddx plugin on code.mios.com.  I implemented UI5 buttons for Arm and Stay last week.
@futzle,
So I'm just getting around to doing this, on the Paradox first so I can test it correctly, but I don't understand how we account for the Missing TextField that was used for PINCode (etc) in scenes.

This is needed to provide 1:1 compatibility for things like Disarm, or for Arming options where people may not have enabled "instant" mode on their Panels.

Also the screen real-estate, and layout, are greatly reduced over what we had under UI4, which is puzzling since the overall UI is much more bloated.

Can you elaborate a little, as UI5's JSON Programming seems less functional than UI4's in this respect.
Title: Re: DSC Alarm System plugin
Post by: futzle on January 08, 2012, 02:30:53 am
So I'm just getting around to doing this, on the Paradox first so I can test it correctly, but I don't understand how we account for the Missing TextField that was used for PINCode (etc) in scenes.

Advanced scenes still have access to all of the fields.  If anyone wants to make a scene in UI5 that (dis)arms the partition with a PIN, they won't be able to do it from the Scene Dashboard, but will have to go into Advanced and set the fields as in the attached screenshot.

Not ideal, but at least it should work.

Quote
Also the screen real-estate, and layout, are greatly reduced over what we had under UI4, which is puzzling since the overall UI is much more bloated.

You can set the top-level "x" and "y" keys in the static JSON to make the dashboard area bigger (default is "x": 2, "y": 2).  I've done this in the public holiday virtual switch to make room for three buttons across the width of the device, so go look there for example code.
Title: Re: DSC Alarm System plugin
Post by: guessed on January 08, 2012, 08:35:13 am
@futzle,
Thanks for the pointers, I checked in a Paradox version y/day and will do the same for the DSC today.  The Hybrid/merged UI is a little different under UI5 but it leads to the same result. 

It'll be interesting to see if people can "work it out" when it comes to using it in the UI5 Scene editor.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on January 08, 2012, 09:57:40 am
Guessed,

I still need to add the changes to the plugin. I'll wait until you update it and checkout the current version.: s there anything special with svn I need to do? Have not touched svn in a while. I have been using git for some time.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on January 08, 2012, 10:00:38 am
@strangely, @garrettwp,
I've merged more UI5 changes into the Tag 0.33-UI5, which should give you the above Dashboard UI for DSC.  This tag also includes the "Style": "numeric" changes requested by @automator.app in another thread, along with generally enabling the Device in the "Automation" (Scene) area of UI5.

As @futzle points out above, there are limitations, even when operating under UI5's Automation tab, as PINCodes cannot be entered with the WYSIAWYG UI of the Scene editor in UI5, you'll have to goto Advanced to get that.

I've tested these changes in the Paradox, but don't  have a good way to test them against a DSC, can you do some validation and let me know?  This is the version I'd like to push up to apps.mios.com.


@garrettwp,
This should be the last round of changes, would be handy to include your stuff and re-label.  Nothing special with SVN really, just the tag afterwards...  some of the free SVN Clients can't do the tag, but I can do it for you if your client cannot.

PS: I noticed the other day that code.mios.com supports git and mercurial, but you have to blow away your existing repos to reconfigure.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on January 08, 2012, 10:03:10 am
I'll see if I can use git and make the changes. I'll test out the plugin as well.

- Garrett

Title: Re: DSC Alarm System plugin
Post by: garrettwp on January 08, 2012, 10:40:41 am
I added my changes to your current release and uploaded it into vera. The plugin appears to be working, however the arming options will not work as they require a pin code. The do work if I arm it under the device options. Also it looks like the text can use some minor tweaks. I'll have to look on how to fix that.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on January 08, 2012, 11:02:51 am
The plugin appears to be working, however the arming options will not work as they require a pin code. The do work if I arm it under the device options.
UI5 removed functionality, specifically the ability to have a textfield (eg. PINCode), and the ability to have popup panes (extra real-estate).

This means that the dashboard UI, in UI5, is now calling the arming functions with an Empty PINCode when invoked from the UI5 dash.

If you have the quick arming enabled on the enabled, these should function, except DISARM which requires a PIN.  I only really left them on the Dash for Scenes...
Title: Re: DSC Alarm System plugin
Post by: garrettwp on January 08, 2012, 11:09:43 am
That is what I figured. Not sure why MCV is going backwards with this stuff. I'll try to upload my changes. I used git, so not sure how well that worked out.

- Garrett

Update: changes were committed and tagged to 0.34-UI5. Hopefully I did not botch anything up.
Title: Re: DSC Alarm System plugin
Post by: guessed on January 08, 2012, 12:22:57 pm
Yeah, not clear if it was a deliberate omission or not, at least for the TextField stuff.  The other item is documented in the UI 4-5 upgrade notes.  @futzle was the one to identify the 'stub' that exists in the code making TextFields not appear.
Title: DSC Alarm System plugin
Post by: computerjohn on January 08, 2012, 02:43:58 pm
Hello to all my friends. Sorry I've been out of the loop for a while, but have had a lot of projects and wrapping up some other issues. Now I know why I have not upgraded to UI5. I just skimmed over the posts, but need to go back and read them. A lot of info to catch up on.

I have had no issues with UI4 and the DSC plugin, but I'm still running possible an old version of the plugin, but rock solid.


Title: Accessing Serial over IP using WIZNet
Post by: maven on January 11, 2012, 03:33:17 am
I am attempting to establish a Serial over IP connection to finally integrate with a DSC 1832 alarm system. But can't get vera to talk too WIZnet yet.


I am very new to the concept of IP addresses, Subnet Masks and Ports so I suspect the is where I may be going wrong.


I have followed posts for setting up the IPSerial under thread   [code.mios.com/trac/mios_ipserial/wiki/Installation-UI4]


Only differences I have is my address is obviously different (the WIZNet has been assigned 10.0.100.3:5000 as set by static assignment in the Apple Router, and it is this address that i have entered here).


I also believe I need to program the WIZNet to match where required. I am using a Mac but have also tried unsuccessfully using a PC too with the std WIZNet software.


Using WIZNet Configurator (for Mac) I set up as follows.
I set the ADDRESS mode to static, IP address to 10.0.100.3, Port to 5000, and subnet mask to 255.255.255.0. My understanding is that this will form the address of the WIZNet device.
However there is also an area to set up Remote Host which I am assuming will relate to the vera settings. Operation Mode mixed, Connect via IP Address, Remote host IP is 100.0.100.2 with Port 5000, I have put the Gateway IP as 10.0.100.1 (that is the address of the Apple router prior to cable modem for internet)
DNS Server Address I have set to 8.8.8.8
Timeout to 0 (default, I haven't changed this) and Protocol I have tried as both UDP and TCP with no change in result.


I have spent many hours scouring the forums and internet and remain frustrated at no real progress. Nothing like a challenge but would really appreciate some guidance if possible.


Thanks



Title: Re: Accessing Serial over IP using WIZNet
Post by: garrettwp on January 11, 2012, 03:49:12 am
You should not have to use the ipserial for setting up the DSC Plugin.

Have a look here:

http://code.mios.com/trac/mios_dscalarmpanel/wiki/UI4

- Garrett
Title: Re: Accessing Serial over IP using WIZNet
Post by: maven on January 11, 2012, 04:29:38 am
Thanks Garret. I did look at that but found the following statement


If the previous DSC plug-in was installed, then it is recommended to uninstall it first, and then remove the plug-in files from the via SSH
Before attempting to install the plug-in, its recommended to connect the respective RS232 adapter, and set this up first in order to establish connectivity.


Thats what sent me on the whole RS232 goose chase to get connected with the panel. I had tried before hand but had no luck.

Kent
Title: Re: Accessing Serial over IP using WIZNet
Post by: strangely on January 11, 2012, 04:35:34 am
@maven, have a look below for an example of the WIZnet configuration. The main thing that has tripped others up has been having it set in something other than "server" mode! Make sure its server!
Title: Re: DSC Alarm System plugin
Post by: broberts on January 13, 2012, 08:03:31 pm
I've been running the plug-in for a few months now, but observe some re-ocurring issues with the alarmStartup function and a 501:
Code: [Select]
50      01/13/12 15:03:42.253   luup_log:47: DSCAlarmPanel: debug ActivePartitions: 1 <0x402>                                                                                         
50      01/13/12 15:03:42.254   luup_log:47: DSCAlarmPanel: debug Appending Child: 1 <0x402>                                                                                         
11      01/13/12 15:03:42.255   Child_Devices::AddChild id Partition-1 parent id  device type urn:schemas-micasaverde-com:device:DSCAlarmPartition:2 parent device: 47 devfile:D_DSCAl
50      01/13/12 15:03:42.257   luup_log:47: DSCAlarmPanel: debug Door Sensors: 2,3,4,5,6,7,11,12,13,19,20,21,22,23,24,25,26,27,28,29,30,31,32 <0x402>                               
50      01/13/12 15:03:42.259   luup_log:47: DSCAlarmPanel: debug Appending Child: 2 <0x402>                                                                                         
11      01/13/12 15:03:42.260   Child_Devices::AddChild id Zone-2 parent id  device type urn:schemas-micasaverde-com:device:MotionSensor:1 parent device: 47 devfile:D_MotionSensor1.x
50      01/13/12 15:03:42.261   luup_log:47: DSCAlarmPanel: debug Appending Child: 3 <0x402>                                                                                         
11      01/13/12 15:03:42.262   Child_Devices::AddChild id Zone-3 parent id  device type urn:schemas-micasaverde-com:device:MotionSensor:1 parent device: 47 devfile:D_MotionSensor1.x
50      01/13/12 15:03:42.263   luup_log:47: DSCAlarmPanel: debug Appending Child: 4 <0x402>                                                                                         
11      01/13/12 15:03:42.264   Child_Devices::AddChild id Zone-4 parent id  device type urn:schemas-micasaverde-com:device:MotionSensor:1 parent device: 47 devfile:D_MotionSensor1.x
50      01/13/12 15:03:42.266   luup_log:47: DSCAlarmPanel: debug Appending Child: 5 <0x402>                                                                                         
11      01/13/12 15:03:42.267   Child_Devices::AddChild id Zone-5 parent id  device type urn:schemas-micasaverde-com:device:MotionSensor:1 parent device: 47 devfile:D_MotionSensor1.x
50      01/13/12 15:03:42.268   luup_log:47: DSCAlarmPanel: debug Appending Child: 6 <0x402>                                                                                         
11      01/13/12 15:03:42.269   Child_Devices::AddChild id Zone-6 parent id  device type urn:schemas-micasaverde-com:device:MotionSensor:1 parent device: 47 devfile:D_MotionSensor1.x
52      01/13/12 15:03:42.284   0x35 0x30 0x31 0x39 0x36 (^[[32;1m50196^[[0m) <0x3c10>                                                                                               
50      01/13/12 15:03:42.285   luup_log:47: DSCAlarmPanel: debug processIncoming:: Command=501, Data='', Checksum=96 <0x3c10>                                                       
50      01/13/12 15:03:42.286   luup_log:47: DSCAlarmPanel: debug Panel::Command Error <0x3c10>                                                                                       
01      01/13/12 15:03:42.421   ^[[31;1mLuaInterface::CallFunction_Startup-1 device 47 function alarmStartup failed [string "..."]:597: attempt to call a string value^[[0m <0x402>   
01      01/13/12 15:03:42.422   ^[[31;1mLuImplementation::StartLua running startup code for 47 I_DSCAlarmPanel1.xml failed^[[0m <0x402>                                               

which causes a cascade startup issue for the whole Vera. 

I'm doing verbose logging (finally managed to circumvent the broken USB stick installer), so how would I dig deeper into this?
Title: Re: DSC Alarm System plugin
Post by: strangely on January 13, 2012, 08:17:19 pm
Which MiOS version are you using?
Title: Re: DSC Alarm System plugin
Post by: broberts on January 13, 2012, 11:51:04 pm
Sorry same old UI4 with firmware 1.1.1350. I'm running the D_DSCAlarmPartition2.json touched 11/8.  I have 32 i/o points on my 1832 and connected via IT-100/Wiznet at a smoking 9600 Tbps (no make that kbps).

I also just noticed a bizarre issue (unknown if it's related) -- creeping ID numbers for the DSC sensors.  The highest one was around 88, now the it's up to 105.  3 sensor today "reappeared" unassigned under devices (unclear when they "disappeared").
Title: Re: DSC Alarm System plugin
Post by: strangely on January 14, 2012, 05:26:39 am
Ok so the issue you have is a know one with UI4 (a MiOS problem) that a few of have experienced with various plugins, and you have two choices:

The latter option I don't recommend at the moment with a V2 as it can create other issues associated with low resources.

You can try UI5 and see how you get on with it, but be ready to roll back in case you run into low memory issues! Otherwise get a V3 or V light and run UI5.
Title: Re: DSC Alarm System plugin
Post by: smilligan on January 14, 2012, 02:07:34 pm
Hello,
I have recently connect an IT-100 to a DSC PowerSeries panel.
It is communicating via UDS serial server.

Host:  Vera2 with UI4 1.1.1362

I installed from apps.mios.com web site (latest version).  I did not use the UI4 directions, i presumed the apps.mios.com service would ensure latest Device files and install correctly based on host being installed to.

The initial plugin installation went OK.

I got the DevicePlugin, and one device to configure the panel.

I then set the serialIP Server device to "used by" the newly installed Plugin

However, at this point, after refresh, i did not get a listing of the 8 zones configured on the Panel.

I viewed the advanced tab for the DSC Device itself and saw the "Partitions" variable was blank.

I set that to one, and refreshed, at which point i saw a new device that appeared to be the partition control.

But still no appearance of the zones.

I was able to arm/disarm the partition via the control tab of the new partition device.   But it seems the "status" of the partition is not reflected.   

Almost like i am able to "transmit" to the IT-100, but the IT-100 is not sending data to the VERA (via IP Serial Server)

I have the green led on IT-100 flashing 1 time per .5 seconds (indicative of good comms on keybus)

I did not do any programming changes in the Alarm panel itself, as i had simply assumed that the virtual keypad (IT-100) would automatically be configured/allowed.   Is this assumption incorrect?  Do i need to configure the DSC panel to "be aware of the IT-100" and use it?

Should i install from the code.mios.com direction for UI4, or is the apps.mios.com installation acceptable given the host?

If anyone has any ideas or pointers, it would be greatly appreciated.

Thanks
Sean

I noticed in the advanced settings
Title: Re: DSC Alarm System plugin
Post by: smilligan on January 14, 2012, 04:33:14 pm
Update to previous post about DSC IT100 and UI4:

I later went back in and manually configured the Motion Sensors Zone in the Device's Advanced tab.

The device zones were created for each integer value i created, and sure enough they REFLECT the current state when doors opened or motion detected.

Not sure why it did not automatically configure...  Maybe something to do with the apps.mios.com version i downloaded?

I am able to set time/date.

And the partition device allows me to ARM and "Away" and "Stay".

However the Partition Device does not allow me to "disarm" and i get a message "invalid function"
Furthermore it does not show the current state as armed/disarmed in the partition device.

Has anybody experienced these types of symptoms before? 

Thanks
Sean



Title: Re: DSC Alarm System plugin
Post by: strangely on January 14, 2012, 07:46:14 pm
In the advanced tab you need to type disarm (all lower case) in EnableRemoteArm variable, then save again to be able to disarm remotely!
Title: Re: DSC Alarm System plugin
Post by: guessed on January 14, 2012, 09:14:38 pm
Sean,
For UI4 you need to follow the wiki instructions...including the manual file downloads from code.mios.com, and ultimate installation into Vera and the creation of a new Device from these files.

If you try getting the one from the store, there are no guarantees what you'll get, and folks likely won't be able to debug or diagnose any problems with it.

Title: Re: DSC Alarm System plugin
Post by: smilligan on January 14, 2012, 09:55:20 pm
Strangley Guessed  (sounds like a good name for a band)

Strangley = I did not find any reference to a AdvancedTab Variable "AllowRemoteAdmin" in either the DSC Panel Device, or the Partition Device.

Mr G = I will follow your advice and uninstall and follow the UI4 directions and archives from code.mios.com  (i do agree, that apps.mios.com is not all that it is stacked up to be)   Hopefully that will solve the problem that Strangley says requires "AllowRemoteAdmin"

Gentlemen:  thank you both very much for your support.

Kind Regards
Sean


Title: Re: DSC Alarm System plugin
Post by: garrettwp on January 15, 2012, 12:45:46 am
Also to note that the plugin will not automatically detect your sensors from the panel. This needs to be setup in the advanced tab of the DSC Alarm Device. You will need to tell it what zones there are and the numbers of the zones for each device type e.g. door, smoke, etc.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: smilligan on January 15, 2012, 07:20:15 am
Folks,

Based on garretwp's comments that the Zones must be set up manually leads me to believe that the Plugin might be working fine and it is just the documentation that is misleading and caused the creation of the ticket.

That being said: Does anyoneone have any confirmation on the AdvancedTab's "AllowRemoteAdmin" variable..   As i cannot find any reference to this variable. 

Nonetheless, I will follow guest's advice and reinstall from code.mios.com (NOT apps.mios.com) and see if that installs a plugin with an "AllowRemoteAdmin" variable, and update in this thread.

Thanks
Sean
Title: Re: DSC Alarm System plugin
Post by: smilligan on January 15, 2012, 08:24:30 am
Ok,

I reinstalled from code.mios.com  (this was to replace a previous installation from apps.mios.com)

It seems that code.mios installation directions resulted in the same behavior that i had with previous apps.mios.com installation.

To confirm i have installed the correct UI4 version: 
Plugin: 114
Title: DSC Alarm Panel
Version: 0.61

I have noted that on neither the Partition nor Alarm Panel device am i able to find a "AllowRemoteAdmin" configuration variable.   Should i create this as a new variable, or do i not have correct versoin?

Otherwise the plugin seems to be working fine.  (From both apps.mios.com and code.mios.com)

I suspect the issues I experienced (and communicated) were due to documentation.

Thanks for everyone's support.

Kind Regards

But there are no devices shown, yet there is a device that was created when i entered the
Title: Re: DSC Alarm System plugin
Post by: strangely on January 15, 2012, 11:59:54 am
The variable you should be looking for is actually AllowRemoteArm not AllowRemoteAdmin

http://code.mios.com/trac/mios_dscalarmpanel


Title: Re: DSC Alarm System plugin
Post by: smilligan on January 15, 2012, 12:11:17 pm
Strangley,

Thanks for the reply.

I have attached a screen shot of the Partition Device's advanced tab.
As well as the Alarm Panel Device's advanced tab.
Neither of them seem to have the variable you reference.

Is it something i might be doing wrong?  Or something relative to UI4?  Should i add the variable myself?  Or do i have the wrong code for UI4 (gotten from code.mios.com)?

Thanks
Sean

Title: Re: DSC Alarm System plugin
Post by: strangely on January 15, 2012, 12:25:50 pm
No need to add the variable yourself.

Can you perhaps try to clear your browser cache / temp files and try again to see if its there after reloading?
Title: Re: DSC Alarm System plugin
Post by: guessed on January 15, 2012, 12:43:53 pm
Sean,
Based upon your screenshots, you're still running the old code....  Either that, or you haven't deleted the old Device (and preferrably deleted the old *Dsc* files, NOTE: Case of files) and installed and created a new Device using the new code (*DSC* files, NOTE: Case of files) per the UI4 Wiki instructions.

The new Plugin NEVER stores a PIN Code (eg. "accesscode" in your screenshots)
Title: Re: DSC Alarm System plugin
Post by: smilligan on January 15, 2012, 01:19:13 pm
Guessed...
Good eye.. It did not even occur to me potential security breach with taht screen shot..  Just goes to show you where my head is.


Gentlemen: 

At any rate, here was my process (from beginning until now)

1) Installed apps.mios.com DSC Plugin on UI4
2) had some issues not discovering zones automatically as per doc, and no visibility of AllowRemoteArm variable.   Later read in thread that partition/zone info had to be entered manually.
3) As Guest suggested i redeployed again as follows:
3.a) removed the originally  installed plugin (trash can from plugin control tab).   This removed all child devices (alarm panel, partition and zones) previously created with original apps.mios.com setup
3.b) Followed the code.mios.com UI4 pluing install and setup process and created new Alarm Device, partition, and zones.

At that point the code.mios.com source/code appeared to have same characteristics as the previous apps.mios.com version.
--  devices not auto discovered
--  no visibility of AllowRemoteArm variable

Strangely went on to indicate that the AllowRemoteArm must be created manually.

Guessed:  I do not know what the latest version of code is on code.mios.com site, but after installing it reported the following;
Plugin: 114
Title: DSC Alarm Panel
Version: 0.61


Is this not the most current version?  Could it be taht code.mios.com UI4 link is not updated?

As for the AllowRemoteArm; Strangely is now indicating that this must be added manually (however doc alludes to different behavior)

I will defer to Guessed and Strangley as opposed to the documentation.

Again thanks in advance for your support.

Thanks
Sean
Title: Re: DSC Alarm System plugin
Post by: guessed on January 15, 2012, 01:51:49 pm
1) Installed apps.mios.com DSC Plugin on UI4
I think you meant marketplace.mios.com, or the MiOS Marketplace, which is for UI4.  The plugins listed in here are ANTIQUE, and there's a reason none of us really used it (we don't have access to put anything in there)

apps.mios.com is for UI5.

Quote
2) had some issues not discovering zones automatically as per doc, and no visibility of AllowRemoteArm variable.   Later read in thread that partition/zone info had to be entered manually.
Per our Wiki documentation, the parameter is called EnableRemoteArm.  When the plugin from code.mios.com runs, it automatically creates this parameter, and gives it a value of false.

The code from the MiOS Marketplace has NONE of this logic.

Quote
3) As Guest suggested i redeployed again as follows:
3.a) removed the originally  installed plugin (trash can from plugin control tab).   This removed all child devices (alarm panel, partition and zones) previously created with original apps.mios.com setup
3.b) Followed the code.mios.com UI4 pluing install and setup process and created new Alarm Device, partition, and zones.

At that point the code.mios.com source/code appeared to have same characteristics as the previous apps.mios.com version.
--  devices not auto discovered
--  no visibility of AllowRemoteArm variable

Strangely went on to indicate that the AllowRemoteArm must be created manually.
Actually the parameter is called EnableRemoteArm, per the doc.  See above.

@strangely was suggesting you fill in the value, not create the Variable, since the right codebase will automatically create the variable for you.

Quote
Guessed:  I do not know what the latest version of code is on code.mios.com site, but after installing it reported the following;
Plugin: 114
Title: DSC Alarm Panel
Version: 0.61

If you're running the right code, this information will NOT be present on your machine.  Looks like you haven't uninstalled the MiOS Marketplace version yet, and removed the underlying *Dsc* (NOTE: Case) files.  This is explained in the first line of the UI4 Install instructions:

http://code.mios.com/trac/mios_dscalarmpanel/wiki/UI4

Quote
If the previous DSC plug-in was installed, then it is recommended to uninstall it first, and then remove the plug-in files from the via SSH

Quote
As for the AllowRemoteArm; Strangely is now indicating that this must be added manually (however doc alludes to different behavior)

Actually this is what he said...

[/quote]
No need to add the variable yourself.

Can you perhaps try to clear your browser cache / temp files and try again to see if its there after reloading?




Quote
I will defer to Guessed and Strangley as opposed to the documentation.

Again thanks in advance for your support.

Thanks
Sean
The UI4 install instructions are correct.  @strangely wrote them ;)


BTW: If I had the option to, I'd completely delete the plugin from the UI4 MiOS Marketplace (marketplace.mios.com).  It's probably the greatest source of install problems than anything, since it's codebase is about 2yrs old, and doesn't reflect any of the DSC Alarm Panel functionality.

For UI4, when in doubt folks should rely solely upon the code.mios.com documentation links.  In turn, these will link to the correct [validated] source versions from source control (code.mios.com).  These documentation links get moved once new "blessed" versions are signed off by @garrettwp and @strangely.
Title: Re: DSC Alarm System plugin
Post by: strangely on January 15, 2012, 02:47:05 pm
@smilligan, please take careful note of the links that we are posting and read them carefully... You must read it step by step to understand first, and then follow the UI4 installation instructions and the download links only contained there!

PS. You may want to change your code from 1234 as that's not very burglar proof ;)
Title: Re: DSC Alarm System plugin
Post by: smilligan on January 15, 2012, 03:03:17 pm
Gentlemen;

Mr G: Thanks for the clarification on the apps.mios.com (UI5 apps) and marketplace.mios.com (UI4) sites.   I think this was the cruxt of my problem as i had downloaded the UI5 app initially, and then when i went back and followed the instructions for UI4 install, I did not follow them explicitly.  Instead I did not really delete the previous bad installation.

I was further confused by an earlier post that had alluded to the fact that one needed to enter the Zone/Partition manually, so i had assumed the documentation was not "spot on".
On another note, I am not sure how you keep people from using the apps.mios.com and marketplace.mios.com portals; as having used the UI4 link first time around might have have eliminated some of the problems I encountered initially.

At any rate, the third time was a charm.  I followed the directions step by step and sure enough the partitions were immediately discovered and all is working as documented in current posts and documentation.   I now see the variable option to EnableRemoteArm and other variable options.

Mr. Strangley:  Thank you very much for a well documented plugin.  Had i not been mislead by earlier post, and followed your doc to the letter, I would not have wasted everyone's time.   Thanks for your patience, as i know it must get frustrating dealing with dumb-a$$s like me that think they "know better than the doc"

Everything is working as you guys claim it should.

As for the code 1234:  This is a "demo" alarm panel in our show room.

Gentlemen: Again thanks for your patience and support.  I look forward to testing your Plugin and seeing if we can incorporate into our energy management systems.

Kind Regards
Sean

Title: Re: DSC Alarm System plugin
Post by: strangely on January 15, 2012, 03:25:59 pm
No worries, that's what the forum is for :)

Sadly its the multiple sources of info and download sources supported by MCV that's the problem! Now while MCV has kept the UI5 app store more up to date, sadly the same cant be said of the UI4 app store!

Glad you are up and running now anyway!
Title: Re: DSC Alarm System plugin
Post by: guessed on January 15, 2012, 03:38:51 pm
When it comes to the UI4 Marketplace, it needs a little disclaimer at the top:

    "These are not the Plugins you are looking for!"
    "How long have you had these Plugins?"
    "Let me see your documentation!"
    "Move along, move along!"

and for those still not getting the reference:
    http://www.youtube.com/watch?v=vzcWPKAv2Ow

Title: Re: DSC Alarm System plugin
Post by: broberts on January 15, 2012, 03:47:29 pm
Thanks @strangely.  Is that 501 issue related to this bug too?

More load issues on Vera2 I do not need!
   # uptime
   17:30:21 up 1 day,  2:48, load average: 13.77, 6.23, 2.57

I see you have a number of Vera flavours -- is migrating from a UI4 Vera2 to a UI5 Vera3 smooth and painless in way, shape, or form?



Ok so the issue you have is a know one with UI4 (a MiOS problem) that a few of have experienced with various plugins, and you have two choices:
  • Live with it when it happens and reload a backup to keep the device numbers the same (to preserve any scenes dependent on these as triggers etc)
  • Upgrade to UI5 where there is a fix for this issue

The latter option I don't recommend at the moment with a V2 as it can create other issues associated with low resources.

You can try UI5 and see how you get on with it, but be ready to roll back in case you run into low memory issues! Otherwise get a V3 or V light and run UI5.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on January 15, 2012, 03:52:11 pm
Thanks @strangely.  Is that 501 issue related to this bug too?

More load issues on Vera2 I do not need!
   # uptime
   17:30:21 up 1 day,  2:48, load average: 13.77, 6.23, 2.57

I see you have a number of Vera flavours -- is migrating from a UI4 Vera2 to a UI5 Vera3 smooth and painless in way, shape, or form?



Ok so the issue you have is a know one with UI4 (a MiOS problem) that a few of have experienced with various plugins, and you have two choices:
  • Live with it when it happens and reload a backup to keep the device numbers the same (to preserve any scenes dependent on these as triggers etc)
  • Upgrade to UI5 where there is a fix for this issue

The latter option I don't recommend at the moment with a V2 as it can create other issues associated with low resources.

You can try UI5 and see how you get on with it, but be ready to roll back in case you run into low memory issues! Otherwise get a V3 or V light and run UI5.

It is a matter of making a backup and loading it onto the Vera 3 or Vera 3 lite.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on January 15, 2012, 05:08:04 pm
@broberts,
To give some background on @strangely's comment, there is an issue in UI4 where events can be delivered "at the same time" into Plugin code by the LuaUPnP engine (the guts of MiOS)

These events include calls created by <startup>, <action>, <incoming>, luup.call_timer or luup.call_delay code blocks, and probably a few other things.

If any two of these occur "at the same time" then there's likelyhood of either the plugin stopping or, in the worst case, data corruption as Lua (the Plugin Programming language) isn't designed to handle this.  For the programmers out there, it's not "threadSafe".

This problem has the potential to impact a number of different plugins, but most are susceptible during Device startup.

Looking at your Log, some sort of IO event from the Panel occurred during Startup.  This then appeared to have trashed part of the Lua state for that Device, and so Startup stopped.


In UI5, changes have been made to the LuaUPnP engine, to fundamentally not allow this to occur.

NOTE: The latest versions of the DSC Alarm Plugin, the one that includes required fixes to make Scenes work under UI5, are still awaiting formal blessing by @strangely and @garrettwp before they're published on apps.mios.com (for UI5).  Until this step is done, the UI5 Version of the plugin from apps.mios.com will only be partly functional.


Thanks @strangely.  Is that 501 issue related to this bug too?

More load issues on Vera2 I do not need!
   # uptime
   17:30:21 up 1 day,  2:48, load average: 13.77, 6.23, 2.57

I see you have a number of Vera flavours -- is migrating from a UI4 Vera2 to a UI5 Vera3 smooth and painless in way, shape, or form?



Ok so the issue you have is a know one with UI4 (a MiOS problem) that a few of have experienced with various plugins, and you have two choices:
  • Live with it when it happens and reload a backup to keep the device numbers the same (to preserve any scenes dependent on these as triggers etc)
  • Upgrade to UI5 where there is a fix for this issue

The latter option I don't recommend at the moment with a V2 as it can create other issues associated with low resources.

You can try UI5 and see how you get on with it, but be ready to roll back in case you run into low memory issues! Otherwise get a V3 or V light and run UI5.
Title: Re: DSC Alarm System plugin
Post by: strangely on January 15, 2012, 05:22:38 pm

I see you have a number of Vera flavours -- is migrating from a UI4 Vera2 to a UI5 Vera3 smooth and painless in way, shape, or form?

Just answering this part since @guessed gave you about as detailed an explanation as you'll need :)

Painless? ... well I decided to Nuke everything and start again for my V3 (many old gremlins hanging around); however, most that have migrated from a V2 have been OK, save for a few where the Vera never came back up again afterwards and required another procedure to fix... more here:

http://forum.micasaverde.com/index.php/topic,8701.15.html

and here:

http://forum.micasaverde.com/index.php/topic,9027.0.html

Got to say though that I'm really happy with both the V3 and V. light! Much more stable coupled with UI5... save for a few bugs that should get addressed quite quickly!
Title: Re: DSC Alarm System plugin
Post by: broberts on January 16, 2012, 12:53:20 am
@strangely  & @guessed -- thanks guys!  I really appreciate the under the covers insight.

I'm guessing with all the events, timers, and actions I have going on, there is a high potential for corruption.

Whereas I don't use WiFi and I can do all the routing over one NIC, is VeraLite a worthy candidate for UI5, or is it really a lightweight compared to Vera3?
Title: Re: DSC Alarm System plugin
Post by: strangely on January 16, 2012, 12:57:15 am
It just has about half the memory of the V3, which is still a lot more than the V2, so it should be OK if you aren't bothered about the WiFi and the switch (not working correctly at the moment anyway with the V3).

Its a nice little unit!
Title: Re: DSC Alarm System plugin
Post by: garrettwp on January 16, 2012, 01:04:55 am
If wifi, switch (as strangely mentioned is not working at the moment) is not needed and you can deal with only one usb port (can use a powered hub) the Vera lite is a really nice unit. It is small and portable. MCV did a great job on the design. Vera 2 only has 32MB or was it 24MB of ram, where as the Vera lite is 64MB (which is plenty). My Vera 3 unit that I have running right now has 80MB free out of the 128 total. Not sure what the vera lite will be as mine is not hooked up yet. Strangely may shed some lite on the memory usage. I can also tell you that the speed is noticeable as well.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: petdocvmd on January 22, 2012, 07:16:40 pm
Hi Folks,

I have been reading through the forums here, and poring over spec sheets and manuals until my eyes have glazed over, and I think I am ready to take the plunge into the Vera / DSC pool.  My post today is an attempt to clarify and distill the facts buzzing around in my addled mind :-)

Tuesday I close on a house that is currently alarm/sensor free.  My plan is to purchase one of the various kits based on the DSC PC1832 and the Vera Lite, plus the IT-100 and RS232-USB cable.  I intend for the Vera to also control a multitude of Z-wave devices as I slowly add to my home automation empire <G>.

Some questions:

 - Many of the kits contain the RFK5500ENG keypad w/ RF receiver.  I seem to remember a subthread where this keypad needs to be in slot 8 and conflicts with the IT-100 - at least for DLS IV programming - maybe Vera integration as well..?  Is this a deal-breaker for those kits, and if so, what would be an alternate recommendation for a main keypad?  It appears that the 'naked' 1832 does not have a built-in RF receiver, correct?  So I'd need either an alternate RF keypad, or some sort of RF receiver module, right (apologies - I have not yet waded through all of 1832 literature and reference manual)?

- I am a little confused regarding UI versions.  I assume that new Veras come with UI5 installed?  There seem to be a LOT of posts throughout the MiCasaVerde forums complaining about how buggy it is.  Would I be better off downgrading immediately to UI4? If not, is the apps.mios.com "DSC Alarm Panels" Plugin the one I would use with UI5?  If so, is there a good thread detailing the downgrade procedure?

- Slightly off topic, but could someone direct me to the accessories I would need to program the 1832 via DLS IV on a PC? Could I use the same type RS232 to USB cable as for the IT-100/Vera bridge?  Anyone tried this via Windows emulation on a Mac <G>?  I come from the days of UV EPROMs and analog dialers, but prefer to program via a software interface when able ;-)

Thanks for any advice you can provide!

Scott
Title: Re: DSC Alarm System plugin
Post by: strangely on January 22, 2012, 08:01:18 pm
- Many of the kits contain the RFK5500ENG keypad w/ RF receiver.  I seem to remember a subthread where this keypad needs to be in slot 8 and conflicts with the IT-100 - at least for DLS IV programming - maybe Vera integration as well..?  Is this a deal-breaker for those kits, and if so, what would be an alternate recommendation for a main keypad?  It appears that the 'naked' 1832 does not have a built-in RF receiver, correct?  So I'd need either an alternate RF keypad, or some sort of RF receiver module, right (apologies - I have not yet waded through all of 1832 literature and reference manual)?

I would go with the following kit to start off with and add to it: http://www.homesecuritystore.com/p-548-kit32-219-dsc-power-1832-wireless-ready-security-kit.aspx
It contains the RFK5500ENG (full messages and wireless keypad) and If it does grab slot 8 then you can move it without too much problem!

- I am a little confused regarding UI versions.  I assume that new Veras come with UI5 installed?  There seem to be a LOT of posts throughout the MiCasaVerde forums complaining about how buggy it is.  Would I be better off downgrading immediately to UI4? If not,

If you buy a V3 or Vera Light then it will come with UI5; ignore the other posts about bugs as many have been fixed already; there are some bugs for the time being, but nothing huge and the new hardware plus combination of UI5 seems to be more stable than UI4! In any case with a V3 or VL, there is no option to downgrade anyway!

is the apps.mios.com "DSC Alarm Panels" Plugin the one I would use with UI5?  If so, is there a good thread detailing the downgrade procedure?

Yes that's the latest one to use for UI5 and UI4, but since the only option you have with a V3 or VL is UI5 you dont need to worry about downgrading :)

- Slightly off topic, but could someone direct me to the accessories I would need to program the 1832 via DLS IV on a PC? Could I use the same type RS232 to USB cable as for the IT-100/Vera bridge?  Anyone tried this via Windows emulation on a Mac <G>?  I come from the days of UV EPROMs and analog dialers, but prefer to program via a software interface when able ;-)
To program via DLS you'll either need to build a cable out of DB9 and floppy drive power connector, or buy one from here http://www.homesecuritystore.com/p-715-pclink-scw-dsc-computer-interface.aspx
If you want to be adventurous then I can dig out the schematics for it from a previous PM where somebody asked the same?! Recommend buying it though!
The DLS software can be found here:
http://www.diyalarmforum.com/DLS_IV/
You'll have to read here for how to get the password:
http://www.diyalarmforum.com/board/index.php?topic=96.0

Not sure about running it in a VM on a MAC, but cant see why it wouldn't work!


Title: Re: DSC Alarm System plugin
Post by: Brientim on January 22, 2012, 08:12:47 pm
There is an alternative to the IT-100.
See http://forum.micasaverde.com/index.php/topic,8781.0.html
I have had both the IT-100 (which I did use with homeseer not Vera) and the 2DS which works fine with Vera too. The 2ds give an option especially if monitoring is a remote location.
Title: Re: DSC Alarm System plugin
Post by: strangely on January 22, 2012, 08:25:44 pm
I also have both concurrently installed, but it may be better to get the 2DS board in the long run for a prospective new buyer once @Richard has finished modifying the plugin; at least it will work in the short term, albeit with some reduced functionality!
Title: Re: DSC Alarm System plugin
Post by: petdocvmd on January 23, 2012, 09:06:44 am
Strangely, thanks for the uber-fast response  :D

I would go with the following kit to start off with and add to it: http://www.homesecuritystore.com/p-548-kit32-219-dsc-power-1832-wireless-ready-security-kit.aspx
It contains the RFK5500ENG (full messages and wireless keypad) and If it does grab slot 8 then you can move it without too much problem!

Pardon my ignorance, but exactly how would I move it - is that doable via programming?

To program via DLS you'll either need to build a cable out of DB9 and floppy drive power connector, or buy one from here http://www.homesecuritystore.com/p-715-pclink-scw-dsc-computer-interface.aspx
If you want to be adventurous then I can dig out the schematics for it from a previous PM where somebody asked the same?! Recommend buying it though!

I'd love to see the schematic - I used to develop and market embedded devices for flight simulation software interfaces, and enjoy getting my hands dirty with this kind of stuff  ;D !

Thanks again for the guidance!

Scott
Title: Re: DSC Alarm System plugin
Post by: Brientim on January 23, 2012, 01:39:53 pm
There are 8 slots on the DSC and you allocate the keypad to a slot. This is done by programming at the keypads. It is is very simple.
Title: Re: DSC Alarm System plugin
Post by: strangely on January 23, 2012, 02:02:32 pm
Moving a keypad to a different slot is as simple as entering:

*8 [Installer's Code] 000 0 1 1 ## This will move it to slot 1, if you want to move it to something else then the bolded 1 can be changed to anything from 1-8

For more on general programming without the DLS software you can read here:

http://www.diyalarmforum.com/board/index.php?topic=3656.0
The full programming manual can be found here:
http://www.diyalarmforum.com/Downloads/DSC/install-manuals/pc1864-prog.pdf (again from my previous post you'll need to create and account there and read the download instructions for the password required)

Schematic for RS232 attached, but to summarize:

DB9 Pin 2 goes to PClink Pin 4
DB9 Pin 3 goes to PClink Pin 1
DB9 Pin 5 goes to PClink Pins 2 and 3
DB9 Pin 4 and 6 Jumper
 


Title: Re: DSC Alarm System plugin
Post by: petdocvmd on January 23, 2012, 03:52:02 pm
Perfect - thanks so much for the help.  Looking forward to getting started :-)

Regards,

Scott
Title: Re: DSC Alarm System plugin
Post by: guessed on January 27, 2012, 09:53:53 pm
Call for Wiki/Documentation volunteers!

Over it's development, we've had a lot of great discussions on this thread, about both the configuration of the Plugin, as well as general advise/guidance/howTo type information on the DSC Panels themselves.

So far, most of the documentation has been authored by @strangely, and I'm sure he'll continue to do that, but now that we have a large number of users I wonder if others would also like to contribute to the Wiki doc over at:

    http://code.mios.com/trac/mios_dscalarmpanel

I think everything that we can do there to aid the newer users, particularly with the Vera3/Vera3 Lite models coming out, will greatly lower the bar to adoption of this Panel unit, which only further motivates it's development.

If you're up to help out, and provide some guidance/doc in any capacity, please post a response, and we'll arrange to get you an account and access to perform the necessary edits....


Thanks in advance!
Title: Re: DSC Alarm System plugin
Post by: guessed on January 28, 2012, 07:42:04 pm
Heads up on coming change...
In the next few weeks we will be releasing a patch to the DSC Alarm Plugin that will fix a problem I introduced a long time ago relating to the DoorZones configuration parameter.

If you don't have anything specified in the DoorZones parameter, and instead have specified your Alarm Zones solely in terms of the MotionZones and SmokeZones parameters, you can safely ignore the rest of this note.

Details...
The change will correctly create all Alarm Zones, listed in the DoorZones parameter, as being of type:
    "urn:schemas-micasaverde-com:device:DoorSensor:1"

instead of how they're currently created:
    "urn:schemas-micasaverde-com:device:MotionSensor:1"

As a result, all devices currently listed as DoorZones will be completely recreated, and will get new MiOS Device Id's.  If you've scripted against the old Device Id's then these scripts will no longer work.

Once we push this change to apps.mios.com (UI5) all UI5 users will automatically pickup the change, we have no control over this as that's the way the current catalog works.  I don't believe users are notified of this change either...

So we're giving a heads up to users so they can be aware of the rollout and, take actions in advance that should avoid any issues.

If you don't have ANY scenes defined against the

Work-around, pre-patch deployment (to be validated)
If you currently have a setup with the following initialization parameters:
    doorZones=1,2
    motionZones=3,4,5


then you can change this configuration, prior to the patch being consumed, to something like:

    doorZones=
    motionZones=1,2,3,4,5


ie. Prefix them onto the motionZones parameter (the front, ordering is important)

then this should cause no disruption in DeviceId's. 

Of course, if you don't have any scripts against the Door-based Alarm Panel devices parameter, or SQRemote associations (the UI controls will lose the underlying MiOS device) then you can just apply the patch and move on.
Title: Re: DSC Alarm System plugin
Post by: strangely on January 31, 2012, 03:43:56 am

Work-around, pre-patch deployment (to be validated)


Work-Around is confirmed as working!
Title: Re: DSC Alarm System plugin
Post by: garrettwp on February 02, 2012, 03:35:55 am
Call for Wiki/Documentation volunteers!

Over it's development, we've had a lot of great discussions on this thread, about both the configuration of the Plugin, as well as general advise/guidance/howTo type information on the DSC Panels themselves.

So far, most of the documentation has been authored by @strangely, and I'm sure he'll continue to do that, but now that we have a large number of users I wonder if others would also like to contribute to the Wiki doc over at:

    http://code.mios.com/trac/mios_dscalarmpanel

I think everything that we can do there to aid the newer users, particularly with the Vera3/Vera3 Lite models coming out, will greatly lower the bar to adoption of this Panel unit, which only further motivates it's development.

If you're up to help out, and provide some guidance/doc in any capacity, please post a response, and we'll arrange to get you an account and access to perform the necessary edits....


Thanks in advance!

Guessed,

I would be glad to provide my services to update and add to the wiki/documentation.

Quote from: trangely
Work-Around is confirmed as working!

Glad to know the work-around works. Would hate to have the updated code break the user's setup.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: smilligan on February 02, 2012, 05:04:31 pm
Hello,

I as wondering if there were any plans to support the "LastTripped" property for sensors.

I am referring to the LastTripped property as seen in the standard zWave Motion and Door sensor devices.

The hope is that the DSC alarm panel sensor would have similar behavior to the existing sensors as described above.

Thanks
Sean
Title: Re: DSC Alarm System plugin
Post by: guessed on February 03, 2012, 01:44:46 am
I would be glad to provide my services to update and add to the wiki/documentation.
You already have access, I granted you and @strangely Admin sometime back ;)

Let me know if you need topic ideas.  I think you lads are closer to this than I am, given you have units in your houses, but I keep a list in my head based upon what I've seen people ask here in this thread.
Title: Re: DSC Alarm System plugin
Post by: guessed on February 03, 2012, 02:01:19 am
I as wondering if there were any plans to support the "LastTripped" property for sensors.

I am referring to the LastTripped property as seen in the standard zWave Motion and Door sensor devices.

The hope is that the DSC alarm panel sensor would have similar behavior to the existing sensors as described above.
Sean,
I made a change to add the LastTrip (note spelling) variable, with behavior consistent with that of the Ping Sensor (it's set on 0 -> 1, and 1 -> 1 transitions of Tripped, but not on 1 -> 0 or 0 -> 0 transitions).

This change is in I_DSCAlarmPanel1.xml version 40 (in trunk).  If you're running the tag 0.34-UI5, you can overlay directly, but the "apps.mios.com" version isn't running that base just yet (as we have a compat issue to sort out for DoorZones parameter, per the above)
Title: Re: DSC Alarm System plugin
Post by: smilligan on February 03, 2012, 11:04:50 am
Guessed,
Thanks for the update.

I assume the reason for not updating "LastTrip" on 1>0 transition, is because the DSC Motion sensors is because they untrip within seconds of tripping.
However, i am hopeful you can explain why not setting LastTrip on 1>0 for door sensors, as a door can remained tripped for an unknown period of time.

Thanks
Sean
Title: Re: DSC Alarm System plugin
Post by: guessed on February 03, 2012, 11:37:19 am
It's more about the semantics of the LastTrip variable being [largely] undefined by MCV.  It's not even in the associated S_xxxx.xml file, and there's no documentation on it's semantic behaviour.  This is part of the discussion I had under the Ping Sensor as well, when I implemented it there.

Given this, it's more conservative to simply treat it as a "Tripped" edge indicator timestamp, and not an "UnTripped" indicator.  Once the Semantic is defined,the various devices can be aligned to it.

Guessed,
Thanks for the update.

I assume the reason for not updating "LastTrip" on 1>0 transition, is because the DSC Motion sensors is because they untrip within seconds of tripping.
However, i am hopeful you can explain why not setting LastTrip on 1>0 for door sensors, as a door can remained tripped for an unknown period of time.

Thanks
Sean
Title: Re: DSC Alarm System plugin
Post by: smilligan on February 03, 2012, 11:52:07 am
Mr. G.
Thanks for the insight on "undefined semantic" relative to "LastTrip" property.
We have predicated a great deal of our Energy Management code on this property for both zWave motion and door sensors.
I will communicate this risk to our software engineer to make sure we do not "back ourselves into a corner" with the property.
Kind Regards
Sean
Title: Re: DSC Alarm System plugin
Post by: oTi@ on February 04, 2012, 12:09:06 am
[...] semantics of the LastTrip variable being [largely] undefined by MCV.
[...]This is part of the discussion I had under the Ping Sensor as well, when I implemented it there.
History: Ping Sensor (http://forum.micasaverde.com/index.php/topic,1997.msg46141.html#msg46141) and bug# 1541 (http://bugs.micasaverde.com/view.php?id=1541).

Now, is it me, or does LastTrip get updated on both edges (these days, for a motion sensor)?

Hallway sensor on a 2 minute 'on time':
Code: [Select]
06 02/04/12 0:16:32.397 Device_Variable::m_szValue_set device: 39 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 1 #hooks: 2 upnp: 0 v:0xe293d0/NONE duplicate:0 <0x2b5d3680>
06 02/04/12 0:16:32.471 Device_Variable::m_szValue_set device: 39 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: LastTrip was: 1328332449 now: 1328332592 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b5d3680>
06 02/04/12 0:18:27.507 Device_Variable::m_szValue_set device: 39 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 1 now: 0 #hooks: 2 upnp: 0 v:0xe293d0/NONE duplicate:0 <0x2b5d3680>
06 02/04/12 0:18:27.605 Device_Variable::m_szValue_set device: 39 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: LastTrip was: 1328332592 now: 1328332707 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b5d3680>

Title: Re: DSC Alarm System plugin
Post by: guessed on February 04, 2012, 12:27:38 am
@oTi,
That's the problem with having observed-behavior (implementation variant) vs defined-behavior (spec, invariant). 

I will not change the implementations from that outlined for Ping (and now DSC) until there is a spec-based behavior defined and, preferably, the LastTrip variable is documented in the S_xxxx.xml file.
Title: Re: DSC Alarm System plugin
Post by: oTi@ on February 04, 2012, 12:47:52 am
That's the problem with having observed-behavior (implementation variant) vs defined-behavior (spec, invariant). 
Precisely.

Quote
I will not change the implementations from that outlined for Ping (and now DSC) until there is a spec-based behavior defined [...]
Right. Personally, I don't find the currently observed behavior (for a Z-Wave motion sensor) very intuitive.
Title: Re: DSC Alarm System plugin
Post by: guessed on February 04, 2012, 12:56:07 am
That's what HaDevice1 LastUpdated is for...  (also, largely undocumented)
Title: Re: DSC Alarm System plugin
Post by: smilligan on February 09, 2012, 09:15:52 am
Mr G...

In an ideal world, everything would be defined (invariant as you say) prior to initiating a development effort.

However you know it is impossible to define all possible use-cases (thus methods/properties) in advance.   There is just too much that is unknown.
So this is why we all rely on good programmers to make decisions on "observed" patterns and then, in turn, implement these as documented standards.

The question really should be:   "how does vera support a collaborative wiki that serves as a gathering point for all the undocumented standards/specs that will, in turn, allow programmers such as yourself to document variant patterns thus making them invariant (standard)?

Regardless:  We all must trudge on and make fundamental assumptions based on perceived patterns..   I do agree that they always come back to "bite you", but we cannot sink waiting for defined specifications for a product/market that is still evolving.

I read the above in a fortune cookie last night while eating at a local sushi restaurant.
Sean
Title: Re: DSC Alarm System plugin
Post by: guessed on February 09, 2012, 10:50:19 am
Maybe, but after 3yrs of product releases, 4 hardware platforms, you'd think that some basic functional documentation would be present for common behaviors.

And yes, I've implemented a reasonable behavior for LastTrip, based upon its name and observed behavior.... A choice that actually makes the most sense (in absence of a clear spec) so I'm well not used to waiting for perfection.  8)
Title: Re: DSC Alarm System plugin
Post by: guessed on February 19, 2012, 01:20:22 pm
Posted version 0.35 of the Plugin at:
    http://code.mios.com/trac/mios_dscalarmpanel/browser/tags/0.35

It has NOT, as yet, been made the documented release, and has NOT been published to apps.mios.com... just yet. 

This version supports both UI4 and UI5.  This version includes support for the HaDevice1::ToggleState action on the Zones.  Clicking on the "Running man" in the UI will toggle the Armed/Bypass state of the Zone (local MiOS State only, since this isn't tied to the Bypass mode in the DSC Alarm unit).  This is per a recent finding of @futzle, and in prep for some upcoming changes in UI5.

As usual, use at your own risk ;)
Title: Re: DSC Alarm System plugin
Post by: guessed on February 19, 2012, 01:25:32 pm
WARNING - UI5 App upgrade imminent
The DSC Plugin, on [UI5] apps.mios.com, will be upgraded tonight to include a number of fixes. 

Please visit the warning page, posted a few weeks back, to ensure you make the necessary prep-changes:

     http://forum.micasaverde.com/index.php/topic,5154.msg61209.html#msg61209

The plugin will be pushed to [UI5] apps.mios.com tonight, and then we wait approval before it'll be unconditionally rolled to all UI5 users.
Title: Re: DSC Alarm System plugin
Post by: strangely on February 19, 2012, 02:26:48 pm
Thanks @guessed, I'm back home for a couple of weeks, and will have some spare time to update the wiki with the warning, and also some troubleshooting tips within the next couple of days.
Title: Re: DSC Alarm System plugin
Post by: JonLove on February 27, 2012, 10:42:19 am
Hi,

Has these been updated in the MIOS Apps list yet?

How does one actually go about updating their plugin (either manually or through the apps list)?

Thanks,

Jon
Title: Re: DSC Alarm System plugin
Post by: guessed on February 28, 2012, 11:56:47 am
Posted version 0.35 of the Plugin from this tag:
    http://code.mios.com/trac/mios_dscalarmpanel/browser/tags/0.35

This version supports both UI4 and UI5.  This version includes support for the HaDevice1::ToggleState action on the Zones.  Clicking on the "Running man" in the UI will toggle the Armed/Bypass state of the Zone (local MiOS State only, since this isn't tied to the Bypass mode in the DSC Alarm unit)

This release also contains the changes required to correctly configure Door Sensors as the right device type (thanks to @garrettwp!!).  Please note the warnings posted here:
    28th Jan - http://forum.micasaverde.com/index.php/topic,5154.msg61209.html#msg61209
    19th Feb - http://forum.micasaverde.com/index.php/topic,5154.msg63651.html#msg63651

Many thanks to @strangely also, as he's updated the documentation for this plugin over at:
    http://code.mios.com/trac/mios_dscalarmpanel


The changes have been submitted to the UI5/apps.mios.com catalog for approval.


As usual, use at your own risk ;)
Title: Re: DSC Alarm System plugin
Post by: JonLove on February 28, 2012, 01:28:44 pm
Just to ask again - how does one update? Either through the app store or manually...
Title: Re: DSC Alarm System plugin
Post by: guessed on February 28, 2012, 01:59:15 pm
Per the first of the two links posted above:

Quote
Once we push this change to apps.mios.com (UI5) all UI5 users will automatically pickup the change, we have no control over this as that's the way the current catalog works.  I don't believe users are notified of this change either...
Title: Re: DSC Alarm System plugin
Post by: JonLove on February 28, 2012, 05:06:18 pm
Thanks for the info. Slightly frustrating process to get the DSC update but hey =)
Title: Re: DSC Alarm System plugin
Post by: garrettwp on February 28, 2012, 09:34:48 pm
If you want the most upto date of the plugin, you'll have to download the files from the link provided by guessed and install manually. Once the plugin is deemed stable, it is pushed to the app section.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: JonLove on February 29, 2012, 09:13:04 am
Gotcha. And how exactly does one do the manual install? =)
Title: Re: DSC Alarm System plugin
Post by: guessed on February 29, 2012, 09:37:41 am
If you're on UI5 (which I'm assuming you are) then it should automatically install/upgrade, if you first installed it from apps.mios.com.  The upgrade release was approved by the MCV Team yesterday.

If you manually installed it the first time around, then you'll need to repeat that process since apps.mios.com won't know you  have it.

UI4 users have to manually install.  Instructions are in the HowTo pages on the wiki:
    http://code.mios.com/trac/mios_dscalarmpanel
Title: Re: DSC Alarm System plugin
Post by: JonLove on February 29, 2012, 09:47:15 am
Thanks guessed!
Title: Re: DSC Alarm System plugin
Post by: Brientim on March 02, 2012, 06:25:25 pm
@guessed, Has this been merged with the branch to included the 2DS or are they still independent?
Title: Re: DSC Alarm System plugin
Post by: guessed on March 02, 2012, 06:28:35 pm
They're independent at the moment.
Title: Re: DSC Alarm System plugin
Post by: Brientim on March 02, 2012, 06:32:45 pm
Thanks for the very quick reply.
Title: Re: DSC Alarm System plugin
Post by: Brientim on March 02, 2012, 06:37:56 pm
@Guessed, I forgot say, if you still need I can assist with the Wiki updates.
Title: Re: DSC Alarm System plugin
Post by: rodrigotejas on March 08, 2012, 02:42:42 pm
According to the Eyes-On forum, firmware 1.06.57 has been officially released and includes the TPI. The annoucement is attached below. Now, for a novice like myself, when will the DSC plugin with 2DS support be released? I haven't figure out how to correctly install the beta version by myself...

Thanks!


snip...

"I am proud to announce the long awaited release of the 1.06 firmware with the Envisalink Third-Party Interface (TPI). The TPI is an API based on the PC5401/IT-100 protocol and will allow developers to create plugins and interface directly with their DSC security panel over an IP interface.

This is the first product in the security industry to allow for such a collaborative framework over TCP/IP.

In addition to the TPI this release offers the following fixes and improvements:

- Local interface "hover" over zones would end at 17 hours. Fixed
- Zone timers were running about 20% fast. Fixed
- Expanded exception reporting

...snip
Title: Re: DSC Alarm System plugin
Post by: strangely on March 08, 2012, 04:24:22 pm
If you have a 2DS then you can try a beta version of the plugin as linked from the bottom of the below page, which also contains instructions about how to install the plugin:

http://code.mios.com/trac/mios_dscalarmpanel/wiki/UI5 (I'm assuming you may have UI5?)

@Guessed is just making some other changes to the plugin, and it will be pushed out to code.mios.com and the main wiki link within a couple of weeks.
Title: Re: DSC Alarm System plugin
Post by: rodrigotejas on March 08, 2012, 04:47:57 pm
Thanks Strangely. I've tried to follow the instructions, but I guess I'm too far removed from the process to really understand how to apply a private. I ended up bricking my Vera Lite (UI5) and had to have tech support recover it.  :o

Title: Re: DSC Alarm System plugin
Post by: strangely on March 12, 2012, 01:04:24 pm
@rodrigotejas, did you get up and running again?
Title: Re: DSC Alarm System plugin
Post by: strangely on March 12, 2012, 01:10:59 pm
***Volunteer request***

I've sent a couple of PMs to people that I know have hard wired smoke connected to PGM's (@timholmesjr and @jmmorgan), but if there is anyone else here using the plugin (with hard wired smokes connected to PGM's), then we could do with a LuaUPnP log taken when the smoke is activated if possible?

@guessed is adding some missing features, and this is needed to help support wired smokes! If you are willing to volunteer then we'll post further instructions.

Thanks
Title: Re: DSC Alarm System plugin
Post by: dali on March 13, 2012, 03:12:34 am
First post from a Vera & 2DS newbie, so please bear with me...

Is it possible (or planned) to use PGM outputs in the plugin?
I'm using a PGM to open/close my garage door, and very often I forget to close the door. Since i have a door sensor on the garage door, it would be nice to have a scene that checks if the garage door has been open for X minutes and the cycles the PGM output.

I'm a total newbie, so I don't know if it's possible to make this work.
Title: Re: DSC Alarm System plugin
Post by: jmmorgan on March 13, 2012, 08:39:04 am
@Strangley:
I received your PM, but it would not let me replay to you.  I would like to help with the 2 wire smoke detectors, but my unit is currently being installed in a new construction and I do not have access to the unit for a while.  The good new is that I will be doing a new install of the DSC so I will log the events when I get a chance, if you have not fixed it by then. Thanks
jmmorgan
Title: Re: DSC Alarm System plugin
Post by: guessed on March 13, 2012, 09:21:41 am
@dali,
Not at this time (planned or implemented).  The focus right now is getting the 2DS and hard wired smokes (Aux + PGM2) functional.
Title: Re: DSC Alarm System plugin
Post by: dali on March 13, 2012, 11:36:06 am
@guessed: That's too bad, for me atleast. But I understand that you want to focus on getting the other stuff done first.
I work as a software developer (but have never user lua), so I'd be glad to assist in any way I can if support will be added for PGM outputs.
Title: Re: DSC Alarm System plugin
Post by: guessed on March 13, 2012, 12:15:50 pm
@dali,
It comes down to priorities across the set of Plugins that I work on, as well as dealing with the extra complexity introduced by UI5 and providing backward compatibility. 

It's not that it won't ever get done, it's that there's not been a strong driver to implement it relative to other items.  Technically PGM's should be standardized, since all Alarm systems have them in one form or another, so the hard part will be working out what that standardization looks like so that it can be exposed up through the Control Points.

The code is easy to tweak if you want to experiment with it.   It's not a huge leap to write Lua if you've programmed/scripted before.
Title: Re: DSC Alarm System plugin
Post by: strangely on March 13, 2012, 11:45:35 pm
@Strangley:
I received your PM, but it would not let me replay to you.  I would like to help with the 2 wire smoke detectors, but my unit is currently being installed in a new construction and I do not have access to the unit for a while.  The good new is that I will be doing a new install of the DSC so I will log the events when I get a chance, if you have not fixed it by then. Thanks
jmmorgan
No worries, hopefully it'll be working for you by then :)
Title: Re: DSC Alarm System plugin
Post by: rodrigotejas on March 19, 2012, 09:33:45 am
@strangely:

Yes, my Vera Lite is restored. It was strange... I could ping the device, but could not access the UI locally or remotely. Not sure what tech support did to recover it, but once restored I had lost all of my automation, but all devices were still present. I restored from backup and all was back to normal (sort of). Since being restored my Leviton 4-button scene controllers have gone flakey (some buttons work, some don't). I've deleted and re-added them and still have the problem. Different topic though...

Can't wait for the officially released DSC app with 2DS support!

Thanks!
Title: Re: DSC Alarm System plugin
Post by: automag928 on March 28, 2012, 09:51:50 am
Hey everyone - I'm currently looking at replacing my existing Brinks system.  From what I've read so far on the forums, the DSC 1832 with a IT100, or the 2DS would allow me to hook up to Vera and use the existing hardwired sensors from  my brinks system as sensors w/ the DSC & show up in Vera as well.  Is this correct?

One thing I've noticed, I cant seem to find the IT100 anywhere.  Due to mounting locations I'm going to have to use wireless to connect the DSC to the VERA...is the IT100 with the WiFI to RS-232 the best way at this point to accomplish what I am trying to do? or is the 2DS with a wireless bridge?

Sorry for the basic questions but I just want to ensure I am going down the right path before pulling the trigger on purchases... Thanks!
Title: Re: DSC Alarm System plugin
Post by: guessed on March 28, 2012, 10:19:28 am
For the IT100, these are available from the link
    http://www.homesecuritystore.com/p-1425-it-100-dsc-power-series-integration-module.aspx

But other places also. The link above is the same site that @strangely linked in the references section, there are other places out there that may be cheaper (in addition to eBay).  My test system is from this mob.

DSC use standard mag-reed switch contacts, then apply resistors at the panel.  Some reed switches may have built in resistors, but weve not heard anyone with problems so far.

Some people use/extend the existing 4-wire Keypad wiring to the IT100 or 2DS, so that it can be closer to Vera without extended wiring.

When I built against the IT100 I was using a barebones Wifi-RS232 bridge.  A real system would need to power that during a power outage to ensure you continue to get communications with it (along with all your networking gear)

The 2DS would need an Ethernet-wifi bridge.

Both options will be as stable as the weakest link in the equation.  There are some bugs in MiOS and the 2DS that were actively working, both dev teams are being extremely useful in resolving these, but they impact Network attached versions of the DSC interface.

The kit version linked can also do wireless sensors (Check the keypad).  Some folks also recommend using the 1864 board so you can expand to more nodes.
Title: Re: DSC Alarm System plugin
Post by: automag928 on March 28, 2012, 11:51:48 am
For the IT100, these are available from the link
    http://www.homesecuritystore.com/p-1425-it-100-dsc-power-series-integration-module.aspx


 Ah - perfect! Thanks for the link.  When I went to the "good base kit" link of the Wiki I looked under accessories and didnt see it, and thought I tried searching for just it-100, but thats what i needed.

DSC use standard mag-reed switch contacts, then apply resistors at the panel.  Some reed switches may have built in resistors, but weve not heard anyone with problems so far.

To make sure I'm understanding, this means the existing hard-wired door/window contacts from Brinks system should work, but not guaranteed?


When I built against the IT100 I was using a barebones Wifi-RS232 bridge.  A real system would need to power that during a power outage to ensure you continue to get communications with it (along with all your networking gear)

Will the battery backup in the alarm panel power the IT-100 and the RS-232 to Wifi adapter?  The rest of the system (routers/Vera/etc) is all on battery backups, so not too concerned with those.  Even if the Vera & routers lost power, the alarm system should still be able to communicate with a alarm monitoring company independent of me being able to utilize/access it via Vera, right?

The 2DS would need an Ethernet-wifi bridge.
Any reason to pick the IT-100 over the 2DS or vice versa?


Thank you so much for the info - the wife really wants me to pull the trigger on an alarm since we cancelled brinks (that's a whole other headache), and being new to the vera environment i want to make sure I am looking at the right things!
Title: Re: DSC Alarm System plugin
Post by: garrettwp on March 28, 2012, 12:06:18 pm
Getting the 2ds will be cheaper as the it200 well cost you the same and you will need a serial to USB adapter or a serial to ethernet adapter. But the 2ds has some connectivity issues that are being worked on. The battery backup will power the it200, but you'll need a separate power for the serial to ethernet adapter or wifi adapter.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on March 28, 2012, 12:26:26 pm
@garrettwp,
Based upon the pricing I've seen for the IT100, it'd be a wash [price-wise] even after you've added a WIZnet (or similar) to get it onto the Network.

IT100 ~ $50-$69 + WIZnet $30
2DS ~$99

IMHO, the 2DS wins out because it has
For increased WAF, get the Alphanumeric keypad.  You'd get one of those if you follow the package link that @strangely put into the front page of the Wiki.
Title: Re: DSC Alarm System plugin
Post by: strangely on March 28, 2012, 12:27:10 pm
There was somebody here that used an iTach serial to WiFi adapter and powered it either from the keybus or PGM output successively.

I would recommend the 2DS anyway also, and it seems with the Beta software for it that we have, the issues seems to be resolved. If you need WiFi, the n you also use an Ethernet to WiFi bridge...  but you'd want to find a 12V one!

For the reed contacts, the only issue you will have is making sure that you either program the panel to ignore end of line resistors (EOLRs) , or you match what may be there already to be 5700 ohms (I think that is whats used of the top of my head). Bottom line its possible to use the old ones you have.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on March 28, 2012, 12:48:03 pm
I forgot what I paid for my IT100, thought is was close to 100.  Now you guys are going to make me spend some more money and pick up the 2ds.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on March 28, 2012, 12:52:38 pm
LOL...  If you have a working one, there's really no need to change.  It's certainly the road-more-tested at this time.

If folks are Serial attaching the device directly to Vera, they'd benefit from the simplicity of the IT100 (less moving parts == increased reliability).  Both are still very valid options, and not everyone wires their Networking closet for BBackup.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on March 28, 2012, 02:52:39 pm
Well it looks like I need to order a new power supply for the alarm panel. I was cleaning up the wires in the media closet of my home theater room and I accidentally knocked the power supply and it hit the floor. Plugged it back in and the led light would not turn on. Tried a few times and it finally kicked back in, but would not power the panel. I am not comfortable plugging this thing in. So the question is, do I order a board? Would hate to order just a power supply and have to pay shipping that would cost close to the power supply lol. Need to make it worth the trip!  The dilemma....

- Garrett

Update:
Took the plunge and picked up an 2DS as it will keep the installation simpler and save an outlet as this will be powered by the panel and I will not have to power the serial to ethernet adapter. Still kicking myself for breaking the power supply!
Title: Re: DSC Alarm System plugin
Post by: strangely on March 29, 2012, 02:23:47 am
Took the plunge and picked up an 2DS
Welcome to the Dual interface club :)

I currently have triple redundancy for alerts on mine as I have the 2DS running on a V.Lite and the IT100 running on my V3, as well as the Envisalerts + Envisacor monitoring.

All very good until my network failed like it did the other night :)
Title: Re: DSC Alarm System plugin
Post by: garrettwp on March 29, 2012, 02:27:38 am
So you have both the it-100 and the 2ds working together? Looks like you'll have to add some redundancy to the network. I have all of my switches, routers, and servers on UPS's as well as the modem. So if power goes out, I still have internet connection. That is unless the ISP takes a crap. One concern I have is if I have the 2ds being monitored, what happens if the internet cuts out? Do I get a call? What are there procedures? I have to go on their site to see if they have all of these questions answered.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: strangely on March 29, 2012, 02:57:13 am
Yep they are all working in parallel, mainly cos I don't trust the 2DS yet and I have a spare V.Lite not doing anything useful apart form looking pretty :)

You get a network supervision alert sent to you very quickly when it occurs and when it clears, however as far as the monitoring goes, I've not had them call me yet when this occurs. The alerts and the monitoring are different entities anyway, but I assume even the monitoring company can act upon it also if set up that way!

When I had mine set up with monitoring the other week, I filled something in on their portal under my account settings and it just became active a couple of days later, and apart from a brief email stating it was active, and seeing that it is from the 2DS's status page, I've not had any contact with anyone wanting to test anything, or customize anything :(

Originally when I first got it, I was sent a couple of forms (one for payment, and another for the setup) and I only ever emailed them off the payment one; I would've expected some form of confirmation back in the mail or something, but nope... all very odd really!

I know there are other people on the eyez-on board that have tested it out, so I'm quite confident it'll work, but I will get round to either setting it off by accident, or calling them up soon, or just wait until the misses does it by accident one day soon :)
Title: Re: DSC Alarm System plugin
Post by: Brientim on March 29, 2012, 04:48:18 am
There was somebody here that used an iTach serial to WiFi adapter and powered it either from the keybus or PGM output successively.

I powered an iTach serial to WiFi adapter from a PC5204. I tried this but was not successful. Revert to USB adapter and then brought the 2DS which still has some comms reliability issues. 
Title: Re: DSC Alarm System plugin
Post by: guessed on March 31, 2012, 12:36:01 pm
Looks like the 2DS units were patched this morning...
   http://forum.eyez-on.com/FORUM/viewtopic.php?f=6&t=297

I have some work to do to adapt to the changes.  :(
Title: Re: DSC Alarm System plugin
Post by: strangely on April 08, 2012, 01:34:15 pm
Here's a new keypad from DSC in case anyone wants to add some bling to their system:

http://baxsecurity.ca/index.php?main_page=product_info&cPath=2_6&products_id=51
Title: Re: DSC Alarm System plugin
Post by: guessed on April 09, 2012, 11:59:08 pm
Looks like the 2DS units were patched this morning...
   http://forum.eyez-on.com/FORUM/viewtopic.php?f=6&t=297

I have some work to do to adapt to the changes.  :(

Can the folks that are running the 2DS units (now firmware 65) let me know if they're still seeing the dropouts? 

My local tests have been successful since that firmware was pushed out, with the exception of the MiOS Bug that we're also tracking.  So far, it looks like the composite of the changes that the EnvisaLink folks have produced are holding up (at least to my stress testing rig)
Title: Re: DSC Alarm System plugin
Post by: strangely on April 10, 2012, 02:15:50 am
Can the folks that are running the 2DS units (now firmware 65) let me know if they're still seeing the dropouts? 

I'm away for the week again, but will get "er-indoors" to plug my V. Lite in again, or will cut over the plugin on my V3 to to using the 2DS rather than the IT100. I've had it unplugged for a bit since I thought you were going to make some changes to the plugin.
Title: Re: DSC Alarm System plugin
Post by: strangely on April 10, 2012, 02:28:06 am
Here's a new keypad from DSC in case anyone wants to add some bling to their system:

http://baxsecurity.ca/index.php?main_page=product_info&cPath=2_6&products_id=51

My Precious... *said in best Gollum voice :)

Oops, I ordered one for $179  ;D
Title: Re: DSC Alarm System plugin
Post by: Mikey on April 10, 2012, 11:26:14 pm
Here's a new keypad from DSC in case anyone wants to add some bling to their system:

http://baxsecurity.ca/index.php?main_page=product_info&cPath=2_6&products_id=51

My Precious... *said in best Gollum voice :)

Oops, I ordered one for $179  ;D
Sweet! Be sure to provide a review! :D

That said, any chance that you/one could finagle some sort of touch screen device that could control any Vera connected devices, i.e. where the DSC plugin would be one of many options?

Thanks for the link, strangely!
Title: Re: DSC Alarm System plugin
Post by: guessed on April 10, 2012, 11:28:14 pm
Sweet! Be sure to provide a review! :D

That said, any chance that you/one could finagle some sort of touch screen device that could control any Vera connected devices, i.e. where the DSC plugin would be one of many options?

Thanks for the link, strangely!

AutHomation has a bunch of this stuff, including Alarm support.
Title: Re: DSC Alarm System plugin
Post by: guessed on April 11, 2012, 12:03:12 am
Can the folks that are running the 2DS units (now firmware 65) let me know if they're still seeing the dropouts? 

I've had it unplugged for a bit since I thought you were going to make some changes to the plugin.

@strangely,
I have some changes queued, but they won't impact you right now.  Running the older codebase against the newer 2DS firmware will just give a warning on the Dashboard... which can safely be ignored.

The new code needs to be reworked a little for UI4, but it would be fine for UI5.
Title: Re: DSC Alarm System plugin
Post by: Mikey on April 11, 2012, 12:28:04 am
Hi everyone,

Trying to get my DSC plug-in working again, and after tracing through the developments of this thread, I am still a bit stuck.

Anyway, I have just recently updated to UI5 and, subsequently, started with a clean installation of the MiOS files for this plugin.  Similarly to the issues that I had with UI4, while the alarm partition and 6 zones would be created without issue, I could never interact with the partition / control box in any way.  Upon entering the disarm code and pressing "Set Time", I'm not getting any response back.  In essence, the Vera knows the box is there and can communicate with it sufficiently to create the devices (and their proper types, although the icons all show as "motion"), but that's about it.

The DSC box is connected via an IT-100 and WizNet board, which is pingable and connected by the configuration tool.

Any help or pointers to move forward would be appreciated.  Admittedly, I'm a UI5 noob, but with the core development towards shoring up the plug-in for the newer OS version and the fact that my previous configuration simply stopped working, I figured there'd be little harm in doing the upgrade.  That said, there is little upside at the moment either.

Thanks, guys, and I appreciate this otherwise very informative thread and great plug-in!

-Mike
Title: Re: DSC Alarm System plugin
Post by: guessed on April 11, 2012, 01:07:39 am
@Mikey,
After installing the plugin from apps.mios.com, you need to associate the IP Address/Port where the WIZnet is running.

I'm guessing that the association with the new DSC Alarm device is missing, or the port is missing.  Can you double check those against the definitions that are in the wiki config page for UI5:
    http://code.mios.com/trac/mios_dscalarmpanel/wiki/UI5

Once we get basic config sorted, we can move onto resetting the Zone(s) etc...  If in doubt, feel free to post some screenshots, similar to those from the guide, and we can usually work it out from that.
Title: Re: DSC Alarm System plugin
Post by: Mikey on April 11, 2012, 01:20:49 am
@Mikey,
After installing the plugin from apps.mios.com, you need to associate the IP Address/Port where the WIZnet is running.

I'm guessing that the association with the new DSC Alarm device is missing, or the port is missing.  Can you double check those against the definitions that are in the wiki config page for UI5:
    http://code.mios.com/trac/mios_dscalarmpanel/wiki/UI5

Once we get basic config sorted, we can move onto resetting the Zone(s) etc...  If in doubt, feel free to post some screenshots, similar to those from the guide, and we can usually work it out from that.
Ok, here we go...first with the Advanced Settings tab showing the IP (statically assigned) and Port (5000).  I've attached the WIZNet Network tab settings as well...one thing that isn't quite clear to me is that, when setting the IT-100 in Server mode, what precisely to set as the server IP and port.  I've tried this as .50 (the IP of the IT-100), .x for the IP of the Vera, and .y for the IP of the gateway to no avail.  Finally, the devices that were automatically created are as shown.

Thanks, in advance, for anything that you might see where I've gone wrong.

-Mike
Title: Re: DSC Alarm System plugin
Post by: Mikey on April 11, 2012, 01:27:52 am
As an additional note, the door sensor zones (1 & 2) and motion sensor zones (3 thru 6) appear to be properly configured upon their respective device creation steps.  In other words...

device_type for zones 1 & 2 = urn:schemas-micasaverde-com:device:DoorSensor:1
device_type for zones 3 - 6 = urn:schemas-micasaverde-com:device:MotionSensor:1

As shown in my previous post, however, the icons for zones 1 & 2 appear as motion detectors.  Reading about the earlier issues with sensor types, I have attempted to specify the pre-configured door zones as motion zones (and back again).
Title: Re: DSC Alarm System plugin
Post by: guessed on April 11, 2012, 01:46:22 am
Ok, I just re-read your original post.  First time around I didn't realize it wasn't working under UI4 either.

A few items to check:

a) The other panes of the WIZnet config, esp things like Baud Rate: http://forum.micasaverde.com/index.php/topic,5154.msg34061.html#msg34061
b) The RS-232 Cable itself: http://forum.micasaverde.com/index.php/topic,5154.msg31909.html#msg31909
c) ... or cutout the middleman cable: http://forum.micasaverde.com/index.php/topic,5154.msg51954.html#msg51954

The Icons are a known issue with UI5.  They have them, they just didn't cutover the UI to use them.  Control Points like AutHomation render these correctly based upon the types you're seeing.

PS: I defaulted Zones 1..6 as you're seeing them to give folks some basic indication of a need to reconfigure ;-)
Title: Re: DSC Alarm System plugin
Post by: Mikey on April 11, 2012, 02:00:48 am
Ok, I just re-read your original post.  First time around I didn't realize it wasn't working under UI4 either.

A few items to check:

a) The other panes of the WIZnet config, esp things like Baud Rate: http://forum.micasaverde.com/index.php/topic,5154.msg34061.html#msg34061
b) The RS-232 Cable itself: http://forum.micasaverde.com/index.php/topic,5154.msg31909.html#msg31909
c) ... or cutout the middleman cable: http://forum.micasaverde.com/index.php/topic,5154.msg51954.html#msg51954

Ok, the 9600-8-N-1 config on the WIZNet appears correct, and I did opt for the "short cable" option C. :D  It looks like all the wiring is connected properly, although the board is detached from its previously fixed position temporarily while I debug.

The Icons are a known issue with UI5.  They have them, they just didn't cutover the UI to use them.  Control Points like AutHomation render these correctly based upon the types you're seeing.

Certainly no big deal from my perspective...thought I'd mention it if it helped you perhaps see something that I may have missed.

PS: I defaulted Zones 1..6 as you're seeing them to give folks some basic indication of a need to reconfigure ;-)

Ok, admittedly I'm hung up on what it means to "reconfigure" a zone.  That is, my perception is that all zones were properly pre-configured, e.g. zone 1 is a door sensor to the DSC, is listed as such in the DSC Advanced Settings on the Vera, and appears to use the proper device file (D_DoorSensor1.xml).

Any other classic pitfalls?  To describe my UI4-based issues, I would summarize it by saying that it seemed as though the DSC would "fall asleep" and not properly update the Vera of its status.  The workaround was to perform a partition-PIN disarm followed by whatever else you wanted to do, i.e. this would "wake up" the Vera device to sync the status (from Stay to Disarm if, in fact, the system was actually disarmed but reporting the status from earlier that day).  The DSC had not connected with the Vera since mid-March, and no amount of PIN disarms would sync it, which is what prompted me to do the UI5 update to see if your new code might have solved the issues that I had been having.

Thanks, again, for your help.  Mrs. Mikey was getting quite used to controlling the alarm through the Vera (Home Buddy specifically), so I'm trying to avoid the WAF from diminishing.  ;)
Title: Re: DSC Alarm System plugin
Post by: garrettwp on April 11, 2012, 02:34:18 am
PS: I defaulted Zones 1..6 as you're seeing them to give folks some basic indication of a need to reconfigure ;-)

Ok, admittedly I'm hung up on what it means to "reconfigure" a zone.  That is, my perception is that all zones were properly pre-configured, e.g. zone 1 is a door sensor to the DSC, is listed as such in the DSC Advanced Settings on the Vera, and appears to use the proper device file (D_DoorSensor1.xml).

You need to add your zones according to what is configured by your panel. Guessed adds 6 zones at plugin install and is just a default. You will need to go into the the DSC Alarm Panel settings and click on the advanced tab. Under the fields for Door Zones, Motion Zones and Smoke Zones, you will need to enter your zones that correspond to those types of devices. For example I have:

DoorZones : 9,10,11,12,13,14,17
MotionZones: 1,15,19,25,26
SmokeZones: 16,18,24

Each zone is separated by a coma.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: Mikey on April 11, 2012, 01:40:22 pm
You need to add your zones according to what is configured by your panel. Guessed adds 6 zones at plugin install and is just a default. You will need to go into the the DSC Alarm Panel settings and click on the advanced tab. Under the fields for Door Zones, Motion Zones and Smoke Zones, you will need to enter your zones that correspond to those types of devices. For example I have:

DoorZones : 9,10,11,12,13,14,17
MotionZones: 1,15,19,25,26
SmokeZones: 16,18,24

Each zone is separated by a comma.

- Garrett

Thanks, Garrett.  I'm observing some very interesting behavior when configuring the zones within the DSC Control Panel Advanced settings as you've described.

As you noted (and using your format), here are the initial settings...

ActivePartition: 1
DoorZones : 1,2
MotionZones: 3,4,5,6
SmokeZones:

...which I then change to match the corresponding device id's of the created zones...

ActivePartition: 43
DoorZones : 44,45
MotionZones: 46,47,48,49
SmokeZones:

...and then Save changes.

The strange phenomenon, then, is that Vera will delete my previous devices - e.g. those numbered 43-49 above - and create new ones: the new partition is id=50, the door zones are id=51-52, and the motion zones are id=53-56.  Again, this appears to require me to re-reconfigure the zones since the DSC Control Panel is looking for devices that don't actually exist any more (after the save).

I think you can see that this creates a loop: (1) configure the DSC Control Panel settings, (2) apply the changes, (3) have a new set of created devices, and (4) GOTO 1.

Thoughts on how to break this loop...?
Title: Re: DSC Alarm System plugin
Post by: garrettwp on April 11, 2012, 02:07:51 pm
The zone numbers are that of the panel and not the device id's from the created devices in Vera.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: Mikey on April 11, 2012, 02:17:20 pm
The zone numbers are that of the panel and not the device id's from the created devices in Vera.

- Garrett
Then these are, in fact, correct...

ActivePartition: 1
DoorZones : 1,2
MotionZones: 3,4,5,6
SmokeZones:

Thanks for explaining the new device creation loop, but now I'm back where I started, i.e. Vera communicating with the DSC control panel upon installation of the plug-in to create the zones and partition, but then not communicating with it any time thereafter.  So it would seem...

Because this issue seems to originate from a progressive worsening "synchronization" issue between the Vera (UI4) and the IT-100 over time, might it make sense to clear any caches or some such thing...?  Again, I'm at this point tinkering with UI5 and the new version of the plug-in because my previous setup with UI4 and the old plug-in (0.32, IIRC) became unreliable.  Just wondering.

Thanks, again, for all of your help!

-Mike
Title: Re: DSC Alarm System plugin
Post by: garrettwp on April 11, 2012, 03:25:02 pm
The zones get created after the installation of the plug in with or without communication to the dsc alarm panel. They are to provide a starting point. So Vera probably never had communication with the panel in the first place.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: Mikey on April 13, 2012, 12:04:56 pm
So Vera probably never had communication with the panel in the first place.

Yeah, I sense - and understand that - now.  All of the connectivity checks seem to pass: half-second repeated blinking on integration board that reflects connectivity to WizNET device, can ping static IP address from both MCV and other machines on same network, readily modify settings on WizNET using config tool, etc.

Here's what goes on in the MCV at startup... (truncated entire log for brevity)

Code: [Select]
...

50 04/13/12 10:34:27.374 luup_log:43: DSCAlarmPanel: Running Network Attached I_DSCAlarmPanel1.xml on 192.168.1.50:5000 Device# 43, id  <0x402>

...

09 04/13/12 10:34:28.123 JobHandler_LuaUPnP::Run device 43 DSC Alarm Panel room 0 type urn:schemas-micasaverde-com:device:AlarmPanel:1 id  parent 0/0x892518 upnp: 0 <0x400>

...

09 04/13/12 10:34:28.132 JobHandler_LuaUPnP::Run device 50 Partition 1 room 0 type urn:schemas-micasaverde-com:device:AlarmPartition:2 id Partition-1 parent 43/0x89da88 upnp: 0 <0x400>

...

09 04/13/12 10:34:28.218 JobHandler_LuaUPnP::Run device 44 Zone 1 room 0 type urn:schemas-micasaverde-com:device:DoorSensor:1 id Zone-1 parent 43/0x894050 upnp: 0 <0x400>
09 04/13/12 10:34:28.219 JobHandler_LuaUPnP::Run device 45 Zone 2 room 0 type urn:schemas-micasaverde-com:device:DoorSensor:1 id Zone-2 parent 43/0x895c78 upnp: 0 <0x400>
09 04/13/12 10:34:28.220 JobHandler_LuaUPnP::Run device 46 Zone 3 room 0 type urn:schemas-micasaverde-com:device:MotionSensor:1 id Zone-3 parent 43/0x8974c8 upnp: 0 <0x400>
09 04/13/12 10:34:28.221 JobHandler_LuaUPnP::Run device 47 Zone 4 room 0 type urn:schemas-micasaverde-com:device:MotionSensor:1 id Zone-4 parent 43/0x898e70 upnp: 0 <0x400>
09 04/13/12 10:34:28.221 JobHandler_LuaUPnP::Run device 48 Zone 5 room 0 type urn:schemas-micasaverde-com:device:MotionSensor:1 id Zone-5 parent 43/0x89a7a8 upnp: 0 <0x400>
09 04/13/12 10:34:28.222 JobHandler_LuaUPnP::Run device 49 Zone 6 room 0 type urn:schemas-micasaverde-com:device:MotionSensor:1 id Zone-6 parent 43/0x89c228 upnp: 0 <0x400>

...

50 04/13/12 10:34:28.131 luup_log:43: DSCAlarmPanel: debug ActivePartitions: 1 <0x402>
50 04/13/12 10:34:28.266 luup_log:43: DSCAlarmPanel: debug Appending Child: 1 <0x402>
50 04/13/12 10:34:28.268 luup_log:43: DSCAlarmPanel: debug Door Sensors: 1,2 <0x402>
50 04/13/12 10:34:28.268 luup_log:43: DSCAlarmPanel: debug Appending Child: 1 <0x402>
50 04/13/12 10:34:28.270 luup_log:43: DSCAlarmPanel: debug Appending Child: 2 <0x402>
50 04/13/12 10:34:28.272 luup_log:43: DSCAlarmPanel: debug Motion Sensors: 3,4,5,6 <0x402>
50 04/13/12 10:34:28.273 luup_log:43: DSCAlarmPanel: debug Appending Child: 3 <0x402>
50 04/13/12 10:34:28.274 luup_log:43: DSCAlarmPanel: debug Appending Child: 4 <0x402>
50 04/13/12 10:34:28.275 luup_log:43: DSCAlarmPanel: debug Appending Child: 5 <0x402>
50 04/13/12 10:34:28.277 luup_log:43: DSCAlarmPanel: debug Appending Child: 6 <0x402>
50 04/13/12 10:34:28.279 luup_log:43: DSCAlarmPanel: debug Smoke Sensors:  <0x402>
50 04/13/12 10:34:28.282 luup_log:43: DSCAlarmPanel: debug Scanning luup.devices[44(number)] <0x402>
50 04/13/12 10:34:28.283 luup_log:43: DSCAlarmPanel: debug extractZone: Zone 1 <0x402>
50 04/13/12 10:34:28.284 luup_log:43: DSCAlarmPanel: debug Scanning luup.devices[45(number)] <0x402>
50 04/13/12 10:34:28.285 luup_log:43: DSCAlarmPanel: debug extractZone: Zone 2 <0x402>
50 04/13/12 10:34:28.286 luup_log:43: DSCAlarmPanel: debug Scanning luup.devices[46(number)] <0x402>
50 04/13/12 10:34:28.286 luup_log:43: DSCAlarmPanel: debug extractZone: Zone 3 <0x402>
50 04/13/12 10:34:28.287 luup_log:43: DSCAlarmPanel: debug Scanning luup.devices[47(number)] <0x402>
50 04/13/12 10:34:28.288 luup_log:43: DSCAlarmPanel: debug extractZone: Zone 4 <0x402>
50 04/13/12 10:34:28.289 luup_log:43: DSCAlarmPanel: debug Scanning luup.devices[48(number)] <0x402>
50 04/13/12 10:34:28.290 luup_log:43: DSCAlarmPanel: debug extractZone: Zone 5 <0x402>
50 04/13/12 10:34:28.291 luup_log:43: DSCAlarmPanel: debug Scanning luup.devices[49(number)] <0x402>
50 04/13/12 10:34:28.292 luup_log:43: DSCAlarmPanel: debug extractZone: Zone 6 <0x402>
50 04/13/12 10:34:28.293 luup_log:43: DSCAlarmPanel: debug Scanning luup.devices[50(number)] <0x402>
50 04/13/12 10:34:28.294 luup_log:43: DSCAlarmPanel: debug extractZone: Zone N/A <0x402>
50 04/13/12 10:34:28.295 luup_log:43: DSCAlarmPanel: debug extractPartition: Partition 1 <0x402>

...

When trying to set the time, I get this...

Code: [Select]
08 04/13/12 11:01:04.034 JobHandler_LuaUPnP::HandleActionRequest device: 43 service: urn:micasaverde-com:serviceId:DSCAlarmPanel1 action: SyncTime <0xa419>
08 04/13/12 11:01:04.035 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=43 <0xa419>
08 04/13/12 11:01:04.035 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:DSCAlarmPanel1 <0xa419>
08 04/13/12 11:01:04.036 JobHandler_LuaUPnP::HandleActionRequest argument action=SyncTime <0xa419>
08 04/13/12 11:01:04.036 JobHandler_LuaUPnP::HandleActionRequest argument PINCode=xxxx <0xa419>
08 04/13/12 11:01:04.037 JobHandler_LuaUPnP::HandleActionRequest argument rand=0.9542079626960399 <0xa419>
50 04/13/12 11:01:04.040 luup_log:43: DSCAlarmPanel: debug Action::SetTime:1101041312 <0xa419>
50 04/13/12 11:01:04.043 luup_log:43: DSCAlarmPanel: debug sent (010,1101041312), setup callback (function: 0xb07128) <0xa419>
Title: Re: DSC Alarm System plugin
Post by: guessed on April 13, 2012, 12:25:26 pm
@Mikey,
Can you send me the full [verbose-enabled] log?  I'll send you a PM shortly with an email address.  I need to see the IO debug lines, which look like they've been filtered out.
Title: Re: DSC Alarm System plugin
Post by: Mikey on April 13, 2012, 05:45:17 pm
@Mikey,
Can you send me the full [verbose-enabled] log?  I'll send you a PM shortly with an email address.  I need to see the IO debug lines, which look like they've been filtered out.
Thanks for your help, @guessed. Using the WIZnet terminal program, I was unable to connect to it from my PC via port 5000: "unable to connect socket".  So surely the MCV is having the same issue.  Appreciate your help in coming up with the conclusion!
Title: Re: DSC Alarm System plugin
Post by: guessed on April 13, 2012, 05:47:54 pm
WIZnet's can only have one thing connected to them at any time.  From the log that you sent me, the Vera is successfully connecting to the WIZnet, so nothing else will be let in (whilst the Vera is running, or whilst it's connected to that ip:port)
Title: Re: DSC Alarm System plugin
Post by: Mikey on April 16, 2012, 11:38:15 pm
WIZnet's can only have one thing connected to them at any time.  From the log that you sent me, the Vera is successfully connecting to the WIZnet, so nothing else will be let in (whilst the Vera is running, or whilst it's connected to that ip:port)
Well, I reached out to WIZnet for support on this, if only to pinpoint the issue.  As a means of testing connectivity between the MCV and the S2E card, I installed the Ping Sensor program and configured it to ping the static IP of the WIZnet every minute (if only as a future means to "keep it alive").  In any event, to my knowledge, the MCV is able to ping it, so comm over port 5000 seems to be the issue.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on April 17, 2012, 12:27:08 am
Are you sure that the settings on the wiznet are setup correctly? The serial settings like baud rate and so forth?

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on April 17, 2012, 12:42:02 am
I'm leaning towards what @garretwp mentions above. 

The logs you gave showed Vera successfully connecting to Port 5000 on the WIZnet, and sending the initial requests to the alarm panel... It's just that there were no responses coming back from those requests, so the TCP side of the WIZnet seems to be working correctly.

Once Vera is connected, no one else can connect.  If you wanted to test it with Telnet (etc) then you can turn Vera off for a while.

The Ping test will only check basic networking connectivity, and is def a good first step (from Vera) but your logs already show successful connection to the WIZnet, so something else is amiss (baud etc, or IT100 wiring to the Combus)
Title: Re: DSC Alarm System plugin
Post by: Mikey on April 17, 2012, 08:35:37 pm
Well, unfortunately, either something is awry with the card or one of my settings - which are otherwise aligned with the instructions - doesn't quite jive with my network environment, i.e. other comm with the card beyond either the MCV or config tool that "monopolizes" it, or other unknown impact to the card.

The IT-100 is reporting consistent half-second LED flashes, so I know that that's working.  And you, @guessed, confirmed that comms are established to the card via the network (on the "TCP side").  That only leaves the serial-to-serial connection, which is, as previously reported, done using the no-middleman-method (because I didn't have a spare cable lying around).

Since the setup worked for a few months and steadily eroded over time, I can't help but wonder if something physically is awry in the connection.  That said, taking a good look at the physical ports themselves, there doesn't seem to be any visible wear or other damage.  Hard to say, but I am thoroughly perplexed.  This is beyond my expertise to sort out, so I may end up just waiting for either (1) stability with the new DSC integration card or (2) alternatives to the WIZnet WIZSR110 as an S2E connector.

Again, gentlemen, I appreciate your expert advice.  This is certainly a well supported plug-in for that reason.  Many thanks for that!
Title: Re: DSC Alarm System plugin
Post by: guessed on April 17, 2012, 09:27:12 pm
a few last things to try:

a) Ensure that the WIZnet is NOT plugged into Vera
Plug it into a regular Network Switch or Router port on your Network, but not into any of the "spare" ports on the Back of Vera

b) Reset the Server IP field to 0.0.0.0, and corresponding Port to 0
It looks like you changed it in the most recent round of mods (compared to prior image you posted).  I have no idea what this does, so it probably should be left "as default".  Alternatively, try telling Vera that the DSC Alarm Plugin is on that IP Address (since it's different)

c) Since you've manually assigned IP, validate that there are no conflicts on the Network.
I think @strangely has his on DHCP, so it's a good address.  It might pay to unplug the WIZnet, and validate (via ping et-al) that there's nothing transient on that address.

d) Try a different power supply for the WIZnet, just in case.
I've seen cases where the PS units get fried, on other hardware, and they start behaving oddly.

e) Set the DNS Server IP Field... just in case.
Yours shows as 0.0.0.0., but @strangely's shows as the one gotten from his DHCP Server.


Other than that, and any physical connectivity, I'm a little stumped.  There are mentions on other forums where people reset the Baud rate on the IT100 itself, but I don't imagine you did that since it seems a little involved, and you're indicating gradual decay.
Title: Re: DSC Alarm System plugin
Post by: strangely on April 18, 2012, 12:09:03 am
Not sure if this has been tried already, but how about down powering the panel/disconnecting the battery for a minute before reconnecting? Or defaulting the IT100 using the method listed indevelopers guide or instruction brochure (shorting some pins)

Failing that the perhaps try a USB serial adapter (if you have one spare?) to rule out something odd with the serial side of the WIZnet?

Also checked for pushed back pins on the connectors, or ones that may not be locked... Sometimes these connectors look fine, with all pins intact, but push back when the connectors are mated together the pins push back until pulled apart again.
Title: Re: DSC Alarm System plugin
Post by: strangely on April 18, 2012, 12:10:08 am
Failing all of the above, ditch it all and get a 2DS instead!
Title: Re: DSC Alarm System plugin
Post by: mpierce on April 18, 2012, 01:19:56 pm
I just installed a DSC 1832 with the 2DS module and am trying to get the plug-in to work. 

I am using a Vera 2 with UI5. 

I have downloaded the plugin from the Wiki uploaded the files through the Develop Apps / Luup files and then created a new device with D_DSCAlarmPanel1.xml as Upnp Device Filename. 

The plugin installed I then set my IP with port (192.168.10.141:1025) in the advanced tab on the plugin.  I also changed interface type to "2DS".

I am getting the following error - "DSCAlarmPanel: Error logging into 2DS, please check your password".  The 2DS password is still the default "user" and is set to "user" in the advanced tab of the plugin.

Thanks in advance and for the time spent making this integration possible!
Title: Re: DSC Alarm System plugin
Post by: strangely on April 18, 2012, 01:27:17 pm
Did you use the files from here:

http://code.mios.com/trac/mios_dscalarmpanel/browser/trunk
Title: Re: DSC Alarm System plugin
Post by: mpierce on April 18, 2012, 02:14:23 pm
I just uploaded those files and it's working now.

Thanks!
Title: Re: DSC Alarm System plugin
Post by: mpierce on April 21, 2012, 01:41:58 am
The plugin was working for about a day and then suddenly stopped.  If I reboot or reloaded Vera it would work for about 1-2 mins then become unresponsive again.  I have tried reloading everything several times and finally just reset to factory defaults and only loaded the Alarm Plugin and still having the disconnect issue.

Any ideas?
Title: Re: DSC Alarm System plugin
Post by: guessed on April 21, 2012, 05:34:42 am
@mpierce,
Can you describe your setup and connectivity of components?

Eg IT100 or 2DS, Vera 2 or 3, Firmware version, Serial or Ethernet, USB Hub or Ethernet switch (etc)
Title: Re: DSC Alarm System plugin
Post by: mpierce on April 21, 2012, 10:59:21 am
I have a Vera 2 with UI5 (1.5.346) and a 2DS (1.07.65) both with static IPs.  I had it working for about a day - the only changes I made were adding a few new switches to my network and manually setting the Zone descrtiptions.  Last night after trying everything I could think of I reset back to factory defaults and installed the plugin like I had when it was working - still no luck...  Now if I do a reboot or refresh it will get the current state of the DSC alarm sensors but will not stay connected long enough to even report a sensor change.
Title: Re: DSC Alarm System plugin
Post by: guessed on April 21, 2012, 12:58:27 pm
Ok, I'll PM you shortly with an email address that you can send a log file to.  I'll need the log to contain a complete startup sequence, all the way up to the point where the 2DS isn't responsive to motion again.

I can then look over that, and see if there's a pattern to it dropping out.

Q: Have you restarted your Vera in the last few weeks, or was it running through to the point where the new Z-Wave devices were being added (since the restart would have triggered the Plugin to be restarted, which might have captured a startup issue)
Title: Re: DSC Alarm System plugin
Post by: mpierce on April 21, 2012, 01:39:10 pm
Just sent you the log file.

Vera had been running stable for several weeks / months (with out the plug-in).  I added the plugin - got it working (for about a day) then added some more z-wave switches to my network and tried to get the correct sensor labels to broadcast to the 2DS (which I was unsuccessful with and ended up setting them manually)  about that time is when I started experiencing the connectivity issues.  Not sure if those changes are related because I still have the issues after a factory reset of Vera.
Title: Re: DSC Alarm System plugin
Post by: mpierce on April 21, 2012, 02:02:43 pm
I also just tried arm / disarm from Vera and that is working.  So it seems like there is some communication via the 2DS but sensor values are not updating.
Title: Re: DSC Alarm System plugin
Post by: oTi@ on April 21, 2012, 02:45:48 pm
Which keypad(s) do you have?
Title: Re: DSC Alarm System plugin
Post by: mpierce on April 21, 2012, 03:04:27 pm
I have the RFK5500 Keypad
Title: Re: DSC Alarm System plugin
Post by: oTi@ on April 21, 2012, 03:14:59 pm
I have the RFK5500 Keypad
Interesting. I do too, and have some observations similar to yours; especially the last bit where you said arming/disarming appears to work, but not zone updates. Have you tried assigning the keypad to a different slot at all?

Also, I just PM'd @guessed with some notes.
Title: Re: DSC Alarm System plugin
Post by: mpierce on April 21, 2012, 03:39:52 pm
Quote
Interesting. I do too, and have some observations similar to yours; especially the last bit where you said arming/disarming appears to work, but not zone updates. Have you tried assigning the keypad to a different slot at all?

Also, I just PM'd @guessed with some notes.

Yes I just reassigned the keypad to a different slot and am having the same results.  It does make me feel better that I'm not alone  :D
Title: Re: DSC Alarm System plugin
Post by: strangely on April 21, 2012, 07:08:35 pm
This was exactly how mine was acting on the 2DS prior to the last couple of firmware revions (2DS) that seemed have fixed it. Looks like it may be be back to its bad ways again.

What does your log on tbe Envisalink site say? Can you see any TPI connect and disconnect messages?

I've been away from home a lot recently, and so have been running mine from the IT100 for the time being, and have t looked how the 2DS has been acting. Guess its time to get it up and running again tonight for some testing!

Richard
Title: Re: DSC Alarm System plugin
Post by: mpierce on April 21, 2012, 07:34:08 pm
Yes I am getting TPI login and TPI Session closed message every couple of minutes.


2012-04-21 16:50:08 - TPI Session Closed
2012-04-21 16:47:03 - TPI Login
2012-04-21 16:46:27 - TPI Session Closed
2012-04-21 16:42:08 - TPI Login
2012-04-21 13:42:08 - TPI Session Closed
2012-04-21 13:38:23 - TPI Login
2012-04-21 13:36:39 - TPI Session Closed
Title: Re: DSC Alarm System plugin
Post by: guessed on April 21, 2012, 08:04:04 pm
Ok, so the startup sequence looks to be correct.  The log file provided (thanks @mpierce !!) shows two full startup sequences

The first sequence terminated with:

Code: [Select]
50 04/21/12 11:23:03.633 luup_log:46: DSCAlarmPanel: debug Partition::Trouble Status (LED OFF) 841 partition: 8 <0x540d>
50 04/21/12 11:23:04.046 luup_log:46: DSCAlarmPanel: debug processIncoming:: Command=510, Data='80', Checksum=FE <0x540d>
50 04/21/12 11:23:04.047 luup_log:46: DSCAlarmPanel: debug Panel::Keypad LED State - Partition 1 only (80) <0x540d>
04 04/21/12 11:23:30.173 <0x803>
06 04/21/12 11:23:33.091

2012-04-21 11:23:43 - LuaUPnP Terminated with Exit Code: 139

The end part being a SIGSEGV termination (11).


Can you run the following on your log file:
Code: [Select]
    grep "Code: 139" /var/log/cmh/LuaUPnP.log
and let me know if the times correlate to the disconnects reported by the 2DS console?

If not, can you turn on Verbose logging, and send me a longer log file (a few hours worth, if at all possible).  I will filter it down here to the bits that I need, but  I'd like the Verbose logging enabled so I can capture the IO (51, 52) signals along with my debug messages.



BTW: I have the RFK 5500 Keypad and a 1832, along with the 2DS, so it's a similar setup.  The main difference is that I only have 2 zones (one manual, one pushed by an Automated Relay tester)
Title: Re: DSC Alarm System plugin
Post by: mpierce on April 21, 2012, 08:54:45 pm
Here is the results of the grep command:

2012-04-21 17:54:55 - LuaUPnP Terminated with Exit Code: 139
2012-04-21 17:58:17 - LuaUPnP Terminated with Exit Code: 139
2012-04-21 18:00:52 - LuaUPnP Terminated with Exit Code: 139
2012-04-21 18:03:05 - LuaUPnP Terminated with Exit Code: 139

Here is what Envisalink website reports:

2012-04-21 18:07:24 - TPI Session Closed
2012-04-21 18:03:26 - TPI Login
2012-04-21 18:03:13 - TPI Session Closed
2012-04-21 18:01:31 - TPI Login
2012-04-21 18:01:00 - TPI Session Closed
2012-04-21 18:00:10 - TPI Login
2012-04-21 18:00:10 - TPI Session Closed
2012-04-21 17:56:05 - TPI Login
2012-04-21 17:55:59 - TPI Session Closed
2012-04-21 17:55:59 - TPI Login
2012-04-21 17:55:58 - TPI Session Closed
2012-04-21 17:55:53 - TPI Login
2012-04-21 17:55:52 - TPI Session Closed
2012-04-21 17:51:40 - TPI Login
2012-04-21 17:41:41 - TPI Session Closed
2012-04-21 17:37:56 - TPI Login
Title: Re: DSC Alarm System plugin
Post by: guessed on April 21, 2012, 09:36:50 pm
Vera is basically crashing and restarting...  and frequently enough that no data is getting back in from the Panel after the initialization sequence has completed.  In some cases, it's completing, and then it's restarting due to a crash of LuaUPnP.

It looks like you have TED5000, SQRemote, the MinMax T-Stat and the Energy Plugin (ERGY?)

One of the main differences in your config is that you have all of the Zones specified as DoorSensors.  Can you switch these over to the MotionSensors config parameter (leaving DoorSensors blank)?

This new sensor type is only relatively new, and perhaps there's an issue in the tech stack somewhere in handling it for this plugin.  There's definitively an issue in some part of Vera, since it should never SEGV.

@oTi@, can you validate the same in your config?  This may need a diagnostics session with MCV to fix if the above W/A doesn't work.
Title: Re: DSC Alarm System plugin
Post by: Brientim on April 22, 2012, 03:26:55 am
Hello,

I have had my test bed offline due to I have been travelling. That place were crows come from this week.

I set it up today for a short period and currently it has only the 2DS and that is it. No other apps or devices on this system.

It is still is disconnecting. I changed setting to se if it still occurred with the W/A implemented and it still resulted in terminations.

I did grab the log it is only for the last four hours.
I do not have much time this week until after 25 Apr which is a big day here and for me.
Title: Re: DSC Alarm System plugin
Post by: mpierce on April 22, 2012, 03:59:53 am
I also reset all my sensors to be motionsensors and am still having the same results.
Title: Re: DSC Alarm System plugin
Post by: guessed on April 22, 2012, 07:27:06 am
Created this post in the UI5 Beta/1.5.346 thread as we need MCV to resolve why the LuaUPnP process is crashing so often:
    http://forum.micasaverde.com/index.php/topic,9970.msg70932.html#msg70932
Title: Re: DSC Alarm System plugin
Post by: guessed on April 24, 2012, 11:33:15 pm
@mpierce, @Brientim, @strangely,
As a side-note, I've been running my Testbed DSC 1832 / 2DS combination all day with an automated tester (cycling input 2 every ~7s) and have not been able to reproduce the crashes against Vera3 with a slightly newer firmware.  I doubt the issue was magically addressed, given the info we have, so it might be something else in the environment.

My Vera3 is stripped down to a small handful of plugins, mostly inactive as I only use it for testing.

@strangely:: If you haven't yet, you may want to hold off of the private Beta upgrade and see if you can get yours crashing on the Public beta release, this would help as a baseline (unfortunately I had updated mine remotely)
Title: Re: DSC Alarm System plugin
Post by: guessed on April 25, 2012, 01:35:48 am
I also reset all my sensors to be motionsensors and am still having the same results.

Since this is reproducable for you, can you open a support ticket, from within Vera, and make reference to errors

eg. 2012-04-21 17:54:55 - LuaUPnP Terminated with Exit Code: 139


In addition to posting a link into the ticket showing the forum post.  That perhaps will get more attention since they've gone somewhat silent on that Beta thread.  SEGV/ABEND/Crashes like this shouldn't happen, and it seems like it's in a core bit of logic so it'll be important to get it fixed up.

I was planning on working with MCV directly, but I'm not able to repro in my environment.   ??? 
Title: Re: DSC Alarm System plugin
Post by: Brientim on April 25, 2012, 03:25:37 am
@guessed,

As identified, the vera caused an aburpt temination after adding an app to Vera. Please find attached the log file.

Regards
Title: Re: DSC Alarm System plugin
Post by: strangely on April 25, 2012, 11:23:23 am

@strangely:: If you haven't yet, you may want to hold off of the private Beta upgrade and see if you can get yours crashing on the Public beta release, this would help as a baseline (unfortunately I had updated mine remotely)
Private beta of the 2DS firmware or the plugin?

I connected mine up before I left for Atlanta again this week, and it seemed to be working (albeit with a password error), however I updated it with the latest tag, and it doesn't seem to work any more. I will give you a call later with some more information.
Title: Re: DSC Alarm System plugin
Post by: guessed on April 25, 2012, 11:45:52 am
... the MiOS Private Beta firmware.  I upgraded mine to the latest version, which is slightly newer than the Public Beta, so there's a chance the reason I'm not seeing any issues relates to the fact I'm on a more recent MiOS release.

... or it could just be environmental.  Presumably everyone's operating off of the /trunk version that's in code.mios.com, and using the latest published/public 2DS firmware (auto-updated, if your registered) at least it should be fine for UI5 users (there's a chance it won't work correctly for UI4 users as I have to borrow a code-snippet from @futzle's code)
Title: Re: DSC Alarm System plugin
Post by: strangely on April 25, 2012, 12:50:02 pm
I only updated my V3 remotely (running against IT100 though), but I haven't seen any notifications from my Vera Lite which is only running the 2DS plugin (no other devices). The V.Lite has not been updated to the private beta yet either.

Normally the door I have a test notification set up on is used frequently, and as my wife is at home I would've expected to have seen a lot of zone trips. I'm also getting a few TPI login and logout messages.

Wont be home until Friday evening but I can likely grab a log shortly and forward it if you like?
Title: Re: DSC Alarm System plugin
Post by: guessed on April 26, 2012, 01:41:53 am
@guessed,

As identified, the vera caused an aburpt temination after adding an app to Vera. Please find attached the log file.

Regards

@Brientim,
From the more detailed logs that you sent me privately, I can see that you're running a much older version of the 2DS codebase.

Can you switch over to loading it from /trunk, and see if the problem continues?

The trunk version was freshly written to handle all of the newer 2DS start-up behaviors (many added at @strangely and my request).  Without the latest code, very strange things will happen, particularly wrt the passwords that the 2DS requests.
Title: Re: DSC Alarm System plugin
Post by: Brientim on April 26, 2012, 02:20:37 am
@guessed,

Done. I only downloaded the new version the other day; however, I must have reloaded the old version from trunk72.... Anyway, I will let it do its thing for next few days and update if anything unexpected occurs.

Thanks again.
Title: Re: DSC Alarm System plugin
Post by: Brientim on April 26, 2012, 06:09:02 pm
@guessed,

SEGV - Not good news: LuaUPnP Terminated with Exit Code: 139. with new version.
I have forward logs to you.


Title: Re: DSC Alarm System plugin
Post by: guessed on April 26, 2012, 06:13:19 pm
Actually, that's good news.  Once they all have consistently reproducible behavior I have a bigger hammer to get MiOS fixed ;)

@strangely is going to do the same to his box this weekend, so we'll have consensus at that point (my Vera3 unit isn't doing it, but I have a slightly newer firmware)
Title: Re: DSC Alarm System plugin
Post by: Brientim on April 26, 2012, 06:32:25 pm
Accepted... Bad news that it is crashing... good news as you identified that there is it a repeatable incident. 

I also remember recently, there was another string in WOL which was reporting or commented on another plugin that was producing a SEGV at Re: Exit Code 139 http://forum.micasaverde.com/index.php/topic,9838.msg66166.html#msg66166 so there is an underlying problem that is starting to surface.
Title: Re: DSC Alarm System plugin
Post by: guessed on April 26, 2012, 06:49:46 pm
If you can, enable Verbose mode on Vera, enable Support tunnels, and then open a Ticket up against them.  Then they'll be able to get into your machine to see it in action (if you're ok with that)
Title: Re: DSC Alarm System plugin
Post by: Brientim on April 26, 2012, 07:56:09 pm
Already done. Ticket allocated to mcvflorin
Title: Re: DSC Alarm System plugin
Post by: oTi@ on April 28, 2012, 12:56:24 pm
Regarding my earlier observations (http://forum.micasaverde.com/index.php/topic,5154.msg70898.html#msg70898), I went from an initially non-working state to a working state and felt the only significant chance I had made was the slot assignment for the RFK, but later changed that back and things kept working. That was last Saturday.

Let that sit until Wednesay, and it was still functional, i.e. I was still getting zone updates for my single test zone. No restarts, or SEGV's.

Then on Wednesday, I moved the 2DS to a static IP and things stopped working. That is, the initial state after Lua restart would be correct and actions initiated from Vera would work, but no autonomous updates from the 2DS would be received.

Looked at that this morning, changed the slot assignment (plus supervisory reset): no change. Same behavior every time, after every Lua restart. Then, power-cycled panel/2DS, restarted Lua: working!

When I changed the IP on Wednesday, I never power-cycled the panel/2DS, but did re-insert the LAN cable a few times, etc.
Title: Re: DSC Alarm System plugin
Post by: strangely on April 28, 2012, 06:37:35 pm
Interestingly mine has been quite unreliable up until I changed my router yesterday, and it seems to have not missed a beat at all now! Not sure if coincidental or not?!
Title: Re: DSC Alarm System plugin
Post by: Brientim on April 28, 2012, 06:42:49 pm
Looked at that this morning, changed the slot assignment (plus supervisory reset): no change. Same behavior every time, after every Lua restart. Then, power-cycled panel/2DS, restarted Lua: working!

I read @oTi's post and decided to run a supervisor reset as well (I did not have to change the slot assignment). I also powered down the panel and remotely rebooted 2DS and restarted Lua and it is working currently as designed without any error. 


Title: Re: DSC Alarm System plugin
Post by: guessed on April 28, 2012, 06:50:27 pm
Maybe that's why I don't see it, I tend to run for days where it's unplugged, between testing cycles which are usually 24-48 hrs ea time before shutting it down again.

Either way, none of the 2DS behavior would cause Vera to SEGV, so that's still a problem...
Title: Re: DSC Alarm System plugin
Post by: Brientim on April 28, 2012, 07:27:51 pm
@guessed,

Totally agree.

Working as designed did not last long... I have stated I believe there are environmental factors involved and I indicated that when another device (via WIFI) was connected to the Vera an error sometimes occurs. When I connected the iPad, this again resulted in an error and in this case it resulted in no autonomous updates and of course that I can not control the panel via the Vera.

The 2DS is reporting it is still connected and the local log on to the 2DS is reporting the updates; however, this is where the story stops. Currently, the same MAC address is allocated as internal, external and against the WIFI and I am not sure if this is causing some underlying problem.   
Title: DSC Alarm System plugin
Post by: binburra on April 28, 2012, 08:33:03 pm
What is the recommended hard wired keypad I can use for the PC 1832 or PC 1864 ?
Does it even matter which keypad I use when I have the 2DS in the DSC panel?


---
I am here: ?nivlme
Title: Re: DSC Alarm System plugin
Post by: strangely on April 28, 2012, 11:29:52 pm
Well you'll need one for programming really, and I don't really recommend not having one!

So it comes down to how much you want to spend and the following questions:


If you can answer the above then I can make a recommendation. As for whether it will run without a keypad... maybe, but it might become problematic to arm / disarm if Vera is down for any reason.
Title: Re: DSC Alarm System plugin
Post by: oTi@ on April 29, 2012, 01:04:15 am
Either way, none of the 2DS behavior would cause Vera to SEGV, so that's still a problem...
Right; seems like 2 separate issues.

Moved the stuff off the test Vera and onto the main Vera; changed the IP again also. Had the problem again, initially, but some reboots later it's running again.
Title: Re: DSC Alarm System plugin
Post by: binburra on April 29, 2012, 01:56:49 am
Well you'll need one for programming really, and I don't really recommend not having one!

So it comes down to how much you want to spend and the following questions: (cost is not a issue  more about quality for me)

  • Do you want to program it easily?
(yes)
  • Do you want it show any open zones with a text description of what may be open or not?
(Yes)
  • Are you planning on adding wireless devices?
(No)
  • Do you want a color LCD screen?
(no)
[/list]

If you can answer the above then I can make a recommendation. As for whether it will run without a keypad... maybe, but it might become problematic to arm / disarm if Vera is down for any reason.
Title: Re: DSC Alarm System plugin
Post by: strangely on April 29, 2012, 05:39:07 pm
OK well if you don't want wireless then the PK5500 will be OK.

Try eBay, otherwise it's about $90 online elsewhere!

This is a good deal if you want to get wireless included:

http://www.ebay.com/itm/NEW-DSC-RFK5500-POWER-SERIES-64-ZONE-WIRELESS-FULL-MESSAGE-LCD-KEYPAD-/230782317258?pt=BI_Security_Fire_Protection&hash=item35bbb2b2ca#ht_500wt_1159

Worthwhile to buy so that you can use keyfobs etc, or if you decide to need something in the future if you have no wires available.
Title: Re: DSC Alarm System plugin
Post by: binburra on April 30, 2012, 06:30:42 am
Thanks Strangley, apriciate the helpfull advice :) :)
Title: Re: DSC Alarm System plugin
Post by: undertoe on May 01, 2012, 01:10:42 pm
Latest 75 trunk on UI5 with 2DS worked perfect Firmware Version: 01.07.70
http://code.mios.com/trac/mios_dscalarmpanel/browser/trunk

Couple things I noticed

EnableRemoteArm variable: stay,arm,disarm from the wiki but stay doesn't seem to work

Any direction on how to get the labels I programmed in my existing keypad to broadcast to the 2DS and show up in vera? I have tried the wiki with
*8[Installer code]*998*

Any help would be great.
Title: Re: DSC Alarm System plugin
Post by: guessed on May 01, 2012, 01:26:24 pm
EnableRemoteArm variable: stay,arm,disarm from the wiki but stay doesn't seem to work
Can you describe the behavior that you're observing?  Typically when the flags aren't set, I'll present a message in the UI indicating it's not enabled.  Once I'm past that, I simply present the Arm/Disarm/Stay (etc) command on the bus.

Quote
Any direction on how to get the labels I programmed in my existing keypad to broadcast to the 2DS and show up in vera? I have tried the wiki with
*8[Installer code]*998*
2DS Units don't support Label broadcast.  I make the request for the Label data, but it never supplies it, so you have to enter them manually (they won't get overwritten, as the 2DS never responds to that message)
Title: Re: DSC Alarm System plugin
Post by: garrettwp on May 01, 2012, 01:26:59 pm
I believe the label issue with the 2ds is a 2ds issue. Last I read this was not supported yet by the 2ds module.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: strangely on May 01, 2012, 02:01:54 pm
We have asked for support of the label broadcast to be added to the 2DS and had some communication with the developer about it.

We need to follow up on it again as it was uncertain if they were going to add support for it due to memory constraints on the 2DS.
Title: Re: DSC Alarm System plugin
Post by: oTi@ on May 01, 2012, 02:18:10 pm
EnableRemoteArm variable: stay,arm,disarm from the wiki but stay doesn't seem to work
Tried it: get the error message in the UI.
If I'm looking in the right spot, it appears stay is not decoded as a valid value in initializeParameters()?
Title: Re: DSC Alarm System plugin
Post by: undertoe on May 01, 2012, 02:31:17 pm
Quote
        if (enableRemoteArming  == nil) then
            ENABLE_REMOTE_ARM = false
            ENABLE_REMOTE_DISARM = false
            luup.variable_set(DSC_PANEL_SID, "EnableRemoteArm", "false", device)
        elseif (enableRemoteArming  == "false") then
            ENABLE_REMOTE_ARM = false
            ENABLE_REMOTE_DISARM = false
        elseif (enableRemoteArming == "arm") then
            ENABLE_REMOTE_ARM = true
            ENABLE_REMOTE_DISARM = false
        elseif (enableRemoteArming == "disarm") then
            ENABLE_REMOTE_ARM = true
            ENABLE_REMOTE_DISARM = true
        else
            return false,
                   "EnableRemoteArm Parameter must be either blank, false or a value from the wiki...",
                   MSG_CLASS
        end

Yep just about to post that no logic for it in initializeParameters I_DSCAlarmPanel1.xml starting at line 855

Other than that really impressed with the plugin, you put in some work whoever did it! Nice to see people other there picking up the slack ;) Thanks for your time and effort!
Title: Re: DSC Alarm System plugin
Post by: Brientim on May 01, 2012, 02:49:56 pm
Update. After they deployed the new firmware 70, I have not had one termination.

Just a minor change:
Modified the 841 to be No trouble - LED off as it read better
Title: Re: DSC Alarm System plugin
Post by: guessed on May 01, 2012, 04:05:07 pm
Yep just about to post that no logic for it in initializeParameters I_DSCAlarmPanel1.xml starting at line 855

Other than that really impressed with the plugin, you put in some work whoever did it! Nice to see people other there picking up the slack ;) Thanks for your time and effort!
Oddly enough, the "stay" option is a Doc-bug that rolled over from the Paradox documentation (where it was also a bug).  It dates back to a time where I had a set of Paradox Alarm Plugin options to let you "pick" which ones you wanted, which I merged/simplified into what you have today (arm, disarm or false)

Looks like I didn't update the doc correctly at that time, and it got cloned into the DSC doc.

The original guidelines were to make "the defaults" such that arming and disarming actions couldn't be done without extra-config, for security reasons.

If folks really need separate control to lockout Stay (and the variants of stay like Night, StayInstant, etc, etc, etc) let me know and I can look at adding it in.  Otherwise we can remove the doc.
Title: Re: DSC Alarm System plugin
Post by: oTi@ on May 01, 2012, 04:10:37 pm
Perhaps for now tweak doc to remove stay option, and add a comment about label broadcasts in conjunction with 2DS?
Title: Re: DSC Alarm System plugin
Post by: undertoe on May 01, 2012, 06:21:59 pm
OK so I am trying to do a trigger scene by the system armed in anyway (stay or away) by (vera or by keypad) to make sure external doors are locked via deadbolts. I am using the 2DS
Title: Re: DSC Alarm System plugin
Post by: strangely on May 01, 2012, 06:25:58 pm
OK so I am trying to do a trigger scene by the system armed in anyway (stay or away) by (vera or by keypad) to make sure external doors are locked via deadbolts. I am using the 2DS
Did you get it to work?
Title: Re: DSC Alarm System plugin
Post by: undertoe on May 01, 2012, 10:18:52 pm
Yes and No.

currently I have a trigger for both "Partition 1 is armed Stay" or "Partition 1 is Armed" this triggers my Garage door to shut & Doors to be locked.

It works when i arm the system via Vera or Direct on the 2DS web interface.

It does not work if I arm from a keypad in my house somewhere. I also noticed from watching the logs that it almost stops "polling" the device. So like when I arm the system from 2DS web or from vera I see activity to/from DSC. But like if I arm from Keypad then nothing, Partition 1 doesn't update status in the UI either.

Is this normal functionality?

EDIT: So tried it after I posted, Armed from Keypad and did report ExitDelay, which I have never seen it do that.

50      05/01/12 22:19:31.319   luup_log:29: DSCAlarmPanel: debug processIncoming:: Command=656, Data='1', Checksum=D2 <0x2eb2d680>
50      05/01/12 22:19:31.322   luup_log:29: DSCAlarmPanel: debug Partition::Exit Delay in Progress 656 partition: 1 <0x2eb2d680>

Even though keypad says armed, Vera partition one says ExitDelay still. Then if i hit Reload in UI5 it refreshes the status of Partition 1 to show the correct status "Stay"
Title: Re: DSC Alarm System plugin
Post by: binburra on May 05, 2012, 10:01:27 pm
I have just setup the 2ds with my alarm and it is working fine via the Eyez-On site but now I want to connect it to Vera.
Some questions
1 My 2ds is on the same local network as Vera so do I need to port foward or can I just use the plain internal IP address ?
2 Which DSC plugin do I download, the one in the app store via Mios ? I have firmware version 70 in the 2ds and I am running the latest beta on u15
Title: Re: DSC Alarm System plugin
Post by: strangely on May 06, 2012, 12:05:21 am
No need to port forward, just use you LAN address.

Plugin is here:

http://code.mios.com/trac/mios_dscalarmpanel/changeset/75/trunk?old_path=%2F&format=zip
Title: Re: DSC Alarm System plugin
Post by: binburra on May 06, 2012, 08:34:14 am
Ok thanks for the advice, I have the plugin loaded but is there anyway to keep the alarm code saved in the system so the arm-disarm works without going to the tools icon and puting it in each time. Nothing seems to change when I disarm a zone either. Does iVera app support this plugin ?
Title: Re: DSC Alarm System plugin
Post by: strangely on May 06, 2012, 09:52:17 am
Is there anyway to keep the alarm code saved in the system so the arm-disarm works without going to the tools icon and puting it in each time
You can create scenes to Arm and Disarm and save the PIN code in your scenes!

Quote
Nothing seems to change when I disarm a zone either.
If you are talking about the arm and disarm buttons on the zone sensor child devices, then these are not designed to disarm or bypass zones on your panel; they there for disarming the zones when they are used within scenes on Vera!

Quote
Does iVera app support this plugin ?
Not sure, but you may want to post that question in the remote control section here as I don't have the app:
http://forum.micasaverde.com/index.php/board,11.0.html

There are two or three other apps that do support Alarms though!
Title: Re: DSC Alarm System plugin
Post by: strangely on May 06, 2012, 09:56:14 am
@guessed, would it be possible to add in support of PIN storage? I know there is risk associated with this, but it was there in the original version, and there's now been a couple of requests to add this. I think its no worse than people creating scenes, and so long as we put a big disclaimer somewhere about the risks (PIN potentially be forwarded to MCV's servers), then that should cover it perhaps?
Title: Re: DSC Alarm System plugin
Post by: guessed on May 06, 2012, 10:05:06 am
@strangely,
I specifically avoided storing the PIN as there is no way to adequately secure that from being delivered to the MCV servers.  This was also consistent with the Panel APIs themselves, which often provide PIN-less arming (as an option) but always required a PIN for Disarm.

Folks that want to store the PIN have the option of creating a Scene, where they (not the plugin) take an explicit action/choice to go that route.



Oh, btw, can you update the wiki-doc to make the changes oTi@ lists above?
Title: Re: DSC Alarm System plugin
Post by: markg on May 06, 2012, 12:01:33 pm
Does anybody know if the issues with the 2ds have been worked out yet?

I recently switched out my security panel with a 864 and a rfk keypad along with a 2ds module.  I bought a new Vera lite and have loaded the rev 75 files for the plugin.  I am getting the same strange disconnect after a few minutes.  If you edit anything or reboot the unit it will work for a couple minutes again and then I get a password error and it stops.  I see everything working in the log when I reload and the password on the 2ds is default so that is fine.  I can only see the zone status for a few minutes, it will not arm even though I changed the false value to disarm in the advanced options.  I took the time to read this entire 45 page post so I wouldn't waste anybody's time but should I just hook the it100 instead? It seems like this might be more stable and I have a new one sitting here anyway?

Thank you to all who have contributed to this, there is a lot of good info here, especially from @gue ssed and @strangly.
Title: Re: DSC Alarm System plugin
Post by: guessed on May 07, 2012, 01:29:21 am
@markg,
I'll send you a PM shortly with my Email address in it.  If you can Enable Verbose logging in MiOS, and then restart Vera, let it run for about 5-10 minutes and then send me the log I can look over it.

I'd like to see if you're seeing the same issue that some of the others here have experienced.
Title: Re: DSC Alarm System plugin
Post by: undertoe on May 07, 2012, 09:18:59 pm
Just wondering if anyone had any input on this? Is this normal behavior with a 2DS?

Yes and No.

currently I have a trigger for both "Partition 1 is armed Stay" or "Partition 1 is Armed" this triggers my Garage door to shut & Doors to be locked.

It works when i arm the system via Vera or Direct on the 2DS web interface.

It does not work if I arm from a keypad in my house somewhere. I also noticed from watching the logs that it almost stops "polling" the device. So like when I arm the system from 2DS web or from vera I see activity to/from DSC. But like if I arm from Keypad then nothing, Partition 1 doesn't update status in the UI either.

Is this normal functionality?

EDIT: So tried it after I posted, Armed from Keypad and did report ExitDelay, which I have never seen it do that.

50      05/01/12 22:19:31.319   luup_log:29: DSCAlarmPanel: debug processIncoming:: Command=656, Data='1', Checksum=D2 <0x2eb2d680>
50      05/01/12 22:19:31.322   luup_log:29: DSCAlarmPanel: debug Partition::Exit Delay in Progress 656 partition: 1 <0x2eb2d680>

Even though keypad says armed, Vera partition one says ExitDelay still. Then if i hit Reload in UI5 it refreshes the status of Partition 1 to show the correct status "Stay"
Title: Re: DSC Alarm System plugin
Post by: guessed on May 08, 2012, 11:01:20 am
There are two problems were tracking at the moment.

The first issue relates to any Network-connected device that goes 'offline' without notice.  In this case Vera will not detect the situation, and will not reconnect to it.  It'll silently stop updating the UI (etc).  There will no hints etc in the logs.  MCV is aware of this issue, and has committed to fix it, but hasn't specified a timeline.

Quote
http://bugs.micasaverde.com/view.php?id=2282

That said, I haven't seen the 2DS drop off the net 'un-anounced' recently.

The second issue relates to it disconnecting periodically because rebooting.  It's not clear what is causing this, as not everyone is seeing it.   This happens shortly after startup, but at semi-random points in the timeline, so the UI is updated, initially, but then not updated over time with zone changes.  A few users have submitted tickets to MCV to diagnose this, but I haven't seen anyone report back on the state.

This looks like this in the LuaUPnP.log file:
Code: [Select]
eg. 2012-04-21 17:54:55 - LuaUPnP Terminated with Exit Code: 139
Unfortunately, in my test rig, I don't see either of these cases, so there's some feeling that the situation may be triggered by something in the CT network environment.

Folks that are having their Vera reboot (139 code restarts above) should file tickets giants MCV to get their units diagnosed, as Vera should never SEGV.

All 2DS users should register with Envisalink so that automated firmware updates can be applied.  There are problems in the shipped versions that are addressed by these automated updates (as well as a few features)
Title: Re: DSC Alarm System plugin
Post by: undertoe on May 09, 2012, 07:07:01 am
Is this the log I should be watching? tail -f /var/log/cmh/LuaUPnP.log | grep DSC
what can I identify in the log output to determine my problem?

Is there maybe a command line i can run with a cronjob every 1 min to do what reload does in the UI but specifically just for the DSC devices to kind of wake it up?


There are two problems were tracking at the moment.

The first issue relates to any Network-connected device that goes 'offline' without notice.  In this case Vera will not detect the situation, and will not reconnect to it.  It'll silently stop updating the UI (etc).  There will no hints etc in the logs.  MCV is aware of this issue, and has committed to fix it, but hasn't specified a timeline.

That said, I haven't seen the 2DS drop off the net 'un-anounced' recently.

The second issue relates to it disconnecting periodically because rebooting.  It's not clear what is causing this, as not everyone is seeing it.   This happens shortly after startup, but at semi-random points in the timeline, so the UI is updated, initially, but then not updated over time with zone changes.  A few users have submitted tickets to MCV to diagnose this, but I haven't seen anyone report back on the state.

Unfortunately, in my test rig, I don't see either of these cases, so there's some feeling that the situation may be triggered by something in the CT network environment.

Folks that are having their Vera reboot (139 code restarts above) should file tickets giants MCV to get their units diagnosed, as Vera should never SEGV.

All 2DS users should register with Envisalink so that automated firmware updates can be applied.  There are problems in the shipped versions that are addressed by these automated updates (as well as a few features)
Title: Re: DSC Alarm System plugin
Post by: oTi@ on May 09, 2012, 07:16:24 am
That said, I haven't seen the 2DS drop off the net 'un-anounced' recently.
What happens after an automatic firmware push to the 2DS?
Title: Re: DSC Alarm System plugin
Post by: undertoe on May 09, 2012, 07:43:16 am
Don't really know how to do that. Is it on the local 2DS interface or EYEZ-ON?


That said, I haven't seen the 2DS drop off the net 'un-anounced' recently.
What happens after an automatic firmware push to the 2DS?
Title: Re: DSC Alarm System plugin
Post by: garrettwp on May 09, 2012, 07:59:29 am
See guessed post above. You need to make sure you are registered with eyez-on to get the automatic updates.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: undertoe on May 09, 2012, 09:16:51 am
Yea I did that before I even set it up with vera. my current firmware, anything special I have to do to enable automatic updates?

current firmware for 2DS: Firmware Version: 01.07.70
Also shows the TPI client as offline unless I hit reload in vera UI5

Anything I can do command line via cron to reload the DSC panel?
I was playing around with http://127.0.0.1:3480/data_request?id=action&DeviceNum=29&serviceId=urn:schemas-micasaverde-com:device:DSCAlarmPanel:1&action=Poll

I don't mind sending the 2DS back if the IT-100 works better with vera DSC plugin, what are your thoughts on that?

See guessed post above. You need to make sure you are registered with eyez-on to get the automatic updates.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on May 09, 2012, 09:30:34 am
Firmware pushes are automatic.  If the 2DS is on, and connected to eyez-on, it'll automatically update.

In older firmwares it did this by just dropping off the net un-announced.  This triggered one of the MiOS problems I list above so I asked that eyez-on fix that, and they did... within a few days.

All firmware upgrades now disconnect the client prior to updating the 2DS device.  Then they upgrade themselves, then they start listening for client connections again.  Since the 2DS gracefully disconnected, Vera is aware and is trying to reconnect during this period... These all fail, but show up in the logs.  Once the 2DS comes back up, after the upgrade, Vera will reconnect very quickly (it's retry interval is very short) and it'll get the signal to re-authenticate... Which it will do, then things just carry on.

When I was looking closely at this, I was using a packet sniffer to capture/view all of the relevant traffic, and I validated it's correctly resetting the client in all newer firmwares.

That said, I haven't seen the 2DS drop off the net 'un-anounced' recently.
What happens after an automatic firmware push to the 2DS?
Title: Re: DSC Alarm System plugin
Post by: guessed on May 09, 2012, 09:34:02 am
That's the correct log file.

If you're experiencing the problem I describe above, please submit a ticket to MiOS so they can diagnose and fix their issues.

Is this the log I should be watching? tail -f /var/log/cmh/LuaUPnP.log | grep DSC
what can I identify in the log output to determine my problem?

Is there maybe a command line i can run with a cronjob every 1 min to do what reload does in the UI but specifically just for the DSC devices to kind of wake it up?
Title: Re: DSC Alarm System plugin
Post by: guessed on May 09, 2012, 10:06:10 am
@Brientim,
Did support work your ticket?

Already done. Ticket allocated to mcvflorin
Title: Re: Re: DSC Alarm System plugin
Post by: garrettwp on May 09, 2012, 10:49:04 am
Yea I did that before I even set it up with vera. my current firmware, anything special I have to do to enable automatic updates?

current firmware for 2DS: Firmware Version: 01.07.70
Also shows the TPI client as offline unless I hit reload in vera UI5

Anything I can do command line via cron to reload the DSC panel?
I was playing around with http://127.0.0.1:3480/data_request?id=action&DeviceNum=29&serviceId=urn:schemas-micasaverde-com:device:DSCAlarmPanel:1&action=Poll

I don't mind sending the 2DS back if the IT-100 works better with vera DSC plugin, what are your thoughts on that?

See guessed post above. You need to make sure you are registered with eyez-on to get the automatic updates.

- Garrett

I use the it100 and has been rock solid. I have the 2ds wired to the panel but not tied into any of my Vera units. When I get time, I'll configure it on my Vera lite test unit. My it100 is on my Vera 3.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: Brientim on May 09, 2012, 02:33:28 pm
@Brientim,
Did support work your ticket?

Already done. Ticket allocated to mcvflorin

No the ticket is still open. Ticket allocated to MCVFlorin 26 Apr but not progressed. I have left the unit alone since then to enable them to investigate.

Since firmware 70 was pushed, it is more stable but still the intermittent disconnections.
Title: Re: Re: DSC Alarm System plugin
Post by: undertoe on May 09, 2012, 07:51:01 pm
So how do you have the IT100 connected to vera?

Serial 2 USB / ethernet / wifi ?


I use the it100 and has been rock solid. I have the 2ds wired to the panel but not tied into any of my Vera units. When I get time, I'll configure it on my Vera lite test unit. My it100 is on my Vera 3.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: undertoe on May 09, 2012, 08:00:43 pm
@guessed thanks for your help.

Should I just say my DSC panel plug in is not updating the status? What is the proper terminology to describe what i am having to support? Sorry for all the questions
vera is still very new to me.

That's the correct log file.

If you're experiencing the problem I describe above, please submit a ticket to MiOS so they can diagnose and fix their issues.

Title: Re: DSC Alarm System plugin
Post by: garrettwp on May 09, 2012, 09:31:27 pm
I have it attached to a wiznet ethernet board which is connected to my network.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: oTi@ on May 10, 2012, 01:07:54 am
All firmware upgrades now disconnect [...] Which it will do, then things just carry on.
Thanks for the confirmation @guessed. I had tested with forced reboots of the 2DS and see the same interactions you describe for a firmware push.

Thing is, last week when I looked at the TPI status and saw it was disconnected, I also noticed build 70 had been pushed. Same thing tonight with build 72. But of course that may just be coincidence, and certainly not the only trigger if it were one.

In fact, I just now was doing a bunch of reboots again and they all seemed to come back ok, but then the last time, letting it sit for less than 5 minutes, I noticed the TPI status going to disconnected. The (same) socket on Vera was still open and any subsequent reboot of the 2DS goes undetected; it requires a Lua restart to get things to sync up again. That is, consistent with the silent disconnect scenario.

Quote
When I was looking closely at this, I was using a packet sniffer to capture/view all of the relevant traffic, and I validated it's correctly resetting the client in all newer firmwares.
I'll see if I can set something up.
Title: Re: DSC Alarm System plugin
Post by: guessed on May 10, 2012, 02:05:45 am
The fail safe for any socket endpoint 'going away' is to use the native KeepAlive functionality.  This is a low level poll of sorts that detects death of a remote end and communicates it.

Vera has not enabled TCP KeepAlives, so ANY socket connected device that just goes away, for any reason, will not be detected.  Vera will hold the socket more or press forever (unless a write() is initiated, which will fail)

So every socket connected device on Vera has a real problem of not being detected.  They need to enable std TCP KeepAlives and all will be well.  Aaron indicated he'd do this, but not what rel it'd be in.
Title: Re: DSC Alarm System plugin
Post by: oTi@ on May 10, 2012, 07:42:08 am
They need to enable std TCP KeepAlives and all will be well.  Aaron indicated he'd do this, but not what rel it'd be in.
Precisely! FWIW, email 'reminder' sent to Aaron.
Title: Re: DSC Alarm System plugin
Post by: undertoe on May 10, 2012, 08:05:11 am
Sounds like my problem, I think I am going to just get a IT100 and solve the problem.

All firmware upgrades now disconnect [...] Which it will do, then things just carry on.
Thanks for the confirmation @guessed. I had tested with forced reboots of the 2DS and see the same interactions you describe for a firmware push.

Thing is, last week when I looked at the TPI status and saw it was disconnected, I also noticed build 70 had been pushed. Same thing tonight with build 72. But of course that may just be coincidence, and certainly not the only trigger if it were one.

In fact, I just now was doing a bunch of reboots again and they all seemed to come back ok, but then the last time, letting it sit for less than 5 minutes, I noticed the TPI status going to disconnected. The (same) socket on Vera was still open and any subsequent reboot of the 2DS goes undetected; it requires a Lua restart to get things to sync up again. That is, consistent with the silent disconnect scenario.

Quote
When I was looking closely at this, I was using a packet sniffer to capture/view all of the relevant traffic, and I validated it's correctly resetting the client in all newer firmwares.
I'll see if I can set something up.
Title: Re: DSC Alarm System plugin
Post by: undertoe on May 10, 2012, 08:17:09 am
for the serial cable from the IT100 to the Wiznet is it male to male or female to male?

I have it attached to a wiznet ethernet board which is connected to my network.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: garrettwp on May 10, 2012, 08:53:36 am
I have the wiznet directly attached to the it100 without a need for a cable. You'll need to remove the screw nuts from the wiznet. Or use a male to female serial cable.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: strangely on May 11, 2012, 03:21:33 am
Here are some pics of the new PTK5507 touchscreen if anyone is interested.

Aesthetically its a nice upgrade on the normal keypads, but as far as usage goes, I wont really know until maybe the weekend when I've had a chance to install it!
Title: Re: DSC Alarm System plugin
Post by: strangely on May 11, 2012, 03:25:13 am
The Box also...
Title: Re: DSC Alarm System plugin
Post by: garrettwp on May 11, 2012, 03:29:20 am
strangely,

How does it get it's power? I guess you were able to get it for the cheap price you mentioned to me?

- Garrett
Title: Re: DSC Alarm System plugin
Post by: strangely on May 11, 2012, 03:43:04 am
Power is supplied purely from the Keybus! :)  And yes I got it from Gemini in the end for $179; the prices there are even better than home security store! I just ordered a 1864 panel also for $53 with no tax or shipping including some other goodies like relays.

Would've had the LCD keypad fitted already if it wasn't for the fact I need to replace my old panel and reprogram! Was running out of zones on the old one, plus I'm going to start using the PGM outputs for a couple of things like Garage door control, and also scene triggering on Vera!
Title: Re: DSC Alarm System plugin
Post by: undertoe on May 11, 2012, 06:52:09 am
@strangely
wow that is really sweet! wish I had some extra $ for it. I bet it makes label programming really easy.

does anyone know if this will work on a    DSC RFK5500, my installer told me it wouldn't
http://www.homesecuritystore.com/p-1269-wt5500-dsc-alexor-2-way-wireless-lcd-keypad.aspx

I would like a wireless keypad for my system
Title: Re: DSC Alarm System plugin
Post by: oTi@ on May 11, 2012, 06:53:07 am
Here are some pics [...]
Nice! Picture with UI5 running on it expected by Sunday. ;) :P

[...] just ordered a 1864 panel also for $53 [...]
Curious to see what the current firmware is on it. Apparently, v4.6 will support 64 wireless zones with the RFK5564 keypad. (Don't know if a PTK5507 + 2 (external) wireless receivers would work.)
Title: Re: DSC Alarm System plugin
Post by: strangely on May 11, 2012, 12:49:18 pm
Curious to see what the current firmware is on it.
its 4.5
Title: Re: DSC Alarm System plugin
Post by: strangely on May 11, 2012, 02:29:32 pm
Another interesting product for those wanting to trigger scenes from their alarm panels based on cars passing by etc:

http://resolutionproducts.com/products/compatible-sensors/re-dsc-compatible-driveway-2/
Title: Re: DSC Alarm System plugin
Post by: strangely on May 11, 2012, 02:34:03 pm
Freeze, flood or excess heat detector:

http://resolutionproducts.com/products/compatible-sensors/re-dsc-compatible-home-disaster-sensor-2/
Title: Re: DSC Alarm System plugin
Post by: S-F on May 11, 2012, 03:41:57 pm
I wonder how well that driveway sensor works compared to the one in the lock/security forum recently. If you get it please give some reviews.
Title: Re: DSC Alarm System plugin
Post by: guessed on May 12, 2012, 04:48:14 pm
Another interesting product for those wanting to trigger scenes from their alarm panels based on cars passing by etc:

http://resolutionproducts.com/products/compatible-sensors/re-dsc-compatible-driveway-2/

It'll be interesting to know if/how DSC Sensors show up under the RFXtrx433 that you have.  Would provide an alternate way to integrate the sensor into the stack if it worked.  I particularly like the idea of a Driveway sensor like this, but they only make models for GE/Elk, DSC & 2GIG/Honeywell.
Title: Re: DSC Alarm System plugin
Post by: guessed on May 12, 2012, 04:54:49 pm
@guessed thanks for your help.

Should I just say my DSC panel plug in is not updating the status? What is the proper terminology to describe what i am having to support? Sorry for all the questions
vera is still very new to me.

That's the correct log file.

If you're experiencing the problem I describe above, please submit a ticket to MiOS so they can diagnose and fix their issues.


@undertoe,
I'll take a look at your logs first, and can give you the right wording for your ticket based upon the specific situation you're seeing.

Seems like MCV has gone silent again over fixing some of these core-platform bugs, so hopefully we can get a few user tickets in to apply some pressure.

I will PM you with my Email address, so you can send the verbose log of the startup-through-disconnect sequence.
Title: Re: DSC Alarm System plugin
Post by: strangely on May 13, 2012, 01:37:42 am
It'll be interesting to know if/how DSC Sensors show up under the RFXtrx433 that you have.  Would provide an alternate way to integrate the sensor into the stack if it worked.  I particularly like the idea of a Driveway sensor like this, but they only make models for GE/Elk, DSC & 2GIG/Honeywell.
Might be worth contacting the manufacturer to see if they have any plans to support other systems?! Either that or fit that DSC panel :D

I'm guessing that something like this might also do the trick if the RFXtrx supported it (or could be made to support it)
http://www.mcmelectronics.com/product/SAFETY-TECHNOLOGY-INTERNATIONAL-STI-34150-/82-13610

Sensor only:
http://www.mcmelectronics.com/product/82-13611&scode=GS401&CAWELAID=838522610
Title: Re: DSC Alarm System plugin
Post by: rwalker on May 15, 2012, 01:02:13 am
I just got 01.07.72 and now my Vera constantly shows disconnected.  It will not connect at all.  Maybe they changed something in the TPI?

Roy
Title: Re: DSC Alarm System plugin
Post by: rwalker on May 15, 2012, 01:21:49 am
I just got 01.07.72 and now my Vera constantly shows disconnected.  It will not connect at all.  Maybe they changed something in the TPI?

Roy

Well... I changed the EnableRemoteArm variable to arm (was set to stay) and now it works fine.  For some reason I can't "Stay Arm" my system (always like that).  Even when done from the keypad, the 2DS shows Away Armed.  Anyone else have this issue?

Thanks,
Roy
Title: Re: DSC Alarm System plugin
Post by: guessed on May 15, 2012, 01:56:30 am
I'll run my relay cycler against my 2DS 01.07.72 overnight to see if I get dropouts or not.  I needed to do this anyhow, to baseline for a Vera fix for one of the other problems we're seeing (referenced above)

Is the 2DS showing Stay on their portal, on the local web/status page or on Vera's dashboard?
Title: Re: DSC Alarm System plugin
Post by: Brientim on May 15, 2012, 03:32:47 am
Interesting: MCV closed the support ticket as resolved 10 May against Unit 2 (test bed).
I have not received any communications that is was resolved or nature of fault.

I have contacted EnvisaLink to request if they could put a trace on the unit to identify the root cause for the termination either confirm the enviromental issues (DNS etc) and they will be putting a seperate firmware to track the fault.
Unit 1 has all of a sudden became very slow and not responding correctly, so it is reset and move on.
It is ashamed I am changing thing around and resetting and maybe loosing the chance to trace what the real cause was.

Worked out issue with Unit 1, it was moved and USB was knocked. When I did some other stuff a while back with IR, I must of download SQBlaster and there were 2 hidden devices which were downloading plugin 188 that went not noticed. The swap file minimised the impact and once the usb was not there and the swap file not available it brought the system to a stand still.  Fixed.
Title: Re: DSC Alarm System plugin
Post by: guessed on May 15, 2012, 10:15:20 am
Brientim,
MCV has an internal build that puts in the TCP KeepLive flags that @strangely and I are testing, but that should be unrelated to the 'random crash during startup' issue you were experiencing.

'188 is a long standing issue, thought to be benign (but def annoying when you're reading logs).  MCV used to host this special interface plugin, but obsoleted it in UI5.  It's not really needed, but you cannot stop it from loading, it would be better if they stubbed it ... Then at least the messages would go away.
Title: Re: DSC Alarm System plugin
Post by: mcvflorin on May 15, 2012, 10:19:39 am
@Brientim,

You can find here how to get rid of plugin #188.
http://forum.micasaverde.com/index.php/topic,9052.msg59279.html#msg59279
Title: Re: DSC Alarm System plugin
Post by: strangely on May 15, 2012, 12:05:05 pm
@Brientim,

You can find here how to get rid of plugin #188.
http://forum.micasaverde.com/index.php/topic,9052.msg59279.html#msg59279
This worked briefly for me, but reappeared again after doing it and I still get the Plugin trying to download on LuaUPnp restart!
Title: Re: DSC Alarm System plugin
Post by: mcvflorin on May 15, 2012, 12:07:18 pm
@strangely

Did you delete all the devices? I've seen Veras with 3 or more SQ Remote devices.
Title: Re: DSC Alarm System plugin
Post by: strangely on May 15, 2012, 12:26:18 pm
Yep, will try it again anyway and give you feedback.
Title: Re: DSC Alarm System plugin
Post by: Brientim on May 15, 2012, 01:04:52 pm
Hi,

I knew about this issues from when UI5 went live. Unit 1 never get touched normally and is left to its own devices...
I had rectified the issue immediately and the main issue was that the usb was knocked out and therefore, the swap file was not available. Just took me a while to realise this and of course, the unit was for a time very slow and unresponsive. Lesson for the day - do move things around and if you do pay attention.

Two alternative process to identify SQblaster plugin as they were hidden devices - multiple device - 1for each ir port.
http://<IP Address>/port_3480/data_request?id=user_data&output_format=xml
http://<IP Address>:3480/data_request?id=lu_invoke

@strangely how is the new keypad? When should we expect the critical review. Mine arrived yesterday but other activities delay install. Just need watch the power noting the number of devices and will power from PC5204.

Have a great day.
Title: Re: DSC Alarm System plugin
Post by: strangely on May 15, 2012, 02:12:02 pm
I never got the chance to install mine as it was my daughters Birthday, and also we had guests staying. I'm away for the week now so wont get the chance until the weekend.

If I hadn't planned on swapping out my 1616 for a 1864 (along with some other changes) then I would've done it already, and am not looking forward to reprogramming!

I'm also worried about power draw with this thing, as It'll also be sharing with a few other devices, and I may also need a PC5204!
Title: Re: DSC Alarm System plugin
Post by: Brientim on May 16, 2012, 12:08:45 am
Brientim,
MCV has an internal build that puts in the TCP KeepLive flags that @strangely and I are testing, but that should be unrelated to the 'random crash during startup' issue you were experiencing.

@guessed,
I missed this; hopefully, this will be available in the near future. As always, I appreciate all the members help. 
Title: Re: DSC Alarm System plugin
Post by: Brientim on May 16, 2012, 12:46:53 am
If I wasn't hadn't planned on swapping out my 1616 for a 1864 (along with some other changes) then I would've done it already, and am not looking forward to reprogramming!
I'm also worried about power draw with this thing, as It'll also be sharing with a few other devices, and I may also need a PC5204!

You have 500ma from the panel and seeing the new keypad is 300ma in use; there isn't much scope for devices. The PC5204 will give you the extra power and adds the extra PGMs. However, another power supply and battery is required.

If you download from the panel, you can convert in DLS as as the 1616 and 1864 have the same programming structure; you should encounter any issues and then after changes them just push it back up. 



Title: Re: DSC Alarm System plugin
Post by: thomen on May 18, 2012, 01:54:26 am
Hi Guys,
sorry am very new to all of this.. just wondering how you'd hook some code up so that if a light isn't manually on at the switch and a motion sensor is triggered after dark, it'll turn a light on to a certain brightness? I was hoping to use the dsc plugin to get me access to my sensors to do motion automation.. is this part of what the plugin lets you do? and if so how do you target the individual sensors that are triggered by the alarm in code?

pardon my ignorance but i get the concept of a stock zwave device but the bridge between the alarm and vera seems like it may have  a trick or 4 to get it right..
thanks,
Tom
Title: Re: DSC Alarm System plugin
Post by: guessed on May 18, 2012, 03:40:31 am
You'll need to create a Scene with an Event based on the specific zone triggering, and the Command indicating to turn the light on (to a certain level).  This is done declaratively in Vera's UI.  All of the Zones are just motion sensor variants so they each look no different (in Vera) than a standard ZWave motion sensor.

Then you'll need Luup code in that scene defn that stops it running during the day (see luup.is_night()) and also stops it running (return false) if the light is already on (see luup.variable_get(...)).
Title: Re: DSC Alarm System plugin
Post by: markg on May 18, 2012, 02:13:16 pm
@guessed

Sorry I did not get that log file for the 2ds to you.  I did what was going on though.  With the 2ds at firmware 72 and the 75 files loaded on the vera lite for the dsc plugin it will work perfectly as long and you do not setup any notifications thru eyez-on.  I had zone followers turned on while I was out of town and so I could see when the neighbor kid was letting my dog out and everytime he would come over and the 2ds would send me a email that front door was open and the tpi session was closed.  If I reloaded the unit would work perfectly until he opened a door again and it sent me a email.  I love this module but have decided to put in a it-100 for now and everything works great. 

I just have one question for anybody that may know how to do this.  I am using the pgm outputs from my dsc 864 panel to open my garage doors and I am wondering if there is a way to set this up thru vera.  Right now I can log into the 2ds module and toggle the pgm output and it will open my garage door and I am just looking to add this into the system.  If anybody is wondering how I did this you can just put a rm-1 dsc relay or similar 12v dc relay with one side of the coil on aux+ on the panel and the negative on one of the pgm outputs.  When you trigger the pgm it basicly grounds the point activating the relay giving me the dry contact to open and close the garage door.  I have garage door contacts installed to monitor the doors position.
Title: Re: DSC Alarm System plugin
Post by: Brientim on May 18, 2012, 03:00:45 pm
As suspected, the issues I encountered we're environmental network problems and not the 2DS, Vera or plugin. It was a faulty switch. It was the switch connected to the router that was causing the fault and It wasn't apparent due to no other aspects of the network were encountering issues. I have removed that switch and it all functioning well.

Now to acknowledgements: both @guessed and support at Envisacor helped trace and identify the fault. Envisacor Support was very quick to assist and knowing this level of commitment to their product and their customers makes me very confident to state this is a very good product and they are right up there with support.

Thanks again @guessed.

@markg,

Have you submitted anything to Envisacor support?  You could connect both devices to you alarm at the same time whilst they investigate, and that way you still have all the other aspects available and the it100 would provide the connection to your Vera.
Title: Re: DSC Alarm System plugin
Post by: strangely on May 18, 2012, 06:00:21 pm
If you download from the panel, you can convert in DLS as as the 1616 and 1864 have the same programming structure; you should encounter any issues and then after changes them just push it back up.
I thought about doing this, but I was advised against it by one of the mods on the alarm support boards!

The other changes that I'm undertaking are to remove an RFK5501 keypad and fitting a stand-alone RF5132 wireless receiver instead, and would need to switch over the sensors to it anyway along with setting up some new zones, and also a hack involving wiring some PGMs to zone inputs (via relay's) so that I can trigger some scenes in Vera from the the PGM page off my PTK5507.
Title: Re: DSC Alarm System plugin
Post by: markg on May 18, 2012, 11:10:20 pm
@strangely, feel free to shoot any questions about programing the dsc panel my way,  i have been programming dsc panels for about 12 years now and pretty much now just about everything you would want to know about them.  I usually program the maxsys 4020 panels since they are more aimed towards commercial use but I have also done a bunch of power series panels.  I just recently replaced my 4020 with a 864 panel since homeseer is pretty much the only home automation software that supports them and I was not going down the microsoft windows route when I started this journey.  I am wondering why you are planning on using a separate wireless reciever?  I know that alot of people on the forums here talk about having problems with the it100 being at slot 8 and the rfk5500 also likes this slot but it is not a problem.  I just moved the rfk5500 to slot 1 and the wireless reciever takes slot 17 by default so by moving the keypad to 1 resetting module supervision and then broadcasting the labels pretty much works perfect.  It also sounds like you are going to do some work with getting the pgm's working, this is exactly what I am trying to do now.  I have my garage doors hooked up to them right now but the only way I can trigger them remotely is thru the 2ds module.  If you get this working I would be very interested on how to do it.

Title: Re: DSC Alarm System plugin
Post by: strangely on May 19, 2012, 12:36:47 am
The main reason I'm cutting over to using the RF5132 instead of the combo keypad and receiver (RFK5501) is due to the fact that the keypad is currently located next to my panel in our upstairs closet (quite far from the wireless sensors), and recently I started to get interference from some a weather station I bought :( As I don't use the other keypad (its a non alpha model), and don't really have anywhere else for it to go (with a closer range to the sensors), the only option that was more centrally located, and in reach of the keybus wiring, would have been in my Garage; now for obvious reasons, I don't want to install it there, and therefore elected for a separate wireless receiver instead that could be located there in the garage.

I also have power considerations to worry about since I'm now about to replace my main keypad (PK5500) with an PTK5507, and since I also have an IT100, a 2DS and the wireless receiver, this takes me to about 480mA total (near the limit) and using the RFK5501 would've taken me over the 500mA limit.

The other main reason for updating my 1616 panel with a 1864 is to gain extra zones (I'm near the limit on 15 presently) and also the two extra PGM outputs.

I'm going to wire one PGM (connected via the keypad PGM) via a relay to also control my garage door, and then probably use the the four on the panel wired to zones (via relays again), so that I can use the PGM control output to trip the zone inputs (configured as null zones), so that I can in turn use those zones to trigger Vera Scenes. This approach allows me to either use DSC keyfobs as scene controllers, or use the the nice PGM control screen in the PTK5507 to trigger some of my commonly used scenes! I'm quite good with the DLS software so should be OK, just need to work out the PGM settings a bit later once I have the basics reprogrammed again.

As far as triggering the PGM's from Vera, the plug-in doesn't currently support this, and also its possible that the functionality could be added, It would have to be done by @guessed, and I know the last time he looked into it, he wanted to perhaps support it in a standard way that could be adopted across all the alarm panels (mainly DSC and his Paradox system); however IIRC, it didn't look easy to do due to the panel differences I think!

I'd also like to ditch the modified Zwave appliance module that I use for door control as I've had a couple of hiccups with this where sometimes the door started to close and then stopped (maybe relay contact bounce), and one other time where the appliance module never switched off again, and stopped my wife from even being able to use the regular door controls due its contacts being grounded! Luckily I figured out what had happened pretty quickly (from a hunch when she called me) and was able to fix it via cp.mios.com by turning the appliance module off!
If I figure out a way to get it to work without a plugin update, or some sort of hackery, then I'll post it here... although I imagine it should be possible to do with some LUUP code in a scene via the eyez-on portal perhaps!

Title: Re: DSC Alarm System plugin
Post by: markg on May 19, 2012, 10:49:21 am
@strangely,  if you are having wireless issues with dsc sensors I would first try replacing the batteries and then the sensor since dsc has had a lot of issues with older wireless devices.  On older wireless receivers they would not report low battery conditions unless you programmed in all 16 wireless keys to the receiver and even then it was still sometimes did not work.  The newer 5132 reciever does not have this problem anymore as long as you use a version 4.5 or newer main board.  You also cannot use the dls2002 anymore with the newer power series panels as dsc does not provide drivers for them anymore, dls4 is the only option. 

Many of your posts here have helped me in journey of installing my system so to you only I will get any security parts you may need for dealer cost.  this is usually 30 to 40 percent cheaper than the internet prices.  I got my 2ds for only about $60 and another example is the wireless door contacts that are normally 30 I get for 19.  I also have a few extra door contacts and motions left over if you would like me to ship you one to see if it helps with the wireless issue you are having.
Title: Re: DSC Alarm System plugin
Post by: strangely on May 20, 2012, 09:49:38 am
Thanks @markg, that's good info! The sensors are about a year and a half old, and I tested the batteries when all this started (exactly the time I bought the weather station), and they were around 3V still, (although I haven't tested them on my 3 smokes yet!). Touch wood, I haven't had any wireless issues now for about 2 weeks now since moving its sensors round to the other side of the house where they are much further away!

I've always used DLS IV so hopefully I'm good to go now to program; other than a bad serial cable of course!

New panel is in; also had some further complications as I had to move a zone to a spare wire elsewhere due to these PTK5007 keypads not supporting Zones/PGMs anymore! Hopefully will have it all programmed later once I get the new serial cable.

Also thanks for the offer of the discount, I'll bear that in mind for the future!
Title: Re: DSC Alarm System plugin
Post by: oTi@ on May 20, 2012, 10:05:19 am
It was a faulty switch.
Very interesting. Did they explain (the technical background of) what was wrong with the switch?
Title: Re: DSC Alarm System plugin
Post by: Mikey on May 21, 2012, 12:07:42 am
Anyone ever seen this in their log before...

Code: [Select]
LuaInterface::CallFunction_Startup-2 device 43 function alarmStartup failed DSCAlarmPanel with return false
This happens after any refreshing or power cycling of the Vera (running .346).

Thanks, in advance,
-Mike

P.S. Earlier in the log, there appears to be a memory leak of some sort at startup...
Code: [Select]
luup_log:43: DSCAlarmPanel: Running Network Attached I_DSCAlarmPanel1.xml on 192.168.1.50:5000 Device# 43, id  <0x402>
ZZZ-POLLING H1,C1,/1/1 __LEAK__ this:266240 start:266240 to 0xb4d000 <0xc04>
Title: Re: DSC Alarm System plugin
Post by: guessed on May 21, 2012, 02:17:31 am
When startup returns false explicitly it usually means that some aspect of the startup processing failed.  There should be more details in the log file just around where that occurred, or in the UI itself.

There are all sorts of points where Vera will log potential memory leaks, I don't usually bother with these unless you're running into short term reboot situations due to low memory (it has many, slow leaks)
Title: Re: DSC Alarm System plugin
Post by: Brientim on May 21, 2012, 04:55:12 am
It was a faulty switch.
Very interesting. Did they explain (the technical background of) what was wrong with the switch?

@oTi,
Yes they did contact me and details provided helped identify the nature of fault.
Extract from Envisacor support
"I was just looking at your log and you can see that about 80% of the TPI closures are due to too many network retries, while about 20% are in response to the Vera closing the socket. The retries are not a sign that the Vera rebooted as it would send a RST packet and I'd log this as a socket abort."

Whilst they were monitoring I was in the process of testing the various aspect of the network as a process of elimination which accounts for the 20%. Without going through the network topogrophy that is here (it is all Cisco and Linksys), when I removed one of the switches, the error disappearred. As I previously stated, it wasn't apparent, because I did not notice any other incidents from other items on the same switch. It is still not completely finished as it also allowed me to identify another limitation that was being encountered with the router and that will be replaced in the next week by my service provided. It was perfect timing as it ran out of warranty next week and a few google searches identify some other issues with modem.       

I have noticed a different issue which also result in a the non updating of zones.  If DCHP is enable on my Vera 2, it will not perform no autonomous updates. If I disable both wireless and DCHP, it seems to work fine, but each restart of luup, they are reset and both enabled.... I need to be able to totally exclude them and therefore, can you permantly (script) disable DCHP, Wireless and DNS? 
Title: Re: DSC Alarm System plugin
Post by: Mikey on May 22, 2012, 02:02:41 am
When startup returns false explicitly it usually means that some aspect of the startup processing failed.  There should be more details in the log file just around where that occurred, or in the UI itself.
Indeed...

Code: [Select]
06 05/22/12 0:54:23.969 Device_Variable::m_szValue_set device: 43 service: urn:micasaverde-com:serviceId:HaDevice1 variable: CommFailure was: 1 now: 1 #hooks: 0 upnp: 0 v:0x8acb88/NONE duplicate:1 <0x402>
01 05/22/12 0:54:23.970 LuaInterface::CallFunction_Startup-2 device 43 function alarmStartup failed DSCAlarmPanel with return false <0x402>
06 05/22/12 0:54:23.971 Device_Variable::m_szValue_set device: 43 service: urn:micasaverde-com:serviceId:HaDevice1 variable: CommFailure was: 1 now: 1 #hooks: 0 upnp: 0 v:0x8acb88/NONE duplicate:1 <0x402>
01 05/22/12 0:54:23.973 LuImplementation::StartLua running startup code for 43 I_DSCAlarmPanel1.xml failed <0x402>
01 05/22/12 0:54:26.926 Mongoose XXX-mg_stop1 0x9257a0 1 1 <0x400>
01 05/22/12 0:54:28.950 Mongoose XXX-mg_stop2 0x9257a0 2 1 <0x400>
01 05/22/12 0:54:28.951 Mongoose XXX-mg_stop3 0x9257a0 2 1 <0x400>
01 05/22/12 0:54:28.952 Mongoose XXX-mg_stop4 0x9257a0 10771896 1 <0x400>
01 05/22/12 0:54:31.090 Main WatchDogRoutine: blocked - terminating 1 <0x6416>
02 05/22/12 0:54:31.133 Dumping 2 locks <0x6416>
02 05/22/12 0:54:31.133 finished check for exceptions <0x6416>
02 05/22/12 0:54:31.134 OL: (0xa1ed50) (>2857) ThreadedClass IOPort.cpp l:88 time: 12:53:52a (39 s) thread: 0x5c18 Rel: Y Got: Y <0x6416>
02 05/22/12 0:54:31.135 finished check for exceptions <0x6416>
02 05/22/12 0:54:31.135 OL: (0xa1ed50) (>3401) ThreadedClass ThreadedClass.cpp l:49 time: 12:54:29a (2 s) thread: 0x400 Rel: Y Got: Y <0x6416>


2012-05-22 00:54:31 - LuaUPnP Terminated with Exit Code: 137

---------------exited-------------

...it looks like I'm added to the list of folks who have the Lua engine crash.  >:(
Title: Re: DSC Alarm System plugin
Post by: guessed on May 22, 2012, 10:39:27 am
@Mikey,
Do you have the lines before that occurred?  It looks like it wasn't able to connect for some reason.  Verbose logging should be enabled also, it looks like you already have it but just in case you don't...
Title: Re: DSC Alarm System plugin
Post by: Mikey on May 22, 2012, 10:46:56 am
@Mikey,
Do you have the lines before that occurred?  It looks like it wasn't able to connect for some reason.  Verbose logging should be enabled also, it looks like you already have it but just in case you don't...
@guessed, I'll check it out when I get back to the ranch. 

As a side note, this has all piqued my interest as I had previously given up on my debugging efforts.  As fate would have it, and without me immediately noticing it, the Vera did manage to communicate with the IT100 (showed an LCD text update ~24 hours old by the time I got to viewing it, anyway).  All of this recent woe, then, is simply trying to get Vera to re-connect, but as shown above, the errors in the Lua script persist now.  ???
Title: Re: DSC Alarm System plugin
Post by: strangely on May 23, 2012, 12:33:23 am
So I finished the upgrade of my Alarm Panel and Keypad, and with the help of the programmable outputs of the alarm panel, I now have scene control from the Keypad!

Here's a quick video I did of it in action which showcases the new DSC PTK5507 keypad:

https://skydrive.live.com/redir?resid=E190908F1B6D2FE3!393

A bit overkill for a scene controller, but worth the effort I think!
Title: Re: DSC Alarm System plugin
Post by: garrettwp on May 23, 2012, 02:08:46 am
How is the new keypad? Worth the extra cost?

- Garrett
Title: Re: DSC Alarm System plugin
Post by: strangely on May 23, 2012, 10:24:59 am
Well it looks nice, and a prefer the style of it over the older keypads, however given the cost I'm not sure its worth the upgrade unless looks are important and you want the WAF etc!

As far as the scene control that I've implemented, It really like it but its nothing that couldn't be accomplished with a standard keypad by pressing *71, *72, *73 or *74 etc.

Programming of certain functions looks to be lot easier, but then again I mainly used DLSIV for the panel swap so I don't know if it makes a huge difference!

I mainly use a combination of scenes, key fobs or the phone to Arm and Disarm, so again its likely a bit of waste really! Overall I'm quite pleased with it, but I guess if you could find a good tablet and make a nice clean wall mount with included power etc, then that might be a better solution!
Title: Re: DSC Alarm System plugin
Post by: strangely on May 24, 2012, 01:24:54 am
Nice! Picture with UI5 running on it expected by Sunday. ;) :P

Sorry a bit later than expected, but here's a picture with UI5 running on it ;)
Title: Re: DSC Alarm System plugin
Post by: garrettwp on May 24, 2012, 02:09:37 am
Haha, Using the picture frame feature I see.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: strangely on May 24, 2012, 02:13:53 am
I wouldn't know what you are talking about  8)
Title: Re: DSC Alarm System plugin
Post by: oTi@ on May 24, 2012, 08:44:27 am
Sorry a bit later than expected, but here's a picture with UI5 running on it ;)
;D LOL. Alright, YouTube video showing off UI5 running on it interactively expected by next Sunday then. :)

Thanks for the pic!
Title: Re: DSC Alarm System plugin
Post by: strangely on May 24, 2012, 01:08:52 pm
Let me see what I can do ;)
Title: DSC Alarm System plugin
Post by: Raynaldg on May 29, 2012, 12:19:58 pm
What is the last status about the 2DS sync problem with Vera ?
A fix is available ?

😊
Title: Re: DSC Alarm System plugin
Post by: guessed on May 29, 2012, 12:40:00 pm
MCV has a special build, that he's asked the Beta team to trial, that enables TCP Keep-Alive processing for all Plugin connections.  This has not yet made it into a formal build for general consumption.

The 2DS lads are looking at adding the corresponding part of the TCP Keep-Alive processing into their device but, in the meantime, I've enabled something in the 2DS (Timestamp Broadcast) that, when combined with MCV's TCP Keep-Alive fix, is effectively a work-around for the missing functionality.

With those two parts together, if the connection is dropped for any reason it will be detected will be re-established.  The outer period for this detect-and-correct will be 4 minutes, with resulting messages lost in that period when it occurs.


We're still collecting data on why these connections are dropping in the first place.  Both oTi@ and @strangely are performing TCP network captures to see if we can discover a pattern.  Of course, it still doesn't happen in my setup ;-)

In @Brientim's case, the loss was due to a faulty switch unit.



What is the last status about the 2DS sync problem with Vera ?
A fix is available ?
Title: DSC Alarm System plugin
Post by: Raynaldg on May 29, 2012, 01:04:47 pm
@guessed : Thank you for your status clearly stated!
I'm available to test the fix if you need to.

😉
Title: Re: DSC Alarm System plugin
Post by: guessed on May 29, 2012, 04:48:27 pm
@guessed : Thank you for your status clearly stated!
I'm available to test the fix if you need to.
One thing that would help us, for anyone with continuing problems, is to outline:

Problems often get fixed over time, so getting a periodic update from users, with the above information, helps narrow down the research efforts.

My goal is to get the latest source version "blessed" (by @oTi@, @strangely ad @garrettwp) and then push it to apps.mios.com for UI5 2DS or IT100 users.  There are still some problems with it that would impact UI4/2DS users (but UI4/IT100 users won't see that)
Title: Re: DSC Alarm System plugin
Post by: undertoe on May 30, 2012, 08:46:25 am
I previously got the 2DS working in Vera UI5. Due it dropping and not really working I decided to give the IT100 with the Wiznet Ethernet adapter.

I am getting "Lua Failure Lua Failure" for the panel device. I have ip:5000 set along with the interface IT100. Plus is setup the wiznet according to screenshots in previous posts.
able to ping wiznet. what am i missing?

Couple questions, should i be installing from Mios App center or should i be downloading and uploading files?
Title: Re: DSC Alarm System plugin
Post by: guessed on May 30, 2012, 12:46:36 pm
I previously got the 2DS working in Vera UI5. Due it dropping and not really working I decided to give the IT100 with the Wiznet Ethernet adapter.

I am getting "Lua Failure Lua Failure" for the panel device. I have ip:5000 set along with the interface IT100. Plus is setup the wiznet according to screenshots in previous posts.
able to ping wiznet. what am i missing?

Couple questions, should i be installing from Mios App center or should i be downloading and uploading files?
@undertoe,
I just sent you a PM with my Email details in it so you can send me a complete log, from startup through error, for the IT100.  This will let me see what's going on.

I forgot to mention in the PM that you should have Verbose logging enabled when you send it over, since there are sometimes details in the Verbose logs that give better clues.
Title: Re: DSC Alarm System plugin
Post by: guessed on May 31, 2012, 01:28:04 am
For the issue @undertoe's outlined above, we diagnosed a bunch in the background, and he was able to determine a misconfig of the wizNET in the deployment. 

Looks like he's operational now, and is going to provide feedback if it looses connectivity.
Title: Re: DSC Alarm System plugin
Post by: strangely on May 31, 2012, 01:36:35 am
I think we should start selling pre-configured wiznets :)
Title: Re: DSC Alarm System plugin
Post by: guessed on May 31, 2012, 01:42:06 am
It's definitely easier to config a 2DS, we just need the data to work out why/where things cause it to disconnect.
Title: Re: DSC Alarm System plugin
Post by: strangely on May 31, 2012, 01:53:14 am
By the way, mine was working fine for a few days since a reboot of my V.lite (after some hiccups the other day), I then go away for a few days with work, and now I'm getting a silly amount of TPI reconnects again.

I have tcpdump installed now, so will take a look when I get home.
Title: Re: DSC Alarm System plugin
Post by: Brientim on May 31, 2012, 05:10:42 am
@guessed. Feedback on observations using the same network infrastructure, UI but different units. 

I had the Cisco router replaced  and I have also finally given received my Vera 3 (a present from my wife).
Even after all managed switches were removed and replaced with a non-managed switches, I was still receiving disconnections but haven't had any time to look at this. After switching out the Vera 2 and replacing it with the Vera 3 two days ago, there has not been one disconnection other than restarts as a result of installing apps etc.

a) a summary of each of the problems they observe - Nil with (Vera3)
b) what UI/Vera version they're running - Vera3 UI5 firmware 1.5.346
c) what their Network topology they're using - Configuration - Netgear G3100 router with 4 non-managed (removed all managed switches).   
d) whether it's a 2DS or a [Network-enabled] IT100 they're using - 2DS

a) a summary of each of the problems they observe
    (i) intermittent disconnections (TPI closures are due to too many network retries - Vera2)
    (ii) no autonomous updates (Vera2).
b) what UI/Vera version they're running - Vera2 UI5 firmware 1.5.346
c) what their Network topology they're using - Configuration -  No change to above.   
d) whether it's a 2DS or a [Network-enabled] IT100 they're using - 2DS

I have also installed Ping Sensor to watch the 2DS connection. No issues encountered with Vera 3.
Title: Re: DSC Alarm System plugin
Post by: undertoe on May 31, 2012, 06:43:12 am
Just need to get the right instructions up there :)
I followed the settings based on this post and the wiki.
http://forum.micasaverde.com/index.php/topic,5154.msg34061.html#msg34061
which is not accurate.

I would be more than happy to revise the IT100/ wiznet setup instructions with screenshots for UI5.

@guessed thanks for the push in the right direction

I think we should start selling pre-configured wiznets :)
Title: Re: DSC Alarm System plugin
Post by: strangely on May 31, 2012, 05:14:17 pm
...interesting, so it didn't work when you had 0.0.0.0 as the server IP? Was that the only difference? Odd how the same setup has worked for everyone else, although I see we have a firmware difference, so I guess that could be on reason (although I doubt it).

It seems stupid that you'd be able to have this setup under DHCP, and then if your address ever changed (assuming that you hadn't reserved the address), that you would then have to match the server IP to the that of the assigned address! I think it was 0.0.0.0 and port 0 by default, and I would imagine the device should automatically set itself up when configured like this to avoid address changes etc. (even though all that use should have static addresses anyway).

I'll change mine anyway so that the server field in mine matches the local IP also; If it still works then I'll update the Wiki.
Title: Re: DSC Alarm System plugin
Post by: strangely on May 31, 2012, 05:31:29 pm
Seems to work still with the if I manually add the server IP.
Title: Re: DSC Alarm System plugin
Post by: mpierce on June 01, 2012, 12:18:22 am
I also was never able to get the 2DS working properly.  I setup the IT100/Wiznet about a week ago and have had no issues since then.
Title: Re: DSC Alarm System plugin
Post by: guessed on June 01, 2012, 12:25:15 am
@mpierce,
Definitely interested in the details of what didn't work, in a form/detail similar to @Brientim's excellent response above, so we can get to the bottom of fixing whatever doesn't work....  The 2DS team is very responsive when we're able to give them quantitative data about the problems we find
Title: Re: DSC Alarm System plugin
Post by: Brientim on June 01, 2012, 02:03:54 am
@Brientim's excellent response above, so we can get to the bottom of fixing whatever doesn't work....  The 2DS team is very responsive when we're able to give them quantitative data about the problems we find

@guessed, I neglected one critical element of testing on Vera 2.Repeatable and confirmed on two different my two different Vera 2 which I had previously mentioned "I have noticed a different issue which also result in a the non updating of zones.  If DCHP is enable on my Vera 2, it will not perform autonomous updates. If I disable both wireless and DCHP, it seems to work fine, but each restart of luup, they are reset and both enabled"

I reduce the number of equipment on an isolated test and the above was still occurring and did not affect performance of the 2ds and the results previously stated were still occurring. Due to travel and other work commitments, I will not get much time to look at this.
Title: Re: DSC Alarm System plugin
Post by: undertoe on June 01, 2012, 08:21:55 am
I second this, I started with the 2DS and now have an IT100/Wiznet and it works flawless. Motion  sensor and door sensor response time is almost instant.
Panel status updates instant. I am keeping both as a backup since the 2DS has its own nice external interface for the panel. But I would recommend anyone
to just save the hassle and go with the IT100/Wiznet.

SO my big question is what is everyone housing the IT100 and wiznet in? I have my 2DS in a nice project box from radio shack but the IT100 + Wiz is too big.
Anyone have any good suggest or maybe even pictures?

I also was never able to get the 2DS working properly.  I setup the IT100/Wiznet about a week ago and have had no issues since then.
Title: Re: DSC Alarm System plugin
Post by: oTi@ on June 01, 2012, 08:47:49 am
[...] housing the IT100 and wiznet [...] Anyone have any good suggest or maybe even pictures?
Example (http://forum.micasaverde.com/index.php/topic,5154.msg51954.html#msg51954).
Title: Re: DSC Alarm System plugin
Post by: undertoe on June 01, 2012, 08:51:55 am
I was looking more for an enclosure, but thanks for the response.

[...] housing the IT100 and wiznet [...] Anyone have any good suggest or maybe even pictures?
Example (http://forum.micasaverde.com/index.php/topic,5154.msg51954.html#msg51954).
Title: Re: DSC Alarm System plugin
Post by: garrettwp on June 01, 2012, 09:27:49 am
What is wrong with using the dsc enclosure? I have mine setup the same in the post above. Everything is in one box.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: undertoe on June 01, 2012, 03:58:42 pm
One word, I am anal and have a huge wall panel with home networking, router, firewall, switch, cable tv distribution, security system, VOIP network, camera dvr all
organized in one big panel. I don;t like to just leave a circuit board in there :) Plus it helps me sleep better at night have a nice little box to have it fit in.


What is wrong with using the dsc enclosure? I have mine setup the same in the post above. Everything is in one box.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: strangely on June 01, 2012, 04:34:32 pm
One word, I am anal and have a huge wall panel with home networking, router, firewall, switch, cable tv distribution, security system, VOIP network, camera dvr all
organized in one big panel. I don;t like to just leave a circuit board in there :) Plus it helps me sleep better at night have a nice little box to have it fit in.

You'd have a bit of a shock if you saw my panel then! Maybe you can sort mine out for me!? :) In my defense I'm always changing too much stuff to warrant keeping it all tidy!

One question though, wouldn't your alarm circuit board be open in there though, or have you boxed that up? 
Title: Re: DSC Alarm System plugin
Post by: Brientim on June 01, 2012, 05:34:39 pm
One word, I am anal and have a huge wall panel with home networking, router, firewall, switch, cable tv distribution, security system, VOIP network, camera dvr all
organized in one big panel. I don;t like to just leave a circuit board in there :) Plus it helps me sleep better at night have a nice little box to have it fit in.

Keep it nice. No need to be say things like that. My wife might read this and get me to do the same....
Title: Re: DSC Alarm System plugin
Post by: guessed on June 01, 2012, 09:18:18 pm
... sounds like an Open-the-Kimono challenge to post pictures of the contents of their wiring setups.

I may create another thread just for that, as it'll be interesting  8)
Title: Re: DSC Alarm System plugin
Post by: strangely on June 01, 2012, 09:57:31 pm
... sounds like an Open-the-Kimono challenge to post pictures of the contents of their wiring setups.

I may create another thread just for that, as it'll be interesting  8)

You better get those "dangling Vera's" sorted out then :)
Title: Re: DSC Alarm System plugin
Post by: guessed on June 01, 2012, 10:22:23 pm
Now what fun would that be 8).

They'll stop dangling there when vendors make either a nice looking unit, or an externalizable antenna...

BTW: I opened a new thread for the more general closet-beauty-contest and pictures
    http://forum.micasaverde.com/index.php/topic,10747.0.html

 
You better get those "dangling Vera's" sorted out then :)
Title: Re: DSC Alarm System plugin
Post by: guessed on June 07, 2012, 02:12:56 am
Just to give a quick update to people that are following along on the resolution of the 2DS issues. 


a) Non updating of zones
Today, oTi@ has been on the batting plate, providing the 2DS engineers with raw Network capture data showing Zone Open/Close events not being reported back to Vera and, eventually, followed by a loss of the TPI Connection.

In this case, some theories have been formed based upon the [tcpdump] data oTi@ collected from his isolated setup, and they all seem likely candidates for both the Zone event not being sent, along with the eventual connection drop.  The 2DS engineers are working on something to further validate their theories, so hopefully we'll see/test that shortly to see if it addresses the problem (at which point, we can discuss it in more details)

b) TimeStamp Broadcast bug...
@strangely identified a situation where the TimeStamp Broadcast, that I'd recently added, would stop working.  This "fix" goes hand-in-hand with the yet to be released TCP Keep-Alive patch for MiOS/UI5.  Anyhow, I added more code to reset the TimeStamp Broadcast for the 2DS unit if it's reconnected and @strangely is currently testing this code for a few days.

We have no ETA on when the TCP KA patch for MiOS will be made more generally available.
Title: Re: DSC Alarm System plugin
Post by: JeffNY on June 07, 2012, 12:34:07 pm
Hey Guys,

I just wanted to say Thank You to you guys who are working on this. I don't have a Vera yet, but I replaced my old ADT system with a new DSC 1832 and a 2DS board, which works great and I love. But getting the 2DS working well with the Vera would be awesome ;D I hope to have a Vera soon...

Thanks again,
Jeff
Title: Re: DSC Alarm System plugin
Post by: strangely on June 08, 2012, 02:04:19 am
48 hours + up and running without a single TPI disconnect/reconnect since the latest revisions (MiOS and plugin version with keep-alives, and time broadcast) along with good solid zone updates!

Will reboot 2DS a bit also in order to validate that the time broadcast work around is re-enabled at TPI log-in!
Title: Re: DSC Alarm System plugin
Post by: Puck404 on June 08, 2012, 04:03:18 pm
I am trying to install this plugin.  When it states "reload luup" how do I do that?  Thanks
Title: Re: DSC Alarm System plugin
Post by: strangely on June 08, 2012, 04:16:59 pm
Hi that doesn't sound good!

Couple of questions for you:

-Where did you install the plugin from? (app store or code.mios.com)
-Which Browser did you use?
-What hardware are you using? (2DS, IT100, Vera1,2,3, V.Lite?)

Posting this sort of information helps us help you :)
Title: Re: DSC Alarm System plugin
Post by: Brientim on June 08, 2012, 04:30:53 pm
I am trying to install this plugin.  When it states "reload luup" how do I do that?  Thanks

On the top right of your browser when on looking at your Vera, click on "reload".
The will then reload luup. Some plugins may require you to do this several times but be patient after clicking reload and all it to reload and then complete actions.
Title: Re: DSC Alarm System plugin
Post by: Puck404 on June 08, 2012, 05:20:18 pm
I did all that, and the dsc alarm panel does show up but it says the image is loading, and there is no "interface type". not sure what I did.
Title: Re: DSC Alarm System plugin
Post by: Puck404 on June 08, 2012, 05:44:18 pm
When I reload the luup it says "cannot send command: '001" After trying to load DSC panel
Title: Re: DSC Alarm System plugin
Post by: Brientim on June 08, 2012, 05:47:39 pm
@Puck404,

As @strangley states, it will depend on:
what and where you got the app?
What interface you have. It100 or 2ds?
If it100 how have you connected it to your unit.

When you created the device, you gave it aK
Name. Does that appear and if so, click on the spanner and select it100 or 2ds. On the second tab.
If you have a 2ds, go to the advanced tab and enter 2ds (ip address):4025 eg 112.122.122.1:4025
Click save. This will restart luup.

See how you go. For your next post provide the info above and work from that point.
Title: Re: DSC Alarm System plugin
Post by: rwalker on June 08, 2012, 06:10:48 pm
48 hours + up and running without a single TPI disconnect/reconnect since the latest revisions (MiOS and plugin version with keep-alives, and time broadcast) along with good solid zone updates!

Will reboot 2DS a bit also in order to validate that the time broadcast work around is re-enabled at TPI log-in!

I would really like to help beta test this.  I am also having the disconnects.  How do I get on the MCV beta wagon?

Thanks,
Roy
Title: Re: DSC Alarm System plugin
Post by: strangely on June 08, 2012, 06:58:24 pm
I would really like to help beta test this.  I am also having the disconnects.  How do I get on the MCV beta wagon?
I will find out if its OK to share the MiOS version I'm on, and if so then I'll PM you. 
Title: Re: DSC Alarm System plugin
Post by: Puck404 on June 08, 2012, 07:00:11 pm
Sorry about that, here is where i stand.  I am using a 2DS, i did all the steps as provided below:
UI5 Installation and Setup for IP170/2DS

NOTE this is currently beta only and will only work if the IP170/2DS has the correct firmware.

    Download the plug-in from this location.
    On the Vera UI go to Apps >> Develop Apps >> Luup files and upload all the files from that archive. Do not check Restart Luup after upload. If it's checked, uncheck it. Click GO to upload the files on Vera.
    Go to Create device.
        In the Description field enter DSC Alarm Panel.
        In the Upnp Device Filename field enter D_DSCAlarmPanel1.xml.
        In the Ip Address field enter the IP address and port of the 2DS. The port is 4025. E.g. if the IP address of the 2DS is 192.168.81.63 the IP Address field must look like this: 192.168.81.63:4025.
        Click on the Create device button to create the device.
    Reload Luup.
    After the plugin is created, open the control panel of the parent device (the one called DSC Alarm Panel) by clicking on the wrench, go to the Advanced tab, scroll to the bottom until you can see the InterfaceType field and change it from IT100 to 2DS.
    Save.

Now I do have 2 devices showing one is labled DSC Alarm Panel and the other one reads Partition 1. I think i may have figured out one of the problems but not how to fix it.  The DS is connected to a WNCE2001 wireless adapter that in then connected to my router.  I am using the ip address of the WNCE2001 and not the DS.  I cant even see the DS connected to my router, could that be the problem?  I do know the DS is online because I can access it remotly.
Title: Re: DSC Alarm System plugin
Post by: strangely on June 08, 2012, 07:14:44 pm
Definitely should be the IP of the 2DS that you enter!

If you are familiar with IP diagnostics etc, then are you able to ping it from anything else on your network?

Title: Re: DSC Alarm System plugin
Post by: guessed on June 08, 2012, 07:32:51 pm
@strangely,
Part of the problem is that the install instructions on this page:
    http://code.mios.com/trac/mios_dscalarmpanel/wiki/UI5

for the 2DS are obsolete.  They're getting the user to download an incompatible version of the Plugin.  It won't work with the latest 2DS firmwares.

For the most part, UI5 users can just use the version out of apps.mios.com, and we'll checkpoint update that once the relevant validations are in place.
Title: Re: DSC Alarm System plugin
Post by: Mikey on June 10, 2012, 02:56:36 pm
I would really like to help beta test this.  I am also having the disconnects.  How do I get on the MCV beta wagon?
I will find out if its OK to share the MiOS version I'm on, and if so then I'll PM you.
If you wouldn't mind checking for those using the IT-100/Wiznet solution too, that would be great.  The 2DS disconnect issues describe what I've been experiencing for months (and detailed a bit back on page 40 of this thread): a few days of flawless interconnectivity between the Vera2 and the IT-100 followed by nothing.

Thanks,
-Mike
Title: Re: DSC Alarm System plugin
Post by: garrettwp on June 10, 2012, 03:33:06 pm
I've been running with an it-100 for months on end with out any issue.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on June 10, 2012, 05:09:59 pm
We'd had a discussion going on one of the other threads about using PGM's as a mechanism for getting Vera-based state data "into" a traditional Alarm configuration:
   http://forum.micasaverde.com/index.php/topic,10763.0.html


For folks with a 2DS unit, you can Pulse the PGM output using a URL like:
Code: [Select]
http://<veraIP>:3480/data_request?id=action&DeviceNum=61&serviceId=urn:micasaverde-com:serviceId:DSCAlarmPanel1&action=SendCommand&Command=071&Data=1*71
and can call it via Luup using a Lua snippet like:
Code: [Select]
luup.call_action("urn:micasaverde-com:serviceId:DSCAlarmPanel1",
                 "SendCommand",
                 {Command = "071", Data="1*71"}, 61)

The above examples will do the action on PGM1 (*71).  For PGM 2..4, substitute to get *72, *73 or *74.


In order to do this, you first need to set the Target PGM to not require a PIN Code.  Many thanks to @strangely for this bit of DSC Configuration!!
Quote from: strangely
For the PGM PIN entry, you need to toggle 501 5 and 502 5 to turn PIN code entry off.

No other changes were made to the generic DSC, and all testing was done using PGM1.  For this setup, I have an LED wired across AUX+ and PGM1 (with an appropriate resistor).  When the PGM is changed, the LED will light for ~7 seconds.  Different PGM outputs have different default configurations, so check the manual to see what options are needed in your specific case.

If this needs to be wired to another Zone, as per the original discussion, then you'd need to use a Low Wattage Relay unit.  I haven't tested this part, but it should work also... as long as the Relay is low wattage (the PGM1 connection can only provide/sink 50mA @ 12v).

Wiring diagram is the standard one shown in places like:
    http://www.dslreports.com/forum/r26407137-Power-without-negative-terminal~start=100

For manual control of the PGM directly from the Alarm unit's Keypad, users can directly key in *71, *72, etc.


As usual, use appropriate caution in this setup.  Having Vera accidentally trigger an Alarm on a Managed/Monitored Alarm Panel may result in the Police arriving at your house unexpectedly...  8)
Title: Re: DSC Alarm System plugin
Post by: guessed on June 10, 2012, 07:00:35 pm
@Mikey,
Based upon the previous log data, it looked like your box was crashing (Exit with 137 code). 

We've not been able to find anyone that can make that consistently occur in their environment.  If it's consistent in yours then I'd strongly recommend opening up a Ticket against MCV's support staff so they can get to the bottom of the issue.

In addition, if you're seeing disconnects after a long period of time, using the IT100/WIZnet combination, then the Keep-Alive fixes MCV is building into the Firmware should help work-around that situation also (the fixes really assist anything that's Network attached)..  we just have to wait for them to release it.

Note though that this is really a work-around to determining why the Network device goes dark after some time.  Finding the root cause will straighten out the problem in a better manner as no data will be lost during the blackout-period. 

I recently had a WIZnet appear to die, only to find out that it's 5v Power supply was failing.  It might pay to check that the PS unit is healthy, or try an alternative one.  If that's working ok, then you may want to check the health of the other devices in the Network chain between the WIZnet and the Vera unit, just in case any of them is on the fritz.

I would really like to help beta test this.  I am also having the disconnects.  How do I get on the MCV beta wagon?
I will find out if its OK to share the MiOS version I'm on, and if so then I'll PM you.
If you wouldn't mind checking for those using the IT-100/Wiznet solution too, that would be great.  The 2DS disconnect issues describe what I've been experiencing for months (and detailed a bit back on page 40 of this thread): a few days of flawless interconnectivity between the Vera2 and the IT-100 followed by nothing.

Thanks,
-Mike
Title: Re: DSC Alarm System plugin
Post by: anonymark on June 12, 2012, 05:51:08 pm
Just thought I'd post a big thank you in this thread. I recently got a Vera3 to hook up to my thermostat and put a few lights on a schedule. I stumbled across this thread and now have a 2DS and DSC KIT32-219 on order, thanks to the recommendations on here.  I had been looking to upgrade a really old ADT system that came with my house 10 years ago and died, but didn't need any monitoring service.

I'll post in a week or so once I get everything installed.
Title: Re: DSC Alarm System plugin
Post by: guessed on June 13, 2012, 02:26:12 pm
2DS Update...

The work that @oTi@ has been doing with the Envisacor/2DS engineers has resulted in release 01.07.81 of their firmware (http://forum.eyez-on.com/FORUM/viewtopic.php?f=6&t=374). 

This addresses a number of the disconnect problems experienced in moderately sized LAN Networks, where the device would disconnect from either Vera, or from their hosting service (and often it would reboot).

There's still work to go to nail down all of the situations, but this set of bundled fixes should give longer runtimes without issues.
Title: Re: DSC Alarm System plugin
Post by: strangely on June 13, 2012, 07:02:53 pm
It'll be interesting to see how much more stable this is.

I switched my V3 over from my V.lite (using the 2DS rather than the IT100) a couple of days ago before going away on a business trip, and judging by the quantity of alert emails I've had from eyes-on, it's been pretty unstable!

Will home tonight, so will be taking a better look!

Title: Re: DSC Alarm System plugin
Post by: guessed on June 13, 2012, 08:57:58 pm
It'll be interesting to see how much more stable this is.

I switched my V3 over from my V.lite (using the 2DS rather than the IT100) a couple of days ago before going away on a business trip, and judging by the quantity of alert emails I've had from eyes-on, it's been pretty unstable!

Will home tonight, so will be taking a better look!
I imagine most of our [TCP] networks look fairly similar.  There were problems in handling/retaining 2DS connectivity when there were multiple devices on the network.

I wouldn't go as far as to say it was caused by "large networks" as they have in their release notes, but these things are always relative.

Interesting side-point, both oTi and I have [roughly] the same number of devices on our [flat, switched] Networks... but I don't experience the same symptoms.

If we continue to see issues, we may need to start cataloging the TCP device types people use to narrow it down, as grabbing tcpdump traces isn't practical for all users that may need diag.

Once you've run it for 24-48 hours, I'd love to hear the feedback on TPI disconnects (etc).
Title: Re: DSC Alarm System plugin
Post by: strangely on June 13, 2012, 09:41:21 pm
Interesting that it was a lot more stable on the Vera lite though as they were both on a network of about 25 to 30 devices (not including switches, router and modem) with a their relative topology similar!
Title: Re: DSC Alarm System plugin
Post by: strangely on June 14, 2012, 03:43:53 pm
The good news is there's no TPI reconnects now, however I'm not getting any zone trips or anything else working now since they pushed this new firmware.

Haven't had a chance to troubleshoot yet (other than a LUUP restart), but will take a look tonight when I get home!

@oTi, @guessed, are both of yours working OK? 
Title: Re: DSC Alarm System plugin
Post by: guessed on June 15, 2012, 12:32:20 am
Updates on Vera are working correctly (at least with the MiOS KA Patch, the DSC Plugin Time Broadcast fix, and 2DS Firmware 1.07.81).

Note that as of Firmware 1.07.78 (http://forum.eyez-on.com/FORUM/viewtopic.php?f=6&t=369), that Eyez-on shows these changes "somewhat delayed", the verbiage they use on their firmware page is a little subtle in this respect.  It's something like 10 minutes delayed for display purposes.

The good news is there's no TPI reconnects now, however I'm not getting any zone trips or anything else working now since they pushed this new firmware.

Haven't had a chance to troubleshoot yet (other than a LUUP restart), but will take a look tonight when I get home!

@oTi, @guessed, are both of yours working OK?
Title: Re: DSC Alarm System plugin
Post by: strangely on June 15, 2012, 12:36:27 am
All is good now!

I just checked and the fake IP I'd entered into the Vera Lite for the 2DS (prior to switching to the V3) had reverted back to the real one, and it was conflicting with the V3!

That'll teach me for being a lazy Bstard, and not just walking upstairs to unplug it :)
Title: Re: DSC Alarm System plugin
Post by: oTi@ on June 15, 2012, 05:49:45 am
@oTi, @guessed, are both of yours working OK?
Definitely seems to be working better than prior to build 80, so I actually now have my main Vera talk to the 2DS. I'm running without KA's and time dist.
Title: Re: DSC Alarm System plugin
Post by: strangely on June 15, 2012, 01:20:49 pm
I had one disconnect/reconnect in the early hours of last night already, however it all seems to be working fine so far!
Title: Re: DSC Alarm System plugin
Post by: guessed on June 15, 2012, 01:40:57 pm
@strangely,
Ok, I will call you over the weekend to get tcpdump setup on your machine.  We'll need packet-captures to go with the disconnects to nail them down. 

In practice, the only valid reasons for a disconnect are:
a) an actual network disconnect,
b) a 2DS Firmware upgrade, OR;
c) a Vera restart
Title: Re: DSC Alarm System plugin
Post by: strangely on June 15, 2012, 01:54:30 pm
I'll keep a close eye on it now that I'm back home, and likely will set up the V3 with tcpdump installed and running also so that we can capture it.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on June 16, 2012, 09:05:49 am
Looks like I'll have to load the dsc plugin on my Vera lite for testing. Hopefully this will convince me to switch over to the 2DS. First need to remove the Vera lite from mios bridge mode to not flood my Vera3 with additional devices.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: strangely on June 16, 2012, 06:22:15 pm
So I saw another restart last night at 3.04AM and had a hunch it might have been connected with the automated heal process, and when I checked my heal logs, the time it finished correlated with the TPI restart.

My V.Lite that I had it running on previously, did not have any Zwave devices linked to it, and I guess that's why I never saw it!
Title: Re: DSC Alarm System plugin
Post by: guessed on June 16, 2012, 06:44:13 pm
... we need to get tcpdump running on your machine so you can see if Vera is gracefully terminating during that time, or if it's just happening to trigger KA logic.

To install tcpdump...
    http://forum.micasaverde.com/index.php/topic,9156.msg74943.html#msg74943

To run tcpdump...
Code: [Select]
    tcpdump -i eth0.2 -s 0 -w foo.tmp
if you want it not to record your Terminal traffic, from <ipAddress>, then you can use:
Code: [Select]
    tcpdump -i eth0.2 -s 0 -w foo.pcap tcp and not host <ipAddress>
just make sure that you have enough space to keep foo.pcap around, since it'll capture ALL of the packet data to Vera.. at least all of the Packet data that Vera would otherwise be able to see (Ethernet Broadcast requests like ARP, Vera originated/targetted traffic, etc).  Other communications will not be picked up because you have a switched network.

You could put into cron so that it only runs at-or-near 3:00 if you wanted to validate your theory above.
Title: Re: DSC Alarm System plugin
Post by: strangely on June 16, 2012, 06:56:36 pm
Well I am certain its related to the heal, as I just checked back in a deleted mail from the day before, and the TPI restart was an identical time. I'll install it all tonight and grab the capture. I know it'll do it again as my Aeon HEM is unconfigured (and unplugged).

I'm assuming its just the result of LuaUPnP process restarting due to the heal.
Title: Re: DSC Alarm System plugin
Post by: guessed on June 16, 2012, 07:13:23 pm
I'm assuming its just the result of LuaUPnP process restarting due to the heal.
Yes, if the LuaUPnP process restarts for any reason, you'll see a TPI Connect in the eyez-on logs...  That's safe to ignore

It'd be the same as hitting (Save)/(Reload) since they do the same thing in restarting the LuaUPnP process.
Title: Re: DSC Alarm System plugin
Post by: strangely on June 16, 2012, 07:43:23 pm
IIRC LuaUPnP always restarts after the heal and I'll test this later by running it manually to make sure the TPI restarts also.
Title: Re: DSC Alarm System plugin
Post by: rwalker on June 18, 2012, 06:53:16 pm
Well my setup is pretty rock solid at this point.  I have had no disconnects since .81 came out.  I still am not getting triggers with the doors to work.  Really hoping the patch from MCV does in fact fix that.
Title: DSC Alarm System plugin
Post by: Raynaldg on June 19, 2012, 12:37:36 pm
About the sync issue between my veralite and the 2DS,  the problem seems to be resolved;  about 4 to 5 days without unsync behavior!  I suppose that I received a new 2DS firmware upgrade that fixed the problem?!?!

I have questions about the the Veramobile integration :

1.  Is it normal that I can see only the security zone and nothing else ( I can't see the 2DS panel / partition so, I can't see the panel status)

2.  The "armed switch" on the zone;  is it suppose to send a bypass on the panel when it's turned off ?  If so, it don't work!

Also, is it possible to send PGM command to the panel ?  If so, do you have a luup script example ?

Thank you !  😄
Title: Re: DSC Alarm System plugin
Post by: strangely on June 19, 2012, 01:31:08 pm
1.  Is it normal that I can see only the security zone and nothing else ( I can't see the 2DS panel / partition so, I can't see the panel status)
As far as I remember yes! The mobile UI hasn't been worked on for a long time!
Quote
2.  The "armed switch" on the zone;  is it suppose to send a bypass on the panel when it's turned off ?  If so, it don't work!
Nope this is just for screen scripting and independent of the alarm plugin.
Quote
Also, is it possible to send PGM command to the panel ?  If so, do you have a luup script example ?
Yes see here http://forum.micasaverde.com/index.php/topic,5154.msg76090.html#msg76090

Title: Re: DSC Alarm System plugin
Post by: guessed on June 19, 2012, 03:59:08 pm
@rwalker,
If you're not seeing disconnects, then the MCV Firmware fix won't help.  It's really about detecting when a reconnect is necessary, and then reconnecting.

You may need to outline the specifics of what you're seeing.

For example, if you open/close doors, are these state-changes being indicated on the Dashboard?

If they're working correctly, then something is amiss in your Scene definitions, and you can probably attach a screenshot of the relevant parts to illustrate how you set it up.

Well my setup is pretty rock solid at this point.  I have had no disconnects since .81 came out.  I still am not getting triggers with the doors to work.  Really hoping the patch from MCV does in fact fix that.
Title: Re: DSC Alarm System plugin
Post by: guest15496 on June 19, 2012, 10:18:24 pm
Hi - long time lurker, first time poster.

I have the .81 version of the 2DS firmware, connected to an 1832 panel. I have Vera 3 running the 1.5.346 firmware connected over Ethernet. My DSC has about 20 zones including doors, motion and a few wireless smokes. I bounced back and forth between the beta code and the release DSC plugin unil I understood how to update files manually, so I am a lit worried that perhaps my plugin file set is inconsistent, if someone can give me something to check there to validate the files timestamps themselves and my overall installed version.

I don't know how to check for disconnects, but I don't see anything (slow/missing DB updates) that tells me I have them. The 2DS web page always seems to say that the Vera's IP is connected over TPI, but I don't check it that frequently.

As of now I have all of my DSC zones appearing on Vera, and they respond properly in the Vera DB to zone events. I haven't learned scenes or triggers yet so haven't set any up.

Right now in addition to the above-mentioned issues with the veramobile app (Android), I also see that my DSC DB objects did not pick up the zone labels, nor do any of the buttons such as Alarm on the panel DB object work.

Also I have two InterfacePassword fields in the mail alarm DB object's Advanced screen, they both contain the proper password.
I created one of them manually and I don't know how to delete it. I also get "DSCAlarmPanel : Error logging in to 2DS, please check your password" at the top, assuming it is related.

Many thanks for your efforts. I am also willing to help test new releases if needed.






Title: Re: DSC Alarm System plugin
Post by: strangely on June 20, 2012, 08:11:26 pm
@bobk,

Sounds like you are running an older version that doesn't support recent changes in regards to passwords etc. Best thing to do is to delete the plugin and use the one from the app store within vera.

Also regarding Zone labels, unfortunately, the 2DS doesn't support that feature due to memory constraints; only the IT100 supports zone labels currently.

Try the app store plugin, and see if it fixes your issues!?
Title: Re: DSC Alarm System plugin
Post by: guest15496 on June 21, 2012, 09:22:02 pm
@strangely,

Thanks for your reply. The production code in the app store doesn't work for me, that was where I started. I was not getting any activity on the dashboard when DSC events occurred. If you would like me to go back to that build and check a specific log file please tell me which one and where. In any case I followed the instructions at http://code.mios.com/trac/mios_dscalarmpanel, installing from the app store, it does have the ip field where I put in the ip:4025 of the 2DS, but it does not have the button where I can select 2DS vs. IT170. So after reading back through this thread I found the discussion of the .36 branch and the beta 2DS-specific branch at code.mios.com. Installing those gives me the selector button, and works correctly to register DSC events, however it seems to have the smaller issues that I reported in my first post. If the 2DS does not handle the zone labels then that answers that question.

Title: Re: DSC Alarm System plugin
Post by: anonymark on June 26, 2012, 09:29:29 am
I'm having the same issue as Bobk. The production app does not register any of the DSC panel events.  I tried going back to the .36 version, but that does not work either. I tried to SSH into the vera and clean out the production luup code after uninstalling it but can't find the SSH password. (Vera light 3 running UI5).  I have my DSC panel running perfectly and I'd like to get this up and running so I can use the DSC sensors to trigger some scenes (Ie  open garage door at night, turn on lights etc...) 


Not sure where to go here....
Title: Re: DSC Alarm System plugin
Post by: strangely on June 26, 2012, 11:49:07 am
@anonymark, I think @bobk got his working OK, just no custom zone labels!

You shouldn't really need to delete the files, but if you want to be sure and get rid of them then you can find your ssh password in the cmh.conf file in a recent backup. The second way to find it is here:
http://wiki.micasaverde.com/index.php/Logon_Vera_SSH

Not sure why the plugin is not working but maybe try the version here:
http://code.mios.com/trac/mios_dscalarmpanel/changeset/78/trunk?old_path=%2F&format=zip

Some tips for a successful install:
- Make sure you upload all files using something other than internet explorer (Chrome, Firefox, Safari etc)
- Create the device by going to Apps>Develop Apps>Create Device and enter D_DSCAlarmPanel1.xml in the Upnp Device Filename box and I_DSCAlarmPanel1.xml in the Upnp Implementation Filename, and then a descriptive name and then hit create device button.
-  In your dashboard you should then have a device with the same name you entered earlier; in the DSC Alarm Panel tab select EnvisaLink 2DS, then go to the settings tab and enter only the IP address (no port).
- Save

If the above works then you should at least get 6 zones configured, if they don't then its possible that perhaps your zones are configured to start after zone 6? (do you have all wireless sensors perhaps?). Confirm your zone numbers and then make sure they are entered in the MotionZones of the advanced tab of the panel device (parent) and save!
Title: Re: DSC Alarm System plugin
Post by: anonymark on June 26, 2012, 01:04:24 pm
Strangely,

Thanks,  I tried using the version you suggested. Everything seems to be set up correctly. I'm just not getting the "running man" to turn red...... I'm running 1 wired door sensor and 2 wireless sensors.   I'm going to play around with some different versions to see what works.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on June 26, 2012, 01:12:47 pm
Just a heads up the wireless sensors have a 6 second delay. So when you do get things working, you are aware that scenes triggered from these sensors are not instant.

Correction this only relates to the motion sensors.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: strangely on June 26, 2012, 01:29:06 pm
I'm just not getting the "running man" to turn red...... I'm running 1 wired door sensor and 2 wireless sensors.   I'm going to play around with some different versions to see what works.

Can you arm or disarm?
Do you see either form the local webpage that a TPI session is connected, or do you get an email alert from eyez-on about a TPI login/logout?
What are your actual zone numbers?
Title: Re: DSC Alarm System plugin
Post by: anonymark on June 26, 2012, 02:22:44 pm
I can't arm or disarm. I'm running zones 1 (hard wired) and 10,11 (wireless door) and 12 (wireless fire)  at the moment. I'm not seeing that a TPI session is connected.
Title: Re: DSC Alarm System plugin
Post by: Kyle on June 26, 2012, 04:54:53 pm
strangely,

I can confirm that the link you posted in #820 does work. I was using the plugin from the app list within Vera and it didn't work. So far its all working... Bummer the 2DS can't read zone labels. I just renamed them.
Title: Re: DSC Alarm System plugin
Post by: strangely on June 26, 2012, 05:01:59 pm
@anonymark , what firmware version is your 2DS at and also did you ever register it at eyez-on?
Title: Re: DSC Alarm System plugin
Post by: Kyle on June 26, 2012, 05:10:09 pm
What firmware version is your 2DS at and also did you ever register it at eyez-on?


It's at 81 and I also registered it at eyez-on. Everything worked once I installed the plugin you posted in post #820
Title: Re: DSC Alarm System plugin
Post by: strangely on June 26, 2012, 05:12:12 pm
Ah sorry I had meant to direct the firmware question towards @anonymark!
Title: Re: DSC Alarm System plugin
Post by: guest15496 on June 26, 2012, 08:33:32 pm
A bit of clarification on my past actions and current state: for me, the only version I can get to work is the 2DS branch - neither the .36 branch nor the app store version work for me (no running man activity). I bounced around between all three again over the weekend to make sure.

Using the eyez-on web site log, I get about one "TPI Session Closed" per day, followed by a re-login typically less than 1 minute later. Overall responsiveness to DSC events including wireless devices continues to be stable, albeing not torture-tested. I can arm and disarm with EnableRemoteArm = disarm. I fully understand that zone labels are not supported by the 2DS.

In the process of reinstalling various versions this past weekend I managed to get rid of the duplicate InterfacePassword fields, but the error message in my previous post remains. However I can't associate that error with any specific problem so I am not concerned about it. I added the zone numbers with leading 0s so they sort properly in the DB, until I can go back and add zone labels.

I wasn't aware that I_DSCAlarmPanel1.xml had to be specified as an implementation filename (in addition to D_... for the device filename) - I'll probably redo the install again regardless, but what do I not have as a result of not doing that?
Title: Re: DSC Alarm System plugin
Post by: Brientim on June 27, 2012, 04:00:59 am
@guessed. Feedback on observations using the same network infrastructure, UI but different units. 

I had the Cisco router replaced  and I have also finally given received my Vera 3 (a present from my wife).
Even after all managed switches were removed and replaced with a non-managed switches, I was still receiving disconnections but haven't had any time to look at this. After switching out the Vera 2 and replacing it with the Vera 3 two days ago, there has not been one disconnection other than restarts as a result of installing apps etc.

a) a summary of each of the problems they observe - Nil with (Vera3)
b) what UI/Vera version they're running - Vera3 UI5 firmware 1.5.346
c) what their Network topology they're using - Configuration - Netgear G3100 router with 4 non-managed (removed all managed switches).   
d) whether it's a 2DS or a [Network-enabled] IT100 they're using - 2DS
I haven't been back to DSC system for awhile and I had some spare time recently and thought I needed to to get my mind off work (concurrent upgrade projects) and step back in to a more fun domain...
Update
As above 2DS firmware now at .81
Network Topology:
The Cisco router was replaced with Netgear GC3100.
Reintroducing the Linksys SRW2016 = 12 active connections.
3*8 Port = 17 active connections.
Router and switches are Gigabit capable and I relocated a few multimedia devices and moved one NAS to improve traffic.

Quitetime normally would have between 19 - 25 active connections and day/peak 30-40 including wifi, multimedia, tv and phone etc.

My reasoning was to see if the new 2DS firmware and the trunk 78 code rectified the previous issues as identified. In addition, the removal of the switch improved service reliability for the 2DS but what happens with new firmware and code if it was reintroduce. The result, not one unexpected disconnection and all zone updates are functioning. Therefore, the previous issues could be attibuted to some network issues, a little laziness and a network traffice hypersentive 2DS which have all now been resolved expect for the "little laziness" got to enjoy life with the kids.  It is very robust now; especially with the number of devices and multimedia traffic that occurrs. Time to introduce the 2DS to my live system.

Thanks to @guessed, @strangley and whomever have assisted along the way.   
 
Off the subject
'188 is a long standing issue, thought to be benign (but def annoying when you're reading logs). 
After the previous removal of the and subsequently stop the download request, it suddenly reappeared. It was traced the iPhone app log on. We normally do not use the app (not that is isn't any good but because we use iRule) however, it is available. Remove the device and used the app again and yes device installed with 188...

device id="122" name="SqRemote" device_type="urn:schemas-squareconnect-com:device:SqRemote:1" room="0" id_parent="0" embedded="0" disabled="0" device_file="" impl_file="" manufacturer="" model="" altid="7xxxxxxxxxxxxxxxxxxxxxxxxxxxxx" ip="" mac="" time_created="1340180342" plugin="188" invisible="1"

Title: Re: DSC Alarm System plugin
Post by: anonymark on June 27, 2012, 09:19:40 am
Strangely,   I'm also at .81 and registered at eyez on. I just reinstalled the 78 plugin. I'm getting no TPI status in the 2DS and I'm getting the "invalid password for the 2ds" error.    I don't see anywhere to enter the password in the advanced settings....this may be a problem? 
Title: Re: DSC Alarm System plugin
Post by: Brientim on June 27, 2012, 10:14:24 am
Feedback on plugin release 0.37. Installed smoothly, no issues encountered.
Only one recommended changed to 841 from "Trouble Status (LED OFF)" to "No Trouble (LED OFF)".

I did notice on general deficiency between available apps and installed apps. Only the version is displayed in the installed app and the modified date is not displayed. This in itself is not a fault but lacks some aspects of verification in reviewing if updates installed automatically as discussed else where. Noting that once an app is installed, it is not displayed in available apps and therefore, removes the capability to quickly audit the modified date.

Thanks again
Title: Re: DSC Alarm System plugin
Post by: strangely on June 27, 2012, 06:27:44 pm
Strangely,   I'm also at .81 and registered at eyez on. I just reinstalled the 78 plugin. I'm getting no TPI status in the 2DS and I'm getting the "invalid password for the 2ds" error.    I don't see anywhere to enter the password in the advanced settings....this may be a problem?
Please delete the plugin and then perform a save once this is done. I'd then like you to install the version in the app store (0.37). If it doesn't work then please leave it on your Vera, and we'll take the troubleshooting from there.

Some other questions for you...
-Did you ever change the default local login on the 2DS?
-How do you have your 2DS connected in your network, along with other details such as how do you have your Vera setup (some sort of topology description would be good)
-Are you familiar with how to SSH into your Vera? If you know how to do this then we may ask you to pull a log, or try some other basics like pinging the 2DS from Vera. It sounds like either you have a connectivity issue (least probable), or the prior password entry is screwing you up.
Title: Re: DSC Alarm System plugin
Post by: WalterWhite on June 27, 2012, 10:39:54 pm
Hey Folks (newbie - first post)

I apologize if this has already been covered but I've searched the thread and didn't find any specific hits and I can't read the almost 900 posts in detail.

Anyway, I picked up a VeraLite (upgraded S/W to the latest), and have it hooked up to a DSC-1832 via an IT-100.  Added the DSC plug-in (v 0.37) and was able to set it up via the instructions on code.mios.com.   Things work pretty well: setup all 18 zones, zone labels came across, can arm/disarm manually from UI5.

The only issue is that sometimes sensors will trip but never clear.  Have had this happen on motion detectors and a door sensor.  They go into the red running man and will never come out.  A reload of the VeraLite doesn't help - I need to un-install and re-install the plug in.  Re-tripping/re-clearing the sensor also doesn't clear it on the Vera.  And sometimes I'm getting a DSC IT-100 not configured error message as well.  But clearly it was configured and working at one point to get the zone names, status', and for me to be able to do arms/disarms via the Vera.

Any suggestions on how to handle this?  I'm new to Vera but I'm a very technical person.  I haven't done it yet on the VeraLite but I do use ssh on daily basis in my profession so that sort of technical thing won't be a problem - I'm just new to the Vera world right now.

Thanks!  (And again my apologies for the newbie questions).
Title: Re: DSC Alarm System plugin
Post by: guessed on June 27, 2012, 10:54:45 pm
@WalterWhite,
A couple of questions:

a) What version of UI5 are you running on your Vera Lite?
b) How is the IT100 connected to Vera?

For (b), if it's Serial then I'd want to know exactly which make/model of USB-Serial you're using.  If it's Network, then what Ethernet-Serial device are you using, it is on the same Network [switch] and has it been configured with StaticIP?

If you're comfortable with SSH, you can also turn on verbose Logging (through the Vera UI) and look at the Log file:
Code: [Select]
    tail -f /var/log/cmh/LuaUPnP.log
This will show you what's going on, as it's going on.  It's very odd that you'd ever have to reload the codebase, since a "reload"/"restart" of Vera will normally just fire up the code again and reset any state inconsistencies (although these should not occur either)

Once we get beyond this, I may PM you my email address  where you can send logs for diag (with detailed logging enabled).  You won't be able to respond to that PM as you don't yet have enough postings, but you'll be able to email me the relevant file (the LuaUPnP.log file listed above)


PS: It might take me a while to get back to you, as I'm fairly busy, but at least I'd have the logs... preferably from a Vera startup up to the point where it's no longer reporting status updates.
Title: Re: DSC Alarm System plugin
Post by: guessed on June 27, 2012, 11:08:40 pm
Only one recommended changed to 841 from "Trouble Status (LED OFF)" to "No Trouble (LED OFF)".
To avoid disputes over the labels, I use the strings from the IT100, or 2DS, Documentation... character-for-character.  If you can convince them to change it, I'll make the same changes  8)

To be honest, I'm not really expecting people to use the Dashboard for much more than validating basic functionality of the plugin.  The Dashboard UI framework is fairly primitive.  I was expecting most people to use an Alarm-aware CP like AutHomation (etc) that will display it's own messages (for the core statuses)
Title: Re: DSC Alarm System plugin
Post by: WalterWhite on June 28, 2012, 12:13:00 am
@WalterWhite,
A couple of questions:

a) What version of UI5 are you running on your Vera Lite?
b) How is the IT100 connected to Vera?

For (b), if it's Serial then I'd want to know exactly which make/model of USB-Serial you're using....

Thanks guessed.  To answer your specific questions:

a) UI5, firmware version 1.5.346
b) via a serial-USB cable (from monoprice : product number 3726)

I've turned on verbose logging and I got your PM and will email you the LuaUPnP.log file.

Thanks a lot!  I appreciate it.  I must have something not set properly here.  (I've done multiple reloads but it still shows one sensor as tripped and the system not ready to arm even though the DSC wall panels say differently.)
Title: Re: DSC Alarm System plugin
Post by: anonymark on June 28, 2012, 12:25:54 am
Strangely,

I defaulted  the 2DS password and everything began working. I deleted and installed the .37 update and it works perfectly also. Unfortunately, I'm working a double shift today and tomorrow (well today and today now). I'll post up exactly what's going on once I have a chance to look at it tonight. Thanks for the password suggestion on the 2DS. I always change default passwords......Guess that was bad for once.

PS.  I'm running the Vera and 2DS behind a gigabyte switch on the same subnet. 
Title: Re: DSC Alarm System plugin
Post by: guessed on June 28, 2012, 12:28:24 am
@WalterWhite,
You may want to check if dmesg or logread is returning anything off wrt that USB Serial Port device.  I've not seen that specific one used before (I use a different PL2303 from Monoprice) so it's possible that it's either flaking, or being re-assigned in the Serial port/USB config - which would definitely screw with the Plugin.

If you have one handy, move the USB-Serial adapter to a powered USB Hub.  This will cause it to move to a different address, so you'll need to reset that association in the Serial Configuration dialog, but it might also stabilize things.  Vera3 units don't supply USB-spec power levels, if using the supplied PS, and I suspect that VeraLite units have the same issue.
Title: Re: DSC Alarm System plugin
Post by: guessed on June 28, 2012, 12:34:44 am
@anonymark,
We have a parameter that can be set to override the default parameter.  It's just not bubbled up in the UI, or "preconfigured" in the Advanced tab, but it's there if you need to create it.  It was deliberately left out as I didn't want to confuse the typical user with requests for a password.

Anyhow, if you want to set it then use the Advanced Tab, using the fields at the bottom of the UI:

ServiceId: urn:micasaverde-com:serviceId:DSCAlarmPanel1
Variable Name: InterfacePassword

If not set, or not present, it defaults to the default passcode for the 2DS  ;)

WARNING: Everything configured here goes into Vera-maintained configuration files.  These may get backed up to MiOS Servers.  There's not a lot of protection of this data, so you'll want to avoid using "secret" passwords ;)


Strangely,

I defaulted  the 2DS password and everything began working. I deleted and installed the .37 update and it works perfectly also. Unfortunately, I'm working a double shift today and tomorrow (well today and today now). I'll post up exactly what's going on once I have a chance to look at it tonight. Thanks for the password suggestion on the 2DS. I always change default passwords......Guess that was bad for once.

PS.  I'm running the Vera and 2DS behind a gigabyte switch on the same subnet.
Title: Re: DSC Alarm System plugin
Post by: Brientim on June 28, 2012, 02:09:13 am
Only one recommended changed to 841 from "Trouble Status (LED OFF)" to "No Trouble (LED OFF)".
To avoid disputes over the labels, I use the strings from the IT100, or 2DS, Documentation... character-for-character.  If you can convince them to change it, I'll make the same changes  8)

To be honest, I'm not really expecting people to use the Dashboard for much more than validating basic functionality of the plugin.  The Dashboard UI framework is fairly primitive.  I was expecting most people to use an Alarm-aware CP like AutHomation (etc) that will display it's own messages (for the core statuses)

Yer, right ::) I knew it was a direct transfer for documentation and accept the "verbatim" transciption is correct.

Well done on the new milsestone 3000+
Title: Re: DSC Alarm System plugin
Post by: anonymark on June 28, 2012, 08:12:07 pm
Guessed,

Just got home and tried it out. Thanks for the Interface Password. Everything is working great now. The wired zones are instantaneous and the wireless are almost instantaneous. I'm playing around with some scenes now (front door opens at night, lights on at 50% etc).  Thank you to you and Strangely!


Anonymark

@anonymark,
We have a parameter that can be set to override the default parameter.  It's just not bubbled up in the UI, or "preconfigured" in the Advanced tab, but it's there if you need to create it.  It was deliberately left out as I didn't want to confuse the typical user with requests for a password.

Anyhow, if you want to set it then use the Advanced Tab, using the fields at the bottom of the UI:

ServiceId: urn:micasaverde-com:serviceId:DSCAlarmPanel1
Variable Name: InterfacePassword

If not set, or not present, it defaults to the default passcode for the 2DS  ;)

WARNING: Everything configured here goes into Vera-maintained configuration files.  These may get backed up to MiOS Servers.  There's not a lot of protection of this data, so you'll want to avoid using "secret" passwords ;)


Strangely,

I defaulted  the 2DS password and everything began working. I deleted and installed the .37 update and it works perfectly also. Unfortunately, I'm working a double shift today and tomorrow (well today and today now). I'll post up exactly what's going on once I have a chance to look at it tonight. Thanks for the password suggestion on the 2DS. I always change default passwords......Guess that was bad for once.

PS.  I'm running the Vera and 2DS behind a gigabyte switch on the same subnet.
Title: Re: DSC Alarm System plugin
Post by: guest15496 on June 28, 2012, 11:35:00 pm
The .37 version of the plug-in from the app store appears to be working successfully for me also. After adding the InterfacePassword info according to the above, it is able to connect and I do not get any errors any more. Thank you.
Title: Re: DSC Alarm System plugin
Post by: MTB on July 06, 2012, 10:19:44 am
Hello, all.  I am new to Home Automation and I just received my Vera 3 and DSC 1832 system.  I read that I could connect two systems using a Ti-100 and a Roving Network (765-RN-134) so I bought both.  So my question is how do you connect the TI-100 to the RN-134?  The documentation says you can directly connect the RN-134 to the serial port but the RN-134 has 10 pins (5 on top and 5 on bottom in line) and the TI-100 has a 9 pin (5 on top and 4 on bottom offset).  Is there a cable that I need to buy to connect them???  Also, from reading the TI-100 info it looks like only the RX, TX and GND connections are used and a straight through RS-232 cable is required.  If this is so, how does the RN-134 get its power?  Is there another cable that I need to purchase or can I wire it to the DSC 1832 board somehow?  Last thing, if I every get these devices hooked up and working, how do I get the wireless to talk to my home network or Vera 3.  Thanks so much for any help!!!!  I know this is complicated and I am not an electrical type - more mechanical.  Thanks!
Title: Re: DSC Alarm System plugin
Post by: guessed on July 06, 2012, 12:38:37 pm
@MTB,
I had this setup during the original coding against the IT100.  From memory, I used ribbon cable and a 10 Pin header to connect to a standard Crimp on RS-232 connector.  If you check the pinouts of both the RN-134 and the RS232 connector, you should see how they're aligned, leaving one "spare" wire that you need to peel off (or cut off) the ribbon cable at the RS232 connector end.

The device will need to be self-powered, using any spare plugpack you have floating around.  There are solder terminals on the RN-134 board for doing exactly that, and the specs indicate the accepted voltage range (which, from memory, are 5-12v, but check the spec sheet)

Once you have the connections in place, you then need to hook it up to a computer, and configure the WiFi SSID, Password, Encryption type and Baud rate using a standard terminal program.  There's a command manual for the RN-131/RN-171 that is shared with this device and the commands are the same.
Title: Re: DSC Alarm System plugin
Post by: strangely on July 06, 2012, 04:51:32 pm
If its confirmed that it can run off of 12V then it should be possible to run it from the AUX + and - of the alarm panel.
Title: Re: DSC Alarm System plugin
Post by: babgvant on July 07, 2012, 04:44:59 pm
I'm seeing a strange issue with the app (via 2DS) where events caused by action by Vera (i.e. arming the alarm through the app) can be used to successfully trigger scenes (e.g. locking all the doors), but if I use the keypad to execute the same action the scene tied to the event does not execute.

Is this normal behavior or am I doing something wrong?

Thanks
Title: Re: DSC Alarm System plugin
Post by: guessed on July 07, 2012, 06:47:17 pm
@babgvant,
External events, like arming and Zone state changes, are reported back to the 2DS which reports them back to Vera.  These should all show up in the MiOS Dashboard, and the corresponding UI components change (and any Events/Scenes fire)

Make sure you're registered with the Eyez-on servers so that your 2DS unit gets the latest firmwares (1.07.81, right now) since there were nasty bugs in the earlier releases that would cause the 2DS to loose touch with Vera.  Firmware upgrades only occur when you're registered with them.
Title: Alarm active/not active triggers and Walk Test
Post by: Dolphran on July 09, 2012, 02:41:43 pm
I have a DSC 1832 V4.5 and a EnvisaLink 2DS.  I set up Scenes to turn a Z-Wave Siren on and off.   The triggers are 'Alarm is active', and 'Alarm is not active' respectively.  When I did a DSC Walk Test (code 901) to test my zones, when I triggered a zone, I got the two second alarm from the 1832, but unfortunately my Z-Wave Siren never turned off.  Has anyone here had better success with the Alarm active triggers and Walk Test?
Title: Re: DSC Alarm System plugin
Post by: babgvant on July 09, 2012, 04:38:24 pm
@babgvant,
External events, like arming and Zone state changes, are reported back to the 2DS which reports them back to Vera.  These should all show up in the MiOS Dashboard, and the corresponding UI components change (and any Events/Scenes fire)

I get the state changes for the different zones, and when I arm the panel via Vera the trigger fires. It's just when I arm it from the keypad.

Make sure you're registered with the Eyez-on servers so that your 2DS unit gets the latest firmwares (1.07.81, right now) since there were nasty bugs in the earlier releases that would cause the 2DS to loose touch with Vera.  Firmware upgrades only occur when you're registered with them.

Yep, that's what I'm running.

Thanks
Title: Re: DSC Alarm System plugin
Post by: MTB on July 09, 2012, 06:38:33 pm
@MTB,
I had this setup during the original coding against the IT100.  From memory, I used ribbon cable and a 10 Pin header to connect to a standard Crimp on RS-232 connector.  If you check the pinouts of both the RN-134 and the RS232 connector, you should see how they're aligned, leaving one "spare" wire that you need to peel off (or cut off) the ribbon cable at the RS232 connector end.

The device will need to be self-powered, using any spare plugpack you have floating around.  There are solder terminals on the RN-134 board for doing exactly that, and the specs indicate the accepted voltage range (which, from memory, are 5-12v, but check the spec sheet)

Once you have the connections in place, you then need to hook it up to a computer, and configure the WiFi SSID, Password, Encryption type and Baud rate using a standard terminal program.  There's a command manual for the RN-131/RN-171 that is shared with this device and the commands are the same.

@Guessed
Thank you for the response.  I received my RS-232 to 10 pin connector today and now I am looking at how I get this to work.  I read the manual on the RN-131 and see the software to download on the Roving site.  When I set the DSC, TI-100, RN-131 up, do I set it up to run or communicate with my home network or the Vera 3 network.  I wanted to install the Vera 3 as an access point on my network (since I already have a router with another access point - good coverage over my whole house) but my understanding is that this is not available with Vera 3 as yet!  I assume that if I get it to work with my Vera 3 I can control it with my iPhone, iPad, etc.  Also, any step-by step instructions would be very helpful (I am not a programer).  Do I need to program the TI-100 also? Or just the RN-131 with the info @Guessed suggested?  I read where the RN-131 can be booted up and will look for a local network and auto connect to it and then you can just connect it to you network (I think I see how this could work if it happened to find my home network - I could just sign into the device and reprogram it - Is this right?  It to bad that the TI-100 people did not just connect the power pin on the RS-232 so that the RN-134 would be powered thru the RS-232 connection!!!!!!
Title: Re: DSC Alarm System plugin
Post by: guessed on July 10, 2012, 12:15:20 am
@MTB,
I'd recommend breaking the config into parts, getting each working separately and then joining it all up at the end.  It'll take a while, but it'll likely avoid a lot of frustration.

The parts I'd break it into include:

a) Getting the DSC Panel itself setup
b) Connecting the IT100 via a USB-Serial cable to Vera directly (getting Baud rates correct, etc)
c) Getting the RN-134 working "freestanding"
d) Connecting the RN-134 to the IT100


Item (a) is referenced via a Link on the DSC Webpage on code.mios.com (http://code.mios.com/trac/mios_dscalarmpanel).  I used this to setup my test system and it's fairly simple to follow.

Item (b) will depend completely upon what OS you're using.  Once you've worked that out, you can connect to the IT100, and send commands like:
Code: [Select]
    000<cr><lf>and the IT100 should respond with
Code: [Select]
    500<cr><lf>(The IT100 Serial port settings are: 9600 baud rate with 8 bit data, No parity and 1 stop bit)

That'll let you know that you have baseline connectivity.

Item (c) is probably the hardest step.  I don't recall all the things I changed, but they included:
Code: [Select]
    set uart baudrate 9600
    set comm close 0
    set comm open 0
    set comm remote 0
    save
    reboot
Do a Google search for "rn-131 filetype:pdf site:gridconnect.com" which shows a number of the commands being run from a Windows machine.  The only extra you should need to set (apart from the Network stuff they set) are listed above, but this is largely from a quick lookup of the manual.

Note that I use a DHCP-assigned address, and that this address is "fixed" inside of my Router so the device always gets the same IP Address (so that Vera has a constant location to connect to)

Before you change any of the Baud rate settings, get it connecting to your WiFi network.  Once you have that, the perform a Save/Reboot step, and then go about changing the Baud rate.  Once you change the Baud settings, you'll need to reconnect from the Terminal program at the newly defined rate.

When I do this step, I connect to the RN-134 using a USB-Serial cable, but it can also be done by connecting to your IP Address, on port "2000".  In Windows, for example:
Code: [Select]
    telnet 192.168.1.57 2000
    Trying 192.168.1.57...
    Connected to serial-wifi.somewhere.overthenetwork.com.
    Escape character is '^]'.

    $$$
    CMD

Once you have that setup correctly, you can move onto Step (d)...
Title: Re: DSC Alarm System plugin
Post by: guessed on July 10, 2012, 01:00:35 am
@babgvant,
I'm going to need some feedback from the others here.  I just tried this on my Vera3 unit (1.5.407) with the latest code (from trunk, in my case).  There's only one small change/difference between that, and what's in apps.mios.com, but I don't expect it'll give the behavior you're describing.

Anyhow, when I manually arm via the Keypad I see the Device on the Dashboard update to reflect those changes in Arm'd state (etc).  It's possible that there's some "over time" behavior where this no longer occurs (which was part of the .80/.81 2DS firmware fixes)...

@babgvant,
External events, like arming and Zone state changes, are reported back to the 2DS which reports them back to Vera.  These should all show up in the MiOS Dashboard, and the corresponding UI components change (and any Events/Scenes fire)

I get the state changes for the different zones, and when I arm the panel via Vera the trigger fires. It's just when I arm it from the keypad.

Make sure you're registered with the Eyez-on servers so that your 2DS unit gets the latest firmwares (1.07.81, right now) since there were nasty bugs in the earlier releases that would cause the 2DS to loose touch with Vera.  Firmware upgrades only occur when you're registered with them.

Yep, that's what I'm running.

Thanks
Title: Re: DSC Alarm System plugin
Post by: Brientim on July 10, 2012, 04:05:43 am
@babgvant,
I'm going to need some feedback from the others here.  I just tried this on my Vera3 unit (1.5.407) with the latest code (from trunk, in my case).  There's only one small change/difference between that, and what's in apps.mios.com, but I don't expect it'll give the behavior you're describing.
@guessed
I am not at home and I had my wife test this. Update via the keypad are being reflected in Vera. I only had her try arm/disarm for the test 2ds on 83 beta and Vera 1.5.408, with plugin 0.37 plus. I could watch this remotely and confirm the Vera dashboard was reflecting the change as a result of the keypad events.
Title: Re: DSC Alarm System plugin
Post by: babgvant on July 10, 2012, 09:14:50 am
@babgvant,
I'm going to need some feedback from the others here.  I just tried this on my Vera3 unit (1.5.407) with the latest code (from trunk, in my case).  There's only one small change/difference between that, and what's in apps.mios.com, but I don't expect it'll give the behavior you're describing.

Anyhow, when I manually arm via the Keypad I see the Device on the Dashboard update to reflect those changes in Arm'd state (etc). 

TBC, the problem isn't that the status in the UI isn't changing when I use the keypad (it is); it's that scenes (e.g. I have one setup to lock all the doors) aren't being triggered by the change.
Title: Re: DSC Alarm System plugin
Post by: babgvant on July 10, 2012, 09:34:42 am
TBC, the problem isn't that the status in the UI isn't changing when I use the keypad (it is); it's that scenes (e.g. I have one setup to lock all the doors) aren't being triggered by the change.

I deleted the scenes and triggers, set them up again and now it's working. If it stops, are there any steps I can take to capture the state to try to figure out why?
Title: Re: DSC Alarm System plugin
Post by: guessed on July 10, 2012, 12:40:04 pm
@babgvant,
The most common cause of this is the DeviceId# changing.  We've seen this under UI4, for some plugins, when certain data corruptions events occur.

That said, in this case you indicated that the Scenes were firing when activated via the UI.  In the above case, the scenes would never fire (via the UI or via the Keypad) as the broken scenes would have been tied to the older DeviceID.

Looking at the deviceId's will give you a sense if this has ever happened.  They tend to be sequential, so if you ever see new ones allocated to a child-device "mid-stream" then you know this has occurred.


You didn't mention the MiOS Version you're running, but I inferred from other posts that you're running a Public Beta release.  One thing to check would be to rollback to the non-beta, and restore your config from there.  If that doesn't have the issue, then there's a problem with the Beta release that'll need to be sorted out by MCV and team.

In most cases, knowing the exact release# is important to solving these things as the problems are often localized to a specific release (esp the Beta releases)


TBC, the problem isn't that the status in the UI isn't changing when I use the keypad (it is); it's that scenes (e.g. I have one setup to lock all the doors) aren't being triggered by the change.

I deleted the scenes and triggers, set them up again and now it's working. If it stops, are there any steps I can take to capture the state to try to figure out why?
Title: Re: DSC Alarm System plugin
Post by: MTB on July 11, 2012, 01:49:18 pm
I am setting up my DSC1832 with the IT-100 and I have it connected to my Vera 3.  I installed the App and it appears to have loaded the device DSC Alarm Panel and also in Overview it has loaded the Security section.  This section has a triangle with system status Ready to Arm and out to the side it has five buttons.  The buttons say:

On (red) Away (black)
On (red) Stay (black)
On (red) Night (black)
Off (red)
(blank)

Below this it has each of my 8 zones and shows them armed except for my Zone 1 (two doors with delays).
Does this sound right?  Also, the upper status area for the Vera keeps cycling thru Unit Busy, then Opening I0 Port and then Running Lua Startup.  Is this normal?  I activated the alarm to arm it but did not see any changes in Vera????  Can someone help me get this working?  Do I have to set up scenes to arm and disarm the DSC?

After I make sure everything is working correctly, I will try to set up my WiFi RN-134.

I just looked under Devices - Sensors and see each of the zones.  The funny thing is that as I said above, the APP or code keeps running and each time or every other time the Zone 1 sensor drops off the screen then when it runs the next time it pops back on - on and on????  My DSC 1832 keypad shows not alarms or problems???

Update: I figured out the problem.  I had somehow entered a 1 under smoke alarm when adding my 6th and 7th zones.  So I had two Zone 1 entries and this must have freaked the program out.  I uninstalled the App and then reloaded it.  All is well.   After this, all is working well.  Will tackle the RN-134 tomorrow!

Thanks!
Title: Re: DSC Alarm System plugin
Post by: guessed on July 12, 2012, 12:43:07 am
Update: I figured out the problem.  I had somehow entered a 1 under smoke alarm when adding my 6th and 7th zones.  So I had two Zone 1 entries and this must have freaked the program out.  I uninstalled the App and then reloaded it.  All is well.   After this, all is working well.  Will tackle the RN-134 tomorrow!
Cool.  I was about to update this posting, then noticed that you'd solved it already.  Yes, there are no guards in the code against putting in dup Zone#'s across the config parameters, so no doubt that causes problems.

Note that the "Arm/Bypass" state of a MotionSensor (Zone) isn't specifically managed by the Plugin.  Only the "running man" (or "door") icon is controlled, and the other often gets used for storing scripting state (etc).... at least for the DSC.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on July 12, 2012, 01:16:09 am
Glancing at the changes, should this not effect my app? I should load the changes onto my Vera lite to see if it does.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on July 12, 2012, 01:28:47 am
Glancing at the changes, should this not effect my app? I should load the changes onto my Vera lite to see if it does.

- Garrett
Which change are you referring to Garrett?
Title: Re: DSC Alarm System plugin
Post by: garrettwp on July 12, 2012, 01:32:58 am
The change that you made for the icon support (Changeset 85). I noticed that the service was changed from urn:micasaverde-com:serviceId:AlarmPartition2 to urn:micasaverde-com:serviceId:DSCAlarmPartition1.

http://forum.micasaverde.com/index.php?action=post;quote=79186;topic=6393.90;last_msg=79186

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on July 12, 2012, 01:36:03 am
For Control Points, the change in changeset 85 is benign.

The change involved adding a new stateVar just to drive the Vera dashboard UI.  All the existing (and standard) stateVars that you use will continue to operate as normal.  The change was to tell Vera, in the JSON file, to use a different state variable binding for the Lock icon.
Title: Re: DSC Alarm System plugin
Post by: meathead88 on July 12, 2012, 09:51:53 pm
Is there a way to control a DSC Alexor alarm panel with this plug in?
I have a TL260 network interface card installed in my Alexor box....
Title: Re: DSC Alarm System plugin
Post by: guessed on July 12, 2012, 10:26:59 pm
Is there a way to control a DSC Alexor alarm panel with this plug in?
I have a TL260 network interface card installed in my Alexor box....
It's for the DSC PowerSeries only.  You can check Panel compatibility with DSC IT100 and/or Eyez-on 2DS interface boards, since that's how it accesses/controls the panel.
Title: DSC Alarm System plugin
Post by: Raynaldg on July 16, 2012, 11:35:46 am
What is the last status about the 2DS sync problem?  I thought that it was resolved but I have that problem again (but a bit less frequently...) ?!?!
I should reboot my Veralite to make it working fine again
Title: Re: DSC Alarm System plugin
Post by: guessed on July 16, 2012, 12:47:02 pm
What is the last status about the 2DS sync problem?  I thought that it was resolved but I have that problem again (but a bit less frequently...) ?!?!
I should reboot my Veralite to make it working fine again
At this time, the 2DS Firmware .81 contains fixes for the known/reproducible issues.  There were additional problems that we weren't able to consistently reproduce in @oTi's environment... so it's likely there are still problems, just ones that are much harder to track down.

MiOS Version 1.5.408 contains an additional "fix" that reconnects to the 2DS if it's unable to contact it for a period of time.

Quote
37. Mantis 2282 : setsockopt(SO_KEEPALIVE)

which goes a fair way towards catching the cases where it goes silently.  Since it takes a while to detect the problem there will be a gap in the DSC Panel event timeline if this mechanism kicks in.

If users are consistently seeing problems within their 2DS environments they should start to engage the eyez-on support folks directly as it may be specific to that environment.  Feel free to continue to report them here also, since we may be able to determine a pattern (but a LOT of detail of your environment will need to be posted, routers/models, topology, #IP Devices, switches/models, DHCP Lease periods, etc)
Title: Re: DSC Alarm System plugin
Post by: Dolphran on July 16, 2012, 04:04:18 pm
Would it be possible for this plugin to report the state of a zone even if that zone's type in the 1832 is set to 00 (nul)?  In other words I want Vera to see the state change in a zone that the alarm system is set to ignore.

Also I asked earlier in this thread but got no response - it seems that I'm not getting appropriate alarm active/not active triggers in a DSC 1832 Walk Test.  When the 1832 does its two second alarm, the alarm active event is triggered but the not active one is not triggered when the 1832 restores after two seconds.  Can anyone else confirm they get this behavior too?  Any chance of it being fixed?

Thanks!
Title: Re: DSC Alarm System plugin
Post by: guessed on July 16, 2012, 04:19:31 pm
Would it be possible for this plugin to report the state of a zone even if that zone's type in the 1832 is set to 00 (nul)?  In other words I want Vera to see the state change in a zone that the alarm system is set to ignore.
The Zones setup by the configuration parameters will automatically follow the status updates presented by the IT100 or 2DS.  If it's not changing state in Vera's UI, then these Ignore-Zones are probably not being sent out by the IT100/2DS itself (or even more likely, not being sent out by the Panel)

One of the more advanced DSC Panel users here will probably be able to recommend another option.

BTW: In my Paradox, I setup a Second Partition/Area for these devices.  This keeps them separate from the main arming states (for Partition 1) but lets you use the Alarm Panel to monitor them (etc)...

Quote
Also I asked earlier in this thread but got no response - it seems that I'm not getting appropriate alarm active/not active triggers in a DSC 1832 Walk Test.  When the 1832 does its two second alarm, the alarm active event is triggered but the not active one is not triggered when the 1832 restores after two seconds.  Can anyone else confirm they get this behavior too?  Any chance of it being fixed?
Can you post a copy of the LuaUPnP.log file during that time period?

I've never tried the walk-test mode, so it's possible that different status messages are being sent during that setup.
Title: Re: DSC Alarm System plugin
Post by: strangely on July 16, 2012, 04:21:21 pm
Would it be possible for this plugin to report the state of a zone even if that zone's type in the 1832 is set to 00 (nul)?  In other words I want Vera to see the state change in a zone that the alarm system is set to ignore.
I have a couple of zones set up like this, although I will have double to check the programming as I may have them 24 hour non monitored in the alarm programming and they update fine; you just need to make sure that you have these zones configured in the plugin too!
Quote
Also I asked earlier in this thread but got no response - it seems that I'm not getting appropriate alarm active/not active triggers in a DSC 1832 Walk Test.  When the 1832 does its two second alarm, the alarm active event is triggered but the not active one is not triggered when the 1832 restores after two seconds.  Can anyone else confirm they get this behavior too?  Any chance of it being fixed?
I've never tried this as a result of a walk test, but I know that an "alarm" does work! Maybe due to this only being a test, perhaps the IT100 or 2DS do not receive this?

**Edit** so it looks like from the last backup I have, I can see that at least one of the zones is set up "24 Hour non Alarm" (26):
The other two that I have I cant see since I'm not sure the backup I have is the latest, and I made a change to them recently.
Title: Re: DSC Alarm System plugin
Post by: Dolphran on July 16, 2012, 05:48:24 pm
I didn't know about zone type 26 ("24 Hour non Alarm").  That should do the trick.  Thanks!

I'll try to set up a debug run on the Walk test to provide more info (may not have time for this right away).  I better change the Alram scene to change the state of a light instead of my Z-Wave siren - otherwise its quite an anoying test when it fails to shut off!

Title: Re: DSC Alarm System plugin
Post by: Brientim on July 16, 2012, 06:04:44 pm
I didn't know about zone type 26 ("24 Hour non Alarm").  That should do the trick.  Thanks!

I'll try to set up a debug run on the Walk test to provide more info (may not have time for this right away).  I better change the Alram scene to change the state of a light instead of my Z-Wave siren - otherwise its quite an anoying test when it fails to shut off!

I suggest the best way to test this is utilising the mobile portal to your 2DS directly. I remember a comment earlier in the post or on the Eyez-On forum where someone was using the iPhone with the $5.99 DSC Alarm app to do this. If that is true, when you establish the walk test form the panel, it should be easy to identify if it is transmitting via the 2DS and then once this is known, you can do the same for you Vera.
Title: Re: DSC Alarm System plugin
Post by: strangely on July 17, 2012, 03:07:40 am
I started to get a lot of TPI disconnects today and my 2DS seems to be showing its running on version 01.07.89 (believe it was 01.07.81 previously); not sure its related, but will take a look a bit more tomorrow with a tcpdump if they persist.

The Eyes-on site has no mention of 01.07.89
Title: Re: DSC Alarm System plugin
Post by: guessed on July 17, 2012, 10:29:31 am
It will definitely disconnect, in quick succession, when a firmware upgrade occurs.  Are they spread out, or clustered together?  ... Did Vera reconnect?
Title: Re: DSC Alarm System plugin
Post by: oTi@ on July 17, 2012, 10:35:24 am
I had some recent events also; which I left un-investigated. ::) However, my 2DS is still indicating build 81.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on July 17, 2012, 10:54:40 am
The other day I was receiving network disconnect emails from eyes-on. They eventually stopped. Maybe a network issue on their end?

- Garrett
Title: Re: DSC Alarm System plugin
Post by: Brientim on July 17, 2012, 11:00:42 am
As I indicated 10 Jul, I was at .83 beta see http://forum.micasaverde.com/index.php/topic,5154.msg78943.html#msg78943,

As far as I remember, there were 3 additional code releases this week, 0.84, 0.87 and now 0.89.

In addition, it could be a result of issues with there servers Which should now be resolved accordining to their forum. This would explain what @strangely reported. Maybe @strangely amend you post reference on their forum and this to suggest that Firmware release should be proceeded by an email notification or an registered event when they force the update as a special event.

http://forum.eyez-on.com/FORUM/viewtopic.php?f=6&t=390&sid=91bf8d1efd137e0ef25e3facdaea2566
GrandWizard   
 Post subject: Re: Service Interruption - **Fixed**Posted: Sun Jul 15, 2012 5:09 pm 

Posts: 268   
We had to switch to a backup server yesterday that had a bug in the alerting engine but everything has been restored so you shouldn't see a problem now. Are you referring to an alert you received today? July 15?

EDIT: I've been told that about 5% of our customers are still on the auxiliary server so it is possible that you are one of them and still receiving the wrong partition. This should be fixed by Monday morning, EDT.
Title: Re: DSC Alarm System plugin
Post by: strangely on July 17, 2012, 11:41:17 am
I saw the server issue they posted there but this started to occur yesterday so I discounted it.

I got a PM back from @Grandwizard that there was a minor update stating that it was pushed to some beta users by mistake, and will be pushed to a wider audience later!

Anyhow, it looks like it stopped after just after veras LuUPNP process restarted shortly after 3:00AM... I always get a TPI restart at this time anyway due to the nightly heal that Vera does!
Title: Re: DSC Alarm System plugin
Post by: garrettwp on July 17, 2012, 11:47:25 am
Around 6-7AM EST I was getting the alarm network disconnects via email.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: rwalker on July 17, 2012, 12:12:16 pm
Running a 2DS and when I first got it working I had to manually upload the files.  I went into the app store and got the latest version which fixed the disconnects, but I now have 2 "DSC Alarm Panel" devices.  The new one is showing attached to the "app" how can I swap them and get rid of the new one?

Thanks,
Roy
Title: Re: DSC Alarm System plugin
Post by: guessed on July 17, 2012, 12:12:50 pm
@strangely,
I'm not too worried about yours, since Vera is quickly reconnecting within a few seconds.  The bigger question on the table is why your 2DS is rebooting sooooooooo often.  It'll definitely do that if it has problems phoning home (to the hosted service) but that seems a little aggressive.

You'll want to ping K and see if he has extra data for those timeslots.
Title: Re: DSC Alarm System plugin
Post by: Brientim on July 17, 2012, 12:21:35 pm
@strangely,

No corresponding events matching your times, which rules out any server interruptions as a possible cause. Do you have any networked scheuled activities during these times, such as backups etc?
Title: Re: DSC Alarm System plugin
Post by: Brientim on July 17, 2012, 12:25:15 pm
I saw the server issue they posted there but this started to occur yesterday so I discounted it.

I got a PM back from @Grandwizard that there was a minor update stating that it was pushed to some beta users by mistake, and will be pushed to a wider audience later!

Anyhow, it looks like it stopped after just after veras LuUPNP process restarted shortly after 3:00AM... I always get a TPI restart at this time anyway due to the nightly heal that Vera does!

Firmware now pushed back to .81
What I would note is the list of events are as far as I can establish immediately after .89 was pushed out.
Title: Re: DSC Alarm System plugin
Post by: djmillett on July 19, 2012, 07:39:17 pm
Not sure if this is correct place to post this...

I always get an Invalid Service error when trying to ARM or DISARM my alarm.  Any ideas on what this means.

Vera2 running UI5, Firmware 1.5.408, DSC plugin version 0.37, using IT100. 

Replaced USB to serial converter and same error.  I've tried removing and re-installing the DSC plugin multiple times.

Title: Re: DSC Alarm System plugin
Post by: guessed on July 19, 2012, 07:48:48 pm
Not sure if this is correct place to post this...

I always get an Invalid Service error when trying to ARM or DISARM my alarm.  Any ideas on what this means.

Vera2 running UI5, Firmware 1.5.408, DSC plugin version 0.37, using IT100. 

Replaced USB to serial converter and same error.  I've tried removing and re-installing the DSC plugin multiple times.
Screenshot?  We'd need to see where you see this error, and what exactly it looks like, as that will likely give folks more clues on how to chime in.
Title: Re: DSC Alarm System plugin
Post by: djmillett on July 19, 2012, 08:17:21 pm
Adding screenshot
Title: Re: DSC Alarm System plugin
Post by: strangely on July 19, 2012, 10:21:15 pm
Not sure if this is correct place to post this...

I always get an Invalid Service error when trying to ARM or DISARM my alarm.  Any ideas on what this means.

Vera2 running UI5, Firmware 1.5.408, DSC plugin version 0.37, using IT100. 

Replaced USB to serial converter and same error.  I've tried removing and re-installing the DSC plugin multiple times.

Did it ever work?
Have you tried it from a scene?
Have you followed the steps in the wiki to make sure you have it configured to be able to allow arm and disarm?
Title: Re: DSC Alarm System plugin
Post by: djmillett on July 19, 2012, 10:32:54 pm
I had it working a few months ago.  At some point it stopped working.
I have not tried it from a scene
EnableRemoteArm is set to disarm.  Is there anything else that must be set?
The other interesting thing is that I no longer get notifications of the alarm being set or triggered that I had previously setup.  I've tested other notifications and they work.
Title: DSC Alarm System plugin
Post by: Brientim on July 19, 2012, 10:37:42 pm
Have you verified the it100 and serial port configuration?
Title: Re: DSC Alarm System plugin
Post by: djmillett on July 19, 2012, 10:44:56 pm
I believe the it100 and serial port are at least partially working.  When I arm the alarm using the keypad I see the status change to exit delay in progress but then the status never changes to armed.  Has the it-100 gone bad?
Title: Re: DSC Alarm System plugin
Post by: strangely on July 19, 2012, 11:21:05 pm
Maybe check your connections? Also perhaps the serial port settings and baud rate? Sounds like maybe you only have one way communications with it!
Title: DSC Alarm System plugin
Post by: Raynaldg on July 19, 2012, 11:52:21 pm
Ok, I had a very strange bug about the sync issue.

1.  I was arming my system in stay mode with keypad
2.  I tried to disarm it with a Veralite scene "disarm system", but nothing append because of the sync problem.
3.  I was rebooting my Veralite.
4.  The DSC received a TPI login followed by a Away arming ?!?!?!

DSC firmware : 1.07.90
Veralite firmware : 1.5.408

Here is some screenshots...
(http://img.tapatalk.com/adb1c862-d606-3f51.jpg)
(http://img.tapatalk.com/adb1c862-d4d4-2f6b.jpg)
(http://img.tapatalk.com/adb1c862-d51c-38d8.jpg)
Title: Re: DSC Alarm System plugin
Post by: Dolphran on July 20, 2012, 10:43:19 am
Regarding my earlier reporting a Walk Test problem - I was getting a Vera Alarm trigger but not disarm.

It turns out this is not just a Walk Test problem.  We accidently triggered a real alarm last night - The Vera scene that turns on the ZWave siren was triggered, but when we canceled the alarm at the DSC Keypad, the ZWave Siren did not shut off.  This creates a rather frantic moment with small kids in the house.  Eventually I got a browser open and shut the siren off manually.  I double checked my scene that is supposed to shut the siren off - its trigger is specified (via the two drop downs) as Type of Event: "Alarm Active", and Is Active? "Device: Alarm is not active".  Perhaps this is not the right way to specify the trigger - it seemed to me that this should trigger whenever an alarm becomes inactive.  I will now try this alternative trigger definition - Type of Event: "Alarm State", and Is Armed? "Device is disarmed".

What is the expected difference between these two trigger definitions?

BTW this is on a Vera Lite with 1.5.408
Title: Re: DSC Alarm System plugin
Post by: vicw on July 21, 2012, 12:44:58 pm
I currently have a working DSC alarm system with a functional Envisalink IP100D interface, and I'm happy with the access and management via browser and mobile android apps, but I would really like to be able to use the plugin just for the purpose of generating triggers, in the case that an alarm condition occurs.

The description of the plugin doesn't include any mention of compatibility with the Envisalink IP100D, so I'm not sure it can be used.  I have tried to connect with it, but my initial results haven't been too successful.

Bottom line, rather than spend a great deal of time experimenting, I would really appreciate if the developer, or any other users can tell me if the plugin really is compatible with the Envisalink !P100D.  I'm considering an upgrade to the 2DS, but would like to use my current configuration for the time being.
Title: Re: DSC Alarm System plugin
Post by: guessed on July 21, 2012, 01:24:37 pm
@vicw,
From memory, the IP170D became the 2DS, so the IP100 likely won't work.  You'd have to check with the eyez-on forum as to what compatibility is between the various device models.

Right now, we're set to only handle the original DSC IT100 and the Envisacor 2DS.
Title: Re: DSC Alarm System plugin
Post by: vicw on July 21, 2012, 01:57:04 pm
@guessed 

Thanks for the response. I think you are most likely right. Unless a IP100D owner reports success, I'll likely go for the upgrade to the 2DS soon.  They have a trade-in program, which lessens the expense somewhat.
Title: Re: DSC Alarm System plugin
Post by: Dolphran on July 21, 2012, 04:56:40 pm
Ok, sorry for the brain f*rt.  Obviously disarmed and alarm not active (restored) are not the same thing.  So I still don't know why my Z-Wave siren isn't shutting off.  At this point I'm suspecting a problem with the Z-Wave message getting to the siren succesfully.  Perhaps a heal is in order.  I may get some opportunity to debug this further before the weekend is over.  Since shutting off the siren is so important, I may modify the scene that shuts it off to do so every second for a few seconds to gaurantee the message gets through.
Title: Re: DSC Alarm System plugin
Post by: strangely on July 21, 2012, 05:18:47 pm
@guessed 

Thanks for the response. I think you are most likely right. Unless a IP100D owner reports success, I'll likely go for the upgrade to the 2DS soon.  They have a trade-in program, which lessens the expense somewhat.

The IP100 for sure won't work with this plugin; however there is a seperate IP100 plugin with some basic functions.
Title: Re: DSC Alarm System plugin
Post by: Mikey on July 28, 2012, 09:53:59 am
With a dwindling WAF on the inconsistency* with my IT-100 / Wiznet combo interacting with my Vera, I think I may try the 2DS.  Anyone interested in starting up their own HA security integration project and/or would like a backup at a reduced cost should PM me.

-Mike

* Inconsistency = works fine for a few days but then connectivity between the integration card and the Vera (established through ethernet-over-powerline adapters)
Title: Re: DSC Alarm System plugin
Post by: strangely on July 28, 2012, 12:14:56 pm
I've never had any problems with my WIZnet/IT100 that weren't caused by earlier version of UI4. If you are having problems then I dont think a 2DS is going to be the answer!

I would suggest taking a look at the environment its in first. What have you done so far to troubleshoot?
Title: Re: DSC Alarm System plugin
Post by: Mikey on July 29, 2012, 02:06:51 am
I've never had any problems with my WIZnet/IT100 that weren't caused by earlier version of UI4. If you are having problems then I dont think a 2DS is going to be the answer!

I would suggest taking a look at the environment its in first. What have you done so far to troubleshoot?
Not sure where to start...there are several of my posts within this thread that have detailed my various pitfalls with accompanying tweaks on various aspects, e.g. networking changes, plugin setting changes, physical configurations (within in the box), etc. none of which have really panned out.

In the end, what you/others have seemed to confirm - and that I can verify - is that the Vera can communicate with the Wiznet card in some way and, if both are powered down for a sufficient period of time, they'll operate completely fine for a few days until their integration breaks again.  At this very moment, both the Vera and the Wiznet both know that the other exists [through a ping].  The Wiznet is physically connected without cable to the DSC card, which is - and perpetually has been - dutifully blinking every half second to suggest proper functionality.  In some twisted way, I look forward to our next power outage, because then I'll know I'll have a few days of functional security integration with the Vera!  :D

Anyway, the 2DS consideration also at least allows me to forward port traffic directly to it outside of Vera and use a separate mobile app to interact with it.  If nothing else, there's potential there to get remote security system control working in some reliable way, even if I need to cut MCV out to perform that particular critical task.

Again, understand the WAF limitation here...neither she nor I can reliably control the security system, which was the whole point of the hardware investments and, subsequently, using the plugin.  That said, I certainly do not blame the software - you guys have done a spectacular job on this thread with the loyal fan base - but piecemealing parts together, e.g. a DSC integration card connected to a serial-to-IP adapter (with awful support itself) connected to an ethernet-over-powerline or bridged router (if only until a wired connection can be put in), doth not a sustainable and reliable solution make.  Too many sources for problems.

So I'm glad to hear that you and others have a solid setup with the same hardware, but I don't, and if the 2DS doesn't solve it - if only to pull the Wiznet out of the solution for simplicity's sake - then I'm going to look at other z-wave HA options, i.e. to salvage my investment in various devices, e.g. locks, thermostats, etc. without having to deal with the instability of MCV as a whole. (probably a different subject, but this issue is a symptom of the larger deal)

By my own admission, I don't have the advanced knowledge of, say, how to analyze TCP activity to further evaluate my problem.  Frankly, I wanted to solve it - or subject this issue to dissection - for my own learning and the betterment of the community, the plugin, and MCV's value as a whole.  If you think that I can avoid another expense to solve this, then I need to understand exactly what "troubleshoot...my environment" means because I have followed the wiki entry and this thread's suggestions to the letter and utilized a reasonably technical capacity all, thus far, to no avail.  But if that level of support is beyond the community's scope - either as plugin author or technical expert - that's fine too.  I would respect - and in many ways expect - that. 

Sorry for the modest rant, and I have all the respect and sincerest thanks for what you guys are offering to users.  I hope to offer much the same to others, if only in contributions on what not to do or to avoid.  For now, wish me luck with the 2DS to at least verify a HW issue with an existing device.  If it doesn't work, well, I've got 30 days to return it, and a good amount of time to start liquidating other HA investments that aren't proving valuable either.

Keep up the good work, and I hope to report a successful swap of hardware solving my problem.

Respectfully,
-Mike
Title: Re: DSC Alarm System plugin
Post by: vicw on July 29, 2012, 02:44:01 am
@Mikey

I can't comment on the hardware you've been using, but I can tell you that I've been using an Envisalink IP100D to control, monitor and report on my DSC system for over a year,  via mobile (Android) DSC Alarm Monitor app and the Eye-Zon mobile Web pages with 100% reliability. You will never find a more responsive and helpful source of support than Eyez-On,  and the Envisalink board is incredibly easy to set up and use.

 I've only been working with the Vera for a few weeks,  and I love using it for controlling lighting and monitoring temps and humidity,  but I don't think it would consider assigning it management and control of the security system. My only objective in tying my DSC/Envisalink interface to Vera is to capture Alarm Conditions from DSC, and trigger scenes that will turn on lights in the case of an alarm. I just received a 2DS board to upgrade from the IP100D in order to make that possible. I'll be installing the 2DS in the morning,  so I should know soon if I will be able to capture the events into Vera.

 2
Title: Re: DSC Alarm System plugin
Post by: strangely on July 29, 2012, 02:49:22 am
@Mikey, I wont discourage you from buying the 2DS, as it does provide the best of both worlds (I'm very happy with mine), and less complication on the connectivity front, however I do encourage you first to perhaps consider a bit more troubleshooting first as I'm always very suspicious of those power-line network adapters since there are a lot of variables affecting the speed those things will sync at, and also noise variables on the lines etc! I'd hate for you to buy one and find it doesn't work any better for you.

Is there any way you can temporarily bypass the power line adapter and maybe slave in a long cable for a few days to assess it? Or alternately move the IT100 to perhaps somewhere else on the keybus where it might more convenient to hook it up to your network? ... Or if neither of these are possible, then how about a wireless bridge?

Also the trouble is with a ping is that it isn't always very good to diagnose an intermittent connection issue, and especially with the default packet size, so you should make it larger if you haven't already... -l in windows and -s in linux/OSX etc.
Title: Re: DSC Alarm System plugin
Post by: guessed on July 29, 2012, 11:03:50 am
@Mikey,
If the PLE is adding any sort of instability in the connection, then the Vera<->PLE<->2DS will have similar problems.

MiOS .401 release added a work-around that better detects dead connections and attempts to reconnect.  In prior releases, these bad connections would continue undetected...forever. Giving the impression that Vera and the network device were connected when they really weren't.

This would lead to loss of alarm/panel state updates in Vera.

The .401 detection mechanism isn't perfect, since the device can still go for some time (10+ minutes) of being bad before its detected and corrected, but its a ton better than the previous situation.

Anyhow, if you're planning on switching to the 2DS, I'd recommend using the .408 MiOS version if you aren't already.

...obviously, the closer you can get Vera to the IT100, and the more 'things' you can remove between them (PLE, extra switches, etc etc) the easier it gets to diagnose any resulting problems.
Title: Re: DSC Alarm System plugin
Post by: StephenMorris on July 29, 2012, 03:33:24 pm
I've been happily using my IT100 and DSC and your plugging on U4 for over a year, mostly to monitor alarming and to do remote alarm enable/disable.
Now, I want to catch events sent by individual devices, specifically two high water alarm sensors that are on the DSC system.
As it is currently configured, these are showing up as Smoke detectors. Will they trigger properly as 'smokes' instead of water sensors?
Is there some reasonable way to make the appear as water sensors?
It looks like I could try and change the device type and xml file, but I am hesitant to do that without some advice from you guys.

FYI, my use case is to detect water in the basement, and when triggered, turn OFF power to the Well Pump.
This is in a second home, and with this in place I will worry a lot less about the house trying to empty the well into the basement if there is a plumbing problem.

I have a Vera 3 on order as an upgrade, so if the answer is to wait and do it in UI5, I'm OK with that answer too.

Thanks much, this has been working like a champ for me.

  Steve
Title: Re: DSC Alarm System plugin
Post by: guessed on July 29, 2012, 03:46:53 pm
There are a fixed number of predefined SecuritySensor devices. From a scripting/scene standpoint these all behave the same way, with the same functions.

Newer UI5 releases use different dashboard Icons to differentiate them visually, as do some of the control points (Authomation, Automator.app, for example)

No real need to change them.  That said, when they are changed their device# also changes.  Any existing scripts against the old device# no longer activate.

Built in ones are for Motion, Door and Smoke (oddly, not one for Window)
Title: Re: DSC Alarm System plugin
Post by: vicw on July 29, 2012, 03:59:15 pm
@anonymark,
We have a parameter that can be set to override the default parameter.  It's just not bubbled up in the UI, or "preconfigured" in the Advanced tab, but it's there if you need to create it.  It was deliberately left out as I didn't want to confuse the typical user with requests for a password.

Anyhow, if you want to set it then use the Advanced Tab, using the fields at the bottom of the UI:

ServiceId: urn:micasaverde-com:serviceId:DSCAlarmPanel1
Variable Name: InterfacePassword

If not set, or not present, it defaults to the default passcode for the 2DS  ;)

WARNING: Everything configured here goes into Vera-maintained configuration files.  These may get backed up to MiOS Servers.  There's not a lot of protection of this data, so you'll want to avoid using "secret" passwords ;)


Strangely,

I defaulted  the 2DS password and everything began working. I deleted and installed the .37 update and it works perfectly also. Unfortunately, I'm working a double shift today and tomorrow (well today and today now). I'll post up exactly what's going on once I have a chance to look at it tonight. Thanks for the password suggestion on the 2DS. I always change default passwords......Guess that was bad for once.

PS.  I'm running the Vera and 2DS behind a gigabyte switch on the same subnet.

I just installed my new 2DS today. Almost everything went easily, but I encountered the Password issue on the 2DS plugin, as soon as I changed the value from the default. I tried the suggested added variable, installing it on the DSC Alarm Panel Advanced settings, and it looks to be properly setting, but has no effect on the outcome. The plugin seems to continue to expect the default value, ignoring whatever I put in the InterfacePassword variable.

The data from Vera shows this line under <states> which looks good to me.
<state service="urn:micasaverde-com:ServiceID:DSCAlarmPanel1" variable="InterfacePassword" value="XXXXXX" id="0"/>
(The actual data shows the content of my Password - I'm just X'ing it here for privacy.)

I understand the concern about password data being exposed in the micasaverde database, but I"m much more concerned about leaving that value in a default state on my system.  Oddly, when I had used the IP100D version, it included the UserID and Password fields, without this awkward and difficult to remember procedure, and it worked for me. If I have erred in my entries, or there is a fix available, I'd really appreciate some guidance.
Title: Re: DSC Alarm System plugin
Post by: guessed on July 29, 2012, 04:19:03 pm
The serviceId strings are case-sensitive, they must be exact matches
Title: Re: DSC Alarm System plugin
Post by: vicw on July 29, 2012, 06:45:13 pm
The serviceId strings are case-sensitive, they must be exact matches

You are exactly right, of course.  It took me three tries, but I finally got both of the case problems resolved, and it's working normally now. Thanks for the help.

Does this little odd procedure prevent the password from being sent out to micasa?
Title: Re: DSC Alarm System plugin
Post by: guessed on July 29, 2012, 06:54:13 pm
Does this little odd procedure prevent the password from being sent out to micasa?
Nope, they don't provide any built-in mechanisms to do it.  It's mostly just a "it's not secure anyhow, so why bother" type thing. 

All Service Variables, as well as the IP Address and MAC Address of anything on your Network, are sent over to the MiOS Servers.  ... yes "all"

I don't want to give people the illusion there's any form of security here, and if they could [easily] set a password, they'd be tempted to use one that represents something else that is secure...  It's all somewhat moot, since the 2DS traffic is all in clear-text, so anything already on your Network can probably capture it.
Title: Re: Re: DSC Alarm System plugin
Post by: vicw on July 30, 2012, 12:16:22 am
Does this little odd procedure prevent the password from being sent out to micasa?
...

All Service Variables, as well as the IP Address and MAC Address of anything on your Network, are sent over to the MiOS Servers.  ... yes "all"
...

I'm hoping that the IP and MAC addresses on your network that you refer to are any of those included in the data included in and used by Vera,  not all of the addresses on my entire home network - true?

Title: Re: DSC Alarm System plugin
Post by: guessed on July 30, 2012, 12:20:01 am
Unravel a copy of your user_data JSON file (see /etc/cmh/ for examples) and see for yourself what it captures... And then backs up to the MiOS servers...

eg. The ip_requests content of the JSON

You can extract this using:
Code: [Select]
root@MiOS_nnnnnn:/etc/cmh# pluto-lzo d user_data.json.lzo tmp.out

UPDATE: Augmented with the specifics for folks wanting to do it from the command line on Vera, along with the specific JSON piece that contains the data of interest.
Title: Re: DSC Alarm System plugin
Post by: vicw on July 30, 2012, 12:40:51 am
Now you are scaring me!  I'll check that out in the morning.

This whole adventure has been to enhance my security system,  not expecting it to provide an open schematic of it to the world.

 2
Title: Re: DSC Alarm System plugin
Post by: garrettwp on July 30, 2012, 12:58:04 am
Unless you are security paranoid, I would not loose sleep over it. Guessed is just pointing it out to make sure you are aware. The data is sent / backed up to MCV's servers over a ssh connection. However, who knows how the data is being saved on their end. So use your good judgement.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on July 30, 2012, 01:43:29 am
Guessed is just pointing it out to make sure you are aware.
Yup, I believe in open disclosure so people can make educated choices.

Quote
The data is sent / backed up to MCV's servers over a ssh connection. However, who knows how the data is being saved on their end.
Yes and no.  In UI4, backup files are transported over HTTPS, so their data is protected in flight.  Log files, which can contain similar values are compressed and sent, over un-encrypted FTP, to ftp://logs.micasaverde.com(1)) using a single write-only account(2)

They don't appear to use the SSH tunnel they've established for remote access to further protect this data (but I could be wrong).

So anything logged to the log files is effectively being sent over the internet in a decodable format... if someone were so-inclined, and had access to the in-flight data stream, or DNS subversion.

I haven't checked UI5 to see if the logic remains the same.  I see that the release notes shows them moving over to curl, from ftpput, for at least part of this stuff (presumably to avoid Vera hangs, due to transient connectivity problems, that used to frequently occur in log rotation)

REF: (1), (2) /usr/bin/Rotate_Logs.sh
Title: Re: DSC Alarm System plugin
Post by: garrettwp on July 30, 2012, 01:50:04 am
You are right. I believe the ssh connection is only for the remote access. I forgot that the data was backed up over ftp. I have to do some digging to see what they use in UI5. I doubt things have changed.

- Garrett

Update:

Looked at the backup script "/usr/bin/backup-store.sh" and it does a backup via https.
Title: Re: DSC Alarm System plugin
Post by: guessed on July 30, 2012, 01:59:08 am
Yes, it's a little odd to go to all the effort of building a [secure(1)] SSH Tunnel and then proceed not to use it for all communications.  I assume this is to allow backups (etc) to occur independent of remote access, or just for performance/cost-of-scale-out reasons.

(1) From memory, @futzle pointed out potential issues with this in a prior thread, but I can't find it right now.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on July 30, 2012, 02:01:34 am
I just updated my previous post. The backups are done over https via a custom php script they have on their end.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on July 30, 2012, 02:07:49 am
Yep, as I list above, HTTPS is just for the user_data JSON backups. 

I re-validated the Rotate_Logs.sh, and it's moved to using CURL, but is still using an unencrypted FTP to stream the Log data (although they made a minor cutover from ftp://logs.micasaverde.com (UI4) to ftp://logs.mios.com (UI5)
Title: Re: DSC Alarm System plugin
Post by: vicw on July 30, 2012, 12:36:21 pm
Unravel a copy of your user_data JSON file (see /etc/cmh/ for examples) and see for yourself what it captures... And then backs up to the MiOS servers...

eg. The ip_requests content of the JSON

You can extract this using:
Code: [Select]
root@MiOS_nnnnnn:/etc/cmh# pluto-lzo d user_data.json.lzo tmp.out

UPDATE: Augmented with the specifics for folks wanting to do it from the command line on Vera, along with the specific JSON piece that contains the data of interest.

You were kind enough to go back and provide guidance for the uninitiated, but I'm embarrassed to admit that I still find myself struggling with it. 

When you say the command line on Vera, is there a command line within the micasaverde Vera UI (which I can't find), or do you mean the browser command, or address line?

Also, how much of the coded line you provided is literal? I'm assuming the "nnnnnn" may require the actual vera device number, or perhaps its  IP address, and that perhaps "user_data" might need the actual file name.  Other than that, is there anything else on that line that needs to be customized? If you know of a reference document that would help, don't hesitate to direct me there, rather than spend too much of your time and effort bringing me up to speed.
Title: Re: DSC Alarm System plugin
Post by: garrettwp on July 30, 2012, 12:41:40 pm
The command line guessed is referreing to is the command line via ssh.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: oTi@ on July 30, 2012, 12:44:03 pm
Also, see this wiki page (http://wiki.micasaverde.com/index.php/Logon_Vera_SSH).
Title: Re: DSC Alarm System plugin
Post by: guessed on July 30, 2012, 12:50:04 pm
You can probably also just get it through the user_data URL:
    http://forum.micasaverde.com/index.php/topic,6780.msg43093.html#msg43093

I've never validated it, but I'd guess it'd work also.... I'm just more used to working old-school with Vera's command line. 

See this older discussion on the topic:
    http://forum.micasaverde.com/index.php/topic,10965.msg77359.html#msg77359
Title: Re: DSC Alarm System plugin
Post by: vicw on July 30, 2012, 03:58:45 pm
Thanks @garrtwp, @oTi & @guessed, for your help. I was able to get the user data with:

http://[IP Address]:3480/data_request?id=user_data&output_format=xml
http://[IP Address]:3480/data_request?id=user_data&output_format=jsn
&
http://[IP Address]:49451/data_request?id=user_data&output_format=xml

It didn't include my social security number, home address, phone number or apparently any other personal data, at least on a quick search, but as you had indicated, it does include all of the active IP addresses and MAC codes on my system, not just those directly related to my use of Vera lite 3, since I installed it, and of course, my password used on the 2DS app.

I guess we are dependent on security control of the files themselves, which from your discussion, may or may not be fully protected in transit, and who knows how protected while resident at the server.

I'm not completely paranoid, so while not happy with the exposure, I don't think there is a probability that it will be maliciously misused, but maybe I don't know enough yet to understand all of the risks. As a layman, new to Vera, it does seem unfortunate that they haven't included encryption at least for the most private data, such as passwords and such. I don't think  that would be all that difficult to accomplish.

What I really don't understand yet is where the servers are, who manages and controls them, and how they they liaison with users like me, and developers like you. I'll be eagerly following any security discussions you engage in, and hope to learn from them.
Title: Re: DSC Alarm System plugin
Post by: Dolphran on July 30, 2012, 06:02:24 pm
Is there any plan to expose the PGM outputs as binary switches?
(My apologies if this has been asked and answered already)
Title: Re: DSC Alarm System plugin
Post by: guessed on July 30, 2012, 07:23:53 pm
For 2DS users, this will let you request PGM changes:
    http://forum.micasaverde.com/index.php/topic,5154.msg76090.html#msg76090

something similar is available on an IT100, but it's a lot more elaborate to enable it.  It's a little difficult to map these to a switch, since "current state" isn't always possible to determine.

A more accurate UI representation would be like a pushButton, where "current state" isn't represented.
Title: Re: DSC Alarm System plugin
Post by: meathead88 on July 30, 2012, 09:31:59 pm
Is there a way to control a DSC Alexor alarm panel with this plug in?
I have a TL260 network interface card installed in my Alexor box....
It's for the DSC PowerSeries only.  You can check Panel compatibility with DSC IT100 and/or Eyez-on 2DS interface boards, since that's how it accesses/controls the panel.

Thanks for the reply but it seems as though the IT100 will not work with the newer Alexor panels :( 
Will there be any dev time on the Alexor w/TL260 card?  I had the Alexor installed so I could have wireless sensors all over the place :0 now I need to integrate into home automation....



Title: Re: DSC Alarm System plugin
Post by: guessed on July 30, 2012, 10:37:45 pm
Thanks for the reply but it seems as though the IT100 will not work with the newer Alexor panels :( 
Will there be any dev time on the Alexor w/TL260 card?
I have no plans to write one, but your best bet would be to find another Vera user that has the Alexor Panel, and can code up a suitable Plugin... if it's possible (not all systems advertise their API's).
Title: Re: DSC Alarm System plugin
Post by: legend99 on August 09, 2012, 07:24:50 pm
Hi Guys,

I have a problem, I have Vera2 running UI5. Installed Envisalink 2DS. (works great through the web). Installed the DSC plugin and it installs the DSC device.

Now what is happening is that the device says Lua failure lua failure.

I have tried uninstalling it and reinstalling, same problem.

The only thing I can see is that in the advanced tab it says; Commuse: RS232 could that be the problem?



Title: Re: DSC Alarm System plugin
Post by: strangely on August 10, 2012, 12:16:58 am
The only thing I can see is that in the advanced tab it says; Commuse: RS232 could that be the problem?

Nope thats fine!

-Are you sure you have its IP correct?
-When you say, "(works great through the web)" do you mean through its local page, or from the eyez-on website? If this was on its local page,       then have you registered the device on the eyez-on site? If not then you need to do this as its likely its running and old version of the code without the automation interface (TPI) and the plugin will not work.
-Do you have it selected as 2DS in the parent device? (selection should be a darker blue)

Title: Re: DSC Alarm System plugin
Post by: legend99 on August 10, 2012, 12:27:12 am
Thanks strangely.


-Are you sure you have its IP correct?
Yes checked it and doubled checked it.

-When you say, "(works great through the web)" do you mean through its local page, or from the eyez-on website? If this was on its local page,       then have you registered the device on the eyez-on site? If not then you need to do this as its likely its running and old version of the code without the automation interface (TPI) and the plugin will not work.

Through the eyes-on website. Firmware on the 2DS was updated today to Firmware Version: 01.07.90

-Do you have it selected as 2DS in the parent device? (selection should be a darker blue)

I try to click on the 2DS but when I get and error that says Device Communication Error. It thinks I am using the DSC-IT200 because that is what is dark blue.


Title: Re: DSC Alarm System plugin
Post by: legend99 on August 10, 2012, 12:35:00 am
Hmmm, under the Advanced tab, InterfaceType, it said IT200, I changed that to 2DS, and reloaded Vera and now works.


Thanks


The only thing I can see is that in the advanced tab it says; Commuse: RS232 could that be the problem?

Nope thats fine!

-Are you sure you have its IP correct?
-When you say, "(works great through the web)" do you mean through its local page, or from the eyez-on website? If this was on its local page,       then have you registered the device on the eyez-on site? If not then you need to do this as its likely its running and old version of the code without the automation interface (TPI) and the plugin will not work.
-Do you have it selected as 2DS in the parent device? (selection should be a darker blue)
Title: Re: DSC Alarm System plugin
Post by: subha on August 13, 2012, 06:22:59 pm
I moved to a home which had DSC 832. I re-activated it and installed IT100 and connected with my Vera 3 (firmware 1.5.408) with rs-232 / usb converter.

I installed DSC plugin from Apps Store and it installed correctly - DSC Alarm Panel, System (Partition 1), Zone 01 - Zone 06 and I added Zone 07 and 08. It also shows the status correctly. If I arm / stay in my DSC keypad, it shows up in Vera. All sensors are also working correctly and any change in the sensors also shows up immediately in Vera dashboard.

My challenge is, I am not able to arm or disarm the system using the Vera Dashboard. It does nothing. I checked the log as described in previous posts and I see the following. Could anyone please let me know what is wrong. Appreciate your help.

Code: [Select]
08 08/13/12 18:20:25.289 JobHandler_LuaUPnP::HandleActionRequest device: 34 service: urn:micasaverde-com:serviceId:AlarmPartition2 action: RequestArmMode <0x2e960680>
08 08/13/12 18:20:25.289 JobHandler_LuaUPnP::HandleActionRequest argument fwdserver=1 <0x2e960680>
08 08/13/12 18:20:25.290 JobHandler_LuaUPnP::HandleActionRequest argument remoteIP=... <0x2e960680>
08 08/13/12 18:20:25.290 JobHandler_LuaUPnP::HandleActionRequest argument token=e5a0c7277110e3f3d5b93a4e7d8e0751ebede867 <0x2e960680>
08 08/13/12 18:20:25.291 JobHandler_LuaUPnP::HandleActionRequest argument PK_AccessPoint=300..... <0x2e960680>
08 08/13/12 18:20:25.291 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=34 <0x2e960680>
08 08/13/12 18:20:25.291 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:AlarmPartition2 <0x2e960680>
08 08/13/12 18:20:25.291 JobHandler_LuaUPnP::HandleActionRequest argument action=RequestArmMode <0x2e960680>
08 08/13/12 18:20:25.292 JobHandler_LuaUPnP::HandleActionRequest argument State=Stay <0x2e960680>
08 08/13/12 18:20:25.292 JobHandler_LuaUPnP::HandleActionRequest argument PINCode=undefined <0x2e960680>
08 08/13/12 18:20:25.292 JobHandler_LuaUPnP::HandleActionRequest argument rand=0.3186291966121644 <0x2e960680>
50 08/13/12 18:20:25.293 luup_log:27: DSCAlarmPanel: debug Action::RequestArmMode Stay <0x2e960680>
50 08/13/12 18:20:25.294 luup_log:27: DSCAlarmPanel: debug extractPartition: Partition 1 <0x2e960680>
50 08/13/12 18:20:25.326 luup_log:27: DSCAlarmPanel: debug processIncoming:: Command=empty, Data='empty', Checksum=empty <0x2e333680>
01 08/13/12 18:20:25.326 LuaInterface::CallFunction-2 lu_incoming failed [string "..."]:1087: attempt to concatenate local 'cmd' (a nil value) <0x2e333680>
Title: Re: DSC Alarm System plugin
Post by: guessed on August 13, 2012, 10:36:42 pm
@subha,
It looks like the IT100 is returning extra data that we're not expecting.  I can't tell what it is from the logs so-far, but if you enable Verbose Logging (in Vera) then it will output additional data during the Stay sequence you're initiating.

From that I'll be able to work out what's going on.


NOTE: I removed some of the private data from your posting above.  Things like IP Address, and Vera Serial#
Title: Re: DSC Alarm System plugin
Post by: subha on August 14, 2012, 11:03:27 am
Thanks a lot @guessed.

I tried to get the verbose mode on in the settings of Vera 3 and tried to get the log from the browser. I was not able to get the details since the scrolling never seems to stop. Is there a better way to get the log file details in verbose mode?

Thanks in advance.
Title: Re: DSC Alarm System plugin
Post by: guessed on August 14, 2012, 11:36:47 am
@subha,
If you are comfortable with using the command line, you can:
a) Login using http://wiki.micasaverde.com/index.php/Logon_Vera_SSH
b) Access the log file using "cat /var/log/cmh/LuaUPnP.log"

If not, then the only way would be to get the MiOS Support team to retrieve it for you.
Title: Re: DSC Alarm System plugin
Post by: subha on August 14, 2012, 07:04:33 pm
@guessed, please find the attached log file. I finally was able to figure out.

Thanks a lot for your help.
Title: Re: DSC Alarm System plugin
Post by: guessed on August 14, 2012, 10:25:07 pm
@subha,
There's a lot of garbage data entering the serial line.  It could be electrical (cabling) or it could be a faulty USB-Serial adapter.

Here's an example:
Code: [Select]
52 08/14/12 18:51:01.856 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x39 0x30 0x31 0x30 0x30 0x30 0x33 0x32 0x20 0x20 0x44 0x61 0x74 0x65 0x20 0x20 0x20 0x20 0x20 0x54 0x69 0x6d 0x65 0x20 0x41 0x55 0x47 0x20 0x31 0x34 0x2f 0x31 0x32 0x20 0x20 0x36 0x3a 0x35 0x31 0x61 0x30 0x37 (#####################################90100032  Date     Time AUG 14/12  6:51a07) <0x2f0bc680>
50 08/14/12 18:51:01.857 luup_log:27: DSCAlarmPanel: debug processIncoming:: Command=empty, Data='empty', Checksum=empty <0x2f0bc680>
01 08/14/12 18:51:01.857 LuaInterface::CallFunction-2 lu_incoming failed [string "..."]:1087: attempt to concatenate local 'cmd' (a nil value) <0x2f0bc680>

and a different one relating to the Stay command that you ran:
Code: [Select]
10 08/14/12 18:51:52.570 luvd_get_info_data_request done /data_request?fwdserver=1&remoteIP=XX.XX.XXX.XXX&token=25f175590c8163e33de616a3ca72f24cc2f05775&PK_AccessPoint=3000XXXX&id=lu_action&output_format=json&DeviceNum=34&serviceId=urn%3Amicasaverde-com%3AserviceId%3AAlarmPartition2&action=RequestArmMode&State=Stay&PINCode=XXXX&rand=0.7914014928974211& ret 0 size 46 pMem 0x124e000/19193856 diff: 11513856 took 0 info (nil) <0x2ea8f680>
10 08/14/12 18:51:52.571 mg_callback /data_request stop id: 3426 <0x2ea8f680>
52 08/14/12 18:51:52.596 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x35 0x30 0x31 0x39 0x36 (############################################################50196) <0x2f0bc680>
50 08/14/12 18:51:52.597 luup_log:27: DSCAlarmPanel: debug processIncoming:: Command=empty, Data='empty', Checksum=empty <0x2f0bc680>
01 08/14/12 18:51:52.597 LuaInterface::CallFunction-2 lu_incoming failed [string "..."]:1087: attempt to concatenate local 'cmd' (a nil value) <0x2f0bc680>

If I were to guess, I'd say that the ground-pin isn't connected in the RS-232 cable.
Title: Re: DSC Alarm System plugin
Post by: subha on August 15, 2012, 10:46:22 am
@guessed,

Thanks. I will change the usb-serial adapter and see if this solves the problem. I will order it today.

Just wanted to let you know that only the problem is while trying to arm/disarm through vera. If the change is done through keypad, it is reflecting correctly in vera.
Title: Re: DSC Alarm System plugin
Post by: GT! on August 15, 2012, 11:12:05 pm
Hmmm, under the Advanced tab, InterfaceType, it said IT200, I changed that to 2DS, and reloaded Vera and now works.


Thanks


The only thing I can see is that in the advanced tab it says; Commuse: RS232 could that be the problem?

Nope thats fine!

-Are you sure you have its IP correct?
-When you say, "(works great through the web)" do you mean through its local page, or from the eyez-on website? If this was on its local page,       then have you registered the device on the eyez-on site? If not then you need to do this as its likely its running and old version of the code without the automation interface (TPI) and the plugin will not work.
-Do you have it selected as 2DS in the parent device? (selection should be a darker blue)

I'm in a similar situation, but slightly different.  When I installed the plugin and gave it the IP address of my 2ds it found it and added the partition and 6 zones (I have more, but I guess I add those manually?) but then gives the LUA failure messages and nothing seems to work.  I've tried rebooting and also changed the InterfaceType to 2DS manually, but so far it has not helped.  The 2ds is working fine with eyez-on.

-GT
Title: Re: DSC Alarm System plugin
Post by: guessed on August 15, 2012, 11:57:34 pm
@GT!,
Can you post a copy of your Verbose-enabled logs, from the file /var/log/cmh/LuaUPnP.log?
Title: Re: DSC Alarm System plugin
Post by: GT! on August 16, 2012, 07:34:39 am
@GT!,
Can you post a copy of your Verbose-enabled logs, from the file /var/log/cmh/LuaUPnP.log?

Sure thing.  Will try to figure that out tonight and post.

Hmmm ... there's a warning that turning on verbose logging can cause system instability unless using USB.  Should I use USB (I have spare thumbdrives)?
Title: Re: DSC Alarm System plugin
Post by: subha on August 17, 2012, 11:20:04 pm
@guessed,

I got my new rs232-usb cable today. Plugged in and it now working perfectly.

Thank you for your time, help and solution.
Title: Re: DSC Alarm System plugin
Post by: Intrepid on August 28, 2012, 08:07:50 pm
OK, got my 1832 and 2DS the other day.  I have never come across a device as cryptic and complicated as programming this panel.

Anyway, I got it temporarily setup and got 2 door sensors programmed for testing.  The 2DS works well. 

The plugin works great, too.  But these points need to be put in the 'help' documentation from the marketplace screen:

1.  I had to change the advanced, interface type to 2DS.
2.  The password deal needs to be mentioned.  I had changed the password also and was getting lua error.

Great job, awesome plugin.  But why is the programming and documentation on the DCS so hard to decipher?

I finally figured out these steps to get my door sensors programmed:

*8
5555 installer code
804 for wireless section....I've reread the docs and still can't find this mentioned
101 for zone #
123456 for module ESN
##

then...

*8
5555
101 for new zone number, I guess
toggle option 8 for wireless
##

Clear as mud.  I've got two sensors working, but I still cannot find out how I did it by reading the manuals.
Title: Re: DSC Alarm System plugin
Post by: strangely on August 29, 2012, 05:20:32 am
Agreed definitely not easy to program, and it can be many degrees more difficult depending on the type of keypad you have (alpha numeric versus numeric). The main reason things are difficult is becuase typically they've not been designed for the end user to install and program themselves.

On the bright side, programming does get easier once you get through the initial fog of all the basics and amount of things you need to program. I've also found the new PTK5507 keypad more logical to program with. Also if you've not already considered it, then you should think about programming with the DLS software instead from a PC, as the learning curve isn't as bad!
Title: Re: DSC Alarm System plugin
Post by: Intrepid on August 29, 2012, 06:33:43 am

On the bright side, programming does get easier once you get through the initial fog of all the basics and amount of things you need to program. I've also found the new PTK5507 keypad more logical to program with. Also if you've not already considered it, then you should think about programming with the DLS software instead from a PC, as the learning curve isn't as bad!

Can the DLS software be used with the 2DS as an interface, or do I need the other interface too?
Title: Re: DSC Alarm System plugin
Post by: garrettwp on August 29, 2012, 07:14:13 am
I believe you need the special cable that plugs into the panel itself.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: Intrepid on August 29, 2012, 07:48:59 am
Thanks. 

The Arm and disarm buttons don't seem to do anything.  I have the variable EnableRemoteArm set to disarm.  Is there a place for the panel's user pins?  I don't think I ever set this (the interface pw variable is set to the 2DS pin).  the stay does arm the panel, but I can't disarm it or arm it.  Am I missing something?

Title: Re: DSC Alarm System plugin
Post by: garrettwp on August 29, 2012, 09:07:44 am
Click on the wrench. There you should see the box to enter the pin and then the arm or disarm buttons. Disarm requires a pin, arming depends on how you have the panel configured.

- Garrett
Title: Re: DSC Alarm System plugin
Post by: radarengineer on August 29, 2012, 09:54:15 am
Can the DLS software be used with the 2DS as an interface, or do I need the other interface too?

I think you do need a second interface, but it is much cheaper ($15 or so):

PCLINK-SCW "DSC Computer Interface"

Programming the DSC through the keypad is horrific. I wanted to throw my panel out the window the first time I had to do it. The software on the other hand lets you get everything set up and then you just push the entire program to the panel, and you can also save backups of configurations. The one issue with the PCLINK is that I understand it doesn't work will all usb to serial adapters. On other forums I've seen the Keyspan USA19-HS recommended. I use the same ethernet to serial adapter I use for interfacing the panel and it works fine, as I think would any other hardware serial port.

I think your best bet for getting the software is here:

http://www.diyalarmforum.com/DLS2002/
http://www.diyalarmforum.com/DLS_IV/

or here:

http://www.diysecurityforum.com/software/

It turns out there are multiple f/w revisions for the 1832 and 1864. I have one of the older ones (v4.1) so I have to use the older DSC software (DLS2002), while the newer revisions (v4.2 and up) can use the newer software (DLSIV). On a previous post WAY back in this thread someone had mentioned that there was some functionality missing from DLS2002 (programming zone labels?). It turns out that wasn't true, it all worked fine for me.

Title: Re: DSC Alarm System plugin
Post by: Intrepid on August 30, 2012, 06:00:57 am
Thanks for the replies. 

Quote
Click on the wrench. There you should see the box to enter the pin and then the arm or disarm buttons. Disarm requires a pin, arming depends on how you have the panel configured.

This works, I just thought these were all controllable from the icon view since I could stay arm via the icon label.

Radar, I'm sure I'll pick up the PC-LINK kit, but I kinda want to get my head around what I'm doing in the meantime.  I'm finally getting the concept of zone, zone type, and zone attributes.  It is just not laid out very clearly in the docs. 

I've still got alot of work to get the thing installed.  I have the panel and siren installed in a closet  I need to run a wire for the keypad, and I need to install the door sensors.  The little recessed door sensors are so tiny and nice, and they'll be invisible when installed.  And the 2DS works amazingly well.  The text notifications are instant.

Aside from the USB adapter, is there any magic in the PC-LINK, or is it simply a cable?  Can I make this part?
Title: Re: DSC Alarm System plugin
Post by: strangely on August 30, 2012, 07:01:22 am
It is a simple cable and you can make one from a DB9 connector and and an old floppy drive power connector. If you search back through the thread (and also maybe linked from the Wiki), there are some instructions on how to cable it.

You should also take a look at some of the other links on the Wiki (to an Alarm Forum), as there are some basic instructions for programming that are very helpful.

**edit**

Link for cable pin-out:
http://forum.micasaverde.com/index.php/topic,5154.msg60596.html#msg60596
Title: Re: DSC Alarm System plugin
Post by: Intrepid on August 30, 2012, 07:29:11 am
It is a simple cable and you can make one from a DB9 connector and and an old floppy drive power connector. If you search back through the thread (and also maybe linked from the Wiki), there are some instructions on how to cable it.

You should also take a look at some of the other links on the Wiki (to an Alarm Forum), as there are some basic instructions for programming that are very helpful.

**edit**

Link for cable pin-out:
http://forum.micasaverde.com/index.php/topic,5154.msg60596.html#msg60596

Thanks.  great info on the wiki. 
Title: Re: DSC Alarm System plugin
Post by: Intrepid on September 02, 2012, 10:53:10 am
If I want to arm the alarm with a scene, what are the values for state?

Title: Re: DSC Alarm System plugin
Post by: garrettwp on September 02, 2012, 10:58:32 am
That would be: Armed

- Garrett
Title: Re: DSC Alarm System plugin
Post by: guessed on September 02, 2012, 12:44:34 pm
I added some basic stubs to the Wiki to describe the parameters.  These are from the main S_AlarmPanel2.xml file, and can be expanded on as needed.
Title: Re: DSC Alarm System plugin
Post by: Intrepid on September 02, 2012, 02:47:57 pm
Thanks, got it.

My schlage 'leaving home' code now arms;  my schlage 'arrive home' code now disarms. 

This is beautiful.
Title: Re: DSC Alarm System plugin
Post by: Intrepid on September 09, 2012, 05:15:48 pm
I made the PC link cable out of an old serial cable and HDD cable.  I got the recommended USB/serial adapter.

I installed the DLS app on a Win7/64 laptop.  The updater installed one update, then I kept getting "cannot connect to update server", and the second critical update disappeared from the options list.  It looks like 64bit is a no no.

So I dug a 2005 toshiba out of the garage (Win7/32) that had not been turned on in over a year.  After hours of updates, the DLS app finally works.  But I don't have a clue how to use it.  I'm gonna take a long break from this before I screw up my properly-working alarm system...

Also, I picked up a 5 pack of the slim RF DSC window sensors on ebay for 79+3, about $16 each.  That will give me 4 wireless door zones, one wired garage door zone (set to be not part of the alarm...forgot what it's called), and 5 of my 11 ground floor windows monitored!  3 of the 11 are in a 'set'/same window, so I may use one sensor for these.
Title: Re: DSC Alarm System plugin
Post by: strangely on September 10, 2012, 12:34:19 pm
I made the PC link cable out of an old serial cable and HDD cable.  I got the recommended USB/serial adapter.

I installed the DLS app on a Win7/64 laptop.  The updater installed one update, then I kept getting "cannot connect to update server", and the second critical update disappeared from the options list.  It looks like 64bit is a no no.

So I dug a 2005 toshiba out of the garage (Win7/32) that had not been turned on in over a year.  After hours of updates, the DLS app finally works.  But I don't have a clue how to use it.  I'm gonna take a long break from this before I screw up my properly-working alarm system...

Also, I picked up a 5 pack of the slim RF DSC window sensors on ebay for 79+3, about $16 each.  That will give me 4 wireless door zones, one wired garage door zone (set to be not part of the alarm...forgot what it's called), and 5 of my 11 ground floor windows monitored!  3 of the 11 are in a 'set'/same window, so I may use one sensor for these.

Like I said before, the DLS software is not exactly easy to use either, but the learning curve is far less, once you manage to get communication with the panel etc!

Just remember to make a backup of your panel configuration first before doing anything else so that you easily return to a working state! And remember the upload and download buttons can easily be misinterpreted for which does what :)

Download = uploading new programming settings from your computer to the panel.

Upload = downloading existing control panel program settings from the panel to your computer.
Title: Re: DSC Alarm System plugin
Post by: Intrepid on October 15, 2012, 06:38:03 pm
I gave up on the DLS stuff for now.  But I have keypad programming down pretty well.  I have 10 zones setup and this plugin has worked flawlessly.  Amazing work.  Thanks.
Title: Re: DSC Alarm System plugin
Post by: smilligan on November 24, 2012, 07:10:19 pm
Hello,
We have been using the DSC plugin with IT 100 for past year, and are happy.
We recently spent a trying 2 days working with IT100 and DLS2002 to make easier programming of alarm panels..
We gave up and found out that the reference to PC-Link in DLS parlance, was NOT a reference to the IT100..  (silly me)

Once we built the simply PC Link cable for the DLS2002 software, the DLS2002 worked like a CHAMP!!

So i have a few questions that I am hopeful someone can answer for me.

1) Does teh DSC plugin support the simple PCLink interface on the power series?  Every reference i see is either for the IT100 or the EthernetBridge.
2) Do the newer versions of DLS have support for the IT100?

The reason for our sudden interest in the DSC plugin is because we find the zWave sensors are not cutting it in a production environment.   Batteries dripping in ZIR000, CA9000 are about as reliable as a broken flip flop, the list goes ON and ON...

Our general thought is to use the more reliable and more pervasive 433Mhz sensors from DSC or Honeywell in concert with a PowerSeries (or Ademco) panel..

Thank you to anyone, in advance, who can shed some light on #1 and #2 above.

Regards and happy thanksgiving.
Sean
Title: Re: DSC Alarm System plugin
Post by: strangely on November 25, 2012, 12:36:02 am
Why do you need to try and program with an IT100? If you are looking for some form of remote programming, the the EVL3 is a better choice since it can be done from the eyez-on portal. Also it's easier to set up than an IT100 and Vera.
Title: Re: DSC Alarm System plugin
Post by: smilligan on November 25, 2012, 12:20:00 pm
Strangely,

Thanks for the reply.

We have IT100 and DSC in stock and we are using VERAs for the intelligence..

Not quite sure what EVL3 or EyesOn portal is and how it might replace our DSC installations.

Kind Regards
Sean
Title: Re: DSC Alarm System plugin
Post by: strangely on November 25, 2012, 12:48:13 pm
Most of us originally using the IT100 have cut over to using the EVL3 (or the older version called 2DS) instead, and it basically replaces the IT100 and it still gives you the interface to Vera and the plugin, however it does it via Ethernet so it's easier to set up since it requires no RS232. It costs slightly more, but by the time you factor in serial adapter etc, its similar price.

The eyez-on portal also provides stand alone remote arming, alerting, monitoring and other functions such as panel programming.
Title: Re: DSC Alarm System plugin
Post by: smilligan on November 25, 2012, 01:27:21 pm
Strangely,

Ok, now i understand.. EVL3 is the ethernet bridge, that also includes Eyezon portal...

I see your point, and yes, it makes great sense to use this as opposed to the traditional IT100.

However, in our case we are using the DSC and Honeywell panels ONLY for the sensor monitoring (not for the alarms)..  So being able to use the PCLink on the DSC Power Series (as opposed to the IT100 or EVL3) is still an attractive alternative.   So this means the VERA is always right next to the alarm panel so the PCLink

1) Do you feel the EyezOn portal is a rich and comprehensive for programming the DSC as the DLS software? (relative to programming DSC kit?)
2) are there any VERA plugins that work with DSC via the PCLink RS-232 interface? (we would still like to consider this as option)
3) Is the VERA honeywell/ademco plugin pretty robust relative to this EVL3 bridge?  The reason i ask, is the attractiveness of a single piece of kit (EVL3) that will allow our VERA LUUP code to use BOTH Honeywell and DSC sensors...   This is a very strong reason to look at this EVL3 bridge.

Thanks again for all your support/advice.

Sean
Title: Re: DSC Alarm System plugin
Post by: Intrepid on November 25, 2012, 01:36:50 pm

The eyez-on portal also provides stand alone remote arming, alerting, monitoring and other functions such as panel programming.

Are you serious?  I had no idea the panel could be programmed via my 2DS.  How?
Title: Re: DSC Alarm System plugin
Post by: strangely on November 25, 2012, 01:44:19 pm

1) Do you feel the EyezOn portal is a rich and comprehensive for programming the DSC as the DLS software? (relative to programming DSC kit?)
I don't think its a good choice to do a new setup, but tweaks etc it would be OK through their portal. The Eyez-on guys though are planning on adding in DLS compatibility though, just dont know where they are with that yet though.

Quote
2) are there any VERA plugins that work with DSC via the PCLink RS-232 interface? (we would still like to consider this as option).
Nope its purely for programming unfortunately.

Quote
3) Is the VERA honeywell/ademco plugin pretty robust relative to this EVL3 bridge?  The reason i ask, is the attractiveness of a single piece of kit (EVL3) that will allow our VERA LUUP code to use BOTH Honeywell and DSC sensors...   This is a very strong reason to look at this EVL3 bridge.

Not sure yet if the two Vera Honeywell plugins have added in support for the EVL3 yet, but I know the Eyes-on developer wanted this to happen, and I passed on the Devs contact details a few months ago.
Title: Re: DSC Alarm System plugin
Post by: strangely on November 25, 2012, 02:15:26 pm
Are you serious?  I had no idea the panel could be programmed via my 2DS.  How?

From the Portal, if you go to into commands and then you'll see a button called sequence as attached.
Title: Re: DSC Alarm System plugin
Post by: Intrepid on November 25, 2012, 04:10:29 pm
I thought DSC PGMs were relays/outputs from the DSC panel.
Title: Re: DSC Alarm System plugin
Post by: strangely on November 25, 2012, 04:20:30 pm
They are but that's different from "sequence". The commands pop up allows you to toggle PGMs, bypass sensors and send key-presses (sequence)
Title: Re: DSC Alarm System plugin
Post by: smilligan on December 06, 2012, 04:07:25 pm
Strangely,
I have purchased 3 x EVL3 to test with various clients for our energy mangement system.
I have not yet tried the DSC plugin, but i assume that the latest DSC plugin will communicate directly with the EVL3 via IP.

I read on the Eyez-on forum that the EVL3 API was only for their cloud/portal, and NOT available for direct coms..   This comment was as recent as NOV12. 

So, my question is this:  Does the VERA DSC Plugin with EVL3 bridge use cloud API or communicate directly with the EVL3 on LAN?
(I am sure that it communicates directly with EVL3 on LAN, but the comments on the Eyez-On forum have me concerned)

Thanks
Sean
Title: Re: DSC Alarm System plugin
Post by: Brientim on December 06, 2012, 04:20:08 pm
Sean,

Rest assured the Vera with plugin with communicate with the EVL3.
Title: Re: DSC Alarm System plugin
Post by: smilligan on December 06, 2012, 04:48:28 pm
Strangely,
Thanks for the quick reply.
Just to make sure i understand: The DSC plugin communicates DIRECTLY with teh EVL3 and not through the cloud portal?
Thanks again for all your support.
Sean
Title: Re: DSC Alarm System plugin
Post by: Brientim on December 06, 2012, 04:53:22 pm
I hold @strangley in high esteem as an SME and hate to steal his glory.
Yes, the Vera communicates directly with the EVL3.
Title: Re: DSC Alarm System plugin
Post by: smilligan on December 06, 2012, 06:34:21 pm
Guys,

Thank you for the update..
Sorry to seem obtuse, but when Strangely said "the plugin communicates with EVL3" i asked myself "Could Strangely be telling me that the VERA communicates with the EVL3 via the portal?"

Thank you for taking the time to clarify something that should have been somewhat obvious to me.

If I program ZONE names through the EVL3 portal, do those ZONE names get automatically pushed to the PANEL itself via the EVL3 bridge?  I ask because i have named the ZONEs in EVL3 protal, and the newly assigned literals only seem to pop-up in the portal.
The newly assigned ZONE names do not appear in the Panel's LCD keypad, nor the EVL3's direct web interface, nor in the VERA (which by the way is still communicating with SAME panel via IT100)..

Any clues/ideas as to what my misunderstanding might be?

Thanks in advance for your support.
Sean
Title: Re: DSC Alarm System plugin
Post by: PurdueGuy on December 06, 2012, 06:36:13 pm
Unfortunately, portal names are only used by the portal.

As far as I know, you have to program in 3 places
1) Portal
2) Keypad (and broadcast to all other keypads)
3) Vera

I hope I'm wrong!
Title: Re: DSC Alarm System plugin
Post by: smilligan on December 06, 2012, 06:46:09 pm
Purdue Guy:
Thanks for the reply.
I was under the impression that the VERA's DSC plugin would only get the Zone Name Literal from the panel itself..  And that yes, you can change the ZONE name in the VERA DSC device sensor icon, but once it reboots, it will be overwritten with the panel's default literal zone name.
But i had read somewhere that the EVL could program the Zone names..  I guess i simply assumed that this meant it would push the new zone names to the panel.
If what you say is correct, we will still need to use the SerialLink interface to program Zone names using the DLS software..  Ouch...
If anyone else has some comments that would be greatly appreciated.
Thanks
Sean
Title: Re: DSC Alarm System plugin
Post by: Intrepid on December 06, 2012, 07:01:59 pm
Quote
If what you say is correct, we will still need to use the SerialLink interface to program Zone names using the DLS software

You can set the zone names via keypad entry, right?  If so...

They are but that's different from "sequence". The commands pop up allows you to toggle PGMs, bypass sensors and send key-presses (sequence)

...could you do it via the envisalink UI sequence?
Title: Re: DSC Alarm System plugin
Post by: smilligan on December 06, 2012, 07:55:52 pm
All,

Intrepid, thanks for this bit of info..  I must admit, programming from the keypad is more painful than DSL2002.

That being said, does anyone have a simple "sequence" example for a zone that might get me started with Intrepid's suggestion?

Kind Regards
Sean
Title: Re: DSC Alarm System plugin
Post by: Brientim on December 07, 2012, 04:50:23 am
All,

Intrepid, thanks for this bit of info..  I must admit, programming from the keypad is more painful than DSL2002.

That being said, does anyone have a simple "sequence" example for a zone that might get me started with Intrepid's suggestion?

Kind Regards
Sean

Hello Sean,

I am a bit perplexed by the question. Even though I agree it is easier utilising DLS software to perform the panel programming, using keystroke via the Envisalink UI sequence is not going to make you happy. "Envisalink UI sequence" is emulation of keypad programming one step at a time.

To be honest, even though I would like DLS over the 2DS or EVL3, if you are at it all the time, there are other issues which really need to be addressed. I have only modified my system once recently to replace a dead keyfob. I know your system are for clients and thus, you really do need to get the initial programming correct. I really would not expect dymanic changes if I had a system installed and monitored.

As to zone name broadcast, I use to hate the fact that the 2DS did not do this but I have added more logic to the way the zones are determined and I have just either accepted this or got used to it. But, if you want to push it, it would be best followed up on the Eyez-on forum or via their support because they developed the firmware and publish the API/TPI.
Title: Re: DSC Alarm System plugin
Post by: smilligan on December 07, 2012, 02:31:23 pm
Brientim,
Thanks for the "heads up" on sequence programming.
If i read between the lines, you are suggesting we use the DLS software as opposed to trying to use EVL3 portal's sequence.
Thank you for your suggestion.
Sean
Title: Re: DSC Alarm System plugin
Post by: Brientim on December 07, 2012, 03:03:31 pm
Sean,

The last few times I changed things were via the keypad as they were only small changes. One a key fob, change a maintenance code and correct a zone spelling. Previously as I had a t-link, I would utilise the DLS2002 to do changes and I do have a full panel back up on DLS. So set up via DLS and incremental changes via keypad.
Title: Re: DSC Alarm System plugin
Post by: Radjin on December 07, 2012, 11:45:41 pm
Are there limits to the number of zones you can see from vera with the DSC 1864 panel?  I seem to be limited to 6 with no arm/disarm control.
Title: Re: DSC Alarm System plugin
Post by: PurdueGuy on December 07, 2012, 11:46:57 pm
Are there limits to the number of zones you can see from vera with the DSC 1864 panel?  I seem to be limited to 6 with no arm/disarm control.
There are directions: http://code.mios.com/trac/mios_dscalarmpanel
Title: Re: DSC Alarm System plugin
Post by: Radjin on December 08, 2012, 12:30:49 am
Are there limits to the number of zones you can see from vera with the DSC 1864 panel?  I seem to be limited to 6 with no arm/disarm control.
There are directions: http://code.mios.com/trac/mios_dscalarmpanel

Now that was fast.  I wish all customer service was this good.  Thanks
Title: Re: DSC Alarm System plugin
Post by: Brientim on December 08, 2012, 01:25:01 am
That's not customer service, just a good forum member helping another, good to see it being acknowledge. :D
Title: Re: DSC Alarm System plugin
Post by: strangely on December 08, 2012, 01:59:17 am
@smilligan

About the only disadvantage that the 2DS/EVL3 has over the IT100, is that zone labels do not get transferred to Vera like they do with the IT100; the only reason this was not implemented previously was due to the fact the 2DS never had enough memory left. Hopefully soon this will be rectified by updated code for the EVL3 since it has more memory, along with adding the DLS programming!

Not sure when either will be added, but I'm sure it it wont be long since the developers have added lots since I've been using it, and both features have been spoken about on their forum by the developers! In the mean time, its not too much of a problem to label the zones manually in Vera (so long as you read the wiki about how to do this)... I never had to do this since I ran it with an IT100 originally anyway before swapping.

***edit***

Not forgetting of course the 2DS/EVL3 will also set the panel time for you also automatically :)
Title: Re: DSC Alarm System plugin
Post by: GT! on December 26, 2012, 07:51:43 pm
Hmmm, under the Advanced tab, InterfaceType, it said IT200, I changed that to 2DS, and reloaded Vera and now works.


Thanks


The only thing I can see is that in the advanced tab it says; Commuse: RS232 could that be the problem?

Nope thats fine!

-Are you sure you have its IP correct?
-When you say, "(works great through the web)" do you mean through its local page, or from the eyez-on website? If this was on its local page,       then have you registered the device on the eyez-on site? If not then you need to do this as its likely its running and old version of the code without the automation interface (TPI) and the plugin will not work.
-Do you have it selected as 2DS in the parent device? (selection should be a darker blue)

I'm in a similar situation, but slightly different.  When I installed the plugin and gave it the IP address of my 2ds it found it and added the partition and 6 zones (I have more, but I guess I add those manually?) but then gives the LUA failure messages and nothing seems to work.  I've tried rebooting and also changed the InterfaceType to 2DS manually, but so far it has not helped.  The 2ds is working fine with eyez-on.

-GT

Finally got this working.  After giving up hope, I decided to try it again after I upgraded the firmware on my primary router today (didn't realize there were new releases since nobody updated the router database).  Bingo, worked right away!  I suspect there must be a bug in DD-WRT (dd-wrt.v24-16785_NEWD-2_K2.6_big-e2k-e3k.bin).  The upgrade also fixed another problem I was having with wireless clients connecting to PPTP VPN.  I upgraded to the latest stable release (19519).  Posting in case this helps someone else (unlikely, but I guess you never know...).

-GT
Title: Re: DSC Alarm System plugin
Post by: Pestus on January 03, 2013, 12:33:42 am
Good day,

This is in regards to issue 2282.    http://bugs.micasaverde.com/view.php?id=2282

The Envisalink 2DS Keepalive problem.  I keep hearing all over the intarwebs that this issue is solved.  My setup exhibits the exact behaviour as described for this issue.  Someone needs to actually declare how to enable these keepalives.  Where does one put this in? Advanced tab somewhere, no doubt?

Or am I missing something here?  Was this a solution purely for plugin authors, and I shouldn't be experiencing this?  Also, does this behaviour exist with the Envisalink 3?

Thanks in advance!

Envisalink 2DS, Firmware version 01.08.107
Vera3 UI5, version 1.5.408.
Both devices on DHCP assigned static IPs.  (Reserved addresses)
Both plugged directly into a Cisco router
Title: Re: DSC Alarm System plugin
Post by: strangely on January 03, 2013, 12:40:07 am
If you have the latest DSC plugin for Vera, the latest Vera Firmware, and your 2DS has been registered (and updated its firmware), then you have the keep alive logic.

If you are having the issue, what do you see? Does the connection go stale without seeing TPI disconnect/reconnect messages?
Title: Re: DSC Alarm System plugin
Post by: Pestus on January 03, 2013, 12:43:09 am
Thank you strangely!

In Vera, the "DSC Alarm Panel" device shows a red error.  "lua failure lua failure" while the Partition 1 shows no state, and can not be controlled.

In Envisalink 2DS, I see TPI showing it being connected.  Rebooting the Envisalink seems to solve the problem.
Title: Re: DSC Alarm System plugin
Post by: strangely on January 03, 2013, 12:53:04 am
This sounds like a different problem. Did this behavior just start?

Are you sure you don't have something else trying to connect to the TPI interface?
Title: Re: DSC Alarm System plugin
Post by: Pestus on January 03, 2013, 01:01:19 am
Hmm..

No, this is my only attempt at using the TPI aspect of this. 

I just recently got the Vera, and the DSC plugin worked out with all the various settings done accordingly.  Or so I had thought, anyways...

It does work..  I have scenes set up where if Partition 1 does this, then do that...   others where if this happens, arm or disarm Partition 1.  It works both ways.  Yet, every day or so, this "lua failure lua failure" occurs.  This has been since installing the plugin.  I have tried removing the device, reinstalling the plugin, etc.

The -ONLY- thing that I am thinking might be out of the norm, is I am arming and disarming the DSC panel via a key switch zone.  I can't see how that really matters, though.

I'll wait until the next time it fails, and I will copy all version numbers, full list of settings, and as much detail as I can.
Title: Re: DSC Alarm System plugin
Post by: guessed on January 03, 2013, 01:16:53 am
Quote
The -ONLY- thing that I am thinking might be out of the norm, is I am arming and disarming the DSC panel via a key switch zone.  I can't see how that really matters, though.
It might, we've not had a keySwitch armed version before and I believe we get a difference sequence of messages in that case.

I will PM you an email address that you can send logs to.  You won't be able to PM me back, since you don't have enough Forum cred just yet, but you can use the email address to send me a copy of your log file.

I'll need a copy of it as close as possible to the time when the error occurs.  Vera rotates the logs throughout the day, so it's entirely possible that the error isn't in the "current" log file that you can see on your Vera unit.

This will get you logged on:
    http://wiki.micasaverde.com/index.php/Logon_Vera_SSH

and the log file in question is in:
    /var/log/cmh/LuaUPnP.log

You can use Winscp (or similar) to copy the log file off of the Vera box.


If that doesn't work, you can always do a copy & paste from the output of:
    http://192.168.x.x/cgi-bin/cmh/log.sh?Device=LuaUPnP
Title: Re: DSC Alarm System plugin
Post by: Pestus on January 25, 2013, 12:42:28 pm
This issue seems to have gone away on it's own.  On top of that, the logs requested have long been over written it seems.  Apologies.  May as well consider this issue closed.  I waited for it to repeat itself, but it did not, and became entirely reliable.  It may have been a keyboard - chair interface issue.

Thanks!
Title: Re: DSC Alarm System plugin
Post by: shdwkeeper on January 31, 2013, 06:58:31 pm
Hmm..

No, this is my only attempt at using the TPI aspect of this. 

I just recently got the Vera, and the DSC plugin worked out with all the various settings done accordingly.  Or so I had thought, anyways...

It does work..  I have scenes set up where if Partition 1 does this, then do that...   others where if this happens, arm or disarm Partition 1.  It works both ways.  Yet, every day or so, this "lua failure lua failure" occurs.  This has been since installing the plugin.  I have tried removing the device, reinstalling the plugin, etc.

The -ONLY- thing that I am thinking might be out of the norm, is I am arming and disarming the DSC panel via a key switch zone.  I can't see how that really matters, though.

I'll wait until the next time it fails, and I will copy all version numbers, full list of settings, and as much detail as I can.

I'm having the same issue as you.  Brand New 1832 install with Envisalink 3, everything works through the Envisalink portal, mobile device, but Vera just gives me the same error and my TPI says Offline when logging into the board. 

Any ideas?
Title: Re: DSC Alarm System plugin
Post by: silencery on April 19, 2013, 06:22:56 am
Hmm..

No, this is my only attempt at using the TPI aspect of this. 

I just recently got the Vera, and the DSC plugin worked out with all the various settings done accordingly.  Or so I had thought, anyways...

It does work..  I have scenes set up where if Partition 1 does this, then do that...   others where if this happens, arm or disarm Partition 1.  It works both ways.  Yet, every day or so, this "lua failure lua failure" occurs.  This has been since installing the plugin.  I have tried removing the device, reinstalling the plugin, etc.

The -ONLY- thing that I am thinking might be out of the norm, is I am arming and disarming the DSC panel via a key switch zone.  I can't see how that really matters, though.

I'll wait until the next time it fails, and I will copy all version numbers, full list of settings, and as much detail as I can.

I'm having the same issue as you.  Brand New 1832 install with Envisalink 3, everything works through the Envisalink portal, mobile device, but Vera just gives me the same error and my TPI says Offline when logging into the board. 

Any ideas?

Similar issues started popping up for me today as well, except the envisalink still says TPI online.  Odd since it was running fine for several months.  It's happened two days in a row where it will work fine for a few hours, but eventually show "lua failure lua failure." Any ideas?
Title: Re: DSC Alarm System plugin
Post by: Pestus on April 19, 2013, 08:26:53 am
Very odd.

I take all this to mean you have no manual control of the partition?  You can't arm or disarm anymore?

Rebooting either the alarm panel or the Vera will probably solve it, but that's a poor solution...

I'm at a loss.  My issue seems to have gone away and not come back.
Title: Re: DSC Alarm System plugin
Post by: silencery on April 19, 2013, 01:32:56 pm
Yup, strange indeed.  No control of the partion nor inputs from any of the devices.  Particularly problematic since a lot of our Vera scenes are triggered by the DSCs door/motion sensors.

Rebooting the 3DS (and subsequently vera) always fixes the issue, but yeah, like you said, it's not a solution.  I'll post back with more details and logs if it happens again.
Title: Re: DSC Alarm System plugin
Post by: ozorowsky on May 24, 2013, 05:54:31 pm
Does anyone have a clue why my envisalink won't disarm in UI5 under devices tab?

I am under devices, stay and arm seem to work, but when I click disarm nothing happens UNLESS I click the wrench put in the code and disarm from there.

I followed the setup instructions, and I listed disarm under enableremotearm.

Any help on what I am missing?
Title: Re: DSC Alarm System plugin
Post by: Pestus on May 24, 2013, 06:22:29 pm
ozorowsky,

Yah inorite?  I think it's probably because these alarm devices don't have "Quick" disarm features, similar to their quick arm modes.  Not having to put in a pin to disarm somewhat defeats the purpose of having an alarm to begin with.

When dealing with scenes, just be sure that under the advanced view, the disarm command also has your alarm code in it.  To deal with this for cell phone control, I just wrote a scene with no trigger that just what I'm proposing.

Short answer, I don't think you can disarm without a code in Vera, because you certainly can't do it on the alarm proper.

Is this addressing your question?
Title: Re: DSC Alarm System plugin
Post by: ozorowsky on May 25, 2013, 07:08:11 am
ozorowsky,

Yah inorite?  I think it's probably because these alarm devices don't have "Quick" disarm features, similar to their quick arm modes.  Not having to put in a pin to disarm somewhat defeats the purpose of having an alarm to begin with.

When dealing with scenes, just be sure that under the advanced view, the disarm command also has your alarm code in it.  To deal with this for cell phone control, I just wrote a scene with no trigger that just what I'm proposing.

Short answer, I don't think you can disarm without a code in Vera, because you certainly can't do it on the alarm proper.

Is this addressing your question?

Got it thanks! I was missing adding the pin to the advanced menu.
Title: Re: DSC Alarm System plugin
Post by: pricebn on November 24, 2013, 10:17:33 am
Help Please!!

I have installed the Envisalink board and the DSC plugin in Vera UI5.  My alarm is a DSC PC1616.  I have also registered in EyesOn site as well and this appears to be working fine.  All of the items seem to be installed in Vera correctly, DSC Alarm Panel, Partition, and zones.  It reports in Vera the current status of the DSC panel correctly. 

Problem
When I try to arm or disarm in Vera, I get this error "Invalid Service".
I have rebooted the LUUP several times and unplugged Vera as well.
Title: Re: DSC Alarm System plugin
Post by: ih8gates on November 24, 2013, 10:27:00 am
Do you have "EnableRemoteArm" set? Set it to "arm" to allow remote arming, "disarm" to allow both remote arm and disarm. The latter is less secure.
Title: Re: DSC Alarm System plugin
Post by: pricebn