Michel Kohanim

Hi fuzzersteve, I do not think the switch can go bad so quickly. I think you may have communication/noise issues. Do you know what type of load is connected to the switch that failed? Is it possible to switch the loads between the two switches? This way, if the problem moves to the good switch, then we know that the problem is load related. Otherwise, it could be the switch. With kind regards, Michel

Hello, 140000 means DNS error and it usually happens when your ISP is down or the DNS server is not accessible. With kind regards, Michel

Hi Jacques, Unfortunately, you cannot have other controllers in the same scene since sub buttons can only follow controllers. As such, you will have to revert using the button groupings. With kind regards, Michel

Hello nedsmith, Please do be kind enough to peruse the following document: http://www.universal-devices.com/mwiki/ ... Thermostat If it still does not work, you would have to make sure you have Access Points in the vicinity of your thermostats to make sure you have RF coverage. With kind regards, Michel

Hi mitch236, Yes, it does .... With kind regards, Michel

Hello all, Apologies for the inconvenience. There was a difference in the plug (2.0 mm vs. 2.1 mm) between 26 and one of the batches of 99i. If your power supply does not fit, please send an email to sales@universal-devices.com and we'll send you an adapter free of charge (using USPS). With kind regards, Michel

Hi Jeff, If you do not mind testing a build, please do send an email to tech@universal-devices.com ... it would be great to have more than one instance being tested. With kind regards, Michel

Hi kingwr, Three ways: 1. Click on the rename menu and you will see the address 2. Topology 3. http://your.isy.ip.address/rest/nodes With kind regards, Michel

Hello sk8er02, Thanks ... based on your logs, it's a guarantee that everything starts when ISY cannot contact WeatherBug and from thereon things get successively worse. I am going to add more constraints to the module infrastructure and, if you don't mind, let you try a different build. If amenable, please send me an email to tech@universal-devices.com . With kind regards, Michel

Mr. Allen, First off, when you replace the battery you MUST do a query on the low bat node to have ISY reset that status. You can use either status or control since when the low bat signal is sent, it does NOT change till you change the battery and query the low bat node. With kind regards, Michel

Hello Mr. Allen, Long time no see. All you have to look for is the name of the node associated with your Motion Sensor Low Battery and status of 100%. If you use Excel, you can simply filter everything out by name. With kind regards, Michel

Hi Robert, Currently, there are only two ways: 1. Send an X10 code from the one linked to the switch and have a program in the others to sense that signal and do an all off 2. Use network resources to do the same ... for this, you have to make sure your ISYs have static IP addresses: a. the master ISY should have network module b. in the program for the master ISY, create a resource to: http://your.isy1.ip.address/nodes/[the all off scene address]/cmd/DFOF http://your.isy2.ip.address/nodes/[the all off scene address]/cmd/DFOF c. In the resource, you want to make sure you use HTTP, GET, and add an Authorization header with the userid/pwd of each The first one is much simpler but X10 signals may get lost in the presence of all the traffic. With kind regards, Michel

Hello sk8er02, Thanks so very much for the update. Apart from Internet connection issues, do you have LAN connection issues? All the errors you posted are related to ISY not being able to either write to an outbound connection (to the Internet) or read from it. i.e. does the system still hang? With kind regards, Michel

Hi tome, Are you saying that even the LED does is not synched with the status of your sensor? With kind regards, Michel

Hello LarryC1116, First of all, apologies for the inconvenience. You should not have to do anything! We do use quality SD Cards and they should last years. The only thing I recommend is to make sure you have release 2.7.15 installed since we added CRC error detection which should help with errors communicating with the SD Card. If you are using your own SD Card, please do ensure that you use a new one and a good brand. With kind regards, Michel

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