Need to connect BACnet and WhatsApp / Telegram? The Weble WBox routes BACnet WhatsApp / Telegram natively: one gateway speaks both protocols and maps data points in real time — no PC, no middleware, no cloud dependency.
BACnet (BACnet/IP, MS/TP) is the standard for building management systems and HVAC supervision.
BACnet driver →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 →The BMS knows the fault the moment it happens — a pump trip, a frost alarm, a ventilation failure — but nobody sits in front of the head-end at night or on weekends. The WBox watches the BACnet objects and pushes the alarm straight to WhatsApp or Telegram: to the on-call technician's number, or to a maintenance group the whole team follows. Recipients can reply to acknowledge, and the reply flows back into the gateway logic — a notification chain with no extra app to install and no alarm server to maintain.
The BACnet driver polls the supervised objects (BACnet/IP or MS/TP) or receives COV notifications; a logic step — Blockly or JavaScript — decides what deserves a message, formats the text and writes it to an Internet Messaging address: %im:whatsapp/+41791234567 for a person, %im:whatsapp/Maintenance for a named group, telegram likewise. Messages travel through the Weble cloud messaging service over a secure outbound connection — no WhatsApp Business account, no Telegram bot, no inbound port. Replies arrive on the driver's #lastMessage address, so an 'OK' from the technician can silence the repeat or escalate to the next person.
%im:whatsapp/+417… or a group like %im:whatsapp/Maintenance — Telegram works the same way.#lastMessage for acknowledgement logic.A worked example on a plant room:
Binary Input 4 (pump fault) → WhatsApp group %im:whatsapp/MaintenanceAnalog Input 2 over its limit (flow temperature) → Telegram %im:telegram/+41791234567#lastMessage address, read back by the gateway logic (acknowledgement)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.
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.
Yes. Replies come back to the gateway 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 on call.
Both work: individual numbers in international format (+41…), or a named group — the whole maintenance team sees the alarm and who acknowledged it. A message can also target one member of a group.
A WBox gateway with the BACnet and Internet Messaging driver licences, plus an internet connection (Ethernet or LTE). It supervises any BACnet/IP or MS/TP installation — no alarm server, no extra app for the recipients.
One WBox gateway with these two driver licences:
Find the right WBox gateway for your installation, or get in touch to validate your case.
Configure my gateway© 2026 Weble Sàrl. All rights reserved. General conditions