Jump to content

tcster

Members
  • Posts

    16
  • Joined

  • Last visited

Profile Information

  • Location
    Essex, VT
  • Occupation
    Server Administrator

tcster's Achievements

Newbie

Newbie (1/6)

0

Reputation

  1. Since LeeG is certain this isn't a 2.8.16 issue, I have moved it to here: http://forum.universal-devices.com/view ... hp?p=45537 Thanks!
  2. Has anyone else tried to add a triggerlinc since upgrading to 2.8.16? I recently acquired 2 #2141 Rev 1.2 triggerlics and I can't get ether of them to link to the ISY. The error I get is: Failed writing the highwater mark [-200000/-1] Node not added- failed removing links (14 40 4A 1) [-200000/-9] I've tried "removing links", not removing links, selecting Auto Discover, selecting TriggerLinc. I've tried linking with the TL 3 feet from the AP. I moved the AP and plugged it into the PLM. Nothing seems to be working. Any other thoughts?
  3. tcster

    Status for Drapes

    Let me start by saying thanks to those that have assisted me. Let me also state that my first stumbling block was that I was having the buttons on two different KPLs show me the status of the AppLinc that powered the drapes. The problem with that is that if the drapes were opened or closed "manually", the timed program would then return them to the opposite position. Instead, I changed that, so that the buttons were lit when the drapes are open, and dark when the drapes are closed. That way I can have programs run, but only based on the status of the KPL buttons. So: The "Scene" contains 1 button on each of 2 KPLs. This way iw one is pushed, the other will show the same status. Then there are two programs: Drapes Open: If Status 'DRKL Drape Switch' is On Or Status 'MKL Drape Switch' is On Then Set 'Drape AL' On Wait 19 seconds Set 'Drape AL' Off Else - No Actions - (To add one, press 'Action') and: Drapes Close If Status 'DRKL Drape Switch' is Off Or Status 'MKL Drape Switch' is Off Then Set 'Drape AL' On Wait 19 seconds Set 'Drape AL' Off Else - No Actions - (To add one, press 'Action') These two programs respond to the buttons being pressed. If I understand IndyMike correctly, I could substitute 'Status' cor 'Control'. After that, I have the programs that control the timed opening and closing of the drapes. Since it's summer here, I have the following: Morning Drapes If Time is Sunrise + 6 hours And Status 'DRKL Drape Switch' is On Then Set Scene 'Drape Controller' Off Else - No Actions - (To add one, press 'Action') Evening Drapes If Time is Sunset + 15 minutes And Status 'DRKL Drape Switch' is Off Then Set Scene 'Drape Controller' On Else - No Actions - (To add one, press 'Action') This keeps the sun from glaring into the living room during the afternoon. Come winter I'll reverse the programs. The nice part is that if the drapes are "manually" opened in the afternoon, they stay opened during the Evening Drapes program whereas before they would go to the opposite state, i.e. closed. I've probably confused everyone at this point, but I'll end by saying that it seems to be working much better than it was before.
  4. tcster

    Status for Drapes

    Clark: The drape motor is pretty simple (Smarthome #3142). When power is applied, the motor turns in one direction until the stop is reached. When power is reapplied, the motor turns in the other direction until the stop is reached. For my particular drapes, it takes about 13 seconds to fully open or close. The instructions did say the power should be shut off after the stop has been reached. Hence the need to "shut off" the AppLinc after 19 seconds. Mike: 1st: The two KPL buttons are/were linked as you sugessted. 2nd: Testing proved to me that I couldn't rely on one program or another being true or false when I thought it should be. That cause the drapes to be constantly opening and closing. So, I reworked the programs so that the "status" was determined by the switches current position (on/open or off/closed). So far this seems to be working, but I haven't tested it fully yet. Once I have some better results I'll post the code in case anyone else is interested, or has a better suggestion. Thanks!
  5. tcster

    Status for Drapes

    Well, I think I have it figured out. I rebuilt my Drape Scene to include the two KPL buttons as controllers. I then created to programs: Drape Open: If Status 'DRKL Drape Switch' is On Or Status 'MKL Drape Switch' is On Then Set 'Drape AL' On Wait 19 seconds Set 'Drape AL' Off Else - No Actions - (To add one, press 'Action') and Drape Close: If Status 'DRKL Drape Switch' is Off Or Status 'MKL Drape Switch' is Off Then Set 'Drape AL' On Wait 19 seconds Set 'Drape AL' Off Else - No Actions - (To add one, press 'Action') After that I created the following conditional for morning timer: If Time is Sunrise + 5 hours And Program 'Drapes Open' is True Then Run Program 'Drapes Close' (Then Path) Else - No Actions - (To add one, press 'Action') That way if the Drapes Open program is true the Drapes Close program will be called, otherwise they will be left alone. Does that seem correct? I'll have to do some more testing to verify everything. Thanks Mike!
  6. OK, I've look around a bit, but haven't been able to find what I'm looing for. I have a set of drapes powered by a drape motor and an ApplianceLinc. The problem is that you turn the ApplianceLinc on for 45 sec or so, and then back off in order to open or close. That way power is no longer being supplied. I have to KPLs that each have a button to operate the drapes. I also have a timer program. The timer program works great EXCEPT when the drapes have been opened or closed manually (by the KPL buttons). What I'd like to accomplish is a "Status", if you will, of whether the drapes are in an open or closed state. That way my timer program can ask if the drapes are already closed and leave them alone, as opposed to opening them again. Or vice versa. Any thoughts on how I could accomplish this? Thanks, Tracy
×
×
  • Create New...