The length of the beacon is 17 bytes (Described in the mcBeacon white paper) and that is the beacon that you want to pay attention to
Beacons start with : 0016010D
I understand all of this.
Are you saying there is no significance to anything in the "gatewayUID" field (I am using this name only because that is what the mc-Mod beacon uses) and aptly named "extraBytes" field of the following 21 byte mc-Gateway "pseudo-beacon?"
{
"protocolVersion": 0,
"messageType": 100,
"messageVersion": 1,
"messageSize": 17,
"uid": 70556, (My mc-Gateway ID: "0x0001139c")
"beaconBytes": 3232241325, (Found out to be my mc-Gateway LAN IP: "192.168.22.173")
"RSSI": 107,
"gatewayUID": 107521, (Since a mc-Gateway does not have a gateway, what does this number - 0x0001a401 - signify?)
"extraBytes": 2416444928 (These are the last 4 bytes - 0x90080600 - Not sure if they should be interpreted as individual bytes, shorts, or all together. Perhaps a 144.8.6.0 interpretation makes more sense. Please clarify)
}
Please satisfy my curiosity for the gatewayUID and extraBytes field in this 21 byte "pseudo-beacon." Perhaps I may find an unseen use for that data.