Jump to content

Sub-Routine

Members
  • Posts

    2226
  • Joined

  • Last visited

Everything posted by Sub-Routine

  1. The flashing is from the cleanup commands failing. 1-15 is one device responding to subsequent requests after a failure, while three other devices fail completely. 20 is four devices not responding. Probably. Since the scene responds this points to good communication from the RL to the devices and poor communication from the devices to the RL. Rand
  2. If you want to use a three wire cord you could locate the switch and the outlet anywhere along the cord you want. Neutral shared. Hot to switch. Load to outlet. Rand
  3. In my limited experience, I found that connecting the opener control wires together will not allow the door to change position, effectively locking the door. Rand
  4. jc, did you try tap-linking them?
  5. One thing you should know Jay, the ONLY way to use a specific ramp rate is to create a scene that specifies the rate. Direct On/Off commands are supposed to use the local rate, but my experience is that the last rate the dimmer used is used. If you call a scene that uses a long ramp rate to turn a lamp on, then send an Off using the ISY the lamp will use the long rate and NOT the local rate. Rand
  6. When you include the ISY in the scene then the ISY is notified whenever the scene changes. If the ISY is not included in the scene the device levels may be incorrect when viewed in the ISY interface. When you use the ISY to create the scenes it is automatically included. And it much easier than tap-tapping, especially when setting levels and ramp rates. Yes, it should be all programmed though the ISY. Unless you are using ISY programs to interpret specific key presses once you create the scene using the ISY the ISY is redundant. The KeypadLincs and RemoteLincs will function without interruption. Rand
  7. I thought you were already using scenes. Interesting reading, thank you for posting. You have very good ideas. Rand
  8. Yes, it makes sense. But there is a link in there, that is why the key is flashing. It may be leftover from testing. Use the Restore on the KPL. You may want to execute a reset first. Rand
  9. Matt, the light will flash when a linked device is not sending an acknowledgment to the KPL. Rand
  10. aLf, you beat me again I prefer to add each controller to the one scene. Once the ISY writes the links to the devices the ISY is out of the picture. If you use a program the ISY has to run the program before any devices are changed which usually takes ~0.5 second. Rand
  11. Any Insteon controller can run a program. You do not have to be in non-toggle mode. Here is an example. These programs are in a folder that is only true between a logical midnight and a logical dawn. Folder Conditions for 'When Midnight' Add conditions to limit when programs in this folder are allowed to run. If From 11:00:00PM To 4:44:00AM (next day) And Program 'Vacation On' is False Or From 11:59:00PM To 5:14:00AM (next day) And Program 'Vacation On' is True Then Allow the programs in this folder to run. When someone turns on the backyard light between midnight and dawn the first program turns on all the outside lights. Backyard Fast On If Control 'Backyard' is switched Fast On Then Set Scene 'Outside Lights' Fast On Else - No Actions - (To add one, press 'Action') When they turn off the backyard light between midnight and dawn this program will override that behavior and turn the light on to a dim level. Backyard Off If Control 'Backyard' is switched Off Or Control 'Backyard' is switched Fast Off Then Set 'Backyard' 49% Run Program 'All Off OL Dark' (Then Path) Else - No Actions - (To add one, press 'Action') Then it resets all the outside lights to their midnight levels. All Off OL Dark If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Scene 'Outside Lights - Evening' On Wait 3 minutes Wait 2 minutes (Random) Set Scene 'Outside Lights - Midnight' On Else - No Actions - (To add one, press 'Action') I have similar programs set up for all our outside light switches. Rand
  12. If you add a Wait command there is a Random option. Clipped example: If On Never Time is Last Run Time for 'Cycle Outside Lights' Then Repeat Every 1 second Set Scene 'XBlue XMas Lights' On Wait 5 minutes Wait 3 minutes (Random) Set Scene 'XBlue and Red Lights' On Wait 20 seconds Else - No Actions - (To add one, press 'Action') Rand
  13. AFAIK the fade commands use the same rate as holding a switch, not a user specified rate. The PLM does not send commands to individual devices when scene commands are invoked so there are not multiple commands being sent for fade up/down/stop. I was surprised at how well the fade works with the ISY and IR, but you are not having the same experience. One other thing I did notice was that if a lamp was still ramping to a level when a dim or bright (not fade) is sent the lamp will jump to it's target and then dim or bright from there. If a fade works the same way then perhaps some of your lamps are still ramping towards off when the fade is sent. I am just throwing out ideas here... Rand
  14. It is also possible with Insteon. However the time used to read the current levels before the change can leave the button pusher wondering why the lights did not react for several seconds. Rand
  15. No, everyone else can use the bright light The local load and rate will apply first. The scene you are calling will override the local settings. If you are using a long ramp rate it will take some time to change the level from 100% to your desired 50%. You might rather set the local level and rate to the dimmer, slower settings (remember to power cycle the SwitchLinc) and use the ISY to brighten the lamp quickly during daytime hours. Or let the users learn to click twice for full on. When the light is set to default level another tap on will change it to 100% at push and hold speed. Be aware that the status a dimmer reports is the level it is aiming for even as it ramps to that level. You light may appear to be 100% but be 99% and dropping. It is a lot of fun! Rand
  16. If you set up the links to control the fan using a method other than the ISY then the ISY will not be included in the scene. You will have to delete the links and use the ISY to create the scene(s). Rand
  17. That's a bug. Rand
  18. Why don't you just create another scene for your 7AM timer? Then you can set the ramp rates to whatever you like. Aren't the remote and touchscreen using scenes to control the lights? The lights should use the rate for that scene when the remote or touchscreen are used. Rand
  19. On Windows I have to use the icon to Open Console, then type "x". Rand
  20. I don't know about an HTML slider either. Perhaps a numeric input box and then a GO button? Thank you, Rand
  21. Michel and company, thank you for this update The HTML interface is working well on my PocketPC. Can we get a slider to set a device level instead of using Dim/Bright several times? Please? A few small notes (other than the AdminCon Dim/Bright): Notify message is still incomplete. KPL LED Brightness for Button 1 still hidden with screen width Status window keeps getting sent to back. This might be new. Thank you, Rand
  22. I still have to keep clearing the Java cache to reopen the console. Rand
  23. That is the same error message I see when trying to reopen the AC. http://forum.universal-devices.com/viewtopic.php?t=1224 Rand
  24. Worked for me! Thank you, Rand
  25. I get the same error. Ed, how did you get past it? Thank you, Rand
×
×
  • Create New...