backinthelab

Well, sure am glad I found this before I started to write programs! Still, I'm not quite there yet as I turn into an idiot as soon as I take a new IOlinc out of the box. Would anyone mind telling me how to wire this to the Pro-C controller? IndyMike, you said you wired it across the two sense terminals of the Pro-C? Would that come from the N/O terminal of the IOlinc? How about the COM terminal? Any help would be greatly appreciated, this is one device that still confuses me to the point of frustration! You guys already help a ton on the programming level, thanks!

Ergodic, any luck on getting this to work? With the ability to control Sonos players, being able to add my AVR would be sweet!

This is for the AVR-4306, but might be what you're looking for? http://www.google.com/url?sa=t&source=web&cd=1&ved=0CCgQFjAA&url=http%3A%2F%2Fwww.domotiga.nl%2Fraw-attachment%2Fwiki%2FDomotiga%2FDenon%2FAVR4306_C4320_PROTOCOL_4.6.pdf&rct=j&q=denon%20avr-4306%20protocol&ei=-6W5TY3CLpTBtge13ajeBA&usg=AFQjCNEL5nu9en1C2yjhYi4CqcSEaTPo5Q&sig2=HelYSZKWeyhcEhHx4qo5Pg

I just purchased this module and I've been excitedly writing programs tonight! A quick question for all of us that live in the regions that often require a shovel and 4-wheel drive to get out of our driveways....how would one set up a notification for snow fall? Obviously, there is no selection for "snow", but can the rain/humidity/temperature settings be combined to accomplish this? If so, any examples that could be posted (I flunked out of meteorology school). So far, I'm very impressed with this module (as I've been with the others), I just don't know why I waited so long to buy it! Can't wait to see what's in store for 2011!

Lee, you're the man! Performed a Restore and switched the sensor wires to red/black instead of green so I wouldn't have to rewrite all of my programs. It's working great now!!! Thanks a million for your help, hope you have had a great Thanksgiving!

Ran a Restore and now a compare results in all "Identical" but the last entry which has an "Ignore". Still, no luck with updating properly in the Admin Console. What's happening is when the door is closed (Sensor ON) and I turn the Relay ON to activate the door, the sensor status and the relay status both remain ON and don't change without a manual query. But something else is happening that is odd. If I don't query the nodes and leave them both ON when the door is opened (incorrect status), then activate the door again, the sensor WILL turn OFF when closed. A query would then show actual status of ON, but it DOES change status in the Admin Console when going from closed to opened but not the other way around. Weird, huh?

LeeG, thanks so much for your help, it's greatly appreciated! I ran a Show Links for both the Sensor and the PLM. I believe I'm reading them correctly, but wanted to post the I/O Linc's results just in case. I also ran "Compare" and it appears that the results might point to something??? [Record mismatch] 0FF8 : A2 00 12.9F.9A FF 1F 01 [Record mismatch] 0FF0 : E2 01 12.9F.9A FF 1F 01 [Extra record] 0FE8 : A2 15 12.9F.9A FF 00 00 [Extra record] 0FE0 : A2 06 07.F3.1A FF 00 00 [Extra record] 0FD8 : E2 01 07.F3.1A FF 1F 01 [Extra record] 0FD0 : A2 07 16.76.C2 00 00 00 [Extra record] 0FC8 : E2 01 16.76.C2 FF 1F 01 [ignore] 0FC0 : 00 00 00.00.00 00 00 00

The sensor status doesn't update correctly in the Admin console, however, I did confirm that the green LED is functioning properly on the relay. The magnetic switch is working well as installed, and there is an access point plugged in directly on the other side of the garage wall. So, it appears that all fingers are pointing to the PLM, which doesn't surprise me since I've had issues before that made me question it's stability. I'm at the office now, but any tests I can run when I get home to prove this out?

@LeeG - I have it working, yes, but put an asterisk by "working". KPL buttons respond and activate, however, I have a problem with the sensor updating it's status. I put a band-aid on this issue by writing a sensor query program that relies on the relay status changing for now, and it works some of the time. I haven't had a chance to actually get up to the device for local programming/resetting. Here's my config if you have any ideas: i/oLinc 2450 v .36 Sensor is the 3-wire one from SH (purchased these items separately but they're the same as the kit) Sensor is wired with green/black wires to N/O and GND, shows a status of ON when door is closed. Relay is in Momentary A with Trigger Reverse activated. If the query program doesn't catch it, I can manually query the sensor and it will return the correct status. Aside from updating sensor status, the other issue (and confusion could be causing this one), is having other devices like the ELK respond to the door opening. Since the i/oLinc is in Trigger Reverse, I'm not sure if my programming is backwards. For example, I have this program to flash my hall lights when the door is opened. It currently is working when the door closes, which is messing with my head: If Program 'Closed' is False And Program 'Open' is True And Status 'Upstairs Hall - Primary' is Off Then Set 'Upstairs Hall - Primary' Fast On Set 'Upstairs Hall - Primary' Fast Off Repeat 0 times Else - No Actions - (To add one, press 'Action') Program "Closed": If Status 'My Sensors / Garage Door - Sensor' is On Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Program "Open" is the same but looking for OFF status. I'm unsure if I should be looking to poll the opposite status? I ask because the ELK has a program to say, "Garage Door Is Open" when sensor is turned off but, again, this is currently working when the door closes. Anyways, that's what's currently going in my struggle. Any ideas would be greatly appreciated, I've read a 1/2-dozen threads but they seem to confuse me more! @Michel - Thanks for the prompt and polite reply (per usual!). As I stated in my first post, I know you guys are working hard on other aspects of the ISY and my comments are just ideas for the future of how ISY users might be able to find information faster. Another added bonus is that you might free up some of your time as wouldn't always have to be on the forums!

