Logs

This article details the different logs available in the console.

These logs are chronological records of events, operations, and errors. They are useful for understanding the behavior of devices connected to the box, diagnosing problems, ensuring security, and monitoring performance.

This information is available in the console's Log tab and is grouped into three categories: Commands, Events, and Properties.

Command Logs

The goal here is to have traceability of commands (write requests from the console or API), particularly for LoRaWAN, by providing detailed statuses and a complete history. This allows for a better understanding of the command state and facilitates the debugging process.

Each command event is displayed with the following information:

• Event date
• Command type
• Status
• Unique ID
• Name and value (if any) of the property involved
• Username (username) in the console or API

Command types include:

• Send configuration
• Write request (property)
• Read request (property)
• Scan (BACnet or mbus)
• Box restart
• Start communication (Cloud data activation for bridges / SIM card activation)
• Stop communication (Cloud data deactivation for bridges / SIM card deactivation)

Sending a command follows a complex process that requires monitoring its progress. The status column describes the current state of the command (Command sent to the box, sent to the equipment, delivered, etc.).

Status History and Debugging Help

A button providing access to the command event details is available on each line:

This allows you to view a complete history of status changes and track all the steps and events that occurred during the process.

Display filtering

You can filter the list of events if you need to search for specific information.

Event Logs

This log lists events related to the operation of the console/box and its interactions with associated equipment (excluding property value updates, which are listed in the section below). These logs can be used to detect problems with communication, data format, configuration, network, etc.

Each log entry is time-stamped and identified by its origin (Type/code). The type categories are as follows:

• Generic (0-999)
• Configuration (1000-1999)
• Network (2000-2999)
• Data Configuration (3000-3999)
• Properties (4000-4999)
• Devices (5000-5999)

You will find all the codes used on this page.

Here, for example, we have codes 2008, 4004, and 4001, which correspond to the following information:

• 4004: Downlink reception status
• 5002: Equipment Activation (Currently only used for lorawan device)
• 4001: Read error (property could not be read)

If the events are related to devices and/or properties, their names are also displayed. The Origin column indicates the command that triggered the event.

Command ID: Command from the console or API
Other: External or local command (BMS, scheduling, scenario, etc.)

The link under Command ID allows you to view the details of this command.

You can also filter the list of events if necessary:

Property Logs

Each time a property value is updated, a line is added to the property log. This occurs, for example, when the box receives a data frame from a LoRaWAN sensor or when the box receives the result of a read request (Modbus, KNX, etc.).

This line consists of the date, the device name, the property, the raw value, and the value corrected for the scaling factor.

The filtering feature allows you to search for specific equipment and/or properties.

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