Jump to content

Michel Kohanim

Administrators
  • Posts

    26777
  • Joined

  • Last visited

Everything posted by Michel Kohanim

  1. Hello, We do have instructions for almost all routers here: http://forum.universal-devices.com/viewtopic.php?t=635 This post will give you the link to portforward.com which has details of port forwarding for ALL routers. With kind regards, Michel
  2. Hello AD8BC, These are known issues with the latest SWL, KPL, and LL/AL firmware. SmartHome is trying to resolve/debug/pinpoint these issues as we speak. How long more do you have on your 30 day? With kind regards, Michel
  3. Hi Rich, If you put your devices in scenes, then you can program them without having to airgap. But, the main issue is that programming on level/ramp rates may take a long time (depending on the number of devices in the scene) and it's usually not worth the trouble and extra traffic. With kind regards, Michel
  4. Hi Rich, I cannot answer the last question by for the first two questions: RL's All on/All off controls ANYTHING that has been linked to RL. The caveat is that the onlevels and ramprates are taken from the first ever linkage to the RL. Yes, you can assign a button for All On/All Off but you will have to create a scene with all your devices (unless you want to use the All on/off button -- see above) With kind regards, Michel
  5. Hi CompKing, Yes, I have scene this and, as Zellarman suggests, it has to do with the IR sensor being close to Plasma TV. Please do keep me posted. With kind regards, Michel
  6. CJVann, I think there's a bit of confusion here: It is NOT the case that INSTEON devices uses the ramp rate of the last scene: 1. They use their stored/default ramp rate/on level. 2. Now, this is ONLY true if you are turning on/off the device directly. If you turn on/off the device through a scene, then the ramp rate/on level for that scene takes over. 3. If you control the device through another controller, then the ramp rate/on level for that controller-device combination takes over. 4. And, FINALLY, if you turn on/off My Lighting, then the ramp rate/on level for the FIRST ever scene of which the device is a part take over. All this said, which scenario are you referring to? With kind regards, Michel
  7. JasonWPB, This is NOT normal at all. When you go to the configuration tab, do you get Request Failed when you try synchronizing with the NTP server? With kind regards, Michel
  8. Hello again, This is a great progress. What this means is that your M1XEP either requires a reboot or has a bug. I strongly suggest rebooting your M1XEP and retrying the port 2101 as I think there are some strange things happening here. If that does not work, then I suspect you have another device on your network with the same IP address as your M1XEP. If you are connected to your M1 RP (which it seems you are), then NOTHING will work neither lighting rules from within ELK nor commands from ISY. The only thing that may work (intermittently at best) is arm/disarm. With kind regards, Michel
  9. Hi again, This is quite strange to say the least. Do you see any errors in ISY's log? With kind regards, Michel
  10. Hello again, The bug should not impact your programs right now. If you see 0 for the status of your thermostats, then please go to Help->About and let me know the version number. With kind regards, Michel
  11. Hi Rob, Yes, the unsecured port will not work. Which port are you using now and are you sure this is the right port configured in M1? With kind regards, Michel
  12. Hi again, This is quite interesting indeed and very much useful. I can tell you that I have not heard of any imminent changes to the thermostats API which would support what you are looking for. This said, however, I think you can do most of what you wish within ISY. Yes, it's quite a roundabout way of doing things but, tactically, that's the only option. With kind regards, Michel
  13. Hi rchorowitz, In the ELK configuration section, do you the correct IP address and port for your ELK? If you can get to your ELK Java Console, and if ELK RP is not connected, then it could only be the case that ISY cannot communicate with your M1XEP. Are they on the same network? With kind regards, Michel
  14. Hello soft00, Apologies for a tardy reply. It seems that your problem has been solved in the other thread. If not, please do let me know. With kind regards, Michel
  15. Hi Eric, LOL ... to be honest, this is one of those things that has been bothering me for a while and it's bound to get fixed. The way it is now is not good. With kind regards, Michel
  16. Hello Geoff, I am not sure what you are alluding to since - to my knowledge - humidity is a read only value. And, I have not seen anywhere in the INSTEON documentation that there's an option of setting humidity settings. Currently, you CAN write programs that do different things based on the humidity reading. With kind regards, Michel
  17. Hello CompKing, This has been fixed in 2.6.14 ... just for reassurance, this is a LOG bug where instead of saying Query, the log is just showing 0. In short, those entries are the query REQUEST and not the response. With kind regards, Michel
  18. Hello Candide, Is it possible that ISY got a new IP address after the upgrade? If so, you have to change the IP address in your settings corresponding to your ISY's IP address: http://forum.universal-devices.com/viewtopic.php?t=784 rchorowitz, Do you know the IP address for your ELK M1XEP? If so, what happens if you go to http://your.m1xep.ip.address? Do you get the Java Console? Also, are your sure your ELK RP is not connected? When RP is connected, no other client can connect to M1. With kind regards, Michel
  19. Michel Kohanim

    WeatherBug

    Hello CompKing, Unfortunately, the limitations of their desktop application also applies to their API which we use. With kind regards, Michel
  20. Hello Charlie, Would you be kind enough to make sure you have the correct year? I just checked LA, and ISY shows the correct time (within 50 seconds) of the times reported by NOAA: http://www.srrb.noaa.gov/highlights/sun ... nrise.html Furthermore, it seems that: 33 3m 36s 117 1m 12s are close enough so that even NOAA shows the time for LA instead. Please do let me know. With kind regards Michel
  21. Hello Eric, Unfortunately not at the moment. Currently, it's an all or nothing deal. With kind regards, Michel
  22. Hi Stowaway, Thanks for the update. My personal feeling is that you are going to have the same problem again especially if you try to program this appliancelinc to anything else. Please do keep us posted. With kind regards, Michel
  23. Hi someguy, Unfortunately you cannot do that now but this is a much requested feature (disable) which we shall include in one of our future releases. With kind regards, Michel
  24. Hello Charlie, This sounds very much like a bug. Would you be kind enough to send me your coordinates (including timezone, latitude, longitude)? Thanks and with kind regards, Michel
  25. Hi aLf, First of all, it would be quite interesting if a device would - by itself - develop links to other devices. But, I've seen worse! Ok, factory reset: 1. Take the set button out and leave out for 10 seconds 2. Push and hold it in for 10 seconds Yes, please do restore with ISY and keep us posted. With kind regards, Michel
×
×
  • Create New...