DSC Alarm System using IP100D

Plugins & Plugin Development General Plugin Discussion
1

[quote=“strangely, post:899, topic:167215”][quote=“vicw, post:897, topic:167215”]@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.[/quote]

The IP for sure won’t work with this plugin; however there is a seperate IP100 plugin with some basic functions.[/quote]

Thanks - I don’t see any with IP100 as its title. Do you know what it’s called?

2

Look in this thread it has the link to the code http://forum.micasaverde.com/index.php?topic=8781

3

Thanks for that. I’ve browsed through the thread and printed out the instructions. I’m quite new to the Vera, and the programming, so it will take some effort and concentration for me to plug through it all, having never dealt with the process before. I did notice in the thread, that the plugin may lack the capability to capture alarm conditions to create triggers for scenes, which is the only function I’m trying to get. I’m assuming that the other plugin does have that capability, but of course not for the IP100D.

Also, it looks like the work supporting the plugin branched out into support for the 2DS, rather than the IP100D, so at this point it isn’t clear to me that the alarm triggering capability exists for either board, but I’ll try to plow through it all again in the morning, when my mind isn’t as muddled as it is right now. This late in the day, I have all I can do to get through the little math tests on each posting.

4

For the IP100 ignore the remaining posts and just stick to the initial post and the install instructions.
I have just conducted a testing install in UI5 and even though I can not test this, it does display as a trigger option within a scene. So it may have limited capability to achieve your desired outcome until you upgrade to the 2DS.

As the instructions were for UI4, I have added two screen captures of the changes you would expect to see with UI5.
After you create the device and the unit has stopped doing anything, you may need to reload (on top right of screen) before it creates the zones.

Yes, this was the development for the 2DS and the 2DS (and IT100) have the full capability to trigger scenes.

5

@Brientim I really appreciate the time you took to detail the installation for me. It helped to clarify things.

I managed to create the device, but I’m not quite getting the result I expected. I only get a single device displayed intially, whereas the instructions say I should have 1 Panel, 1 Partition and 6 zones.

I also don’t see any fields available for User and Password entries in the Advanced section of the DCSIP100D device, as the instructions suggest will be there.

I went back and double-checked the files that I uploaded. There are a couple of things that I don’t know are normal or not.

  1. The D_DSCIP100DAlarmPartition2.json shows as D_DSCIP100DPartition2.jso…son
    (when I float the cursor over the View or Download for that file, it shows the correct name, with a .lzo suffix)

  2. In the Luup file listing, I see the S_Partition2.xml file listed twice. Both the files seem to be identical in content. I don’t think I uploaded it twice, and I also haven’t found any way to remove a Luup file.

I don’t know if either of those things are normal or relevant to the problem. I don’t mean to drag you deeply into troubleshooting for a Vera newbie, but if you can tell me if those things are abnormal, or if you know how I can remove the duplicated file, I will appreciate the feedback.

I’ve deleted the device, and tried Creating it again, with the same results.

UPDATE: Regarding #2, I think I figured out how that duplication happened. The primary DSC Alarm app apparently puts a file with the same name into the Luup files. Again, I don’t know if that is a problem or not, or how to remove it.

6

I’ve split out this conversation, relating only to the IP100D, so it can continue separately from the main thread.

7

Good idea. Thanks.

8

When you create the initial device, it will only give you one device. On the to right of you browser click the reload button. You will need to do this I think twice or three times to enable all functions to be completed. Please give it a few minutes between clicking on the reload.

The user name and password will default.

If that does not result in the complete load of the zones. Go back and check the file names have no space at the end of them.

I only have my iPhone so I can’t redo this at the moment to verify the load process.

9

@Brientim I tried the Reload button quite a few times, and I’ve checked and rechecked all of the file names. Other than the 2 items I mentioned earlier, which probably aren’t relevant, I think I’ve followed the instructions. I also tried it using an alternate browser, just to be sure, but no difference. Thanks for all of your help and effort for me.

I wonder if anyone has actually been successfully using this plugin with an IP100D? The original thread said the plugin was created for that, but the discussion immediately diverted into getting it to work on the 2DS, but I didn’t see any posts that showed actual success using the 100.

It’s doubtful whether the IP100D will give me the scene trggering capability on alarm conditions that I’m trying to achieve, so I may just abort and trade up to the 2DS.

In the meantime, if anyone has been able to get it to run on the IP100D, I’d really appreciate hearing from you.

10

Hi, at the time of the post both the ip100d and the 2DS were working on basically the same API/TPI. It was Richard in the original post that had the ip100 and as far as I am aware it was working for him until he upgraded to the 2DS. I tested this against the 2DS and it was working at that point.

There were other threads were this was raised at that time but I ca not direct you to them.

You could try sending Richard a Private Message and see if he can verify this for you.

