cartman413

Thanks agin LeeG, I was thinking about all sorts o ways to reproduce what i'm doing with programs instead of scenes. But just seems like a big headache. My little exercise here was a perfect example of knowing enough to be dangerous. LOL thanks again for the help. After realizing the trigger reverse was my issue I was able to research the issue and have seen you have given this advice many times. appreciate the patience! btw are you an UDI programmer? seems like you have been an ISY guru forever based on the posts I've been seeing. I have a quick question about creating my on query program. Do I need to query every single button? or just each device?

Okay, i think that is what has been causing my issue. It wasn't a communication issue, the ISY status was updating fine, but when i hit query it would change (flip) as it would return the standard status instead of the "trigger reverse" status and then i would close the door and nothing would happen as the state would match now. The query i would run was always pulling the opposite state. So when i moved the door to the next position it would match the trigger reverse state again, i hit query again, and it reports the opposite state again. Like a dog chasing it's tail. So it sounds like this is a bug in the I/O linc software? or is this a bug with the ISY ? Any thoughts on how to maintain the state of the I/O linc? I'm assuming the query is so the ISY can resync every night. But it's actually throwing it out of sync with the garage. The trigger reverse is necessary because It lights the keypadlinc buttons as well. So off (closed) is a dim light and On (Open) is a lit LED key. Is it possible to change the query to not include the garage I/O linc? or is the only solution to buy a new sensor? I was hoping i could change the sensor state using a program in the ISY, but that doesn't seem to do anything. (any help on that as a work around would be appreciated as well.)

Hi LeeG, Okay, I thought it was a reference to the terminals, but now i get what you are saying. I didn't know that you could even change that function outside of the "Trigger Reverse" check mark. The kit i have just has two magnetic bars and they attach to the I/O link via GND and Sensor. Can you help me understand the work around? hoping my program will fix the "flip" when the ISY Query happens. But less complicated always seems better so If I can not have it switch on me by just reversing some connections, that would be ideal. Also, I wonder if the change of state overnight is what was causing the issue as i noticed if i unselect the "Reverse Trigger" the status doesn't update properly until I open and close the garage. Appreciate the Help!

The LED was actually doing something It had like a slight flicker or something. It was as if it was blinking, but the blink was so fast you could barely tell. I'm fairly sure that it was receiving signal as I can regularly update and control that bank of lights with the ISY and my phone. And the status has always been up to date from what i can tell. Sorry I should have mentioned the flicker when i said I think it was passing the test. Not sure why it doesn't flash green though. I took it as "Solid White" meaning it was passing. But it definitely looked different than when in normal operation due regular flicker.

HI LeeG, Not sure I understand this fix. Isn't the NO/NC the terminals for the replay in the I/O linc? i.e. isn't that how i close the circuit to activate the garage? If I set it to N/C won't it just stay closed all the time (like keeping the garage button pressed all the time?) I like the trigger reverse setup cause in mobilinc and open garage is red and a closed garage is Green (i think colors are tied to on/off status.) I was thinking of using this after the ISY runs a query at 3am. Any thoughts on this? If Time is 3:03:30AM And Status 'Garage Sensor' is On Then Set 'Garage Sensor' Off Else - No Actions - (To add one, press 'Action') Thanks!

Thanks again for the reply. So I do not have any 240 devices save the A/C. I have 240 breakers for an Oven but it's not in use. We are all gas here. The A/C has not been on at all either. I know by looking at my panel layout that the Master Bed (where i have a keypad and dualband switchlinc installed) is on the same phase as the garage door opener. I ran the 4 push test just now. The Master Bed room dual band stays solid white. The other set Dual band in my Living room blinks red. So that tells me that the garage door is communicating with the switchlinc in the master bed which communicates over RF with the PLM. Does that make sense given the Log saying 1 hop? Or should that be 2 hops? When I was having the issue, the master bed did not have any issues that i know of communicating with the ISY, but i guess it's possible since most of those are scenes that are written to the insteon devices themselves. It stil seems odd to me that a on trigger sent from the ISY would go through no problem but the return status message send a second or two later would not make it back to the ISY. Guess we can't tell much more until it happens again?

