MarkJames

Thanks, Michael.... Only problem is that I can't find 2.7.7 anymore. It seems to be something one needs to sign up for. Could you please point me at it? Thanks! mark Oh.. and by the way - while I remember - I was sitting at my computer today for quite some time plodding away with the ISY software and after an hour or two I realized that I had been backing up and saving my changes every few minutes. I do that automatically as I'm so accustomed to things crashing on me. The thing is - the ISY software never crashed - not even a hiccup..... That's quite remarkable! Thanks for that!

I thought the same - that sending an ON should be an ON whether an off was sent first or not. But I do, indeed, have to send an off first. I've tried this both from direct control of the iolinc or with it in as a responder in a scene. As for my firmware - in an effort to make this work properly I upgraded from 2.7 which was the version I got it with to 2.7.6 which is what it's currently at. The smarthome manual states that the iolinc can be set up so that an on will cause it to open the door while an off will cause it to close. http://www.smarthome.com/manuals/74551qs.pdf near the bottom says this. Very confoozalating

Ahh.... Thanks for that. I read a lot of the code snippets people were using but didn't get why so much elaboration for what should be a simple task. My 2450's are brand new.... one would think they would work as advertised. Thanks again, Mark

I've searched and searched and I'm sure I'm doing something just silly but I can't figure out where I'm going wrong. I hooked up an iolinc as per the smarthome instructions and it works as it should - tap set and it opens - tap it again and it closes. I can't make it work properly from ISY though. I have it set for LED on TX and momentary:both. The time out is set for 2 seconds and this seems to be OK with my garage door opener I've confirmed that: When the door is closed the sensor reads off When the door is open the sensor reads on If the door is open and I send an ON it will close Once it's closed an off will NOT open it. In order to open it I have to send the off and then a subsequent on. In other words it only works in response to an ON command and not to the off regardless of the sensor input. Am I missing something obvious?

I thought 13 seconds seemed a bit much... I have a LOT of insteon in my house - 13 KPLs and 65 other devices. The problem that I think I'm experiencing is that I have a weird electrical system. I have something called E-plus. The power comes in to my main panel and then feeds off to a sub panel that provides heating/cooling to the house. The feed to that sub panel goes through a separate meter as I get charged less for the electricity I use for heating than I do for regular power. Unfortunately some other devices are on the heating side as well and the insteon signal has a hard time getting past the meter. I'd hoped that the RF portion of insteon would prevent that problem and it's certainly much more reliable than X-10 ever was (I've had a large x-10 install for 15 or so years) but it's still a bit quirky. I've got 2 of the older insteon access points (the ones with antennas) installed on both legs of the panel as well as a couple of other newer 2443 access points in other areas of the house. I've ordered two more 2443's in the hopes that this might improve matters. Oddly... when I install the access points I can't get the newer style to communicate properly across both phases - only the older ones. I'm not sure what that means - perhaps you have some insight into this? At the moment I'm linking an 'every light in the house off' scene which turns off 92 lights and KPL LED's. It's been running for nearly half an hour and is not quite done yet. This seems ungodly long! Mark

As the only Insteon installation I'm familiar with is my own I have no way to gauge how well my system is communicating. I was wondering how long, typically, it takes for some of you to have a link successfully write to an insteon device. Obviously the more responders and controllers within a scene the longer it will take for that scene to be created. But if you were to create a blank scene and add one device to it as a responder how long does it take the ISY to successfully write that link. In my case it takes about 13 seconds. I understand that some of the newer switches accept extended messages and write faster. Just curious. Mark