Michel Kohanim

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

Hi Chuck, It seems that your PLM is no longer communicating with your INSTEON network. This said, however, the first step is to upgrade to the official 2.7.0 release. After the upgrade, check Tools->Diagnostics->PLM Status/Info. If it shows disconnected, then, in all likelihood you either have a defective PLM or the cable that connects it to ISY. Do NOT reset/restore anything please as it would have NO impact in what you are currently experiencing. With kind regards, Michel

LG, Good questions. The procedure is quite simple: If you live in a state that observes DST, check DST and do NOT touch it unless your state decides otherwise. Now, checking and unchecking DST has zero impact on the actual time. It only has meaning when we move in and out of DST. So, as I mentioned: 1. Click on DST 2. Make sure you have the correct timezone 3. Click on Synchronize with NTP/Computer With kind regards, Michel

Hi Joe, Please do me a huge favor: go to Link Management | Advanced Options and let me know what mode you are on. Please contact us whenever you are free since I would surely want to fix this as much (if not more) than you do. I truly apologize for all the problems you've been experiencing. With kind regards, Michel

Hi Joe, This seems to be OK. Now, we need to figure out if #4 is in your PLM. Perhaps it would be best if we schedule a call for tomorrow so that we can login remotely and figure out the issues? If so, please give us a call tomorrow and we'll schedule you in. With kind regards, Michel

Hi Joe, Yes, please link it again. To copy/paste, click on the Save button (when the process is done), save it to a file of your choice, and then open the file, copy the contents and paste here. Or, if you wish, you can attach them to an email to support@universal-devices.com. With kind regards, Michel

Hello Joe, It's quite unlikely that both RLs would have the same exact issue. I suspect the PLM does NOT have a slave link for button 4 on your RL. Now, the main question is whether or not this link exists. As such, would you be kind enough to do the following: 1. Tools | Diagnostics | Device Links Table (make sure your RL is in programming mode) ... copy/paste what it shows 2. Tools | Diagnostics | PLM Links Table ... copy and paste the last 20 entries With kind regards, Michel

Hello Lewis, Here's the scenario: The old ISY firmware works with the older SHN products. 2.7.1 and above, requires newer SHN firmware because we assume they are going to have a different address space. With kind regards, Michel

Hello KEoqgtkQ, Unfortunately, not yet but it's on our todo list with low priority. With kind regards, Michel That looks good, but is there any way to automatically do it for the entire network? It will take me hours to do all my devices individually. Thanks

Hello, Please use the compare feature of Device Links Table. If you see more than 1 [ignore] flag, then please do a restore on the device. With kind regards, Michel

Hi aLf, Do not let it bother you ... if it does, simply reboot ISY and it will show you the flags again. It's a bug that's being worked on but with a very low priority since it has zero impact on the correct operation of ISY. With kind regards, Michel

rhughes, Thanks for the information. I am not at all worried about not being able to communicate with the NTP server (which is probably network related). What I am worried about is that your ISY didn't update for DST. This, if a bug, is a very serious one. Would you be kind enough to: 1. Make sure Day Light Saving box is checked 2. Manually adjust your ISY's time to 03.08.2009 01:59:50 AM If all OK, ISY should automatically adjust to 3:00 AM when the clock reaches 2:00. Please do let me know. With kind regards, Michel