Okay, got it.I think.
This is one-way traffic, no feedback from end devices.
For sanity if nothing else, you’ll want individual Items representing your blinds etc.
That in turn allows you to use standard UI widgets, seems desirable!
Standard widgets and Items will deal in standard OH commands,but we need to convert those to unique per Item + command strings (for your Broadlink MAP Item). Like your rule does now.
Your master MAP for all seems smart - much more manageable than many little maps.
There isn’t a shortcut for this, but the one rule can be made “universal” and handle all Items and commands, if you adopt an Item naming convention relating Items to your master MAP.
Example from your original -
Roller Item named Bedroom1NightBlind
Expect commands UP/DOWN/STOP from UI or rules.
So - name entries in your master MAP
Bedroom1NightBlind_UP = 1234
Bedroom1NightBlind_DOWN = 5678
Now the rule can trigger on any command, and in script build a string from triggering Item name and incoming command. Obviously, command that new string to master Item.
Then we can get clever; put all Broadlink Items into a Group.
Change the rule trigger to be a command to any member of the group.
The rule can find out the triggering Item’s name to build the new string together with the actual command, and send to master as before.
One rule for all devices.
So to add some new roller -
Create an Item, add to Group.
name_command=code entries to master MAP
Should be easy to manage.
I can’t give you a script example as I don’t work in UI, but this is all straightforward stuff.
There is undoubtedly a way to embed the individual IR codes in the actual Item’s metadata, and have a rule call those out for sending direct to broadlink, so avoiding the master MAP. Personally, Ilike the idea of allin one place though.