Jump to content
C4 Forums | Control4

daluza

c4Forums Member
  • Posts

    6
  • Joined

  • Last visited

Posts posted by daluza

  1. I have 5 Modern Forms fans that are wifi enabled fans and have replaced the OOB bluetooth switched with a KPD-CFG.  I wanted to use the Up / Down buttons to dim / brighten the light.  However the device specific command doesn't see to work as you would expect (it doesn't do anything).  

    HAs anyone solved this use case? I would hate to write a long set of conditionals / if / else statements to enable a gradual step wise up or down setting the absolute light brightness.

     

    image.thumb.png.d122038e11a21837bce0bf0e1537f8fc.png

  2. 2 hours ago, fleon said:

    I actually did away with connections and went to programming only for one reason  (which takes a lot more programming, btw).  I have my "Lights"
     button cycle through scenes instead of the ramp/fade connection.   So, hit it the first time, it's bright; 2nd time it's dim; 3rd is a warmer color; 4th is reds/orange; 5th is a nightlight; 6th off.

    Saves me having to use a lof of buttons or remember what single/double/triple tap does.  

    So it's a preference for you.  I didn't like how connections worked for me.  And no, I don't see any speed difference.  

    Fleon, this is a great suggestion, and I will think about that...it might be worth the hassle to have that flexibility, I have figured out managing the LED states myself so might give it a try.

  3. I have an extra KPD-DIM left over and want to use it as a KPD-CFG (i.e. configure all the buttons as keypad and not have anything hooked up to the load).  Any issues with this?  Wanted to bottom this out before i put my next order in with my dealer...

  4. 12 minutes ago, mstafford388 said:

    1.  You can have a connection and programming fire of with the same button press.  Obviously this could create some undesired outcomes and typically isn't best practice.  If you program something the a button the connection doesn't automatically go away.

     

    2. Yes.

     

    3. Yes.

     

    4. You should absolutely be using connections for advanced lighting scenes with keypad buttons, simply for the ability to ramp/fade scenes with a button hold.  You can replicate the rest through programming (with a lot of work to make LEDs track properly across multiple keypads, when fired off with app vs button, etc), but the ramp/fade is a doosy to do via programming.  It can be done (timers, variables, etc), but it's not easy and won't ramp/fade as cleanly across the scene. 

    Thanks Matt, very helpful.

  5. Background: I have a relatively new installation that I am working on with my installer.  I have many KPD-C all throughout the house and most are marginally configured to give my rudimentary lighting throughout the house while I figure out what I really want in terms of scenes and from what locations (buttons) I want them controlled.  Also, I have a development background and been HA enthusiast for years - as such I like to do as much as I can myself using HE and when I hit the limitations of HE, have my dealer do it based on a clear design description. I find my dealer likes this better as they have a list of stuff to do and can knock it out and not deal with a lot of back-and-forth questions... :)  Now the questions...

    1) For the KPD buttons the dealer set up connections to I want change.  If I use programming to change what a button does, what happens to the preexisting connection?  Do they conflict, does the programming override the connection? (I intend to try to reuse the advanced lighting scenes where they exist, but some are just bindings from the keypad directly to the light)

     

    2) Once I lock in on what I want to do, will it make sense to have the dealer change those into connections where possible (assuming I also use advanced lighting scenes wherever possible?

     

    3) Once they get moved to connections, do I have to go back and clean up (delete/undo) all the programing that I did initially (like work to activate/deactivate the scenes, manage LED colors and activation, etc.)

     

    4) I get that a lot of the work to make a full scenario just work (multiple KPD synchronization, LED management, etc.) is handled when using connections... but is there a performance or reliability edge to using connections versus programming? Another words, If i get it to work like I want, is it worth having my dealer even mess with them?

    Thanks!

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.