Some info about the new virtual sensor types (taken from the manual)
Failover
When designing a failover mechanism, you need to define a master (which provides data to the virtual sensor during normal operation) and a slave, which provides data instead of the master sensor, when the master has not been sending data for a certain amount of time. To make this definition your have to make two entries in virtual sensor section for the new ID.
Code: Select all
New ID Name Trigger Conversion
th9 failover-th th0 failovermaster
th9 th2 failoverslave 300
Example above defines "th9" to receive data from primary sensor "th0". When "th0" has not sent data for more than 300 seconds and "th2" provides fresh data, then data from "th2" is used to feed virtual sensor "th9".
Sensor Difference
When designing a sensor difference evaluation mechanism, you need to define a master (which provides the reference data) and a slave, which provides data to be compared. The result represented in the virtual sensor is the subtraction of the slave sensor from the master sensor. Which part of data provided by the slave sensor gets subtracted from which part of data from the master sensor is controlled by a position argument. A second parameter is the time frame how long a recorded value is regarded valid. When the time frame has passed no differences are computed.
Code: Select all
New ID Name Trigger Conversion
t9 tempdiff thb0 sensdiffmaster 1 300
t9 th0 sensdiffslave 1 300
Example above defines "t9" to represent the temperature difference between indoor ("thb0") and outdoor ("th0"). Difference is only computed when sensor data is not older than 300 seconds. Values to be subtracted is parameter 1 from "thb0" sensor (first parameter on THB sensors is temperature) and parameter 1 from "th0" sensor (first parameter on TH sensors is temperature).
