BACnet/WS  and BACnet/IBM-Watson

Try it your self against a live DINGO setup in our laboratory

Release the power by simplicity


The DINGO BACnet stack includes an app called "BACnet to IBM Watson Gateway". This easy to configure gateway is used to enable MQTT publishing of BACnet properties to IBM Watson IoT Platform. It also enables commanding from Watson to BACnet devices. Last but not least important, this gateway enables BACnet Web Service requests (BACnet/WS) to be tunneled from Watson to BACnet devices.
For further details of how to configure and use this gateway, refer to our recipe at IBM-Watson web site here... 


Below is a link to a simple test WEB page. In this simple example you can browse a BACnet network at our laboratory, pick a particular object and subscribe to its COVs (Change Of Value). Try it for example for the temperatures. You can have this web page open at the same time as the dashboard example above and see how those interact with the same physical setup. 
This example explains how easy it is to make a web-page using our BACnet/WS implementation to subscribe to push-notifications from the BACnet network (no polling is used!)

If you are a java-script programmer, coding COV subscriptions is relatively easy. Right click somewhere in the test-page (testclient.htm)  and select "View Frame Source". Search for the function:
Study the code and you will soon find out how things are done.


BACnet/IoT implements the cutting edge BACnet/WS part of the BACnet standard. This is very important for extending BACnet to the world of IoT.

The BACnet/WS module is a free standing software module. It is only needed to be installed on one device (or computer) in the network of devices to be accessed from the LAN or WAN (the Internet). This module does not only enable BACnet/WS access to our DINGO and WINGO products, but also any other BACnet device on the network, from whatever vendor it is.

BACnet/WS is very easy to use. You can actually test it from your browser with URLs like this:
where ".blt" is a shortcut of ".bacnet/.local/.this" indicating the local device. Notice the ".local" means "the local network" that can be replaced for a network number in a more complex BACnet setup.

This would return this response:
This is the list of all devices on the local BACnet network.

Then dig deeper and investigate for example device with ID 104301:
Would return this response:
This is the list of all objects in device 104301.

Let us investigate the first object:
The result will be:
Those are all the properties in analog-input with ID 48.

Now you can re-poll the temperature very easily:
This will result in the temperature as "plain" text:


Trend Logging is one of the most important feature in many IoT use-cases. We have specialized in Trend Logging for more than 20 years. Therefore we did not leave it out when it came to our BACnet implementation.
So let us try retrieving some Trend Logs via BACnet/WS. Note that this can also be done via the BACnet to Watson gateway discussed earlier, using the BACnet/WS tunnel.
By browsing the network similarly as shown above, you can soon find some trend log objects. For example there some in device with ID 104000 that log temperatures.
Let us investigate the one that logs the outside temperature, which is trend-log with ID 182:
You should get a list of all it's properties:
      "description":"TrendLog for DinGo-C inner temperature (the inner 1-Wire sensor)",
As you can see there is a lot of properties. Study those and compare to the standard as you like. It is not the intention of this short demo do go into any details here. But in short, this is a an TL object that logs the outside temperature every 15 minutes (at 00:00, 00:15 .... 23:45).
Now let us request for logged data from the log-buffer property. This is done with the BACnet Read Range service, where you can do simple-to-complex queries to retrieve logged time-series data.
The BACnet/WS query below retrieves the first 100 records after 16th Jan. 2017 00:00.
Or as we are dealing with the local device:
The response will be returned:


As you can't do PUT request from your Web browser, you need tools like Fiddler or Postman app for Google Chrome, to test BACnet/WS write commands. Or you can code your own program.

A typical PUT request to switch a relay would be for example:

with this payload to switch it off:
   { "$base": "integer", "$value" : "0" }
or this for switching it on:
   { "$base": "integer", "$value" : "1" }
or this for setting at don't care at the given priority in the path (see for example "?priority=8" in the example path above).
   { "$base": "Null" }