There is no doubt the original focus changed to the 2DS and that was due to the increased functionality that it offered with new firmware and this resulted in the new branch and code developed by @guessed. Consequently, the 2DS and IT100 are effectively merged with the current app for MIOS.

11

I will PM to Richard, to ask for his confirmation of the plugin performance using the IP100. I went ahead and ordered a 2DS last night, since I intended too soon, anyway, aside from VERA consideration.

I’m a bit suspicious that something on my system is interacting via the browser, and causing the problem creating the device properly. I’m most suspicious of my Ad Muncher app, which I’ve used for years, but they added a new version just a couple of weeks ago that interfaces via the browser more aggressively than in the past.

I notice some odd behavior in the micasa UI last night viewing Luup files, and some indications that it may have imbedded some code into the files, so I downloaded all of the files and reran everything with it disabled, and then exited, but it changed somewhat, but I still wasn’t fully successful. I’m going to completely remove the app temporarily and start all over with the device creation, to try to rule it out completely, or demonstrate that there is an issue with it. If there is a problem with the update in Ad Muncher, the developer is very responsive, and I’m confident that he will resolve it.

Sent from my Transformer TF101 using Tapatalk 2

12

I apparently can’t PM Richard, but I think I can reasonably assume that he had the code working with the IP100D. He released the plugin about a month before he upgraded to the 2DS.

I created a device on my Desktop PC with the Ad Muncher app totally uninstalled - no change, still shows as a generic device, with just the single display, so it loots like that wasn’t my problem.

13

I have retested and it load correctly.

I went back to the original thread and there were comment relating to errors with the downloaded files, so I have added the copies I had and tested the load with.

Do not use Internet Explorer; instead use Chrome and Safari. There has been issues with IE
Upload the 7 files to the Luup files.
Select Restart luup (after upload and click GO.
After restart, Create Device
The Description enter DSCIP100D
The Device Type enter urn:schemas-micasaverde-com:device:AlarmPanel:1
The Upnp Device Filename enter D_DSCIP100DAlarmPanel1.xml
The Upnp Implementation Filename enter I_DSCIP100DAlarmPanel1.xmi
The IP Address enter IP address:PORT i.e. 192.168.1.40:80
Click Create device

Wait for the message Device has been created.
Go to Device and once it has finish restarting, click on reload.

See how this goes.

To enable disarm function in the Advance tab of Parent Device got to EnableRemoteArm and enter disarm

Hopefully, this is successful. I will be out of contact for a while as I about to have an operation on my hand today. But I will try to follow up as soon as I am capable to do so.

14

:smiley: Wow, I have to admire your patience and perseverance through this adventure. I was successful on the first attempt with the procedure and files that you provided today. I don’t know if it was due to the inclusion of the Device Type entry, or some difference in one or more of the files, but together it worked.

Just to clarify, I noticed that there isn’t really any real feedback for clicking GO to upload the files to Luun, or restarting it. Presumably they really have taken place.
Both your procedure, and the original one used “After restart” at that point, and its not really clear whether that means a Reboot, or if that just means after the Restart Luup has presumably completed. I didn’t do a Reboot at that point.

The original called for me to “Restart the Vera” after the Create device action. which I concluded meant to do an actual Reboot, whereas you called for me to “Go to device and once it has restarted, click on Reload”, In any case, I decided to do the Reboot, just to be sure. Not sure that it mattered. (By the way, after I finally dug out a Reboot button this morning, buried in Setup/Net & WiFi, I started using that for reboots, rather than pulling power, as I had been doing. It seemed to go through a complete
Reboot cycle.)

Regarding the EnableRemoteArm setting - it defaulted to “false”. I went ahead and changed it to disarm, but it spit up on that, insisting that it had false, true, or some other setting, so I put it back to “false”

It generated the Panel, Partition1 and ten Zones. I don’t see any capability for capturing Alarm condition to use as a trigger for scenes, which is as I expected, but I think it was worth the effort to be able to generate a functional interface to be sure my configuration will support the device. I was really concerned that I had a hidden issue in the system somewhere.

It seems I can’t generate a PM, but it might be worthwhile to ask Richard to update his procedure and file links in his original post regarding the release of the plugin for the IP100D. It might save future users tremendous frustration, based on the issues. I would think there are many more users of the IP100D than either the 170 or the 2DS interfaces, so they would probably be able to benefit with the update.

Again, I’m very grateful for your help, patience, expertise and diligence getting me through this period of frustration. I’m excited about the potential of Z-Wave, mostly from a security standpoint, and to a lesser extent convenience. I hope your surgery went easily for you today, and that your recovery will be fast and relatively painless.

15

The feedback is a comment on top of the first file input box. If I remember correctly files loaded correctly or words to that effect.

You only needed to restart luup. You should just about never need a hard restart.

Go luck.