@didou
then check your sensors in an async way, far better than using wait.
there are different way of writing this, but here an example, maybe easier to read when new to programming : https://www.arduino.cc/en/tutorial/BlinkWithoutDelay
In this example, instead of toggling leds, process your sensors.
Also, maybe start simple, like a sketch processing your sensors as you wish, then once it's working well, add MySensors lib
seems arduino learning related 
you mentioned sleep in your first post, and I think wait might delay your irq processing too
just in case, in theory (no time for testing), D3=PA05(gpio name under the hood)=IRQNUM is 5 so you could replace the digitalTointerrupt function by the irq mapping name; 5 for D3, or 7 for D4.
so just as an example, revamping your example, the logic should look something like this
volatile bool myIsrTriggerVar = false
setup() {
attachInterrupt(digitalPinToInterrupt(MYSX_D4_INT), myInterrupt , FALLING); // means attachInterrupt(7, myInterrupt , FALLING);
}
loop() {
if (myIsrTriggerVar) {
// process your irq here
#ifdef MY_DEBUG
Serial.println("Motion Interrupt");
#endif
send(MotionMsg.set("1"));
// reset flag
myIsrTriggerVar = false
}
// wait(60*1000); // Wait one minute between each probe (60 * 1000)
}
void myInterrupt()
{
detachInterrupt(digitalPinToInterrupt(MYSX_D4_INT));
myIsrTriggerVar = true
attachInterrupt(digitalPinToInterrupt(MYSX_D4_INT), myInterrupt , FALLING);
}
Hello,
if you're planning to use it as a gateway, then don't use sleep function else it will miss messages..it won't wake up on receive like you said.
as you noticed sleep is not implemented for SAMD mcus, like sensebendergw
mapping of SAMD does not work like well known avr8 328p for example. Did you use digitalPinToInterrupt ?
https://www.arduino.cc/reference/en/language/functions/external-interrupts/attachinterrupt/
like attachInterrupt(digitalPinToInterrupt(3), myisr, CHANGE ) for your "D3.
@evb
samd21 can have a few independant spi bus (depends on the samd21 variant and pincount).
these spi bus needs to be defined in boards definition files.
the mcu on arduino zero is able to do that, but it is maybe used by some other stuff like the onboard debugger, can't tell you more about this because I always made custom board with all peripherals available (and no time to compare the Zero schematic vs datasheet).
back to your problem, just to be sure did you try something like this:
#define MY_RFM69_IRQ_PIN 2
#define MY_RFM69_IRQ_NUM digitalPinToInterrupt(MY_RFM69_IRQ_PIN)
or
#define MY_RFM69_IRQ_PIN 2
#define MY_RFM69_IRQ_NUM 14
@evb said in Arduino Zero clone SAMD21 M0 board with RFM69HW sending but not receiving parent response:
As test sketch I'm using the example pingpongsensor example adapted for the RF69 radio.
The IRQ pin is not defined, because I thought that mysensors lib takes pin D2 as the default.
Out of range is normally not the case, they are at 10 cm of each other...
not the case for ARM mcus which are very flexible, MySensors cannot cover all makers boards and their different mapping That wasn't a problem with regular AVR8 328p which has fixed mapping but tends to become obsolete and limited imho
So your sketch example is still missing the above defines..this is a mandatory for your board.
Could you show your logs with those defines enabled plz
Note it could also be the range, if the antenna was not good, or wrong power settings etc. I even read once people forgot to add an antenna etc 
but for the moment I think it's pin mapping, as there is no problem with MySensors SAMD afaik
from your logs, it seems your SAMD21 board irq is not triggering, so Find parent fails.
it could be a very few things:
but I feel it could be 1).
It could be related to your defines, but you haven't posted your test sketches, so can't tell you.. 
Note: I don't remember though if 'virtual' eeprom is handled for SAMD in MySensors (HW support might be basic) as these mcu don't have integrated eeprom. so in case you need it in future, you could add one, could be handy for a gw.
@zboblamont
Hi.
Maybe I misunderstood, but I don't use a sdcard on my rpi3, it directly boots on ssd.
That said for reliability, or longterm use and possible HA evolution, sure a rpi is not ideal, even the rpi4 could be quickly limited, + tests says it heats more.. (though for the moment usb boot is not released)
Because it depends on what you'll need in future, a NAS storage feature like openmediavault, cameras motion management, a media server (plex, emby/jellyfin), adblocker, IA, voice assistants etc. so many nice services to use. Then a x86 intel/amd solution might be a better solution, a lot more powerful, very well known solution. some cpu have very low tdp but I think this electricity cost variable needs to be compared to the ROI..
maintaining only one server machine might be easier too vs a swarm of RPIs.
So:
All solution are nice, like I said it really depends how many service you'll want to run in future
@zboblamont
for filtering output of switching converters, it's easier when you know the parts used (reference of ic, inductor). then you can get some "filtering" calc vs load, freq etc.
It can help using low esr ceramic capacitors (ideally x7r dielectric). 10n+100n like skywatch said won't hurt sure, I would add maybe 22n and 22-47uf. It might improve. Otherwise, try adding 1-2 more low value capas.
Then if not enough, I would a ferrite bead in serie and add another 10n/10u combo. But you need the right reference else it can be worse (3 datas are important for this choice: impedance and freq, low resistance, and max current). But it's easier when you have an oscillo for checking.
Else a good high psrr LDO+a few caps for very sensitive circuit (like those for rf..) but sometimes there is no other choice than switching converters (they are handy too).
And depending on the circuit, there are additional things to do (using tvs etc), but I don't think that's your case here.
I hope this helps a bit!
@peter-loeffler said in Ethernet/WiFi-Client Gateway enhancement:
@scalz please don't get me wrong!
I just "clarified" things. In your posts you were debating about how this stuff should be named or not, how should work a gateway example firmware, what features should have been provided etc. a picture of your archi needs would have been more useful.
....but:
why is there a "feature requests" section, when you tell mea) write yourself whatever you want
b) take it as it isas MANY others already asked in this forum, there is (not only me) a always re-appearing demand for enhanced hardware/tech. (eg IP)
your turn! trying to get me wrong. kidding 
what's a feature request section in a non remunerated opensource project with limited resources?
sort of "todolist" !
I don't think the context implies any duty nor deadline.
That's why community is patient when they need something for free. Or they find workarounds if they are in hurry.
Will a feature request fullfill your need in short term. I don't think so..
If you need this for a professional project and are in hurry (you mentioned many greenhouses)
do you have better options than a) or b) ?? maybe
c)if really in hurry, hiring someone
d) if no hurry or you don't feel comfortable with coding, wait for community or future releases, try mfalkvidd solution or nodered
usually people chooses d)
Releasing takes time then support..free time (time==money..) that I do not have for the moment.
I really hope you'll find a solution/workaround for your project
@Peter-Loeffler
Not completely sure if there is any overhead in your whole archi, but I think now I better imagine how it looks.
Regarding your previous comments, it seems you didn't know what exactly MySensors provides for the moment, and had maybe too much expectations??
Still there are always different ways to do things !
Let's try to clarify some points (as far a s I remember):
So users can publish their work when they want to share etc..
What you're asking is an extended usecase which is not covered yet.
I'm sure there is certainly different ways of doing what you need.
for example, here I also use esp32s, some in AP mode too, with http server for webapp, websockets server for comm with ethernet clients (can be used for bridging), serial cli&proxy, RF transports etc.
It's an example of what's possible when coding by yourself (private local code for the moment..as I have no time for providing support/users wishes, also very busy with real life job).
So you can:
@Peter-Loeffler
well just re-read what I said, and what infos you gave us
even atm I still don't really get it, you're now talking about rs485, serial to esp8266.. but you started by telling us "I have a bunch of ESP32DEVKIT modules lying arround and want to use them with wifi" . not much more
mfalkvidd also explained that esp8266/32 can be used in gateway mode, and gateway id is 0.
I don't see why topic-id would be the same when using a dedicated mqtt, rest lib
what's the hw for the sensors nodes(I guess when you say 20 equal sensors you mean 20 nodes with 4 connected sensors per node)? gateways specs? your controller sw? the architecture (rs485, wifi, serial connections)? etc..
then maybe I hope we can help/guide you better