AD8BC Posted December 23, 2008 Share Posted December 23, 2008 I recently installed a new Insteon motion sensor in our big closet, and an Icon relay switch on the closet light. I wrote a program in my ISY-26 that operates like this: When the switch is manually turned ON, and the motion sensor is OFF then it waits one minute and turns off the switch. That way if someone walks into the closet with the light on, it resets the timer. It works great... EXCEPT... sometimes, when the switch is turned ON the ISY doesn't see it turn ON. I can sit there sometimes and cycle the switch over and over and the status won't change. If I do a manual query on the device, or do a manual query on everything, afterwards it seems to work perfectly for hours. I first noticed this after I installed 2.6.11 (my existing revision didn't have a motion sensor option) and saw that many people were having some similar issues so I installed 2.6.12 beta and it all went away except for this new Icon. Anybody have any more ideas? Link to comment
ulrick65 Posted December 23, 2008 Share Posted December 23, 2008 I recently installed a new Insteon motion sensor in our big closet, and an Icon relay switch on the closet light. I wrote a program in my ISY-26 that operates like this: When the switch is manually turned ON, and the motion sensor is OFF then it waits one minute and turns off the switch. That way if someone walks into the closet with the light on, it resets the timer. It works great... EXCEPT... sometimes, when the switch is turned ON the ISY doesn't see it turn ON. I can sit there sometimes and cycle the switch over and over and the status won't change. If I do a manual query on the device, or do a manual query on everything, afterwards it seems to work perfectly for hours. I first noticed this after I installed 2.6.11 (my existing revision didn't have a motion sensor option) and saw that many people were having some similar issues so I installed 2.6.12 beta and it all went away except for this new Icon. Anybody have any more ideas? Install the latest Beta of 2.6.13 and see if that helps. Restoring the device may help as well. Have you checked the event log and see if you are getting anything into ISY when you turn on the ICON? Link to comment
AD8BC Posted December 23, 2008 Author Share Posted December 23, 2008 No I didn't check the log, I watched the device directly on the screen. I'll update the firmware after I get back home from Christmas vacation and give it a shot.... Thanks! Link to comment
MikeB Posted December 23, 2008 Share Posted December 23, 2008 AD8BC - Could you post the event viewer log from your testing? Specifically, I'm interested in what the Event Viewer shows when it DOES successfully see that your switch was turned on compared to when your ISY DOESN'T recognize that the switch was turned on. Link to comment
Michel Kohanim Posted December 23, 2008 Share Posted December 23, 2008 AD8BC and MikeB, Lately we have been receiving increasing amount of trouble tickets relating to SWL communications issues. These are related to V35 and V40 specifically whereby either you cannot communicate with them OR you do not get status responses from them. What version SWLs do you have? With kind regards, Michel AD8BC - Could you post the event viewer log from your testing? Specifically, I'm interested in what the Event Viewer shows when it DOES successfully see that your switch was turned on compared to when your ISY DOESN'T recognize that the switch was turned on. Link to comment
MikeB Posted December 23, 2008 Share Posted December 23, 2008 Hey Michel - The SwitchLinc Dimmer I was discussing with you early is an older v.27. I still need to troubleshoot further to find the root cause. I'm confident that if I spend a couple hours I can narrow it down. Link to comment
AD8BC Posted December 24, 2008 Author Share Posted December 24, 2008 Michel, if I weren't getting ready to catch a plane, I'd go take it out of the wall and look I can tell you it's an Icon, one of the ones that they just discontinued. If this helps, it shows up in the ISY as a (2876S) Icon On/Off Switch v.35 -- this may mesh with the SL v.35 problem you mentioned. AD8BC and MikeB, Lately we have been receiving increasing amount of trouble tickets relating to SWL communications issues. These are related to V35 and V40 specifically whereby either you cannot communicate with them OR you do not get status responses from them. What version SWLs do you have? With kind regards, Michel AD8BC - Could you post the event viewer log from your testing? Specifically, I'm interested in what the Event Viewer shows when it DOES successfully see that your switch was turned on compared to when your ISY DOESN'T recognize that the switch was turned on. Link to comment
Michel Kohanim Posted December 24, 2008 Share Posted December 24, 2008 Hi Mike, Yes, please do narrow it down! AD8BC, Thanks! I think Mike is going to troubleshoot for us and then I can be more certain. With kind regards, Michel Link to comment
AD8BC Posted December 24, 2008 Author Share Posted December 24, 2008 Thanks Michel! And be sure to take time to enjoy the holiday! I'll be back home in a week and then I can do some troubleshooting for you. Hi Mike, Yes, please do narrow it down! AD8BC, Thanks! I think Mike is going to troubleshoot for us and then I can be more certain. With kind regards, Michel Link to comment
Stowaway Posted January 1, 2009 Share Posted January 1, 2009 I just noticed that the Remotelinc button I have linked to a 2456D2 Icon Lamplinc stopped working after upgrading to 2.6.13. I have attempted to restore as well as remove and reinstall the link to the button with no success. The Lamplinc still works otherwise for timers as well as on/off from the console. The other Remotelinc buttons work as well. Anybody else experiencing this issue with Icon devices....? Link to comment
upstatemike Posted January 1, 2009 Share Posted January 1, 2009 Are you sure the problem is the Icon lamplinc? Did you try linking that RemoteLinc button to something else to confirm the button still links OK? Link to comment
Michel Kohanim Posted January 1, 2009 Share Posted January 1, 2009 Hello Stowaway, Please try restoring the LampLinc. If this works, then the problem is a bug in LL where duplicate links are created. With kind regards, Michel I just noticed that the Remotelinc button I have linked to a 2456D2 Icon Lamplinc stopped working after upgrading to 2.6.13. I have attempted to restore as well as remove and reinstall the link to the button with no success. The Lamplinc still works otherwise for timers as well as on/off from the console. The other Remotelinc buttons work as well.Anybody else experiencing this issue with Icon devices....? Link to comment
Sub-Routine Posted January 1, 2009 Share Posted January 1, 2009 I just noticed that the Remotelinc button I have linked to a 2456D2 Icon Lamplinc stopped working after upgrading to 2.6.13. I have attempted to restore as well as remove and reinstall the link to the button with no success. The Lamplinc still works otherwise for timers as well as on/off from the console. The other Remotelinc buttons work as well.Anybody else experiencing this issue with Icon devices....? If the link was created previously and you are not interpreting the button press using a program the link should work with or without the ISY. Changing the firmware in the ISY would have no effect on established links. Rand Link to comment
Stowaway Posted January 2, 2009 Share Posted January 2, 2009 Gents - Thanks for your comments. Sorry I was delayed in returning to the forum to update my progress by a New Year's day gathering. I have resolved the issue by clearing the links and factory reseting the remotelinc as well as the lamplinc followed by reinstalling the links to each of the buttons. Must have been a fluke as all seems to be fine now!!! Link to comment
Michel Kohanim Posted January 2, 2009 Share Posted January 2, 2009 Hi Stowaway, Thanks for the update. My personal feeling is that you are going to have the same problem again especially if you try to program this appliancelinc to anything else. Please do keep us posted. With kind regards, Michel Gents - Thanks for your comments. Sorry I was delayed in returning to the forum to update my progress by a New Year's day gathering. I have resolved the issue by clearing the links and factory reseting the remotelinc as well as the lamplinc followed by reinstalling the links to each of the buttons. Must have been a fluke as all seems to be fine now!!! Link to comment
Stowaway Posted January 2, 2009 Share Posted January 2, 2009 Hi Stowaway, Thanks for the update. My personal feeling is that you are going to have the same problem again especially if you try to program this appliancelinc to anything else. Please do keep us posted. With kind regards, Michel Gents - Thanks for your comments. Sorry I was delayed in returning to the forum to update my progress by a New Year's day gathering. I have resolved the issue by clearing the links and factory reseting the remotelinc as well as the lamplinc followed by reinstalling the links to each of the buttons. Must have been a fluke as all seems to be fine now!!! Michel, The problem device is an Icon LampLinc. Is this because the early "economic" Icon product design does not interact nicely with the latest ISY firmware? I assume that this means that Icon devices should not be used for Mission Critical purposes !!! ROFLMAO !!! Link to comment
AD8BC Posted January 6, 2009 Author Share Posted January 6, 2009 Well since I got back home from vacation I have been doing a little playing around. I still have the same issue with my new Icon Relay switch for the bedroom closet. When I turn it on locally, the status does not change in the ISY. However, it always seems to recognize a Fast ON and I think it recognizes an ON after that. Or, the same old Query Device works and then it will also recognize the Local ON after that for a time. I also seem to have an issue with at least three other switches... two SWLs and one KPL. And with these it's not always a local ON that isn't recognized... it's sometimes a remote group ON that will do it. I know I have a problem because I have a group that illuminates a KPL LED when any inside light is on (uses an ISY program). Sometimes when one of these lights is turned ON the progam won't run because it won't get the status. And this all seemed to noticeably happen after upgrading to .13. I loaded the beta after having issues with .11 and my motion sensor... I'm at work now but I'll get rev levels of the devices I am having difficulty with tonight or tomorrow. Link to comment
Stowaway Posted January 7, 2009 Share Posted January 7, 2009 Well since I got back home from vacation I have been doing a little playing around. I still have the same issue with my new Icon Relay switch for the bedroom closet. When I turn it on locally, the status does not change in the ISY. However, it always seems to recognize a Fast ON and I think it recognizes an ON after that. Or, the same old Query Device works and then it will also recognize the Local ON after that for a time. I also seem to have an issue with at least three other switches... two SWLs and one KPL. And with these it's not always a local ON that isn't recognized... it's sometimes a remote group ON that will do it. I know I have a problem because I have a group that illuminates a KPL LED when any inside light is on (uses an ISY program). Sometimes when one of these lights is turned ON the progam won't run because it won't get the status. And this all seemed to noticeably happen after upgrading to .13. I loaded the beta after having issues with .11 and my motion sensor... I'm at work now but I'll get rev levels of the devices I am having difficulty with tonight or tomorrow. It does appear that the various Icon lamplinc and appliancelincs that I have, do not consistantly manage "Status updates" with the recent ISY firmware updates. None of my Icon problems are mission critical, hopefully future ISY firmware updates will resolve.... Link to comment
AD8BC Posted January 8, 2009 Author Share Posted January 8, 2009 It has gotten more interesting. I downgraded back to 2.6.8... Same issues. But I did some further poking around... It still did not reliably hear when devices turned ON. But it always heard FAST ON, OFF, FAST OFF. But here's the kicker -- in some cases, on the affected devices that are dimmers, I could not use the ON command from the Administrative Console... If the light was ON at any level, clicking on ON would turn the unit OFF. Then, after doing a REFRESH ALL, everything seems to work again. Link to comment
Michel Kohanim Posted January 8, 2009 Share Posted January 8, 2009 Hello AD8BC, These are known issues with the latest SWL, KPL, and LL/AL firmware. SmartHome is trying to resolve/debug/pinpoint these issues as we speak. How long more do you have on your 30 day? With kind regards, Michel It has gotten more interesting. I downgraded back to 2.6.8... Same issues. But I did some further poking around... It still did not reliably hear when devices turned ON. But it always heard FAST ON, OFF, FAST OFF. But here's the kicker -- in some cases, on the affected devices that are dimmers, I could not use the ON command from the Administrative Console... If the light was ON at any level, clicking on ON would turn the unit OFF. Then, after doing a REFRESH ALL, everything seems to work again. Link to comment
AD8BC Posted January 8, 2009 Author Share Posted January 8, 2009 Michel, Unfortunately, with the exception of the one new Icon relay switch, two Icon lamplinks (that have been running fine) and the motion sensor, the rest of the items on my network that I have been having difficulty with are 14-20 months old, unless the new items are somehow corrupting communications with the old ones. This morning everything seems to be running well since I manually ran the "Query All" last night, with the exception that my motion sensor doesn't seem to be reporting to the ISY -- could this be because I went from .13b to .8? I'll play a little more after work this evening. Thanks for your help! Oh, what did you mean by how long more on my 30 day? -- Bill Link to comment
Michel Kohanim Posted January 9, 2009 Share Posted January 9, 2009 Hello Bill, Thanks so very much for the update. This is not good at all. Has anything else changed in your environment? A new computer, an older monitor, anything at all. I really do not think the difference between version would cause such drastic problems unless the PLM is not handling the i2 commands (and is becoming deaf/dumb). This is very possible if you have PLMs version 58 and below. Please do be kind enough to keep me posted. With kind regards, Michel Michel, Unfortunately, with the exception of the one new Icon relay switch, two Icon lamplinks (that have been running fine) and the motion sensor, the rest of the items on my network that I have been having difficulty with are 14-20 months old, unless the new items are somehow corrupting communications with the old ones. This morning everything seems to be running well since I manually ran the "Query All" last night, with the exception that my motion sensor doesn't seem to be reporting to the ISY -- could this be because I went from .13b to .8? I'll play a little more after work this evening. Thanks for your help! Oh, what did you mean by how long more on my 30 day? -- Bill Link to comment
AD8BC Posted January 14, 2009 Author Share Posted January 14, 2009 Well, Michel, version .8 has been running reliably since last Thursday. All statuses seem to be reporting just fine to the ISY (with the exception of the motion sensor, I may have to re-install it into the ISY. Link to comment
Michel Kohanim Posted January 14, 2009 Share Posted January 14, 2009 AD8BC, Thanks for the update. Would you be kind enough to check the version of your PLM (Tools->Diagnostics->PLM Status/Info). With kind regards, Michel Well, Michel, version .8 has been running reliably since last Thursday. All statuses seem to be reporting just fine to the ISY (with the exception of the motion sensor, I may have to re-install it into the ISY. Link to comment
AD8BC Posted January 14, 2009 Author Share Posted January 14, 2009 Sure Michel, it comes up v52. AD8BC, Thanks for the update. Would you be kind enough to check the version of your PLM (Tools->Diagnostics->PLM Status/Info). With kind regards, Michel Well, Michel, version .8 has been running reliably since last Thursday. All statuses seem to be reporting just fine to the ISY (with the exception of the motion sensor, I may have to re-install it into the ISY. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.