Definitely need to be able to use ">" and "<" in rules triggered by temperature. It is really useless otherwise. Further, comparing values for two different sensors would be invaluable, such as being able to compare temperatures in different parts of the house and run the central fan if they are more than n degrees apart.
I had the same thoughts (some written somewhere in the forum). Ashok I was wondering if we could also get the ability to define a new virtual value.
Besides use in a rule, I might want to display that virtual value somewhere (Almond+ or webGui).
And be able to define more than one virtual value for a device.
Such as:
Dev17(Aeon_Multisensor6).V1_RelHumidityBathToIndoor = Dev17(Aeon_Multisensor6).Humidty - Dev16(Aeon_Multisensor6).Humidity
Dev17(Aeon_Multisensor6).V2_RelHumidityOutdoorToIndoor = Dev18(Aeon_Multisensor6).Humidty - Dev16(Aeon_Multisensor6).Humidity
Dev17 is in a bathroom, Dev16 is in a central area of the house. Dev18 is outside.
And be able to select virtual values V1_RelHumidty & V2_RH in a rule for Dev17.
When Dev17.V1_RH > 10% and Dev17.V2_RH < 20% Then Dev14(Fan).(On, Medium)
When Dev17.V1_RH > 10% and Dev17.V2_RH > 20.2% Then Dev14(Fan).(On, Low) // ignoring 20.0%..20.2% for a bit of hysteresis.
When Dev17.V1_RH < 5% Then Dev14(Fan).Off
When Dev17.V3_TeenagerTookALongHotShower Then Dev14(Fan).(On,High).Delay(5,"minutes").(On,Low).Delay(15,"minutes").Off // ;-)
These virtual values could live somewhere else than on a specific device. Logically it makes sense to me to have the value in a context (device) such as above.
Could take it a bit further..., and create a logical device, Dev19(BathVentilation), that holds the virtual values and conditions and matching (other) device states.