Michel Kohanim

robandcathy, There was a small batch of SWL v35s which exhibited the same symptoms as you are describing: intermittent response to scenes, unreliable communications, and basically unpredictable behavior. When it comes to activating a scene, there's really not much that ISY does so I highly doubt that the bug is in 2.7.9. Of course, I would certainly appreciate it if you could go back to 2.7.7 (+ restoring your backup) and let us know if in fact the problems are 2.7.9 related. With kind regards, Michel

Hi AnthemAVM, I seriously doubt 2.7.9 is the problem: when your KPL blinks, it means that it cannot communicate with at least one responder for that button. With kind regards, Michel

Hi Dave, This procedure is only for the following condition: 1. Button A is in the same scene as some other button (say button C) from the SAME KPL 2. You wish to have button A turn OFF when button C (on the SAME KPL) is turned on For all other scenes for which Button A is a responder (and as long as the controller is not on the same KPL) you can do as you would with any other device. I hope this makes sense. With kind regards, Michel

upstatemike, You do not have to change these devices unless: 1. You have intermittent communication problems. Especially, if you have two devices in the same gangbox, one of which is SWL35, and the other is not. SWL 35 responds intermittently while the other one does not 2. Progressive worsening of overall communications amongst all devices If you do not have these issues, I wouldn't worry about it. Again, these problems only affected a small batch and the newer SWLs (even though v35) do not exhibit these issues. AnthemAVM, Please note that this is isolated to SwitchLinc (not KPL) v. 35. So, if you are having issues with your KPL, then I do not think we are talking about the same problem. Now, to figure out the version number, in the Admin Console click on a device, you will see the Address, the Type, and the Version number at top center of the screen. With kind regards, Michel

Hi again, thanks. I think that would be an excellent test. I am not sure why you cannot close your IOLinc but we'll take this one step at a time. First, we have to figure out why your KPLs blink ... once we have that resolved, then we'll figure out what else is going on with the setup. With kind regards, Michel

Hi ryarber, Apologies for not being more specific. The path is embedded in the Device name. i.e. Bedroom / Closet / Ceiling Light ... If you do not have any folders, then there will not be any path information. Just to make sure you are going to see the path information in your topology, please use http://www.universal-devices.com/99i/2.7.9 . With kind regards, Michel

ryarber, Sometimes these devices are in folders and thus you won't seem them under My Lighting. What I recommend is this: 1. Go to Tools | Topology 2. Check the topology for the address of the missing device 3. Check the right column and you will see the path to that device (if any) With kind regards, Michel

rlebel, thanks. I'll take a look at this right after we have 2.7.10 out (this is UI related and I do not want to delay 2.7.10 because of it). With kind regards, Michel

AnthemAVM, And odd question but I would have to ask: how difficult would it be for you to move your IOLinc closer to your KPL and retrying? If you do not see flashing lights, it means there's a problem with communications between the KPL and the IOLinc. With kind regards, Michel

Hi robandcathy, I would have them replaced. With kind regards, Michel

Hi trev, Windows compress/decompress does not work properly. You might want to use AllZip (free) or Winzip instead. With kind regards, Michel

gfridland, The issues are KPL related: 1. Mutual exclusive buttons 2. Buttons from the same KPL in the same scene If you do not have any of these conditions, then everything should be migrated automatically. rlebel, No, because once 2.7.10 migrates 2.7.9 files, it's going to ignore certain bytes and thus restore will not work. With kind regards, Michel

Hi richardl007, Apologies for the inconvenience. Would you be kind enough to let me know: 1. Which firmware version does your ISY have? 2. Do you access your ISY remotely using HTTPS? 3. When the web server stops, can you access ISY locally at home? With kind regards, Michel

Hello wacvmd, If you have communication issues, I do recommend replacing them. In some cases, they would cause communication problems impacting communications with other devices as well. With kind regards, Michel

greg, Yes, this must be quite frustrating ... First of all, let's make sure that we are coming to the right conclusions: I am not sure I understand how we arrived at IOLinc working properly and ISY being the culprit. In short, you linked a dimmer as a controller to your IOLinc and it worked properly. Whereas, in your previous posts, it seems as if you are controlling the IOLinc relay from the Admin Console and not from a controller (or a scene). One more test: What happens if you create a scene, put your dimmer as a controller and the IOLinc RELAY as the responder? Does IOLinc respond properly? Please note that IOLinc will never ever send a status update when it turns off (or on) in momentary mode. With kind regards, Michel

Hello all, Apologies for causing a panic! We put that notice up there to discourage new installations. Please note the following: 1. 2.7.10 will automatically migrate your system from 2.7.8/9 2. The only things you might lose (are not going to be in synch with ISY) are KPL related settings: -- Mutually exclusive button for the same KPL -- Buttons from the same KPL controlling one another 2. If you really want to go back to 2.7.7, you will have to RESTORE the backup from 2.7.7 ... 2.7.7 cannot backward migrate file system With kind regards, Michel

Hi robandcathy, Apologies for a tardy reply (I was sleeping!). Is is possible that this device is a SwitchLinc v35? Hi Nick, There was an issue with the file system which could have contributed to what you are experiencing. This has been fixed ... With kind regards, Michel

Hi greg, This seems to be an issue with the IOLinc itself: if you turn it on and it turns off by itself even though you are not in momentary mode, then there's something really wrong. Can you try: 1. Remove the IOLinc from your ISY 2. Do a factory reset on it 3. Add it back to ISY and check again With kind regards, Michel

Hello robandcathy, I suspect you have some signal/noise issues. Can you query this device? If not, try doing a factory reset on it and then a Restore (right mouse click | Restore Device). If that still fails, then we would have to figure out what's preventing the signal to get to your device. With kind regards, Michel

Hi Nick, We'll have to check into it ... was this the last entry in your log? Please note that log entries are flushed to the file at some intervals so, if possible, check your log again and see if you have another entry for that device now. With kind regards, Michel

Hi evarsanyi, that would be PERFECT! Thanks and with kind regards, Michel

Hi Mark, This error happens when the motion sensor sends a NACK to the PLM. In most cases, when motion in sensed, the motion sensor should send a group command to the PLM + all associated responses. NACK is sent when the MS has problems processing something. Do you get these errors on ALL your motion sensors or only one? If only one, I would do a factory reset on it and retry. If on all, then I would check the location of your Access Points. With kind regards, Michel

Hi Nick, Apologies for the inconvenience. Are you saying that the logs show that the program actually ran but the devices do not respond nor do you get any errors in the log? Please note that you are not going to see comm errors on the Admin Console if a) there was a comm error and the subsequent command was successful. What we need to find out are -2s in the log right after the execution of the programs. With kind regards, Michel

Hi AnthemAVM, The best and least intrusive method is this: 1. If your KPL button is already a controller in a scene, then add the "something" in that scene as a responder and then remove it 2. If your KPL button is NOT already a controller in a scene, make scene, but the KPL button as a controller in the scene, add the "something" as the responder in the scene and then remove both as well as the scene With kind regards, Michel

Hi Carl, I personally do not recommend disabling SSL because your credentials will be in cleartext and thus anyone, by the virtue of knowing your IP address, can turn on/off your devices and change all your programs. Now, if you so choose to use HTTP, all you have to do is to change the port forwarding port from 443 to 80. And, from then on, you can use http://your.external.ip.address . With kind regards, Michel