Wattsense Support Portal

How can we help?

Search

Common troubleshooting topics:

Getting Started

Getting started with Wattsense products

Tutorials

You'll find here tutorial about Wattsense configuration

Troubleshooting

You'll find here some helpful article to debug your installation

Getting Started

Tutorials

Troubleshooting

Promoted articles

Required open Port in a network for Box/Remote HUB (with sim card suspended)
1. The Box is not a server thus does not require to open any ports in your internal network,
2. The box communicates with remote servers, your firewall has to authorized communication with the box through:
- *.wattsense.com, TCP port 443 (HTTPS) and 19000
- *.amazonaws.com, TCP port 443 (HTTPS) and 8883 (MQTT)
- time1.google.com, UDP port 123 (NTP)
- Google DNS 8.8.8.8, UDP port 53
Please note that you cannot setup custom DNS.
See more
What happen if my Box or Hub lost network connection?
Wattsense always helps customers to get the best remote connectivity by monitoring and identifying issues at a very early stage. However disconnection sometimes takes place because the remote connection fades.

At Wattsense, our customers’ data delivery is a priority.

Our solution is designed to overcome such situations when the Box or the Hub (Remote Hub) can’t upload data to the server. There are mechanisms in place to retain data (100K measurements) during that blackout period and send the data to the server when communication is reestablished.

In case the disconnection is extended for more than a day and the device does not pick up the network, please follow this procedure:

Do not reboot or switch off the Box or the Hub

Contact your support representative at Wattsense by submitting a technical support request here

Step 1 is very important to avoid losing data.

Wattsense will get in touch with you right away and investigate the root cause.
Please feel free to contact us if you need any additional information,

Best,

Wattsense Support Team
See more
Onboarding process with your Remote HUB
What is it?

Until now, with a Wattsense Hub, you had to configure the Hub by connecting it to a computer using the Wattsense Desktop Application to set it up.
Starting today, the configuration can be done remotely through the Wattsense web console at https://console.wattsense.com/, the same way as you would do it with a Wattsense Box.

How does it work?

The new Hubs have their SIM card activated by default without any additional cost from the start*. Thanks to this, the connection between Wattsense servers and your Hub remains open, and you can enjoy such things as:
- Send a new configuration to your device using the cloud
- No need to be onsite and connected to the HUB to check your configuration
- Benefit from new software updates and security patches automatically
- Make use of new equipment added to our library
All of this without having your data points sent to us and stored in our servers.

Remote Hub Activation

Once connected to your console.wattsense.com account, you'll see your product(s) in the "HUBs" section.

Then click on the "power" button to activate it,

Remote HUB console specifications:

The yellow circle next to your Hub’s name informs you that your Hub is connected to the Wattsense servers without sending any data.

If you want to check the configuration result, you can still activate the switch next to your Hub’s name.

The green circle next to your Hub’s name informs you that your Hub is connected and sending data points values to the Wattsense servers.

By doing so, the data points values are sent to the Wattsense servers but only to allow you to check your configuration. After one hour, the values will be deleted, and we won’t keep any record of them in our database.
See more
How to create a custom routing table ?
As with any other device connected to the Internet, the Wattsense product comes with its routing table. The routing table will help identify where to send the data to a recipient based on its IP address.

Our product can connect to the Internet with 2 different ways:
- Through one of the two Ethernet interfaces
- Through its GSM modem
The connection with the GSM modem has to be permanent, in order to allow direct communication between the Wattsense servers and your device.

For example:

It is necessary to send a new configuration to the device or to benefit from a new firmware update.

Default Route

A default routing is configured for this in your device to redirect any IP traffic to the Wattsense server.

Default routing table (wwan0 represents the GSM modem)

If an IP network is added, the default routing is updated to reflect the new connection.

eth2 interface configuration here for a MQTT gateway

Default routing table updated to reflect the eth2 interface configuration

Custom Route

In some specific cases, you will need to edit the routing table of the device to specify your own route. The case we know the most of is the following:

In this example, we have two sub-networks in the building: network A and network B. If data should transit between network A, where the Wattsense device is, to network B thanks to the router, then the routing table should be edited in the configuration of the device. Otherwise, the data will go through the wwan0 interface and will never reach the network B.

Addition of the new route

The full table will then read:

In case you need help or any further information concerning the routing table configuration, feel free to contact us here.
See more
How to send a downlink from a Modbus IP client ?
This article is a tutorial for users who configured a Modbus IP Gateway into their HUB/BOX, which is redirecting Lorawan sensors values. You can learn more about setting up a Modbus IP Gateway from this tutorial.

Attention

Downlink specifications are explained in sensor manufacturer documentation only.

Step 1

Be sure that you configured a Modbus IP Gateway redirecting the correct properties. In order to send a downlink, the property "Encoded downlink message" is required.

Note

Remember the address of the property. Here is 268.

Warning
The type of the property is Text and should not be changed.

Step 2

Go to your Modbus client interface and connect to your Wattsense device IP address. You should be able to find it on the Configuration > Connectors tab.

