Michel Kohanim

Hi David, Unfortunately not because we do not have access to the internal IRLinc database. We have been investigation what we could do to support this without making more trouble. Alas, and as you might have guessed, we've not been successful as of yet. With kind regards, Michel

Hi Steve, Thanks so very much for the update and your kind words about my wisdom! Based on what I see, I can almost assure you that once you replace the SWLs and remove some of the excess access points, all your problems are going to go away. I have contacted SmartHome and I am sure they will help you out. In the meantime, you might want to try the Scene Test. And, yes, ISY should have all the statuses reflected in the log. With kind regards, Michel

Hi Jeff, Would you be kind enough to send an email with this information to tech@universal-devices.com . I will see what we can do to support them. No, it's not as easy as formatting ... everything in the certificate is binary. With kind regards, Michel

Hi Jason, The problem is that the status of the motion sensor does NOT change till the internal timer turns is off. What you might want to try is Control instead of status. Control means every time ISY hears an On or and Off (regardless of the status of the motion sensor) then the program is re-evaluated. And, for testing purposes, it's always best to have a folder and separate this program in two: one for On and one for Off. This way you can actually see the status of the programs as they are being re-evaluated. With kind regards, Michel

Hi Steve, Thanks so very much for the update. First, I would like to know a little more about your sunset scene: 1. Do devices actually respond to your sunset commands? 2. Are you actually turning on/off a scene? 3. Is the status in ISY on when it should be off or the other way around? As far as query all, yes, indeed it does query every device for it status. Please note that there was a bug in the log which returned 0 for certain devices (when doing a query). And, unfortunately - and please forgive me - I really do not think adding more access points is going to solve the issue. Personally, I think adding more access points is going to cause more problems than fix anything. And, finally, I do not think anything would recompense for the issues relating to SWL 35. All this said, if you wish, send and email to tech@universal-devices.com and I'll see if I can help you get your SWLs replaced before spending more money on Access Points. With kind regards, Michel

Hi AnthemAVM, Currently, there's no way for this to work with ISY. Incidentally, this is a requirement we already track but with a low priority. Have you considered using free Dynamic DNS services? With kind regards, Michel

Hi kingwr, Yes, indeed this is an issue with the unit. It seems like you have file system/SD card error. I already have an email from you to which I am going to respond shortly with instructions for RMA. Sincere apologies for the inconvenience. With kind regards, Michel

Hi Jeff, The format is ISY specific. It uses X501 certificates but decomposed into p, q, exp, mod, with their lengths. We are planning to support CA certified formats in the future but have assigned it a very low priority since most people are not willing to pay between $14.00 to $400.00 per year for a certificate. With kind regards, Michel

Hi zyll, Apologies for a tardy reply ... I have already responded to your tech support ticket. Please note that incomplete means that ISY could not restore ALL devices. It does not mean that it completely failed. For instance, if you have any RF devices, you must put them into programming mode before you try a PLM restore. In releases 2.7.10 and above, ISY changes the icons for the nodes that it could not restore to 0101 (in green). In the meantime, it would be best to open the Event Viewer to level 3 ... this way, you will know exactly which devices are not restored. With kind regards, Michel

Hi delston, Apologies for the lack of clear documentation on this. The first thing is to note that you can only install the SSL certificate if and only if you are local to your ISY. Secondly, please note that installing 2.7.10 caused ISY to reload the default certificate. In which case, you will have to reinstall the new certificate. mgreene, Which URL did you use to install the certificate? With kind regards, Michel

Hi heatvent, Ah ... apologies for not understanding your question correctly. You are very much correct on both accounts: 1. This is INSTEON limitation 2. The scene commands do NOT have any attributes for the responders. They simply tell the devices to turn on/off/dim/brighten a scene. The responders MUST already be pre-programmed with on level/ramp rate for that scene Sorry ... With kind regards, Michel

