How to reuse code between UI rules?

[Neolinger (Antonio)]

@rlkoshak

You didn’t say what you are using

That’s true, sorry!

@rlkoshak

OHRT has some rule templates but It isn’t rule templates. It’s a node module (i.e. a library).

To be honest, I always have a hard time with the wording. What I did up there with the code, what do you call it?

@rlkoshak

It’s always possible but not always available. The rule can become too long or complicated to run.

Also true again, it can be assumed that the rule will be too complicated for what I have in mind. Now I have already created the thread that concerns this topic

Optimizing House Shutdown: Room-based Control with Multiple Occupants

Hello everyone, I’m working on optimizing my house shutdown automation and need some advice on implementing a more granular room-based control system, especially with multiple family members. Current Setup: 4 family members (2 adults, 2 children) Each person has three states: “absent”, “sleeping”, or “awake” I have created computed items that combine these states for different zones and floors (e.g., “sleeping_or_absent”, “awake_or_absent”) to manage intermediate states for each area of the …

@rlkoshak

At a high level you write a but of Rules DSL code in a file with the .script extension in the scripts folder and you call it from another rule using callScriot(file name). However, you can’t use imports and you can’t get a return value.

Sounds to to me like JavaScript is the better option, doesn’t it?