belias

Io_guy: Thanks for the ideas. I checked comm on the KPL and all appears good...it never misses a group command, it's fast to program and no errors in the log. I also tried a restore yesterday, but I'll give it another shot today with a factory reset as well. As far as latching mode on the garage: I'm not sure how that would work since it seems like it would hold the garage door opener switch on indefinitely (unless I make a program using a wait command to perform an on/off). The advantage of the "Momentary C" in my application is that I'd like one button to close any open garage door. Using Momentary C saves me some programming since I could always send just an ON command to all garage doors and only those open would close. I'll wait to see what Michel, etc. has for suggestions and if not maybe the latching mode with a program is the way to go. Thanks! - Brian

Hi Michel, On the KPL v36 units, I see both "Off level" and "On level" as available options (actually, I see both of these for the v2C and v2D as well). The latching mode works correctly with my V.35 I/O Lincs - it will hold the relay closed (or open) indefinitely when set to this mode. Also - I'm not entirely sure I understand your comment for #3 from my original post (regarding the 6-button KPL). I didn't do a great job of explaining it... when I was using HouseLinc2, there was an option for the 6-button KPL's (it was a checkbox called "backlight" that applied to the load on/off buttons). When the box was unchecked, pressing "Load ON" turned the backlight on bright for the top button; pressing "Load OFF" resulted only in the dim backlight for the top and bottom. As it is now, when the Load is switched OFF, the bottom button glows brightly which I don't want. I _do_ want the normal on/off backlight for all the other buttons. I may be able to program this locally at the switch if it's not supported by the ISY. Thanks again, -Brian

Hi Michel, Thanks for the quick reply. I am using 2.7.13, but I'll upgrade to the latest and try again. I'm a little confused on the correct way to access the ISY. I have been simply browsing to the static IP of the ISY and choosing "Admin Console". What's the difference between that and using the URL you provided? Thanks again, Brian

I'm in the process of setting up my ISY, and I have a few questions. I've tried my best to search the forum / Wiki before posting, but there's a LOT of information - so if I missed something, my apologies! Any help would be great. Thanks! 1. I have two I/O Lincs (v. 35) on my garage doors. I've read the previous forum postings on these units, and my V.35's both correctly report the sensor status (when not set to "reverse trigger"). The problem I'm having is that the "Momentary C" option doesn't seem to work as intended - instead it seems to act as Momentary B (an ON signal always triggers the relay). This option should (and did, when set manually) allow the relay to only trigger based on the sensor status (i.e. an OFF command would only close those doors that are open). I've tried a factory reset / restore device with no luck. Any ideas? 2. I have 4 KPL's, and for some reason only one of them responds to the LED Brightness setting (as set by the "LED Brightness" button in the device screen). The one that responds correctly is a V. 2D; the ones not responding are V. 2C and V. 36. For the latter two, there is no change in KPL brightness regardless of the setting in the ISY...for the V. 2D, the change shows almost immediately on the KPL. 3. I have a few 6-button KPL's and I know there's an option to turn off the backlight on the lower "OFF" button. So, in other words, when the main load is switched on, the top-button glows brightly; however, when the main load is off, the lower button remains at the "off" backlight setting. I can't figure out how to do this via the ISY...am I missing something or is it easier to make that change locally? 4. For some reason any time I create a new program it always defaults to disabled the first time I save it, even though the checkbox is marked for "Enabled". I have to reopen the program, check the box, and re-save for it to be enabled. At most this is a little annoyance, but I thought I'd through it out there. 5. If I have multiple scenes turning on in a program (in the "Then" section), do I need a delay between them? Not sure how the ISY works with "group cleanups", etc... Thanks for any help - and this is one AWESOME product. I'm doing things with my home that I never thought possible! Also, thank you for the amazing support. I wasn't sure about spending the money on the ISY, but after reviewing this forum and level of support offered - it was an easy decision... -Brian

Thanks for the quick response and the excellent forum! My unit should be arriving this weekend, and I'll try loading the 2.7.13 FW before adding devices. The only thing I'm not sure on is the 2413SH PLM... I had read a while back that ISY had some concerns with the dual-band PLM (slower to issue commands, NAK's etc.) - has this been resolved? In other words, is the 2412 the "preferred" PLM? Thanks again, -Brian

Hello, I have an Insteon system that I've built up over the past few years, and currently I'm using HouseLinc 2 to program/control the system. Recently, I've really outgrown its capabilities and I'm looking into the ISY. Before I invest the money (and time I know I'm going to spend playing around with it), I have a few questions for those more knowledgeable. If anyone has a moment to give a few quick answers, I'd really appreciate it. Here goes: 1. How do I interpret the "max devices/scenes" in the model comparison? I have 4 KPL's, 3 I/O Lincs and about 15 SL's. At the moment in HL2, I have about 10 scenes. Does this correlate to 4+3+15+10 = 32 (i.e. well below the need to go to PRO)? 2. One of the most annoying things about HL2 is how it handles the situation where a PLM scene turns a switch on. HL2 registers this as an "OnPressed" and triggers any event (program) with an "OnPressed" initiating action. In other words, it's impossible to differentiate between someone pressing "ON" and the device turning on because it was called from a PLM scene. I realize this may sound a bit crazy - but it's been driving me insane and I wanted to make sure that is indeed an HL2 issue and not something common to the Insteon protocol. (In other words, I won't have this issue with the ISY, right?) 3. I have a 2413SH PLM (dual-band serial, HL2 enabled). I realize the 2412 is recommended, however as an interim solution can I use this PLM with an AC adapter for power? SmartHome appears to be out of stock on the 2412 until April 30 (!!) - if the 2413SH won't work, any ideas where I can pick up a 2412? 4. I'm not sure I understand the purpose of the network module. Is it only to initiate TCP actions from the ISY? Is it required to use MobiLinc? 5. When I transition to the ISY, I'll likely add my devices by using the "enter address" and "remove existing links" method to give as clean a start as possible. Will this also remove my device properties (i.e. KPL button modes, I/O Linc settings, ramp rate, etc.)? I've spent a decent amount of time setting these up and to lose them would be really annoying. Thanks again for any help! -Brian