User Console

This article details the functionality of the scheduling module.

General information

A new major feature is now available on the Wattsense console through the two new products Tower Control and Bridge Control. This functionality allows weekly time programming and offers the possibility of defining the occupancy schedule of your building.

Here is a basic example scenario that can be easily programmed : different setpoints are assigned depending on the occupancy of the room :

Of course, the Wattsense module allows to create much more complex configurations, with more slots, more slot types in association with all kinds of writable properties.

For more information, you can use the following links :

Know more about the Wattsense Control Range

Visit our product page for detailed features and pricing information

Without the control range, you will be able to access the creation of weekly schedules but you will not be able to associate properties with them or therefore specify setpoint values.

How to program a schedule ?

In the Wattsense console, in the configuration tab, select the Scheduling button.

Below the short demo video that demonstrates the functionality, click "Create your first schedule" to start the programming sequence :

General information settings

First of all, fill in the fields Name and Description of the schedule. Then select the Box timezone. This point is important as the schedule will run according to the local time defined in the box.

A notification appears if the time zone indicated in the field above does not match the box internal time zone.

Slot settings

It is now a matter of specifying how the value of the properties of the equipment will be set depending on the day and time of day.
The first step consists of defining “status” periods (e.g. a building is occupied or not).
To complete this programming table, a complete weekly calendar is displayed :

Click on the day card (ex Monday) to define the schedule :

Select the time slot (from start time to end time) and specify the type of this period. Several slots can be added to a day (by clicking on the + button at the end of the line).

The types themselves can also be customized (click the "Occupied" button in this example)

You can custom the type labels as well as the associated colors.

Once you have defined the slots for a day, you can duplicate them on other days using the copy button :

You must also specify the default status type that will be applied outside the specified slots.

If you have an empty scheduler slot, the default slot will work. If you do not want the default type of slot to operate you will have to fill all slots. The slots are day specific. A slot can not start on Monday and finish on Tuesday. You will have to have two slots, the first till the end of the day on Monday. And the second that starts on Tuesday at 00:00.

Then click on the next button to access the properties and setpoints configuration.

Exceptions settings

In addition to the classic calendar, you can add exceptions, for example bank holidays or any other exceptional events.

To add an exception, click on the "Add exception" button, and fill in the parameters :

You can specify in single slot type : it will be applied during all the exception period. Or you can specify multiple slots for the period :

Please note that exceptions are shared across all schedules in your box, this means that you do not need to recreate exception configurations for each schedule, you can reuse an existing template. All exceptions are listed in the screen below. So you just need to select the exception schedule you need. It will be applied to your current schedule.

Properties settings

The next step is to associate the property values ​​with the time slot type. Click on Select properties :

The following page presents all the equipment connected to the box.
1) You can filter on device name
2) You can filter on property names

Then select the properties that will be modified according to the schedule (Only writable properties are displayed in this list). 

The last step is to define the values ​​of these properties for each slot. Slots types are displayed in the table header :

If you want to send a downlink to a Lorawan device that is not supported by the Easy Downlink feature. Please use the "Encoded Downlink message" and search for the correct hexadecimal payload to send. If you set a data that do not match a BACnet data type, e.g., (write an analogue value on multistate value or binary value) : there will be an error in the box when writing the value. It should be listed under Logs/Events.

You can also specify the application period for each setpoint : click on the label "All year" if you want to modify the default parameters :

then choose "Specific Period" and click on "Select date range"

To select a period in the calendar form, first click on the first day, then Shift+click on the last day of the period. 

A small bulk edit feature is also available to modify multiple setpoints simultaneously : select the properties via their check boxes (1) and click on the action button / Modify setpoint values ​​(2)

Fill in the setpoint values :

The properties are updated :

Once the fields are filled, you can save the schedule :

and send it to the box :

If the operation is successful, the following message is displayed :

If you update an existing scheduler and push the configuration, a service will restart on the box which will rewrite the value at that specific time.

The mains page lists all the existing schedules :

From this page, you can activate the schedule (enable button), modify the calendar and the properties,  but also duplicate the schedule.

The planner can also be viewed in calendar format (Calendar View button)

