Ummmm, no it really doesn’t make sense to me, truth be told.
So, you’re wanting to be able to command a microcontroller to from ST to perform 324 unique actions? That seems a little crazy, as I have to believe no human being, operating that remote control would remember 324 unique button press combinations. Thus, I have to believe you and I are still not exactly on the same page.
Let’s try it from a different angle. You have 11 shutter groups, that you’d like SmartThings to be able to control, correct?
- How many remote controls are you planning on hacking?
- Is there one remote per shutter group?
- Or one remote to control all of them?
- How many microcontrollers do you believe are required?
In SmartThings, how are you planning on controlling these groups of shutters?
- Will you be trying to use standard Automations and Scenes?
- Will you be using webCoRE?
In SmartThings, what exact ‘high level’ commands are you planning on issuing to the groups of shutters?
- Will all of the groups of shutters always be controlled to the exact same position (Fully Open, Fully Closed, Partially Open) in unison?
- Or will each group of shutters be controlled independently?
- What will you use to trigger the group(s) of shutters to change their state?
I am trying to understand your requirements, however I am not quite there yet. Please try to describe exactly what you expect SmartThings to do throughout the course of a typical 24 hours with respect to your shutters.
To be honest, I was sort of expecting you to say something like… “I’d like for ST to be able to send commands to Fully Open, Fully Close, and Partially Open my shutters.” I would translate this to mean that the microcontroller needs to handle three command sequences. To implement this, we could use a device that supports the “Switch” and “Switch Level” capability. This would allow us to map OFF/0% = Fully Closed, ON/100% = Fully Open, and ON/50% = Partially Open. The microcontroller would then interpret these three possible combinations in a specific ‘sequence of button presses’ on the hacked remote control. This would be ‘3’ Button Sequences in my mind.
Help simplify your requirements down to exactly what you’d like to accomplish during a typical day. That will help immensely.
For example, maybe the desire is to simply adjust all groups of shutters 3 times a day. Once in the morning, once in the afternoon, and once in the evening. This would wake up the microcontroller at each of these three specific times. For each event (morning, afternoon, evening), the microcontroller could issue whatever sequence of button presses on the remote control you’d like (i.e. control 1 group of shutters, or all 11 groups, whatever you’d like.)
However, if you’re looking to be able to manually control every group of shutters independently via the ST Mobile App, or a dashboard like SharpTools or ActionTiles, then a true integration between ST and the vendor needs to be explored.