answer question 2
This commit is contained in:
parent
61f623b079
commit
e5fb720c9c
1 changed files with 15 additions and 1 deletions
16
answers.md
16
answers.md
|
|
@ -1,4 +1,16 @@
|
|||
## 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
|
||||
|
|
@ -12,4 +24,6 @@ It's also possible to send notifications to your smartphone through the Thingsbo
|
|||
|
||||
sources:
|
||||
- https://thingsboard.io/docs/user-guide/device-profiles/#alarm-rules
|
||||
- https://thingsboard.io/docs/getting-started-guides/helloworld/#step-6-alarm-notifications
|
||||
- https://thingsboard.io/docs/getting-started-guides/helloworld/#step-6-alarm-notifications
|
||||
|
||||
|
||||
|
|
|
|||
Reference in a new issue