Michel Kohanim

Hello jmayzurk, I would appreciate all the pointers and help you can give us to isolate/fix this problem. Thanks so very much! With kind regards, Michel

Hi Wayne, I think there's surely something wrong with the configuration file for this device. It might be corrupted, backed up corrupted, and the upgrade simply tries to recover from a corruption. If this does not happen without an upgrade, then what I suggest is to just leave it as is for now. Before the next upgrade - and although painful - I recommend removing this device from ISY completely and starting from scratch. With kind regards, Michel

Hello Dale, Unfortunately not since RL is a controller only device and the status of the buttons can only be changed by physical interaction with the RL itself. With kind regards, Michel

Hi Wayne, Does this happen every time you do an upgrade (or, let's say the majority of time)? With kind regards, Michel

Hello douglasking, Please try the following (Adding ISY to the trusted list): 1. Open Kaspersky 2. Click on Settings 3. Click on Threats and Exclusions on the left 4. Click on the second Settings... button on the right 5. Click on the Trusted applications tab 6. Click on + Add, then go to Applications and select your program 7. Check check : Do not scan network traffic 8. Click OK three times. With kind regards, Michel

Hello ergodic, Thanks so very much for the update. The problem is hardware related and not firmware. I also want to thank you for your great write up on If/Then/Else programming. It's an excellent reference and, if you do not mind, we would like to put a link to it in our Wiki. Thanks again and with kind regards, Michel

Hi Wayne, I must agree with you ... the only problem is that if we cannot reproduce it we cannot fix it. In any case, I have now put this on our bug list to make sure it's going to be looked at more thoroughly. In the meantime, if you can think of anything that you may have done prior to this issue, it would greatly help us in debugging. With kind regards, Michel

Hello douglasking, The two symptoms (invalid length and not seeing the status) are quite related and point to your firewall software. Have you changed your firewall (or its settings lately)? What firewall software do you have? With kind regards, Michel

Hello ergodic, My pleasure. Yes, the relays have the same firmware and thus may exhibit the same problem in the future. As far as the issue being ISY/PLM related, suffice it to say that if it were an ISY/PLM problem, then a) why would you have the same problems if you unplugged ISY/PLM? and knowing SH's replacement policies, why would they replace devices if the problem was with third party software/hardware? Simply put: we are used to being blamed for all SH and SHN product ills! With kind regards, Michel

Hello ergodic, Unfortunately what you're describing are classic symptoms of V35 dimmer(s). It might be just one of them causing all the trouble or it could be a few. The problem is that you would not know which one unless you take one offline (one at a time), test for a few days, and then move on to the next one. At this point - and although quite painful - I do suggest replacing your SWL v35s. With kind regards, Michel

Hi oberkc, You are right on (operator precedence) ... thanks so very much. Curt, welcome aboard!!! With kind regards, Michel

Hello steckbeck, If you have ISY99i PRO series, then you can do everything in batch mode before applying the changes (except the initial registration). To answer your questions: 1. NO ... it is not normal. The Admin Console does not bring up the progress bar UNLESS it knows that the process is going to take longer than 2 minutes 2. I do think you have major communications issues. Please use Tools | Diagnostics | Event Viewer (on level 3), make some changes and observe the traffic. If you see many INST-ACK not followed by INST-SRX, then it means that ISY keeps trying to communicate with your device but it cannot. In short, for every INST-ACK there should be an INST-SRX. With kind regards, Michel

Hi Chuck, I think it's now time for getting in contact with our tech support team. Personally, I can only think of two things causing this issue: 1. A defective PLM 2. Some device on your network started going bad and is causing all sorts of network traffic/noise and thus all the comm errors Does your PLM blink continuously on its own even though there should not be any traffic? With kind regards, Michel

Hi wwat, By missing I assume you mean that nothing shows in the Viewer, correct? The best thing to do would be to try and restore you last good backup before the upgrade to see if they reappear. With kind regards, Michel

Hi Jim, The easiest way is to make the sensor also a controller in the same scene. In short, both are controllers in the same scene. Yes, right mouse click and then choose Copy to clipboard. With kind regards, Michel

Hello Steve, Please do a Find in your programs and look for anything that references this program. I think you have another program that does the enable/disabling ... With kind regards, Michel

Hello rudyramirez, Is there any difference in the load type for these devices. Specifically, for the one that fails the scene test. The problems are really limited. We just have to figure out which one is the cause: 1. Noise ... 2. Signal strength ... 3. Defective switch ... Would it be possible to swap (location/load wise) the non-responding SWL with a functioning SWL? In this case, if the problem moves with the Switch, then the Switch is probably defective. Otherwise, there's something wrong with the load or wiring. With kind regards, Michel

Hello Bill, oberkc got it right! In short, every time there's a change in the state of any device to which the condition depends on, then program is re-evaluated and if true, the Then part will run. With kind regards, Michel

Hello rudyramirez, I can answer your question: scene commands are different than direct commands (point to point). A scene command is send once and all the devices participating in the scene should respond. Also, when they respond, they have to send a packet back to the PLM. You mentioned that both of your SWLs are v37, correct? Are you certain you do NOT have any v35 SWLs in your system? With kind regards, Michel

Hello ergodic, What is the nature of the problem you are experiencing? Is it that ISY does not hear the events OR that devices that are programmed to respond to the MS do not respond reliably? With kind regards, Michel

Hi ergodic, I would not worry about this message if the previous message states "duplicate". In short, all RF devices send the same message more than once. ISY filters out those that are duplicates. Reliability issues with Motion Sensors are usually related to the Access Points or the battery. With kind regards, Michel

Hello rudyramirez, That's the crux of the issue! For some reason the signal is not getting from the PLM to your switches. If you have any Access Points, my I humbly suggest plugging one right on top of the PLM? With kind regards, Michel

Hi again, thank you. Would you be kind enough to go to Tools | Diagnostics | Scene Test, choose your scene from the list, and then let me know if it succeeds. If it does not, then there is a signal strength/noise issue between your PLM and your switches. With kind regards, Michel

Hello rudyramirez, Can these device control one another? When you click on the scene icon itself (the round looking icon), what are the on levels for each of these switches? With kind regards, Michel

Hi Simon, With releases 2.7.10 and above, ISY actively tries to synch what it knows about your system with what the system has. This means that "any" update to any device will cause ISY to re-evaluate and make sure your system is in fact in synch and write updates to devices that are out of synch. I assume you have 99i PRO since you mentioned batch button. Right next to the batch button, there's the RF devices button. If you do not want ISY to keep trying to update your RF devices, please make sure that button is grayed out. Furthermore, you will get a "Writing->" icon next to devices that are being updated. Ultimately, though, you do need to figure out why those devices are out of synch and why ISY does not succeed in updating them. With kind regards, Michel