Bug in RM with custom attributes?

Hi All
i have been playing with a driver for an alarm interface and cannot seem to get RM to trigger on a custom attribute if i select changed in the trigger.

To test this i created the cut down driver below

metadata {
	definition (name: "Attribute Test", namespace: "entire", author: "Entire") {
    capability "Presence Sensor"
    
	attribute "alarmState", "enum", ["unset", "set", "active", "confirmed"]
    
    command "alarmSet"
    command "alarmUnset"
    command "alarmActive"
    command "alarmConfirmed"
  }
}


def alarmSet() {
  log.info "Alarm now set"
  sendEvent(name: "alarmState", value: "set", descriptionText: "Alarm is set")
}

def alarmUnset() {
  log.info "Alarm now unset"
  sendEvent(name: "alarmState", value: "unset", descriptionText: "Alarm is unset")
}

def alarmActive() {
  log.info "Alarm now active"
  sendEvent(name: "alarmState", value: "active", descriptionText: "Alarm is active")
}

def alarmConfirmed() {
  log.info "Alarm now set"
  sendEvent(name: "alarmState", value: "confirmed", descriptionText: "Alarm is confirmed")
}

created a device with this driver called "Attribute Test" and the following rule

I can then set the alarmState to any of the 4 values but it never triggers the rule.
If i change the rule to trigger from the individually values then it triggers correctly.

Has anyone seen this before, is there a bug in the way it handles custom attributes or am i doing something wrong ?

Edit: sorry forgot say i am using version 2.1.6.118

Cheers

There was a bug with this. Update to 2.1.7 and see if that fixes your problem.

Yes that fixes it, excellent Cheers :+1:

Just another quick question, i had to put a dummy capability into the driver as without any of the predefined capabilities it could not be selected in RM for a custom attribute, is that right ?

Cheers

No, it doesn't need a capability, just an attribute. We usually put in Sensor or Actuator.

That worked :+1:

Cheers