HWS-only accounts are rejected by config flow as “No devices found”

[123Orion123]

Checklist

• The account and device work in the official Panasonic Comfort Cloud app.
• This report covers one issue.
• I searched the existing issues and pull requests for HWS, no_devices, has_hws_devices, HE-UM40CR and HE-UM60CR.

Description

Thank you for adding standalone HWS support in 2026.8.3.

While testing the new support with an HE-UM60CR on an account that appears to contain only the standalone hot-water system and no conventional Panasonic air conditioners, the configuration flow reports:

No devices found

Authentication succeeds and ApiClient.start_session() completes without an observed authentication, MFA, HTTP, JSON or dependency exception, but no config entry is created.

This appears to be a small device-presence-check oversight in the new HWS support.

Environment

• Home Assistant: 2026.8.2
• HACS: 2.0.5
• panasonic_cc: 2026.8.3
• aio-panasonic-comfort-cloud: 2026.8.4
• Device: Panasonic HE-UM60CR standalone CO₂ hot-water system
• Account configuration: standalone HWS, with no known conventional Panasonic AC devices

Steps to reproduce

1. Use a Panasonic Comfort Cloud account containing a standalone HWS device and no conventional AC devices.
2. Install panasonic_cc 2026.8.3.
3. Add the Panasonic Comfort Cloud integration.
4. Authenticate successfully.
5. Observe “No devices found”.
6. Confirm that no config entry is created.

The HE-UM60CR remains visible and functional in the official Comfort Cloud app under the same account.

Expected behaviour

A session containing a recognized standalone HWS should pass config-flow validation and create a config entry, allowing the HWS setup path to run.

Actual behaviour

The config flow treats the normal devices list as empty and returns no_devices, even when the API has separately classified HWS devices.

Root-cause analysis

In the current config flow, _async_try_login() performs this check:

devices = api.get_devices()

if not devices and not api.has_unknown_devices:
    errors["base"] = "no_devices"

Source:

https://github.com/sockless-coding/panasonic_cc/blob/master/custom_components/panasonic_cc/config_flow.py#L119-L136

aio-panasonic-comfort-cloud treats standalone HWS devices as a separate device family:

• HWS_DEVICE_TYPE = "11":
  https://github.com/sockless-coding/aio-panasonic-comfort-cloud/blob/2026.8.4/aio_panasonic_comfort_cloud/constants.py#L201-L203
• HWS devices are excluded from normal is_valid devices and identified by is_hws:
  https://github.com/sockless-coding/aio-panasonic-comfort-cloud/blob/2026.8.4/aio_panasonic_comfort_cloud/panasonicdevice.py#L103-L141
• They are placed in _hws_devices, not _devices:
  https://github.com/sockless-coding/aio-panasonic-comfort-cloud/blob/2026.8.4/aio_panasonic_comfort_cloud/apiclient/_devices.py#L36-L66
• The client exposes has_hws_devices:
  https://github.com/sockless-coding/aio-panasonic-comfort-cloud/blob/2026.8.4/aio_panasonic_comfort_cloud/apiclient/__init__.py#L97-L113

Consequently, for any HWS-only account classified by the library:

• devices is empty
• has_unknown_devices is false
• has_hws_devices is true

but the current config-flow condition does not consider has_hws_devices.

Runtime setup already uses the broader check:

if (
    not devices
    and not api.has_unknown_devices
    and not api.has_aquarea_devices
    and not api.has_hws_devices
):

Source:

https://github.com/sockless-coding/panasonic_cc/blob/master/custom_components/panasonic_cc/__init__.py#L139-L143

This suggests the corresponding config-flow update was missed when the standalone-HWS support was added.

Evidentiary note

We did not capture the raw /device/group response from this setup attempt. We therefore cannot claim as directly observed that this particular response contained the HE-UM60CR with deviceType: "11".

What was observed is that the group request completed without a logged request/parsing exception and the flow subsequently returned no_devices. The HE-UM60CR continued to work in the official app.

Independently of that uncaptured response, the source-level config-flow bug is deterministic whenever the library has classified an HWS-only account such that has_hws_devices == True.

Suggested fix

Mirror the runtime device-presence check in the config flow:

if (
    not devices
    and not api.has_unknown_devices
    and not api.has_aquarea_devices
    and not api.has_hws_devices
):
    errors["base"] = "no_devices"

Both initial setup and reconfiguration use _async_try_login(), so this should cover both config-flow paths.

Suggested regression cases:

• HWS present, normal/unknown/Aquarea devices absent → allow setup
• Aquarea present, other families absent → allow setup
• All device families absent → return no_devices

