30211aa006
https://github.com/google/eddystone/tree/master/eddystone-url#frame-specification states 1-17 When one makes a general google for the max length, some have written 18 and some 17 :( The difference could lie in the https://github.com/google/eddystone/tree/master/eddystone-url#url-scheme-prefix which adds an extra byte but it's use is to in someway allow for more bytes in the 1-17. The implementation in the micro:bit Lancaster is unknown as to how the url-scheme-prefix is or is not used: there does not seem to be a scheme for "Just take the 1-17" for the url. At the moment, "play it safe" and write 17 ?