Michel Kohanim

Hi Joe, If you only had the ERR light blink, then there was an issue with your file system. If you had ERR/MEM blinking then there was an issue with Network/router. What version of ISY firmware are you running? With kind regards, Michel

MSM, I do apologize for the inconvenience and all the time you've spent on getting this to work. It does seem like your unit is defective. Please do let us know if you have any trouble getting a replacement unit. With kind regards, Michel

Hi Rich, If you are starting from scratch, then please use either the first or the second option. My preference is the first option because it would take much less time (ISY does not have to read in all the records in your devices). It's always best to start from scratch since in the majority of cases, there are half/orphaned links which would cause unexplained behavior down the road. With kind regards, Michel

Hello osullys, Just as a background, this is how we rate features/bugs: 1. The number of requests (in this case only two requests) 2. How easy is it to implement (in this case 2, 1 being trivial and 5 being non trivial) So, there's a likelihood that we'll have it implemented shortly not because it's a hotly requested feature but because it's not that difficult to implement. With kind regards, Michel

Hello Dave, Would you be kind enough to check your logs for errors starting with -140xx? If you find any, please do be kind enough to post them here. Or, if you wish, you can send your log to support@universal-devices.com . What I suspect is that, for some reason, ISY cannot get to WB. Can you synchronize your time with the NTP server? I am so very sorry for all the problems you are experiencing. With kind regards, Michel

Hi Mike, Thanks for the update. We have to figure out what's causing these anomalies ... I know for a fact that a few devices do not respond to ID Req. But, KPLs, SWLs, and LL/ALs have never had this issue. There must surely be something wrong somewhere. With kind regards, Michel

Hi Richard, I am so very glad that it worked. What you might want to do is to have your router reserve this IP for your ISY. Otherwise, when the router changes the IP, you might lose remote access. With kind regards, Michel

Hello Tim, Some devices do not respond to ID Req which provides the device type. We use ID Req when you add devices by address and I suspect that's where the problem lies. When you add by linking, the device type is returned in the link response and thus we do not issue an ID Req. In any case, I am going to add this to our bug list to make sure it's investigated. As far as your programs, unfortunately that's the case when you replace devices. Fortunately, you can use the Find/Replace function to replace those with the correct ones. With kind regards, Michel

Hi Mike, long time no see! Hope all is well. Are you adding them by address or by link method? If by address, would you be kind enough to try the linking method and let me know what you find? With kind regards, Michel

Hi oberkc, I am so very sorry to hear about your troubles. Would you be kind enough to let me know: 1. What's your PLM firmware (Tools | Diagnostics | PLM Status/Info) 2. How many phases are there in your house? 3. How many Access Points do you have? 4. Are you using any FilterLincs? With kind regards, Michel

Hello Richard, Please note that Y must be capitalized when responding to CT commands. So, y will not work. Please retry and let me know if this fixes the issue. With kind regards,

H Tim, I think this is a good idea but there's a major issue with this: Battery operated devices in general (such as MS) require manual intervention to put them in programming mode and, as such, even if you have a program, you would have to have someone actually put the motion sensor into programming mode before anything can be done. Therefore, unfortunately so, we cannot accommodate this feature. With kind regards, Michel

Hi Tim, Are you talking about the programs? If so, this is a bug as all devices that can have on level/ramp rate should be included in the drop down. With kind regards, Michel

Hi, thanks SO very much. We shall surely give this a try and see how it works out. Again, I want to thank you for your time! With kind regards, Michel A search located this: wiki2PDF http://sourceforge.net/projects/wikipdf WikiPDF is a mediawiki extension based on Wiki2PDF that adds PDF/LaTeX features to mediawiki. Wiki2PDF is a python script to convert multiple articles of a mediawiki based wiki (pre-configured to use with www.wikipedia.org) to a single LaTeX or PDF file. I have not tried this app so I can't speak to it's usefulness.

Hi Frank, To be honest, we are contemplating on moving to a new hosting service due to all the downtime and performance issues that our customers have been experiencing. Till we resolve all those issues, we cannot change anything in our environment. This said, however, we are very interested in a better forum platform. Do you know if vBulletin allows migration from PHPBB? I do not want us to get to a situation where we have two disjoint forums. With kind regards, Michel

Frank, This has been on our list for a while and we just haven't had time to get around to it. We are basically looking for a software or service that converts WiKi to PDF. Does anyone know of such product (hopefully free)? With kind regards, Michel

Hi Frank, There are absolutely no differences whatsoever except the firmware and, on the most recent units, the enclosure has been changed to allow easier access to the SD Card. So, please do not waste your money! With kind regards, Michel

Hi Joe, Do the status of EZX10 buttons change (not within the scene)? Have you used Event Viewer to check what events are being sent. I do not think 2.7.5 will help you since what you are describing is precisely the same issues as all other EZxxx devices for which we have not been able to find a solution yet. With kind regards, Michel

Hi Ken, In all likelihood, you have a defective PLM. To test, please choose any one of your INSTEON devices, Right mouse click and then choose Restore Device. When done, please go to Tools | Diagnostics | Show PLM Links Table and see if you have any links in your PLM. If you don't, then you have a defective PLM. With kind regards, Michel

Hi KenUD, The first thing I would suggest is to: 1. Open Tools | Diagnostics | Event Viewer 2. Change the level to 3 3. Click on any of the buttons on your RL and see if there is any traffic in the Event Viewer If you do see traffic on the Event Viewer, then please copy/paste your program here so that we can check it for problems. If you do not see any traffic in the Event Viewer, it means that ISY is not hearing the signals from your RL the causes of which may include: 1. There's no Access Point that bridges the RL to the PLM (if your RL is too far from your PLM, then you would need two access points) 2. Noise on the line 3. The PLM does not have the slave links for the RL. For this, you can go to Tools | Diagnostics | Show Device Links Table and choose your RL. After you are done, click on the Compare button. If you have any mismatches, then please restore your RL Please do keep us posted. With kind regards, Michel

Hi Illusion, The password cannot be longer than 10 characters. With kind regards, Michel

Hi osullys, Unfortunately we do not use device comm. errors as conditions in programs yet but this is something that we have on our list to implement. With kind regards, Michel

Hello jamesx0, It's correct if you used Or as the conjunctive operator. If you used And, it does depend on which condition is first. With kind regards, Michel

Hi Richard, I suspect that your LL is gone bad. Have you had a power outage/surge? Can you access/control other devices? With kind regards, Michel

Hello Kelly, The only reasons are the support for different modules in ISY-99i: 1. Weatherbug module allows you to use your local weather information in your programs ($49.00) 2. Networking module allows you to ($49.00): a. Use ISY as a web server ... i.e. for use with iPhone web apps b. You can call any network resource (TCP/UDP/HTTP/HTTPS) from your programs Above and beyond the modules, there are no other differences. Warranty is 1 year parts and labor. With kind regards, Michel