superfreq Posted February 8, 2010 Share Posted February 8, 2010 I have my Elk M1G talking to a ISY-99i with a IOLinc v.36 Insteon module to monitor my garage door status. My problem is that the ISY does not seem to update the status of the sensor until I do a Query on it from the ISY Admin console. I currently have Trigger Off, LED on TX, and Momentary:A set to true and everything else is set to false and timeout is set to 2 seconds. For some reason it seems to update the on status but not the off sometimes, and usually incorrectly. So when the door closes it says garage door is open, and then after a query it says closed (Durring all of this it did not register the opening of the door). Do I need to set these devices up in a scene? Do I need to setup a program to query the device every few seconds? Is there a better way to have this setup to have it just update the status when it changes? Link to comment Share on other sites More sharing options...
Michel Kohanim Posted February 8, 2010 Share Posted February 8, 2010 Hi superfreq, Before we delve deeper into what we should with ISY, would you be kind enough to: 1. Open the Event Viewer on level 3 2. Short pins Common and NC and check what you see in the Event Viewer 3. Short pins Common and NO and check what you see in the Event Viewer If you do not see anything in the Event Viewer, then the problem is either signal related (the signal is not getting from your IOLinc to the PLM) OR the IOLinc is not setup correctly in ISY. And, finally, you might have a defective IOLinc. Please note that momentary settings only impact the relay and not the sensor. Depending on your garage door, you either need NO or NC. And, sometimes (if in toggle) then you would to connect both. In most cases, NO should work fine. With kind regards, Michel Link to comment Share on other sites More sharing options...
superfreq Posted February 8, 2010 Author Share Posted February 8, 2010 Do the settings in the ISY override the settings on the IOLinc? I remember putting the IOLinc into what I believe was mode C, but I could have done this wrong. I am a bit confused by there being similar settings on the ISY. I will test out the event viewer when I get home. Thanks for the help! Link to comment Share on other sites More sharing options...
superfreq Posted February 9, 2010 Author Share Posted February 9, 2010 Strange thing, today it is working but the signals are backwards. I switched them in the logic and everything is running well. We will see how long this lasts . It might have just been an communication error. Link to comment Share on other sites More sharing options...
Michel Kohanim Posted February 9, 2010 Share Posted February 9, 2010 Hi superfreq, If the signals are backwards, then you might want to use the NC instead of NO or vice versa. Please note that the momentary modes are for the relay and not the sensor. In short, if you do not use the relay portion of IOLinc, these settings do not mean anything. With kind regards, Michel Link to comment Share on other sites More sharing options...
kaplansa Posted October 13, 2010 Share Posted October 13, 2010 Sorry for the cross-post (see: http://forum.universal-devices.com/view ... highlight=) but this thread may be more relevant for my situation. And I may have done this to myself. Basically... I purchased an ISY-99i and a couple of garage door kits and actually everything was great for about a week. I have a program that sends me an email every time the garage door opens (sensor changes from on --> off). Then this past weekend I upgraded my ISY to firmware 2.8.3 beta. Realizing I didn't need to upgrade to the beta, I downgraded back to 2.7.15. I never lost a single program or device in the process, even though I've been taking backups along the way (kudos UDI!) BUT since I upgraded and subsequently downgraded, my I/O Lincs for my garage door are acting funny. They don't update the ISY status unless I manually query them. So now my email-when-garage-door-opened program no longer runs. I'm reading this thread and thinking it's unlikely the I/O Lincs broke or all of a sudden were unable to communicate since it all happened precisely when I did the upgrade and downgrade. So the question is if (a) can you downgrade the ISY in the first place? ( could there be a bug in 2.8.3 that caused this behavior that propagated to 2.7.15 when I downgraded? © could there be a simple fix like unpairing the I/O Lincs and re-pairing them to the ISY? Thoughts? Thanks!! Link to comment Share on other sites More sharing options...
kaplansa Posted October 13, 2010 Share Posted October 13, 2010 For the record, I removed my garage door IOLinc from my ISY and performed a factory reset (on the IOLinc) and plugged it back it and repaired. Same as before - the IOLinc status won't update the ISY unless I perform a manual query. What's odd is that this was working before I went to the beta firmware and then rolled back to 2.7.15. Just wanted you to know I tried. Thoughts? Link to comment Share on other sites More sharing options...
LeeG Posted October 13, 2010 Share Posted October 13, 2010 When a device stops reporting status it is likely either the link records in the device or the link records in the PLM have been corrupted or lost. With the last thing done (before your attempts to recover) being an update to the ISY I would look to the link records in the PLM first. Since you factory reset the I/O Linc that erased all the link records in the I/O Linc so a Restore Device must be done to restore the link records in the I/O Linc. If that does not resolve the problem the Restore Modem (PLM) would be the next step. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.