RTLS gateways, smart beds, infusion pump servers and fridge probes already produce the data. ConnectMQ brings it onto one MQTT broker, so your asset tracking app, CMMS and facilities dashboards all work from the same live picture.
No card required
PUBLISH hospital/campus-a/pump/ip-0412/location
{"ward":"4E","room":"412","zone":"corridor-b","state":"available","gw":"gw-4e-07","ts":"2026-10-22T08:15:03Z"}QoS 1 · TLS 8883 · PUBACK
Nurses lose time hunting for infusion pumps and wheelchairs, biomedical engineering cannot find the devices due for preventive maintenance, and a medication fridge that drifted out of range overnight is noticed at the morning round. The data exists — in RTLS, device vendor and BMS silos that do not talk to each other.
BLE or UWB tags on pumps, beds and wheelchairs are picked up by RTLS gateways; fridges and freezers carry temperature probes; smart beds and pump servers expose status.
Each gateway or integration publishes location and status changes per site, asset type and asset ID, with the last known state retained.
Threshold rules raise an alert when a fridge leaves its range or a gateway goes silent; the live dashboard shows equipment by ward and floor.
Your asset tracking app shows where the nearest free pump is, the CMMS receives usage and location for PM planning, facilities follows up on fridge alerts.
Retained messages give every new subscriber the current location and status of each asset immediately, without waiting for the next tag beacon.
Publish/subscribe lets the tracking app, CMMS, BMS and your data platform consume the same messages independently — no point-to-point links per vendor.
Each RTLS gateway and integration has its own credentials, and per-topic ACLs let it publish only to its own topics, while the CMMS can read but not write.
Threshold rules and notifications cover fridge ranges and battery levels, and Last Will flags a gateway that drops off the network.
hospital/campus-a/pump/ip-0412/location
hospital/campus-a/pump/ip-0412/status (retained)
hospital/campus-a/fridge/pharm-3b/temp
hospital/campus-a/rtls/gw-4e-07/status (retained)Many BLE and UWB gateways and location engines can publish MQTT natively — point them at your ConnectMQ endpoint with TLS and their own credentials. Where a system only offers a REST API, a small bridge service polls it and publishes the changes to MQTT.
Yes, as the data transport. Probes or gateways publish readings, threshold rules alert when a fridge leaves its range, and your monitoring or quality system keeps the records. Validation of the overall monitoring system stays with your organisation.
Yes. With MQTT every system subscribes to the topics it needs: the CMMS takes usage hours and locations, the BMS takes fridge and room data, and your tracking app takes everything — all from the same messages.
Start on the Free plan — no card required — connect your first devices today and upgrade when you go live.