Hi Chris, I am glad that it worked alas I am not satisfied for two reasons: 1. I want to track down the breakdown in our ticketing system. As such, if you do not mind, please do be kind enough to forward the ticket creation confirmation (if you received any) to support@universal-devices.com. I would sincerely appreciate it 2. The fact that it took you multiple times to restore your ISY is bothering me. As such, I would like to know what firewall software you have Now, going forward: 1. Please note that since you have a new PLM, you MUST do File | Restore Modem (PLM) otherwise none of your scenes will work nor would you get any status updates from any of your devices 2. I strongly recommend upgrading to 2.7.7 (after we determine the cause of intermittent restores) As far as Internet Access, in all likelihood your router is not UPnP enabled. It's generally a better idea to do manual port forwarding the instructions for which you find here: http://www.universal-devices.com/mwiki/ ... o_Your_ISY With kind regards, Michel

Hi heatvent, You can dim scenes (ISY scenes) from any ISY client. What you cannot do is to send Dim-to-level since INSTEON does not support this feature on scenes. So, what I would do would be: 1. Click on the Scene in the Admin Console 2. Adjust the desired on level / ramp rate for both of your devices 3. Click on each one of the devices in that scene, and then click on Copy Attributes button This way, all your controllers, including ISY, will have the same on level/ramp rate behavior and you can use any one of them to have the same exact behavior. When you want to dim, please dim the ISY scene instead of any of your devices. With kind regards, Michel

Hi Chris, First of all, I have to apologize for not responding to your voicemail. I have checked our ticketing system and I was not able to find you so I must assume that we did have a system failure. I do apologize. The first thing we want to do is to make sure you have a good backup. On top of that - and since you have access to an SD Card reader - please copy all the files on the SD Card to directory on your computer. Try rebooting ISY 4 times. If this does not help, please call our tech support or use http://www.universal-devices.com/contact.htm to open a ticket. Rest assured that your unit is under warranty and we either help you fix it or will have SH send you a replacement. Again, I am so very sorry for all the troubles. With kind regards, Michel

Mark, Please do NOT get 2413. You will have even more problems. With kind regards, Michel

Hi gfridland, Since this happened on an extremely small batch of KPLs and if you have not experienced intermittent behavior lately, I wouldn't worry about it. With kind regards, Michel

Clarence, Unfortunately the only way is to have a link to an external site (checkout the Img button at the top for syntax when you post). With kind regards, Michel

Hi Zick, Thanks for the update. Since addresses must be unique within ISY, therefore if you try to add another device with the same address, you should get a Request Failed error. With kind regards, Michel

Hi Jim, I agree with you ... I do not think this is noise related either. That's why moving them is what we need to isolate the problem. With kind regards, Michel

Hi endiablado, What you need to do is: 1. Factory reset your ISY (http://www.universal-devices.com/mwiki/ ... ur_ISY-99i) 2. Upon reboot, do File | Restore Modem (PLM) ... this factory resets the PLM 3. Add your devices using the first option (Remove existing links) With kind regards, Michel

Hi Mark, as I mentioned in my email I think your PLM is now resting in peace (or maybe not that peaceful!). Unplug it, do a factory reset on it, and retry. If this works, do a File | Restore Modem (PLM). If this does not work - although I still think it's your PLM - we have to do more investigation just to make sure. With kind regards, Michel

Hi Mark, as I mentioned in my email I think your PLM is now resting in peace (or maybe not that peaceful!). Unplug it, do a factory reset on it, and retry. If this works, do a File | Restore Modem (PLM). If this does not work - although I still think it's your PLM - we have to do more investigation just to make sure. With kind regards, Michel

Thanks so very much az1324. With kind regards, Michel

Hi az1324, This is wonderful and thanks so very much for sharing this with us. As far as CRLF, you might want to use the C encoding in the drop down (literally C programming encoding) in which case you can use \r\n for CRLF. Do you have a link to how this was done in more detail that we can link to in our Wiki? With kind regards, Michel

Mark, Please do NOT restore your devices. This is not device related nor ISY related. This is signal related especially if your RL is not linked to anything else. The main question is: did you add an access point in the room where the RL is supposed to reside? If so, just remove it. If you have changed the location of any of your access points, just go back to the original topology. With kind regards, Michel PS. All my emails to you bounced back.