Allow System settings to be used in actions

[w-le]

Currently when defining an Action, I am restricted to using only static values as Module exec parameters. Conditions are restricted to only that and Module status variable values.

But I would love to use the values of System (and maybe even Logic Module!) settings as variable values, for Actions at least.

Example use case:
There are 100 Systems (rooms), each with unique Lighting IDs, controlled by the same Lighting Driver. Every System has a unique setting e.g. lighting_id: 323
If I could use that setting in the Trigger Action "Turn on room lights when x", then I can avoid having to write a logic driver that abstracts the lighting control for the room (or having to create a trigger with static values for EACH room)

.

[w-le]

Steve has mentioned that implementing this would be very hard and that since Node RED integration is on the roadmap, that Triggers can be kept for more simple scenarios which won't need to access system settings (those would be implemented as Node RED automation instead).