Michel Kohanim

Hi Vince, is this RL or RL2? Do you see the status of RL change in the Admin Console when you press the button? With kind regards, Michel

Hi Vince, Did you follow the instructions below to link your MorningLinc to ISY? http://www.universal-devices.com/mwiki/ ... orningLinc With kind regards, Michel

Hello binaryman, 2.8.x does not support 2048 bits and thus the reason to upgrade to the most stable beta (3.1.16). Would you please try creating a certificate using http://www.cacert.org/ (free certificate)? With kind regards, Michel

Hi binaryman, What's the key strength? And, do you still have the text version of the certificate that was sent back from the CA? If key strength is 1. Go to https://www.universal-devices.com/ssl/insteon 2. Login 3. Go to SSL Certificate Management | Receive Certificate from CA and Install With kind regards, Michel

Hi Rick, Unfortunately not that I am aware of but this should be something we add in our Wiki. In short, those that look like squares are controller devices. Those that are light bulbs, responders only. The rest should be based on the type of device. With kind regards, Michel

Hi OmegaQuest, Unfortunately we do not have any such plans because REST was designed as a programming tool (so you would put the userid/password in the proper HTTP hearders). dennisric, We should have it released shortly. With kind regards, Michel

Hello OmegaQuest, Text should work as well but have not tested it thoroughly. Status issues are usually firewall related: your computer's firewall is blocking ISY from publishing events to the Admin Console. In the best case, all you would have to do is to put ISY in the trusted zone white list or exclude from checking. In the worst case, you have Avast or Kaspersky in which case you have to do a lot more things to get it to work. In most cases, though, if you use HTTPS instead of HTTP, then the firewall lets it go through thinking security is done at the certificate level. With kind regards, Michel

