Thank you for both of these links.
An architectural orientation is something that seems kind of missing in the world of DIY home automation as I've seen it so far. The focus seems to be on the devices first and then on the hubs, integrations and specific automation, with little focus on use cases. This seems a significant barrier to entry for new adopters that would be lowered if the focus began with the user experience, what you can do with automation, and then you can drill down into how this can be achieved at the application (hub etc programming) and physical (device) level. No doubt this will come as the industry matures.
While I have developed a reasonably good idea of how I would like things to work, I am struggling to work out whether or not I can achieve this with the devices (which i need to commit to fairly quickly given the stage of our build) that are available within the price bracket I'm willing to pay for the volumes I need - most immediately 40+ relay modules of various types, 10+ LED strip controllers and 10+ under cabinet lighting drivers. After ongoing review of what is available, I think some quick Proofs of Concept are in order!
The post on good practices with RM will be very useful when I actually get the time to start configuring automations in earnest.
