The Nwave approach is “all sensors Sensors must be positioned before using”/ bound to parking parking space position in order to generate parking occupancy events and be available via APIs. While a sensor is not positioned you can only see its raw messages getting from it. It looks . The look like a sentence sequence of hexadecimal numbers . It is and are not too useful.
But when you set a sensor position , you open for using the following featuresfunctionality become available:
Device Monitoring - for getting information about sensor health;
Occupancy - for monitoring which allows you to know which sensors are vacant and which are not;
HTTP outgoing calls - for getting occupancy data using HTTP triggers about sensor occupancy states changes;
https://nwaveio.atlassian.net/wiki/pages/resumedraft.action?draftId=1864761385
| Tip |
|---|
Even if you make your first steps in Nwave Console using Test Devices, you should set their positions before using them. |
...
As you can see in the Nwave ecosystem document, Nwave stores sensors' positions in the hierarchy. Before setting a sensor position, you need to create or select an existing project, zone, level and group. Level and group may be created right now in the SPlace App, but project and zone must be registered using Nwave Console and assign labels to spaces (EV, ADA/Disabled, etc).
Using SPlace you can set positions sensor by sensor, or set positions for a Zone of sensors with one step. Both scenarios are considered in our Video Tutorial:
...