Make rule with 196 if-statements more generic

[lipp_markus]

I cannot type it out for your, but I would like to believe that the right REGEX transformation will allow you to parse the string as needed.
You seem to get all the info you need in a string with the first four digits your connected to your item name and the last one your command.
You can piece together item names from strings, this post here is imho an excellent guide:

Design Pattern: Working with Groups in Rules

Edit: Updates for OH 4, inclusion of JS Scripting and Blockly examples, removed the doors example as it’s superfluous. Please see Design Pattern: What is a Design Pattern and How Do I Use Them for how to read and use DPs. Problem Statement One powerful way to consolidate code in rules is to use array/list manipulation operations on the members of a Group. For example, filter down to just those members that are ON, get a list of the labels of those Items that are NULL, etc. Concept [image] T…

REGEX can be tricky, but there are REGEX validators online (e.g., regex101) and the documentation hopefully gives you a start.
So in short:
creating a string with “Tex_GV_Z”+REGEX(here-comes-expression-for-getting-device-number converting it to a item object replace the string in your sendCommand with another REGEX that gives you the relevant digit, may just collapse your code into a more manageable size.
Sorry that I am unable to give more concrete examples but hopefully the pointers above will allow you to proceed.