If the box starts in the middle of a slot (e.g. Monday 11:00 a.m. in our example), the instructions are automatically sent without waiting for the next slot.

If you need any additional information, please contact us here.

The changes below are introduced with version 6.2.2 of the firmware.

This article describes the different Bridge connection status in the Wattsense console header panel.

Modifications have been made to this connection module mainly to remove the mandatory delay of 600 s between two data sendings (gateway) when in LAN configuration (second part of the article).

A – Bridge with default GSM configuration

Case A-1 : Bridge is offline

The red indicator shows that the box is offline and the following instructions are displayed :

You may have to wait around 10 to 20 seconds before GSM connections are established due to synchronization tasks.

Case A-2 : Bridge is connected via the GSM network

The box is online. Displayed symbols have the following meaning :

	GSM Antenna active
	Cellular network signal strength

The data is transmitted to the MQTT broker via the cellular connection.

If you are not using a LAN connectivity, when the toggle button will goes OFF, the data will stop being transmitted via GSM.

Once connected, you can send a configuration from the console to the Bridge as well as display equipement properties in the console during 1 hour (Live Data Tab). Data will be removed from the console atfer this period.

B – Bridge is connected via Ethernet/IP network

In addition to the default cellular mode, you can connect the Bridge to the internet via a LAN Ethernet cable.

In this case, several connection states are possible.

Case B-1 : Bridge connected to internet thanks to Ethernet/IP network. No data are transmitted.

In this case, you can send a configuration from the console to the Bridge, but you won't receive data into the live data Tab. Data are transmitted to customer MQTT broker through the Ethernet/IP network.

The following instructions are displayed :

Case B-2 : Bridge has Ethernet/IP connection. GSM connectivity is activated.

In this case, the Bridge is connected via GSM (cf paragraph A-2 above)

Case B-3 : if no GSM network is available, data and configuration are sent through the Ethernet/IP network.

For more information, feel free to contact us here.

This article explains how to modify a LoRaWAN property in a simple way.

Direct update of a LoRaWAN property from the Live Data

