Checking variable at Pimatic start (building correct rule)

---

Hi! I have one question about one rule:
I have a rule, which send to me status of my garage doors ($gdoors): (opened, closed)

Rule syntax:
If $gdoors changes (gets update) then send mail to me@mail.ru

Problem: at Pimatic start system is see, about doors is closed and send me e-mail, and it is send every time when Pimatic is restart(start). How I can build a correct rule, for Pimatic is not send e-mail, at every restart, I want e-mail if only variable changes from closed to open and open to closed, thanks!

First thing I would try is to set the term into brackets like IF [$gdoor changes] THEN do some stuff…

@leader21 said:

First thing I would try is to set the term into brackets like IF [$gdoor changes] THEN do some stuff…

but I guess this won’t do the job.

i have the same issue for my “turn everything off switch”

It’s like this: if switch1 is turned off then ...
Since the button “is turned off” when pimatic starts, the rule is executed.

That’s why I’d like a predict for the rules: if pimatic is starting then ...

But @sweetpi already said this would be a more complex issue

[brackets] not works

@MocArt
I have no mail-plugin installed but with pushbullet and this rule it works fine here.

"rule": "if $gdoors changes then push message:\"garage is $gdoors\"",

Here a workaround how you can prevent messages witch are pushed on pimatic startup by changed variables via script or shell…
create a variable $startup

rule 1: startup (I have placed this rule on first place…? OK tested, works also with 1 second on last place)

if pimatic is starting then set $startup to 0 and after 1 second set $startup to 1

rule 2: this rule will send the message only when $gdoors changes after startup

if $gdoors changes and $startup = 1 then push message:\"Garage is  $gdoors\"

@magic-tune said:

Here a workaround how you can prevent messages witch are pushed on pimatic startup by changed variables via script or shell…
create a variable $startup

rule 1: startup (I have placed this rule on first place…? OK tested, works also with 1 second on last place)

if pimatic is starting then set $startup to 0 and after 1 second set $startup to 1

rule 2: this rule will send the message only when $gdoors changes after startup

if $gdoors changes and $startup = 1 then push message:\"Garage is  $gdoors\"

@magic-tune great idia, this method is works! SOLVED

@magic-tune

Nice solution!
But it’s not working for me with this rule:

lichtallaus
if [homeduino-remote-a is turned off or homeduino-duwi2 is turned off] and $startup = 1
then turn homeduino-lampe-fenster off and turn homeduino-lampe-sofa off and turn homeduino-lampe-tv off and turn homeduino-duwi2 off and turn homeduino-remote-a off

alloff
if [homeduino-remote-d is turned on or homeduino-duwi1 is turned on] and $startup = 1
then turn LED Event on and turn off homeduino-lampe-sofa and turn off ...

log
14:05:34.634 [pimatic] info: New device "Internet"...
14:05:34.644 [pimatic] info: New device "System"...
14:05:49.146 [pimatic] info: rule startup: set $startup to 0
14:05:49.184 [pimatic] info: rule lichtallaus: turned Duwi2 off
14:05:49.185 [pimatic] info: rule lichtallaus: turned Gemütliches Licht off
14:05:49.205 [pimatic] info: rule alloff: turned LED Event on
14:05:49.209 [pimatic] info: rule alloff: turned Gemütliches Licht off

startup
if pimatic is starting
then set $startup to 0 and after 30 seconds set $startup to 1

can you find an error in my rules? startup rule is executed first…so all the other rules shouldn’t be called at all…

@georg90
Hi,
strange…It should fireup with 30 seconds delay when $startup =1
You must use “$variable changes” in the rule.

Try something like this…

if [$homeduino-remote-a.state changes and homeduino-remote-a is turned off and $startup = 1] or [$homeduino-duwi1.state changes and homeduino-duwi1 is turned on and $startup = 1]
then do something...