No worries, but thanks for the update anyway.

As the system just got installed yesterday (and I had to leave for the weekend) I haven't had time to play with it much, but I did get a few minute to test their web interface which is clever. If their firmware gets delayed more than a few weeks, I'll whip up something super simple with their crude API at http://forum.eyez-on.com/FORUM/viewtopic.php?f=6&t=128&sid=26032ecd07269a3bf845665ce1a6661e, but of course I'd much rather have a local (e.g. reliable) interface.

wow... what a great plug-in. I just ordered an IT-100 to try this out but I have a couple of basic questions.

1) Is this a do it yourself kind of install where I just have to attach 4 wires to my PC1832 or does my security panel have to be programmed or something to acknowledge the new module. The installation instructions says that it should be installed by a professional. Is this just to scare us or is there some kind of trick to this?

2) I was looking online for a DB9 to USB cable to connect to my mac mini and found a ton of them online ranging from under a dollar to over fifty. A lot of reviews say that most of them don't work with Mac's. I am not sure of the complexity of the drivers required for this. Will any cable do or do you have any recommendations? BTW my mini is only about 5 feet away from the security panel.

I can't wait to get this going.

Thanks!

To answer your questions:

1) For me it was as simple as connecting the four wires to the IT-100, there was no panel programming necessary. I believe this is the most common scenario. I'm not a DSC panel expert by any means so I can't say for sure, but I believe the installer might have the option to program the panel to disallow the addition of new devices without their permission.

2) I have been leaning towards the USB-serial adapters based on the FTDI chipset. Smarthome uses an FTDI chip in their Insteon PLCs so you'll already have the drivers installed if you use one of those. I've heard a few people have problems with them but I've got three FTDI devices on my MacMini and they work great. After a reboot they always come up with the same port name. I can't say the same for Prolific based devices. I've got two of those, after a reboot there's no way to know which of them will be assigned what port name so I often have to go change settings in some plugins after a reboot. I'll be getting rid of those shortly.

Hope that helps.
Travis

That helps a lot. Thanks

I ordered a cable with the FTDI chipset. I'll give the install a try when everything arrives, what could be the worst that happens. LOL, famous last words before the SWAT team arrives at my house.

Anyways, thanks again.

travisc: Any news on the firmware patch yet?

At the end of last week they got the 2DS firmware to the point where I can start working on it, I'll get started on it this weekend. It's a really early beta though, more of an alpha, as they themselves have said. The last version had a nasty networking bug, it'll probably be a few weeks before you'd even want to consider trying the beta.

Great news - even if it's in Alpha as that says they're continuing to work on it.

I'm having some trouble with using their http-based API, and it would be a bad hack at this point anyway, so your code is the one I'd rather use.

Good luck, and let me know if I can help.

travisc:

I wanted to let you know I've hacked up some scripts to get the basic integration working with my Indigo installation. I'm doing this by polling 2DS website and parsing their XML on the status of my 2DS. While it works, it has some major drawbacks:
1. It's a "reactive" system, meaning sometimes it takes 60 seconds to see a status change.
2. Being reactive, sensing things like motion in real-time isn't possible, so Indigo can't use the DSC motion sensors to trigger "lights on in hallway".
3. Sometimes the 2DS website shows a incorrect sensor reading like "Door OPEN" when it's really closed.

So I'm limping along, but really looking forward to your code being able to poll the 2DS module directly!

Eyez-on is almost ready to release the new firmware to the public. I have the plugin talking to the 2DS but it's not quite ready yet, I need a few more hours of coding to get it to a stage where it's usable. Shouldn't be too much longer.

Awesome Travis thanks - I'm not setup with Insteon, or Indigo yet - but about to dive in. (simple X10 atm) I've been lurking to get a better understanding of possibilities. One of the first things I'll be buying is a 2DS - hopefully they've given you the one you have, as like me, I'm sure a number of people will buy it as a result of your extensions to the plugin. Then some beer money your way as I get things working!

Hi Fishysan,

Yes they are letting me keep the one they sent me.

I'm hoping to get it up and running this weekend. The 2DS is a no brainer compared to the IT-100 now that it supports this new protocol. Plus it has all the other options like self-monitoring and paid monitoring over IP that the IT-100 doesn't support.

Travis

Awesome. I'm likely to order some goodies this weekend. No rush here, but I'm sure dstrickler will be happy.

Good points! Thanks for the reminder about paid monitoring via IP as well, I'd love to get rid of the land line but it's still holding on, that's one of the reasons (WAF). Hopefully my monitoring will, else great reason to shop for cheaper, as it's a bit much currently. Damn things creep up on you when you aren't looking.

Simplicity in the wiring is what sold me.. the rest just makes it that much better.

I've got the 2DS working with the plugin now. For the most part it works just as well as an IT-100. I'll keep using it as my main interface from now on to work out any kinks.

Cool! Let me know when you'd ready for a Beta tester. I'll be back at the house (with the 2DS) on Sunday.

It's ready now if you can get Envisalink to put you on the beta list so your 2DS gets updated.