[Solved] pimatic-phone problem with rules

---

Hey,

i try to use pimatic-phone to switch on my heating devices when the distance to home is lower then 1500m. So when i write the rule:

WHEN phone.distanceToHome is lower than 1500 THEN switch heating on

everything is fine. But if i add an dummy-switch to this rule like this

WHEN dummyswitch is on and phone.distanceToHome is lower than 1500 THEN switch heating on

the rule gets triggerd when i switch on the dummy switch while the distance is still much larger than 1500.
Any ideas why this happens?

daice

@daice, I think it’s not related to pimatic-phone but to Breaking Changes in pimatic v0.9. You should try

WHEN dummyswitch is on and if phone.distanceToHome is lower than 1500 THEN switch heating on

If in doubt regarding the value of distanceToHome enable debugging in plugin and device configuration and inspect the daemon log or console output

I have already tried “and if” but it doesn’t work too. I don’t think that there is a problem with the value. In my opinion it’s a kind of syntax problem with/of pimatic.

@daice said in pimatic-phone problem with rules:

I have already tried “and if” but it doesn’t work too. I don’t think that there is a problem with the value. In my opinion it’s a kind of syntax problem with/of pimatic.

Looks like everyday pimatic rule magic The rule

when distanceToHome of phone is less than 1500 and if state of switch is on then do something ...

is triggered only when the distances changes to a value less than the limit and the switch has been turned on. The rule is not fired

• by toggeling the switch
• if the value was already less than the limit
• on device (re-) creation
• during startup

This behavior should meet you requirements to control the heating.

Have you tested this rule? When i build this on it is fired when i toggle the switch and the distance is still much higher.
Which distance is used? The one i see in the device (DTL in km) or the one from the variable $phone.distanceToHome (in m)?

If i change the rule from

WHEN DummySwitch is on and if…
TO
WHEN state of DummySwitch is on and if…
it’s working…

But it makes no sense to me what de differnece is

Thanks

For the pimatic rule engine the toggle event of the switch (switch is turned on) is different from the check of the device attribute (state of switch is on). For me still a little bit strange is your initial problem that the rule is triggered by the switch event even if you have additional conditions that are not met.

Thanks, solved