Access Official Technical PDF

Share Summary:LinkedInEmail

CCU2 firmware updates illustrate how changes to a building automation controller can affect much more than its user interface. Across the releases documented here, updates add support for devices and integrations, refine control behavior, correct data and display issues, and modify system services. For engineers and integrators maintaining a Homematic installation, reviewing these changes helps identify what an update may mean for configuration, commissioning and ongoing operation.

CCU2 firmware updates expand device and integration support

A recurring theme in the release history is the addition of supported devices. Homematic and Homematic IP additions span heating controls, switching and dimming actuators, blinds and shutters, sensors, remote controls, alarms, and energy measurement. The controller also gained integrations for OSRAM Lightify and Philips Hue, with the Philips Hue integration listed for Bridge 2.0 and later.

This breadth matters because a controller’s device list determines which field devices can be configured, monitored, linked directly, or used in programs. The release notes describe support for functions such as device configuration, operation, direct links, program use and charting for Homematic IP. They also show that support did not always arrive as a complete set: an earlier release explicitly listed groups, device replacement and service messages as unsupported for HmIP at that point.

Integrators should therefore distinguish basic device recognition from support for the workflows a project requires. Before adding a device, check the relevant controller release and device firmware requirements. Some changes require a device to be removed and paired again, or to be unpaired and re-paired, before new parameters or functions become available.

Control logic and configuration behavior

Many changes address the relationship between configuration, controller logic and the status shown in the WebUI. Examples include corrections to heating-group status, transfer of settings to devices, channel parameter handling, program conditions and system-variable use. Other fixes address blind and shutter position reporting, slat adjustment, dimmer parameters and alarm actions.

These details are operationally important. A value that appears correct in a configuration screen is not necessarily sufficient evidence that the field device received it or that the controller will display it consistently after a page reload. Release notes also identify cases where a feature depends on a device’s firmware, a specific channel, or a configuration mode. For example, automatic calibration and motor start-delay compensation for certain shutter actuators are offered only when automatic end-position detection is enabled.

Changes to the ReGaHss logic layer also affect how programs and scripts behave. The documented updates include fixes and additions to mathematical functions, time-module behavior and script execution. The notes distinguish standard, community and legacy logic versions, and warn that the community option could cause scripts to terminate in some circumstances. That makes logic-layer selection a configuration decision, not merely a cosmetic preference.

Diagnostics, data and controller maintenance

CCU2 updates also improve or correct the tools used to observe system behavior. Changes include charting and energy data handling, CSV export, axis scaling, sensor values, service messages and the display of device firmware availability. The release history records defects that could produce incorrect readings or require affected charts to be recreated. It also documents cases where devices needed to be re-paired to correct energy-counter behavior.

For maintenance teams, the implication is to treat monitoring data as part of the update review. Identify whether an installation relies on affected chart types, energy counters, time programs or device status displays. After an update, verify representative values in the WebUI and confirm that scheduled programs and direct links continue to behave as intended.

Controller-level changes matter too. The notes describe an optimized HM-Server boot process, improvements to communication stability, a change to the Web proxy port, and a change in the API behavior of User.getLanguage(): it receives a user ID rather than a username. That API change may matter to custom integrations or scripts that call the method. Network and application dependencies should be checked before deployment.

Security, limitations and update planning

Security-related changes in the history include starting the firewall at system startup, addressing a directory traversal vulnerability, restricting SSH to stronger cipher and MAC choices, and improving session-ID validation. A later release also introduced a startup security notice that highlights risks such as port forwarding. These items reinforce the need to review both firmware and network exposure as part of controller maintenance.

Release notes also preserve known limitations. Examples include Hue and OSRAM Lightify switched outlets being treated as dimming actuators, which restricts switching through the WebUI, and behavior that may be delayed or incomplete for particular devices or channels. A listed workaround for one LAN gateway issue is to assign a fixed IP address; another note says the gateway must be powered before the CCU2 starts for it to be detected. Such caveats can affect commissioning and troubleshooting, even when the main update installs successfully.

A practical update review should include:

  • Checking supported device models and required device firmware.
  • Identifying features that require re-pairing, reconfiguration or chart recreation.
  • Reviewing custom scripts, API calls, network settings and gateway dependencies.
  • Verifying critical programs, heating groups, actuator positions and monitoring data after the change.
  • Documenting known limitations that could affect operator workflows.

Conclusion

The CCU2 release history shows a controller platform evolving through a combination of new device integrations, refinements to automation logic, corrections to status and data handling, and security updates. The practical value of an update depends on the installation: its devices, programs, integrations and network configuration. A structured compatibility review followed by targeted functional checks helps teams understand the impact and maintain predictable operation in Homematic-based building automation systems.

Access Official Technical PDF

About The Author