Closed derandiunddasbo closed 6 years ago
From the documentation:
If
fire_event
is setfire_event_filter
has to be specified.fire_event_filter
defines a list of patterns for filtering KNX addresses. Only telegrams which match this pattern are sent to the HOme [sic!] Assistant event bus.
Oops, thanks. I should actually read the documentation. Erm... ;-)
Home Assistant release with the issue: 0.68.1
Last working Home Assistant release (if known): not known
Operating environment (Hass.io/Docker/Windows/etc.): Docker @ Synology
Component/platform: https://www.home-assistant.io/components/knx/
Description of problem: The KNX component documentation states, that the
fire_event_filter
configuration is optional. But adding onlyfire_event
to the config, omittingfire_event_filter
results in a config error:Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information: It should either be made more clear in the documentation, that
fire_event_filter
is no longer optional, iffire_event
is used, orfire_event_filter
should become truly optional, i.e. default to["*/*/*"]
if omitted in the config.