* Add `knx.telegram` integration specific trigger
* Move implementation to trigger.py, use it from device_trigger
* test device_trigger
* test trigger.py
* Add "incoming" and "outgoing" and handle legacy device triggers
* work with mixed group address styles
* improve coverage
* Add no-op option
* apply changed linting rules
* Don't distinguish legacy device triggers from new ones
that's now supported since frontend has fixed default values of extra_fields
* review suggestion: reuse trigger schema for device trigger extra fields
* cleanup for readability
* Remove no-op option
Co-authored-by: Sid <27780930+autinerd@users.noreply.github.com>
Co-authored-by: Marc Mueller <30130371+cdce8p@users.noreply.github.com>
Co-authored-by: J. Nick Koston <nick@koston.org>
* Fix menu in knx config flow
* Update tests
* Fix strings.json
* Rename new menu steps for readabiltiy
---------
Co-authored-by: Matthias Alphart <farmio@alphart.net>
* feat(knxproject-explore): providing knxproject via websocket, also xknxproject version in info mesage
* feat(knxproject-explore): adding test case
* reverted back adding of xknxproject version
* fix(): Enriching get project test case to check against FIXTURE
* feat(knxproject-explore): providing knxproject via websocket, also xknxproject version in info mesage
* feat(knxproject-explore): adding test case
* reverted back adding of xknxproject version
* fix(): Enriching get project test case to check against FIXTURE
* remove impossible test
IndividualAddress telegrams are not processed by xknx.telegram_queue
* Use Telegrams helper class for group monitor messages
* Store 50 telegrams in deque for group monitor
* Send recent telegrams at once on connection of group monitor
* Update KNX-frontend to support group monitor prepopulation
* telegram device trigger initial
* add Telegrams helper class
to parse and convert Telegram only once instead of once per device trigger
* translation
* label for extra_field
* test device trigger
* test trigger callback removal
* rename extra_field key to same name as used in trigger
* typo
* Add KNX panel
* provide project data for the panel group monitor
* upload and delete project from panel
* test project store
* more tests
* finish tests
* use integers for DPTBinary payload monitor display
* add project to diagnostics
* require new frontend version
* update knx_frontend
* review suggestions
* update xknxproject to 3.1.0
---------
Co-authored-by: Marvin Wichmann <me@marvin-wichmann.de>
