Ahh - that was actually a mistake in the documentation that has already been fixed (the new docs will update when 1v93 is released). If you specify a 128 bit UUID as a string then it should work fine - the only gotcha is the lack of space in the advertising packet... with a 128 bit UUID there's not much space for data!
Perfect :) and yeah that is a challenge too. My plan for that was to return the custom UUID data in the SCAN_RESPONSE packet - I found this article, the array format for setScanResponse is pretty horrible, I noticed you mentioned you'd log an issue for adding a nicer API, any updates on this?
In the meantime, any tools or references I can look at to help me build a scan response payload? e.g. if I wanted to advertise a custom service UUID with some data
© Espruino, powered by microcosm.
Report a problem