Currently receiver can turn on programmable board for one cycle, issue is that we can't extract actual message receiver got. One solution would be to keep this message and be accessible over API instead of only be accessible over event. Another solution could be to fire message receive event after PB toggle cycle which would allow for PB to start and initialize before message is being sent over event listener.
Additionally. Could we get configurable timer for receiver to keep PB (on signal) turned on before toggling it off? At this point it only keeps for one cycle and is quite limited in its use as it is. This could be completely optional and by default could behave as it is, so that we could only enable this longer toggle when we actually need it.
Currently receiver can turn on programmable board for one cycle, issue is that we can't extract actual message receiver got. One solution would be to keep this message and be accessible over API instead of only be accessible over event. Another solution could be to fire message receive event after PB toggle cycle which would allow for PB to start and initialize before message is being sent over event listener. Additionally. Could we get configurable timer for receiver to keep PB (on signal) turned on before toggling it off? At this point it only keeps for one cycle and is quite limited in its use as it is. This could be completely optional and by default could behave as it is, so that we could only enable this longer toggle when we actually need it.