Jump to content

Sub-Routine

Members
  • Posts

    2226
  • Joined

  • Last visited

Everything posted by Sub-Routine

  1. Interesting. Let me pass this on to the programmers. Thank you for pointing this out. Rand
  2. I just got an IOLinc to test. Garage door is #1 on my list. Meanwhile this thread should help you. Rand
  3. Program 'Weather Warm' If Module 'Climate' Temperature >= 20 °F And Program 'Temperature Warning' is True Then Run Program 'Temperature Warning' (Else Path) Else - No Actions - (To add one, press 'Action') When temperature rises Only runs if it was cold during last check Rand
  4. I use one program that waits before sending the Notification. This way if the temperature is fluctuating emails aren't continually sent. That program is called by two other programs, one starts the timer and the other stops it. If you duplicate the Notification in the Else path you could have an email when it warms again. Program 'Temperature Warning' If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 15 minutes Send Notification to All Else Wait 15 minutes Program 'Weather Cold' If Module 'Climate' Temperature < 20 °F And Program 'Temperature Warning' is False Then Run Program 'Temperature Warning' (Then Path) Else - No Actions - (To add one, press 'Action') When the temperature falls Only runs if it was warm during last check
  5. Yes, in the User Guide. Rand
  6. No you are not too picky. This should work with the ISY. If the button is flashing it is usually an indication that an Insteon responder is missing from the scene the controller knows. That doesn't explain why the buttons aren't turning off immediately though. Do you have an odd load on the KPL? Rand
  7. Steve_p, You can set button D to non-toggle-off and create a scene that contains all the other buttons controlled by button D. Scenes are all written to the devices and will work without the ISY. Whatever mode the button is in when changing it to non-toggle will stick when using the using the ISY to change the toggle mode, so if you want it non-toggle off be sure the button is off before changing it to non-toggle. Rand
  8. If you want to Query the devices once an hour, just to be certain of their statuses, then make a scene with all the devices and use another program to run a Query on that scene once an hour. Rand
  9. The ISY does not send requests for Status unless the Query command is used. Otherwise it just keeps track of statuses. Rand
  10. If you haven't yet would you try a power cycle? I haven't seen any new tickets come in today. If the power cycle doesn't work I suggest you resubmit. Thank you, Rand
  11. Make a new scene with the all lights you want to control. If they are at different levels the softest ones will turn off first, but they will all fade at the same rate. Rand
  12. Yes, they are Mutually Exclusive Buttons. Rand
  13. Oh, I see. That is odd. Did restoring the RL correct the extra flashing? Thank you, Rand
  14. Good post to_lighter! Rand
  15. Wayne, that is a small glitch in the display program, it's displaying one too many records. Any record that begins with 00 is the end of file. 22 = deleted, E2 = controller, A2 = responder. To be fixed in the next drop. Rand
  16. Good deal. I have changed most schedules to sunset/sunrise and use the light data to control the lights from sunrise to sunset. I vary the threshold depending on the windows in the room. Now, in the winter, I use a lower Light level to turn off lights in rooms that have a window to the south and a higher level in rooms with windows to the north. It's been working great! We had some snow a few days ago and I watched the lights stayed on later after sunrise, turned off in the south, came back on as the clouds rolled in, and turned all off as the sky cleared. Our upstairs hall is open to the foyer and has a large window facing east. I use a lower level from sunrise to noon than I do from noon to sunset. How's the sick child? Rand
  17. There is a checksum. Every Insteon commands contains a checksum. The devices themselves generate and decipher the CRC codes. Rand
  18. Yes. Mine is labeled v 1.1. Rand
  19. The only way to change the local level involves resetting the switch. Is that your intention? If so assign a low light level to the switch (local level) and use a program like this: If From Sunrise To Sunset (same day) And Status 'Bathroom' > Off Then Set 'Bathroom' Fast On Else - No Actions - (To add one, press 'Action') Rand
  20. Yes it is a limitation of the switch. A keypad can reread the values without a reset. If you use the ISY to fine tune the local levels and rates on your switches a quicker way to reset many switches is to cycle the circuit breaker(s) instead of pulling each set button. Rand
  21. No, only the levels and rates in scenes the ISY controls can be changed in programs. When you change the local level a switch requires a reset before it takes effect. Rand
  22. That is an Insteon function. It would take a hardware change in the devices. Rand
  23. Greater than 417 links in the PLM. Rand
  24. Darrell, you make me proud Rand
  25. It sounds like you did it correctly. I assume you have checked the level of the keypad button in the scene? Is the KPL B present as a responder in another scene? Viewable in the Membership display on the device window. Or controlled with another program? Find/Replace function in the Program Details pane. Start at My Programs. What version ISY and firmware and KeypadLinc do you have? Thank you, Rand
×
×
  • Create New...