node-red-contrib-knx-ultimate 6.3.16 → 6.3.18

package/CHANGELOG.md

@@ -6,6 +6,17 @@
 
 # CHANGELOG
 
+**Version 6.3.18** - August 2026<br/>
+
+- **KNX AI — focused configuration with fixed defaults**: aligned the hidden traffic-analysis defaults to a 600-second history, disk archival enabled for 10 days, automatic summaries disabled, a 120-second analysis window, 5,000 in-memory events and a Top-12 list. The Node-RED project inventory is now always included, while traffic analysis, chat input/output mappings and their obsolete editor controls remain hidden. Documentation language selection was removed because the AI now chooses the appropriate language. Proactive-home switches and advanced proactive settings were removed without legacy-value migration: user-managed AI Education is now the sole configuration surface for this behaviour. Editor help, examples and wiki documentation were updated in EN, IT, DE, FR, ES and zh-CN.<br/>
+- **KNX AI — horizontal accordion and visible chat context**: rebuilt the editor accordion with the same horizontal-tab layout and visual behaviour as KNXUltimate. Automatically detected adapters now appear at the end, followed by a new context card that summarizes what chat can access, including generated context filenames and the absolute KNX telegram archive directories.<br/>
+- **KNX AI — TTS Ultimate announcements**: added automatic discovery of `node-red-contrib-tts-ultimate` and a selector for the TTS Ultimate node to use across all flows. Chat responses can now dispatch spoken announcements through the selected TTS/Sonos path while preserving the existing adapter registry design.<br/>
+- **KNX AI — local model providers and responsiveness**: promoted Ollama out of beta and added Bionic LM Studio. Model selection now discovers each local model's maximum context length and configures it when loaded; smaller context windows automatically receive reduced, relevance-selected prompts and bounded output budgets, with progressive context compaction on provider overflow errors. Local requests use a ten-minute minimum timeout, preserve detailed provider errors and retry supported OpenAI-compatible parameter variants. Chat users receive localized thinking feedback while inference is running, and the node status now reports only incoming requests and thinking state instead of KNX telegram traffic.<br/>
+
+**Version 6.3.17** - August 2026<br/>
+
+- **KNX AI — unified Assistant context for chat channels**: Telegram, RedBot and custom chat adapters now receive the same complete KNX analysis context as the web Assistant, including the full relevant traffic selection, summaries, areas, learned home memory, Node-RED flow context, Function-node source and documentation snippets enabled by the node configuration. The chat-specific ETS catalog, camera capabilities, persistent conversation context, command validation and confirmation safeguards remain layered on top.<br/>
+
 **Version 6.3.16** - August 2026<br/>
 
 - **KNX AI — automatically detected camera adapters**: installed camera suites can now register vendor-neutral camera catalogs, connectivity state, snapshots and smart events directly in the KNX AI chat runtime, without selectors or camera-node wiring. The “Conversations & home” editor section shows every detected adapter together with its registered controllers and cameras. `node-red-contrib-unifi-ultimate` is the first provider: users can request or visually analyze a current Protect snapshot and create persistent Telegram/RedBot notifications for motion, smart line crossings and intrusion/loiter zones. Generic smart-detection rules now correctly distinguish classified people, animals, vehicles, faces, license plates and packages from unclassified motion, and match classifications across Protect smart zones, lines and loiter zones. Chat snapshots no longer force full-HD; the provider chooses a supported quality and retries only transient failures at standard quality. An offline camera is identified explicitly before Chat AI proposes an unavailable snapshot. Camera rules share `knxai-chat-context.md` and survive Node-RED restarts; Telegram adapters emit snapshots as native photos. Existing `node-red-contrib-telegrambot` presets saved before image support are upgraded at runtime for snapshot replies, including explicit JPEG filename and MIME metadata. The same registry contract is ready for packages such as `hikvision-ultimate`.<br/>

package/examples/KNX AI - Conversational Control with Confirmation.json

@@ -199,33 +199,13 @@
     "server": "cfg_knx_ai_control",
     "name": "KNX AI with confirmation",
     "topic": "knx-ai",
-    "notifyreadrequest": true,
-    "notifyresponse": true,
-    "notifywrite": true,
-    "analysisWindowSec": "120",
-    "historyWindowSec": "600",
-    "historyStoreToDisk": false,
-    "historyStoreRetentionDays": "10",
-    "emitIntervalSec": "0",
-    "topN": "10",
-    "maxEvents": "50000",
-    "rateWindowSec": "10",
-    "maxTelegramPerSecOverall": "0",
-    "maxTelegramPerSecPerGA": "0",
-    "flapWindowSec": "30",
-    "flapMaxChanges": "0",
-    "enablePattern": true,
-    "patternMaxLagMs": "1500",
-    "patternMinCount": "8",
     "llmEnabled": true,
     "llmProvider": "openai_compat",
     "llmBaseUrl": "https://api.openai.com/v1/chat/completions",
     "llmModel": "gpt-5.4",
     "llmSystemPrompt": "Sei un assistente per un impianto KNX. Rispondi in italiano e proponi solo comandi necessari e coerenti con la richiesta.",
     "llmIncludeRaw": false,
