Michel Kohanim

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

Hi aLf, Sorry I must of missed it. When the time changes (either through DST or otherwise), all the last run time, next run time, etc. will be reset till the next time that they are calculated. As far as Run at Start Up, this is an in-memory/display bug but it has ZERO impact on the operation of ISY: in case your ISY reboots, all those programs that were supposed to run at start up would still run at start up and the flag reappears. With kind regards, Michel Michel: Posted this earlier on another thread and never got a response. I've since corrected the time issues by "forcing" them through toggling Home & Away. None are a big deal, but wondered if there is a simple answer to why it happened. The Run at Startup is the most troubling. To fix that I physically had to go in (remotely) and re-add the run at startup call to that particular program. I assume that at DST the time moved and therefore the last runs and next runs couldn't keep up? Just wanted you to have a picture of what I saw. aLf

Hello, All NTP servers have mechanisms which prevent clients to query more frequently than some predefined periods. As such, please do make sure that your refresh interval is not less than 24 hours since, especially during heavily accessed times, the server will simply ignore your request. Now, not adjusting to DST is a cause for concern. What versions of ISY firmware do you have? Adjusting for DST has NOTHING to do with the NTP server: ISY has to adjust the time automatically. With kind regards, Michel

Hi Joe, No, we do not support it yet (or, better said: we do not have official support for it) and will not add support until such time that we iron out our support for all the EZIOxxx devices. With kind regards, Michel

Hello drw, Would you be kind enough to let me know which URL do you use? Do you use: http://www.unviersal-devices.com/99i OR do you access your ISY's URL directly? With kind regards, Michel

Hi aLf, My pleasure ... and, yes, the reason you do not see it at home is because you are local. SSL kicks in if and only if you are accessing your ISY remotely. With kind regards, Michel

Hello W, Apologies for the inaccuracy: I do not know of a programmatic way of making that button non-toggle. I do not think that's the issue. The controller is always group 1 = the 2 min button. With kind regards, Michel It is on and off on mine... (there is a setting for that as well as an extra key cap that says on/off). I am sure it is the manual someplace if you want to look it up. I wonder if that is why I am seeing this problem, and other are not? W

Joe, It has a capacitor which should keep your time for up to 6 hours. If by power cycling you lose the time, then: 1. If you do NOT have automatic synchronization with NTP checked, then, the battery is not working 2. Otherwise, your NTP server is providing the wrong time Please note that ISY, by default, adjusts the time to the NTP server (if one is defined) at reboot. So, unless you have change this, I suspect the problem is your NTP server. With kind regards, Michel

Hi aLf, This is 100% normal simply because you are signing and using YOUR own certificate. If you wish to pay for a Certificate Authority signed certificate (between $14.00 to $400.00 year), let me know and I'll set it up for you. Please note that you will not get any more secure that what you already have. With kind regards, Michel

Hello W, As far as I know - and unless you have figured out otherwise - H is only OFF. I have not been able to use H to turn anything on. 2 Minutes button is group 1 which is the load button. With kind regards, Michel

Hi W, Sorry ... yes as long as they are both controllers in the same scene. Now, if you wish to turn on the timer remotely (using another button on the KPL), then only thing you can do is to put the desired timer button as a "RESPONDER" with the remote button as the controller. I do apologize for the confusion. All I am trying to say is that no matter what you do, you will be out of synch simply because the KPL timer buttons can never be controllers. As you suggested, you can make a program that simply turns of the remote button but, then, you will have to write the same program 7 times for each one of the timer buttons. With kind regards, Michel

Hi W, I guess but I do not think you have to test the status. i.e. you already know that someone turned it either on or off. The main problem is that you will have to do this for all 8 buttons which makes it not worthwhile. If you only have ONE kpl button for which you want to do this, then simply put the Load on the timer and that button as controllers in the same scene. This way, whenever the timer turns off, then your other KPL will also turn off. With kind regards, Michel I guess I could write a quick program that would run 31 minutes later to check the status and turn off KPL controller if it is still on, right? W

Hello smileyw, You can actually put the timer buttons in a scene as responders and have another KPL button in there as a controller. This way, you can turn the timer's load on for the amount of time indicated by button. The only problem is that your KPL controller will never know when the timer has turned off. With kind regards, Michel