[Solved] UniPI Evok Relais

---

Hello a question,

I use the UniPI on EVOK interface, but if I want to turn several relays simultaneously remains only the last.

 "rules": [
    {
      "id": "sperre-bahnen-turen-zu",
      "name": "Sperre Bahnen Türen1 zu",
      "rule": "when contact of UniPi Digital Input 1 is closed for 3 second or when contact of UniPi Digital Input 2 is closed for 3 second then switch Relay 1 on",
      "active": true,
      "logging": false
    },
    {
      "id": "sperre-bahnen-turen-zu-3",
      "name": "Sperre Bahnen Türen2 zu ",
      "rule": "when UniPi Digital Input 1 is closed or when UniPi Digital Input 2 is closed then turn Relay 2 on",
      "active": true,
      "logging": false
    },
    {
      "id": "sperre-bahnen-turen-zu4",
      "name": "Sperre Bahnen Türen3 zu  2",
      "rule": "when UniPi Digital Input 1 is closed or when UniPi Digital Input 2 is closed then turn Relay 3 on",
      "active": true,
      "logging": false
    }

@mwittig
Marcus could you have a look pls.
Thx a lot!!

@elru Next time please quote code in your posts as described here https://forum.pimatic.org/topic/1179/how-to-post-code-on-the-forum.

I have tested your rules which work fine for me. All three relays will be switched on. However, one relay is being switched about 2s later. This should not be case eventhough “simultaneously” is not achievable as you have three independent rules executed sequentially and three call-outs to evok. I’ll have closer look at this to find out why there is this significant delay for one action.

Thank you first , I look to hear from you if there is something new .

@elru Actually, I did not recognize the first rule contains the predicate “is closed for 3 second”. This is why one relay switches on later. So everything works as expected.

No that is korrekt.

My problem is, I can´t close two or more Relais at the same time only one of it swith.
i wont that
"when …then turn Relay 1 on and turn Relay 2 on and turn Relay 3 on"
But it dosen´t work.

Hello,
I’m not involved in the UniPi-Plugin.
But would the work like this:

"when ... then turn Relay 1 on and after 5 seconds turn Relay 2 on and after 5 seconds turn Relay 3 on"

the 5 seconds delay you can adjust to your needs.(1-5 Seconds)
My rule was working then.

mfg
Chris

@chris Possibly I did not understand what @elru is trying achieve here. I thought it is about switching all relays simultaneously of input 1 or 2 is closed.

@mwittig @elru
yes i just meant:
when you gave the controller a short while (1-5 seconds) to send the command, then the rule worked for me.

I had a rule to switch all my devices (433MHz) off by one button,
the rule worked only when I inserted the short wait.

mfg
Chris

Yes Chris exactly I try all or more relays simultaneously turnon or off.

If I install a delay so as thou hast done this it goes. but that is not that what I want.

Guys, for me it works without flaws! If I take out the “for 3 second” from the first rule, all relays are switched almost simultaneously. There is a gap of perhaps less than 50ms between the relay actions in my setup which is due to fact that three rules are executed sequentially. You can put the three actions in one rule to minimize the delay, however, the callouts to evok will still be executed sequentially. It it slower in your setup this may due to slow network performance or high load on the involved hosts. May setup is as follows:

Raspi 3 with piamtic 0.9 <----- 100 MBit LAN ----> Raspi B with evok

Of course, it is also possible to run Pimatic and Evok on the same host.

EDIT: Here are my test rules for the following behaviour: “If DI 1 or 2 is in closed state for three seconds turn relay on. After the relay has been turned on for 3 seconds turn relay off again”

{
      "id": "sperre-bahnen-turen-zu",
      "name": "Sperre Bahnen Türen1 zu",
      "rule": "when contact of UniPi Digital Input 1 is closed for 3 seconds or when contact of UniPi Digital Input 2 is closed for 3 seconds then turn UniPi Relay 1 on for 3 seconds",
      "active": true,
      "logging": false
    },
    {
      "id": "sperre-bahnen-turen-zu-3",
      "name": "Sperre Bahnen Türen2 zu ",
      "rule": "when contact of UniPi Digital Input 1 is closed for 3 seconds or when contact of UniPi Digital Input 2 is closed for 3 seconds then turn UniPi Relay 2 on for 3 seconds",
      "active": true,
      "logging": false
    },
    {
      "id": "sperre-bahnen-turen-zu4",
      "name": "Sperre Bahnen Türen3 zu",
      "rule": "when contact of UniPi Digital Input 1 is closed for 3 seconds or when contact of UniPi Digital Input 2 is closed for 3 seconds then turn UniPi Relay 3 on for 3 seconds",
      "active": true,
      "logging": false
    }

Hello it’s fascinating,
if I want to turn themselves only with a sofware botton three relays simultaneously reacting all but mostly attracts only one really on. individually’s all good. I run everything aul a host raspberry 2 b +