node-red-contrib-knx-ultimate 6.3.29 → 6.3.30

package/CHANGELOG.md

@@ -6,6 +6,10 @@
 
 # CHANGELOG
 
+**Version 6.3.30** - August 2026<br/>
+
+- **KNX AI — two-way RedBot Telegram voice chat**: the `RedBot / node-red-contrib-chatbot (Telegram)` preset now accepts RedBot's native inbound `audio` payload and its already-downloaded OGG/Opus `Buffer`, applies the same 20 MB and five-minute safeguards without downloading the file a second time, and transcribes it through the selected OpenAI-compatible provider. Successful requests receive a native RedBot `audio` reply with the localized AI-generated-voice disclosure and text caption; KNX confirmations deliberately remain RedBot `inline-buttons` text messages because its Telegram voice sender cannot attach that keyboard to `sendVoice`. Existing saved RedBot input/output mappings are upgraded at runtime. The separate `windkh/node-red-contrib-telegrambot` voice contract and its tests remain unchanged.<br/>
+
 **Version 6.3.29** - August 2026<br/>
 
 - **KNX AI — patient provider-neutral model requests**: every LLM chat request now receives the same 30-minute minimum deadline, regardless of provider, model or model manager, while longer legacy configured values remain honored. The model transport carries that deadline through both streaming and non-streaming responses instead of inheriting a shorter HTTP-library header timeout; fast responses are returned immediately, model-response timeouts remain distinct from unreachable-server errors, and Telegram audio operations retain their separate two-minute safeguard.<br/>

package/nodes/knxUltimateAI.js

