" and " in rules either not implemented or not working. about rpieasy HOT 5 CLOSED

I am afraid there are some more hidden bugs.. But thanks, this one closed.

from rpieasy.

It's interesting as "and" worked in my first testings.. could you switch Log level to Debug and see "Parsed condition" lines? I will check it today evening. /it's morning now here :) /
In fact "and" is not implemented by me, i am using the Python Eval() command to evaluate expressions. There must be some string related problems such as 0.00 is not equal to 0 or type mismatch. Could you add some detail about "station" and "auto"?

from rpieasy.

"Station" is a dummy device where I store values. The hours value is incremented up 1 every hour. After a set time this value is used to start the watering sequence. So [station#hours] is just a dummy value.
"Auto" is a switch connected to a PI GPIO. "auto" is the switch name and "switch" is the value name. So [auto#switch is simply a switch that is either 1 or 0. (input pullup) in the hardware settings.

192.168.1.62 Feb 11 22:35:00 RPIEasy kern debug Irrigation Parsed condition: if 48>47 and 0=0 False

Debug Developer Level. Above line is all that shows. I get that via syslog. I do not have serial connected. If need be I can set that up.

from rpieasy.

== is not equal to = in python.. using eval() is convenient choice, but equal signes needs to be converted back and forth.. i think it is fixed in commit 60ec0f8

from rpieasy.

Another bug seems to have been exterminated!!

from rpieasy.