Jump to content

Michel Kohanim

Administrators
  • Posts

    26777
  • Joined

  • Last visited

Everything posted by Michel Kohanim

  1. Hello madcodger, We could possibly include an option in ELK configuration to ignore A1. This should be a stop-gap till ELK adds facilities to filter what is being sent to ISY. With kind regards, Michel
  2. Hi Dave, I think the problem was that your PLM was overwhelmed! (this does happen with PLM firm 52). Please keep a very close eye on this issue and, if it happens again, please replace your PLM before the warranty is over. With kind regards, Michel
  3. Hi Bob, I do apologize for the inconvenience and a tardy reply. Yes, there is a way to update the firmware through the serial port. But, before doing so, please send us your URL and perhaps we could upgrade it remotely (support@universal-devices.com). With kind regards, Michel Hi Michel, This appeared to work for a short time, where it said "negotiating keys" or something along those lines, then the browser (Opera) died. I retried using Explorer and the browser immediately died after attempting to login. Is there anyway to login using the serial port and update/reset the software this way? I'd really like to change the time, because one of our lights comes on at 4am or so, and I think our baby sees the light under her door and thinks we're up. It's no fun getting up at 5am to put the baby back to sleep. Thanks, Bob
  4. Hi Dave, Sincere apologies for a tardy reply. It could certainly be a bug which was introduced in 2.6.7: do you have a thermostat in your installation? But, to be honest, I think there's something much more serious going on. How old is your PLM? With kind regards, Michel
  5. Hi AnthemAVM, You are not doing anything wrong: ISY is asking your router for the external IP address to which your router is responding with 0.0.0.0. Perhaps you should reboot your router one more time! With kind regards, Michel
  6. SomeWhatLost, Unfortunately I have no more ideas. Umm, ok, one last question: When you first used your ISY with this computer, did you accept the certificate? If not, or if you do not remember, please go to your Java console, click on the Security tab, and delete all your certificates. With kind regards, Michel
  7. Hello Keith, I do apologize for the inconvenience. This is a bug that has been eluding us ... in all likelihood, the reason the GUI shows you ISY, is because it defaults to that if it cannot retrieve the configuration. It would tremendously help us find this bug if you could enable internet access so that we can get to it remotely. With kind regards, Michel
  8. Hi SomeWhatLost, We do know for a fact that 32 bit Java installation does NOT work well on a 64bit system (it runs in compatibility mode). I am not sure why it work on Friday ... we have had reports of intermittent behavior but we could not reproduce them. With kind regards, Michel
  9. SomeWhatLost, Apologies for a tardy reply ( I am in a week long conference). Aha! If you are using 64 bit Windows, you must use 64 bit Java (look for the x64 link here): http://java.sun.com/javase/downloads/ea ... p#6u10JREs Please do let us know of the outcome. With kind regards, Michel
  10. Hello eddyk, Yes, it is! (unfortunately, though, at a very low priority since there's a workaround). With kind regards, Michel
  11. jwagner010, KPL timers only allow for group 1 to be a controller. This means that regardless of which button you press, only group 1 multicast is sent. And, therefore - unless I am totally off - there's no way for adding individual buttons as controllers. So, all you have to do is to drag/drop button 1 into a scene as controller. The effect is that based on the button you press, the elapsed time for Off will vary. With kind regards, Michel
  12. d_l, I am so very sorry for the inconvenience. From what I read (especially the fact that ISY could not query some of your devices + the fact that no events are received) tells me that we might be dealing with a faulty PLM. Please do be kind enough to: 1. Reboot your PLM ... wait at least 60 seconds before you plug it back in 2. Try query those devices that had problems Please let me know if you still do not receive event statuses. With kind regards, Michel
  13. SomeWhatLost, Now I am VeryMuchLost! Does this happen on any URL used (http://www.universal-devices.com/99i as well as the direct URL)? With kind regards, Michel nope, both are just running the windows firewall... I tried turning it off, and still no go...
  14. jrabin, I think you would want to do the following: If Time is Sunset Then Send X10 'H11/On' Else - No Actions - (To add one, press 'Action') If On Mon, Tue, Wed, Thu, Fri at 11:00 PM Or On Sat, Sun at 12:30 AM Then Send X10 H11/Off Else - No Actions - (To add one, press 'Action') With kind regards, Michel
  15. Hello again SomeWhatLost, I don't think it's Java. I think it's firewall ... do you have a different firewall software installed on the other computer on which everything works fine? With kind regards, Michel
  16. Hello chadg, A point of clarification: There's really no direct link between switches even if you set them up manually; they are all group links (based on the button number). There's, however, a direct command which can be sent from one device to another. So, for instance, when you send turn on a device from ISY, you are sending it a direct command. For direct commands to work, there must be at least one link record in the responder with the address of the controller. So, in summary, when you put controller/responders in the same scene (in ISY), ISY actually creates all the links as they would've been created manually. With kind regards, Michel
  17. Hello deeepdish, long time no see! Apologies for a tardy reply ... At any point in the program, if the condition become false, the program stops running. As such, you are seeing the correct behavior. May I humbly ask why you have that condition in the first place? It seems that all you want to do is to turn on a fan for 30 seconds every 30 minutes. With kind regards, Michel
  18. Hello Denis, First of all, you are not doing anything wrong. The only issue is that for ISY to find devices in a PLC, the PLC should have the same type of memory map as PLMs or other INSTEON devices. The next best alternative is to retry the same method but this time start from a regular switch that has the most number of links to other devices in your house. Please do keep us posted. With kind regards, Michel
  19. Hello SomeWhatLost, We have some reports of recent Firefox/Java incompatibility which we are trying to resolve. Would you be kind enough to let me know: What version of Firefox do you have? What version of Java do you have? In the meantime, if you are accessing your ISY through /99i, please try accessing it directly and if you are accessing it directly try accessing it through 99i and let me know of the outcome. Thanks and with kind regards, Michel
  20. Hello ctviggen, Please do be kind enough to try: http://www.universal-devices.com/99i Also, if you have not already done so, I do recommend upgrading to 2.6.7 ( http://forum.universal-devices.com/viewtopic.php?t=1613 ) With kind regards, Michel
  21. Hello Eug, I do apologize for the inconvenience. This must be a bug; may I ask what version of ISY did you try to upgrade from? Yes, there's absolutely a way to recover. We can update it for you remotely (if you have it on the Internet) or we could send you instructions to do it over the serial communications if you feel like it. Please do let me know how you would like to proceed (tech@universal-devices.com). With kind regards, Michel
  22. Hi Gary, Yes, precisely. Have you tried this with Gmail yet? With kind regards, Michel
  23. jwagner010 and Gary, This is noted and we shall try and implement it in the next release (I hope!). With kind regards, Michel
  24. Hi Gary, Please start here http://forum.universal-devices.com/viewforum.php?f=2 . I will also send you our draft WSDK documentation. With kind regards, Michel
  25. boots, I do apologize for the inconvenience. Please do be kind enough to immediately contact our support (support@universal-devices.com) so that we can logon remotely and find out where the problems are originating from. As far as frequent request failures, in our experience, these are mostly related to noise on the powerline. With kind regards, Michel
×
×
  • Create New...