The interface would be determined in how the system designer
and homeowner chose to configure them on the guis, but just
typing in names and associations, just like asigning stuff in
lutron homeworks software.
But determing what the homeowner wants and creating that is what custom installers do, it's not what your product is doing for them. And it's still hard and it still oftne takes multiple iterations since the customer doesn't always really want in the end what he thought he wanted and so forth.
The magic is the elimination in the timing writing the code
to get the interface and association with everyhting including
phantom keypads, and debug and such. I haven't seen a
programmer blwon away by getting everything out of a
network connection yet. no diagrams, no polling, just did it.
This isn't very magic. The Lutron system provides access to the configuration data to the automation system, and it sucks that out and knows what is available. Our Vantage driver does the same. If that's magic, it's pretty common magic.
