Jump to content

pwaara

Members
  • Posts

    19
  • Joined

  • Last visited

pwaara's Achievements

Newbie

Newbie (1/6)

0

Reputation

  1. More questions.... If I have the remote in non-toggle mode, what command gets sent if I press and hold the button? I tested it with Bright, but that didn't seem to get triggered. I was looking at the diagnostics to see if I could interpret the data going across. I see something being sent, but I don't have any clue what the codes mean. Is there and api or some reference document that describes what the codes mean in the diagnostics? ~Pat
  2. Thanks, LeeG. That's what I thought (was afraid of). If only the remotes could act as a Responder, none of this would be necessary. You have all been a great help. I truly appreciate it. ~Pat
  3. I think I know the answer to this, but... I had to remove the remote as a controller from the scene that would control the light I wanted the remote to control, since with the program, it was now getting called twice. The side effect of this is now, press and holding the remote button has no effect on the light. Do I need to create a control program for each kind of button press (e.g., press and hold and double tap)? Can I put that all in one program controlling that button or do I need separate programs for each type of button press? Thanks for all of your help. ~Pat
  4. Thank you LeeG and oberkc. That seems to have done the trick. Just so I understand, do all programs get evaluated any time a state changes, a condition occurs, or a schedule fires? At that point any conditions that are true will execute. Is this correct? ~Pat
  5. I'm still trying to get my remotes to behave they way I want them to. Ideally, my remote would be in non-toggle mode (since I cannot update its state) then when a button is pressed, it would toggle the state of the responders it was connected to. For example, I press the e button and if the light is on, it turns off; if the light was off it turns on. I tried writing a program that had a Condition saying if Control 'remote e' is switched On And Status 'light' is not Off Then Set 'light' Off Else Set 'light' On What happens is the light cannot be turned off. It dims for a moment then turns on again. It appears that the Control statement looks at the state of the button on the remote, not the action of pressing the button. I'd like to know when the button has been pressed, not just its current state. Can that be done? Any other ideas on how to accomplish what I'm trying to do with my remote? Any help is greatly appreciated. ~Pat
  6. Thanks for the reply, LeeG. I was afraid of that. I'll have to decide whether it's worth buying a separate remote just for the fan or live with pushing the buttons twice. No, I'm not using Maverick. This is on Windows 7. Java version 7 update 45. ISY 994i Pro (1100) - OpenADR (21010) UI v4.0.11, Firmware v4.0.5. I'll not use this feature as I'm afraid it will mess everything up, and that was a lot of work getting all these remotes set up. ~Pat
  7. Well, I manually put the remote into non-toggle mode, and it doesn't really work the way I want. It works great for the fan speeds, but I can't turn off lights with the other buttons. I can only turn them on. I don't suppose there is a way to put some of the buttons in non-toggle mode and other buttons in toggle mode. As it stands now in toggle mode, you pretty much have to push the button twice to get the desired effect. Not horrible, but not what I want either. The best solution would be for the remote to act as a responder. That would fix everything. Any suggestions for the best way to set up an eight button remote to do fan motor functions and control other lights that are also controller by other switches?
  8. I have a RemoteLinc 2 programmed currently in toggle mode to turn on the four modes of a fan plus some additional lights. Since you cannot update the state of the remote via a controller, it gets our of sync when the fan or lights get updated from the other switches. I thought if I put it in non-toggle mode that maybe this would work; however, when I update the mode in UDI ISY99, it locks up. I have to kill the java process to get it to respond to anything, and it doesn't seem to update the remote even though it is on and in program mode. Any suggestions as to what is going on or how to best try putting the remote in non-toggle mode? Will this get me the desired effect being in sync with the other switches? Any advice is appreciated. ~Pat
×
×
  • Create New...