KNX alarms on WhatsApp / Telegram

Need to connect KNX and WhatsApp / Telegram? The Weble WBox routes KNX WhatsApp / Telegram natively: one gateway speaks both protocols and maps data points in real time — no PC, no middleware, no cloud dependency.

The protocols

KNX

KNX is the worldwide standard for home and building control, running over twisted-pair, IP or RF.

KNX driver →

WhatsApp / Telegram

The Internet Messaging driver sends alarms and notifications from the gateway to WhatsApp and Telegram — individual numbers or named groups — and reads replies for acknowledgement, with no WhatsApp Business account and no Telegram bot.

WhatsApp / Telegram driver →

Typical use case

A KNX installation reports its faults on the bus — a thermostat's frost alarm, a leak detector, a heating or ventilation fault — but without a BMS, nobody sees them. The WBox listens to the group addresses and pushes each alarm to WhatsApp or Telegram: to the caretaker, the facility manager or a team group. No supervision system needed — the gateway is the installation's notification layer, and replies flow back into its logic for acknowledgement.

Example deployment

Typical scenario A KNX building without a head-end, alarms on the caretaker's phone A small office building runs on KNX with no BMS. The WBox listens to the fault group addresses — heating, ventilation, leak detectors — and messages the caretaker on WhatsApp; critical alarms also go to the installer's maintenance group, and a reply acknowledges them. Technical documentation →

How the WBox bridges KNX and WhatsApp / Telegram

The KNX driver listens to the relevant group addresses — DPT 1.005 alarm objects, binary states, DPT 9.x measurements against thresholds — over KNX TP (WBox S485 KNX) or KNXnet/IP. A Blockly or JavaScript step filters, debounces and formats the message, then writes it to %im:whatsapp/… or %im:telegram/… — an individual number or a named group. Sending goes through the Weble cloud messaging service over a secure outbound link, with no WhatsApp Business account and no Telegram bot; replies arrive on #lastMessage to acknowledge or escalate.

Step by step

Connect the WBox to the KNX installation — KNX TP with the WBox S485 KNX, or KNXnet/IP on any model — and to the internet (Ethernet or LTE).
Enable the KNX and Internet Messaging drivers — licence-activated, no extra hardware.
Pick the group addresses to watch: alarm objects (DPT 1.005), fault states, measurements with a threshold.
Write the alarm rule in Blockly or JavaScript: format the message and send it to %im:whatsapp/+417… or a group like %im:whatsapp/Maintenance — Telegram works the same way.
Test end-to-end: trigger an alarm object, receive the message, reply — the reply appears on #lastMessage for acknowledgement logic.

Example mapping

A worked example in a building without a BMS:

KNX 4/0/1 heating fault (DPT 1.005) → WhatsApp group %im:whatsapp/Maintenance
KNX 2/3/7 leak detector (DPT 1.005) → Telegram %im:telegram/+41791234567
Reply in the group → #lastMessage address, read back by the gateway logic (acknowledgement)

Capacity & limits

KNX — KNX exposes the installation's group objects; a TP line carries up to 64 bus devices, extended through lines, areas and KNXnet/IP.
WhatsApp / Telegram — Internet Messaging sends through the Weble cloud messaging service over a secure outbound link — recipients are individual numbers or named groups, with replies routed back to the gateway; no WhatsApp Business account, no Telegram bot, no inbound port.

On the WBox, a driver licence enables the whole protocol — there is no artificial per-point tier to unlock. Capacity scales with the gateway model, from the compact S103 to the E413: you are bounded by the field bus, not by your licence.

Frequently asked questions

Do I need a WhatsApp Business account or a Telegram bot?

No. Messages are sent through the Weble cloud messaging service over a secure outbound connection — you configure recipients on the WBox and it works, with no Meta or Telegram-side setup and no bot to host.

My KNX installation has no BMS — do I need one for alarms?

No, that is the point: the WBox listens to the bus directly and is the notification layer. Alarm objects, faults and thresholds go straight to WhatsApp or Telegram without any supervision system.

KNX TP or KNX IP — which does the WBox support?

Both. KNX TP (twisted pair) via the WBox S485 KNX model, which has the interface on board, or KNXnet/IP on any WBox.

Can the recipient acknowledge a KNX alarm by replying?

Yes. Replies come back on the driver's #lastMessage address, where your logic reads them — an 'OK' can stop the repetition, log the acknowledgement or escalate to the next person.