-    "llmIncludeFlowContext": true,
     "llmIncludeDocsSnippets": true,
-    "llmDocsLanguage": "it",
     "llmAllowKnxCommands": true,
     "llmRequireCommandConfirmation": true,
     "x": 520,

package/examples/KNX AI - Summary Anomalies and Ask.json

@@ -137,22 +137,6 @@
     "server": "cfg_knx_ai_1",
     "name": "KNX AI",
     "topic": "knx-ai",
-    "notifywrite": true,
-    "notifyresponse": true,
-    "notifyreadrequest": true,
-    "analysisWindowSec": "60",
-    "historyWindowSec": "300",
-    "maxEvents": "5000",
-    "emitIntervalSec": "0",
-    "topN": "10",
-    "enablePattern": true,
-    "patternMaxLagMs": "1500",
-    "patternMinCount": "8",
-    "rateWindowSec": "10",
-    "maxTelegramPerSecOverall": "0",
-    "maxTelegramPerSecPerGA": "0",
-    "flapWindowSec": "30",
-    "flapMaxChanges": "0",
     "llmEnabled": false,
     "llmProvider": "openai_compat",
     "llmBaseUrl": "https://api.openai.com/v1/chat/completions",
@@ -236,4 +220,3 @@
     "autoReconnect": "yes"
   }
 ]
-

package/examples/KNX AI - Telegrambot Direct Chat.json

@@ -30,8 +30,8 @@
     "id": "comment_knx_ai_home_intelligence",
     "type": "comment",
     "z": "tab_knx_ai_telegram",
-    "name": "3. Home intelligence: bounded memory + proactive cover notifications",
-    "info": "This example enables proactive notifications after 120 minutes, outside 23:00-07:00. The most recent Telegram chat becomes the recipient. AI Education remains user-managed, and the Markdown memory file has a hard 256 KB limit. Proactive observations use output 3 only and never write to KNX.",
+    "name": "3. AI Education: bounded memory + proactive cover notifications",
+    "info": "AI Education requests proactive notifications after 120 minutes, outside 23:00-07:00, with a six-hour repeat interval. The most recent Telegram chat becomes the recipient. The Markdown memory file has a hard 5 MB limit. Proactive observations use output 3 only and never write to KNX.",
     "x": 520,
     "y": 120,
     "wires": []
@@ -76,45 +76,19 @@
     "server": "cfg_knx_ai_telegram",
     "name": "KNX AI + Telegram adapter",
     "topic": "knx-ai",
-    "notifyreadrequest": true,
-    "notifyresponse": true,
-    "notifywrite": true,
-    "analysisWindowSec": "120",
-    "historyWindowSec": "600",
-    "historyStoreToDisk": false,
-    "historyStoreRetentionDays": "10",
-    "emitIntervalSec": "0",
-    "topN": "10",
-    "maxEvents": "50000",
-    "rateWindowSec": "10",
-    "maxTelegramPerSecOverall": "0",
-    "maxTelegramPerSecPerGA": "0",
-    "flapWindowSec": "30",
-    "flapMaxChanges": "0",
-    "enablePattern": true,
-    "patternMaxLagMs": "1500",
-    "patternMinCount": "8",
     "llmEnabled": true,
     "llmProvider": "openai_compat",
     "llmBaseUrl": "https://api.openai.com/v1/chat/completions",
     "llmModel": "gpt-5.4",
     "llmSystemPrompt": "Sei un assistente per un impianto KNX. Rispondi nella lingua dell'utente.",
     "llmIncludeRaw": false,
-    "llmIncludeFlowContext": true,
     "llmIncludeDocsSnippets": true,
-    "llmDocsLanguage": "it",
     "llmAllowKnxCommands": true,
     "llmRequireCommandConfirmation": true,
     "chatAdapterPreset": "none",
     "chatInputCode": "",
     "chatOutputCode": "",
-    "proactiveEnabled": true,
-    "proactiveRecipient": "",
-    "proactiveOpenMinutes": "120",
-    "proactiveCooldownMinutes": "360",
-    "proactiveQuietStart": "23:00",
-    "proactiveQuietEnd": "07:00",
-    "aiEducation": "Avvisami se una persiana, una finestra o una porta rimane aperta insolitamente a lungo. Non inviare notifiche durante le ore silenziose configurate.",
+    "aiEducation": "Avvisa la mia ultima chat se una persiana, una finestra o una porta rimane aperta per almeno 120 minuti. Non inviare notifiche tra le 23:00 e le 07:00 e non ripetere lo stesso avviso prima di 6 ore.",
     "x": 500,
     "y": 210,
     "wires": [