Yiiiiiihaaaaaa! Features Features Features

[ff6347]

We have been busy lately with some new features for you.

1. Delete sensor data

You can now delete specific measurements from your sensor page. Once logged in, use the little checkboxes in front of every row in your values table, below the line chart, and squash those little errors from your data. Thanks to @vogelino for pulling his hair over this one.

2. Manually specify the time of the measurement

When posting records to your sensor's endpoint, you can now pass the property recorded_at with an ISO date-time string (like 2022-5-10T13:24:42Z) to set the date when your data was recorded. If you want to be Berlin specific with your time, add those pesky 2 hours to it. So our example from above would be 2022-5-10T13:24:42+02:00. If you are in another timezone, make sure to pass the right UTC offset. See the Wikipedia page on ISO 8601 to get this right. This is of course optional. If you are okay with our server time just keep your POST requests as they are. For all you TTN folks out there, nothing has changed. We are already using the time from the payload TTN gives us.

{ "measurements": [1, 2, 3], "recorded_at": "2022-5-10T13:24:42Z" }

3. Batch update

Our last goodie for you today: If you need to bring lots of data into stadtpuls.com, you can now do a batch update. Pass a body like the one shown below to your sensor's endpoint and we will try to catch them all (1MB of payload is the limit). The recorded_at property is mandatory here, since applying the same timestamp to all records makes no sense.

{
  "records": [
    { "measurements": [1, 2, 3], "recorded_at": "2022-5-10T13:24:42Z" },
    { "measurements": [4, 5, 6], "recorded_at": "2022-5-10T14:24:42Z" },
    { "measurements": [7, 8, 9], "recorded_at": "2022-5-10T15:24:42Z" }
  ]
}

We will update our docs soon(-ish) to cover all those nice things. Until then feel free to ask any question or report bugs that slipped past us.

Yours truly

stadtpuls.com