Michel Kohanim

az1324, Consider it done! With kind regards, Michel

Hi Clark, Thanks and please do keep us posted. Also, you might want to try the DBG command (in the shell) and look at your Java console to see where it fails. With kind regards, Michel Yes, it still failed. I just tried the query from My Lighting and had no problems. And my laundry room program ran fine this morning. I tried it when I got home as well, and it worked then too. Yes, I have a long Ethernet cable. I will move the ISY and PLM to the outlet below my keypadlinc and see how it works. Presently they are only 20ft apart. Not saying that it is on the same phase, or it will be when I move it either. I have an access point in between them as well, by the way the crow flies.

Hello 1001001 (73?), I do apologize for the inconvenience. Would you be kind enough to retry the same link again (download)? With kind regards, Michel

Hello Clark, You are 100% correct: if a device is already at a level, the log does not show that the device was activated again. Do you still get Request Failed on your KPL Relay. We've had some problems with KPL Relays before but all isolated to Mutex/Toggle modes. Is it possible to move your KPL closer to your PLM and see whether or not you have the same issue? With kind regards, Michel

Chuck, That's true. Run simply runs the Then part. With kind regards, Michel

Hi, Unfortunately, not at the moment. With kind regards, Michel

az1324, If you are 100% sure that this has no effect on other browsers, we can immediately add it. With kind regards, Michel

Hello again, This is quite strange indeed. The log shows that the Scene was triggered by a program but the only program that activates that scene is based on a Fast On which is nowhere to be found in the log (in that time period). So, either the scene was triggered by the same program and the log is inaccurate or the program is run by itself. Either case is quite disturbing! As far as request failed, please do a query on your Network (top most node in the tree) and see if you get any device communication errors. In all likelihood, ISY cannot communicate with your device either because of noise or a defective PLM. With kind regards, Michel

Hello d_l, You can use the timers in EZRain but the only problem is that ISY does NOT hear EZRain's change of state and thus your ISY status will not be in synch with the actual EZRain. Of course, the Query at 3:00 AM will make them in synch again. In short, if you don't care whether or not ISY/EZRain states are in synch, and if you don't have any other conflicting programs, then you should be OK. With kind regards, Michel

CompKing, You do NOT need to open port 80 on your router to access ISY locally on the LAN. All you need is to figure out what's your ISY's local LAN IP address. So, please do not open the port 80 on your router. With kind regards, Michel

clark21236, ISY does not show Fast On/Fast Off in the log. It just shows the status of the device. From what I see in your log (see below), ISY did not sense the Fast On; it only sensed On at 5:53 AM and thus the scene was not triggered. Actually the scene is not triggered at all till 6:16 AM. So, do you have any other programs that activate this scene? With kind regards, Michel

Digger, Furthermore, may I humbly suggest unplugging ELK before ISY/PLM? It might be the ELK. With kind regards, Michel If it's a single scene you're executing with the ISY, where would you add the pause? Sounds like it's caught in some sort of loop. Do you have a program somewhere that triggers this scene?

Hello RLIKWARTZ, We just got confirmation from SmartLabs that there are no broadcast/multicast messages that INSTEON devices send out based on Load Sensing. Furthermore, this is not part of the specification [yet]. As such, what you are doing is [and shall be for the foreseeable future] the solution. With kind regards, Michel

brobin, Thanks for the feedback. We actually did some experimentation with this and decided against it simply because we do NOT know how a specific device (say a relay) behaves when we restore the links for dimmer into it. Theoretically, they should work but we found some anomalies which made us hesitate doing so (the code is already there, we just removed the mapping which shows which devices are compatible with what other devices). With kind regards, Michel

Hello greensha, I am not sure but I can tell you from experience that they are superior to SignaLincs (some of which are actually the sources of some of the problems). With kind regards, Michel

Hi Drew, Yes. To quote, simply use the Quote button when replying to posts. With kind regards, Michel

Hello Andy, You might also want to consider changing your SignaLincs to AccessPoints. Please keep us posted. With kind regards, Michel

Hello Andy, In either case (using Sunset or From/To), the success of the Action (i.e. turn scene on/off) has no impact on the evaluation and execution of the condition. If you have scene and devices within scene which do not respond to ISY (intermittenly), then the best bet would be to FIND OUT WHY! We've seen so many different solutionts that address the symptoms (such as repeating a command n times) but at the end of the day, they will eventually fail at least once and cause other problems (such as network congestion). Is there a pattern to your comm errors? With kind regards, Michel

IndyMike, If you have a new PLM, then I wouldn't worry about it. That's all that matters. 2.6.4 should be out shortly and we should be able to solve this mystery soon! With kind regards, Michel

Hello Drew, Yes, precisely. If you have an RL in the same scene, your Mutex buttons will NOT work (or behave the way you want them to). I am so very glad you are starting to have fun! ISY stands for Intelligent System. With kind regards, Michel

Mark, thank you so very much. With kind regards, Michel

Hi IndyMike, The Replace function in 2.6.0 and above on occasion changes the device type and as such I do not recommend it (unless you feel brave!). If you do not mind waiting, we should have 2.6.4 shortly. You got it: if the replace on a new switch creates the same behavior, then it's ISY otherwise it's the SWL. Other questions: 1. How old is your PLM? If older than 6 months, please take a look at your http://your.isy.ip.address/WEB/NODESCNF.XML and see if you find any groups with the element having any value below 20. If so, it might also be the PLM. With kind regards, Michel

Drew, Yes. But you have to be very careful if you have other controllers in the same scene that control B and C: Mutex Groups/Buttons work at a local level only so if you have other controllers in the scene that can turn on/off B and C then Mutex will be ineffective. With kind regards, Michel

RLIKWARTZ, Yes, you can use ISY programming to query this device continuously: If - no conditions Then Repeat Every 1 minute Set Your_receptacle Query But, this should not be the ultimate solution. We are working with SL to see how we can sense the load state changes. With kind regards, Michel

Hello IndyMike, I am so very sorry to hear that you are having these problems. The one thing that makes this rather difficult is that you have done any permutation of factory reset and restore none of which worked. On the one hand, I could've immediately declared that ISY has a corrupt configuration file for your device but, on the other hand, you have already restored it from a previous backup. It's very possible that ISY always had a corrupted configuration file for this device but this cannot be proven till we swap this device with another (you would need 2.6.4) using the Replace function. With kind regards, Michel