Michel Kohanim

Hi Moshe, Two questions: 1. Locally, you are not using the HTTPS port. Please note that there are two ports in ISY: one is HTTP and the other HTTPS. Please ensure that you use the HTTPS port and that you are accessing your isy using https://your.dyndns.url 2. In your router configuration for port forwarding, there are two ports: one is public (from outside) and one is private (your ISY's port number). As such, there will be a mapping from the public to private. Make sure these two values are EQUAL to your ISY's new HTTPS port 3. Make sure your ISY is not in the DMZ With kind regards, Michel

Hi dansmith, I am so very sorry to hear about all these problems. Would you be kind enough to let me know if you have any SwitchLinc version 35 (as reported on the Admin Console)? The other question I have is the difference between the state of devices when it worked (this morning) and the state of those devices when nothing worked. With kind regards, Michel

Hi jca, The difference are: 1. Number of devices/scenes 2. Number of programs 3. Batch mode ... you can do all the programming in batch and then let ISY do all the actual device programming later on With kind regards, Michel

Hello 87boosted, Thanks so very much for the detailed analysis; it makes much more sense now. Perhaps it would be much better to have a short call to discuss. If you're amenable, please send me an email to tech@universal-devices.com. Thanks again and with kind regards, Michel

Hello apostolakis, Excellent questions! Please see my comments below. With kind regards, Michel Yes Yes Wait terminates if and only if the condition turns to false. During the wait, if the condition does NOT change (regardless of the permutation of the events that keep it true) then the program continues with its current execution and does NOT restart from the beginning

Hi Jason, ISY provides the following methods/SDKs for integration with ISY: 1. WSDK ... Web Services SDK; simply import the WSDL to your VStudio project, supply the URL and userid/pwd and you can do everything in the link you sent in a day. We also have a sample C# project that you can start from 2. JSDK ... same as WSDK but it's a Java library 3. REST ... you can use URL based commands to control ISY For more information please checkout our developer forum: http://forum.universal-devices.com/viewforum.php?f=2 Furthermore, we have a $50.00 developer discount provided that you are willing to share/sell the outcome of your endeavors with the rest of our community. With kind regards, Michel

Hi Moshe, It seems that your router does not support UPnP. What you want to do is to manually create port forwarding rules in your router: http://www.universal-devices.com/mwiki/ ... PnP_Router With kind regards, Michel

Hello all, Wait is interruptible (so is Repeat): if the condition for the program in which the Wait is specified turns false, then the statements after the Wait are not executed. I am not certain where the notion that the condition is re-evaluated after a Wait stems from. Conditions are evaluated based on events; if ANY statement - and regardless of the program causing it to execute - creates events for which there are conditions, those conditions are re-evaluated as they should be. With kind regards, Michel

Hi rudyonrails (nice!), Please take the following into consideration: 1. Apple routers do not support UPnP ... so, you cannot use File | Enable Internet Access from the Admin Console 2. If your Airport is connected to another router/modem, then what you have to do is to disable Airport from distributing IP addresses. Otherwise, both your Linksys and your Airport are going to distribute IP addresses and thus cause a conflict 3. Finally, you will have to do manual port forwarding from your router to ISY the instructions for which you will find here: http://www.universal-devices.com/mwiki/ ... PnP_Router With kind regards, Michel

Hi kingwr, Thanks so very much for your feedback. It's indeed appreciated. I am not sure I understand the question. In the above example the intended behavior is: if (A && then C where A = x && y && z The concept of short-circuit in logic suggests that C should not even be evaluated if A is false. And that's precisely what's happening. Furthermore, C is transient: so, it follows that if C is taken place then A should be evaluated and thus the whole condition should be re-evaluated. Am I missing something? Would you elaborate on why folders are counter-intuitive? This is quite surprising because folders are the organizational units that allow you re-use of conditions without having to repeat them. For instance, Christmas folder will only be evaluated during Christmas (provided the correct constraints). I do agree that scripts are quite powerful and much easier for developers and we are in fact investigating scripts. This said, however, scripts would be quite difficult for the non-developers. With kind regards, Michel

