...
Device may not have sample payloads - There may no longer be enough live data to pull from. In this case look to see if sample_payloads is defined in the Template. If not, add it with good data that can always be pulled from [Shramik currently handling this].
Sample readings are random, can be duplicated - The data pulled for the sample (whether live or sample) is random. This means it is entirely possible the same data can be pulled multiple times even though you’ve clicked the button. There is an enhancement request for this [See eptak’s list of tasks]
Special Case: BLE / Beacons required (requires_template_id)
| Info |
|---|
We added this to solve the ‘Beacon also needs to be present’ scenario, but one could imagine we’ll have more situations where a device won’t work unless ‘this or that is also present’ that will need to be solved as well. |
There are some special cases where an additional BLE device or beacon is also required or the device won’t function properly. E.g. it’s not much use to allow a customer to add a BLE Tag if there isn’t an appropriate BLE gateway device also added that would tell us which location is being pinged.
In this case we allow an additional requires_template_id Attribute which will then pull in say a beacon device as well. I.e. when you add a GlobalSat Multi-Press button, during the Add process it will also add a simulated beacon device (the Add process walks the user through adding both when the simulated device is added). The sample payload for the simulated button refers to the simulated beacon for position info.
Here is an example from the GlobalSat Panic Button (Multi-Press) template.
...