Michel Kohanim

Hi Joe, The motion sensor sends an On if and only if: 1. Motion has been sensed 2. The current state is off So, if you have a timeout of 10 seconds, and if motions is sensed within those 10 seconds, then motion sensor will never send off till no motion is sensed within 10 seconds after the last motion. With kind regards, Michel

Hello Joe, Yes, the unlinking will continue and all the RL links are removed from all other devices (that the RL was linked to) + the PLM. With kind regards, Michel

oberkc, I sure will. Thanks so very much for the offer. With kind regards, Michel

Hi aLf, The algorithm is from NOAA. With kind regards, Michel

Hello drw and oberkc, Thanks so very much for the detailed responses. I am really at a loss as to what could have caused these problems mostly because I have not been able to reproduce it with/without NTP connection and even with a failing NTP server. And, it seems that drw's sunset programs ran at the correct times but oberkc's didn't. It's quite baffling and I do take this issue very seriously (we cannot expect anyone to reboot just to get the correct time). As such, I am going to add this to our list of bugs and have it tested more thoroughly. Thanks again and with kind regards, Michel

Hi LG, Perhaps your port forwarding rules are no longer in effect? With kind regards, Michel

Hello slpelts, Try this: If From Sunset To Sunrise (next day) Then ... Else ... With kind regards, Michel

Hi Joe, I am sorry ... I think I didn't get your question correctly. You are right: all on/off is only for those that are linked to the RL. So, if the RL All on/All off cause unrelated devices to turn on/off, then I suspect you have slave links in the other devices. Can you verify that this is indeed the case? With kind regards, Michel

Hello Joe, The All On/All Off buttons on RL turn all devices that have ever been linked to any of the RL buttons. That is, regardless of which buttons were programmed, any device linked to RL will turn on/off. With kind regards, Michel

Hi again, thanks so very much. I will check into this more closely ... the main issue is that I cannot reproduce this issue no matter what I do. With kind regards, Michel

Hello all, Would you be kind enough to tell me which firmware version of ISY do you have? With kind regards, Michel

Hello legalguy, Based on what I see, you should see Running Then while office work hours is false. I assume office work hours is false more than 5 minutes. With kind regards, Michel

Hello to_lighter, I think perhaps now is a good time to schedule a call with our tech support. What I see and based on what you describe is something rather impossible unless you have discovered a bug. With kind regards, Michel

Hello oberkc, Please make sure you have Daylight Saving box checked in the configuration page without which ISY does not automatically adjust for DST. As far as not synching with pool.ntp.org, please make sure ISY has access to the Internet. With kind regards, Michel

Hello Traditore, Unfortunately, till such time that APs can become controllers, this is the only way (polling for status). With kind regards, Michel

Brian H, Please do give a couple of days to get to the bottom of this ... I do have PLM 85 but it may have been Beta and the production/shipping is 7A. I shall keep you posted. With kind regards, Michel

Hello to_lighter, You are right about the progress bar: it's the best approximation. If you have non-communicating devices, then the approximation gets inaccurate. By links I mean PLM links. So, would you be kind enough to: 1. Make sure you have a quiet environment 2. Tools | Diagnostics | PLM Links Table ... wait for completion and then click on the count You used to have 1700 and I can guarantee you that you will not have reliable status information if your count remains this high. With kind regards, Michel

Hi NJ_Mark, Yes, your understanding is correct! With kind regards, Michel

Hello Traditore, No, it does not. With kind regards, Michel

to_lighter, You will need PLM v.85 ... again, you will have to somehow reduce the number of links (or number of scenes) you have otherwise you are always going to have status problems with the devices you linked "last". With kind regards, Michel

Hello to_lighter, A very good question and something that we had never thought of before. Although crude, please try the following (you have 16 seconds for the 3rd step) 1. Clearly mark the addresses for each one of your devices 2. Open Tools|Diganostics|Event Viewer (level 3) 3. Start the Restore process, look at event viewer: it will tell you which device is being worked on. You have almost 16 seconds to put your MS into programming mode With kind regards, Michel

DEGoodrich, Do you have the DST checkbox checked? What were the symptoms with your IES touchscreen? And, are you saying that NONE of your programs worked? With kind regards, Michel

Hi Randy, It's best to do neither! Please wait for 2.7.2 (hopefully by the weekend) which should alleviate some of the missed events (especially if you have the in a sequence). If you really have to, it's best to start from scratch. The next best thing would be to factory reset your switches and restore from ISY. With kind regards, Michel

NJ_Mark, No apologies are necessary; that's what this forum is for. This is a frequently asked question and one which requires the memory map for IRLinc which we do not have access to. I have requested documentation for IRLinc with this information but, as of yet (almost 5 months) it has not been forthcoming. With kind regards, Michel

to_lighter, Please look at the event viewer and you will clearly see the devices that have failed. Incomplete means that ISY was not able to restore all the devices. In the same vein, it also means that only the devices that failed were not restored while all others have been restored successfully. With kind regards, Michel