Until now, the standard way to update a LoRaWAN property was to send its new value via a complete downlink (combination of raw encoded payload in Hexadecimal and it's respective port). (See complete article on the subject).

A new feature arrives with the firmware 6.0.3 APPS which allows some properties to be written as a simple value (example : 12) instead of a complex downlink message (example : 401E20:1). The encoding part is done by the software.

Please note that for the moment, this feature is available from version 6.0.3 APPS and only for the devices / properties below :

	ADEUNIS	DRY CONTACTS AND DRY CONTACTS 2	• Output 1, 2, 3, 4 : current state (0: OFF/OPEN; 1: ON/CLOSED)
	MCF88	MCF-LW13IO	• Output 1 state (0 : False 1 : True)
	MCLIMATE	FAN COIL THERMOSTAT	Target temperature Operation mode (00: Ventilation ; 01: Heating ; 02: Cooling) Fan Speed (00: Automatic ; 01, 02: Low ; 03, 04: Medium ; 05, 06: High) Device Status (00: Turn off the device ; 01: Turn on the device) Cooling set-point not occupied Heating set-point not occupied Fan Speed not occupied (00: Low; 01: Automatic; 02: Do not change) External sensor temperature Allowed operational mode (00:Ventilation/Heating/Colling; 01:Ventillation/Heating; 02:Ventillation/Cooling) Device status on Set Digital IO1/IO2 (Refer to equipment user guide for documentation) Automatic temperature control mode (00: Automatic temp. control mode deactivated; 01: Automatic temp. control mode activated)
	MCLIMATE	VICKI	Target temperature External temperature Child Lock Keep alive period Operational mode Valve openness
	MCLIMATE	WIRELESS THERMOSTAT	Target temperature
	MICROPELT	MLR003	Target temperature Ambient temperature
	MILESIGHT	WT101	Target temperature Reporting Interval Temperature Control Mode Valve Opening Percentage Child Lock
	THERMOKON	SAB07	Target temperature External temperature Child Lock
	WATTECO	IN'O	Output 1, 2, 3, 4 (1/True: ON, 0/False: OFF)
	WATTECO	PILOT WIRE	• Output state (0:comfort, 1:economic, 2:antifreeze, 3: stop, 4:comfort -1°C, 5:comfort -2°C)

How to proceed ?

Example for the Target temperature property :

After adding one of the two sensors above in the configuration Tab of the Wattsense Console, the Target temperature appears as a Read and Write property.

In order to send a new target temperature, go to the Live Data page, and click on the "Set a Value" button.

and save.

The target temperature is updated.

The target temperature value must be within the appropriate range (cf manufacturer documentation)

Update a LoRaWAN property through a Gateway (BACnet/Modbus/MQTT)

LoRaWAN properties can be also updated via gateways. 

For BACnet getaways, the full procedure is explained here : How to send a downlink from a BACnet client ?
Similar to the Live Data feature, the properties above can be written here as a simple value (implementation of an integer format) instead of a full downlink message.

How to proceed with existing configuration ?

If you already have one of these sensors in your configuration and you want to take advantage of the new feature, please contact the Wattsense support.

Next Step

Likewise, more sensors and properties will be added very soon to complete the LoRaWAN property editing process. If you are interested in this new feature, please let us know your suggestions.

If you need any information, please contact us: here 

This article explains how to forward a property from an equipement to another device.

It is possible to redirect a property from one device to another even if their respective protocols are different. For example, redirection is possible between BACnet equipment and LoRaWAN equipment, or LoRaWAN to KNX Synco... The goal of this feature is to sent the property value to another device of your choice.

This function is not applicable from LoRaWAN to LoRaWAN

For example, a Synco device needs an external temperature value but no temperature sensor is connected to it. At the same time, a LoRaWAN sensor with this information is available in the Wattsense Console. The idea is to redirect the temperature property to the corresponding register of the Synco.

How to proceed ?

Go to the configuration Tab of the Wattsense console, choose the device and property to redirect. Then click on the edit button.

On the properties page, click to the label Advanced :

Then choose equipment/property target.

And that’s all …
Then in the Live Data Tab, a redirect symbol indicates that the temperature property is forwarded.

You will have to wait for the next update of the source device to check if the rediction process is correct. (Especially if the source device is LoRaWAN, it may take a while before the update is visible).

Before trying to redirect a property into another, please verify the format of the data. The forwarding process will success if the source and the destination properties format are consistent (float -> float, int16 -> int16, …)

If you encounter any difficulties with the redirection module, do not hesitate to contact the Wattsense support.

This article describes some improvements that have been made to the Graph section of the Console to make the interface easier to use.

Quick overview

1 – The default abscissa time goes from 1 to 15 days to have a better view of the evolution of indicators.
2 – Two arrows have been added to access the view of the next or previous period.
3 – A direct shortcut to the export function has been added on this page.
4 – All the curve’s properties are available from the property card
5 – A new function of interval calculation and display has been added.
6 – The right panel which contains all the graph attributes can be hidden if necessary.

Change the properties of the curve

Clicking on the property card opens a new window which allows you to modify the attributes of the matching curve.

Here, you can change the :

• Chart type (curve, steps, bars)
• The Y axis. You can link the curve to a Y left axis or Y right axis. (in the case of 2 curves on a single graph with different units for example)
• The end marker of the line segment plotted on the chart.

Interval curves

You can now simulate a metering function by showing a new calculated curve based on an existing property. The calculation mode is similar to virtual properties.

For example, if you want to have the interval view of an existing index, just choose the interval period in the Interval section and select the source data (index property)

Create a virtual property from the graph interface

From this point, you just have to click on the "+" button to create a virtual property.

The next steps are explained in the article dedicated to virtual properties.

The graphs allow you to visualize the values ​​over 8 months. The creation of a Virtual Properties allows you to historicize the values ​​beyond 30 days and thus make an archive request to have all the values ​​available. The creation of a Virtual Properties allows its use in alarms and in dashboards.

If you need any additional information, please contact us here.

This article describes some major improvements that have been made to the Live Data section of the Console to make the interface faster to use. New shortcuts have been added on the page (properties, gateway) to reduce search time and avoid multiple page changes.

Equipment header

On the device description line, the number of properties is now diplayed and a new button has been added. This button is a shortcut to the Configuration / Equipement page. So you have an access to the properties list directly from this place.

Filters

Each property is available either in Read Only access or in Read/Write access. We added a filter function to select properties based on this attribute.

Once the type of access is selected, the page only displays the corresponding lines. If you want to view both kind of attributes (read and read-write), simply click on the “Select” item.   

Quick properties access

You can now access the properties settings directly from the Live Data Page. The old way was to to go to the Configuration Tab / chose equipement / properties / search for properties / Modify. The new shortcut is available on the property’s line via the gear button :

Once the property has been modified, you must check the “send changes to device” checkbox to validate the changes with the box, then click the Save button.

Quick gateway access

In the same way, a gateway button has been added to the property line to directly access  the gateway page. Since a property can be linked to several gateways, an intermediate list is displayed so that you can choose the right line.

Assign a value to a property

For all the writable properties, a "remote control" button icon is available.

This functionnality allows you to update the value of a property.

Create a graph directly from the live data

A new button “Add a Graph” is available in the chart section. This functionnality is useful to create a graph in the Graph Tab of the Console without quiting this page. You just have to click on the button “Add a graph”.

Create a new chart or add the property to an exising one :

And the graph is available  in the Graph Tab :

Additionnal information about timestamp

In addition to the last sensor value, a pop-up window displays the penultimate timestamp when you hover over the timestamp with the mouse. Displaying the last 2 timestamps allows users of LoRaWAN devices to infer the frequency with which frames are sent and thus know when the next value will be received.

Responsive interface for mobile viewing

As the console application is often used on mobile devices, the interface now adapts to the display size of the medium. Here is an example of buttons that appear differently compared to the landscape format of a typical PC application.

Please contact us if you need any additional information : Wattsense Support

Virtual properties let users calculate indicators from existing properties. This article explains how to create them.

Please note that this functionnality is for the moment only available for calculation of consumption. It is intented for Towers only. The virtual properties are available from the Wattsense Console and the cloud (they are not available from the device itself meaning, they can't be used/redirected on gateways).

For example : this kind of property can display a hourly, daily, weekly or monthly consumption of one building instead of the real time (index) consumption.

The value of a virtual property is updated as soon as a new value for the underlying property is received. This to see the current consumption alongside the consumption of the period before.

Consumption virtual properties can be applied to electric power data, water flow, gas flow …

They can be displayed in graphs, and used to create alarms.

How to proceed ?

In the Wattsense console, go to the Virtual properties Tab, and click on the Create a virtual property button.

Fill in the fields as follows :

1 - For the moment, only Calculate a consumption is available.

2 - Choose a name for the virtual property

3 -Select an existing property of an equipement

4 - Choose the computing interval (Hourly, Daily, Weekly, Monthly). See the note below to understand how the periods are taken into account.

5 - Specify the scaling if necessary. This function can be useful if the value of the difference between to properties is not meaningful in the unit’s origin.

6 - In this case above, it can be interesting to change also the original unit. 

7 - Use Create another virtual property after this one chekbox to add a new property which will be prefilled by all the parameters of the previous one. 

Then use the button Save to finalize the adding.

The new property appears in the listing, then Save changes to send the information to the console Wattsense.

Once the virtual properties are created, they all appear in the listing of the Virtual properties Tab.

From this page, you can modify, duplicate or delete the property.

You can only modify the name and the description of the property, the rest of the fields are not available for editing. If you want to change the interval for example, you will have to delete the property and recreate it.

Intervals calculation details 

Calculation rule : the virtual property is the last value of the period minus the first value of the period.

The virtual properties (consumption) have their timestamp at the beginning of the period as follows :

Hourly : example

Daily : example

Weekly : example

Monthly : example

Virtual properties : Data Analysis

The virtual properties are available in the live data tab as well as all the standard properties. They appear in the list in a special group (Virtual properties) like a new equipment.

They also can be displayed in graphs.

Virtual properties :

• can be exported and are available in the archive requests
• can be used to create alarm
• are available in the API and by extension in the data streams

Please contact us if you need any additional information : Wattsense Support

Here is an article about how to configure your Datastream Webhook.

A Datastream Webhook is an HTTPS communication between our Wattsense backend and your web server.

Available only with a Tower subscription, when our backend will receive either a value, an event or an alarm from the Tower, it will be automatically send to your web server.

Datastream Webhook architecture

Requirements to configure Datastream Webhook

In order to configure the Webhook communication correctly you'll have to get (from your web server parameters, Wattsense does not have them) the important informations that will allow our Backend to connect to it.

To do so, you will need :

Step by step configuration

Connector configuration

First of all, click on the "Organization" tab, select the Organization where you want to create your Webhook datastream and click on "Add a connector".

You can create several Webhook connector per datastream

Name your Webhook Datastream and fill the blanks according to your web server requirements :

Triggers configuration

Once the communication setup is done, you'lle have to create the Triggers :

Triggers define what is required to call the connector and what values to send.

When you click on the " Create new trigger" button, here is the interface you'll have to fill:

- Select what type of trigger you want to receive in your Web server.

- Add the Tower(s) in the list in the scope of the trigger. (Note that you'll only see Towers in the current Organization, not from an other one.)

Activate the Datastream

At the end of the configuration, don't forget to activate the datastream by enabling the toggle button

Data format

The data is sent with the following structure :

deviceId: String,
property: String,
timestamp: Long,
payload: Any,
receivedAt: Long?
scaledPayload: Number?
name: String?
unit: String?
externalId: String?
propertyId: String?
equipmentId: String?
gatewayInterfaceId: String?
slug: String?
isOutOfService: Boolean?
tags: Map<String, String>

The ? at the end of the line means that the field can be null.

Here's an example :

If you need any additional information, please contact us here.

Here is an article about how to configure your Datastream MQTT.

A Datastream MQTT is an MQTT communication between our Wattsense Backend and your Cloud based MQTT broker.

Available only with a Tower subscription, when our backend will receive either a value, an event or an alarm from the Tower, it will be automatically send to your MQTT Broker.

Datastream MQTT architecture

Requirements to configure an MQTT Datastream

To properly configure MQTT communication, it is necessary to obtain the crucial information from your broker parameters, which Wattsense does not provide. This information will enable our Backend to connect to your MQTT broker, which could be AWS, Azure, IBM, or a custom one.

Step by step configuration

Connector configuration

First of all, click on the "Organization" tab, select the Organization where you want to create your MQTT datastream and click on "Add a connector".

You can create several MQTT connector per datastream

Name your MQTT Datastream and fill the blanks according to your broker requirements:

Triggers configuration

Once the communication setup is done, you will have to create the Triggers :

Triggers define what is required to call the connector and what values to send.

When you click on the " Create new trigger" button, here is the interface you'll have to fill :

- Select what type of trigger you want to receive in your MQTT broker.

- Add the Tower(s) in the list in the scope of the trigger. (Note that you'll only see Towers in the current Organization, not from an other one.)

Activate the Datastream

At the end of the configuration, don't forget to activate the datastream by enabling the toggle button

Data format

The data is sent with the following structure :

deviceId: String,
property: String,
timestamp: Long,
payload: Any,
receivedAt: Long?
scaledPayload: Number?
name: String?
unit: String?
externalId: String?
propertyId: String?
equipmentId: String?
gatewayInterfaceId: String?
slug: String?
isOutOfService: Boolean?
tags: Map<String, String>

The ? at the end of the line means that the field can be null.

Here's an example :

If you need any additional information, please contact us here.

This article is about how to create and edit Dashboards.

We wanted to give you a simple tool to visualize a building data that is why we created Dashboards.

The Dashboards tab offer two experiences :

• Schematics : please refer to the schematics article for more details.
• Dashboards : A board to visualize values or schedules.

To add a new Dashboard, click on the Dashboard circle : 

The configuration panel for the Dashboard is displayed.

Give the Dashboard a name.

Dashboards are made of different charts. Three type of charts are available : Single Value, Table or Schedule. Here is an example of each type of display :

Single Value display

Select the “Single Value” chart type to start with and click “Add property” to choose the data points that will be represented in the charts.

On the next page, you can select equipment and properties :

   1) You can filter properties by equipment

   2) You can search for specific properties by name (ex “Tempe”)

   3) You can select properties in the list. Perform an other search and select the new properties matching the results. They will all be added to the current list

Once you have selected the properties that you want to display in a single value chart, click "Save".

As we are adding charts for the first time here, we can add multiple single value chart at once. There will be as many single value charts created as there are data points selected. Example :

Finally, click “Add” to create the Dashboard.

It will create four single value cards as I selected four data points :

You can now access several functions using the menu at the top right of the tile :

• See the lastest values is a shortcut to the general Console Live data Tab
• Configure the property is a shortcut the the general Configuration Tab
• Edit / Delete the widget : you can change the property and the name on the chart, or delete the card

You can add as many charts as you want. To add a table chart, click “Add widget” on the Dashboard

Table display

Select “Table” as the new chart type. This chart allows you to display data points in a table format similar to Microsoft Excel for example.

Complete the settings in the dedicated page as follows :

1) Select the properties that you want to display. (4 properties in the example below).

