29 lines
1.8 KiB
Markdown
29 lines
1.8 KiB
Markdown
## 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.
|
|
|
|
sources:
|
|
- https://thingsboard.io/docs/user-guide/rule-engine-2-0/overview/
|
|
- https://thingsboard.io/docs/user-guide/rule-engine-2-0/tutorials/transform-incoming-telemetry/
|
|
- https://thingsboard.io/docs/user-guide/calculated-fields/
|
|
|
|
## 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:
|
|
- https://thingsboard.io/docs/user-guide/device-profiles/#alarm-rules
|
|
- https://thingsboard.io/docs/getting-started-guides/helloworld/#step-6-alarm-notifications
|
|
|
|
|