Did you know that your internet is out of date?
Your browser is out of date, and may not be compatible with our website.
Just click on the icons to download a compatible browser.
By closing this window you acknowledge that your experience on this website may be degraded.
-
Global Pages
-
Asia Pacific
-
Europe
-
North America
- |
- Niagara Community
- |
- Niagara Marketplace
- |
- Niagara Resource Center
- |
- Tridium University
- |
- VYKON
- |
-
Global Pages
-
Asia Pacific
-
Europe
-
North America
- |
- Niagara Community
- |
- Niagara Marketplace
- |
- Niagara Resource Center
- |
- Tridium University
- |
- VYKON
- |
You are browsing the product catalog for
You are viewing the overview and resources for
- Candela IoT Inc
- GeoBMS API Driver for Niagara
GeoBMS API Driver for Niagara
Connect a Niagara station to the GeoBMS, a platform-independent device points read-write REST API protocol. The driver discovers the devices of every other driver in the station and mirrors them and their points into GeoBMS. Live values and Niagara histories are exported automatically, and values set in GeoBMS are written back to the source points in Niagara.
CONTACT SELLER
Enter the GeoBMS API key in the network's Authentication view; the driver checks it against the GeoBMS API and stores it encrypted in the station. Device discovery lists every device under the station's other networks (BACnet, Modbus, Tesla Fleet, Google Home and so on), and point discovery offers its points with their facets and enum ranges. Each added device and point becomes a GeoBMS entity, linked to its device and kept in sync across restarts without duplicates. Per point, the data source is live (changes posted as they happen), history (records exported with their own timestamps, including revisions and late backfill) or auto, which uses the point's history when it has one. A value set in GeoBMS for a writable point is commanded to the source point, so its own driver writes it to the device.
PRICING:
Niagara 4 (N4.14+), per station: $1,000
Niagara 5 (N5.0+), per station: $1,000
Annual support and updates: included
FAQs
Q: What do I need? A: A JACE or Supervisor on Niagara 4.14 or later, or Niagara 5.0 or later, with outbound HTTPS access to the GeoBMS API, and a GeoBMS account with an API key, either the cloud or on-prem instance.
Q: Which devices can be sent to GeoBMS? A: Any device under another driver network in the same station, from Tridium's drivers or third-party ones. The GeoBMS driver reads and commands the source points through Niagara, so it doesn't talk to the field devices itself.
Q: Where is the API key kept? A: Encrypted in the station database. The key field is cleared after you enter it, and the key is never logged.
Q: How are histories exported? A: Records go to GeoBMS with their own timestamps. Each poll sends new and recently revised records, an hourly sweep picks up late backfill, and a Reexport History action on the device sends everything again.
Q: What if a device or point is deleted in GeoBMS? A: The matching Niagara point goes into fault and stops syncing instead of recreating it. The device's Relink action reconnects it on purpose.
Q: How often are points updated? A: On the network's configurable poll frequency. Writes are sent immediately.
Requirements:
N4.14+ and N5.0+
Platform:
JACE; Supervisor
Sign up to receive exclusive communications about offerings, events, news, and related topics via email and other forms of electronic communication.
Copyright © 2026 Tridium, Inc.