At the moment, we haven’t added support for interrupts on the GrovePi, but it’s something we definitely have to consider in the near future.
Since the communication is initiated by the Raspberry Pi, this means the Pi is still responsible for polling in the data, but it should be done behind the scenes without letting the user feel like he’s the one polling in the data. Think of this like some food for thought.
Really, @s.maam, if you’ve got more ideas on how we can improve the GrovePi, please tell us here. We’ll take into consideration anyone’s suggestion.
I am concerned with the problem that GrovePi (with internal Chip/Controller) and the connection via I2C to the RaspberryPi, which means that it’s hard to capture hardware interrupts at sensors which are connected with GrovePi.
So maybe there won’t be a chance to fix this problem via software, I think.
Are there currently improvements with interrupts, for example hardware / software updates?