Upgrading from old licenses to new licenses 

Following the update of the Wattsense product catalog in October 2025, we have decided to migrate licenses created before October 1, 2025, to a corresponding license in the new catalog.

This migration will be to your advantage. Here are the details:

• For Bridge licenses: switch to the new default multi-protocol Bridge license with 100 points or Bridge 5000 points, without any additional fees, depending on the number of points currently activated on your box.
• For Tower and Tower Control licenses: switch to the new default multi-protocol Tower Control license, which includes schedules for controlling setpoints and automation scenarios with 50, 100, 200, 500, 1000, 2000, and 5000 points, without any additional fees, depending on the number of points currently activated on your box.

If it has been activated, the license activation date will remain the same, as will its expiration date.

Examples:

• You have a Tower Medium with 200 points included and 2 extensions of 50 points. The license is valid for 3 years and was activated on October 4, 2024 (expiration date October 4, 2027) => you will switch to a Tower Control 500 points license with the same activation date of October 4, 2024 and an expiration date of October 4, 2027.
• You have an IoT Bridge with 100 data points with only the LoRaWAN protocol authorized for incoming data. The Bridge was activated on  June 20, 2023 (cellular communications included for 10 years) => you will switch to a 100 points multi-protocol Bridge license. The activation date remains June 20, 2023, and cellular communications support will end on June 20, 2033.

The migration will happen on June 30th and will not require any action on your end. You will be notified by e-mail. Once it is complete, you will see the names of the new licenses appear in your box information.

Changes to how virtual properties are counted

Virtual properties are points available exclusively in the cloud that you can create in the console based on the values of incoming properties. There are of two types: consumption calculation and arithmetic calculation.

Until now, virtual properties could be created up to a limit of 10% of the points included in your subscription. Example: for a Tower license with 100 points, a user could create up to 10 virtual properties in addition to retrieving the values of 100 properties.

Soon, and on the same date as for licenses—June 30, 2026—the limit on the number of points in your subscription will apply to incoming properties and virtual properties, eliminating the 10% credit. Example: For a Tower license with 100 points, a user will be able to create as many virtual properties as they wish, as long as the total number of incoming points and virtual properties is less than or equal to 100.

Following this update, a single counter will then be visible in your box’s information:

This article explains what happens when your Tower license expires. Bridges are also impacted by this process even if they are not directly linked to a license. 

Towers

One month before a license expires, emails are sent to the Tower sub-organization administrator and billing contact. They indicate that the subscription is about to expire and suggests taking action to renew the license. Other reminder emails are sent one week before the expiration date and on the expiration date.

At the same time, this information is also displayed on the console interface :

		1 month before the end of the license
		License has expired

If you click on the Renew shortcut, you will have access to a list of technical impacts if the licence is not renewed detailed here:

The following diagram shows the features that are no longer available as well as the services that are still active after the license expires.

Legend

	Services are interrupted
	Services are available for 6 months (archive API feature)

Six months after the last license end date is reached, the box data is deleted from Wattsense servers. All the data is deleted but not the configuration. Users are notified via email and in the console.

A final email is sent when the tower goes into restricted mode. At this time, the status of the box changes to gray in the console.

Bridges

Bridges do not have a license strictly speaking, but there is a 10-year limitation linked to the GSM subscription. If you do not use the GSM connection (your bridge is connected via LAN / Ethernet network), there is no impact.

If you use the default GSM connection :

If the subscription is not renewed when the 10 years period is reached, the features of the Bridge will be restricted as described in the console :

On the following diagram, you can see the impact if the GSM connection is interrupted (in red)

Reactivation

When a hardware becomes active again :

● its sim card is reactivated
● the restriction are removed

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

This article describes the detailed functional diagram of the Tower and Bridge boxes. 

1) Bridge

Main features

• Remote configuration: Manage your gateway settings from anywhere.
• Real-time data: Access immediate insights from your connected devices.
• Local Redirection: Easily integrate with BACnet, Modbus, or MQTT for on-site control.

Ideal for: Projects requiring a reliable, local bridge for sensor data (e.g., LoRaWAN) to be integrated into an existing BMS, enabling local automation based on real-time conditions. Available in 100 points or unlimited versions to scale with your needs.

Schema

2) Tower Lift

Main features

• Data historization: Store and access historical data for in-depth analysis.
• API & Webhook Integration: Seamlessly push data to your preferred cloud platforms and applications.

Use case: Residential buildings or portfolios where the primary need is to collect vast amounts of data (e.g., electricity, water meters, environmental sensors) and integrate it into a central analytics platform or Energy Management System via API for billing, predictive maintenance, energy performance or tenant experience apps.

Schema

3) Tower Control

Main features

• Automation scenarios: Create custom rules to optimize energy consumption and comfort.
• Scheduling: Implement time-based controls for HVAC and more.
• Remote alarms: Receive instant notifications for critical events.
• Dashboards & Graphs: Visualize building performance with customizable insights.

Use case: Small to medium-sized commercial buildings (e.g., post offices) where you need to connect various equipment (boilers, controllers, meters, sensors) and implement intelligent automation to react to conditions, optimize schedules, and reduce operational costs.

Schema

If you would like to have a more synthetic view of the differences between the two models, you can refer to this article : differences between Tower/Bridge.

For more information, feel free to contact us here.

This article is about the requirements to connect a Wattsense Tower/Bridge to a BMS.

Below the information needed to connect the Wattsense Tower/Bridge with an existing BMS :

R = Required - O = Optional - N/A = Not Applicable - (*) = See remarks			Checklist	Remarks
Document
BMS network overview	R			It helps to identify the best location of the Box
Connectivity
GSM/3G/4G Signal quality test	R		Not Filled	As indication, use your mobile phone as reference:  • Write down the network carrier used for the test • Check the number of network bar of your mobile phone  • Check if you can access website smoothly
Only applicable for IP network
Assign IP address and netmask for the Box	R*			(*) Check with the IT manager of the building to gather these informations
Internet access via ethernet	O*			(*) Check with the IT manager of the building to obtain the gateway IP address
Protocol used on the BMS primary network
BACnet
	IP (Ethernet/RJ45)
BACnet port (UDP port)	R			• IP : Default UDP port is 47808 (0xBAC0)
BOX should be on the same network as BBMD	R
Communication configuration (Baud rate)	N/A			(*) MS/TP: Check with your Wattsense customer support contact
Modbus
	IP (Ethernet/RJ45)	RTU (RS485)
Slave address of all equipment	*	R		(*) This is required when Modbus TCP/IP <==> RTU gateway is used (e.g Schneider EGX 150)
IP address and UDP ports of all equipment	R	N/A		Default UDP port is 502
Network communication configuration	N/A	R		Obtain Baud rate/Parity/Data bit/Stop bit of each Modbus network (Contact your technical team responsible for the BMS)
Modbus register list	O	O		• Required information for the collection of data. Please send via the support contact email: • A list in Xls, CSV, or text file format of the specific data points (properties) you wish to recuperate. - Name of the variables - Register address - Data format - Access type - Modbus function used

For more information, feel free to contact us here.

• • LoRaWAN
  • Bacnet 
  • Modbus 
  • M-Bus
  • LPB
  • KNX
  • Diematic