Of course as soon as i'm asked to post a log, the behavior has corrected itself this AM. However I got a garage was open for more than 5 minutes messages right after my ISY was scheduled to do it's Query All at 3am. Also the state of the Garage has flipped. Now Off is Closed and On is Open. (I use Mobilinc and I label them so I know when it's changed). (not sure if this is indicative of a communication error?) I've attached my log file. First four triggers were from the ISY interface (open, close, open, close) than a couple more from the mobilinc interface. Mobilinc has an issue where i have to flip the switch back to off again to make the I/O linc activate. So that will probably show an extra line in the log for that. I did the PLM count it's 41, 41, 41 I have not moved the I/O linc to the ISY plug (have to pull a ladder out and it's working currently). My setup is relatively simple currently. Two Keypadlincs (non-dualband) and two Switchlinc dimmers (dual-band), the ISY and the I/O linc in the garage. They are grouped 1 keypadlinc and 1 switchlinc (DB) share a breaker controlling lights in two rooms. My PLM is located in my network box plugged in there. The 2nd plug of that receptacle has a power strip with a small unmanaged switch and my router. Both very low power consumption boxes. The breaker it's attached eludes me as I've gone through about half of my breakers and never found the right one. (we have two panels) But I do know it's not on any of the AFCI circuits. I was trying to isolate what phase it was on earlier, but when I plugged in and everything seemed to communicate fine I stopped my search. It's odd that I never have issues with sending commands from the ISY to the garage, and status for all the other devices seem to have status in sync so I discounted the communication issue. But now that I see everyone's comments, is it possible to see if the return router for updating status from the I/O linc is different than the transmission of the initial command? Thoughts would be appreciated, and will definitely post a log when the behavior starts again. Thanks, ISY-Events-Log.v4.0.5__Sun 2013.07.14 09.29.11 AM.txt

Thanks for the tips, but nothing seems to work. any other troubleshooting thoughts? the compare showed everything identical and one (ignore/identical) I did the PLM restore and even did factory restore on the I/O linc. nothing seems to work.

Thanks Lee. I must have mixed up manuals or something no idea why my search for resume bright didn't bring that up. Again that fixed that issue.

Thanks for the reply. I only see résumé bright as part of the x10 commands. And all it says is to have the turn the initial on level to something other than 0. It did say something about locking the initial on level but that required setting it while to linked to a controller. And to not link it to a controller for 4 minutes. Does that see. Right? Or am I just reading the manual wrong?

Hi, Thanks for all the help, as you can see i'm working on a new install and have plenty of questions. I have an I/O linc garage sensor that does not update it's status in the ISY when the garage is opened and closed. If i run an manual query, it updates with 100% accuracy. Also all the keypad lincs that are responders to the I/O linc show the correct status every time. (lit for open, dim for closed) It's an I/O linc 4.1 2450 with garage sensor kit. I'm very confused as to why the status is not being reported to the ISY as the garage opens and closes. Also after reading other posts. The greenlight on the I/O linc does come on and off as well when the garage moves. The way my garage is set up is ON means closed and OFF means open. my settings are currently TX on LED, Trigger Reverse, and Momentary A. (hold of .2 seconds) Also, the garage responds 100% of the time when sending a open/close command from the ISY interface. But the status never updates without a query. Seems like something is not linked properly, but I thought the ISY was automatically linked with all the devices to receive status? TIA.

Hi, I have a Keypadlinc that I have setup to have a dimmer up and down switches in the C and E position. the Dimmer send 6 brighten or dim signals when each is pressed once and a fast off from either C or E will set it to 100% or 25% respectively. My question is when I have dimmed the lights. Then hit off. When i hit ON again the lights come on at 25% (or the level they were at when turned off) but the ISY will report that the lights have come on at my initial turn on rate of 75%. I have to send a manual query for the ISY to get back in sync. As it seems the switch is remembering the last setting and ignoring the initial on level expected by the ISY. I could not figure out how to disable the remember feature in the keypadlinc if that is possible. My other thought was to write another program to correct the on status should the switch turn on and after a query the light level doesn't match 75%. (if a program containing a query is even possible.) So I thought I would ask the gurus on this board for their help! thanks.