...
| Code Block |
|---|
[
{
"format": "json",
"ignore_codec": true,
"payload": [
{
"channel": 5,
"type": "batt",
"unit": "p",
"name": "Battery",
"value": 88
},
{
"channel": 506,
"type": "co2",
"unit": "ppm",
"name": "CO2",
"value": 250
}
]
},
{
"format": "json",
"ignore_codec": true,
"payload": [
{
"channel": 5,
"type": "batt",
"unit": "p",
"name": "Battery",
"value": 28.57
},
{
"channel": 506,
"type": "co2",
"unit": "ppm",
"name": "CO2",
"value": 500
}
]
}
] |
FAQs
Must I enable Simulator and add Payloads?
Technically, no. Enabling the simulator flag is the only requirement. But in adding devices to the simulator, QA found that very few devices had enough live data to get away with adding the flag only.
| Note |
|---|
After enabling a device in the simulated device list, be sure to add it into an account. If you find that it says ‘Waiting on data’ after being added, that’s an indication that you need to add sample payloads before calling it ready for customers. Another good indicator that samples are needed is if you click the Update button a few times and nothing changes (or it’s so subtle it won’t be noticed easily). |
How to locate sample payloads from the codec
...
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] where we want the sample payloads to be sent in order, one after another when provided.
Special Case: BLE / Beacons required (requires_template_id)
...