@@ -834,6 +834,7 @@ const buildKnxAiSetupDoctorSnapshot = ({
   if (apiKeyRequired && llm.apiKeyConfigured !== true) missing.push('API key')
   const providerReady = missing.length === 0
   const chatPreset = String(llm.chatAdapterPreset || 'none').trim() || 'none'
+  const telegramVoiceApplicable = ['windkh-telegrambot', 'redbot-telegram'].includes(chatPreset)
   const chatPresetLabels = {
     'windkh-telegrambot': 'Telegram Bot',
     'redbot-telegram': 'RedBot Telegram'
@@ -903,7 +904,7 @@ const buildKnxAiSetupDoctorSnapshot = ({
     { id: 'chat', status: chatStatus, blocking: chatPreset !== 'none', weight: chatPreset !== 'none' ? 10 : 0, details: { preset: chatPreset, presetLabel: chatPresetLabels[chatPreset] || chatPreset, ready: chatVerified, wired: chatWired, upstreamCount, outputConnected: assistantOutput.connected === true } },
     { id: 'commands', status: commandStatus, blocking: llm.allowKnxCommands === true, weight: llm.allowKnxCommands === true ? 10 : 0, details: { enabled: llm.allowKnxCommands === true, connected: commandOutput.connected === true, verified: commandTargetVerified } },
     { id: 'tts', status: ttsOutput.connected === true ? 'pass' : 'info', blocking: false, weight: 0, details: { connected: ttsOutput.connected === true, connectionCount: Math.max(0, Number(ttsOutput.connectionCount) || 0) } },
-    { id: 'voice', status: chatPreset !== 'windkh-telegrambot' ? 'info' : provider === 'openai_compat' && providerReady ? 'pass' : 'warn', blocking: false, weight: 0, details: { applicable: chatPreset === 'windkh-telegrambot', ready: chatPreset === 'windkh-telegrambot' && provider === 'openai_compat' && providerReady } },
+    { id: 'voice', status: !telegramVoiceApplicable ? 'info' : provider === 'openai_compat' && providerReady ? 'pass' : 'warn', blocking: false, weight: 0, details: { applicable: telegramVoiceApplicable, ready: telegramVoiceApplicable && provider === 'openai_compat' && providerReady } },
     { id: 'cameras', status: Number(integrations.cameraCount) > 0 ? 'pass' : 'info', blocking: false, weight: 0, details: { cameraCount: Math.max(0, Number(integrations.cameraCount) || 0), adapterCount: Math.max(0, Number(integrations.cameraAdapterCount) || 0) } },
     { id: 'webAccess', status: webDetails.enabled ? 'pass' : 'info', blocking: false, weight: 0, details: webDetails },
     { id: 'proactiveWeb', status: proactiveWebStatus, blocking: false, weight: 0, details: proactiveWebDetails }
@@ -12741,7 +12742,7 @@ module.exports = function (RED) {
 
     const prepareKnxAiTelegramVoiceInput = async (message) => {
       if (!isKnxAiTelegramVoiceInput(message)) return message
-      if (node.chatAdapterPreset !== 'windkh-telegrambot') return message
+      if (!['windkh-telegrambot', 'redbot-telegram'].includes(node.chatAdapterPreset)) return message
       const voiceInput = Object.assign({}, message.knxAi.voiceInput)
       redactKnxAiTelegramVoiceLocations(message)
       if (!node.llmEnabled) {
@@ -12775,14 +12776,16 @@ module.exports = function (RED) {
       })
       delete safeVoiceInput.weblink
       delete safeVoiceInput.path
+      delete safeVoiceInput.data
       message.knxAi = Object.assign({}, message.knxAi, { voiceInput: safeVoiceInput })
       return message
     }
 
     const enrichKnxAiTelegramVoiceReplyMetadata = async ({ inputMessage, content, speechContent, metadata = {} } = {}) => {
       const enriched = Object.assign({}, metadata)
-      if (!isKnxAiTelegramVoiceInput(inputMessage) || node.chatAdapterPreset !== 'windkh-telegrambot') return enriched
+      if (!isKnxAiTelegramVoiceInput(inputMessage) || !['windkh-telegrambot', 'redbot-telegram'].includes(node.chatAdapterPreset)) return enriched
       if (enriched.image && enriched.image.data) return enriched
+      if (node.chatAdapterPreset === 'redbot-telegram' && enriched.confirmationRequest && enriched.confirmationRequest.required === true) return enriched
       let speechText = speechContent === undefined ? content : speechContent
       if (speechText && typeof speechText === 'object') {
         speechText = speechText.error || speechText.message || safeStringify(speechText)

package/nodes/locales/de/knxUltimateAI.html

@@ -78,7 +78,7 @@ Mit dieser Vorlage wird eine Telegram-Sprachnachricht (`msg.payload.type = "voic
 
 Jede native Sprachantwort beginnt in der Bildunterschrift mit dem lokalisierten Hinweis **KI-generierte Stimme**, der für den Telegram-Empfänger sichtbar ist.
 
-Die enthaltene Vorlage **RedBot / node-red-contrib-chatbot (Telegram)** folgt dem gemeinsamen RedBot-Nachrichtenformat. Verbinden Sie `chatbot-telegram-receive` direkt mit KNX AI und Ausgang 3 direkt mit `chatbot-telegram-send`; ein separater Callback-Node ist nicht erforderlich, da RedBot Postbacks von Inline-Schaltflächen in normale Eingangsnachrichten umwandelt. Die Eingangszuordnung liest `transport`, `chatId`, `type`, `content` und die Telegram-Sprache. Die Ausgangszuordnung bewahrt die RedBot-Trackingdaten `originalMessage`, `chat`, `api` und `client` und erzeugt anschließend entweder einen `message`-Payload oder einen `inline-buttons`-Payload mit `postback`-Aktionen zur Bestätigung. RedBot bleibt eine separate optionale Abhängigkeit.
+Die enthaltene Vorlage **RedBot / node-red-contrib-chatbot (Telegram)** folgt dem gemeinsamen RedBot-Nachrichtenformat. Verbinden Sie `chatbot-telegram-receive` direkt mit KNX AI und Ausgang 3 direkt mit `chatbot-telegram-send`; ein separater Callback-Node ist nicht erforderlich, da RedBot Postbacks von Inline-Schaltflächen in normale Eingangsnachrichten umwandelt. Text und Postbacks verwenden RedBots `message`-Payload. Eine native Telegram-Sprachnachricht kommt als `type = "audio"` mit dem bereits von RedBot heruntergeladenen OGG/Opus-`Buffer` an: KNX AI wendet Größen- und Dauergrenzen ohne zweiten Download an, transkribiert sie mit demselben oben beschriebenen OpenAI-kompatiblen Provider und antwortet mit einem nativen RedBot-`audio`-Payload samt Textunterschrift und lokalisiertem Hinweis auf die KI-generierte Stimme. Wenn eine KNX-Schreibbestätigung erforderlich ist, bleibt die Antwort bewusst ein textbasierter `inline-buttons`-Payload, da RedBot diese Schaltflächen nicht an dieselbe Sprachnachricht anhängen kann. Die Ausgangszuordnung bewahrt die RedBot-Trackingdaten `originalMessage`, `chat`, `api` und `client`; ältere gespeicherte RedBot-Zuordnungen werden zur Laufzeit aktualisiert. RedBot bleibt eine separate optionale Abhängigkeit.
 
 ### Automatisch erkannte Kamera-Adapter
 Installierte Kamerapakete können KNX AI zur Laufzeit einen Kamera-Adapter bereitstellen. Es gibt weder eine Auswahl noch einen Kamera-Node, der mit KNX AI verbunden werden muss: verfügbare Adapter, Controller und Kameras werden automatisch erkannt und in den Chat-Kontext aufgenommen. `node-red-contrib-unifi-ultimate` ist der erste unterstützte Anbieter; weitere Pakete wie `hikvision-ultimate` können sich über denselben herstellerneutralen Vertrag registrieren.

package/nodes/locales/en/knxUltimateAI.html

@@ -78,7 +78,7 @@ With this preset, a Telegram voice message (`msg.payload.type = "voice"`) is han
 
 Every native voice caption begins with a localized **AI-generated voice** disclosure for the Telegram recipient.
 
-The included **RedBot / node-red-contrib-chatbot (Telegram)** preset follows RedBot's common message contract. Connect `chatbot-telegram-receive` directly to KNX AI and output 3 directly to `chatbot-telegram-send`; no separate callback node is needed because RedBot converts inline-button postbacks into normal inbound messages. The input mapping reads `transport`, `chatId`, `type`, `content`, and the Telegram language. The output mapping preserves RedBot's `originalMessage`, `chat`, `api`, and `client` tracking data, then emits either a `message` payload or an `inline-buttons` payload containing `postback` actions for confirmation. RedBot remains a separate optional dependency.
+The included **RedBot / node-red-contrib-chatbot (Telegram)** preset follows RedBot's common message contract. Connect `chatbot-telegram-receive` directly to KNX AI and output 3 directly to `chatbot-telegram-send`; no separate callback node is needed because RedBot converts inline-button postbacks into normal inbound messages. Text and postbacks use RedBot's `message` payload. A native Telegram voice arrives as `type = "audio"` with an OGG/Opus `Buffer` already downloaded by RedBot; KNX AI applies its size and duration limits without downloading it again, transcribes it with the same OpenAI-compatible provider described above, and returns a native RedBot `audio` reply with the localized AI-generated-voice disclosure and text caption. When a KNX write needs confirmation, the reply deliberately remains a text `inline-buttons` payload because RedBot cannot attach those buttons to the same voice message. The output mapping preserves RedBot's `originalMessage`, `chat`, `api`, and `client` tracking data, and older saved RedBot mappings are upgraded at runtime. RedBot remains a separate optional dependency.
 
 ### Automatically detected camera adapters
 Installed camera packages can publish a camera adapter to KNX AI at runtime. There is no selector and no camera node to wire to KNX AI: available adapters, controllers and cameras are detected automatically and included in the chat context. `node-red-contrib-unifi-ultimate` is the first supported provider; other packages, such as `hikvision-ultimate`, can register through the same vendor-neutral contract.

package/nodes/locales/es/knxUltimateAI.html

@@ -78,7 +78,7 @@ Con este preajuste, los mensajes de voz de Telegram (`msg.payload.type = "voice"
 
 La leyenda de cada respuesta de voz nativa comienza con el aviso localizado **Voz generada por IA**, visible para el destinatario de Telegram.
 
-El preajuste incluido **RedBot / node-red-contrib-chatbot (Telegram)** sigue el formato común de mensajes de RedBot. Conecta directamente `chatbot-telegram-receive` a KNX AI y la salida 3 a `chatbot-telegram-send`; no hace falta un nodo callback separado porque RedBot convierte los postbacks de los botones inline en mensajes de entrada normales. El mapeo de entrada lee `transport`, `chatId`, `type`, `content` y el idioma de Telegram. El mapeo de salida conserva los datos de seguimiento RedBot `originalMessage`, `chat`, `api` y `client`, y después emite un payload `message` o un payload `inline-buttons` con acciones `postback` de confirmación. RedBot sigue siendo una dependencia opcional separada.
+El preajuste incluido **RedBot / node-red-contrib-chatbot (Telegram)** sigue el formato común de mensajes de RedBot. Conecta directamente `chatbot-telegram-receive` a KNX AI y la salida 3 a `chatbot-telegram-send`; no hace falta un nodo callback separado porque RedBot convierte los postbacks de los botones inline en mensajes de entrada normales. El texto y los postbacks usan el payload RedBot `message`. Un mensaje de voz nativo de Telegram llega como `type = "audio"` con el `Buffer` OGG/Opus ya descargado por RedBot: KNX AI aplica los límites de tamaño y duración sin volver a descargarlo, lo transcribe con el mismo proveedor OpenAI-compatible descrito arriba y responde con un payload RedBot `audio` nativo, el texto y el aviso localizado de voz generada por IA. Cuando una escritura KNX necesita confirmación, la respuesta se mantiene deliberadamente como payload de texto `inline-buttons`, porque RedBot no puede adjuntar esos botones al mismo mensaje de voz. El mapeo de salida conserva los datos de seguimiento RedBot `originalMessage`, `chat`, `api` y `client`; los mapeos RedBot antiguos guardados también se actualizan en tiempo de ejecución. RedBot sigue siendo una dependencia opcional separada.
 
 ### Adaptadores de cámara detectados automáticamente
 Los paquetes de cámaras instalados pueden publicar en tiempo de ejecución un adaptador para KNX AI. No hay selector ni nodo de cámara que conectar a KNX AI: los adaptadores, controladores y cámaras disponibles se detectan automáticamente y se incorporan al contexto del chat. `node-red-contrib-unifi-ultimate` es el primer proveedor compatible; otros paquetes, como `hikvision-ultimate`, pueden registrarse mediante el mismo contrato independiente del fabricante.

package/nodes/locales/fr/knxUltimateAI.html

@@ -78,7 +78,7 @@ Avec ce préréglage, un message vocal Telegram (`msg.payload.type = "voice"`) n
 
 La légende de chaque réponse vocale native commence par la mention localisée **Voix générée par l’IA**, visible par le destinataire Telegram.
 
-Le préréglage inclus **RedBot / node-red-contrib-chatbot (Telegram)** suit le format de message commun de RedBot. Connectez directement `chatbot-telegram-receive` à KNX AI et la sortie 3 à `chatbot-telegram-send` ; aucun nœud de callback séparé n’est nécessaire, car RedBot convertit les postbacks des boutons inline en messages entrants ordinaires. Le mappage d’entrée lit `transport`, `chatId`, `type`, `content` et la langue Telegram. Le mappage de sortie conserve les données de suivi RedBot `originalMessage`, `chat`, `api` et `client`, puis émet soit un payload `message`, soit un payload `inline-buttons` avec des actions `postback` de confirmation. RedBot reste une dépendance optionnelle distincte.
+Le préréglage inclus **RedBot / node-red-contrib-chatbot (Telegram)** suit le format de message commun de RedBot. Connectez directement `chatbot-telegram-receive` à KNX AI et la sortie 3 à `chatbot-telegram-send` ; aucun nœud de callback séparé n’est nécessaire, car RedBot convertit les postbacks des boutons inline en messages entrants ordinaires. Le texte et les postbacks utilisent le payload RedBot `message`. Un message vocal Telegram natif arrive avec `type = "audio"` et le `Buffer` OGG/Opus déjà téléchargé par RedBot : KNX AI applique les limites de taille et de durée sans second téléchargement, le transcrit avec le même fournisseur OpenAI-compatible décrit ci-dessus et répond avec un payload RedBot `audio` natif, sa légende textuelle et la mention localisée de voix générée par l’IA. Lorsqu’une écriture KNX exige une confirmation, la réponse reste volontairement un payload texte `inline-buttons`, car RedBot ne peut pas joindre ces boutons au même message vocal. Le mappage de sortie conserve les données de suivi RedBot `originalMessage`, `chat`, `api` et `client` ; les anciens mappages RedBot enregistrés sont également mis à niveau à l’exécution. RedBot reste une dépendance optionnelle distincte.
 
 ### Adaptateurs de caméra détectés automatiquement
 Les paquets de caméra installés peuvent publier à l’exécution un adaptateur pour KNX AI. Il n’existe aucun sélecteur ni nœud caméra à relier à KNX AI : les adaptateurs, contrôleurs et caméras disponibles sont détectés automatiquement et ajoutés au contexte du chat. `node-red-contrib-unifi-ultimate` est le premier fournisseur pris en charge ; d’autres paquets, tels que `hikvision-ultimate`, peuvent s’enregistrer avec le même contrat indépendant du fabricant.

package/nodes/locales/it/knxUltimateAI.html

@@ -78,7 +78,7 @@ Con questo preset, un messaggio vocale Telegram (`msg.payload.type = "voice"`) v
 
 La didascalia di ogni vocale nativo inizia con l'indicazione localizzata **Voce generata dall’IA**, visibile al destinatario Telegram.
 
-Il preset incluso **RedBot / node-red-contrib-chatbot (Telegram)** segue il formato comune dei messaggi RedBot. Collega direttamente `chatbot-telegram-receive` a KNX AI e l'uscita 3 direttamente a `chatbot-telegram-send`; non serve un nodo callback separato perché RedBot converte i postback dei pulsanti inline in normali messaggi in ingresso. La mappatura d'ingresso legge `transport`, `chatId`, `type`, `content` e la lingua Telegram. Quella d'uscita conserva i dati di tracciamento RedBot `originalMessage`, `chat`, `api` e `client`, quindi emette un payload `message` oppure un payload `inline-buttons` con azioni `postback` per la conferma. RedBot resta una dipendenza opzionale separata.
+Il preset incluso **RedBot / node-red-contrib-chatbot (Telegram)** segue il formato comune dei messaggi RedBot. Collega direttamente `chatbot-telegram-receive` a KNX AI e l'uscita 3 direttamente a `chatbot-telegram-send`; non serve un nodo callback separato perché RedBot converte i postback dei pulsanti inline in normali messaggi in ingresso. Testo e postback usano il payload RedBot `message`. Un vocale Telegram nativo arriva come `type = "audio"` con il `Buffer` OGG/Opus già scaricato da RedBot: KNX AI applica i limiti di dimensione e durata senza scaricarlo una seconda volta, lo trascrive con lo stesso provider OpenAI-compatible descritto sopra e risponde con un payload RedBot `audio` nativo, didascalia testuale e indicazione localizzata della voce generata dall'IA. Quando una scrittura KNX richiede conferma, la risposta resta intenzionalmente un payload testuale `inline-buttons`, perché RedBot non può allegare quei pulsanti allo stesso messaggio vocale. La mappatura d'uscita conserva i dati di tracciamento RedBot `originalMessage`, `chat`, `api` e `client`; anche le vecchie mappature RedBot salvate vengono aggiornate a runtime. RedBot resta una dipendenza opzionale separata.
 
 ### Adapter telecamera rilevati automaticamente
 I pacchetti di telecamere installati possono pubblicare a runtime un adapter per KNX AI. Non esistono selettori né nodi telecamera da collegare a KNX AI: adapter, controller e telecamere disponibili vengono rilevati automaticamente e inseriti nel contesto della chat. `node-red-contrib-unifi-ultimate` è il primo provider supportato; altri pacchetti, come `hikvision-ultimate`, possono registrarsi tramite lo stesso contratto indipendente dal produttore.

package/nodes/locales/zh-CN/knxUltimateAI.html

@@ -78,7 +78,7 @@ Canvas 上的节点状态专门用于显示最近收到的请求，以及 LLM
 
 每条原生语音回复的文字说明都会以本地化的 **AI 生成的语音** 提示开头，Telegram 收件人可以看到该提示。
 
-随附的 **RedBot / node-red-contrib-chatbot (Telegram)** 预设遵循 RedBot 的通用消息格式。将 `chatbot-telegram-receive` 直接连接到 KNX AI，并将输出 3 直接连接到 `chatbot-telegram-send`；无需单独的 callback 节点，因为 RedBot 会把内联按钮的 postback 转换成普通入站消息。输入映射读取 `transport`、`chatId`、`type`、`content` 和 Telegram 语言。输出映射保留 RedBot 的 `originalMessage`、`chat`、`api` 和 `client` 跟踪数据，然后发送 `message` payload，或发送带有确认 `postback` 操作的 `inline-buttons` payload。RedBot 仍是独立的可选依赖项。
+随附的 **RedBot / node-red-contrib-chatbot (Telegram)** 预设遵循 RedBot 的通用消息格式。将 `chatbot-telegram-receive` 直接连接到 KNX AI，并将输出 3 直接连接到 `chatbot-telegram-send`；无需单独的 callback 节点，因为 RedBot 会把内联按钮的 postback 转换成普通入站消息。文本和 postback 使用 RedBot 的 `message` payload。Telegram 原生语音以 `type = "audio"` 到达，其中包含已由 RedBot 下载的 OGG/Opus `Buffer`；KNX AI 无需再次下载即可执行大小和时长限制，使用上文所述的同一个 OpenAI-compatible 提供商进行转录，并返回带文字说明和本地化 AI 生成语音提示的原生 RedBot `audio` payload。当 KNX 写入需要确认时，回复会有意保留为文本 `inline-buttons` payload，因为 RedBot 无法把这些按钮附加到同一条语音消息。输出映射会保留 RedBot 的 `originalMessage`、`chat`、`api` 和 `client` 跟踪数据；旧的已保存 RedBot 映射也会在运行时升级。RedBot 仍是独立的可选依赖项。
 
 ### 自动检测的摄像机适配器
 已安装的摄像机软件包可以在运行时向 KNX AI 发布适配器。无需选择器，也无需将摄像机节点连接到 KNX AI：可用的适配器、控制器和摄像机会被自动检测并加入聊天上下文。`node-red-contrib-unifi-ultimate` 是首个受支持的提供方；`hikvision-ultimate` 等其他软件包可通过同一套厂商无关协议注册。

package/nodes/utils/knxAiTelegramVoice.js

@@ -128,15 +128,47 @@ const resolveTelegramVoiceAllowedOrigin = (message) => {
 }
 
 const applyKnxAiTelegramVoiceInputPresetFallback = ({ preset, message } = {}) => {
-  if (String(preset || '') !== 'windkh-telegrambot' || !message || typeof message !== 'object') return null
+  const normalizedPreset = String(preset || '')
+  if (!['windkh-telegrambot', 'redbot-telegram'].includes(normalizedPreset) || !message || typeof message !== 'object') return null
   const telegram = message.payload && typeof message.payload === 'object' ? message.payload : null
-  if (!telegram || telegram.type !== 'voice') return null
+  if (!telegram) return null
   const chatId = telegram.chatId
   if (chatId === undefined || chatId === null || chatId === '') return null
   const original = message.originalMessage && typeof message.originalMessage === 'object'
     ? message.originalMessage
     : {}
   const voice = findTelegramVoiceMetadata(message)
+
+  if (normalizedPreset === 'redbot-telegram') {
+    const redbotType = String(telegram.type || '').trim().toLowerCase()
+    if ((redbotType !== 'audio' && redbotType !== 'voice') || !Buffer.isBuffer(telegram.content)) return null
+    const mediaType = normalizeVoiceMediaType(voice.mime_type || telegram.mimeType)
+    message.sessionId = String(chatId)
+    message.language = (original.from && original.from.language_code) ||
+      (original.message && original.message.from && original.message.from.language_code) ||
+      telegram.language ||
+      message.language ||
+      ''
+    message.topic = 'ask'
+    delete message.prompt
+    message.knxAi = Object.assign({}, message.knxAi, {
+      sessionId: String(chatId),
+      voiceInput: {
+        source: 'telegram',
+        originalType: 'voice',
+        transport: 'redbot-buffer',
+        data: telegram.content,
+        fileId: String(voice.file_id || '').trim(),
+        mediaType,
+        filename: sanitizeVoiceFilename({ filename: telegram.filename || voice.file_name, mediaType }),
+        durationSeconds: Math.max(0, Number(voice.duration || telegram.duration) || 0),
+        fileSize: Math.max(0, Number(voice.file_size || telegram.fileSize) || telegram.content.length)
+      }
+    })
+    return message
+  }
+
+  if (telegram.type !== 'voice') return null
   const mediaType = normalizeVoiceMediaType(voice.mime_type || telegram.contentType || telegram.mimeType)
   const fileId = String(telegram.content || voice.file_id || '').trim()
   const weblink = String(telegram.weblink || message.weblink || '').trim()
@@ -175,6 +207,7 @@ const redactKnxAiTelegramVoiceLocations = (message) => {
   if (!message || typeof message !== 'object') return message
   if (message.payload && typeof message.payload === 'object') {
     message.payload = Object.assign({}, message.payload)
+    if (Buffer.isBuffer(message.payload.content)) message.payload.content = ''
     delete message.payload.weblink
     delete message.payload.path
   }
@@ -182,6 +215,7 @@ const redactKnxAiTelegramVoiceLocations = (message) => {
   delete message.path
   if (message.knxAi && message.knxAi.voiceInput && typeof message.knxAi.voiceInput === 'object') {
     const voiceInput = Object.assign({}, message.knxAi.voiceInput)
+    delete voiceInput.data
     delete voiceInput.weblink
     delete voiceInput.path
     message.knxAi = Object.assign({}, message.knxAi, { voiceInput })
@@ -258,6 +292,16 @@ const fetchKnxAiTelegramVoice = async ({
   }
   const mediaType = normalizeVoiceMediaType(source.mediaType)
   const filename = sanitizeVoiceFilename({ filename: source.filename, mediaType })
+  if (Buffer.isBuffer(source.data)) {
+    if (!source.data.length) throw new Error('Telegram returned an empty voice message')
+    if (source.data.length > maxBytes) throw new Error(`Voice audio exceeds the ${Math.round(maxBytes / (1024 * 1024))} MB limit`)
+    return {
+      data: Buffer.from(source.data),
+      mediaType,
+      filename,
+      source: String(source.transport || 'telegram-buffer')
+    }
+  }
   const weblink = String(source.weblink || '').trim()
   if (weblink) {
     let parsed
@@ -409,11 +453,15 @@ const postKnxAiVoiceSpeech = async ({
 }
 
 const applyKnxAiTelegramVoiceOutputPresetFallback = ({ preset, message, inputMessage } = {}) => {
-  if (String(preset || '') !== 'windkh-telegrambot' || !message || typeof message !== 'object') return message
+  const normalizedPreset = String(preset || '')
+  if (!['windkh-telegrambot', 'redbot-telegram'].includes(normalizedPreset) || !message || typeof message !== 'object') return message
   const audio = message.knxAi && message.knxAi.audio
   if (!audio || !Buffer.isBuffer(audio.data) || !audio.data.length) return message
   const currentPayload = message.payload && typeof message.payload === 'object' ? message.payload : null
-  if (currentPayload && (currentPayload.type === 'voice' || currentPayload.type === 'photo')) return message
+  if (currentPayload && (currentPayload.type === 'voice' || currentPayload.type === 'audio' || currentPayload.type === 'photo')) return message
+  if (normalizedPreset === 'redbot-telegram' && currentPayload && currentPayload.type === 'inline-buttons') return message
+  const confirmation = message.knxAi && message.knxAi.confirmationRequest
+  if (normalizedPreset === 'redbot-telegram' && confirmation && confirmation.required === true) return message
   const source = inputMessage && typeof inputMessage === 'object'
     ? inputMessage
     : message.inputMessage && typeof message.inputMessage === 'object'
@@ -435,6 +483,28 @@ const applyKnxAiTelegramVoiceOutputPresetFallback = ({ preset, message, inputMes
     .filter(Boolean)
     .join('\n')
     .slice(0, 1024)
+
+  if (normalizedPreset === 'redbot-telegram') {
+    const transport = currentPayload && currentPayload.transport
+      ? currentPayload.transport
+      : sourcePayload.transport || 'telegram'
+    const userId = currentPayload && currentPayload.userId !== undefined
+      ? currentPayload.userId
+      : sourcePayload.userId
+    message.payload = {
+      transport,
+      chatId,
+      type: 'audio',
+      inbound: false,
+      content: audio.data,
+      filename: sanitizeVoiceFilename({ filename: audio.filename, mediaType: audio.mediaType, fallback: 'knx-ai-reply' }),
+      mimeType: normalizeVoiceMediaType(audio.mediaType),
+      caption
+    }
+    if (userId !== undefined) message.payload.userId = userId
+    return message
+  }
+
   const options = Object.assign({}, currentPayload && currentPayload.options ? currentPayload.options : {})
   if (caption) options.caption = caption
   message.payload = {

package/package.json

@@ -3,7 +3,7 @@
   "engines": {
     "node": ">=20.18.1"
   },
-  "version": "6.3.29",
+  "version": "6.3.30",
   "description": "KNX Ultimate is the most advanced KNX integration for Node-RED, providing secure KNX/IP communication, routing, ETS project import, Philips Hue, Matter Controller and Matter Bridge (control matter device via KNX and expose KNX GA via Matter), MQTT and Modbus adapters, diagnostics with AI, virtual devices, and powerful automation nodes. Build professional, reliable, and scalable smart home and building automation projects with minimal effort.",
   "files": [
     "nodes/",
@@ -150,4 +150,4 @@
     "vite": "^7.3.6",
     "vue": "^3.5.41"
   }
-}
+}

package/resources/KNXAIChatAdapterMappings.js

@@ -193,15 +193,13 @@ return msg;`
       id: 'redbot-telegram',
       title: 'RedBot / node-red-contrib-chatbot (Telegram)',
       inputCode: `// RedBot Telegram Receiver -> KNX AI
-// RedBot normalizes Telegram text and inline-button postbacks in msg.payload.
+// RedBot normalizes Telegram text, voice audio and inline-button postbacks in msg.payload.
 const redbot = msg.payload;
 if (!redbot || typeof redbot !== 'object') return;
 if (redbot.transport && redbot.transport !== 'telegram') return;
 
 const chatId = redbot.chatId;
-const content = typeof redbot.content === 'string' ? redbot.content.trim() : '';
-if (chatId === undefined || chatId === null || content === '') return;
-if (redbot.type !== 'message') return;
+if (chatId === undefined || chatId === null) return;
 
 msg.sessionId = String(chatId);
 msg.language =
@@ -210,6 +208,37 @@ msg.language =
     msg.language ||
     '';
 
+const redbotType = String(redbot.type || '').trim().toLowerCase();
+if ((redbotType === 'audio' || redbotType === 'voice') && Buffer.isBuffer(redbot.content)) {
+    const original = msg.originalMessage && typeof msg.originalMessage === 'object'
+        ? msg.originalMessage
+        : {};
+    const voice = original.voice && typeof original.voice === 'object'
+        ? original.voice
+        : original.message && original.message.voice && typeof original.message.voice === 'object'
+            ? original.message.voice
+            : {};
+    msg.topic = 'ask';
+    msg.knxAi = Object.assign({}, msg.knxAi, {
+        sessionId: String(chatId),
+        voiceInput: {
+            source: 'telegram',
+            originalType: 'voice',
+            transport: 'redbot-buffer',
+            data: redbot.content,
+            fileId: String(voice.file_id || '').trim(),
+            mediaType: String(voice.mime_type || redbot.mimeType || 'audio/ogg'),
+            filename: String(voice.file_name || redbot.filename || 'telegram-voice.ogg'),
+            durationSeconds: Math.max(0, Number(voice.duration || redbot.duration) || 0),
+            fileSize: Math.max(0, Number(voice.file_size || redbot.fileSize) || redbot.content.length)
+        }
+    });
+    return msg;
+}
+
+const content = typeof redbot.content === 'string' ? redbot.content.trim() : '';
+if (redbotType !== 'message' || content === '') return;
+
 const action = content.toLowerCase();
 if (action === 'confirm' || action === 'cancel') {
     msg.topic = action;
@@ -300,6 +329,33 @@ if (image && Buffer.isBuffer(image.data)) {
     return msg;
 }
 
+const confirmation = msg.knxAi && msg.knxAi.confirmationRequest;
+const audio = msg.knxAi && msg.knxAi.audio;
+if (audio && Buffer.isBuffer(audio.data) && !(confirmation && confirmation.required === true)) {
+    const voiceLanguage = String(msg.knxAi.language || (source && source.language) || '').trim().toLowerCase().split(/[-_]/)[0];
+    const disclosureLabels = {
+        de: 'KI-generierte Stimme',
+        en: 'AI-generated voice',
+        es: 'Voz generada por IA',
+        fr: 'Voix générée par l’IA',
+        it: 'Voce generata dall’IA',
+        zh: 'AI 生成的语音'
+    };
+    const disclosure = disclosureLabels[voiceLanguage] || disclosureLabels.en;
+    msg.payload = {
+        transport: sourcePayload.transport || 'telegram',
+        chatId: chatId,
+        type: 'audio',
+        inbound: false,
+        content: audio.data,
+        filename: audio.filename || 'knx-ai-reply.ogg',
+        mimeType: audio.mediaType || 'audio/ogg',
+        caption: [disclosure, content].filter(Boolean).join('\\n').slice(0, 1024)
+    };
+    if (sourcePayload.userId !== undefined) msg.payload.userId = sourcePayload.userId;
+    return msg;
+}
+
 const redbotPayload = {
     transport: sourcePayload.transport || 'telegram',
     chatId: chatId,
@@ -309,7 +365,6 @@ const redbotPayload = {
 };
 if (sourcePayload.userId !== undefined) redbotPayload.userId = sourcePayload.userId;
 
-const confirmation = msg.knxAi && msg.knxAi.confirmationRequest;
 if (confirmation && confirmation.required === true && Array.isArray(confirmation.actions)) {
     redbotPayload.type = 'inline-buttons';
     redbotPayload.buttons = confirmation.actions.map(function (action) {