Cloud adapter for Danfoss Ally™ — using OAuth2 (Client Credentials).
Reads temperature, humidity, valve position, and battery data for all devices in your Ally account,
and allows targeted single writes without forced mode changes or chained sequences.

• Direct connection to the Danfoss Ally Cloud API
• Automatic OAuth2 token refresh
• Discovers all registered devices
• Reads all available sensor and control data (temperature, humidity, battery, valve position, etc.)
• Converts raw Danfoss values (×0.1) into real units (°C, %)
• Fully automatic polling with configurable interval
• Supports single, isolated write commands from ioBroker to the cloud

• Single Writes — each state is sent independently (no automatic mode switching)
• Smooth Sync Logic
  • Anti-Race (5s): skip one poll right after a local write
  • Hold Window (1min): protect recent local values from overwrite
  • Lag Suppress (15s): ignore temporarily outdated cloud data
  • Soft Refresh (~1.5s): re-fetch only affected states after each write
• Quiet Logging — info-level for clean operation, debug-level for diagnostics
• Auto Scaling — temperatures/humidity auto-converted to °C / %

Note: Cloud updates from the Danfoss Ally app may appear in ioBroker with a short delay (1–2min).

• Danfoss Icon2 RT (Room thermostats)
• Danfoss Icon2 Controller
• Danfoss Ally™ Gateway
  (other Danfoss devices auto-discovered)

Go to Instances → danfoss-ally → Settings

Shorter intervals update faster but create more API traffic. 30–60s is a good balance.

API Key:      your-client-id
API Secret:   your-client-secret
Token URL:    https://api.danfoss.com/oauth2/token
API Base URL: https://api.danfoss.com/ally
Polling:      300

Each discovered device creates a device tree: danfoss-ally.0.<device_id>.*

The adapter separates read-only status values from writeable control values.

danfoss-ally.0.<deviceId>.status.*

These states mirror values received from the Danfoss Cloud API.

Properties:

• read: true
• write: false

Do not write to these states from scripts.

Examples:

• status.temp_current
• status.temp_set
• status.mode
• status.humidity_value
• status.battery_percentage

danfoss-ally.0.<deviceId>.control.*

These states are intended for user interaction and can be written from scripts or Blockly.

Properties:

• read: true
• write: true

Examples:

• control.temp_set
• control.manual_mode_fast
• control.mode
• control.child_lock

The adapter automatically sends commands to the Danfoss Cloud and updates the corresponding status values.

All numeric values are scaled from ×0.1 → °C/% automatically.

The adapter supports precise single writes to each controllable state without chaining or automatic mode changes.
This gives you full control in Blockly, JavaScript, or custom logic scripts.

Adapter does not auto-switch modes when writing setpoints — you decide in your logic.

// Manual mode
setState("danfoss-ally.0.<id>.control.mode", "manual");
setState("danfoss-ally.0.<id>.control.temp_set", 21.5);

// At home
setState("danfoss-ally.0.<id>.control.mode", "at_home");
setState("danfoss-ally.0.<id>.control.at_home_setting", 21.0);

// Leaving home
setState("danfoss-ally.0.<id>.control.mode", "leaving_home");
setState("danfoss-ally.0.<id>.control.leaving_home_setting", 19.0);

// Pause
setState("danfoss-ally.0.<id>.control.mode", "pause");
setState("danfoss-ally.0.<id>.control.pause_setting", 5.0);

// Holiday
setState("danfoss-ally.0.<id>.control.mode", "holiday");
setState("danfoss-ally.0.<id>.control.holiday_setting", 10.0);

// Child lock
setState("danfoss-ally.0.<id>.control.child_lock", true);

// Explicit source (usually not needed)
setState("danfoss-ally.0.<id>.control.SetpointChangeSource", "Externally"); // or 'schedule'

Write commands must target the control.* states.
The status.* states are read-only mirrors from the Danfoss Cloud.

These mechanisms ensure smooth synchronization between ioBroker and the Danfoss Cloud without flickering or value loops.

The adapter provides detailed debug-level information for diagnostics but remains quiet during normal operation.

• ack=true updates appear only in debug
• HOLD, MATCH, SUPPRESS → debug-level, harmless diagnostics
• API errors (HTTP 400/401) retried automatically (logged at debug)
• Clean info-level summary after every poll:

Poll Summary Example

✅ Updated 13 devices. Changed=2, Skipped=253, Held=1
📡 Found devices, updating states...
⏸️ Skipping poll (anti-race 5000ms)

🔄 Starting Danfoss Ally adapter...
🔑 Refreshing OAuth2 token...
✅ Token acquired. Expires in ~3599 s
📡 Found 13 devices, updating states...
✅ Updated 13 devices from Danfoss Ally Cloud.
⏱ Polling interval set to 300 s

• Uses OAuth2 Client Credentials Flow
• Token auto-request on startup, refresh before expiry
• On 401 Unauthorized: refresh + retry once
• Tokens kept in memory, never stored
• Optional scope / audience supported
• All token events visible in debug log

The adapter communicates with the Danfoss Ally Cloud API (base URL configurable).

Headers:
Authorization: Bearer <token>
Content-Type: application/json
Optional: X-App-Key, X-Tenant-Id, etc.

Error Handling:

• 400: invalid header/value → logged
• 401: token refresh + retry
• 5xx: retried next poll
• Temperature writes auto-scaled ×10 (e.g. 21.5 → 215)

• Default: 300s (configurable)
• Updates only changed values
• Includes all anti-race / hold / lag / soft-refresh logic above
• Info summary after each poll shows changed, skipped, and held states

• One command per state (no mode chaining)
• Mode + temperature must be written separately
• Values are clamped to allowed limits, scaled ×10
• child_lock: tries 0/1, retries true/false on 400 error
• SetpointChangeSource: optional; defaults to "Externally" when manual modes are active

All send, retry, and confirm logs appear at debug level.

• Fixed invalid io-package.json (JSON syntax error)
• No functional changes

• Introduced control channel for writable states
• status channel is now strictly read-only
• Improved write detection and state handling
• Prevented writes to channels or non-state objects
• Improved adapter stability

• Updated CI & deploy workflow
• Fixed npm publishing process
• Improved code formatting (Prettier / ESLint)
• No functional changes for end users

npm i
node main.js

or install via ioBroker development tooling.

MIT License

Copyright (c) 2025-2026 Author [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.