Hi,
I used the search function but I didn’t found something like that. Are there plans to implement “ELSE”-function to rules? This would make things a lot easier!
if / then / ELSE
Hi,
I used the search function but I didn’t found something like that. Are there plans to implement “ELSE”-function to rules? This would make things a lot easier!
the v0.9 rule system has been evolved but an else function is still missing.
actually i cannot tell you if / when this feature will come.
so upvote and we will see
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebook
make it so !
Yes, this is a good feature request …
Meanwhile, you can use variables as a placeholder
“IF light is turned on AND security is on THEN turn sound-the-alarm on”
“IF light is turned on AND security is off THEN variable = 1”
Of course depends whole lot on which functions you would like to achieve with else
Maybe to Pimatic 1.0 … 0.9 has many improvements already.
@kitsunen yes, thats the thing. for now you have to make 2 rules for simple expressions.
would be cool if we have something like: if tv is on or lamp1 is on or lamp2 is on or onkyAVR is on then set $someoneIsAtHome to 1 Else set $someoneIsAtHome to 0
instead of writing two rules. no big deal. im totally ok with doing that. just a wish for the future
Should be more like an “ELSE IF”. Because “ELSE” would always be the case if some other device or variable changes.
Hello to all developers here, I know this post is already a few days old 😉. But are there still ambitions to make something like this possible? I think many other users would be happy about it. Unfortunately I can not estimate in the slightest what effort that would require.
But I could imagine that with something like this, pimatic will be safer for the future and there will be many new users as well.
Unfortunately, all those who have written here have been offline for a very long time.
"Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)