Another great post by our guest blogger Richard Perlman:

I hacked at the VistaICM email process and here is what I found:

Part 1: The information for the email is sent, via HTTP, to outgoing.in2myhome.com. So, If you are running a local DNS server, you can enter a record for that host/domain and resolve it to some other HTTP server.

Part 2: The information is sent as a GET request. I.e. It’s ALL in the URL. Really simple (and insecure). For example, here is an “Armed” notification:
GET /email.aspx?address=alarm%40foo.com&subject=Security+Alert&message=System+Armed&mac=00%3A0e%3A70%3A00%3A35%3A7d&time=02-16-2010+01%3A03%3A33+PM

So, all that would need to be done is to write a simple cgi-bin script to handle requests for /email.aspx to parse the GET request and create an email or do whatever you wanted.

Richard

I got a great email from Richard Perlman containing detailed information about the latest ICM update 2.8. Since people tend to end up here for info on the ICM he wanted to share it with the rest of you. Thanks Richard!

Many changes in the Vista ICM, some significant:

Most notable: Honeywell has discontinued the Vista ICM. It seems there was some disagreement with in2net over fees. Since in2net seems to have designed most of the internal code, it doesn't look good for further support. I have emailed them, but they don't reply. The immediate result is that email is effectively dead, unless you pay a fee. If you are running a DNS service on your network it should be simple to "deflect" the HTML connection used by the ICM to pass email messages to in2net to a local web server. Then you'd just have to figure out how they pack the email message into the HTML content.

Other things as of release 2.8:

1. There is no more backup (i.e. download). You can still upload, but "download" is pretty much limited to cat/copy/paste.
2. A lot of the web pages, like the PDA page, are now configured differently, not as easy to change.
3. I found the same TCP data that was on port 50003 on port 50001 too and I also found an in2networks debug facility of port 50501. But, I can't make any sense of it.

On the other hand, using the TCP interface I have been able to build a fairly simple state engine in Perl. This maintains a state table for each zone, as well as reporting the panel state. The script was customized to Interface to the Indigo home automation system running on a Mac. But, it could be easily modified to report to other services. Take a look at:

http://www.perceptiveautomation.com/userforum/viewtopic.php?f=9&t=5444&p=32308&hilit=ademco#p32308

If there is sufficient interest maybe we can set up a small mail-list to share ideas and discoveries, etc.

Richard Perlman

Just noticed that there's been an update available for the Honeywell / In2Networks Vista ICM. The latest version is in2 fusion image_2.8.0 - Tue Dec 30 09:55:28 MST 2008. The old root password still works and I haven’t seen any adverse side effects yet.

The change log is as follows (http://inunicn.com/honeywell_ecp/version.htm):

2.8.0

• Improved device management, time management, and setup.
• Vizia ICM - New ICM controls Leviton ViziaRF lighting systems.
• Energy ICM - Added humidity alerts and improved EnviraCom error handling.

2.7.2

• Added trouble-free remote access support and event logging through www.in2myhome.com
• Improved support for corporate networks and static IP addressing.
• Reset button handling works more reliably.
• Email reliability is improved with a trusted email server.
• Local web page improvements reduce Java errors.

I ordered another HDHomeRun Thursday and was expecting it to arrive Friday. Well, after having some friends over for dinner I got around to checking the UPS order tracking and it stated “Delivered – Front door”. Well, I certainly couldn’t find it. So I started D-ViewCam to check the security footage from our front door and guess what? No UPS guy had ever walked past our front door Friday.

The software that comes with certain D-Link web cameras is pretty awful. It also creates proprietary files (MJPEG/MPEG4?) along with additional information such as motion detection details. This was the first time I wanted to actually get the video out in a format that I could actually forward on if needed which I didn’t end up needing. Amazon had placed a replacement order with free next day shipping about two hours after I emailed customer support. Of course, this didn't really help on a Friday (OK, OK… Saturday) past midnight.

Turns out that D-ViewCam doesn’t work all that well on a Windows Home Server, at least through Remote Desktop. I was able to set the start and end cue points only once for an export. Other times they were disabled making it impossible to actually export anything. And the one time I was able to export, I ended up with a zero length file.

Long story short (I’ll leave out having to install VS2008 in a virtual machine since D-ViewCam doesn’t work under 64-bit Vista either), a few hours later I had a custom utility that will take a .DVF file and convert it into an .AVI. Unfortunately, I have to use the libraries from D-ViewCam to do this, which means you’ll need to have that installed. In addition, the format (compression) doesn’t seem to work (It doesn’t have any effect. The same goes for exporting via D-ViewCam).

The story also has a happy ending, the person who received the package a few streets down was kind enough to bring it over this morning, so now I have 4 tuners in Vista MCE, but getting that to work is another post altogether.

The utility is a quick hack. It will only convert the whole file, and this will take several hours. It doesn’t do batches, and you can’t cancel it (unless you kill the app with Task Manager). I didn’t want to spend the time writing these unless someone actually asks for these features.

It’s available on the downloads page. Just extract and run DvrConvert.exe. Let me know if you want the source.

I’ve only tested with D-ViewCam 2.03 (available here) which is listed to work with the following cameras:

DCS-900
DCS-900W
DCS-G900
DCS-910
DCS-920
DCS-950
DCS-950G
DCS-1110
DCS-2000
DCS-2100
DCS-2100+
DCS-2100G
DCS-2120
DCS-3110
DCS-3220
DCS-3220G
DCS-3410
DCS-3415
DCS-3420
DCS-5220
DCS-5300
DCS-5300G
DCS-5300W
DCS-5610
DCS-6620
DCS-6620G
DCS-6110

Spent some time figuring out what the Vista ICM module I've had installed for over a year could finally do for me. I've wanted to integrate it into mControl, but they don't have a driver. Step one was to look at the ICM and figure out how to access it and read information from it. The following attempts to document as much as I could figure out and the resulting C# component is available on the Downloads page.

More...