geogecko

Hmm, ok, that's too bad. That's the only thing I don't like about Insteon products, is that the firmware is not field upgradeable.

Lol, while this is in the garage, the wiring added to add the sensor looks ugly. I'm not going to run another wire to the wired remote on top of the drywall. I guess if it bothers me enough, I can take one of the wireless openers, and make some modifications, however, at some point the battery will die, and then I will lose control over the door until its replaced...unless I make a little circuit to drop the 5V output of the IOlinc down to 3V (hopefully that's what they use inside), and hard wire power to the remote... Lol. I probably have an old LM317 that I could use to do that... I did the same thing you are planning on doing. I moved the original opener to the single car door, and bought this new fancy one to use on the main door. Overall, I've been happy with it, but after about 3 years, the wireless operation has been intermittent. Sometimes we will have to be right up next to the door to get it to open or close, and it doesn't matter which car (Homelink), or remote we use. I think maybe the capacitors in the GDO are going bad...or something else...

That stinks. I just finished installing mine last night, and so far, am loving it. I like the way I have it setup, and I just have one little maintenance program that goes out and checks to see when the relay is on, and then waits 2 seconds, and queries the relay so that it has the proper status. My only complaint, is that by using this, the relay shorts out power to the LCD wall control for the garage door opener, which resets the clock on it. I am trying to remember if there is a backup battery (CR2032 maybe) inside the wall control that might be dead. Otherwise, I guess I'll just have to quit using it for a clock in the garage. My unit is a Chamberlain Liftmaster with the battery backup.

Yes, thermostats work perfectly fine, minus the time syncing. The All-In-One thermostat is brand new, about 2 weeks old. They both appear to have v.95 firmware, at least, I think that is what that means. It's listed at the top of the main node of each thermostat in the admin console.

The thermostats seem to be working great, just not the time syncing feature. Don't seem to get an error message from what I can tell, this is all I get in the diagnostic log: Sun 12/16/2012 06:06:49 PM : [ Time] 18:06:51 6(0) Sun 12/16/2012 06:06:54 PM : [ Time] 18:06:56 6(0) One for each thermostat.

I have a 7 day programmable Venstar 1700 with an Insteon Thermostat Adapter (2441V) v.95, and an All-In-One Venstar 1 day programmable (2491T) with internal adapter v.95. Are these compatible with the new commands in the beta firmware of the ISY-99i/Pro? It doesn't appear to be working. (ISY firmware 3.3.5)

Understood. Mentally, I just find it weird turning on, an already on relay. Also, it works a little different in Mobilinc. If I use the icon to toggle the state, if I don't reset it to off, I first have to cycle it to off, then back on, in order to activate the relay. If I reset the relay, every press of the Mobilinc icon for the relay, will cause action on the part of the garage door opener. Thanks for your help in understanding this operation.

Or could I just wait 2 seconds, and query the relay? Wouldn't that reset it to off? Edit: Just tried this...actually has to be status, not control, I keep forgetting that direct control by the ISY does not trigger a control command in a program.

Ok, so I guess I should just think of it like "on" always toggles the garage door. So I guess if I wanted the relay state to really be reflected, even though it doesn't really matter, I could write a program that looks for the relay being turned on, and 1-2 seconds later, I can turn it off, so that it matches it's real state. Then I just monitor the sensor to determine if the door is open/closed.

LeeG, Thanks for the assistance here. The changes from those versions of firmware is what I was talking about. I noticed that no matter what I did in 3.2.6, I could not get anything to behave differently. I also noticed that the nomenclature of some of the options changed. Currently, I have the I/O Linc connected to the green/black wires (for the sensor). When the magnet is close to the sensor, the sensor is "on," which with the way it will be installed in the garage, will indicate that the door is "closed." The I/O Linc relay normally open contact will be used to operate the garage door opener. When the door was open (magnet away from sensor), I set the following options: With Sensor "on" (door closed) Relay direct commands operate as follows (via admin console): On - Relay momentarily clicks (closes circuit), shows status "on" (door will be open now) On - Relay momentarily clicks again, shows status "on" (door will be closed now) Off - Relay does nothing, shows status "off" Off - Relay does nothing, shows status "off" (behaves the same if I go back to On commands, etc.) With Sensor "off" (door open) Relay direct commands operate as follows (via admin console): On - Relay momentarily clicks (closes circuit), shows status "on" (door will be closed now) On - Relay momentarily clicks again, shows status "on" (door will be open now) Off - Relay does nothing, shows status "off" Off - Relay does nothing, shows status "off" (behaves the same if I go back to On commands, etc.) So in other words, the relay operates the same, no matter what the sensor state is. Ideally, and I don't know if this is possible, but this is the desired operation: With Sensor "on" (door closed) Relay direct commands operate as follows (via admin console): On - Relay momentarily clicks (closes circuit), shows status "on" (door will be open now) On - Relay does nothing, shows status "on" Off - Relay momentarily clicks (closes circuit), shows status "off" (door will be closed now) Off - Relay does nothing, shows status "off" With Sensor "off" (door open) Relay direct commands operate as follows (via admin console): On - Relay momentarily clicks (closes circuit), shows status "on" On - Relay momentarily clicks again, shows status "on" Off - Relay does nothing, shows status "off" Off - Relay does nothing, shows status "off" (behaves the same if I go back to On commands, etc.) I think I have the logic right, but anyone feel free to correct me. I am guessing that if this is not possible operation to setup via direct commands, that a little program running in the background could provide this type of operation, I just wanted to be sure that the functionality didn't exist, before I start writing code.

Yes, that is also what I didn't like, that the scene itself wouldn't contain the status of the door, so I'd have to go somewhere else to verify that. I kinda like the icons mobilinc uses too. I don't plan on using a KPL to show status, so that didn't bother me. I was going to see about writing a program that would either flash a light after a given amount of time, or something like that. Also send email, in case I was away. At this time, I haven't installed mine until I figure this out, because it's a lot easier to troubleshoot with it in the same room as my computer. I'm interested in how you guys set it up. I notice the setting options keep changing in the last couple RC firmwares...

I've also just received this I/O Linc, and bought the NO/NC sensor, and am just as puzzled. It seems like the scene setup works, but I like using MobiLinc to control my stuff, and going to the My Devices page is usually what I do to control devices. I guess if there is no other way, I'll use the scene...

LOL, this has just gone south, really fast!

Tested it out last night, works perfectly. Thanks for simplifying my code! I am a bit surprised with how all this works, but I think I have a better grasp on it now, thanks to you all.

Ah, wow, that explains it well, thanks for that. I think I'll have to print out a copy of that post for use while programming, so I can remember this behavior. The work around is annoying, but also not that complicated, except for the fact that it requires multiple programs to accomplish.