Note

For this example, I am using my computer as my Modbus client, using the software ModbusDoctor.

Step 3
- Set the address of the Encoded downlink message property. (268 in my example)
- Set the type as Holding register.
- Configure the number of registers of the downlink, depending on its size. (A single register contains 16 bits, so you can put 2 ASCII characters per register).
- In this exemple, we send the following downlink: 401E20:1
  (This downlink contains 8 characters so we can set the size to 4)
- Write 2 ASCII characters of your downlink in each register area.
- Click on WRITING to send the downlink.
Attention

Be aware that for a Class A Lorawan sensor, the downlink will be received only right after it sends an uplink. If you send multiple downlinks they will be stored and sent to the sensor one by one. The downlink queue is a LAST IN - FIRST OUT queue per sensor.
Link to further documentation about Lorawan downlink.
See more
How to send a downlink from a Bacnet client ?

This article is a tutorial for users who configured a Bacnet Gateway into their HUB/BOX, which is redirecting Lorawan sensors values. You can learn more about setting up a Bacnet Gateway from this tutorial.

Attention

Downlink specifications are explained in sensor manufacturer documentation only.

Step 1

Be sure that you configured a Bacnet Gateway redirecting the correct properties. In order to send a downlink, the property "Encoded downlink message" is required.

Warning
The Bacnet Object Type must be a CharacterString.

Be aware that most supervisors do not support the necessary data type in BACnet to write Downlink. CSV is not supported.

Step 2

Go to your Bacnet client interface and search for your Wattsense Bacnet Gateway. You should be able to find your redirected Lorawan properties.

Note

For this example, I am using my computer as my Bacnet client, using the software Yabe.

Step 3

Choose the Encoded downlink message property and write your downlink as a present-value. Press enter to send the downlink to your sensor

Attention

Be aware that for a Class A Lorawan sensor, the downlink will be received only right after it sends an uplink. If you send multiple downlinks they will be stored and sent to the sensor one by one. The downlink queue is a LAST IN - FIRST OUT queue per sensor.
Link to further documentation about Lorawan downlink.

See more
How can I create my Bacnet network?

Here is a video that would explain you how to create your Bacnet network really easily.

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

See more
How can I send a lorawan downlink ?

First of all, make sure that you've followed the installation tutorial here.

Step 1

Go in your equipment properties:

In the selected properties, be sure that you've checked the one called "Encoded downlink message"

NOTE: It's the only property with a "Write" Access type

Step 2

Now that all the requirements are completed, you can send the downlink. Go to "Live data" and click on "Set property"

Step 3

1) Fill this blank with the value of your downlink. Downlink specifications are explained in sensor manufacturer documentation.

2) Once you click on "Save" the downlink will be sent to the sensor.

NOTE

if you send several downlinks in a row, the last downlink will overwrite the previous one. Link to further documentation about Lorawan downlink

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

See more
How to debug my MQTT communication
Here is an article to help you debug your MQTT gateway.

If you are not really familiar with MQTT environment we suggest you this really well designed website.

Test your MQTT connection with an MQTT client:

If you're not seeing any connection from your Box/Hub after you have configured it.

The first step would be to test your credential/parameters with an other MQTT client.

Here is a list of potential MQTT client you can use:
1. Mosquitto : https://mosquitto.org/
2. MQTTFx : https://mqttfx.jensd.de/
If you have the correct configuration and you can connect using an other MQTT client and not with the Box you can go on with the next step.

If you are not able to connect to your MQTT broker even with on of those, that means your credential/parameters are either wrong or you are missing something.

TEST WITH MQTTfx 1.7.1 TUTORIAL:

AIM OF THIS TEST: Be sure that your MQTT broker is accessible with an MQTT client and correctly configured. Check also if an MQTT client (your laptop) can connect to it if the box cannot.
If you can connect to the Broker after this test:

-> The targeted MQTT broker is available and you have the right parameters.

-> Then the issue would be:

-> The Box MQTT gateway is not correctly setup. Please double check your MQTT config.

-> The Box has an issue -> contact support.wattsense.com
REQUIREMENTS: 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)
-> Launch MQTTFX:

Then create your new profile (MQTT client)

1. Change your profile name

2. Select "MQTT Broker" in the profile Type

3. Fill the information with your broker setup.

4. If your MQTT broker authentication require a "Basic Authentication", switch to the User Credentials Tab and fill Username/Password.

-> If your MQTT broker requires a TLS secured connection click on the SSL/TLS.

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 in the SSL/TLS tab for MQTTFX (see below) and that you have also load it in the Box during your first test.

SSL/TLS COMMUNICATION:

(1) -> Enable the SSL/TLS

Choose the certificate you want to use:

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. Using MQTTFx, if you only enabled the SSL/TLS tickbox without specifying the CA certificate, it will automatically load the public certificate (as your laptop have access to them automatically).

If you have any problem, please do not hesitate to contact us: Wattsense Support
See more