Skip to content
Website
🧱 CFC 238KNX home automation: topology, addressing and parameter settingChapter 9 of 10 in the section

What the bus records: occupancy traces, retention period and notice

This chapter teaches you how to configure KNX gateways and supervisors in rented residential property without infringing the law. You will know how to parameterise presence telegram retention, purge diagnostic logs after commissioning and provide the technical details required for written notice to the occupant.

Key takeaways

  • The LPD requires limiting the collection of occupancy traces to strict functional necessity.
  • A KNX presence detector transmits telegrams that can be exploited as personal data through cross-referencing.
  • The retention period parameterised on the local server must be reduced to the strict minimum.
  • Written notice to the occupant specifies the purpose of processing and the identity of the legally responsible party.

Technical limitation of telegrams and occupancy logging on the bus

In a residential KNX installation, every state change generates a standardised telegram on the twisted pair. When a passive infrared presence detector switches lighting in an entrance hall or a magnetic door contact signals the opening of the apartment entrance door, the bus broadcasts a telegram containing the group address, the binary value and the routing flag. In autonomous line-to-line operation, these frames circulate in the RAM of couplers without physical persistence. As soon as an IP coupler, a communication gateway or a supervisory server is connected to the building's local network, these events can be captured, timestamped using the DPT 19.001 format and stored in the form of a chronological database.

In rented accommodation, the operator or property owner has no business knowing the precise return times, nocturnal movements or daily rhythms of the residents. Continuous occupancy logging presents the risk of building an accurate profile of the residents. The telematics technician must therefore intervene at the software configuration level in ETS and on the home automation server's management interface to restrict systematic logging.

  • Deactivation of the logging function on internal presence group addresses.
  • Removal of timestamping for lighting and blind controls within local databases.
  • Maintenance of bus communication in point-to-point mode without export to text log files.
  • Reservation of extended logging solely for technical alarm frames or hardware malfunctions.

The principle of technical proportionality leads to distinguishing real-time automation from retrospective storage. To regulate ventilation or switch thermal comfort levels, the controller only requires the current state: 'occupied' or 'unoccupied'. Keeping a minute-by-minute history of these transitions in a persistent file constitutes excessive collection that cannot be justified simply for operating convenience.

Parameterised retention period and protocol for written notice to the occupant

When a KNX IP gateway includes an event logger for preventive maintenance, the technician must configure a strictly delimited, parameterised retention period. Recent supervisory controllers feature FIFO circular buffers. If technical monitoring is required for diagnosing intermittent incidents on bus devices, maximum retention of presence frames must not exceed 24 to 48 hours. At the end of this sliding window, the oldest telegrams are overwritten automatically without any possibility of restoration.

Configuring logs according to operational purpose
Bus data typePermissible purposeRecommended retention periodConfiguration action
Presence and motion detectionReal-time lighting management0 days (no logging)Disable logging in the supervisor
Access traces or door contactTechnical building security24 hours maximumConfigure a short circular buffer
Actuator faults or bus outagesTechnical network maintenance30 daysIsolate in a dedicated system log
ETS commissioning telegramsDiagnostics during construction site work0 days after handoverPurge the group monitor

Upon handover of the installations, the telematics technician provides site management with a technical file including the operating manual for the automation system. This document serves as the basis for the landlord to provide written notice to the occupant. Art. 19 LPD specifies that the controller must inform the data subject adequately, providing at least their identity and contact details, the purpose of the processing and, where applicable, the recipients.

  1. Purging of commissioning toolsCompletely delete ETS group monitor capture files and reset the memory buffers of IP communication interfaces before leaving the construction site.
  2. Locking of remote maintenance accessChange default manufacturer passwords on IP gateways, disable unsolicited remote access and terminate telemetry uploads to unsecured third-party servers.
  3. Handover of the technical data-processing sheetDraft a clear appendix detailing the list of connected sensors, the absence of continuous named tracking and the automatic erasure parameters configured in the installation.

Gateway configuration and restriction of supervisory traffic

In rented accommodation equipped with KNX, presence detectors and push-buttons continuously broadcast telegrams across the twisted pair. Activating a lighting group or sending a 1-bit telegram upon motion detection is a standard technical event, but recording it chronologically creates an accurate record of the occupant's daily habits. The boundary between convenience automation and unlawful surveillance depends directly on the configuration of communication interfaces and apartment servers.

Under art. 7 LPD, the controller must implement technical and organisational measures from the design stage of processing and guarantee, through appropriate default settings, that processing is limited to the minimum required for the purpose. For the telematics technician, this data protection by design requirement entails systematically disabling log-recording functions in line couplers and KNX/IP routers. If an IP gateway is connected to the building network for maintenance or remote management, it must not relay any presence status telegrams to a building concentrator. The filter table of the apartment coupler must block all internal groups linked to volumetric detectors and interior lighting controls.

Event flow parameterisation and recommended retention periods
KNX sourceTechnical purposeBus processingPermissible retention
PIR detector (DPT 1.001)Walkway lighting and switch-offDirect telegram to switching actuatorNo logging (0 seconds)
Magnetic window contactThermostat setback to standbyFlag sent to dedicated heating groupInstantaneous state only, no history
MID energy meter (M-Bus / KNX)Individual metering of ancillary costsCumulative index reading for property managementArchived monthly value (without hourly curve)
Common weather stationWind protection for external blindsGeneral broadcast on the main lineNo linked personal data

