Jump to content

Michel Kohanim

Administrators
  • Posts

    26777
  • Joined

  • Last visited

Everything posted by Michel Kohanim

  1. Hi south, What you have should work provided that Coming In's last runtime is actually valid. When you go to Program Summary, is the last runtime accurate? With kind regards, Michel
  2. Hello south, You can use the last run time of a program as conditions in your other programs and evaluate the elapsed time. With kind regards, Michel
  3. Hello Joe, No ... i was just wondering what happened above and beyond loading an old backup. With kind regards, Michel
  4. Hello jcip, The first thing I recommend is to upgrade to 2.7.12. Please note that the fan mode/state changes have a little issue in thermostats: if you turn the fan on/off quickly enough, the thermostat dongle may get confused and from then on provide you with the wrong status. With kind regards, Michel
  5. Hi again, Thanks so very much for the detailed description. Things are a little more clear now: 1. In firmware 2.7.7 and below, you could not create a controller/responder link between sub buttons of the same KPL in scenes. For that you had to use Button Groupings (or Mutually Exclusive buttons). As such, the first thing I recommend is upgrading to 2.7.12 2. In all cases, and for all KPLs: - You cannot create a mutually exclusive relationship between a sub button and the load for the same KPL. i.e. you cannot have it such that when button C is on the load should turn off. You can, however, adjust the on level and ramp rate for the load given the sub button as a controller - There are no on levels/ramp rates for sub buttons; they can either turn on or off With kind regards, Michel
  6. Hi Joe, That's indeed bad news! What is this specific KPL connected to? Did you do a factory reset on it before restoring it? With kind regards, Michel
  7. jkraus, It's really not in an endless loop. It's trying to write all pending writes for all devices. This might take a while especially if those devices are not responding. If you have time, please let ISY try completing what it's doing. Once done, please take a look at your devices and make sure you do not have any devices with green 0101. If you do, then we have to figure out why they cannot be written out. With kind regards, Michel
  8. Hi matapan, Yes and specifically: -Getting status updates from the thermostat without having to query them With kind regards, Michel
  9. Hi mbrett, I have searched both the Google Account history for your name as well as our accounting system for any orders for your name and there's only one order. Would you be kind enough to send your full name to sales@universal-devices.com with a link to this post? With kind regards, Michel
  10. Hi Dave, Yes, I am certain! With kind regards, Michel
  11. Hi Dave, No, ISY should continue with the execution. I am thinking that the problem is that ISY cannot communicate with none of your devices in the action list. With kind regards, Michel
  12. Hi stevehoyt, Increasing the retry count would cause degradation of performance. I do not recommend it. 3 tries should be enough. I think it would be best to figure out under what conditions you see the comm. errors. With kind regards, Michel
  13. Hi mbrett, I have searched the system and there is only one order for you on 4/10/2009 for an ISY. Is it possible that you ordered using a different name? If so, would you be kind enough to send the possible names that may have been used to place the order to sales@universal-devices.com? With kind regards, Michel
  14. Hi Mark, You are 100% correct ... I think it had to do with our paranoia about security: the certificate holds your private key and we felt that it should not be stored on your machine and thus it was deleted after the installation. We just made a change that asks the user whether or not the file should be stored on the machine with a warning that this might constitute a security risk. Thanks again and with kind regards, Michel
  15. Hi Jeff, Please do take a backup of your 2.7.8. In most cases, the migration phase in 2.7.12, will migrate all your configurations properly. In rare cases (and specifically related to KPLs) and if and only if you have any problems, you have two choices: 1. Redo those scenes OR 2. Use a backup from 2.7.7 (or below) Again, I really do not think you are going to have any problems. Just to be safe, take a backup of your 2.7.8 and export your programs. With kind regards, Michel
  16. Hi Mark, If you do not have user accounts off on Vista/Windows 7, then the file will not be stored in any location except in Java's temp directory. With kind regards, Michel
  17. Hi AnthemAVM, They might be unrelated OR perhaps another device on your network is using port 444. For custom ports, it's always best to use a number above 1200 (1500 and above are much safer). If you can access your ISY, I wouldn't worry about infrequent mem/error lights. If they become frequent, then we have to figure out the cause: you might want to reboot your router especially if you use ISY to configure port forwarding. With kind regards, Michel
  18. Hi justin.cool, I'd have to agree with oberkc ... if the main button is not listed to the right then we either have a bug or that the main KPL button is not added to the scene. Please advise. With kind regards, Michel
  19. Hi justin.cool, Are you trying to turn the load OFF using one of its own sub buttons? If so, unfortunately this will not work. You would have to use a very small on level instead (if it's not a relay). With kind regards, Michel
  20. Hi Jeff, Sincere apologies ... wrong library version was installed. Please do be kind enough to clear your java cache and retry: http://www.universal-devices.com/ssl/insteon With kind regards, Michel
  21. Hi mitch236, ISY does not really care what your external IP address is. It simply shows you that IP for your information. ISY does check for external IP address changes if and only if its own IP configuration has changed. With kind regards, Michel
  22. Hello mbrett, Please forward your Google invoice to sales@universal-devices.com ... it shall be taken care of. With kind regards, Michel
  23. Hi ljm, In most cases you do not need programs. The main question is how does the current switch in your garage door works? i.e. if you took the wires that are connected to the switch out: 1. What happens if you short them? 2. What happens if you disconnect them? 3. What happens if you short them again? If the answer is that 1 opens (or closes) and 3 closes (or opens), then you are correct: indeed you would need a program since your garage apparatus is toggled. On the other hand, if 1 opens (or closes) and 2 closes (or opens) and 3 is equal to 1, then all you need are: 1. Latching mode in IOLinc 2. Non Toggle Off on your KPL button 3. The wires to the IOLinc are connected to NC or NO depending on what 2 is. i.e. if 2 causes the door to open, then you connect to NO. Otherwise, you connect to NC. With kind regards, Michel
  24. Hi Mark, I think we found the problem. Would you be kind enough to do a test with any of the following URLs: http://www.universal-devices.com/99i/2.7.12/admin.jnlp OR http://www.universal-devices.com/99i Thanks again and with kind regards, Michel
  25. Hi Steve, I am not sure why this would be the case. Query All (from the Admin Console) clears all the statuses and therefore any status is a change. In programs, Query All does not clear all the statuses ... So, are you referring to QueryAll in programs or through the Admin Console? With kind regards, Michel
×
×
  • Create New...