I use various temperature sensors in different areas. I have this rule set to turn on a fan when the temperature is >= 43.
This sensor is reporting 43.2 but it doesn't trigger (as of this writing it is still OFF). I've seen it at 43.5 and not trigger. I don't watch it closely because eventually the fan will turrn on. (So I don't know if it needs to be 43.6). My question is does the temperature get rounded up/down before it is seen as my target? I would think 43.2 is >= 43.... This particular device is a Zooz ZSE44, but I have other brands that act the same. Thoughts???
There was a recent post (within the last month IIRC) that mentioned a possible bug where Rule was doing a > comparison even though >= was selected. I did a search but can't find it.
Anyway, turn on logging for the rule and post those results.
42.x wouldn't ever trigger it as 42.x is always < 43, so those last logs there all look good to me.
As far as why 43.x doesn't work or works inconsistently, I'm not sure...
If it's ignoring the equal-to part for some reason as JLV mentions above, and something here (app? device? dunno) is having issues parsing decimals, that could explain it (i.e., 43.0-43.9 is being treated as just plain 43)
Yep-- I forgot I changed that by 1 degree (42 to 43) last week when I was trying to track this down. Best I can tell the decimal is the issue. 43.3 triggered it today, but previously it needed to be .5 or higher. Because of this issue, I raised it 1 degree (>=43) instead of 42 because the rule that turns it off is doing the same thing and I needed to seperate them a bit so they were not triggering each other. I don't recall this being an issue previously...
Thanks Sebastion. For now I'm going to leave it at 43. I have another rule that turns it OFF <42. So I think the decimals were causing the issue. I can live with a degree between the ON and OFF. I'll watch them all and post accordingly.