Hi Joe, MEM/Error blinking means any one of the following: 1. ISY could not renew its DHCP lease ... this can happen a lot with some routers and there's no reason to worry about it since a) ISY retries 5 times and if there were issues, you would not be able to access the Admin Console 2. ISY does not sense being connected to the router ... this does not happen often at all ... if it did, you wouldn't be able to access the Admin Console 3. ISY sensed a conflict of IP address with another device ... this SHOULD not happen ... if it did, not only you would not be able to access the Admin Console but also the other device would be inoperable So, in all likelihood the problem is #1 and I would not worry about it at all UNLESS you have network communication issues with your ISY. With kind regards, Michel

Hi Joe, Is it really every few minutes? If it happens up to 10 times a day, I wouldn't worry about it at all. If it really happens every few minutes and continuously then there's surely something very wrong. With kind regards, Michel

Hi, There are two things that you must look for: 1. Loose neutral (I think it's white) wire 2. The load for these device might actually be the cause of all the issues With kind regards, Michel

Hi again, It is really not MobiLincs fault! MobiLinc is using ISY's APIs and therefore I have to assume that you have communications problems with those devices. Would you be kind enough to let me know the firmware version for your SWL Relay? If v35, then I bet that's the issue right there. If not, then we have to figure out why those devices do not respond reliably to scene commands. With kind regards, Michel

Hi dansmith, Good catch! Yes, indeed the program is re-evaluated every time an associated condition is changed. As far as D3 On, is it still happening? With kind regards, Michel

Hi gfridland, Apologies for a tardy reply as we were trying to reproduce this problem to no avail. As such, would you be kind enough to 1. Send a copy of your programs (My Programs | Export) to support@universal-devices.com 2. In the email, list the name of the programs that you think are causing the problem With kind regards, Michel

Hello sceaton, Apologies for a tardy reply. You are correct, I didn't notice that. If you are sure that you linked your thermostat at the OFF mode, then I have no choice but to suspect the thermostat dongle. This said, I am also wondering if you have thermostat from a batch with different firmware (this has happened before) ... As such, although I do recommend replacing your thermostat, I am going to keep an eye out for others with the same issue. With kind regards, Michel

Hi sceaton, But, indeed you are getting setpoint changes from the thermostat: Mon 03/22/2010 05:56:57 PM : [ 14 6 CC 1] CLISP 142 (Set point) Mon 03/22/2010 05:56:57 PM : [ 14 6 CC 1] CLISPC 154 (Cool set point) Mon 03/22/2010 05:56:57 PM : [ 14 6 CC 1] CLISPH 142 (Heat set point) Do these not get reflected in the Admin Console on the thermostat's main node? What are you are not getting is fan mode and the heat/cool calls. Is this the only thermostat you have? With kind regards, Michel

Hi Genstr, The fact that you get the second login prompt points to some networking issues. What firewall software do you have. Yes, LED brightness is supported for KPL 2D and above however the prerequisites are: 1. ISY Admin Console must report the version for your KPL as a number above 2D (not 00) 2. You must be using the latest URL ... using /99i will not work. So, please try http://www.universal-devices.com/99i/2.7.13/admin.jnlp I am more concerned about the double login and status issues. Please do let us know so that perhaps we could setup a tech support session to login to your computer and see what's causing all the issues. With kind regards, Michel

Hi Illusion, I verified this issue and it's now a bug that we'll fix for the next release. Apologies for the inconvenience. With kind regards, Michel

Hi bbconvert, The maximum number depends on your model number: 99i support 256 nodes=devices/scenes/folders, so, if you do not use any scenes at all, the total number of thermostats is 256/4 (nodes per thermostat)=64. If you have PRO series, then it would be 1024/4=256. With kind regards, Michel

Hi Justin, I am so very glad to hear it! You can remove the the KPL from ISY and it removes all the buttons from the associated scenes/folders automatically. This said, however, it would still take a long time to process all the communications. With kind regards, Michel

Hi johnmsch, Yes! Can you tell me what firewall software you are running on your computer? Also, you might want to try https://your.isy.ip.address (some firewalls are more lenient on https sites). With kind regards, Michel

Hi dkaleita, Thanks so very much for the update. This is indeed strange ... With kind regards, Michel

Hi Dodger, I am so very sorry to hear this. If the RX is lit all the time, then you are surely having a PLM issue. What you want to do is: 1. Unplug your PLM from the outlet, wait for a minute, and then plug it back in. If this does not solve the issue, then 2. Try using a different cable between the PLM and ISY, if this does not solve the issue, then 3. I strongly recommend getting a replacement PLM With kind regards, Michel