2) Specify the number of rows and columns (2 or 3), and associate the properties to the corresponding cell.

The configuration above will be displayed in this format :

A 2 by 2 table will let you 1 cell to display the value of your data point(s).

A 2 by 3 table will let you 2 cells…

Depending on the number of columns and rows, you are asked to edit the headers or the labels of the columns and rows. Then, select the position of the different data points values in the newly defined table. For this select for each data point, the cell where it will be displayed. The cells are named in the same fashion as in Microsoft Excel with letters for the columns and numbers for the rows.

Click “Add” to add the table to the current dashboard.

As with single value charts, you can edit/delete the chart by clicking in the chart menu at the top right.

Schedule display

This feature offers a dedicated display for schedules (Wattsense console schedules or equipment schedules).

First of all you will have to choose the type of schedule :

Controller schedule

Here you can display schedules that are stored inside controllers equipments.

All the availables schedules are present in the list. You just have to select the one you want to display and click on the "Add" button. Here is an example of a programmed planning retreived on a Siemens RVL 480 :

In the menu at the top right, alongside the standard Edit/Delete functions, two functions are available to modify the schedule itself as well as the property settings.

• Edit the value feature is a shortcut to the Console main menu / Live Data Tab :

• Configure the property feature is a shortcut to the Console main menu / Configuration Tab :

