Michel Kohanim

Hi Oktane, I am so very sorry to hear about this. I wouldn't worry about upgrading/updating issues since ISY is in the safe mode: we have to fix the PLM issue first. Most of the time, the problem with the PLM is that the cable does not make contact with the pins inside the PLM. So, what I suggest are the following: 1. Change the cable that connects ISY to the PLM 2. If 1 does not work, use a sharp object and pull up the pins on the PLM's RJ45 jack 3. If 2 does not work, then you will surely need a new PLM With kind regards, Michel

Hi Jim, Thanks so very much. Please do keep us posted. With kind regards, Michel

Hi Jim, Just to test your scenario, I tried reproducing this problem with ISY firmware 2.7.5 and it worked fine. What ISY firmware are you using so that at the least we have the correct baseline? With kind regards, Michel

Hi pdxcav, I do apologize, I didn't know that you already have a static IP address for your ISY. So, now, I must submit to you that ISY does NOT do anything with your router as long as its IP address does not change. So, are you certain that your router does NOT reboot? UPnP port forwarding does not survive router restarts. Would you be kind enough to: 1. Disable internet access on ISY 2. Create a manual port forwarding rule in your router (http://www.portforward.com) 3. Test it for a few days and let me know if you still have any problems With kind regards, Michel

Hi Bernhard, Long time no see! Unfortunately not yet but it shall be added in 2.7.6 (next release). With kind regards, Michel

Hi Joe, This is QUITE strange. Please do be kind enough to keep an eye on it and let me know if it happens again (as soon as possible). With kind regards, Michel

Hello Jim, I do not think this has anything to do with your WB module but, based on the event viewer, it seems that your MS went out of programming mode (does not hear INSTEON traffic anymore). Usually all Radio devices have a 4 minute programming mode timeout. It seems that your MS timed out and that's why it didn't respond to ISY's 3 retries. With kind regards, Michel

Hi MSM, I do apologize for the inconvenience. Please do keep us posted. With kind regards, Michel

Hi Eug, Can you check the log and let me know if you see any -6000x ? With kind regards, Michel

Hello pdxcav, Apologies for the inconvenience. I think the problem is that your router is assigning a new IP address to ISY (DHCP). When this happens, ISY has to disable the old port forwarding rules and create a new one. Sometimes, this does not work depending on the router. As such, it's always best to assign a static IP address to ISY: http://www.universal-devices.com/mwiki/ ... IP_Address Furthermore, I strongly recommend getting a free dynamic dns account for your home network. With kind regards, Michel

Hi Joe, You didn't reboot ISY in the process? If so, this is quite odd. The ERR light indicates that there is a file system error. ISY has a file system which is maintained by the framework. If the framework cannot access the file system, then the ERR light keeps blinking. On the other hand, if ISY cannot get a DHCP lease or if it cannot join the local area network, then ERR and MEM blink. That's why it's really odd that it started working by just unplugging and plugging back in the network cable. Please let me know what version of ISY firmware you are running. Thanks and with kind regards, Michel

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.