Add PyKumoBase.has_profile() to expose profile-populated state

[d-walsh]

Summary

Add a one-line public method has_profile() -> bool to PyKumoBase that tells callers whether the unit profile has been populated from a successful poll.

Motivation

_profile starts as {} at construction and is populated after the first successful update_status() call. Capability methods — has_auto_mode(), has_heat_mode(), get_fan_speeds(), get_vane_directions(), etc. — all read _profile and return silent defaults (False / a hardcoded fallback list) when the profile is empty. A truthiness check on their return values cannot distinguish real hardware data from those defaults.

Consumers that derive capability lists (e.g. which HVAC modes are supported) and cache the result need a reliable way to know whether the profile is populated before trusting capability output. Without this, capabilities derived before the first successful poll (e.g. when the WiFi adapter is offline at startup) are silently wrong and never corrected.

This is the exact scenario described in hass-kumo PR #223, which currently works around it via self._pykumo._profile — a direct reach into a private attribute.

Change

# py_kumo_base.py — PyKumoBase

def has_profile(self) -> bool:
    """Return True if the unit profile has been populated from a successful poll.
    ...
    """
    return bool(self._profile)

3 unit tests added in tests/test_py_kumo_base.py.

Relationship to hass-kumo

hass-kumo PR dlarrick/hass-kumo#223 adds a profile-populated guard before refreshing HVAC capabilities. Once this method is available and released, that PR can replace self._pykumo._profile with self._pykumo.has_profile() and bump the pykumo requirement accordingly.

[Copilot]

Pull request overview

This PR exposes whether a unit’s capability profile has been populated by adding a small public API (PyKumoBase.has_profile()) so consumers can avoid caching capability defaults before the first successful poll.

Changes:

• Add PyKumoBase.has_profile() -> bool returning whether _profile is non-empty.
• Add unit tests covering the populated/unpopulated profile state transitions.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
pykumo/py_kumo_base.py	Adds has_profile() to let callers detect whether capability data is real vs fallback defaults.
tests/test_py_kumo_base.py	Adds tests validating has_profile() before/after profile population and after clearing.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[d-walsh]

Removed the unused MagicMock and patch imports; pre-commit/ruff clean now.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.