https://devzone.nordicsemi.com/f/nordic-q-a/14049/eddystone-url-parser-is-broken-in-mcpIn the MCP app, if I have the following service data for an Eddystone beacon: 0x10, // Eddystone-URL type 0x00, // TX power in dBm. This is a signed integer so 0xEE = -18, 0x00 = 0 dBm, etc. 0x01, // URL scheme. 0x01 is ' https://www.' 't',en-USTelligent Community 13Tue, 14 Nov 2017 10:43:53 GMT