"Member of" does not work in OH 2.1

[Michal_Szymanski]

Hi,
I tried to rewrite my old rule to use constrution “Member of”. Such construction was presented in

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…

I created such rule:

rule “Low_battery_alarm”
when
Member of gLowBattery changed
then
logInfo( “FILE”, “Low_battery_alarm: -START-”)
…

I’ve got such error:

2018-08-13 23:51:56.129 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model ‘General.rules’ has errors, therefore ignoring it: [8,3]: no viable alternative at input ‘Member’

Does it work only in new OH versions?

Michal Szymanski

[mstormi (Markus Storm)]

I don’t see “Member” to be a valid trigger point according to OH2 docs. @rlkoshak please share your knowledge if you think this is supposed to work.

Now while I don’t know your application, maybe a standard ‘when Item gLowBattery changed’ will also do what you want it to (as changes to group members will change the group’s status, too).

[danielwalters86 (Daniel Walters)]

As far as I know “Member of” trigger was only introduced in OH2.3

[Michal_Szymanski]

So far I had:

rule "Low_battery_alarm"
	when 
		Item gLowBattery received update 
	then
		val sensor = gLowBattery. members.filter[sensor | sensor.lastUpdate != null].sortBy[lastUpdate].last

but using "Member of " looks more elegant

Michal

[sihui]

@danielwalters86

As far as I know “Member of” trigger was only introduced in OH2.3

Features for Rules that work with Groups

Introduction This post provides an overview of two features that have been added to openHAB recently to make it easier to write rules that work with groups of items. These features only apply to rules defined in .rules files (also know as DSL Rules), and not any other types of rules/scripts such as those for the Experimental Rule Engine or JSR223 Scripting. The following sections will provide examples of the usage of each feature. These examples will be based on the items shown here. Group All…

Availability

“Member of” is an openHAB 2.3 feature. It is not available in any current release build. It is available in snapshot builds starting with openHAB 2.3.0 Build #1212.

[rossko57]

@Michal_Szymanski

but using "Member of " looks more elegant

I resisted moving from OH1 to OH2 for various reasons, but the introduction of that method was the clincher for me. I’ve rewritten about three quarters of my rules to take advantage of it.

As 2.3 is currently stable release, go for the update.

[Michal_Szymanski]

I’ve spent weekend to migrate to 2.3 but I’m block by MCP23017 binding , it has some bugs and I wait for fix. I’ve notice also many errors during boot process e.g I have hundred error logs that persistence is not registered but after several minutes persistence works without any problem

BTW It is pity that OH release version so seldom, ok you can use snapshot version but it is little dangerous for serious installation. They should release major version once a severel month but patches every several weeks.

Michal Szymanski

[rlkoshak (Rich Koshak)]

@mstormi

@rlkoshak please share your knowledge if you think this is supposed to work.

@Michal_Szymanski

Does it work only in new OH versions?

It was added in 2.3 and will not work in 2.1. Member of and triggeringItem do not exist in 2.1.

I don’t think I’ve explicitly stated it anywhere but the DPs are assumed to work with the latest version of OH. So they should work with whatever was out at the date/time the DP was last edited. I should probably add a little note with the version the DP was written for/last updated for.

@mstormi

I don’t see “Member” to be a valid trigger point according to OH2 docs

Has that still not yet been added to the docs? Grumble. We need to change that. I just submitted a PR.