I’m happy to test a fix against a real HE-UM60CR/HWS-only account.

[sockless-coding]

I've consolidated the checks in 2024.8.4

[123Orion123]

Thanks Jimmy, much appreciated! I can see 2026.8.4 is available now. I’ll update and test it against my HWS-only account and let you know how it goes. Thanks for turning this around so quickly! Cheers, Ian McGlashan | Network/Systems Administrator Team Leader Timaru District Council | PO Box 522 | Timaru 7940 P:+64 3 687 7295 | Cell: +64 21 066 0473 | W: www.timaru.govt.nz - The content of this email is confidential and may be legally privileged. This email is intended for the recipient specified in message only. ​It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. ​If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. On 19 Aug 2026, at 6:59 AM, Jimmy Everling ***@***.***> wrote:  [https://avatars.githubusercontent.com/u/25462432?s=20&v=4]sockless-coding left a comment (sockless-coding/panasonic_cc#499)<https://protect.checkpoint.com/v2/r04/___https://github.com/sockless-coding/panasonic_cc/issues/499%23issuecomment-5332701229___.Y3A0YTp0aW1hcnVkYzpjOm86ZjJkNTYzMDEwMDllMGYwMTQ0OTg2Yjc0NDUzMmI5NDg6Nzo4ZTEyOjYzNzM1NjRmZGYyMWIxYjJlMTNiNmVhZWI1MTFlZDBlNDYxMWIyZGE3Y2YyZjBkZDY2ZWY5MGEyMzMzN2I2MzM6aDpUOk4> I've consolidated the checks in 2024.8.4 — Reply to this email directly, view it on GitHub<https://protect.checkpoint.com/v2/r04/___https://github.com/sockless-coding/panasonic_cc/issues/499?email_source=notifications&email_token=CC66HKNZT5UJZZW45KVQUKT5KSROZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZTGI3TAMJSGI42M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L%23issuecomment-5332701229___.Y3A0YTp0aW1hcnVkYzpjOm86ZjJkNTYzMDEwMDllMGYwMTQ0OTg2Yjc0NDUzMmI5NDg6NzpmZDJmOmUwZjMwODhjMDgxZGU5MzRhMmIyNzE2NDliZDk0NDI3YmRjNmExOGVhNTZkMjNjNzljN2U0Mzg3NmZjMmEwNDY6aDpUOk4>, or unsubscribe<https://protect.checkpoint.com/v2/r04/___https://github.com/notifications/unsubscribe-auth/CC66HKJDIF6NU2T4PI2D3S35KSROZAVCNFSNUABFKJSXA33TNF2G64TZHMZDMMBUGEYDINJTHNEXG43VMU5TKMJXGYZTSNZYGA4KC5QC___.Y3A0YTp0aW1hcnVkYzpjOm86ZjJkNTYzMDEwMDllMGYwMTQ0OTg2Yjc0NDUzMmI5NDg6NzozNjIxOmY5OWZmMmQ0MTU3NWY1ZGNhZTY2ZWUxOTFlZGViMDAzNzZiOGQ1ODE0ZDYzODZjN2QxZDI1NDUyMjhmNGVkZWY6aDpUOk4>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://protect.checkpoint.com/v2/r04/___https://github.com/notifications/mobile/ios/CC66HKKX3TWHYKG6QQOUZVL5KSROZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZTGI3TAMJSGI42M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG___.Y3A0YTp0aW1hcnVkYzpjOm86ZjJkNTYzMDEwMDllMGYwMTQ0OTg2Yjc0NDUzMmI5NDg6Nzo4NDg1OmFlMmE2NDdiYzk3OTQzZjQyMWUwNTA2ZGU0MDQzZGEyYzQ4YzdiZDlkMTc4NDVmODIzYmJhYTg2NDY3ZWI3Y2M6aDpUOk4> and Android<https://protect.checkpoint.com/v2/r04/___https://github.com/notifications/mobile/android/CC66HKOE65IKLSYHTNQO7A35KSROZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZTGI3TAMJSGI42M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA___.Y3A0YTp0aW1hcnVkYzpjOm86ZjJkNTYzMDEwMDllMGYwMTQ0OTg2Yjc0NDUzMmI5NDg6Nzo5ZDY5OjMxZDk3N2JlZWNkODFiMzE3NDFiODY0MzU4OTU3NGMxN2RkNTA4NjA0YWUzODVhMzk5Yzg5Mzc5NWNkM2ZjMzc6aDpUOk4>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>