Operating file, handover to property management and tenant information sheet

Art. 6 LPD stipulates that all processing of personal data must be lawful, in accordance with the principles of good faith and proportionality, with collection for specific and recognisable purposes, and that data must be destroyed or anonymised as soon as they are no longer required. Within rented property stock, property management or the building owner bears responsibility for processing, but the telematics technician is responsible for the technical implementation of these principles. If the installation retains profiling data without the resident's knowledge, the compliance of the installation is directly compromised.

To hand over the installation rigorously, the telecommunications and network company must include a dedicated section on data management in the operating file submitted to the client. This document outlines the software architecture: absence of undeclared remote servers, absence of continuous occupancy logging and strict separation between apartment buses and the common building automation and control system (BACS) network.

  1. Purging of commissioning memoryPrior to key handover, completely clear diagnostic logs from ETS software, erase test buffer files on IP gateways and restore local maintenance passwords.
  2. Locking of remote maintenance accessDisable unsolicited permanent remote access. Any access for subsequent troubleshooting must require manual confirmation from inside the dwelling or a temporary software key.
  3. Drafting of the occupant information sheetDraft a concise leaflet intended for the tenancy agreement. The document outlines the presence of sensors, their exclusive function for local regulation (lighting, thermal comfort) and the complete absence of tracking of entries or exits.
  4. Signing of the technical handover protocolHave site management and the landlord's representative countersign the technical sheet certifying that occupancy recording functions have been disabled at both hardware and software levels.
  • Verification of the absence of an active predictive profiling module (algorithms learning occupancy habits).
  • Inspection of physical or logical isolation (dedicated VLAN) between the tenant's multimedia IP network and the technical home automation subnetwork.
  • Handover of password-protected ETS project backups (.knxproj) solely to the person designated by the building owner.

Disputes, memory purges and bringing installations into compliance

On a rented housing construction site, disputes often arise during key handover or following a complaint from a tenant discovering a timestamped passage history on their wall interface or on the property management agency's app. When an occupant challenges the traceability of their comings and goings, configuration liability falls squarely on the technician. Under art. 6 LPD, all processing of personal data must be lawful, in accordance with the principles of good faith and proportionality, and data must be destroyed or anonymised as soon as they are no longer required.

If the landlord or property management demanded occupancy logging without complying with the duty to inform set out in LPD, the installer must intervene on the local server to disable continuous recording. The network electrician connects to the IP gateway via ETS or the supervisor's management interface to reconfigure communication objects. Lighting or blind actuation telegrams must then be decoupled from the circular archive tables.

  1. Audit of log tablesExtract the ETS project and the residential supervisor configuration. Check SQL databases or internal flash memory to identify all timestamped measurement points linked to motion detectors and access controls.
  2. Purging and limitation of circular memoryPerform a full purge of nominative switching logs. Configure buffer memory to circular mode with automatic overwriting of technical data within 24 to 48 hours, a threshold sufficient for network diagnostics.
  3. Deactivation of logging objectsDelete diagnostic group addresses sent to the property management agency's remote servers. Maintain bus operation locally without persistence of presence states.
  4. Updating of operating documentationDraft an addendum to the technical operating file certifying the absence of personal data recording, and document the reset of gateways for the attention of the owner.

Frequently asked questions

Can a KNX motion detector store a tenant's movement time?

The device itself has no internal clock or event memory. It only transmits a binary telegram across the bus upon motion. However, if this telegram is addressed to an area controller or supervisor equipped with a system clock, that third-party device can log the exact time of detection. Retention therefore depends on the concentrator's settings.

What retention period should be parameterised for bus technical troubleshooting?

For diagnosing possible malfunctions or telegram collisions on the line, a log of a few hours up to 48 hours is more than sufficient. Beyond that, continuous recording of presence signals becomes disproportionate in a private dwelling. Buffer memory must overwrite the oldest events using a circular buffer (FIFO) principle.

Can property management demand access to presence states to check occupancy?

No. Monitoring the lifestyle habits or return times of a tenant infringes their privacy. The installer must refuse to route presence group addresses to remote management gateways accessible to the landlord. Only aggregated or strictly technical data, such as technical alarms or fault states, may be transmitted.

How should the written notice provided to the dwelling's occupant be formalised?

The electrician includes a simplified guide explaining the role of the KNX sensors in the installation documentation. This document specifies that the detectors control only lighting or local regulation, that no nominative time profile is stored, and that the system does not record continuously. The sheet is handed over to the client for forwarding to tenants.

Texts and standards cited

  • LPD art. 6principles: all processing of personal data must be lawful, in accordance with the principles of good faith and proportionality; collection for specific and recognisable purposes; data destroyed or anonymised as soon as they are no longer required; consent is valid if given freely and informed, and express for sensitive personal data.
  • LPDduty to inform when collecting personal data: the controller informs the data subject adequately, providing at least their identity and contact details, the purpose of the processing and, where applicable, the recipients.

In the same section