As far as I know, wildcards are currently only supported for thing status triggers, for example:
triggers.ThingStatusChangeTrigger('homematic:*')
It would be great if the same could be done for channel event triggers as well. So far, all the channels / events must be listed individually. Example:
triggers: [ // wildcard trigger not supported for channels
triggers.ChannelEventTrigger('homeconnectdirect:dryer:siemens-wt7yh780-xyz:drying_process_finished_event'),
triggers.ChannelEventTrigger('homeconnectdirect:dryer:siemens-wt7yh780-xyz:program_finished_event'),
triggers.ChannelEventTrigger('homeconnectdirect:dryer:siemens-wt7yh780-xyz:condensate_container_full_event'),
triggers.ChannelEventTrigger('homeconnectdirect:dryer:siemens-wt7yh780-xyz:lint_filter_full_event')
],
With a wildcard, this could be simplified to
triggers: [ // wildcard trigger
triggers.ChannelEventTrigger('homeconnectdirect:dryer:*
],
Home appliances and other devices may be able to produce a larger variety of events, and one would generally try to implement a single generic rule for all of those, ideally without listing each trigger separately. So this is what this request is trying to achieve.
Just for completeness:
I am on release 5.1.4, with a standard openhabian environment on a Pi5.
As far as I know, wildcards are currently only supported for thing status triggers, for example:
triggers.ThingStatusChangeTrigger('homematic:*')It would be great if the same could be done for channel event triggers as well. So far, all the channels / events must be listed individually. Example:
With a wildcard, this could be simplified to
Home appliances and other devices may be able to produce a larger variety of events, and one would generally try to implement a single generic rule for all of those, ideally without listing each trigger separately. So this is what this request is trying to achieve.
Just for completeness:
I am on release 5.1.4, with a standard openhabian environment on a Pi5.