Hi Todd, Thanks so very much! My only question is why do you have the following: In Scene 'Motion Responses / Hall After Motion' Set 'Dimmer - Hallway' 30% (On Level) If your intended goal is to have a different on level/ramp rate when the motion sensor is tripped, then all you need is: In Scene 'Motion - Hall - Sensor' Set 'Dimmer - Hallway' 30% (On Level) The only reason you would want to use the first one is if this scene is activated by an ISY client such as Admin Console or a mobile app. And, even so, you can always do this after everything is already programmed for the motion sensor (doesn't have to be done before). I know this is not going to make it much faster but it removes at least one set of commands. With kind regards, Michel

Hi Bruce, Thank you and now I understand. Unfortunately I do not know of any other way. Questions: 1. What's the timeout for this resource? Do you know approximately how long this command should take (when repeating the IR signal 6 times)? 2. Have you tried opening the Event Viewer on "Device communications events" level and see whether or not some IR signals are bounced back to ISY (that is if you have the IR version) 3. Also, is it possible to run this resource from another program and just copy/paste the output? If not, does the API define what should be returned? With kind regards, Michel

Hello thedishking, Yes, please and please do let me know: 1. Whether or not you have ELK and/or ELK Module 2. Whether or not you are using network resources 3. Whether or not your programs continued to execute 4. Whether or not you have any information on how to reproduce Hello k7zpj, thanks so very much. During reboot (right before Start) UDQFull:LOG is completely normal. You really do not need ddwrt or anything else. All you need is Wireshark and capture the traffic between ISY and IPTOIR when the network resource is activated. I am so very sorry that you have to do this but it would help us tremendously. With kind regards, Michel

Hello Toddimus, Thank you. I really need to figure out which is the issue: 1. Slow when adjusting scene on level OR 2. Slow when you use programs to activate the hallway switch OR 3. Both As LeeG mentioned, #2 should be pretty quick. I want to figure out if that's not the case in your situation and what might be contributing to it. With kind regards, Michel

Hi Todd, Kind of! So, you have two dimmer switches and, currently (using programs), are you turning them on/off discreetly or are they in a scene and you just send a scene command? There are major performance implications if you use the former including at least 500 m.s. delay between each command. Also, can you tell me: 1. What is your ISY's firmware version? 2. How many programs/devices do you have? With kind regards, Michel

Hello OmegaQuest, Figured out how to add a display name to email address. In 3.1.17 (to be out shortly), all you need to do is to use: name1 name2:email_address in the From field. ISY will automatically parse and send name1 and name2 as display name. Please note that most SMTP servers require name1 name2 separated by a space. Hi Bruce, thank you. Since I do not have an IPTOIR, my tests did not crash the unit. Would you be kind enough to unplug your IPTOIR unit from the network, run the test, and let me know if the unit still crashes. If not, then we will have to use a packet sniffer to see what IPTOIR is returning (in those cases) that ISY does not like. With kind regards, Michel

Hello OmegaQuest, We do not have any plans to support nested Ifs. Hello morgan4x4, Can you do me a huge favor? Can you add a notification email right before the last net resource activation? If you get the email but the net resource is not activated, then you might be on to something. If not, then we have to figure out what breaks the last wait and what other programs you have that might be activating that resource. Log full right prior to Start is completely normal. If you have other errors, please post them here. With kind regards, Michel

Hello OmegaQuest, We the @ sign requirement is from the SMTP server. In short, if you do not have a valid from, the server just uses the account. I am really not sure what to suggest above and beyond taking a closer look. With kind regards, Michel

Hello stillen_i30, Please do contact our support team (links below) and we'll schedule a call to help you out. With kind regards, Michel

Hi Todd, Thank you. Can you tell me how slow the delay is? Are you simply looking for Control for the Motion Sensor and then activate a scene (or is it a device and/or multiple devices)? With kind regards, Michel

Hello morgan4x4, As we have noted in the instructions, the way in which we handle network resources has changed and thus, now, they run in a separate thread. The only thing that the program does is to queue the activation requests. So: This basically means only two things (though it's rather unlikely that the delay would actually be 30 seconds): 1. The previous network resource activation had a timeout of more than 30 seconds and it actually took 30 seconds to complete 2. The program itself turned to false and then back to true (while waiting) and everything restarted from scratch 3. ISY is busy doing things with much higher priorities (unlikely) So, my recommendations are: If you really have to use a wait command, ensure that the condition does NOT turn to false while waiting. You can do this by putting those that require a wait in a separate program. i.e. Program 2, has NO conditions: Resource 'Basement LED Yellow' Resource 'Home Theater Receiver Power On' Set Scene 'IR TV Power On' Wait 1 Second Resource 'Directv Home Theater On' wait 6 seconds Resource 'Home Theater Receiver Volume -26DB' Resource 'Home Theater Receiver HDMI 2' Wait 30 Seconds Set Scene 'AV rack LED Off' Wait 1 Second Set Scene 'Home Theater Nook LED Off' Resource 'All LED Ambience' This will ensure that this program will always run to its completion. This said, the first thing we have to do is to make sure that your condition does NOT turn false. Also, if you long timeouts in Network resources, you need to make them shorter. With kind regards, Michel

Hi Bruce, Thank you. Does this crash the unit all the time and is reproducible? With kind regards, Michel Hi Michel, That is correct. I am sending one command from the ISY-99i to the IPTOIR to have it repeat the the IR signal 6 times. Regards, Bruce

Hi Todd, Thanks so very much for the feedback. First of all - and as you noted - the fact that the motion sensor has to be in programming mode (or listen mode) before we make any changes is quite daunting. As a matter of fact, we did try this a few times and the success rate was not that high. Furthermore, it seems that HouseLinc has the same type of issues with this approach. The best case is that we can program the motion sensor. The worst case is that we cannot and now your system is left in a zombie state till we retry again. And, then, we have to define number of retries before failing and finally the interval between retries. All and all, if the solution was as easy (or supportable) as changing the scene level (which you already do), then it would have already been implemented. I am so very sorry to disappoint but I am afraid that this solution will cause more damage than good especially since: 1. It has to run a few times a day 2. It's RF 3. The RF device has to be in listen mode With kind regards, Michel

Hello OmegaQuest, I tested this with multiple SMTP servers and, unfortunately, even with , From field is replaced with the account email address unless the SMTP server is configured with the From. We can do further testing to see if there's anything we can do to change this. With kind regards, Michel

Hello Bruce, That's not good. So, in short, you are sending ONLY one command which repeats the IR signal 6 times on its own, correct? With kind regards, Michel

Hello OmegaQuest, If you use the default SMTP settings, then no. Otherwise, it all depends on your SMTP server. Most SMTP servers out there use the Account information and either ignore the From field OR if you put something other than the Account (email), they will reject the message. With kind regards, Michel

Hi jtara92101, I am not sure which documents you were looking at so please do let us know so that we can update. Our latest WSDK does have everything you need to know about REST with optional parameters to show folders recursively or not. That's how ISY AJAX works and thus it must have been documented somewhere. Just need to figure out what you were looking at. Thanks and with kind regards, Michel

Hi Tim, I do think the length has something to do with it. If you have another switch/router, you might want to put the switch/router in the garage and the hookup ISY to it. I suspect you are getting a lot of collisions because of the length. With kind regards, Michel