[Solved] Eventor behavior (bug/feature?)

[Lichtsignaal]

Time to add a a little something.

Following is the case. Couple of ESP’s with Relays and PWM output managing my local lights. In my dashboard I have a single button to switch all lights on/off. This is just a V-pin button, so there is no code. The ESP’s have just a simple BLYNK_WRITE to turn on/off the relays (also V-pins).

Eventor widget:

ESP’s:
Event: At 6.00am switch on V-pin 26
Event: At 7.00am switch off V-pin 26

Button on V-pin 26
Event: When V-pin 26 is HIGH, set V-pin 24 High (Relay 1), also set V-pin 25 High (relay 2), also set V-pin 23 to 1023 (PWM output on 2nd ESP).
Event When V-pin 26 is LOW, set V-pin 24 to 0 etc.

Now. when I add the V-pins to the timed Event everything works fine, but when I try to trigger all V-pins to turn on on V-pin 26 HIGH it doesn’t work.

I figured if I combine all my lights in 1 V-pin it makes the Events much easier to follow. E.g. when I add a new relay I only have to add it to the two Events on V-pin 26 (which has two events, all on, all off).

Any thoughts?

[Gunner]

I don’t know why it isn’t documented clearer, but in my testing a while back I found that with Eventor, set pin to is “likened to PWM” in that it can be set to a range of 0-1024 (or whatever, depending on MCU), so setting to 1 is still LOW

Use either a high enough range to actually trigger a HIGH signal or use turn ON pin

Eventor switch On on time is OK, as for the OFF part not OK

When using direct pin control in the App, it is generally one widget per pin… the inventor can still affect that, but I wonder if the switch mode or perhaps the pin choice is causing issues?? Add in a notification for both ON and OFF events, that way you have dual responses to track Eventor or Pin issue. PS I realized that the TZ only shows if you set something different than the default.

[SOLVED] Eventor working just in one direction

There is a possibility that your relay is one of those that activates on a LOW and deactivates on a HIGH? Also here are some basics that I think are how the eventor choices work… Using set pin to allows a range of numbers, as in PWM, so 0 is “ON” for your relay, but so is 1… and probably anything up to around 512… at which time there might be enough change to trip the breaker… use 1023 instead and that would set the pin fully HIGH or “OFF” for your relay. Or just use the easier option and us…

[Lichtsignaal]

That;s good and all, but you cannot use turn ON with Vpins…

-edit

Guess I could do with sync feature, but I’d really like to prevent coding on the hardware side to keep things as simple as possible.

[Gunner]

Guess I wasn’t paying attention to the V part of the whole Vpin

But still, how does setting a vPin to 1 (or anything) trigger something on the hardware without hardware side code?

[Lichtsignaal]

Because it triggers another Event. So I’d like to combine Events so I can just have one trigger.

E.g. Event1 triggers Event2 and Event3 to do something.

[Gunner]

Got ya… In that case IDK… I once tried to make a Virtual LED automatically flash ON and OFF, all in Eventor, and nothing happened… I gave up and always used code from then on…

[Gunner]

Interesting… I was curious, so I set up a simple cascading “cause and effect” scenario with Virtual Buttons in “button” NOT “switch” mode… and it half works…

… Pressing 1st button visual changes the 2nd button’s state…

…but waits until that 2nd button is manually pressed before processing that state change… and so on…

So instead of an automatic chain of events, it needs to be manually activated each step.

Probably what you are running into @Lichtsignaal… so issue confirmed!!

[Lichtsignaal]

Yeah, sort of like that! Thank you for duplicating the issue

[Dmitriy]

@Lichtsignaal @Gunner ha, I knew someone will try to do that . This is done by design. Otherwise, any user may setup endless recursive flow that eventually will kill the server.

I’ll update doc accordingly.

[Gunner]

@Dmitriy

This is done by design. Otherwise, any user may setup endless recursive flow that eventually will kill the server.

It can still have useful benefits I guess… can’t you mitigate the “dead server” potential the same way you have “fixed” the flooding issue?

[Dmitriy]

@Gunner Well, 1.5 year passed since we introduced Eventor and this is the first time someone tried this feature. I think you got what I’m trying to say .

[Lichtsignaal]

Guess I’ll just go back to the old ways and include more code to adjust for this specific button issue.

I’ll just code a second or third V-pin in all hardware. So be it!

[Gunner]

@Dmitriy

and this is the first time someone tried this feature

No, it is the first time someone has conclusively diagnosed how it doesn’t work I know I did try it, but moved onto coding instead. But now that it is known, perhaps someone else might want to validly use it, and as I just mentioned, you did “fix” the potential flooding issue already.

[mpo881]

@Dmitriy way back in Oct "16 the post was made that Eventor will soon be available in IOS. Did I miss something? I still do not see it in IOS. I have latest update for the app.

Continuing the discussion from No Eventor widget in my (IOS) app:

[Dmitriy]

@mpo881

Did I miss something?

Nope. Eventor is still not released on iOS. It is not a priority right now.

[mpo881]