Schedule created in the console

Select the schedule in the list and choose the display format (Single day, 5 days slidings or week without week-end). You can create a schedule in the general Configuration Tab / Scheduling. (Cf article Scheduling)

Here are examples of display, with single day / full week configurations.

Here the top right menu can be used to duplicate or modify the schedule :

Dashboards management

Three additionnal fonctions are available in the common dashboard menu :

• The first cloud icon indicates the dashboard state.
• The second function allows you to switch the display to full screen mode.
• The last one allows the deletion of the current dashboard tab.

If you have any question, please contact us here

Requirements :

Step 1 :

Step 2 :

Once you have added the image :

1) you can modify the name of the schematic

2) you can add the properties of the devices connected to the box directly on the photo. To do this, click on the Edit button.

Step 3 :

Select the equipment, then the properties.

Step 4 :

Then place the data labels where you want on the schematic :

 

To add new properties or remove labels, click again on the Edit button.

The selected properties appear as a list in the top part of the screen.

You can create multiple schematics by clicking on the "+" button :

   then   

 

Tower licenses

 

Example:  If your license contains 100 points, you could have 4 sensors using 25 points each one. You can still use your license because you have access to 100 points. With 2 sensors and 25 points your license continues working as long as you do not exceed the threshold.

Purpose of the Modbus IP Gateway