Well, it's been almost one year to the day since I received my ISY and first Insteon modules and I wanted to share some thoughts on what I perceive as the good and bad thus far. 1. I have to start by stating that Micheal and the gang at UD provide AWESOME support. You can tell that they're dedicated to this product just by looking at the updates! Hand's-down, their customer service is some of the best there is. 2. Coolness factor - While I'm not a programmer, I'm definitely a guy who revels in the latest tech. The things a person can do with the ISY are pretty astounding! You should see the faces of my guests when I turn on my stereo, family room lights, and dim the kitchen with one press of a button! 3. Security - While I do feel that I was somewhat duped when I bought what Smarthome labeled as the "ELK M1 with Insteon Compatibility" (Not UD's fault, SH branded this in a way that made a LOT of people think it was more than it is.) Nonetheless, using programs to notify me through both the ISY and ELK has made me much more confident that I'll know if there is trouble (ie break-in, fire, etc.). Plus, I can keep tabs on the housekeeper and dog-sitter when they're there! 4. Now for the first negative....time and effort. I'm somewhat tech-savvy, and learn quickly, but I've found that searching through forums to be both a help and hinderence. Not that learning something new is a bad thing, I've just spent more time reading and testing that I thought would be needed. For example, I've spent most of my weekend (probably 16 hours) configuring my newly-installed garage sensor. I rendered myself lost when trying to contemplate the status of devices vs. actual status (ie Sensor "ON", Trigger Reverse [Wiki shows "Trigger Off"], Relay "ON", KPL programming, etc.). 5. This goes along with #4...I don't know how, specifically, but it would be nice to see the Wiki organized in a way that is more efficient to us common folk. More/better tutorials on items like setting up new devices to run a certain way, programming logic, using/configuring the Networking Module, and general troubleshooting would be awesome. Take LED brightness on KPL's as an example. There is a Wiki page with a very brief explanation of creating scenes for the LED buttons, but it wasn't until I stumbled upon a post by LeeG that I learned that using brightness levels in programs is a bad idea. Again, I don't have a specific layout in mind, just something that might enable the average user to avoid opening 12 tabs in Firefox with different forum posts, then having to disseminate between them to find the best/right way. These are the things that come to my mind when looking back over the past year. I hope that any criticisms are taken constructively, as I definitely feel that the pros outweigh the cons. I don't mind spending the time so long as my intended results are working. It's just that when they don't, finding out why can take a LOT of effort and this might surprise/deter the guy who gets into the world of HA thinking that it'll all operate his way out of the box. With all of that said, I completely understand how busy the UD team is making improvements and responding to customers. That's what I appreciate the most and it's the main reason why I'll keep visiting these forums and remain a UD customer as new modules are released. Without fail, the ISY is the best choice to manage all of my devices.

Scratch that....just found it.

Michel, I hope I speak for the rest of us in that it's more reasonable to take the time and get the updates fully tested before release. (ie, don't rush it out on account of this forum.) You guys have done a spectacular job in improving this device, so I'd rather wait it out for updates than to prematurely install them and hope for another fix down the road. Besides, you've gotta have some time to enjoy the New Year, right? (thumbs up)

I was attempting to check out your pricing for the Network module, however, when I click on "Purchase Modules" I'm being prompted that I need 2.7.7 to continue. I'm currently at 2.7.6 but I'm hesitant to update again until .7 is out of beta. Any chance I can still add-on modules at my current version?

I had thought that the scene would conflict, thanks for verifying this! Conversely, could I keep the scene in place of the M1 & M2 programs? If so, would this program work: Disable Motion: If Control "Kitchen Island" is switched On or Control "Kitchen Island" is switched Fast On or Control "Kitchen Main" is switched On or Control "Kitchen Main" is switched Fast On Then Set "Motion 1" Off Else Set "Motion 1" On What would be the pros/cons of this method? I'll probably just delete the scene and let the ISY take full control, just wanted to see if I could keep the scene and somehow just disable it with a program. Thanks for the help so far!

Rand, I have the opposite situation with motion in the kitchen. Currently, the motion sensor is linked to the "Kitchen Island" switch. I want the sensor's "Off" command disabled if someone manually hits the "Island" or "Main" switch, then to resume functionality once those switches are turned off. Can you verify this programming? M1: If Control "Motion 1" is switched On or Control "Motion 1" is switched Fast On Then Set "Kitchen Island" On M2: If Control "Motion 1" is switched Off or Control "Motion 1" is switched Fast Off Then Set "Kitchen Island" Off Disable Motion: If Control "Kitchen Island" is switched On or Control "Kitchen Island" is switched Fast On Control "Kitchen Main" is switched On or Control "Kitchen Main" is switched Fast On Then Disable program "M2" Else Enable program "M2" I currently have a scene named "Kitchen Motion" that has Motion 1 managing Kitchen Island. Do I need to delete this? Any help would be greatly appreciated. I've been racking my brain with this and thought I had it working. Thanks!