Rules, Humidity, not firing

[mr23]

I have a multisensor (Aeotec MS6). It is operating with Almond+, including giving humidity & temperature & illumination changes and motion events.
My A+ is running R083.

If I set up a rule for that device, select to have it trigger off humidity and set the rule value (to say 42 %), set a lamp to go off....
when the humidity rises and almond sensor reports (through cloud) shows 41% 42% 43% ...
(or  43% 42% 41% depending on whether I'm raising or lowering the sensor locations humidity) ...
the rule never fires.

Has this been tested by Securifi ?

Also, how does one set a temp or humidity to fire when above some value? or in some range? 
The rule seems to only take a specific value, and I assume must match that value.  Since the value reported may skip a specific integer value (say 40% 41% 43% 44%) then a rule set to do something at a specific value may prove unreliable.

And Temperature is reported in tenths of a degree (F). But the rule setting for temperature is integer. What chance is there that will ever compare to True ? I'm having the sensor report a change of 0.2F, so it steps down 74.6, 74.4, 74.2, 74.0, 73.8 and the rule made for this sensor/temp to turn off a lamp did not fire.

On the bright side, when motion is detected it will fire the rule and turn on a lamp, and when "no motion" is reported it does turn off a lamp. That gives me the bare minimum functionality of turning on a fan while someone is present, until so many minutes after they've left the room. I was expecting I could have a short "no motion" time and if humidity is still high then leave the fan on, but without humidity-firing rules I have to have a long "no motion" time to leave the fan on for awhile.

Securifi, when will T&H rule functionality be available, including either 'range' or greater and less than a value conditions ?

Thanks,
-Chris

Ps. On another positive note, the MS6 can be calibrated, so I have the temperature measuring within 0.1F of the actual room temp.

Pps. I went in via ssh and grabbed the RuleEngine log. It shows a motion event occuring and rule firing setting a lamp to 115 of 255, followed by Humidity (which had been climbing from 41%) hit 42%, and matched the setpoint in the rule, but no rule executed, only saying All Rules Done. Did this fail because it compared "42" to "42 %" ?  Below that is  the temp data report at 74, did that fail because it compared "74" to "74.0 °F" ?

Code: [Select]

[2016-5-28 20:28:50.686140653]   {PRINT}         Msg Received for Device 16,index:1,Value:true,EventType:0,ruleslist size:10,bytes read:48
[2016-5-28 20:28:50.686312607]   {PRINT}         rulesEngine:device and index matched,cvalue:false,Avalue:true
[2016-5-28 20:28:50.686445354]   {PRINT}         rulesEngine:device and index matched,cvalue:true,Avalue:true
[2016-5-28 20:28:50.686566008]   {PRINT}         Rule 11 executing for AND condition is success
[2016-5-28 20:28:50.688216937]   {PRINT}         rulesEngine:setting Device 5 Index 2 to Value true.
[2016-5-28 20:28:50.689813634]   {PRINT}         rulesEngine:setting Device 5 Index 1 to Value 115.
[2016-5-28 20:28:50.689978981]   {PRINT}         All Rules Done
[2016-5-28 20:28:50.820095439]   {PRINT}         Callback Received for Device 5,Index:2,Value:true
[2016-5-28 20:28:50.820340366]   {PRINT}         No Trigger is registered on this Index of Device,so not queuing the msg
[2016-5-28 20:28:50.820541340]   {PRINT}         Scenes MSG Received for Device 5,index:2,Value:true,EventType:0,ruleslist size:10,bytes read:48
[2016-5-28 20:28:50.820721507]   {PRINT}         Scene false
[2016-5-28 20:28:50.820834460]   {PRINT}         +++++++++++++++++++++++++++++++++++++++++++++++++++
[2016-5-28 20:29:44.680093661]   {PRINT}         Callback Received for Device 16,Index:5,Value:42 %
[2016-5-28 20:29:44.680311982]   {PRINT}         Scenes MSG Received for Device 16,index:5,Value:42 %,EventType:0,ruleslist size:10,bytes read:48
[2016-5-28 20:29:44.680468142]   {PRINT}         Scene false
[2016-5-28 20:29:44.680590796]   {PRINT}         +++++++++++++++++++++++++++++++++++++++++++++++++++
[2016-5-28 20:29:44.680741643]   {PRINT}         Msg Received for Device 16,index:5,Value:42 %,EventType:0,ruleslist size:10,bytes read:48
[2016-5-28 20:29:44.680906376]   {PRINT}         rulesEngine:device and index matched,cvalue:42,Avalue:42 %
[2016-5-28 20:29:44.681045163]   {PRINT}         All Rules Done
[2016-5-28 20:29:55.803716913]   {PRINT}         Callback Received for Device 16,Index:4,Value:72.9 °F
[2016-5-28 20:29:55.804047080]   {PRINT}         Scenes MSG Received for Device 16,index:4,Value:72.9 °F,EventType:0,ruleslist size:10,bytes read:48
[2016-5-28 20:29:55.804191520]   {PRINT}         Scene false
[2016-5-28 20:29:55.804298594]   {PRINT}         +++++++++++++++++++++++++++++++++++++++++++++++++++

Code: [Select]

[2016-5-28 20:49:57.682496539]   {PRINT}         Callback Received for Device 16,Index:4,Value:74.0 °F
[2016-5-28 20:49:57.682796573]   {PRINT}         Scenes MSG Received for Device 16,index:4,Value:74.0 °F,EventType:0,ruleslist size:10,bytes read:48
[2016-5-28 20:49:57.682931620]   {PRINT}         Scene false
[2016-5-28 20:49:57.683042020]   {PRINT}         +++++++++++++++++++++++++++++++++++++++++++++++++++
[2016-5-28 20:49:57.683181961]   {PRINT}         Msg Received for Device 16,index:4,Value:74.0 °F,EventType:0,ruleslist
size:10,bytes read:48
[2016-5-28 20:49:57.683341894]   {PRINT}         rulesEngine:device and index matched,cvalue:74,Avalue:74.0 °F
[2016-5-28 20:49:57.683469981]   {PRINT}         All Rules Done

[Ashok]

@ mr23,

Mostly if everything goes well, our next firmware would take care of this issue, because we are adding the >= or <= under rules.

[mr23]

@ mr23,

Mostly if everything goes well, our next firmware would take care of this issue, because we are adding the >= or <= under rules.

Thanks for this!

Please consider again the following; will the comparison work by just adding the >= <=, or does the sensor response need to be processed to just the value so the "74" >= "74.0 °F" ?  Please make sure they test both °F and % cases.

Code: [Select]

I went in via ssh and grabbed the RuleEngine log. It shows a motion event occuring and rule firing setting a lamp to 115 of 255, followed by Humidity (which had been climbing from 41%) hit 42%, and matched the setpoint in the rule, but no rule executed, only saying All Rules Done. Did this fail because it compared "42" to "42 %" ?  Below that is  the temp data report at 74, did that fail because it compared "74" to "74.0 °F" ?

[bjp]

I'm running R085 and the hardware UI says there aren't any updates.  This is higher than R083 listed in this thread, but I don't seem to have comparisons other than == available for rules.  It seems like this makes rules pretty much useless for most sensor values; am I missing something?  The example rule I want to make is "if it's hotter than 79 F, then turn on my switch".  Seems like it doesn't get much simpler than that, yet I don't seem to be able to do this.  Is it possible?  If not, when will it be available?

[fillibar]

Greater than or less than functions are not yet in the general software. Ashok mentioned the next firmware. Dates for firmware are not generally given.

[bjp]

This is an older thread and Ashok said next firmware when the OP was running R083.  So...next-next firmware?  Never mind...

[fillibar]

Sorry, I saw the last post from Ashok as being end of May but forgot R085 had come out at the beginning of May (I just had to look that up). My mistake.