TWIG devices use the MPTP protocol. This is a protocol which is maintained by TwigCom. Cuebly understands the protocol and uses it to implement the best possible amount of features.
The protocol can be quite hard to read, so this page is dedicated to have better understanding on how Cuebly is parsing the protocol.
Consider the following communication from a random device:
| Time | Line | Comment |
|---|---|---|
| 10:00:00 | !EMX_100_20231129150944_e,SOS BUTTON_g,,,,,,,,_w,30,bcf31034edd4,MY_SSID,-58_w,30,bcf31034eb94,MY_SSID,-70 |
Start alarm report with wifi position |
| 10:00:01 | !EMX_100_20231129150944_w,30,bcf31034df94,MY_SSID,-74_w,30,bcf31034f154,MY_SSID,-74_w,30,bcf31034ef14,MY_SSID,-74 |
|
| 10:00:02 | !EMX_100_20231129150944_n,-32,2G,204,4,3053,23,-67,227,0_r |
Position report complete |
We can extract information from this data:
e,SOS BUTTON._r is present.w,30. This means that the beacon was found at 10:00:00 - 30s = 09:59:30!EMX_100_20231129150944"After this alarm, the device will perform a new scan for wifi, BLE, radio and/or GPS (depending on your configuration).
When the scans are complete, it will send a new !EMX report with the same ID (20231129150944 in this case).
For example:
BENR,0000,--,91444325,#!EMX_100_20231129150944_e,SOS BUTTON_g,,,,,,,,_w,-15,bcf31034edd4,MY_SSID,-58_w,-15,bcf31034eb94,MY_SSID,-70_r#,0011,nnn
Note that the ages of the beacons now have a negative number (-15).
This means that the beacons are found on 10:00:00 - -15s = 10:00:15. (note that we calculate from the timestamp of the FIRST report)
TWIG regularly updates the firmware of their devices. Since Cuebly is not in control of the changes that manufacturers make, Cuebly will not support every firmware.
It is recommended to test your firmware for your use case before your supply your customer.
CT5P.01.060.0000:
- Cannot validate setting 2321
CT5P.02.001.0000:
- wifi communication issues (wifi for positioning is OK)
CT5P.02.007.0000:
- wifi communication issues (wifi for positioning is OK)
CT5P.02.008.0000:
- wifi communication issues (wifi for positioning is OK)
CT5P.02.009.0000:
- wifi communication issues (wifi for positioning is OK)
CT5P.02.0010.0000:
- wifi communication issues (wifi for positioning is OK)
CT5P.02.0011.0000:
- wifi communication issues (wifi for positioning is OK)
- Timer alarm issues
Without openly pronouncing, TWIG has changed the SRD module hardware on newer models. This has a result that setting 2860 - SRD tranceiver sleep time does not support a value between 0…4min anymore, but has a minimum of 1. This also results in that impacted devices are unable to set the SRD tranceiver on listening for beacons continuously.