
Specify the deliverables before work starts
List the project export, as-built drawings, equipment schedule, operation guide and any separate configuration backups in the scope. A KNX project file is not automatically a backup of every camera recorder, router, visualisation server or third-party app. Ask the contractor to identify which separate systems need their own handover material.
Identify the final ETS project export
KNX documentation identifies the .knxproj format for an ETS6 project export. Ask which version and export date correspond to the installation handed over. Have the authorised integrator confirm the appropriate import/version requirements. A PDF point list or a screenshot is useful documentation, but it is not the same item as an editable ETS project export.
Agree passwords and secure transfer
A project may be password protected, and KNX Secure introduces additional credential requirements. Agree who retains the required access information and how it is transferred and stored securely. Do not place passwords, device keys, personal account details or house plans in a public marketing folder or shared project showcase. Confirm recovery responsibilities before depending on a single person’s laptop.
Separate owner accounts from service access
For apps and remote services, document the account holder, administrator role and permitted service access. Where supported, use appropriate separate roles rather than sharing one personal account. Agree how a departing employee or former service provider will lose access without breaking the homeowner’s operation. The available roles depend on the actual platform; do not assume every product provides the same controls.
Record updates after an approved change
Keep a dated handover record when scenes, devices or configurations are changed. Agree who maintains the current backup and whether a new export is included in the maintenance scope. A copy from before the last alteration may not describe the current installation. Label the version and responsible provider so later work starts from the right material.
Demonstrate the agreed handover
Ask for a documented check by an authorised professional that the delivered files and access information match the agreed scope. Record missing items and a resolution date rather than treating a verbal promise as a completed delivery. File delivery does not itself grant a software licence, permission to modify all systems or ownership rights beyond the contract; confirm those arrangements separately.
Your practical checklist
- Named final project export and date
- Separate backups for other configured systems
- Agreed account holders and access roles
- Secure credential-transfer and recovery procedure
- Dated update and acceptance record
Frequently asked questions
Is a PDF device list the same as the KNX project file?
No. A readable schedule and an ETS project export serve different purposes. Identify both in the agreed deliverables.
Should every app use the installer’s personal email?
Discuss the intended account holder and available user roles before setup. Confirm how the homeowner retains suitable access and how service permissions are managed.
Can I publish the project export as proof of installation?
Do not publish private configuration files or credentials as marketing evidence. Use approved, non-sensitive diagrams or a client-permitted case study instead.
Start with a clear project scope
Ask Sedra Electric to define the documentation and access handover in your project scope.
Contact Sedra on WhatsAppPrimary technical sources
Confirm compatibility and support scope with the responsible specialist for the actual devices and design.
