Michel Kohanim

Hi Guys, If you put MorningLinc in a scene as responder, upon scene activation, one locks and the other one unlocks. With kind regards, Michel

Hi Tim, Yes, it's fixed and it's installed on all shipping PLMs. If you are having major issues with your PLM (especially if you have records with 0000 in them), please do send me an email. With kind regards, Michel

Hi Pete, I am so very sorry to hear. There seems to be two issues here: 1. It seems that status updates are not sent from ISY to your computer. Perhaps after the upgrade, your ISY's IP address changed and your firewall rules are now blocking ISY ... this has to be fixed before we try to figure out what's going on with your IRLinc 2. Please go to Help | About and ensure that UI Version is the same as Firmware version. If not, please clear your Java cache and go to http://www.universal-devices.com/99i/3.1.15/admin.jnlp With kind regards, Michel

Hello connorrc, The ISY Finder has always been there. The function for ISY Finder is: 1. It lets you have an icon on your desktop and add as may ISYs that are NOT local to you to the list 2. It relieves you from having to download the applet from ISY when you are remote Not having correct status points only to two things: 1. There's a mismatch between the UI and the firmware. Please go to Help | About and make sure your UI version (it must exist) is equal to the Firmware version. If they are not, clear your Java cache and go to http://your.isy.ip/admin 2. You recently upgraded, changed, or reconfigured your firewall especially if it's AVAST or Kaspersky I do not have much experience with X10 so I will leave it to others in the community to respond. This said, from my experience, when INSTEON works, it works till something breaks such as a power supply becoming noisy, the device failing, etc. With kind regards, Michel

Hello Elvis, I am so very sorry to hear. Is this problem reproducible and does it happen all the time? Are the times correct especially the one that happened right at midnight? With kind regards, Michel

Hello boatfevor, %20 is the URL encoded version for white space. So, let's say the node address is: 17 F7 C0 1 (you get this address in the tag in /rest/nodes) So, the encoded URL would be: http://your.isy.ip.address/rest/nodes/1 ... 01/cmd/DON As you note, each white space has been replaced with %20. With kind regards, Michel

Hello connorrc, This is normal behavior for the application version. If you don't like to use the application version, you can use the Applet version (which requires your browser to be on): http://your.isy.ip.address/admin OR http://www.universal-devices.com/99i/ With kind regards, Michel

Hi Robert, Thank you. I do not think moving the motion higher is going to help. I would try to eliminate variables. For instance, the first thing I would do is to disable the program that calls this program. Secondly, I would create the same exact program but instead with state variables. And, in the Then, instead of running thing, I would send notification. This way, we would know the status of each program and all the events associated with it. Again, this new program is the duplicate of the original so that both can run at the same time with two differences: state variable instead of integer and notifications instead of turning things on/off. With kind regards, Michel

Hello tim2u, This will require forecast information from WeatherBug which is not always available for all stations. I am worried that if we add this and if the information is not available (or spotty), then we are going to have many unhappy customers. With kind regards, Michel

Hi JMC, Locate Me is based on the location that your ISP reports for your location. It may not be as accurate as using the Zip Code. So, please use Zip Code instead of Locate Me. If you are not getting any status updates from WeatherBug, the main question is whether or not you get any status updates from any of your devices. Also, you may want to: 1. decrease the polling interval to 10 seconds 2. open up the Event Viewer on Device Communications 3. check and see if there are any weatherbug releated events/errors Once done, please change the interval back to 60 seconds or more. With kind regards, Michel

Hello neupane00, I understand how frustrating this could be and, as such, if you are still having issues, please do let us know so that we can help you remotely. You can even schedule a call for a time most convenient for you. With kind regards, Michel

Hi Robert, Are you certain that: AlarmState = 0 Bedroom_Chill = 0 Also, you mentioned that you call this program. Is it called from another program? The main issue we have is that we cannot reproduce this behavior and need as much information as possible. I understand that it's quite intermittent and it may not happen all the time but the more information we have, the more the likelihood that we can perhaps figure out what's going on. With kind regards, Michel

Hello neupane00, I do apologize for the inconvenience. This is not normal and it all points to the firewall software on your computer especially if it's one of AVAST, Kaspersky, NOD32, McAfee, and AVG. These solutions are notorious in blocking ISY communications with your computer and, at the minimum, require ISY to be in the trusted zone/white list therein. Please do be kind enough to search for your specific firewall software or do a quick browse for resolutions to most in the following forum: viewforum.php?f=3 If you are still having the same problems, please do not hesitate to contact our tech support team and we'll be delighted to help figure out the root cause and fix it. With kind regards, Michel

Hi Robert, Is the variable State or Integer? If integer, then the condition is not re-evaluated when the state of the variable changes. With kind regards, Michel

Hi Robert, Thank you. You had mentioned that when you move this program to the root folder, it starts working. So, I do not think the problem is the var but the condition on the folder. Can you please create another folder (without any conditions), move this program there, and see if it works? With kind regards, Michel

Hello lspurgeon, The first thing I recommend is to use the Event Viewer on the last level and make sure you do get status events from your RL. The second question I have is whether or not any segments (separated by Wait) or is it that none of the segments run? With kind regards, Michel

Hello suttonnc, The want to connect directly with a wire (and not through their Local Area Network)? If they already have a network at home (which seems so since ISY is currently on it) and if their MAC is on the same network, then all they need to do is to go to: http://www.universal-devices.com/99i//admin.jnlp ... this will install an icon on their desktop to use. So, for instance, if ISY's firmware is 3.1.15, they would go to http://www.universal-devices.com/99i/3.1.15/admin.jnlp . With kind regards, Michel

Hi Robert, There are no conditions on the parent folder at all? With kind regards, Michel

Hi midrar, Do you mean just program/folder structure or do you mean the content of each program as well? With kind regards, Michel

Hi Wuench, Sincere apologies for tardy reply. First of all, I must tell you that, yes, our user experience will benefit from more feedback. Secondly - and based on what you have described - I think the problems are much larger than the dual band PLM not being as good as the old one. I really think you have major RF interference which could be caused by any of the following: 1. SwitchLinc v35 ... if you have any of these, you have to replace them. Sorry, but this is a MUST 2. Baby monitors which use frequencies is 800 to 900 MHz ... this could kill INSTEON RF 3. Older version Thermostat dongles ... if you do not have 2.2 or above, they have to be replaced (yet another MUST) 4. A defective PLM I know you have already had a hell of time and that you do not want to touch the unit but I am afraid you are in for a major problems in the future especially since you used Device Reported. This may seem to work from ISY perspective, but this does not mean that the devices actually did write the correct links. As a matter of fact, that's why default is Automatic since, in most cases, Device Reported has major side effects that you might not notice now but they will show up randomly. If you can rule out #s 1, 2, and 3 above, please do send me an email (support@universal-devices.com) as soon as possible to resolve #4. Please do not order a replacement PLM from SmartHome before contacting me. I am so very sorry for all the trouble you have been going through. With kind regards, Michel

Hello als223, Thanks so very much for the update! With kind regards, Michel

Hi matapan, I am a little concerned with what you are trying to accomplish. Please do be kind enough to pay heed to the WARNING on the top of the dialog. This dialog is kept there only for backward compatibility and using it is NOT recommended (you should use scenes instead). Furthermore, in the same Warning, you will note the difference: setting up button grouping with the dialog prevents ISY from being able to predict the status. Yes, WiKi is not updated and it's inexcusable ... this said, I think the big red WARNING sign on the dialog should be sufficient to explain what course of action should be taken. With kind regards, Michel

Hi Tom, Thank you but I have to warn you that Java 1.7 is full of bugs so much so that we had to revert to 1.6.29. And, yes, we had all sorts of issues with icons and menus. ISY Finder is designed that way. With kind regards, Michel

Hello Wuench, Have you tried Event Viewer? I am certain Event Viewer will tell you everything you need to know especially if you use the last level. As far as 3 busy dialogs, I will have to consider this a bug since, from code perspective, this must be an impossibility since the dialog is a singleton (you can only have one instance). It would be great if the next time it happens, you can tell us the procedures to reproduce. As far as all the problems you are having, you must note that changing the PLM means changing the links to the PLM in all devices. Even though ISY is extremely good at queuing things such that there's no interference with anything else, in some cases it's best to disable all your programs before restoring PLM or all devices. I have to emphasize that the ISY will continue to work even in conditions where you have 100s of programs running BUT for cases where you do not know why you have comm errors, it's easier to remove one variable. Once that's done: 1. Disable all nodes with green 1011 icons 2. Query all nodes with ! .. if it succeeds, right mouse click | Restore Device. If not, disable it At this point, you have a list of disabled devices. What you will have to do is for each, right mouse click | Write updates to device (keeping the Event Viewer open). If it fails, we will have to figure out why. With kind regards, Michel

apostolakisl/LeeG, I think it would be safe to say: a. The way we have handled cleanups and ACKs has NOT changed for as far back as 2.8.16 b. The way we currently handle cleanups "may" cause all the problems apostolakisl is experiencing As such, I recommend waiting for our next release so that we can have a better understanding of where the actual problems may be. With kind regards, Michel