Kydoimosandanthropic/claude-opus-5
706580fab2
The GitHub mirror is gone, so the HACS packaging and the GitHub-only CI no longer have anything to run against. Remove hacs.json and the .github/ workflow. Both of its jobs (hassfest and hacs/action) were gated on `github.server_url == 'https://github.com'` and are GitHub-hosted actions, so neither can run on the Gitea runner. Replace them with .gitea/workflows/ci.yml: - lint: ruff check + ruff format --check, version pinned because ruff's default rule set and formatter output move between releases - validate: byte-compile, then scripts/validate_integration.py, which covers the part of hassfest that matters for a manually installed custom component (manifest keys, domain/directory agreement, and translations matching strings.json key for key) README now documents manual installation only, and points at the local CI commands. manifest.json documentation and issue_tracker point at the Gitea repo; NOTICE keeps its upstream attribution. Adopting ruff surfaced two real defects, fixed here: - climate.async_set_hvac_mode raised HomeAssistantError for an unsupported mode from inside a try that catches Exception, so the message was re-wrapped as "Failed to set HVAC mode: Unsupported HVAC mode: ...". The validation is now hoisted above the try. - config_flow.async_step_reauth_confirm swallowed unexpected exceptions into a bare "unknown" error with no log, unlike the user step. It now logs via _LOGGER.exception. Remaining changes are mechanical: import ordering, docstrings on public methods, ClassVar on mutable class attributes, contextlib.suppress, and asyncio.TimeoutError -> TimeoutError (an alias since 3.11). The smoke test now reads the new DknCloudNaClient.socket_connected property rather than reaching into _socket. Co-authored-by: anthropic/claude-opus-5
DKN Cloud NA — Home Assistant Integration
Control your Daikin mini-split air conditioners through Home Assistant using the DKN Cloud NA cloud service.
This integration is a port of the homebridge-dkncloudna plugin by @plecong, adapted for Home Assistant.
Supported Hardware
Any Daikin mini-split system connected to the DKN Cloud NA WiFi adapter (North America). The adapter must be set up and working in the official DKN Cloud NA mobile app before using this integration.
Prerequisites
- A working DKN Cloud NA account
- Your Daikin unit(s) already set up and visible in the DKN Cloud NA app
- Home Assistant 2024.1 or later
Installation
This integration is installed manually — it is not published to HACS.
- Download or clone this repository
- Copy the
custom_components/dkncloudna/directory into your Home Assistantconfig/custom_components/directory, so that you end up withconfig/custom_components/dkncloudna/manifest.json - Restart Home Assistant
To upgrade, replace the dkncloudna directory with the newer copy and restart again.
Configuration
- Go to Settings → Devices & Services → Add Integration
- Search for DKN Cloud NA
- Enter your DKN Cloud NA email and password
- Optionally adjust the scan interval (default: 60 seconds)
- Optionally enable Show tokens after login to view your access and refresh tokens
All discovered devices are added automatically.
Entities
Each device exposes the following entities:
| Entity | Type | Description |
|---|---|---|
| AC unit | climate |
On/off, mode (auto/cool/heat/dry/fan), target temperature, fan speed, swing |
| Room temperature | sensor |
Current room temperature (°C) |
| Exterior temperature | sensor |
Outdoor temperature (°C) — disabled by default |
| Wi-Fi signal | sensor |
RSSI in dBm — diagnostic |
| Error code | sensor |
Active error code — diagnostic |
| Connected | binary_sensor |
Whether the device is online — diagnostic |
| Machine ready | binary_sensor |
Whether the device is ready to receive commands — diagnostic |
How It Works
- Authentication. The integration exchanges your DKN Cloud NA credentials for access + refresh tokens on first setup, then uses the refresh token to keep the session alive. Refreshed tokens are persisted to the config entry so they survive restarts.
- Device discovery and polling. All installations and their devices are fetched from the REST API on a configurable interval (default 60 seconds). The poll establishes the device list and acts as a heartbeat against the cloud.
- Live updates via Socket.IO. While the integration is running, it maintains a Socket.IO connection to dkncloudna.com and applies
device-dataevents to entity state in near real-time — no waiting for the next poll cycle. - Control via Socket.IO. Mode, target temperature, fan speed, and swing commands are sent as Socket.IO machine events. Local changes are reflected optimistically in Home Assistant and reconciled when the cloud echoes the new state back.
- Temperature units. Home Assistant always presents temperatures in Celsius. Devices reporting in Fahrenheit are transparently converted in both directions — values you set in HA are sent to the device in its native units.
Known Limitations
- Reauthentication is required if your refresh token expires (e.g. you change your DKN Cloud NA password). Home Assistant will surface a "Reconfigure" prompt when this happens.
- Multi-zone systems are exposed as one climate entity per indoor unit; there is no aggregate "installation" entity.
Development
CI runs on Gitea Actions (.gitea/workflows/ci.yml). To reproduce it locally:
pip install ruff==0.16.8 # version is pinned in CI
ruff check .
ruff format --check .
python3 scripts/validate_integration.py
scripts/validate_integration.py checks that every JSON file parses, that
manifest.json has the keys Home Assistant requires of a custom integration,
and that each file in translations/ has the same key structure as
strings.json.
smoke-test/run.sh exercises the client against a real DKN Cloud NA account.
It needs a .env with DKN_CLOUD_NA_EMAIL and DKN_CLOUD_NA_PASSWORD (see
.env.example) and is run by hand, not in CI.
Credits
- Original Homebridge plugin: homebridge-dkncloudna by @plecong
- EU counterpart inspiration: DKNCloud-HASS by @eXPerience83