Any particularly good resources on how to get started with an install?
There's some good general how-to-get-started articles here if you do some searching, but I don't know how many are specific to HAI. Here's a few things I learned when I did mine:
Before Installation: Decide exactly where you're going to put the controller, and make sure you have a good stable base to fasten the box to (this is assuming you don't already have a structured wiring enclosure up). A good simple idea, if you're installing it an area where looks don't matter, is to nail a couple of pieces of 2x4 blocking across two studs, and then you can fasten the enclosure to that. Leave the center area open because the enclosure has two large holes in the center of the back to route wires in. (There are also knockouts on top and bottom.)
Put in a dedicated circuit for the controller if you can. You'll want at least one duplex outlet, one to plug in the controller and one to plug in a PIM for UPB/Insteon lighting. Also, you will need a phone line routed to the vicinity of the controller, and it will be highly desirable to be able to connect the controller to your home network if you have one.
There are several pieces that you need to get in order to have a functioning controller. The best way is to look for a kit; HAI markets several kits that have different mixes of components, and you can choose the one that best fits the installation that you plan to do. Besides the controller itself, the kit needs to have at least: a power supply (it's a big wall wart), a battery, and a "console". (In HAIspeak, a keypad is a "console". All HAI systems need to have at least one console.) Here's some other bits that you might need or want initially:
* You really want PC Access, which is a program that runs on Windows and connects to the controller via Ethernet or a serial port. PC Access lets you set all of the setup parameters at one time and write them to the controller in one burst. It lets you see the status of anything the controller knows about, and command anything that the controller can control. It also is your interface for writing automation code and storing it in the controller. It isn't absolutely necessary to get the system running, but it will make setup far easier. And since version 3.0 of the Omni firmware, you really can't do programming through the keypad any more. Also, PC Access is the only way to install firmware updates. Get the dealer version so that you have access to all setup parameters. (No, you don't have to be a dealer to buy it.)
* Sounders: The Omni controllers don't provide a "siren" waveform; they just apply power to the internal and external alarm outputs. So just connecting loudspeakers to them won't work; you need something like piezo buzzers for internal, and a horn and/or strobe for external if you want an external alarm. Hint: If you go to allelectronics.com, they usually have piezo buzzers really cheap.
* If you are going to use UPB lighting, get an extra PIM. This way, you can have one that remains attached to the controller while you're using the extra one to configure things with Upstart.
* If you are going to connect a computer to the controller using one of the RS232 ports, make sure you order the correct serial cable.
HAI requires the online dealers to not advertise a price below the MSRP. However, they can still sell below that price; they just can't advertise it. When you are shopping and comparing prices, make sure you call and ask if there is a better price. You may be pleasantly surprised. Don't just go by what's listed on the Web site.
Once you get the system, read through the installation manual before you do anything. When I got mine, I first did a temporary setup on my basement couch with just the power, console, Ethernet, UPB PIM, and one zone connected, and I played with that for a while in order to understand the system. If you haven't dealt with this type of system before, here's some terminology that may help:
Zone: An input to the system; something it can sense directly. For example, a motion detector or door/window sensor. All of your security-related inputs to the system are through zones. However, not all zones have to be security related; they can also be used to sense things for automation purposes.
Unit: Something the system can turn on and off. This may be one of the hardwired outputs in the controller itself, or a UPB/Insteon/Zwave/etc switch.
Area: This is a partition of the system. If you divide the system into areas, each area can be alarm armed and disarmed individually. This is sometimes useful in residential installations when, for example, you have a detached garage or an outbuilding. Most of the time, in a residential setup, you only need the one default area.
Codes: These are the four-digit numbers that you enter at the keypad to arm and disarm the alarm. You can assign one to each member of the family. Codes designated as "master" have the ability to change setup parameters. There is an "installer" code that controls access to some of the setup parameters. When you first receive the system, the installer code will be 0000. You'll want to change that, but DON'T FORGET THE INSTALLER CODE!
Flags: These are internal memory cells that can be turned "on" and "off", store a numeric value, or be used as timers. You use them in programming.
Buttons: These are blocks of code that are assigned a name and can be invoked by other code blocks, or through a console or a touchpad.
Hardware expander and expansion enclosure: This bit of terminology can be a bit confusing. They are both expanders that add zones and outputs to your system. The difference is: A hardware expander is a board that mounts in your controller enclosure and connects to the main board via a very short cable. An expansion enclosure is in its own box, with its own power supply and battery. It connects to the controller via the console data bus, and logically it looks like an extension of the controller. It can be mounted some distance away.
