As a long-time user of Home Assistant, I’ve always been impressed by its ability to integrate with various smart home ecosystems. Recently, I upgraded my KNX installation to the latest HA version (2024.5.5) and encountered an unexpected challenge with my climate sensors. While my setup had been working flawlessly for years, the upgrade introduced a hiccup in how my KNX sensors reported temperatures.
The issue revolved around the target_temperature_state_address attribute in the KNX integration. Previously, this attribute was optional, but the update made it mandatory, which threw my setup into disarray. My climate sensors stopped displaying current temperatures, which was a significant setback for my heating automation logic.
After some research, I discovered that the KNX integration had changed around version 2024.2, and the attribute was no longer optional. This meant I needed to adjust my configuration to include the target_temperature_state_address. The challenge was finding the right group addresses (GAs) to map this attribute to.
Through trial and error, I realized that I needed to reserve unused GAs for target_temperature_state_address to ensure the sensor functionality remained intact. This adjustment allowed my heating automation to function as intended, with the valve opening and closing based on the temperature logic I had built.
Reflecting on this experience, it’s a testament to how adaptable and powerful HA is, even when dealing with legacy systems like KNX. The community support and documentation were invaluable in helping me navigate this challenge. If anyone else is facing similar issues, I’d recommend thoroughly reviewing your KNX configuration and ensuring all mandatory attributes are correctly mapped. Happy automating! ![]()