You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there @Julius2342, @farmio, @marvin-w, mind taking a look at this feedback as it has been labeled with an integration (knx) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of knx can trigger bot actions by commenting:
@home-assistant close Closes the feedback.
@home-assistant rename Awesome new title Renames the feedback.
@home-assistant reopen Reopen the feedback.
@home-assistant unassign knx Removes the current integration label and assignees on the feedback, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.
Hi 👋!
Thanks for pointing this out!
How can one export a keyring for use with Secure Routing and DataSecure in ETS 6? Afair in ETS 5 the backbone key wasn't included in the keyfile when not exporting everything (eg. a single tunnel).
Not sure how this works in ETS 6 as I currently don't have a license for it.
Feedback
https://deploy-preview-22203--home-assistant-docs.netlify.app/integrations/knx/#knx-secure states that the knykeys file should be exported from the project security details.
For ETS6, this is wrong. The knxkeys file must be created by the "Export Interface Information" command on the IP Tunnel that shall be used for HA.
URL
https://www.home-assistant.io/integrations/knx/
Version
2022.3.8
Additional information
The text was updated successfully, but these errors were encountered: