TITLE: HE-UM40CR CO₂ hot water heat pump: status & energy return 403 (4300) — Comfort Cloud HWS uses /device/a2wInfo/ not /deviceStatus/now/

[aussiestorblog]

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?

core-2026.7.4

Describe the issue

Environment
Panasonic Comfort Cloud integration version: 2026.6.7
Bundled aio_panasonic_comfort_cloud: as shipped with 2026.6.7 (running on Python 3.14)
Home Assistant: HAOS
Device: Panasonic HE-UM40CR — CO₂ (R744) heat-pump hot water system (DHW), sold in Australia
Device guid: HE-UM40CR+ (serial redacted)
Managed via Comfort Cloud (accsmart.panasonic.com), not Aquarea Smart Cloud
Problem

The device is enumerated correctly (Got 1 Panasonic devices), but every per-device call fails with 403 {"code":4300,"message":"Have no authority to the request"}, so the device never sets up and the energy coordinator backs off to 600s. This happens on the owner account with terms accepted and the device fully working in the Comfort Cloud app.

Two calls fail identically:

Status — get_status → GET /deviceStatus/now/{guid}
Energy — get_todays_energy → POST deviceHistoryData with {'dataMode': 2, 'date': ...}

Both of these are the air-conditioner endpoints. The HE-UM40CR is a hot-water unit, and the Comfort Cloud backend denies these AC endpoints for it (hence 4300). The existing Aquarea support in the integration doesn't apply either, because this unit is on Comfort Cloud, not Aquarea Smart Cloud.

Evidence from the app (APK 4.3.0, com.panasonic.ACCsmart)

The official app has separate request paths per device family. Decompiled string/class evidence:

GetDeviceStatusRequestAC and GetDeviceStatusRequestPCPF — AC/PCPF status classes
Hot-water / A2W devices use a distinct endpoint family, not /deviceStatus/now/:
GET https://accsmart.panasonic.com/device/a2wInfo/{guid} → returns A2wStatusEntity (tank temp, a2wStatus, setDhwFlg, icon_tank, energyConsumption)
POST https://accsmart.panasonic.com/device/a2wInfoUpdate → control
Confirmed host+path literals present in the app: /device/a2wInfo/, /device/a2wInfoUpdate, /device/a2wRegisterInfo/, alongside the AC ones /deviceStatus/now/, /deviceStatus/control, /deviceHistoryData.

So for a Comfort Cloud hot-water unit the app reads status/energy from /device/a2wInfo/{guid}, while the integration calls the AC /deviceStatus/now/{guid} and deviceHistoryData, which the backend rejects with 4300 for this device class.

Suggested fix

Route Comfort Cloud hot-water / A2W device types to /device/a2wInfo/{guid} (read) and /device/a2wInfoUpdate (write) instead of the AC deviceStatus/deviceHistoryData endpoints, and parse the A2wStatusEntity (tank temperature, operating state, energyConsumption) into the existing water-heater entity. Device-type detection can key off the model/guid prefix or the deviceType returned by /device/deviceList.

Logs (redacted)
ERROR [aio_panasonic_comfort_cloud.helpers] Error in get_status
Expected status code '200' but received '403'
Response body: {"code":4300,"message":"Have no authority to the request"}
WARNING [aio_panasonic_comfort_cloud.apiclient] Failed to get live status for device HE-UM40CR+ switching to cached data.
...
ERROR [aio_panasonic_comfort_cloud.helpers] Error in get_todays_energy
Expected status code '200' but received '403'
Payload: {'deviceGuid': 'HE-UM40CR+', 'dataMode': 2, 'date': '20260725', 'osTimezone': '+10:00'}
Response body: {"code":4300,"message":"Have no authority to the request"}
WARNING [custom_components.panasonic_cc.panasonic.coordinator] 46 HWS Energy API failure 1/5 — Access Denied ... polling interval increased to 600s

Full traceback shows the failing call chain: coordinator.get_device → apiclient.get_device → apiclient._get_device_status → execute_get(self._get_device_status_now_url(guid), "get_status", 200) → 403/4300.

I'm happy to test a patch against this device and provide diagnostics.

Error/Debug Logs

[dennismdejong]

Upstream issue tracking this fix: sockless-coding/aio-panasonic-comfort-cloud#14 (HWS endpoint /device/a2wInfo/)\n\nThe integration documents the limitation and points to the upstream fix in PR #485.

[sockless-coding]

@aussiestorblog the Panasonic CC App is a mess of different devices and API call paths...
I don't have access to one of these devices, but I can see if I can merge some of the PRs from @dennismdejong if they are valid... I got flooded by issues and PRs and they seem AI generated (all published the same time).

[aussiestorblog]

Thanks @sockless-coding I am more than happy to run any diagnostic command or do testing.

[sockless-coding]

@aussiestorblog if you clone the https://github.com/sockless-coding/aio-panasonic-comfort-cloud repo
Edit the example.py to enable debug logging logging.basicConfig(level=logging.INFO) -> logging.basicConfig(level=logging.DEBUG)
You can probally comment out the Example: Turn on a device and set temperature section since it will throw an error on your device.
And post the json so I can see how the device response looks

[aussiestorblog]

Thanks @sockless-coding

I am using Claude to help me out.

The HE-UM40CR reports deviceType: "11", a hot-water/HWS class the library has no branch for. It falls through to the air-conditioner code path, so per-device calls to /deviceStatus/now/{guid} and deviceHistoryData (dataMode 2) return 403 {"code":4300,"message":"Have no authority to the request"}, the device never sets up, and the energy coordinator backs off to 600s.

Running the debug py against this account, the GET /device/group call returns full tank state inline for this device (guid + serial redacted):

json
{
"deviceGuid": "HE-UM40CR+REDACTED",
"deviceType": "11",
"deviceName": "46 HWS",
"deviceModuleNumber": "HE-UM40CR",
"permission": 3,
"parameters": {
"hpuOperationStatus": 0,
"operationMode": 0,
"boostMode": 0,
"tankTemperature": 60
}
}

I can confirm the tank is currently at 60 degree with boost mode turned off.

So for deviceType 11 the tank temperature and operating state come back in the group payload directly. The AC-style deviceStatus/now / deviceHistoryData calls that the library makes afterwards are what 403 — they don't apply to this device class.

Parameter schema observed for deviceType 11 (HWS)
tankTemperature — current tank temp (°C); read 60 here.
hpuOperationStatus — heat-pump unit on/off state
operationMode — operating mode
boostMode — boost on/off
From the Comfort Cloud app (APK 4.3.0) for reference

Hot-water/A2W devices in the app use a distinct endpoint family, not the AC ones:

GET /device/a2wInfo/{guid} (status)
POST /device/a2wInfoUpdate (control) (also present: /device/a2wRegisterInfo/). The OAuth scope requested by the app includes a2w.control, confirming the A2W device family is a first-class path.
Suggested fix

Add a deviceType 11 (HWS) branch that:

Reads state from the parameters block already returned by /device/group (tankTemperature, hpuOperationStatus, operationMode, boostMode), rather than calling the AC deviceStatus/now / deviceHistoryData endpoints that 403 for this class.
For control, targets the A2W endpoints (/device/a2wInfoUpdate).
Maps this to the existing water-heater entity.
Failing calls (from HA, redacted)
Error in get_status — 403 {"code":4300,"message":"Have no authority to the request"}
Error in get_todays_energy — payload {'deviceGuid': 'HE-UM40CR+REDACTED', 'dataMode': 2, 'date': '...'} — 403 {"code":4300,...}

Happy to test a patch and provide further diagnostics against this device.

[sockless-coding]

