Adding more example queries.

Author: jason-fox

docs/iot-agent-json.md

@@ -504,12 +504,21 @@ reading `c` with the context attribute `count` (which is defined as an `Integer`
 > model defines attributes such as `category` or `controlledProperty` which enable queries to be made like:
 >
 > -   _Which **Actuators** currently have a low `batteryLevel`?_
+>
+> `/v2/entities?q=category=="actuator";batteryLevel<0.1`
+>
 > -   _Which **Devices** measuring `fillingLevel` were installed before January 2020?_
 >
+> `/v2/entities?q=controlledProperty=="fillingLevel";dateInstalled<"2020-01-25T00:00:00.000Z"`
+>
 > Obviously static data can be extended as necessary and can also include additional data such as a unique `name` or
 > `serialNumber` for each device should the entity ID be too inflexible for queries.
 >
+> `/v2/entities?q=serialNumber=="XS403001-002"`
+>
 > Additionally devices with a fixed `location` static attribute can also be queried using the Geofencing parameters.
+>
+> `/v2/entities?georel=near;maxDistance:1500&geometry=point&coords=52.5162,13.3777`
 
 You can simulate a dummy IoT device measurement coming from the **Motion Sensor** device `motion001`, by making the
 following request

docs/iot-agent.md

@@ -490,12 +490,21 @@ reading `c` with the context attribute `count` (which is defined as an `Integer`
 > model defines attributes such as `category` or `controlledProperty` which enable queries to be made like:
 >
 > -   _Which **Actuators** currently have a low `batteryLevel`?_
+>
+> `/v2/entities?q=category=="actuator";batteryLevel<0.1`
+>
 > -   _Which **Devices** measuring `fillingLevel` were installed before January 2020?_
 >
+> `/v2/entities?q=controlledProperty=="fillingLevel";dateInstalled<"2020-01-25T00:00:00.000Z"`
+>
 > Obviously static data can be extended as necessary and can also include additional data such as a unique `name` or
 > `serialNumber` for each device should the entity ID be too inflexible for queries.
 >
+> `/v2/entities?q=serialNumber=="XS403001-002"`
+>
 > Additionally devices with a fixed `location` static attribute can also be queried using the Geofencing parameters.
+>
+> `/v2/entities?georel=near;maxDistance:1500&geometry=point&coords=52.5162,13.3777`
 
 You can simulate a dummy IoT device measurement coming from the **Motion Sensor** device `motion001`, by making the
 following request