REST-API

---

Hello.

Can anybody provide an example of a curl request for this

queryDeviceAttributeEvents

queryDeviceAttributeEvents([criteria : object]) -> events : array
Get logged values of device attributes
Parameters
• criteria (object, optional)
○ deviceId (string|array, optional)
○ attributeName (string|array, optional)
○ after (date, optional)
○ before (date, optional)
○ order (string, optional)
○ orderDirection (string, optional)
○ offset (number, optional)
○ limit (number, optional)
Result
• events (array)
HTTP-Request
GET /api/database/device-attributes/

The example for execution works. I guess that I am not able to construct a valid json string with objects.

curl \
  -X PATCH \
  --header "Content-Type:application/json" \
  --data '{"type": "value", "valueOrExpression": 1337}' \
  --user "user:password" \
  http://your-pimatic/api/variables/the-answer

Please see the following topic for future posts containing code or command snippets. Thanks!
https://forum.pimatic.org/topic/1179/how-to-post-code-snippets-and-alike-on-the-forum

@lopiki i dont understand what you want.

Could you maybe clarify a bit more what you want to do?

sure, I succeded in using Curl as CLI with given example for updating a variable:

curl  -X PATCH  –header “Content-Type:application/json”  –data ‘{“type”:  “value”, “valueOrExpression”: 1337}’  –user “user:password”  http://your-pimatic/api/variables/the-answer

but sending a get request to get a variable value for a specific time I fail.

so I am looking for an example same as given for the execution action

@lopiki said in REST-API:

Can anybody provide an example of a curl request for this

See the following example for a device with id “dht22”. It makes sense to limit the number of matching query results (either use “limit” as I did or specify a time range using “before” or “after”) as massive database queries use a lot of system resources. Note, the jq command is not required. I have only used it below to pretty print the json result returned by curl.

EDIT: Time values for “before” and “after” need to be provided in number of milliseconds since 1970/01/01. It is originating from Javascript “Date” internal time representation which is based on UNIX Epoch Time. Note, however, the epoch time is usually output in seconds,

pi@raspi3:~/pimatic-dev $ curl  -XGET --silent --header "Content-Type:application/json" --user "XXX:XXX" --data '{"criteria": { "limit": 5, "deviceId": "dht22" }}' http://localhost/api/database/device-attributes | jq '.'
{
  "events": [
    {
      "deviceId": "dht22",
      "attributeName": "humidity",
      "type": "number",
      "time": 1532513906420,
      "value": 59.2000007629395
    },
    {
      "deviceId": "dht22",
      "attributeName": "temperature",
      "type": "number",
      "time": 1532513906418,
      "value": 27.2999992370605
    },
    {
      "deviceId": "dht22",
      "attributeName": "humidity",
      "type": "number",
      "time": 1532513600729,
      "value": 59.2999992370605
    },
    {
      "deviceId": "dht22",
      "attributeName": "temperature",
      "type": "number",
      "time": 1532513600728,
      "value": 27.2000007629395
    },
    {
      "deviceId": "dht22",
      "attributeName": "humidity",
      "type": "number",
      "time": 1532513297157,
      "value": 59.5999984741211
    }
  ],
  "success": true
}

Great,
SUCCESS.

seems that I am not good at brackets! And one request went thru but crashed my Pimatic instance. As you advised -> limit

Thanks a lot for these details.

keep up the good work and support. (reminds me to donate again)

@lopiki said in REST-API:

seems that I am not good at brackets!

I am glad this is working for you, now. The code snippet you have posted earlier contains curly quotes “” ’’ rather than straight quotes "" ''. This may cause strange error messages when you copy/paste the command string to the console.Apart from this I must admit the documentation of the REST APIs limited and it would be helpful to have more examples

And one request went thru but crashed my Pimatic instance. As you advised -> limit

Yes, it might even happen the process runs out of memory or Raspbian starts continously swapping (if Swapping is enabled on the system). The built-in database
system is not good at handling large data sets as all the query processing is done in-memory.

keep up the good work and support. (reminds me to donate again)

Thanks! Donations are always welcome, of course