This repository has been archived on 2025-12-23. You can view files and clone it, but you cannot make any changes to it's state, such as pushing and creating new issues, pull requests or comments.
2025IoT-project-ThingsBoard/report/report.md
2025-12-19 17:22:45 +01:00

3.2 KiB

ThingsBoard Assessment

Jarne Clauw Tibo De Peuter Mathis De Witte

Introduction

Idk small introduction text

ThingsBoard

Setup of ThingsBoard...

Injecting data

Jarne had already a script that could inject data...

Discussion

Question 2

Q: Due to processing constraints, one of our end nodes cannot convert the measured voltage from a TMP36 sensor to temperature. Is it possible to accomplish this conversion at Thingsboard? How this could be done?

A: Yes this is possible, there are generally two ways of doing this:

  1. You could add a script node to the rule chain which receives the (voltage) sensor data and transforms this into the temperature through a certain function.
  2. There is now also a new feature in Thingsboard called "Calculated fields". This way is generally more elegant as it doesn't require you changing the rule chain. The calculated fields can be configured at both the device level and the device profile level. We can either use a "Simple calculated field" for simple arithmetic functions, or we can use a "Script calculated field", which allows us more control over the computation on the data. These scrips are written in a language called "TBEL".

sources:

Question 3

Q: We have a node monitoring pumps vibration on a water station. We need to predict when vibration will reach critical levels so we can schedule preventive maintenance for the pump and avoid unplanned downtime. Briefly describe how this could be accomplished with ThingsBoard.

A: This too can be done by calculated fields. For this field we would probably want to use a "Script calculated field" as it allows us to access historical data (through the variable ctx). The function will need to do some analysis on thi historical data and based on that estimate when a device would need preventive maintenance. The output of this script should be an Attribute, as we want a single answer for when to plan the maintenance.

source:

Question 4

Q: Alarms are an important part of telemetry monitoring. Describe how they work in ThingsBoard and what options are available to send notifications when an alarm is triggered.

A: Alarms are defined for certain device profiles which you choose. If certain telemetry data is sent that meets certain conditions, the alarm will be triggered. This will be visible in your notifications. The alarms can also be displayed in a dashboard that is associated with a device of the device profile.

Personalized notifications can be delivered via email, SMS or other third party systems through the Notification Center.

It's also possible to send notifications to your smartphone through the Thingsboard Mobile Application

sources:

Conclusion

Conclusion and lessons learned

References

Do we add them to where we use them or here at the end of the report?