Panasonic CC HACS addon incompatible with 2026.1.1, had to rollback to HA Core 2025.12.5

[carlosresu]

Checklist

• I have verified that the account and device works in the Comfort Cloud App.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This issue is not a duplicate issue of currently previous issues..

What version of Home Assistant Core?

2026.1.1

Describe the issue

No longer works with HA Core 2026.1.1

Error/Debug Logs

[lassej01]

Im on the same verson, and it's works for me.

[Auka84]

It's working also for me

[carlosresu]

here's what claude said:

Based on my research, I've identified the most likely cause of your panasonic_cc integration breaking in Home Assistant 2026.1.1.

Root Cause: Deprecated Climate Constants

The panasonic_cc integration was using deprecated climate constants that were finally removed/enforced in HA 2026.1. This was documented in Issue #190 on the repository back in June 2024:

Deprecated constants used by panasonic_cc:

Old Constant | Should Be Replaced With -- | -- HVAC_MODE_OFF | HVACMode.OFF SUPPORT_TARGET_TEMPERATURE | ClimateEntityFeature.TARGET_TEMPERATURE SUPPORT_FAN_MODE | ClimateEntityFeature.FAN_MODE SUPPORT_SWING_MODE | ClimateEntityFeature.SWING_MODE SUPPORT_PRESET_MODE | ClimateEntityFeature.PRESET_MODE

These constants were originally scheduled for removal in HA Core 2025.1, but the actual enforcement appears to have occurred in 2026.1/2026.1.1.

Why 2025.12.5 Works

In HA 2025.12.5, these deprecated constants were still accepted (likely with warnings in your logs). In 2026.1.1, they appear to have been fully removed or stricter validation was applied, causing the integration to fail.

Evidence in 2026.1 Release

The 2026.1 changelog includes a beta fix: "Fix hvac_mode validation in climate.hvac_mode_changed trigger" (#160364), which suggests climate entity validation became stricter in this release.

What You Can Do

1. Report/check the issue: Check if there's already an open issue about 2026.1 compatibility on the panasonic_cc GitHub
2. Temporary workaround: Continue using HA 2025.12.5 until the integration is updated
3. Wait for an update: The integration maintainer (@sockless-coding) will need to update the code to use the modern HVACMode enum and ClimateEntityFeature flags
4. Check for a fork: Some users may have created a patched version (similar to how climate_group_HA2025 was created for another integration with the same issue)

The latest release of panasonic_cc is 2025.5.0 (May 2025), which predates the enforcement of these deprecations. The maintainer will need to release an update that replaces all the deprecated constants with their modern equivalents.

[Echoes2207]

Also not working for me. But I just installed the integration and have no Idea if it would have worked with earlier versions. I get an 500 internal server error. But the login seems to work out.

[carlosresu]

Same, that’s what I get. Internal server error 500, on 2026.1.1. I haven’t tried 2026.1.2. I’m on 2025.12.5 and it’s working again. From: Echoes2207 ***@***.***> Date: Saturday, January 17, 2026 at 3:54 PM To: sockless-coding/panasonic_cc ***@***.***> Cc: Carlos Miguel Resurreccion ***@***.***>, Author ***@***.***> Subject: Re: [sockless-coding/panasonic_cc] Panasonic CC HACS addon incompatible with 2026.1.1, had to rollback to HA Core 2025.12.5 (Issue #422) [Image removed by sender.]Echoes2207 left a comment (sockless-coding/panasonic_cc#422)<#422 (comment)> Also not working for me. But I just installed the integration and have no Idea if it would have worked with earlier versions. I get an 500 internal server error. But the login seems to work out. — Reply to this email directly, view it on GitHub<#422 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BJOPULARUOZ2PSGPJVF2OTT4HHTEDAVCNFSM6AAAAACRPZ7Q4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONRSHA3DSOBZGU>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Echoes2207]

I’m on 2026.1.2 and it’s still not working. I don’t want to downgrade because of one integration. Hopefully it will get fixed soon :)

[Auka84]

Strange, it's working for me but all data where not available, i just click on "fetch lastest ..." for each and all is back

[carlosresu]

Installation method
Home Assistant OS
Core
2026.1.2
Supervisor
2026.01.1
Operating System
17.0
Frontend
20260107.2
Companion app
2026.1.1 (2026.1652)

Works now with these, but clicking the integration in the devices UI still says error 500