You are reading a single comment by @DrAzzy and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@DrAzzy
My experience with this in it's current state has been that with or without debounce (is debounce implemented as efficiently as it (sh|c)ould be? It seems to make little difference, even though it should be filtering out almost all the noise in my system, including the training bursts), you cannot have the espruino wait for and respond to an RF command. It can turn on listening, and grab a response, but it can't wait for spontaneous commands from afar.
The next question, is whether it ever could be made to perform well enough for that. That means almost constantly getting interrupts and handling them, while also acting like an Espruino.
I think option 3 is the most versatile, and would probably have applications outside RF processing too. Would this be fast enough that the Espruino could run other code acceptably while listening to a 433mhz rf receiver continuously?