mc-Things

mc-Products => mc-Product General => Topic started by: millennial on January 29, 2017, 04:23:49 pm

Title: Device Type data in Beacon Bytes?
Post by: millennial on January 29, 2017, 04:23:49 pm
mc-Studio is able to determine whether a device is the mcGate110, or a mcMod110/120. How is it doing this? Perhaps device type can be added to the next version of the beacon protocol, or the mc-Things team can share the UDP protocol that allows asking for this information.
Title: Re: Device Type data in Beacon Bytes?
Post by: mc-T2 on February 01, 2017, 04:28:59 pm
This doesn't happen through UDP, this is an exchange between gateway and mcStudio.

Also, here is no more space within the beacon to add this.

With some of the innovations that are coming up (more info to follow!) all the device information will be available in mcStudio (with the ability to 'name' devices for easy reference)
Title: Re: Device Type data in Beacon Bytes?
Post by: millennial on February 03, 2017, 08:58:21 am
Also, here is no more space within the beacon to add this.

This is why I suggested to add "device type" to the next version of the beacon. There is a beacon version in the beacon, so this should be possible because beacon parsers will know how to act based on the version byte.

Innovations to mc-Studio will not be enough for our use case. Unless we can infer the device type of 5, 10, or 100 devices automatically through UDP, it will just be adding more complexity to deploy a multitude of devices simultaneously. Manual data entry and retrieval in mc-Studio is not solely what we want. Perhaps there can be an API release (perhaps over UDP, or whatever protocol mc-Studio uses) to garner this information through our own network applications.