In 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', 'e', 's', 't',
0x00, // short for '.com/'
Then the tag actually works, but the MCP app doesn't understand the TX power byte (maybe it wasn't in an earlier version of the spec? So it interprets the URL wrong - it comes out as http://www..org/test.com/