Step 1

Step 2

Important information: SlaveID needs to be unique in order to avoid conflict

 

Step 3

Step 4

Property configuration :

By clicking on the  button, you will be able to have the details of your gateway property.

 

Be sure that your Modbus IP client configuration is matching these parameters.

 

Step 5

 

The Modbus table is mandatory in order for you to configure your Modbus IP client, with this table, you'll know how to access the data made available by the Tower/Bridge

 

This article describes the QoS levels in MQTT.

QoS stands for : Quality of service

There are 3 different QoS available for MQTT :

Wattsense is at the QoS level 1.

If you need any additional information, please contact us here.

 

REQUIREMENTS TO CONNECT YOUR BOX TO YOUR MQTT BROKER : 

You'll need your MQTT broker connection information

1. Broker Address
2. MQTT Port (1883,8883,etc..)
3. Client ID
4. Authentication information (if required)
5. Certificate (if required)

These informations should be available in your Broker configuration, if not please contact your Broker provider.

First of all, you'll need to create a new MQTT gateway :

 

 

Fill the required fields with your MQTT broker parameters.

 

 

AUTHENTICATION :

If your MQTT broker require an authentication with Username and Password click on the Authentication button and fill the fields.

 

 

TLS CERTIFICATE :

 

IMPORTANT INFORMATION ABOUT SECURITY IN MQTT SSL/TLS: The default port for MQTT TLS connection is : 8883 This implies a connection using certificates. Certificates are security files that allows you to authenticate to your broker. If you are using a TLS secured authentication please be sure that you have loaded your CA certificate.

 

