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!