Let's Control It

hi

In my test setup, longpress only works once after starting. I have eight buttons (on a switch input - PCF8574), the long press event is only sent once for each.
Longpress min. interval (ms) ist set to 1000ms and running ESP_Easy_mega_20210114_normal_ESP8266_4M1M. Any ideas or help?


Thanks.

Will have a look at it.
Can you post the screenshot of the device configuration?

thanks, here is my configuration

You are using an inverted logic, where HIGH=1.
Have you tried to flag the "Inverted Logic" option?

Thanks, but I didn't see why i use inverted logic? For me 1=HIGH ist normal

I still activated the option and tried all possible settings. All variants send LONGPRESS only once.

Then I did a downgrade (mega-20200426). With this version everything works correctly, LONGPRESS is sent every time.

What may have changed since this version?

I have seen another reported issue on the latest (or maybe last 2) builds regarding the GPIO expanders.

It is in an unrelated PR on GitHub, but it looks like it may be the same issue as you're seeing: https://github.com/letscontrolit/ESPEas ... -773838731

herber_ch wrote: ↑06 Feb 2021, 21:35 Thanks, but I didn't see why i use inverted logic? For me 1=HIGH ist normal

I still activated the option and tried all possible settings. All variants send LONGPRESS only once.

Then I did a downgrade (mega-20200426). With this version everything works correctly, LONGPRESS is sent every time.

What may have changed since this version?

Hi @herbert_ch
I mean that you are using ACTIVE=HIGH. Is this what you want?
The PCF8574 has ACTIVE=LOW. It means that it has state=1 when not pressed, and state=0 when pressed.

Try using
"Doubleclick event: Active only on LOW"
"Lonpress event: Active only on LOW"

Finally, if you don't solve with the above changes, can you try a version built in december 2020 (20201227) to understand where the problem has been introduced?

hi

Sorry, i have been away for a long time for personal reasons. but now i'm back and want to solve the problem.

I mean that you are using ACTIVE=HIGH. Is this what you want?
The PCF8574 has ACTIVE=LOW. It means that it has state=1 when not pressed, and state=0 when pressed.

Ah, now i understand. But i'm not using a regular switch but a TTP223 Touch Sensor witch is inverted also. So it shoud double invertet = normal ?

I have tested many older builds (without change the config) to find out, when it started:

• Build 20201016 Longpress work normal
• Build 20201022 Longpress only works once

so it must be any change in Build 20201022 (https://github.com/letscontrolit/ESPEas ... a-20201022) that is causing the longpress to stop working. any ideas what that could be?

This elaborate PR was merged in between those builds, so I guess it would very likely be related to this PR: https://github.com/letscontrolit/ESPEasy/pull/2778

this seems to be about this issue. but most of it doesn't mean anything to me, I'm not a programmer.

is there anything i can do or help?

I asked the author of that PR to have a look.

Not sure if he is on holiday right now, he hasn't read his Slack message yet

Hi,
I need sometime to setup a PCF expander in my lab.

In the meantime, can you make the following test:
1) disable the doubleclick event and try to see if longpress still works only once
2) reduce the doubleclick time to 500ms and try to see if longpress still works only once

then report back your findings.

thanks

hi

Tested with build 20210503:
1) if I disable doubleclick, longpress also only works once
2) reduce the doubleclick under 1000ms is not possible, there is a check for that

I also tested:
- doubleclick=1000, longpress=5000 => still works only once, but the event 11 comes after about 1 second
- doubleclick=3000, longpress=1000 => still works only once, but the event 11 comes after about 3 seconds

ok. Thanks for testing.
Can you try to set "Longpress event" = "ACTIVE only on LOW" ?

And then report back?

Tested also with build 20210503:
- "Longpress event" = "ACTIVE only on LOW", doubleclick=1000, longpress=1000=> still works only once

Hi,
Bug is confirmed and solution will provided ASAP.

Please see: https://github.com/letscontrolit/ESPEasy/issues/3736 for updates.