TIPS It can happen that your broker is not using custom CA certificate but Public one. In that case, you will still have to load them in the Box. Because we do not stored them by default.

ADVANCED TAB :

TOPICS :

Uplink topic and Downlink topic are simple strings conformed to one or more topic levels. For instance, topics are case-sensitive.

Each topic is structured with forward slash as delimiters. The forward slash alone is a valid topic.

The broker uses the topics to filter the messages for each client subscribed to the topic.

UPLINK TOPICS

A new feature (available since firmware APPS 6.1.3) allows customization of the Uplink Topic format (per equipment or per property) in order to publish the data to monitoring / controlling software.
MQTT uplink topics structure can be defined according to your needs, using variables and strings. This structure will generate MQTT topics for each redirected property.

The following variables can be combined in the uplink topic structure  :

1. equipment name
2. equipment ID
3. property name
4. property ID
5. gateway ID

This feature has been added in order to avoid using slugs to group data. When you used slugs, you had to have a script in your MQTT broker to parse the message and access the slug, and then aggregate the data.

So, you can build the topic structure at your convenience by mixing simple texts / Equipements ID / Properties ID …

DOWNLINK TOPICS

Since the APPS 6.1.3 firmware version, you can add a wildcard (#) in the downlink topic settings. This multi-level wildcard (#) covers multiple topic levels and must be placed at the end of the topic format.

When a downlink topic finishes with /#, it receives all messages starting with the text before the wildcard character. If the subject is only "#", the client receives all the messages.

Example : If the downlink topic format is

Room1 / Sensor1 / #

Messages sent to the MQTT broker :

Room1 / Sensor1 / Temperature	OK
Room1 / Sensor1 / Pressure	OK
Room1 / Sensor2 / Temperature	NOK

EXAMPLE

FORMAT

NOTE Property Slug is the uniqueID of a variable, you'll find it in the property configuration itself Please note that your modifications will be aplied for ALL properties in the Gateway.

 

 

MQTT Gateway property configuration

 

To add properties to your gateway, select the properties button :

 

 

Then add Property:

 

 

On the next view you'll have the choice between all the properties available, select the one you want to redirect to your MQTT broker and click on Save

 

 

Once the properties select, you'll have that kind of view :

 

Click on "Save changes" to apply the modifications.

 

Be sure that the Access Type stay as LOCAL in this configuration.

 

If you need any additional information, please contact us: here 

Here you will have a video that will show you how to create your bacnet gateway:

 

You need to configure the Tower/Bridge before the sensor, otherwise the JOIN process will not succeed.

 

Step 1 :

 

NOTE If your equipment is not available in our database, you can still connect your sensor. You'll have "undecoded" informations : Communication level (RSSI, SNR and Spreading Factor) and the Raw-Payload.

 

 

Step 2 :

Step 3 :

Step 4 :

Step 5 :

Step 6 :