Rules for latching relays group

[rossko57]

@julesx81

Nope, after your mod i can’t control single pulse.

Don’t know what that means, cannot see what you are doing.

@julesx81

logInfo(“GF_lights_off”,“Rule started.”) gLight?.members.filter[a|a.state==OPEN].forEach[s|

I thought you wanted to control members of group like GF_Dining ?
Why would you not use GF_Dining?.members.filter[...

[julesx81 (Lorenzo S.)]

@rossko57

Don’t know what that means, cannot see what you are doing.

GF_Dining is only a room, i would fiter all lights on floor GF , i tried with GF?.members.filter , but members are only the rooms.

[rossko57]

@julesx81

i tried with GF?.members.filter

Ah right, nested groups.
GF?.allMembers.filter...
will reach through the layers.

Design Pattern: Working with Groups in Rules

Please see Design Pattern: What is a Design Pattern and How Do I Use Them for how to read and use DPs. Problem Statement Often one finds a number of Rules that are very similar and that all work on similar Items resulting in a lot of duplicated code. One way to solve this problem is through the use of Groups. Concept [image] This DP is not a standard DP in that it provides a single concrete template to follow to solve a specific problem. Instead this DP is more of a grand exploration of some …

[julesx81 (Lorenzo S.)]

I solved simple with string compare

rule "GF lights off"
when
    Item GF_lights_off received command ON
then
    logInfo("GF lights off","Rule started.")
    gLight?.members.filter[a|a.state==OPEN].forEach[s|
        logInfo("GF_pulse","Processing Item {} ({})",s.name,s.state)
		var nameOfLight = s.name.split("_")
		var nameofPulse = nameOfLight.get(0) + "_" + nameOfLight.get(1) + "_Pulse"
		            if ( nameOfLight.get(0) == "GF") {
		           sendCommand(nameofPulse, "OFF") } else {}

        Thread::sleep(300) 
    ]
    logInfo("GF lights off","Rule ends.")
	sendCommand(GF_lights_off, OFF)
end