@aussiestorblog lets try this I assume you don't have any other devices.
In the file custom_components\panasonic_cc\aquarea\__init__.py and the method async_setup_aquarea remove the following section:

    if not panasonic_api.has_unknown_devices:
        hass.data[DOMAIN][AQUAREA_COORDINATORS] = []
        return []

And in the file custom_components\panasonic_cc\panasonic\__init__.py and the method async_setup_panasonic return early by adding

return data_coordinators, energy_coordinators

to line 68 or so, I don't know if this will break the integration but if it works I can add a special case for device type 11 so it doesn't enter the normal hvac path.

[aussiestorblog]

Getting this error:

Logger: homeassistant.components.climate
Source: helpers/entity_platform.py:500
Integration: Climate (documentation, issues)
First occurred: 18:49:24 (2 occurrences)
Last logged: 18:49:34

Error while setting up panasonic_cc platform for climate: 'data_coordinators'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 500, in _async_setup_platform
await asyncio.shield(awaitable)
File "/config/custom_components/panasonic_cc/climate.py", line 23, in async_setup_entry
await panasonic_setup(hass, entry, async_add_entities)
File "/config/custom_components/panasonic_cc/panasonic/climate.py", line 472, in async_setup_entry
data_coordinators = hass.data[DOMAIN][DATA_COORDINATORS]
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
KeyError: 'data_coordinators'

[sockless-coding]

@aussiestorblog ah I see the return early needs to be changed to

    hass.data[DOMAIN][DATA_COORDINATORS] = data_coordinators
    hass.data[DOMAIN][ENERGY_COORDINATORS] = energy_coordinators
    return data_coordinators, energy_coordinators

So the data variables are set to empty lists

[aussiestorblog]

Slightly different error now:

2026-07-29 19:12:31.494 ERROR (MainThread) [homeassistant.components.number] Error while setting up panasonic_cc platform for number: 'data_coordinators'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 500, in _async_setup_platform
await asyncio.shield(awaitable)
File "/config/custom_components/panasonic_cc/number.py", line 18, in async_setup_entry
await panasonic_setup(hass, entry, async_add_entities)
File "/config/custom_components/panasonic_cc/panasonic/number.py", line 58, in async_setup_entry
data_coordinators: list[PanasonicDeviceCoordinator] = hass.data[DOMAIN][DATA_COORDINATORS]
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
KeyError: 'data_coordinators'

[sockless-coding]

Hmm,

Try removing the line await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS) from the method async_setup_entry in custom_components\panasonic_cc\panasonic\__init__.py.

I'm not sure why it keeps trying to initialize the panasonic entities when the coordinators are empty

[aussiestorblog]

I tried that but now get this:

Log details (ERROR)
Logger: homeassistant.components.climate
Source: helpers/entity_platform.py:500
Integration: Climate (documentation, issues)
First occurred: 29 July 2026 at 18:49:24 (6 occurrences)
Last logged: 10:57:27

Error while setting up panasonic_cc platform for climate: 'data_coordinators'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 500, in _async_setup_platform
await asyncio.shield(awaitable)
File "/config/custom_components/panasonic_cc/climate.py", line 23, in async_setup_entry
await panasonic_setup(hass, entry, async_add_entities)
File "/config/custom_components/panasonic_cc/panasonic/climate.py", line 472, in async_setup_entry
data_coordinators = hass.data[DOMAIN][DATA_COORDINATORS]
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
KeyError: 'data_coordinators'

[sockless-coding]

Are you sure the async_setup_panasonic methods in custom_components\panasonic_cc\panasonic\__init__.py sets

hass.data[DOMAIN][DATA_COORDINATORS] = data_coordinators
hass.data[DOMAIN][ENERGY_COORDINATORS] = energy_coordinators

Before returning?

You can just add

hass.data[DOMAIN][DATA_COORDINATORS] = []
hass.data[DOMAIN][ENERGY_COORDINATORS] = []

As the first lines of that method to make sure