Search results for:

👍👍👍

Yes, yes, it is indeed this issue.

I can read it after writing, so I can read the value I wrote. Just write => read.

no no no no no... writing does work!
just the callback function onWrite() is not implemented
I can both read and write / edit the value of certain characteristic, but could not call the onWrite() callback function
In my conception, I should write / edit the value of characteristic A, and then my ESP32 call the onWrite() callback function to verify this value. If the value is valid, ESP32 will change characteristic B to readable mode.
Just like some kind of encryption verification.

I plan to learn the source code when I have some free time in a while and try to solve this problem (since I don't have a hardware background myself, I actually find it a bit difficult, though you say it's easy).

There are indeed some issues with ESP32, sad...

After solving the existing problems, I found that callback function for onWrite() is not implemented.
And Unable to implement the notify and indicate, my phone always reports error when sending notification listening requests to ESP32.

NRF.setServices({
  0x1901: {
    0x1902: {
      value : "Hello",
      broadcast : true,
      readable : true,
      writable : true,
      notify : true,
      indicate: true,
      onWrite: (event) => {
        console.log("Got: ", event);
      }
    }
  }
});

This is really wonderful. Thank you all very much for your selfless and kind work, which has inspired me so much!

This is really wonderful! This further enhances my motivation to handle many tasks later on, Many thanks for you!

It works! It works! It's actually well done! WOW~ It's splended!

wow! Thank you!

It's so nice of you!
Your guidance and tips have given me lots of inspiration and encouragement, yet it also poses certain challenges for me. I'll try to build from source and try to fix it during this summer vacation! ^_^

Yes, Espruino firmware version of my ESP32 board was updated to 2v21 version.
Seems the problem is not with the public code, but rather with EPS32.

It is issue of ESP32 port. I have just tried the code without quotes and dashes:

NRF.setServices({
  a18419019ed149b3b998172d8f29b213 : {
    a18419029ed149b3b998172d8f29b213 : {
      readable : true,
      writable : true,
      notify : true,
      onWrite: (event) => {
        console.log("Got: ", event);
      }
    }
  }
});
NRF.setAdvertising({}, { name: "ISP" });

It does not work.

F 6
F 0
Uncaught Error: invalid Char UUID:UUID string should only contain hex characters and dashes at line 12 col 2
});

May be there are some bugs in ESP32 code.

recent now, I've tried:

a1841902-9ed1-49b3-b998-172d8f29b213 : {...

and:

"a1841902-9ed1-49b3-b998-172d8f29b213" : {...

and:

'a1841902-9ed1-49b3-b998-172d8f29b213' : {...

and:

0x1902 : {...

and:

"0x1902" : {...

and:

'0x190' : {...

none of them succeeded.

so sad... it dosen't work, told me:

Error parsing JavaScript, but uploading anyway.
SyntaxError: Unexpected token (3:12)

Uncaught SyntaxError: Got '-' expected ':'
at line 3 col 13
a1841902-9ed1-49b3-b998-172d8f29b213 : {

Is there a problem with the regular expression for verifying Char UUID's validity?

I am trying to send this command to my ESP32:

NRF.setServices({
  "a1841901-9ed1-49b3-b998-172d8f29b213" : {
    "a1841902-9ed1-49b3-b998-172d8f29b213" : {
      readable : true,
      writable : true,
      notify : true,
      onWrite: (event) => {
        console.log("Got: ", event);
      }
    }
  }
});
NRF.setAdvertising({}, { name: "ISP" });

Then the console reported an error:

F 0
F 0
Uncaught Error: invalid Char UUID:UUID string should only contain hex characters and dashes at line 12 col 2
});

I changed the Char UUID to 0x1901, but it still doesn't work.

好好学习，天天向上。