Good to see a well documented project with proper BoQ and schematic.

@didou Tryed it today with no luck.

The behavior is globally simillar

loop()
{
unsigned long currentMillis = millis();

// Check Sensors global timer
if (currentMillis - previousMillis >= intervalMillis)
{
previousMillis = currentMillis;
readSensors();
}

// Check Triggers
if (myIsrTriggerVar1)
{
#ifdef MY_DEBUG
Serial.println("Motion Interrupt");
#endif
send(MotionMsg.set("1"));
// reset flag
myIsrTriggerVar1 = false;
}
}

I got the interrupt then mysensor message -> 13:13:07.719 -> 0;255;3;0;5;1 (Motion/V_trigger -> 1)
Then I have to wait for 120 seconds before being able to do an other interrup
Not before I have this message 13:15:07.621 -> 0;255;3;0;5;0 (Motion/V_trigger -> 0) which is not in my own code

How often i do read the sensors do ot have any impact within the 120 seconds or outside of them.
I have roufly checked the mysensor code and haven't seen any such define behavior for Motion/V_trigger)

@scalz will try that as proposed ovoiding wait and let you know. Thanks again.

@scalz Great help yes I get one at least but need to wait 120 sec to get an other one ?

Agree for the attachInterrupt in setup

My loop does also have few sensors read every minutes so I need to both wait for one minute and also been able to catch interrupts

@didou It is reset after 2 minutes then I can send a new interrupt. Where does come from the 120 sec hold time ?

@didou I have also noticed thta I have to wait for a (0;255;3;0;5;0) reset message to be able to capture a new interrupt. I do not send it I guess it is sent by the core ?

@scalz Yes I did try even with something different as CHANGE like FALLING

But seems I was tracking the debug message which it is never displayed in that case !
But the Serial message is sent (0;255;3;0;5;1)

It is working only one time after a GW reset, further test do not fire up the interruption

loop()
{
attachInterrupt(digitalPinToInterrupt(MYSX_D4_INT), myInterrupt , FALLING);
wait(60*1000); // Wait one minute between each probe (60 * 1000)
}

void myInterrupt()
{
detachInterrupt(digitalPinToInterrupt(MYSX_D4_INT));
#ifdef MY_DEBUG
Serial.println("Motion Interrupt");
#endif
send(MotionMsg.set("1"));
attachInterrupt(digitalPinToInterrupt(MYSX_D4_INT), myInterrupt , FALLING);
}

@tbowmo I have seen that no issue but it still should be able to catch interrupt when in wait state ?

@didou I have also noticed that in the MyHwSAMD.cpp there are some functions like hwSleep(....) that are in "ToDo" state. Is that related ?

I do have difficulties using MYSX_D3|D4_INT Interrupts.
I'm using the sensebender Gateway as a Gateway with local sensors that does require interrupt ...

Neither MySensor int8_t sleep (const uint8_t interrupt, const uint8_t mode, const uint32_t sleepingMS = 0, const bool smartSleep = false ) which is not supposed to catch interrupts in Gateway mode or native Arduino AttachInterrupt does catch interrupts on these Pins.

Is there any trick or turn around about that issue ?