Yes, I think that's to be expected. It's exactly what the NFC stack passes back to Espruino (Espruino doesn't check to see if it was on before sending an off message).
I think you only get NFCon if the NFC connection has progressed to a certain point, but you get NFCoff if anything happened but then stopped - so the proportion of off to on events probably gets greater the further you are from the Pixl (and so the more unreliable the connection).
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.
Yes, I think that's to be expected. It's exactly what the NFC stack passes back to Espruino (Espruino doesn't check to see if it was on before sending an off message).
I think you only get NFCon if the NFC connection has progressed to a certain point, but you get NFCoff if anything happened but then stopped - so the proportion of off to on events probably gets greater the further you are from the Pixl (and so the more unreliable the connection).